Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's too early to take numbers until the new task scheduler lands. Also the compiler in general is not very fast yet.



Are you talking about the speed of the compiler itself, or the speed of the code produced by the compiler? If you're talking about the speed of produced code, then I think the compiler is actually fairly decent, since they rely LLVM to optimize the code. Maybe not performance equivalent to C, but still very decent performance.


Speed of the compiler itself. I understand it's not related to the benchmark discussion as such but it's the first thing someone will notice new to rust. Compiling rust itself takes for ages.


Yes, I would like to spend time in the next release cycle working on compiler performance. To start with, I have a patch that improves performance of translation by 15%.

brson and I have been discussing using stage0 LLVM for subsequent stages, so that LLVM itself won't have to be compiled. This should reduce the amount of time required to compile Rust by a lot.


A clang build was recently taken out of that process, though I haven't tried building since then.


It took me ~1 hour to compile on my MacBook Air.


Ouch. Did you run the build with multiple jobs? (Parallel builds have been a bit messed up because of fetching the bootstrap, but you can coax it into working.)


I just did ./configure && make && sudo make install.


I don't think I've actually tried that, except on my netbook (conclusion: don't try to build Rust on a netbook.) I have made a habit of typing supplying `-j 8` to make. Note: if it hasn't been fixed yet, you'll need to fetch the bootstrap compiler before that will work.


yup, me too.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: