public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Lukas Geyer <lukas@debian.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/10194: [3.2 regression] [arm] gcc optimization error with -O2, affecting bison
Date: Wed, 30 Apr 2003 21:06:00 -0000	[thread overview]
Message-ID: <20030430210600.24096.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/10194; it has been noted by GNATS.

From: Lukas Geyer <lukas@debian.org>
To: ehrhardt@mathematik.uni-ulm.de, 185903@bugs.debian.org,
	 gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	 nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/10194: [3.2 regression] [arm] gcc optimization error with -O2, affecting bison
Date: 30 Apr 2003 16:57:23 -0400

 ehrhardt@mathematik.uni-ulm.de writes:
 
 > Synopsis: [3.2 regression] [arm] gcc optimization error with -O2, affecting bison
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: cae
 > State-Changed-When: Mon Apr 28 11:24:14 2003
 > State-Changed-Why:
 >     According to the Bug-Database, this report is most likely 3.2-only.
 >     As the 3.2-branch is closed, i.e. there will be no further release
 >     after 3.2.3 we should probably close this report. Could you possibly
 >     verify that this is indeed fixed in 3.3 (as stated in the report) and 3.4?
 
 I re-checked with gcc-3.3, more precisely
 
 gcc-3.3 (GCC) 3.3 20030415 (Debian prerelease)
 
 (output of --version) and it compiles correctly. However, there seems
 to be no Debian package of 3.4 installed on the machines I use for
 testing. So I cannot test with gcc 3.4, as I do not have any ARM
 machines myself.
 
 Best regards,
 Lukas


             reply	other threads:[~2003-04-30 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 21:06 Lukas Geyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-03 13:12 ehrhardt
2003-04-28 11:24 ehrhardt
2003-03-23 20:26 Matthias Klose

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=20030430210600.24096.qmail@sources.redhat.com \
    --to=lukas@debian.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).