This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH RFC: gcc 4.1 extern inline patch, take 2


Jakub Jelinek <jakub@redhat.com> writes:

> Even a warning will break many packages out there that use -Werror,
> especially if you warn also in system headers.  Have you checked you
> aren't getting dozens of warnings for each source file
> when you compile with -std=c99 on Linux?  I have in my /usr/include
> on Linux several hundred of extern inline uses...

But we don't warn in system headers.  And indeed I checked, and the
warnings in system headers only appear with -Wsystem-headers.

If you are arguing that there are packages out there using gcc 4.1.x
which use all of -Werror, -std=c99, and "extern inline" functions,
then I concede that we will break those packages if they upgrade to
gcc 4.1.3.

Am I the only person who sees the advantage to warning about cases
where gcc is going to change in an incompatible fashion?  Does
everybody think it is OK to only warn for a single release before
making an incompatible change?

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]