public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: eljay@adobe.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/2109: followup #2072 - -ffloat-store negates bug
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010226235415.28644.qmail@sourceware.cygnus.com> (raw)
>Number: 2109
>Category: optimization
>Synopsis: followup #2072 - -ffloat-store negates bug
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Mon Feb 26 15:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: John Love-Jensen
>Release: GCC 2.95.2
>Organization:
>Environment:
Solaris 2.6, 7, 8
>Description:
Interaction of optimizations produces broken code.
>How-To-Repeat:
>Fix:
Using -ffloat-store -fPIC -O3 will avoid the bug.
Good, now I won't need any more followups!
I'm contacting John West at Sun to inform him of these
findings. Keep the ball rolling.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 0:00 eljay [this message]
2001-11-17 22:37 rodrigc
2001-11-17 22:54 rodrigc
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=20010226235415.28644.qmail@sourceware.cygnus.com \
--to=eljay@adobe.com \
--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: link
Be 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).