public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: 166255@bugs.debian.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kalmquist1@hotmail.com, kenner@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: ada/8606: GNAT floating point optimization bug Date: Tue, 13 May 2003 06:10:00 -0000 [thread overview] Message-ID: <20030513061007.12063.qmail@sources.redhat.com> (raw) Synopsis: GNAT floating point optimization bug Responsible-Changed-From-To: unassigned->kenner Responsible-Changed-By: ebotcazou Responsible-Changed-When: Tue May 13 06:10:07 2003 Responsible-Changed-Why: Ada specialist. Richard, this bug is related to the very classical problem of the extra-precision of the x86 FPU. The "fix" for other languages is to pass "-ffloat-store" to the compiler. Is it valid for GNAT too? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8606
next reply other threads:[~2003-05-13 6:10 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-13 6:10 ebotcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-13 17:56 Geert Bosch 2002-11-22 8:19 Matthias Klose
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=20030513061007.12063.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=166255@bugs.debian.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=kalmquist1@hotmail.com \ --cc=kenner@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).