fix: add -g0 to zig presets to eliminate 11GB debug info bloat#21071
Merged
ludamad merged 2 commits intomerge-train/barretenbergfrom Mar 3, 2026
Merged
fix: add -g0 to zig presets to eliminate 11GB debug info bloat#21071ludamad merged 2 commits intomerge-train/barretenbergfrom
ludamad merged 2 commits intomerge-train/barretenbergfrom
Conversation
ludamad
added
ci-draft
ludamad
approved these changes
Mar 3, 2026
AztecBot
force-pushed
the
claudebox/1a779e17d1e4caac-2
branch
from
f4b260c to
8ba75e9
Compare
The -g0 flags set in CMakePresets.json leak to LMDB's make -e build, replacing its CFLAGS entirely (losing -O2, -pthread, -fPIC, etc). This causes zig cc to insert UBSan instrumentation at -O0, leading to undefined __ubsan_handle_* symbols at link time. Fix by unsetting CFLAGS/CXXFLAGS in the cmake -E env wrapper so LMDB uses its own Makefile-defined CFLAGS.
Collaborator
Author
|
❌ Failed to cherry-pick to |
AztecBot
added a commit
that referenced
this pull request
Mar 3, 2026
Zig cc injects DWARF debug info into every object file by default, even in Release (-O3) mode. This inflates the barretenberg build directory from **2.8 GB to 14.0 GB** (5x blowup). Adding `-g0` to suppress this brings zig builds in line with system clang builds. | Artifact | Before (-g0) | After (-g0) | Reduction | |----------|-------------|-------------|-----------| | Total build dir | 14.0 GB | 2.8 GB | **80%** | | libvm2.a | 1,406 MB | 219 MB | 84% | | bb-avm | 1,271 MB | 182 MB | 86% | | prover.cpp.o | 486 MB | 31 MB | 94% | - Adds `"CFLAGS": "-g0", "CXXFLAGS": "-g0"` to the `clang20` preset (native zig builds) - Adds the same to the `zig-base` preset (all cross-compilation presets inherit from this) - Presets that intentionally use `-g` (tracy, debug, xray) override these flags as expected - Machine code output is identical (verified: .text sections are byte-for-byte the same) - Incremental builds are fully preserved - Build time improves marginally (5m29s → 5m06s) Full analysis: https://gist.github.com/AztecBot/5c919316852d4d66095d0eefaa1a7c00 ClaudeBox log: http://ci.aztec-labs.com/1a779e17d1e4caac-2
This was referenced Mar 3, 2026
ludamad
pushed a commit
that referenced
this pull request
Mar 3, 2026
…ort #21071) (#21085) ## Summary Backport of #21071 to v4. Adds `-g0` to zig cross-compilation presets to suppress DWARF debug info that inflates the build directory from 2.8 GB to 14.0 GB. Also unsets CFLAGS/CXXFLAGS for the lmdb external build to prevent `-g0` from interfering. ### Conflict resolution The `clang20` preset on v4 uses system `clang-20` (not zig), so the `-g0` addition to that preset was dropped — it only applies to zig's debug info behavior. The `zig-base` preset change (which all cross-compilation presets inherit) and the `lmdb.cmake` change applied cleanly. ClaudeBox log: http://ci.aztec-labs.com/df32ffacdebfa007-1
johnathan79717
pushed a commit
that referenced
this pull request
Mar 4, 2026
## Summary Zig cc injects DWARF debug info into every object file by default, even in Release (-O3) mode. This inflates the barretenberg build directory from **2.8 GB to 14.0 GB** (5x blowup). Adding `-g0` to suppress this brings zig builds in line with system clang builds. ### Key numbers (measured on 186-core machine with full AVM build): | Artifact | Before (-g0) | After (-g0) | Reduction | |----------|-------------|-------------|-----------| | Total build dir | 14.0 GB | 2.8 GB | **80%** | | libvm2.a | 1,406 MB | 219 MB | 84% | | bb-avm | 1,271 MB | 182 MB | 86% | | prover.cpp.o | 486 MB | 31 MB | 94% | ### What this changes - Adds `"CFLAGS": "-g0", "CXXFLAGS": "-g0"` to the `clang20` preset (native zig builds) - Adds the same to the `zig-base` preset (all cross-compilation presets inherit from this) - Presets that intentionally use `-g` (tracy, debug, xray) override these flags as expected ### What it does NOT change - Machine code output is identical (verified: .text sections are byte-for-byte the same) - Incremental builds are fully preserved - Build time improves marginally (5m29s → 5m06s) Full analysis: https://gist.github.com/AztecBot/5c919316852d4d66095d0eefaa1a7c00 ClaudeBox log: http://ci.aztec-labs.com/1a779e17d1e4caac-2
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 5, 2026
BEGIN_COMMIT_OVERRIDE fix: add -g0 to zig presets to eliminate 11GB debug info bloat (#21071) fix: resolve flaky p2p_client test race condition on ARM64 (#21088) chore: remove domain iteration macros and address backing memory race (#20988) fix: [ECCVM] added domain separation for the multiset equality check. (#20352) feat: hybrid CRS hash verification — 8MB chunks, parallel, span-based (#21113) chore: unify splitting scalars interface (#20805) chore: add a unique id to each origin tag (#20924) chore: Native curve audit (#20936) chore: Update bootstrap in test vk haven't changed script (#21153) END_COMMIT_OVERRIDE
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 6, 2026
BEGIN_COMMIT_OVERRIDE fix: add -g0 to zig presets to eliminate 11GB debug info bloat (#21071) fix: resolve flaky p2p_client test race condition on ARM64 (#21088) chore: remove domain iteration macros and address backing memory race (#20988) fix: [ECCVM] added domain separation for the multiset equality check. (#20352) feat: hybrid CRS hash verification — 8MB chunks, parallel, span-based (#21113) chore: unify splitting scalars interface (#20805) chore: add a unique id to each origin tag (#20924) chore: Native curve audit (#20936) chore: Update bootstrap in test vk haven't changed script (#21153) fix: use reduced form in WASM FromMontgomeryForm test (#21164) chore: erase ephemeral secrets from memory in schnorr and aes (#21106) chore: suppress clangd target triple version diagnostic (#21180) feat: Optimise new claim calculation (#21179) docs: add Quick Start build instructions to barretenberg README (#20951) feat: batched chonk verification (#21083) fix: link libc++ instead of libstdc++ for Rust FFI on Linux (#21203) fix: [ECCVM] in the transcript table, no-ops force the next accumulator to be 0. (#20849) fix: resolve merge-train conflict with next (zig wrapper scripts + -g0) (#21201) fix: [ECCVM] rare edge case completeness issue when `z1 == 0` but `z2 != 0` (#20858) fix: use actual data extent for CommitmentKey in HypernovaDeciderProver (#21206) END_COMMIT_OVERRIDE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Zig cc injects DWARF debug info into every object file by default, even in Release (-O3) mode. This inflates the barretenberg build directory from 2.8 GB to 14.0 GB (5x blowup). Adding
-g0to suppress this brings zig builds in line with system clang builds.Key numbers (measured on 186-core machine with full AVM build):
What this changes
"CFLAGS": "-g0", "CXXFLAGS": "-g0"to theclang20preset (native zig builds)zig-basepreset (all cross-compilation presets inherit from this)-g(tracy, debug, xray) override these flags as expectedWhat it does NOT change
Full analysis: https://gist.github.com/AztecBot/5c919316852d4d66095d0eefaa1a7c00
ClaudeBox log: http://ci.aztec-labs.com/1a779e17d1e4caac-2