public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/102930] equal values appear to be different due to missing correct rounding in libc
Date: Mon, 25 Oct 2021 13:57:01 +0000	[thread overview]
Message-ID: <bug-102930-4-arp210IRrq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102930-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102930

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think there is nothing that can be done about this, and something like this
has been there since forever.  While perhaps some double routines in glibc used
to be at some point correctly roundded, many others (e.g. float or long double)
never were, there is always a chance you get different results from compile
time folding vs. runtime evaluation.

  parent reply	other threads:[~2021-10-25 13:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 13:43 [Bug middle-end/102930] New: " vincent-gcc at vinc17 dot net
2021-10-25 13:51 ` [Bug middle-end/102930] " vincent-gcc at vinc17 dot net
2021-10-25 13:57 ` jakub at gcc dot gnu.org [this message]
2021-10-25 14:01 ` vincent-gcc at vinc17 dot net
2021-10-26  0:59 ` joseph at codesourcery dot com
2021-10-26  7:06 ` rguenth 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=bug-102930-4-arp210IRrq@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).