From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: joel@rtems.org, newlib@sourceware.org
Subject: Re: incorrectly rounded square root
Date: Thu, 03 Jun 2021 12:21:46 +0200 [thread overview]
Message-ID: <mwk0nbqmdh.fsf@tomate.loria.fr> (raw)
In-Reply-To: <CAOox84uTnypYU68Ffgq+XMdRDA01t053vCWZhY-ozEBR9e01ow@mail.gmail.com> (message from Jeff Johnston on Wed, 2 Jun 2021 23:01:53 -0400)
Hi Jeff,
I've investigated and found (partially) the cause of the problem. When I
compile my program, gcc uses the system fenv.h, which contains FE_TONEAREST=0,
FE_DOWNWARD=0x400, FE_UPWARD=0x800, and FE_TOWARDZERO=0xc00 in
/usr/include/bits/fenv.h.
However, the values in x86_64/newlib/targ-include/sys/fenv.h are different:
FE_TONEAREST=0, FE_DOWNWARD=1, FE_UPWARD=2, FE_TOWARDZERO=3. Thus the test
at the beginning of fesetround in newlib/libm/machine/x86_64/fenv.c fails
except for round=FE_TONEAREST:
/* Will succeed for any valid value of the input parameter. */
if (round < FE_TONEAREST || round > FE_TOWARDZERO)
return EINVAL;
enter fesetround, round=0 use_sse=1
enter fesetround, round=3072 use_sse=1
enter fesetround, round=2048 use_sse=1
enter fesetround, round=1024 use_sse=1
This explains why the other modes are not set.
A first question is why Newlib and the system libm (here glibc) use different
constants for the rounding modes.
Now if I compile with -I/tmp/x86_64/include (where the Newlib fenv.h is
installed) I get:
enter fesetround, round=0 use_sse=1
enter fesetround, round=3 use_sse=1
enter fesetround, round=2 use_sse=1
enter fesetround, round=1 use_sse=1
but I still do get the same results whatever the rounding mode!
If I look at the cw and mxcsr registers like in Newlib fenv.c, I get with glibc
(after the fesetround call):
fegetround: 0
cw=895 mxcsr=8064
RNDN: 0x1.ff83fp+63
fegetround: 3072
cw=3967 mxcsr=32672
RNDZ: 0x1.ff83eep+63
fegetround: 2048
cw=2943 mxcsr=24480
RNDU: 0x1.ff83fp+63
fegetround: 1024
cw=1919 mxcsr=16288
RNDD: 0x1.ff83eep+63
and with Newlib:
fegetround: 0
cw=895 mxcsr=8064
RNDN: 0x1.ff83fp+63
fegetround: 3
cw=3967 mxcsr=32640
RNDZ: 0x1.ff83fp+63
fegetround: 2
cw=2943 mxcsr=24448
RNDU: 0x1.ff83fp+63
fegetround: 1
cw=1919 mxcsr=16256
RNDD: 0x1.ff83fp+63
The cw values do match but not the mxcsr values.
Best regards,
Paul
> Something weird is going on. I condensed the newlib code into the
> following files and when I compile and run the test,
> it works as expected:
>
> gcc -std=c99 -g3 -O0 test_sqrt.c fesetround.c ef_sqrt.c
> [jjohnstn@localhost shared_x86]$ ./a.out
> RNDN: 0x1.ff83fp+63
> RNDZ: 0x1.ff83eep+63
> RNDU: 0x1.ff83fp+63
> RNDD: 0x1.ff83eep+63
>
> Can you verify that you are calling the fesetround in fenv.c and what
> configuration call did you use for building newlib?
next prev parent reply other threads:[~2021-06-03 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:08 Paul Zimmermann
2021-05-31 20:52 ` Jeff Johnston
2021-06-01 7:11 ` Paul Zimmermann
2021-06-01 16:28 ` Jeff Johnston
2021-06-02 7:51 ` Paul Zimmermann
2021-06-02 13:07 ` Joel Sherrill
2021-06-02 18:43 ` Jeff Johnston
2021-06-02 19:07 ` Marco Atzeri
2021-06-02 19:12 ` Joel Sherrill
2021-06-03 3:01 ` Jeff Johnston
2021-06-03 10:21 ` Paul Zimmermann [this message]
2021-06-03 15:50 ` Jeff Johnston
2021-06-04 7:14 ` Paul Zimmermann
2021-06-04 18:44 ` Jeff Johnston
2021-06-04 18:59 ` Joel Sherrill
2021-06-05 13:25 ` Brian Inglis
2021-06-07 9:51 ` Paul Zimmermann
2021-06-12 22:31 ` Maciej W. Rozycki
2021-06-03 11:25 ` Paul Zimmermann
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=mwk0nbqmdh.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=jjohnstn@redhat.com \
--cc=joel@rtems.org \
--cc=newlib@sourceware.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).