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 19:58:59 -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>

Mark Mitchell wrote:

No, I don't think we know.  There's speculation in the PR trail, but
that's it.  I'd appreciate it if you were able to investigate further,
but I think I'd best just accept that this will not be fixed for 4.2.0.

Or revert the patch that revealed the bug, or apply Richard Guenther's other patch to work around it?

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

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