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: GCC 4.2.0 Status Report (2007-05-11)

From: Jason Merrill <jason at redhat dot com>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: Daniel Berlin <dberlin at dberlin dot org>, GCC <gcc at gcc dot gnu dot org>
Date: Sun, 13 May 2007 20:36:06 -0400
Subject: Re: GCC 4.2.0 Status Report (2007-05-11)
References: <4644E80E.1030905@codesourcery.com> <46463FE8.2000400@redhat.com> <46474F54.8060702@codesourcery.com> <4647A643.5070204@redhat.com> <4647A9D2.4020707@codesourcery.com>

Mark Mitchell wrote:

I'm concerned about either of the other approaches, in that we don't
fully understand why they work, so we can't really be confident we're
not just pushing the bug around.

Yes. But I would assert that pushing the bug back to where it was in previous releases is better because it's not a regression.

Jason

Follow-Ups:
- Re: GCC 4.2.0 Status Report (2007-05-11)
  - From: Mark Mitchell

References:
- GCC 4.2.0 Status Report (2007-05-11)
  - From: Mark Mitchell
- Re: GCC 4.2.0 Status Report (2007-05-11)
  - From: Jason Merrill
- Re: GCC 4.2.0 Status Report (2007-05-11)
  - From: Mark Mitchell
- Re: GCC 4.2.0 Status Report (2007-05-11)
  - From: Jason Merrill
- Re: GCC 4.2.0 Status Report (2007-05-11)
  - From: Mark Mitchell

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