public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tprince@computer.org
To: gcc-gnats@gcc.gnu.org
Subject: middle-end/6205: -O -fpmath=sse breaks visibility of register accumulated sum
Date: Sat, 06 Apr 2002 07:16:00 -0000	[thread overview]
Message-ID: <20020406151057.3286.qmail@sources.redhat.com> (raw)


>Number:         6205
>Category:       middle-end
>Synopsis:       -O -fpmath=sse breaks visibility of register accumulated sum
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 07:16:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tim Prince
>Release:        3.1
>Organization:
>Environment:
linux-SuSE 7.3 or cygwin/2K
>Description:
result of a float sum in SSE register is seen as NaN in certain contexts, when built with -O -mfpmath=sse

Problem originally seen in larger examples in g77; case available on request.

>How-To-Repeat:
gcc -O -march=pentium3 -mfpmath=sse badsum.c
./a.out

result seen as nan in printf(), but is OK if -O or -mfpmath options are removed
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="badsum.c"; name="badsum.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="badsum.c"

I2luY2x1ZGUgPHN0ZGxpYi5oPgojaW5jbHVkZSA8c3RkaW8uaD4KaW50IG1haW4oKXsKaW50IGks
bj03OwkvL2Nob29zZSBhbnkgbiA8IHNxcnQoMS9GTFRfRVBTSUxPTikKICAgIGZsb2F0IGNvbXAs
c3VtPTA7CiAgICBmb3IoaT0xO2k8PW47KytpKQoJc3VtICs9IGk7CiAgICBwcmludGYoInN1bSBv
ZiAlZCBpbnRzOiAlZ1xuIixuLHN1bSk7CiAgICBjb21wID0gbioobiouNWYrLjVmKTsKICAgIGlm
KHN1bSAhPSBjb21wKXsKCXByaW50ZigiQmFkIHN1bSAoc2VlbiB3aXRoIGdjYyAtTyAtbWFyY2g9
cGVudGl1bXBybyAtbXNzZSlcbiIpOwoJYWJvcnQ7Cgl9CiAgICByZXR1cm4gMDsKfQo=


             reply	other threads:[~2002-04-06 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06  7:16 tprince [this message]
2002-05-28  5:51 hubicka

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=20020406151057.3286.qmail@sources.redhat.com \
    --to=tprince@computer.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: 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).