Ian Lance Taylor - Re: PATCH RFC: gcc 4.1 extern inline patch, take 2 (original) (raw)

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

• From: Ian Lance Taylor
• To: Eric Botcazou
• Cc: gcc-patches at gcc dot gnu dot org, Jakub Jelinek , "Joseph S. Myers"
• Date: 09 Feb 2007 08:26:15 -0800
• Subject: Re: PATCH RFC: gcc 4.1 extern inline patch, take 2
• References: <m3zm7ng9rz.fsf@localhost.localdomain> <20070209155610.GC22959@devserv.devel.redhat.com> <m3wt2re2lt.fsf@localhost.localdomain> <200702091714.15345.ebotcazou@libertysurf.fr>

Eric Botcazou ebotcazou@libertysurf.fr writes:

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?

4.1.3 seems to be a little late in the 4.1.x series, no?

Yes, it definitely does. If I were in charge, I would move the incompatible change from gcc 4.3 to gcc 4.4.

I'm trying to work within certain constraints. As I said before, I think the 4.1.3 issue is putting a philosophical point about warnings ahead of the needs of actual users. Yes, it is possible that some people would be hurt by adding a warning to 4.1.3. I believe the set of such people who exist in the real world is the empty set.

Ian

• References:
  • PATCH RFC: gcc 4.1 extern inline patch, take 2
    * From: Ian Lance Taylor
  • Re: PATCH RFC: gcc 4.1 extern inline patch, take 2
    * From: Jakub Jelinek
  • Re: PATCH RFC: gcc 4.1 extern inline patch, take 2
    * From: Ian Lance Taylor
  • Re: PATCH RFC: gcc 4.1 extern inline patch, take 2
    * From: Eric Botcazou