public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] gcc-13/changes.html: Document C++ -fexcess-precision=standard
Date: Fri, 10 Feb 2023 10:06:03 +0100 (CET)	[thread overview]
Message-ID: <541d2859-4029-3a21-e57e-10a401c5d226@pfeifer.com> (raw)
In-Reply-To: <Y+UdYvqGpAggRqVD@tucnak>

On Thu, 9 Feb 2023, Jakub Jelinek wrote:
> Martin Liska mentioned that porting_to.html doesn't mention
> the C++ excess precision changes.  Not really sure if porting_to
> should document those, but I think changes.html certainly should.

Do you think this is a widely spread issue for existing software? Did 
it materialize a couple of times building/testing Fedora with GCC 13 
snapshots (assuming you have done so as in the past)?

> Ok for wwwdocs?

Yes, thank you! Two minor suggestions/questions below:

> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> +      <code>-fexcess-precision=fast</code>.  The option affects mainly

Here I'd say "mainly affects".

> +      IA-32/x86-64 where when defaulting to x87 math and in some cases on
> +      Motorola 68000 <code>float</code> and <code>double</code> expressions
> +      are evaluated in <code>long double</code> precision and S/390, System z,
> +      IBM z Systems where <code>float</code> expressions are evaluated in
> +      <code>double</code> precision.

The "where when" part proved a bit tricky for my brain. :-) 

I think it is precise, but am wondering whether

  ...IA-32/x64 using x87 math and in some cases on Motorola 68000, where
  <code>float</code> and <code>double</code> expressions are evaluated...

might work? What do you think?

Gerald

  reply	other threads:[~2023-02-10  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 16:20 Jakub Jelinek
2023-02-10  9:06 ` Gerald Pfeifer [this message]
2023-03-02 10:32   ` [wwwdocs] gcc-13/porting_to.html: " Jakub Jelinek
2023-03-02 12:40     ` Martin Liška
2023-03-02 23:05     ` Gerald Pfeifer
2023-03-02 23:16       ` Jakub Jelinek
2023-03-09  7:09     ` Gerald Pfeifer
2023-03-09  8:05       ` Jakub Jelinek

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=541d2859-4029-3a21-e57e-10a401c5d226@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).