-
Notifications
You must be signed in to change notification settings - Fork 13k
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
ICE when hitting recursion limit with crate attrs #105700
Labels
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
C-bug
Category: This is a bug.
glacier
ICE tracked in rust-lang/glacier.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
jruderman
added
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
Dec 14, 2022
Noratrieb
added
the
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
label
Dec 14, 2022
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 20, 2023
create dummy placeholder crate to prevent compiler from panicing This PR is to address the panic found in rust-lang#105700. There are 2 separate things going on with this panic. First the code could not generate a dummy response for crate fragment types when it hits the recursion limit. This PR adds the method to the trait implementation for `DymmyResult` to be able to create a dummy crate node. This stops the panic from happening. The second thing that is not addressed (and maybe does not need addressing? 🤷🏻) is that when you have multiple attributes it ends up treating attributes that follow another as being the result of expanding the former (maybe there is a better way to say that). So you end up hitting the recursion limit. Even though you would think there is no expansion happening here. If you did not hit the recursion limit the compiler would output that `invalid_attribute` does not exists. But it currently exits before the resolution step when the recursion limit is reached here.
Fixed by #107721 |
Alexendoo
added a commit
to Alexendoo/rust
that referenced
this issue
Feb 22, 2023
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Feb 22, 2023
…errors Fix test filename for rust-lang#105700 The test is for rust-lang#105700 rather than rust-lang#21102
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Feb 22, 2023
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#107736 ( Rename atomic 'as_mut_ptr' to 'as_ptr' to match Cell (ref rust-lang#66893) ) - rust-lang#108176 (Don't delay `ReError` bug during lexical region resolve) - rust-lang#108315 (Lint dead code in closures and generators) - rust-lang#108342 (apply query response: actually define opaque types) - rust-lang#108344 (Fix test filename for rust-lang#105700) - rust-lang#108353 (resolve: Remove `ImportResolver`) Failed merges: - rust-lang#107911 (Add check for invalid #[macro_export] arguments) r? `@ghost` `@rustbot` modify labels: rollup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
C-bug
Category: This is a bug.
glacier
ICE tracked in rust-lang/glacier.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Found with a modified fuzz-rustc
Code
ICE
thread
<unnamed>
panicked at 'internal error: entered unreachable code', compiler/rustc_expand/src/base.rs:446Backtrace
Regression
Regression in nightly-2021-12-02, perhaps from #91313 (@petrochenkov)
Might be related to #99478
Version
The text was updated successfully, but these errors were encountered: