public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46080] [4.4/4.5/4.6 Regression] incorrect precision of sqrtf builtin for x87 arithmetic (-mfpmath=387)
Date: Wed, 20 Oct 2010 08:29:00 -0000	[thread overview]
Message-ID: <20101020082900.G4_xsNGc5zWJ-_OdAdD55xvz0XYbrW70Ak6KdtGjHbs@z> (raw)
In-Reply-To: <bug-46080-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46080

--- Comment #3 from Uros Bizjak <ubizjak at gmail dot com> 2010-10-20 08:28:57 UTC ---
(In reply to comment #2)
> Created attachment 22089 [details]
> sh script to test sqrtf
> 
> Similar problems can also be found with:
> 
>   printf ("%.60f\n%.60f\n%.60f\n", sqrtf(x), sqrtf(x), sqrtf(x));
> 
> I've found that every GCC version I could test was showing some incorrect
> behavior (but GCC 4.2.4 was the most consistent one). With the attached script,
> I get:
> 
>            -DSEP  -O0   -O1   -O2
> GCC 3.4.6   SSS   SSS   SDD   SDD
> GCC 4.1.3   SSS   SSS   DSS   DDS
> GCC 4.2.4   SSS   SSS   DDD   DDD   (x86)
> GCC 4.3.5   SSS   SSS   DSS   DDD   (ditto with GCC 4.3.2 on x86)
> GCC 4.4.5   DSS   SSD   DSS   DDD
> 
> where S means that one gets the result in single precision (as expected) and D
> means that one gets the result in double precision.

You should use -ffloat-store to remove excess precision.


  parent reply	other threads:[~2010-10-20  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19  8:55 [Bug target/46080] New: " vincent at vinc17 dot org
2010-10-19 10:49 ` [Bug target/46080] [4.4/4.5/4.6 Regression] " rguenth at gcc dot gnu.org
2010-10-20  1:52 ` vincent at vinc17 dot org
2010-10-20  8:29 ` ubizjak at gmail dot com [this message]
2010-10-20  9:39 ` jakub at gcc dot gnu.org
2010-10-20  9:54 ` zimmerma+gcc at loria dot fr
2010-10-20 10:46 ` jakub at gcc dot gnu.org
2010-10-20 23:43 ` vincent at vinc17 dot org
2010-10-20 23:49 ` pinskia at gcc dot gnu.org
2010-10-21 19:26 ` zimmerma+gcc at loria dot fr
2010-10-21 20:56 ` jakub at gcc dot gnu.org
2010-10-22  6:56 ` zimmerma+gcc at loria dot fr
2010-10-26 13:41 ` jakub at gcc dot gnu.org
2010-11-12 14:35 ` rguenth at gcc dot gnu.org
2010-11-16 10:56 ` jakub at gcc dot gnu.org

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=20101020082900.G4_xsNGc5zWJ-_OdAdD55xvz0XYbrW70Ak6KdtGjHbs@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).