GCC -Wall and -Wextra diagnostic overlap and prioritization

Question

The GNU Compiler Collection (GCC) utilizes a tiered system of warning flags, primarily -Wall and -Wextra, to alert developers to potentially problematic code. While these flags enable a broad set of diagnostics, there is often overlap in the types of issues they detect, and the internal categorization of these diagnostics into warning, error, or note levels can vary between compiler releases.

When implementing strict coding standards using -Werror, the lack of a granular, documented mapping between specific diagnostic triggers and their parent flag groups can lead to inconsistent build failures across different GCC versions (e.g., GCC 11 vs GCC 13).

How does GCC determine the priority of a diagnostic when it is triggered by both -Wall and -Wextra?
  Is there a documented mechanism to identify which specific warning flag is responsible for a diagnostic without manually testing -Wno- suppressions?

Muntasir · Answer

No Runtime Priority Between -Wall and -Wextra

GCC treats -Wall and -Wextra as additive flag groups. When a diagnostic is enabled by both, there is no internal priority mechanism that prefers one over the other. The warning fires exactly once under the union of their scopes. The compiler does not track or report which group "won"; it simply emits the diagnostic because at least one active flag group enables it.

Identify the Triggering Flag with -fdiagnostics-show-option

Since GCC 4.5, the flag -fdiagnostics-show-option appends the specific option name that enabled each diagnostic to the warning message. This is the documented, supported way to determine whether a warning came from -Wall, -Wextra, or another group without manual -Wno- testing.

gcc -Wall -Wextra -fdiagnostics-show-option -c test.c

Output lines will end with tags such as [-Wunused-variable] or [-Wextra], making the origin explicit.

Version Differences Affect -Werror Stability

The exact set of warnings enabled by -Wall versus -Wextra changes between GCC releases (e.g., GCC 11 vs. GCC 13). New warnings are often added to -Wextra first and may later move into -Wall. This migration is why a codebase that builds cleanly with -Wall -Wextra -Werror on one GCC version can fail on another without any source changes.

Practical Verification Steps

Compile with -fdiagnostics-show-option to see the enabling flag for each diagnostic.
If you need to suppress a specific warning, use -Wno-<warning-name> (e.g., -Wno-unused-parameter) after confirming the name via step 1.
For a full catalog of which flags enable which warnings in your installed GCC, run:
```
gcc -Q --help=recursive | grep '^-W'
```
To compare flag-to-diagnostic mappings across versions, run the same command on each compiler and diff the output.

Caveats

-fdiagnostics-show-option is unavailable in GCC versions older than 4.5.
Using -Wno-<warning> disables that diagnostic globally, even if it is also enabled by another flag group with overlapping coverage.
Undocumented changes in minor releases can shift warning membership between -Wall and -Wextra, so pinning the GCC version in CI is the most reliable way to avoid surprise -Werror failures.

GCC -Wall and -Wextra diagnostic overlap and prioritization

1 answer

No Runtime Priority Between -Wall and -Wextra

Identify the Triggering Flag with -fdiagnostics-show-option

Version Differences Affect -Werror Stability

Practical Verification Steps

Caveats

Your perspective belongs here.

0 question comments