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.6.1 Release Candidate available from gcc.gnu.org

From: Eric Botcazou <ebotcazou at adacore dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 21 Jun 2011 11:18:25 +0200
Subject: Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
References: <20110620130147.GD11563@sunsite.ms.mff.cuni.cz> <201106211047.54269.ebotcazou@adacore.com> <20110621085950.GI16443@tyan-ft48-01.lab.bos.redhat.com>

> I guess it depends on how risky the patch is, while reorg.c affects only a
> few targets, they still include some primary targets.  If it is not a
> regression from 4.6.0 and the fix isn't very obviously safe, it would
> probably be better to postpone it for 4.6.2 (though, I think CPU cycles
> wouldn't be wasted by preparing a fix for 4.6.2).

I think it is as obviously safe as a reorg.c patch can be so I'm going to test 
it (on the branch) and post it afterward, but it will be your call of course.

-- 
Eric Botcazou

References:
- GCC 4.6.1 Release Candidate available from gcc.gnu.org
  - From: Jakub Jelinek
- Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  - From: Eric Botcazou
- Re: GCC 4.6.1 Release Candidate available from gcc.gnu.org
  - From: Jakub Jelinek

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