public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkorb@pacbell.net To: gcc-gnats@gcc.gnu.org Subject: c/8083: GCC 3.2 Optimization bug Date: Sat, 28 Sep 2002 14:56:00 -0000 [thread overview] Message-ID: <200209282200.g8SM0WBu020621@bach.korb> (raw) >Number: 8083 >Category: c >Synopsis: GCC 3.2 Optimization bug >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sat Sep 28 14:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Bruce Korb >Release: 3.2 2002-07-26 (prerelease) >Organization: GNU >Environment: System: Linux bach 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown Architecture: i686 Stock SuSE 8.0 + cvs gcc-3_1-branch, configured as below. host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../configure --enable-language=c --prefix=/home/gcc >Description: When compiled with -O2, autogen produces invalid results. When compiled without a -O, the results are correct. Therefore, the program behavior is different. I do not believe I am using improperly aliased pointers. >How-To-Repeat: Download autogen-5.4.3, fix some #define redefinition issues that were not bugs before gcc3.x and do a "make distcheck". (CVS version has this fixed.) I will add to this as I narrow the issue. >Fix: None known, other than eliminating optimization. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-09-28 21:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-28 14:56 bkorb [this message] 2002-09-28 15:06 Bruce Korb 2002-09-28 15:56 Bruce Korb 2002-09-28 16:56 Bruce Korb 2002-09-29 11:19 nathan 2002-10-01 12:22 nathan
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=200209282200.g8SM0WBu020621@bach.korb \ --to=bkorb@pacbell.net \ --cc=bkorb@gnu.org \ --cc=gcc-gnats@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).