public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "newbie-02 at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/113455] ROUNDING: IEEE Standard: Missing decimal rounding mode 'nearest, ties away from zero' for decimalxxx datatypes.
Date: Wed, 17 Jan 2024 23:29:22 +0000 [thread overview]
Message-ID: <bug-113455-4-r4Uzu9Glgm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113455-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113455
--- Comment #2 from newbie-02 <newbie-02 at gmx dot de> ---
(In reply to Joseph S. Myers from comment #1)
hello and thank you very much!!,
> The decimal rounding mode is set with fe_dec_setround.
found in my directories that I already had experimented with that,
a distinct include of libdfp/dfp/fenv.h made progress,
but also with `fe_dec_setround(FE_DEC_TONEARESTFROMZERO)`,
successful as `if ((r = fe_dec_getround()) == -1)` produces '4',
the implicit rounding for the addition stays with 'to even'.
:-( will continue research tomorrow.
the strategic discussion is above my experience, from POV
wanting an alternative for people fed up with bin-FP imprecision
it would be:
- good if it works,
- is easy to find,
- wouldn't require much 'info gathering' and configuration effort,
next prev parent reply other threads:[~2024-01-17 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 17:41 [Bug c/113455] New: " newbie-02 at gmx dot de
2024-01-17 17:51 ` [Bug c/113455] " jsm28 at gcc dot gnu.org
2024-01-17 23:29 ` newbie-02 at gmx dot de [this message]
2024-01-18 0:20 ` jsm28 at gcc dot gnu.org
2024-01-18 6:41 ` newbie-02 at gmx dot de
2024-02-06 0:48 ` newbie-02 at gmx dot de
2024-02-07 20:28 ` jsm28 at gcc dot gnu.org
2024-02-10 13:43 ` newbie-02 at gmx dot de
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=bug-113455-4-r4Uzu9Glgm@http.gcc.gnu.org/bugzilla/ \
--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).