linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David <dllorens@lsi.uji.es>, linux-kernel@vger.kernel.org
Subject: Re: Posible bug in gcc
Date: Mon, 26 Feb 2001 12:33:09 -0500	[thread overview]
Message-ID: <20010226123309.A16592@devserv.devel.redhat.com> (raw)
In-Reply-To: <3A9A8489.224CF54C@inf.uji.es> <E14XRFC-0001ay-00@the-village.bc.nu>
In-Reply-To: <E14XRFC-0001ay-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 26, 2001 at 05:15:28PM +0000

On Mon, Feb 26, 2001 at 05:15:28PM +0000, Alan Cox wrote:
> > I think I heve found a bug in gcc. I have tried both egcs 1.1.2 (gcc
> > 2.91.66) and gcc 2.95.2 versions.
> > 
> > I am attaching you a simplified test program ('bug.c', a really simple
> > program).
> 
> Well gcc-bugs would be the better place to send it but this is a known problem
> fixed in CVS gcc 2.95.3, CVS gcc 3.0 branch and gcc 2.96 (unofficial, Red Hat)

I'm not sure if it is known, at least not known to me, but definitely not
fixed in any of gcc 2.95.2, CVS gcc 3.0 branch, CVS gcc 3.1 head, gcc 2.96-RH.

	Jakub

  reply	other threads:[~2001-02-26 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 16:30 Posible bug in gcc David
2001-02-26 17:15 ` Alan Cox
2001-02-26 17:33   ` Jakub Jelinek [this message]
2001-02-26 18:02     ` Alan Cox
2001-02-26 18:02       ` Richard B. Johnson
2001-02-27 19:50         ` Ville Herva
2001-02-26 21:03       ` J . A . Magallon
2001-02-26 20:53     ` David Relson
2001-02-26 22:30 ` J . A . Magallon
2001-02-27 10:56   ` Erik Mouw

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=20010226123309.A16592@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dllorens@lsi.uji.es \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).