https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641
--- Comment #2 from Pierre Ossman <ossman at cendio dot se> --- It's problematic when you are trying to adopt a "no warnings" approach to your development. This severely undermines that, as you train the developers back in to ignoring warning messages. It also seems excessive to still warn about this almost 10 years after the change? Most users would likely be compiling with compilers of similar version (i.e. same ABI). gcc's own documentation even suggests that is how gcc policy is: > Since G++ now defaults to updating the ABI with each major release, normally > -Wabi warns only about C++ ABI compatibility problems if there is a check > added later in a release series for an ABI issue discovered since the initial > release. -Wabi warns about more things if an older ABI version is selected > (with -fabi-version=n). Is there a way to disable this when configuring gcc? Or do we need to patch gcc for that?
