From: Jakub Jelinek <jakub@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jwright@penguincomputing.com, redhat-devel-list@redhat.com,
linux-kernel@vger.kernel.org, Jeremy Hogan <jhogan@redhat.com>,
Mike Vaillancourt <mikev@redhat.com>,
Philip Pokorny <ppokorny@penguincomputing.com>
Subject: Re: bug in redhat gcc 2.96
Date: Wed, 9 May 2001 05:14:19 -0400 [thread overview]
Message-ID: <20010509051418.C9725@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105081927320.1798-100000@foo.penguincomputing.com> <E14xPli-0001qP-00@the-village.bc.nu>
In-Reply-To: <E14xPli-0001qP-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, May 09, 2001 at 09:56:24AM +0100
On Wed, May 09, 2001 at 09:56:24AM +0100, Alan Cox wrote:
> > As this is with Red Hat's version of gcc, I'm not sending
> > this to the gcc folks. RPMs of gcc with this problem
>
> (If you have the time check 3.0 CVS doesnt show the same problem, the RH tree
> diverges from it so may well be unique in having the bug but many bugs are
> shared)
The bug was present in 3.0 and 3.1 as well, but has been fixed the day it
was reported. Use gcc-2.96-82 or above, or gcc-3_0-branch newer than 2001-04-25
(or CVS head newer than that).
Jakub
next prev parent reply other threads:[~2001-05-09 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 3:05 bug in redhat gcc 2.96 Jim Wright
2001-05-09 3:24 ` Matt Wilson
2001-05-09 8:56 ` Alan Cox
2001-05-09 9:09 ` Tobias Ringstrom
2001-05-09 10:31 ` Stefan Hoffmeister
2001-05-09 15:09 ` Dan Kegel
2001-05-09 15:09 ` Bernhard Rosenkraenzer
2001-05-09 9:14 ` Jakub Jelinek [this message]
2001-05-09 16:42 ` Matt Wilson
2001-05-09 10:27 ` David Woodhouse
2001-05-09 15:01 ` Jeremy Hogan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010509051418.C9725@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jhogan@redhat.com \
--cc=jwright@penguincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikev@redhat.com \
--cc=ppokorny@penguincomputing.com \
--cc=redhat-devel-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.