-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal compiler error: can't buffer lints after HIR lowering #65253
Comments
It'd be helpful to have a more minimal example here I suspect -- for example, at least reducing to a single crate. cc @estebank since this deals with diagnostic machinery |
It seems like this was introduced a month ago in #64066, f7434ae#diff-fe6fbe1c488f33762a812dfee7e5e919R509-R515 |
I think I find the solution on my side: the removal of |
apache/incubator-teaclave-sgx-sdk@librustc-bug-report...test-2019-10 A working branch is baidu/rust-sgx-sdk : test-2019-10. After I enable this line, the compiler starts to fail. |
The minimum sample is as follows:
and compile by
|
Fixed in #65283. |
Cool! |
stability: Do not use `buffer_lint` after lowering to HIR Fixes rust-lang#65253
stability: Do not use `buffer_lint` after lowering to HIR Fixes rust-lang#65253
stability: Do not use `buffer_lint` after lowering to HIR Fixes rust-lang#65253
Hi there,
I'm updating rust-sgx-sdk (solving rust-sgx-sdk #161) to use latest rust nightly compiler to help the error info more ergonomic by the help of #60561. However, the compiler always panics. Your help would be very much helpful.
The current code is at https://github.com/baidu/rust-sgx-sdk/tree/librustc-bug-report . To reproduce this bug, please checkout branch
librustc-bug-report
and build sgx_tstd as follows:And the reproducible failure info is:
Meta
rustc --version --verbose
:rustc 1.40.0-nightly (032a53a 2019-10-03)
binary: rustc
commit-hash: 032a53a
commit-date: 2019-10-03
host: x86_64-unknown-linux-gnu
release: 1.40.0-nightly
LLVM version: 9.0
Backtrace:
The text was updated successfully, but these errors were encountered: