public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Guillermo Ballester Valor <gbv@oxixares.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5926: gcc 3.0.3 generates incorrect code with -O3 option
Date: Mon, 18 Mar 2002 22:26:00 -0000	[thread overview]
Message-ID: <20020319062602.18883.qmail@sources.redhat.com> (raw)

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

From: Guillermo Ballester Valor <gbv@oxixares.com>
To: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/5926: gcc 3.0.3 generates incorrect code with -O3 option
Date: Tue, 19 Mar 2002 07:16:27 +0100

 Hi, 
 
 I've just now repeated the test again with my i586, compiled with 'gcc -O3 
 testbug.c -o testbug' , gcc 3.0.3 and the result is:
 
 Results of no bugy routine 1780
 Results of bugy routine 238611074
 
 
 And I remember to have the same problems since gcc 3.0. On a pentium III the 
 problems are the same.
 
 Guillermo.
 
 On Tue 19 Mar 2002 00:47, jakub@gcc.gnu.org wrote:
 > Synopsis: gcc 3.0.3 generates incorrect code with -O3 option
 >
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: jakub
 > State-Changed-When: Mon Mar 18 15:47:21 2002
 > State-Changed-Why:
 >     Cannot reproduce this with any of
 >     gcc 3.0.4, gcc 3.1 20020314 and gcc 3.0.2 20011002,
 >     with -O3 for -march=i386, -march=i586 nor -march=i386 -mcpu=i586.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&
 >pr=5926
 
 -- 
 Guillermo Ballester Valor
 gbv@oxixares.com
 Granada (Spain)
 


             reply	other threads:[~2002-03-19  6:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 22:26 Guillermo Ballester Valor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-01 19:08 neroden
2002-04-29  0:26 gbv
2002-03-18 15:47 jakub
2002-03-12 12:06 gbv

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=20020319062602.18883.qmail@sources.redhat.com \
    --to=gbv@oxixares.com \
    --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).