-
Notifications
You must be signed in to change notification settings - Fork 49
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
Bootstrapping rustc
with wee_alloc
as the global allocator should work
#10
Comments
Running
However, I'm exteremely not sure that I set up things well. You can take a look at the change here |
Did you build with debug info? I'd expect that to give function names rather than I was imagining trying to bootstrap rustc with the unix version of |
Ahaha, I should have figure it out! Will try : )
Nope, im even not sure how to do it. But yeah, AFAIK, debug info + latest |
I'm not sure what this means, but compiling stage1 with stage0 which uses Can it be just so awfuly slow? UPD: CPU utilization is not constant 100% and memory consumption seems to be raising (although, very slowly, from 250 mb to 390 in 1hr) |
I've never actually bootstrapped rustc myself, so I don't know what is a reasonably amount of time... Maybe try a normal bootstrap and compare? |
Just asked aturon, and he said he expects something closer to half an hour... Seems like we have some low hanging perf work to do! |
Yeah usualy it takea around 0.5 to get stage2 with default settings. In this case it takes more that two hours to compile single crate! |
(it still didnt complete yet) |
lol... this is what happens when there's been zero performance work yet... |
Aaaaaaand it's done! Sort of
(and yes, it turns out it stucked on |
Looks like we have some work cut out for us :) |
rustc
with wee_alloc
as the global allocatorrustc
with wee_alloc
as the global allocator should work
This would be a nice smoke test :)
The text was updated successfully, but these errors were encountered: