On Wed, Jul 9, 2008 at 6:50 PM, Ben Elliston <[EMAIL PROTECTED]> wrote: >> In this case, I argue that this code is always compiled with a C >> compiler, and should never be compiled by a C++ compiler. Therefore, >> I believe it is wrong for this code to be compiled with the >> -Wc++-compat warning enabled. This should be fixed somewhere in the >> configure script and/or Makefile. > > I agree. Aren't there some potential nasty problems here with the > shared libgcc being compiled with a C++ compiler and the ABI changing > one day? (The C ABI, could, too, but it's much less likely.)
if libgcc is at the intersection of GNU C and GNU C++ -- which it should be -- there is no problem that the C++ ABI will change without the C ABI also changing. -- Gaby
