Joseph S. Myers wrote:
> On Tue, 30 Jan 2007, Mark Mitchell wrote:
>
>>>PR target/30370 (powerpc-unknown-eabispe can't build libgcc2) is a
>>> regression from 4.1.1. A patch was posted earlier this month at
>>> http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00600.html>. I have
>>> regrettably fo
On Tue, 30 Jan 2007, Mark Mitchell wrote:
> >PR target/30370 (powerpc-unknown-eabispe can't build libgcc2) is a
> > regression from 4.1.1. A patch was posted earlier this month at
> > http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00600.html>. I have
> > regrettably forgotten to ping this patch
Rask Ingemann Lambertsen wrote:
> On Sun, Jan 28, 2007 at 11:53:41AM -0800, Mark Mitchell wrote:
>> I plan to create GCC 4.1.2 RC1 sometime this afternoon, US/Pacific time.
>>
>> Therefore, please do not make any checkins to the 4.1 branch after 2PM
>> PST. Once RC1 is uploaded, the branch will be
On Sun, Jan 28, 2007 at 11:53:41AM -0800, Mark Mitchell wrote:
> I plan to create GCC 4.1.2 RC1 sometime this afternoon, US/Pacific time.
>
> Therefore, please do not make any checkins to the 4.1 branch after 2PM
> PST. Once RC1 is uploaded, the branch will be open only for changes
> which have m
I plan to create GCC 4.1.2 RC1 sometime this afternoon, US/Pacific time.
Therefore, please do not make any checkins to the 4.1 branch after 2PM
PST. Once RC1 is uploaded, the branch will be open only for changes
which have my explicit approval, until the release.
Remember that the primary criter
I am (finally...) starting the 4.1.1 RC1 build.
Please do not check in any changes on the 4.1 branch, even if previous
approved.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
As previously, announced the GCC 4.1 branch is now frozen. All
non-documentation changes now require my explicit approval.
I had hoped to generate a release candidate last night, but (a) there
are a couple of new PRs I need to review, and (b) I'm onsite with a
customer, and didn't hvae as much ti
