https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #10) > What about fixing the -g interaction? Much like how -g shouldn't affect > code generation, it probably shouldn't be affecting warnings like this. > > There may be more we can/should do here, but that seems like a good place to > start. Agreed, I'm looking into that too. Fixing it won't avoid the warning though, just make it more consistent (see comment #4).
