This is the mail archive of the gcc@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] Fix PR29519 Bad code on MIPS with -fnon-call-exceptions

From: Richard Sandiford <richard at codesourcery dot com>
To: Eric Botcazou <ebotcazou at libertysurf dot fr>
Cc: gcc at gcc dot gnu dot org, Roger Sayle <roger at eyesopen dot com>, Andrew Haley <aph at redhat dot com>, David Daney <ddaney at avtrex dot com>
Date: Wed, 25 Oct 2006 19:55:10 +0100
Subject: Re: [PATCH] Fix PR29519 Bad code on MIPS with -fnon-call-exceptions
References: <Pine.LNX.4.44.0610250925260.11491-100000@www.eyesopen.com> <87iri8uw4s.fsf@talisman.home> <200610252051.17997.ebotcazou@libertysurf.fr>

Eric Botcazou <ebotcazou@libertysurf.fr> writes:
>> Also, having patches on mainline and not a release branch can cause
>> quite a bit of confusion.  Witness what happend with PR 28243, where I
>> fixed something on mainline, but it was not directly approved for a
>> release branch.  Then Eric B. worked around the same problem on the
>> release branch and forward-ported the work-around to mainline, where
>> it wasn't really needed.
>
> I'd have said: "fixed a subcase" but the picture is globally correct.

Yes, I chose my words very badly there, sorry.  I wasn't trying to
belittle your fix.

Richard

References:
- Re: [PATCH] Fix PR29519 Bad code on MIPS with -fnon-call-exceptions
  - From: Roger Sayle
- Re: [PATCH] Fix PR29519 Bad code on MIPS with -fnon-call-exceptions
  - From: Richard Sandiford
- Re: [PATCH] Fix PR29519 Bad code on MIPS with -fnon-call-exceptions
  - From: Eric Botcazou

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