public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/4258: gcc-2.95.2 produces wrong code Date: Fri, 07 Sep 2001 09:36:00 -0000 [thread overview] Message-ID: <20010907163600.15723.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/4258; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: rohloff@in.tum.de Cc: gcc-gnats@gcc.gnu.org Subject: Re: c/4258: gcc-2.95.2 produces wrong code Date: Fri, 7 Sep 2001 09:27:47 -0700 On Fri, Sep 07, 2001 at 03:42:53PM -0000, rohloff@in.tum.de wrote: > Compiling the attached code with -O2 produces a > binary which skips a loop iteration. I have compiled this code with -O1 and -O2 with "gcc-2.95.4 20010902 (Debian prerelease)" and get identical output. It seems, therefore, that the bug has been fixed in 2.95.3 or 2.95.4-to-be. I cannot be certain, however, because you do not say what the program should output. This is what I get: BFFFFA18 BFFFFA1C BFFFFA20 BFFFFA24 BFFFFA28 I don't know if that is correct or not. zw
next reply other threads:[~2001-09-07 9:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-07 9:36 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-01 20:16 rodrigc 2001-12-01 20:05 rodrigc 2001-09-10 9:26 Zack Weinberg 2001-09-07 8:46 rohloff
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=20010907163600.15723.qmail@sourceware.cygnus.com \ --to=zack@codesourcery.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: linkBe 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).