From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>, Qing Zhao <qing.zhao@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Should -ffp-contract=off the default on GCC?
Date: Tue, 21 Mar 2023 17:28:52 -0600 [thread overview]
Message-ID: <9a05445f-320d-08ca-7ca6-42c1ec44a1bf@gmail.com> (raw)
In-Reply-To: <ZBoBiPAhgLPkwNYd@tucnak>
On 3/21/23 13:12, Jakub Jelinek wrote:
> On Tue, Mar 21, 2023 at 07:01:36PM +0000, Qing Zhao via Gcc-patches wrote:
>> In addition to this, Standards have been changed from time to time.
>
> So, the user needs to know the standard they are compiling for.
>
> Anyway, talking again about contractions, it isn't anything new in the
> standard, C99 had those too.
And I think Qing is asking if adding a warning in the manual about how
fp contractions can cause unpredictability in FP results is appropriate
in the fp-contract section.
I think that would be a fine addition to the manual.
jeff
next prev parent reply other threads:[~2023-03-21 23:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 16:24 Qing Zhao
2023-03-16 16:31 ` Andrew Pinski
2023-03-16 16:38 ` Qing Zhao
2023-03-16 16:53 ` Jakub Jelinek
2023-03-16 18:40 ` Qing Zhao
2023-03-20 22:05 ` Qing Zhao
2023-03-20 22:25 ` Jakub Jelinek
2023-03-21 12:49 ` Qing Zhao
2023-03-21 15:01 ` Qing Zhao
2023-03-21 16:56 ` Paul Koning
2023-03-21 17:00 ` Qing Zhao
2023-03-21 17:59 ` Jeff Law
2023-03-21 18:03 ` Paul Koning
2023-03-21 18:55 ` Toon Moene
2023-03-21 18:12 ` Alexander Monakov
2023-03-21 18:18 ` Jeff Law
2023-03-22 10:13 ` Richard Biener
2023-03-22 12:26 ` Alexander Monakov
2023-03-22 13:57 ` Richard Biener
2023-03-22 15:52 ` Qing Zhao
2023-03-24 7:12 ` Fangrui Song
2023-03-24 19:42 ` Andrew Pinski
2023-03-31 16:31 ` Qing Zhao
2023-03-21 19:01 ` Qing Zhao
2023-03-21 19:12 ` Jakub Jelinek
2023-03-21 23:28 ` Jeff Law [this message]
2023-03-21 23:31 ` Jakub Jelinek
2023-03-21 19:51 ` Jeff Law
2023-03-21 21:08 ` Qing Zhao
2023-03-22 12:33 ` Alexander Monakov
2023-03-22 14:33 ` Qing Zhao
2023-03-27 9:03 Zeson
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=9a05445f-320d-08ca-7ca6-42c1ec44a1bf@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=qing.zhao@oracle.com \
/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).