public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Jeff Law <law@redhat.com>,
	gcc-patches@gcc.gnu.org, joseph@codesourcery.com,
	richard.guenther@gmail.com
Subject: Re: [PATCH v2] Fix -ffast-math flags handling inconsistencies
Date: Tue, 24 Nov 2020 17:23:17 -0600	[thread overview]
Message-ID: <20201124232317.GZ2672@gate.crashing.org> (raw)
In-Reply-To: <20201124184247.GA3173@oc3748833570.ibm.com>

Hi Ulrich,

On Tue, Nov 24, 2020 at 07:42:47PM +0100, Ulrich Weigand wrote:
> This did handle flag_excess_precision incorrectly, causing in particular
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97970
> 
> I've reverted for now and will post a modified patch later.
> Sorry for the breakage!
> 
> At a first glance, it appears the problem is that -fexcess-precision=fast
> is already the default, so it does not make sense for -fno-fast-math to
> "reset" this back to default.  Probably the best is for fast-math to
> simply not touch excess precision at all:
> - if it is set explicitly on the command line, fast-math should not
>   affect it in any case;
> - if it is not set explicitly on the command line, the default either
>   with fast-math or no-fast-math is excess-precision=fast, so again
>   it should not be touched.
> 
> I'll still need to look into the language-specific handling of the
> excess precision setting to make sure this works for all languages.

At least C uses "standard" (instead of "fast") for the strict ISO C
dialects.


Segher

  reply	other threads:[~2020-11-24 23:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 18:43 Ulrich Weigand
2020-02-11 23:56 ` Segher Boessenkool
2020-11-21  4:33 ` Jeff Law
2020-11-21 19:57   ` Segher Boessenkool
2020-11-24 10:55     ` [wwwdocs] " Ulrich Weigand
2020-11-24 17:19       ` Segher Boessenkool
2020-11-24 18:42   ` Ulrich Weigand
2020-11-24 23:23     ` Segher Boessenkool [this message]
2020-11-25 13:12     ` Christophe Lyon

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=20201124232317.GZ2672@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=law@redhat.com \
    --cc=richard.guenther@gmail.com \
    --cc=uweigand@de.ibm.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).