b1083d3751
A wider audit revealed that semver=(snapshot) is genuinely ambiguous in
CE configs:
- IBM Advance Toolchain: ppc64g8/g9, ppc64leg8/g9, plus c/fortran/gimple
variants — 12 compilers — are stable AT releases (named "AT12.0",
"AT13.0") that happen to incorporate an upstream gcc snapshot. Their
semver=(snapshot) is descriptive, not a release-track signal. The
prior heuristic mis-classified them as nightly.
- ppc64clang/ppc64leclang/cppc64clang/cppc64leclang are genuine clang
trunk builds, also using semver=(snapshot). These DO want to be
classified nightly.
Two compilers, one tag — no clean way to distinguish from semver alone.
Resolution:
- Remove 'snapshot' from NIGHTLY_TAGS so the default for (snapshot) is
the safer of the two ('stable' if isNightly=false, 'experimental' if
isNightly=true). The 12 IBM AT compilers now correctly classify as
stable without intervention.
- Add releaseTrack=nightly overrides on the 4 PPC clang trunks. This
is the canonical use of the override mechanism: the maintainer knows
the compiler is conventionally nightly but the structural metadata
can't say so.
Net: 12 IBM AT compilers fixed, 4 PPC clangs explicitly preserved as
nightly. (trunk)/(main)/parens-stripped 'main'/'master'/'nightly' tags
are still recognised as nightly via the heuristic.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
How do I ?
This is a how-to guide for the user-interface presented by Compiler Explorer. This doesn't cover the details of how to set up or modify Compiler Explorer for your own needs. For that, please check the documents which already cover topics like:
- Adding a language
- Adding a compiler
- Adding a library
- Adding a tool
- and many more at compiler-explorer/docs
Fast links:
Change the assembly syntax from Intel
The option to switch assembly from Intel to AT&T syntax is present in the Output option of each compiler. If enough
space is not present, the option also presents itself as the gear symbol (⚙)
Compare the time taken by compilation and networking
This is the symbol that looks like a bar graph (📊). If your compilations are taking long, you can use this to check the time taken by:
- Networking, JavaScript, waiting for events, etc.
- Checking the cache and retrieving from it on a cache-hit
- Compilation (on force compilation or cache-miss)
- Parsing the generated assembly before presenting it
View intermediate information provided by the compilers
Though both GCC and Clang create supplementary outputs along with assembly (shown by default), and an executable (created if an executor has been added), the exact nature of the outputs and their formats differ between the compilers.
GCC allows the Tree, IPA, RTL and graph outputs, while Clang allows optimization, AST, IR and graph outputs. Some outputs (e.g. RTL or graph) also have a rich set of options in the UI to enable focussing on a particular function or compiler stage.