diff options
author | Richard Biener <rguenther@suse.de> | 2023-03-24 10:19:55 +0100 |
---|---|---|
committer | Richard Biener <rguenther@suse.de> | 2023-03-28 08:52:01 +0200 |
commit | 33312336d576a0aaa4f425686d652b09151a7c24 (patch) | |
tree | 68f75376ab8aa016b5d5827590db835152ede32b /fixincludes | |
parent | cc4b7d6bb3b1ec6c52aa6bce1c892218d4c1a2f4 (diff) | |
download | gcc-33312336d576a0aaa4f425686d652b09151a7c24.zip gcc-33312336d576a0aaa4f425686d652b09151a7c24.tar.gz gcc-33312336d576a0aaa4f425686d652b09151a7c24.tar.bz2 |
Remove Negative(gwarf-) from gdwarf
Prior to the removal of STABS support the gdwarf, gstabs, ... options
formed a cycle with their Negative(..) option attribute. But that
didn't actually have any effect since most of the options also
are Joined or JoinedOrMissing for which there's no pruning of options
and so once ran into the set_debug_level diagnostics reporting
conflicting debug formats.
The following removes the remains of that cycle, which is a
Negative option from gdwarf to gdwarf-. With RejectNegative
added the expected effect of -gdwarf-4 -gdwarf would be to
enable DWARF5 support (but this doesn't happen for some reason).
I think the more sensible behavior is that seen and implemented
in opts.cc, the more specific -gdwarf-4 determines the DWARF level
and a later or earlier -gdwarf becomes a no-op. So the
Negative(..) annotation on gdwarf is just confusing.
* common.opt (gdwarf): Remove Negative(gdwarf-).
Diffstat (limited to 'fixincludes')
0 files changed, 0 insertions, 0 deletions