public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Sven Verdoolaege <skimo@kotnet.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/7002: gcc -fPIC incorrect optimization on i586 Date: Sat, 05 Oct 2002 12:06:00 -0000 [thread overview] Message-ID: <20021005190601.26831.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/7002; it has been noted by GNATS. From: Sven Verdoolaege <skimo@kotnet.org> To: hubicka@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: optimization/7002: gcc -fPIC incorrect optimization on i586 Date: Sat, 5 Oct 2002 21:01:33 +0200 On Thu, Oct 03, 2002 at 05:29:47PM -0000, hubicka@gcc.gnu.org wrote: > Synopsis: gcc -fPIC incorrect optimization on i586 > > State-Changed-From-To: open->feedback > State-Changed-By: hubicka > State-Changed-When: Thu Oct 3 10:29:46 2002 > State-Changed-Why: > The code produced by 3.2 branch looks entirely different now and testcase is dificult to analyze. Is it still broken? > It's difficult to say. The particular snippet of code shown in the bug report seems to get compiled correctly, but something in the same file still gets compiled incorrectly with both -fPIC and -O2 and not with just -fPIC. I'll submit a new bug report when I figure out where the problem moved. skimo
next reply other threads:[~2002-10-05 19:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-05 12:06 Sven Verdoolaege [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-10 11:28 hubicka 2002-10-03 10:29 hubicka 2002-06-12 4:46 skimo
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=20021005190601.26831.qmail@sources.redhat.com \ --to=skimo@kotnet.org \ --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).