public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10877: [3.3/3.4 regression] miscompilation with -O3 -fPIC on x86 Date: Tue, 20 May 2003 17:06:00 -0000 [thread overview] Message-ID: <20030520170600.29597.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10877; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: Wolfgang Bangerth <bangerth@ices.utexas.edu> Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-bugs@gcc.gnu.org, lloyd@acm.jhu.edu, gcc-gnats@gcc.gnu.org Subject: Re: optimization/10877: [3.3/3.4 regression] miscompilation with -O3 -fPIC on x86 Date: Tue, 20 May 2003 19:00:33 +0200 On Tue, May 20, 2003 at 10:26:37AM -0500, Wolfgang Bangerth wrote: > OK, I made the experiment -- and my small snippet still segfaults with > both 3.3 and 3.4 checked out an hour or so ago. This is the assembler > output I get on my system with present 3.4. I think I'm at a loss for > further explanations, but feel free to ask me if you think you have a > theory... Feeding this assembler file into gcc 3.2 on an Intel box works for me and the program doesn't crash! This might mean that we have an assembler/binutils problem here. Gruesse Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-05-20 17:06 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-20 17:06 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 12:46 Christian Ehrhardt 2003-05-21 11:28 Christian Ehrhardt 2003-05-21 8:46 Christian Ehrhardt 2003-05-20 22:46 Janis Johnson 2003-05-20 19:36 Andrew Pinski 2003-05-20 19:27 Andrew Pinski 2003-05-20 19:16 Wolfgang Bangerth 2003-05-20 17:16 Andrew Pinski 2003-05-20 17:06 Wolfgang Bangerth 2003-05-20 16:16 Wolfgang Bangerth 2003-05-20 13:56 Wolfgang Bangerth 2003-05-20 2:06 Andrew Pinski 2003-05-20 1:16 bangerth
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=20030520170600.29597.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --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).