-
Notifications
You must be signed in to change notification settings - Fork 356
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
dogfooding miri #282
Comments
Where does that flag have to be added? |
Good question. I turned it on unconditionally in the source... I should probably add a config.toml flag |
This issue is pretty old, but every few months someone on the community Discord will point out some dodgy code in rustc and everyone will clamor that we should run Miri on rustc or Miri on Miri. So I think it's fair to say that there is ambient interest in this, if it were made more accessible. I looked over the instructions above and I think there is a bit missing.
|
only
that was just me hoping it would run faster that way ^^
yea that's really old. I think if you install miri in step 3 you can use |
With this in my
I ran this to build rustc:
Then based on the contents of the
Then tried to
And all I see is:
and more missing There is for example a |
The rustc-dev compoment needs to be installed. |
This issue is just to document my process. It's ridiculously slow, but a lot of fun.
-Zalways-encode-mir
(stage2 build necessary)stage2
)RUSTFLAGS=-Zalways-encode-mir -Zmir-opt-level=3
--extern
flags and the-L dependency=...
flagRUSTFLAGS=-Zalways-encode-mir -Zmir-opt-level=3 rustup run stage2 cargo run --bin miri/bin/miri.rs --verbose -- -Zmir-opt-level=3
and append all the flags from 4. after that command lineThe text was updated successfully, but these errors were encountered: