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: Sat, 10 Feb 2024 13:43:45 +0000 [thread overview]
Message-ID: <bug-113455-4-dxbQnxLu3t@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 #7 from newbie-02 <newbie-02 at gmx dot de> ---
> (and GCC doesn't implement the FENV_DEC_ROUND pragma to set a constant rounding mode in a particular scope)
here we are leaving my level of knowledge about internals.
Let me formulate from a user / programmers perspective:
Wanted is 'decimal compatible math'. Which is to some degree
announced and partly fulfilled with _Decimalxxx datatypes.
Shortcomings are:
- requires libdfp ( hard to find and tricky to use ), or
other library.
- even with that there are situations where the rounding
mode isn't respected,
thus no system of reliable human compatible math.
Could and should - IMHO - be improved by implementing
something in gcc which accounts users wish 'ties away'
in all situations. Can't say if that is a 'pragma' or
what else.
The essential point is to offer a well-rounded system /
environment that relieves programmers and users from
being constantly surprised by deviations. And thus set's
them free from always and anytime having to check for it.
Too big a wish?
( code - compiler - libraries - math shouldn't play
Larry Laffer )
prev parent reply other threads:[~2024-02-10 13:43 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
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 [this message]
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-dxbQnxLu3t@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).