Joe Buck <[EMAIL PROTECTED]> writes:
| On Fri, Jan 05, 2007 at 03:02:00PM -0500, Andrew Pinski wrote:
| > >
| > > [ omitting gcc-patches ]
| > >
| > > On Fri, 5 Jan 2007, Joe Buck wrote:
| > > > I'd like to see it closed. We have some bugs that are only open
| > > > because they are targeted fo
On Fri, Jan 05, 2007 at 03:02:00PM -0500, Andrew Pinski wrote:
> >
> > [ omitting gcc-patches ]
> >
> > On Fri, 5 Jan 2007, Joe Buck wrote:
> > > I'd like to see it closed. We have some bugs that are only open
> > > because they are targeted for 4.0.4 (fixed on all branches but 4_0).
> >
> > If
>
> [ omitting gcc-patches ]
>
> On Fri, 5 Jan 2007, Joe Buck wrote:
> > I'd like to see it closed. We have some bugs that are only open
> > because they are targeted for 4.0.4 (fixed on all branches but 4_0).
>
> If there is consensus, I'll be happy to take the appropriate steps,
> which inclu
[ omitting gcc-patches ]
On Fri, 5 Jan 2007, Joe Buck wrote:
> I'd like to see it closed. We have some bugs that are only open
> because they are targeted for 4.0.4 (fixed on all branches but 4_0).
If there is consensus, I'll be happy to take the appropriate steps,
which include:
1. Updating o
The GCC 4.0 branch is now open, under the usual release-branch rules.
However, I do not plan to make any further releases from the 4.0
branch.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
Bobby McNulty wrote:
> Since this is just staying on the cutting edge of programming, I am only
> going to use release cygwin1.dll.
> Waiting for cygwin 1.5.19
FYI, http://cygwin.com/ml/cygwin-cvs/2005-q4/msg00072.html
Brian Dessent wrote:
Brian Dessent wrote:
/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/ -isystem
/usr/local/i686-pc-cygwin/i
nclude -isystem /usr/local/i686-pc-cygwin/sys-include -DHAVE_CONFIG_H
-I. -I../.
./../../g
Brian Dessent wrote:
> > /home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
> > -B/usr/local/i686-pc-c
> > ygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/ -isystem
> > /usr/local/i686-pc-cygwin/i
> > nclude -isystem /usr/local/i686-pc-cygwin/sys-include -DHAVE_CONFIG_H
> > -I. -I../.
> > ./../.
Brian Dessent wrote:
Bobby McNulty wrote:
I have been noticing the following error in trunk and in branch.
I get no such error when compiling the trunk.
/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/ -
Bobby McNulty wrote:
> I have been noticing the following error in trunk and in branch.
I get no such error when compiling the trunk.
> /home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
> -B/usr/local/i686-pc-c
> ygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/ -isystem
> /usr/local/i686-pc-c
I have been noticing the following error in trunk and in branch.
It looks look in libstdc++-v3 signbit,
Has it been reported yet?
/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -B/usr/local/i686-pc-cygwin/lib/ -isystem
/usr/local/i686-pc-cygwin/i
nc
GCC 4.0.2 has been released; the GCC 4.0 branch is open under the normal
branch rules: fixes for regressions only.
Here are the wwwdocs patches I checked in when creating the new release.
Although I still consider the 4.0 branch open, I am not going to focus
on creating a 4.0.3 release until the
I am now going to start spinning 4.0.2 RC1.
(I was planning to do that last weekend, but it didn't happen.)
Therefore, as of now, the GCC 4.0 branch is frozen. If you've had a
patch approved for 4.0.2 that's not yet been checked in, and you want to
check it in, please send m
On Fri, 22 Apr 2005, Mark Mitchell wrote:
> The GCC 4.0 branch is now open for regression fixes only, under the usual
> release branch rules.
Documented thusly.
Gerald
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/
Mark Mitchell wrote:
The GCC 4.0 branch is now open for regression fixes only, under the
usual release branch rules.
I presume this means that we (The Fortran Illuminati) can fix any bug in
the gfortran frontend, as we don't have any regressions yet (at least
not against gfortran itself -
Toon Moene wrote:
Mark Mitchell wrote:
The GCC 4.0 branch is now open for regression fixes only, under the
usual release branch rules.
I presume this means that we (The Fortran Illuminati) can fix any bug in
the gfortran frontend, as we don't have any regressions yet (at least
not ag
The GCC 4.0 branch is now open for regression fixes only, under the
usual release branch rules.
--
Mark Mitchell
CodeSourcery, LLC
[EMAIL PROTECTED]
(916) 791-8304
"cvs rtag" has been running for an hour, and I need to go to sleep. The
load average on the gcc.gnu.org is about 20, and I guess my CVS process
isn't making much process. So, the 4.0 branch may not actually be
created until some time from now. I've got a job running overnight to
do the appro
18 matches
Mail list logo
