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: [3.3/3.4/head] fix 14535


Michael Matz <matz@suse.de> writes:

| Hi,

I agree a coordination is desirable, but:

| > I don't think so.  The fix (which is a regression fix) is not going to
| > be present in 3.3.3 since it is already out.  It is going to be 3.3.4
| > which will go out long after 3.4.0 is released.  And since it will be
| > included in 3.4.1 or 3.4.0,
| 
| This is exactly what Gerald is talking about.  It's not yet approved for
| 3.4 branch only for 3.3 (and it's in mainline, so will be in 3.5), so we
| can't be sure about this.  The _current_ state is that 3.3.4 and 3.5 have 
| it fixed, but 3.4.0 doesn't.

The bug being fixed is already a regression.  So the question is only
how far or close you move the regression point.  I don't think
applying the patch itself introduces a regression. 
We ought to be careful not about use of "regression".

-- Gaby


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