public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, lloyd@acm.jhu.edu, nobody@gcc.gnu.org Subject: Re: optimization/10877: [3.3/3.4 regression] miscompilation with -O3 -fPIC on x86 Date: Tue, 20 May 2003 01:16:00 -0000 [thread overview] Message-ID: <20030520011638.25212.qmail@sources.redhat.com> (raw) Old Synopsis: GCC 3.3 miscompiles code with -O3 -fPIC on x86 New Synopsis: [3.3/3.4 regression] miscompilation with -O3 -fPIC on x86 State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue May 20 01:16:37 2003 State-Changed-Why: Confirmed. This is a smaller snippet (it has nothing to do with namespaces): ---------------------------- int* i; int& get_x() { return *i; } int main() { int j; i = &j; get_x(); } -------------------------- It crashed in get_x: g/x> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -O3 -fPIC x.cc g/x> ./a.out Segmentation fault Note that we really need both -fPIC and -O3. This crashes with both 3.3 and present mainline. It doesn't with 2.95 and 3.2.3, so it's definitely a regression worth fixing! W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10877
next reply other threads:[~2003-05-20 1:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-20 1:16 bangerth [this message] 2003-05-20 2:06 Andrew Pinski 2003-05-20 13:56 Wolfgang Bangerth 2003-05-20 16:16 Wolfgang Bangerth 2003-05-20 17:06 Wolfgang Bangerth 2003-05-20 17:06 Christian Ehrhardt 2003-05-20 17:16 Andrew Pinski 2003-05-20 19:16 Wolfgang Bangerth 2003-05-20 19:27 Andrew Pinski 2003-05-20 19:36 Andrew Pinski 2003-05-20 22:46 Janis Johnson 2003-05-21 8:46 Christian Ehrhardt 2003-05-21 11:28 Christian Ehrhardt 2003-05-21 12:46 Christian Ehrhardt
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=20030520011638.25212.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=lloyd@acm.jhu.edu \ --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).