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

update readme: use bazel --batch clean

main
Motiejus Jakštys 2022-11-29 16:17:00 +02:00
parent a7fdcd0457
commit 020ff7ad38
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -16,7 +16,7 @@ Steps to reproduce
Baseline is llvm14: 12-13 seconds:
```
$ bazel clean; bazel --batch build --extra_toolchains=@llvm_toolchain//:cc-toolchain-x86_64-linux ...
bazel --batch clean; bazel --batch build --extra_toolchains=@llvm_toolchain//:cc-toolchain-x86_64-linux ...
INFO: Elapsed time: 12.454s, Critical Path: 1.11s
```
@ -24,7 +24,7 @@ zig cc without the sandbox. Which means different invocations of `zig cc` will
see that all files in `zig_lib_dir` are the same file. 17 seconds:
```
bazel clean; bazel --batch build --spawn_strategy=local --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
bazel --batch clean; bazel --batch build --spawn_strategy=local --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
INFO: Elapsed time: 17.021s, Critical Path: 1.67s
```
@ -33,7 +33,7 @@ zig_sdk, are put to `/dev/shm`. However, they are all symlinks, which means zig
will re-hash all it's dependencies. 42 seconds:
```
bazel clean; bazel --batch build --sandbox_base=/dev/shm --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
bazel --batch clean; bazel --batch build --sandbox_base=/dev/shm --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
INFO: Elapsed time: 42.251s, Critical Path: 5.26s
```
@ -41,7 +41,7 @@ zig cc plain: 142 seconds. Sandbox is on a real disk, which means it will take
even longer to re-hash all its dependencies:
```
$ bazel clean; bazel --batch build --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
bazel --batch clean; bazel --batch build --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 ...
INFO: Elapsed time: 142.264s, Critical Path: 20.65s
```