motiejus/test-zig-cc
1
Fork 0
Code Releases Activity

add more prose to README

Browse Source
This commit is contained in:
Motiejus Jakštys 2022-12-20 12:54:45 +02:00
parent 535015e76b
commit b6f4798319
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -105,10 +105,25 @@ Explanation:
recommended with both bazel-zig-cc and a nontrivial sysroot. As a result, recommended with both bazel-zig-cc and a nontrivial sysroot. As a result,
this is the most important benchmark to look at. this is the most important benchmark to look at.
Extracting the fastest meaningful benchmarks in all categories:
'bazel build --experimental_reuse_sandbox_directories //...' ran
2.77 ± 0.08 times faster than 'bazel build --extra_toolchains=@llvm_toolchain_with_sysroot//:cc-toolchain-x86_64-linux --experimental_reuse_sandbox_directories //...'
2.85 ± 0.07 times faster than 'bazel build --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 --experimental_reuse_sandbox_directories //...'
This demonstrates that **adding a hermetic toolchain to a project caused 177%
slowdown on this project**. Note that we are not counting `llvm_toolchain//...`
as a real toolchain -- one needs a sysroot to compile anything meaningful
anyway (which zig bundles with the compiler).
Once we have determined that a hermetic C++ toolchain is required, bazel-zig-cc
is about 2.8% slower than its contender plain llvm14.
Flame graphs and discussion Flame graphs and discussion
--------------------------- ---------------------------
Flame graphs in results/. Only of historical interest, because the original Flame graphs in results/. Only of historical interest, because the biggest
performance issues have been resolved with a combination of zig and performance issues have been resolved with a combination of zig and
bazel-zig-cc changes. bazel-zig-cc changes.