Like if someone with the correct authority said "we don't do any more feature work or bug fixing or anything until cycle time is down to 10 minutes", it would get solved. It's not like compilers that bootstrap and self-test that fast (without $infinite_aws_bill) can't be written.
As we all know, LLVM could do a lot better with certain optimizations, but nobody thinks a 2x across-the-board runtime performance (or compile time) increase is likely with LLVM improvements. The point of diminishing returns was long past. MIR is fast approaching this point too.
-
-
Maybe. Maybe not. Getting a 5% benchmark improvement by just tweaking a bunch of PartialEq::eq functions makes me think MIR peephole optimisations could change a lot.
-
I’ve seen enough potential silver bullets go by at this point to know better. :) Inlining and copy prop was far more potentially impactful, and it didn’t really help much.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.