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
Should be able to change stack limit #643
Comments
@oli-obk did that get lost in the move to rustc? |
I think it was. From quickly grepping rustc's repository it looks like this value is hardcoded to 100: I didn't find any place where this field gets changed (https://github.com/rust-lang/rust/search?q=const_eval_stack_frame_limit). Not sure about the other configurations ( |
Hm. yes, they seem to have gotten lost. We should probably just remove that limitation entirely, just like we got rid of the memory limit. |
Currently rustc uses this Do we want to keep this limit for compilation? |
For const eval we can just use the recursion limit, which is already configurable by users |
The bug part of this is now "fixed" by removing this text from I am turning this into a ticket to track the enhancement request that the stack limit should be changeable. |
I think rust-lang/rust#66726 should address this? I would just like to note that I hit the stack frame limit exactly, which prompted me to check how difficult it'd be to change this:
|
It is currently not possible to change the stack limit. It would be great to get that functionality back!
Original report
Maybe I'm doing something wrong, but I'm unable to set the stack limit for miri.
If I call
cargo miri test --help
it says:After adding
#![cfg_attr(miri, stack_limit = 100000)]
to my
lib.rs
I get "stack limit reached error" at the same depth.The text was updated successfully, but these errors were encountered: