Great showcase of the superpower that comes with using @bazelbuild and hermetic-llvm.
Using remote executors and distributed Thin LTO to dramatically reduce the link time of large binaries such as LLVM.
1 min link with distributed Thin LTO.
15 min without
Links below ⬇️
BazelCon Training Day in Amsterdam is now live!
Whether you're getting to know Bazel or you're already a pro, we have a session for you.
Spaces are limited, so securing your spot early is highly recommended.
Check out this years schedule👇
events.linuxfoundation.org/b…
this is very cool! what's your strategy? when i had to do this to build a bazel project with hermetic_cc_toolchain, i just used cross-ng a helper script to pre-compile static versions of libstdc so they could be plugged into a toolchain: github.com/sin-ack/gnulibs
Porting all versions of libstdc from source using @bazelbuild since GCC 8 to 17 =>✅
This closes the loop of Linux binary portability. And re-opens the door to CUDA hermetic compilation since they want libstdc headers.
And it has now moved under the hermeticbuild org and available in the @bazelbuild BCR under `rules_zig`. It is battle tested, powers all zig compilation at @zml_ai, give it a try ! Link below ⬇️
I've been working extensively on the @bazelbuild ruleset for @ziglang this past 12 months. In today's release:
- Integrate zig with any other language
- Use a Zig compiler compiled from (your) sources
- Cross language LTO
- ZLS support
- Translate-C
With @bazelbuild and the hermetic LLVM BCR module which codex already uses, they could cross compile for every single Linux distro specs and be guaranteed correctness (glibc, kernel and libstdc version).