https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87407
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |125576
See Also|https://bugs.llvm.org/show_ |https://github.com/llvm/llv
|bug.cgi?id=22712 |m-project/issues/23086
--- Comment #15 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #14)
> (In reply to Eric Gallager from comment #13)
> > (In reply to Andrew Pinski from comment #5)
> > > Test the warning out on clang from a header file and you will see you get
> > > the warning in the header too. As I said I actually ran into this while
> > > working on the vpp project and cursed clang for having this warning turned
> > > on.
> >
> > I think something similar happened with the gdb project; I'll try to find it
> > later...
>
> Right, found it, thread starting here:
> https://sourceware.org/ml/gdb/2015-02/msg00045.html
>
> cc-ing people from it.
>
> Also, corresponding clang bug is here:
> https://bugs.llvm.org/show_bug.cgi?id=22712
After the migration to GitHub, the clang bug is now:
https://github.com/llvm/llvm-project/issues/23086
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125576
[Bug 125576] [meta-bug] clang/LLVM compatibility
