In Rust's case I wrote up an autobatching scheme years ago, requiring a straightforward three way PR classification, but doing it well requires more CI budget than we have right now. Probably could deploy a simpler version of it that gets us some wins.
-
-
Replying to @ManishEarth @stephentyrone
I mean I'm nowhere near the purse strings but this has literally been an issue off-and-on since I .. uh .. left the project. We were having an argument over it that very week. It means prioritizing cycle time in a way that seems to resist all rational planning. I don't get it.
1 reply 0 retweets 4 likes -
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.
2 replies 0 retweets 10 likes -
I’m fine with investing in automatic rollups (the fact that we have to do them bugs me too), but you lost me at “stop all feature/bug fix work until the compiler is 10x faster”.
1 reply 0 retweets 3 likes -
Replying to @pcwalton @graydon_pub and
I’m not even convinced it’s possible for Rust to compile that fast without simplifying the language a lot. Even if it were, you’re talking about a complete rewrite of major subsystems. Like either “rewrite the whole typechecker” or “rewrite LLVM”.
2 replies 0 retweets 8 likes -
Replying to @BRIAN_____ @graydon_pub and
Can you describe how to make rustc 10x as fast? Everyone says that of course it’s possible, 10x is easy to get, it’s just that nobody cares about compiler perf, etc. etc., And then everyone who tries ends up with, like, a perf boost of 10% if that.
3 replies 0 retweets 3 likes -
This Tweet is unavailable.
-
Replying to @sayrer @BRIAN_____ and
The self-hosting nature of the compile means that there is a strong serial bottleneck. The build time is not something that a caching build system will help with. Believe me, if it were, we’d have fixed that long ago.
1 reply 0 retweets 0 likes
We already cache LLVM in the rustc build system! It’s just that we don’t appear to in *Travis* for whatever reason. It’s important to understand the problems first before jumping on Bazel as the solution. I don’t think this is a build issue at all.
-
This Tweet is unavailable.
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.