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: [patch] Backport fixes for PR54146 to GCC 4.7

From: Jakub Jelinek <jakub at redhat dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Steven Bosscher <stevenb dot gcc at gmail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Wed, 22 Aug 2012 15:44:54 +0200
Subject: Re: [patch] Backport fixes for PR54146 to GCC 4.7
References: <CABu31nN=CCkKES1_8p5ctkrmc4G_YNVDGtE4YZFzh7xBpOymcg@mail.gmail.com> <CAFiYyc2_2Ci=6NYGtuLHDhTEF18SJD4D9OHv09aMBSkPyH3nsg@mail.gmail.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Wed, Aug 22, 2012 at 03:41:08PM +0200, Richard Guenther wrote:
> On Wed, Aug 22, 2012 at 12:57 AM, Steven Bosscher <stevenb.gcc@gmail.com> wrote:
> > Hello,
> >
> > This patch back-ports most of the changes made to resolve the worst of
> > PR54146 on trunk to GCC 4.7. This PR is basically an accumulation of
> > various compiler speed and memory usage regressions, and all fixes are
> > almost trivial, so I think it's fair and safe to back-port these
> > changes.
> >
> > Bootstrapped&tested (gcc-4_7-branch, of course) on
> > x86_64-unknown-linux-gnu, and on powerpc64-unknown-linux-gnu. OK?
> 
> Ok with me, please give other RMs a chance to object.

To me the patch looks way too long, changing too many things, to be suitable
for the release branch.

	Jakub

Follow-Ups:
- Re: [patch] Backport fixes for PR54146 to GCC 4.7
  - From: Steven Bosscher

References:
- [patch] Backport fixes for PR54146 to GCC 4.7
  - From: Steven Bosscher
- Re: [patch] Backport fixes for PR54146 to GCC 4.7
  - From: Richard Guenther

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