Stability Issues (Broken Pipe) in Clang 21+ Toolchains on GitHub Actions #1
Description
I am reporting a recurring issue regarding build stability when using ZyCromerZ Clang versions 21 and above, specifically compared to Clang 20 and older versions.
Observation:
Clang 20 and below: The build process is perfectly stable with no errors.
Clang 21 and above: Encountering frequent broken pipe errors during the compilation phase.
Test Environment & Logs:
Environment: GitHub Actions (Ubuntu 24.04/22.04
), 16GB Swap enabled.
Scenario 1 (4 Cores / -j4): The build completes, but broken pipe errors appeared 318 times in the logs.
Scenario 2 (2 Cores / -j2): The stability improved significantly, and the broken pipe errors were reduced to only 2 occurrences.
Impact:
Although the build sometimes finishes, the high frequency of pipe errors suggests an internal issue with how the toolchain handles multi-threading or memory management in newer LLVM versions when running on shared CI environments.
Request:
Could you please look into why Clang 21+ is more prone to these errors compared to Clang 20? Is there a specific optimization or flag in the newer toolchains that might be causing this instability under load?
Note from the user:
"I want to clarify that I am not a professional developer or a compiler expert; I am just an enthusiast trying to build and experiment with this toolchain. However, the difference in stability between versions is very noticeable during my tests."