From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: [wwwdocs] gcc-13/changes.html: Document C++ -fexcess-precision=standard
Date: Thu, 9 Feb 2023 17:20:50 +0100 [thread overview]
Message-ID: <Y+UdYvqGpAggRqVD@tucnak> (raw)
Hi!
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.
And perhaps porting_to could have some examples and link to this
spot in changes.
Ok for wwwdocs?
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -230,6 +230,21 @@ a work-in-progress.</p>
<h3 id="cxx">C++</h3>
<ul>
+ <li>Excess precision support (which has been available in C since GCC 4.5)
+ has been implemented for C++ as well. It is enabled by default
+ in strict standard modes like <code>-std=c++17</code>, where it
+ defaults to <code>-fexcess-precision=standard</code>, while in GNU
+ standard modes like <code>-std=gnu++20</code> it defaults to
+ <code>-fexcess-precision=fast</code>. The option affects mainly
+ 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. Also, on several architectures where
+ <code>std::float16_t</code> or <code>std::bfloat16_t</code> types
+ are supported those are evaluated in <code>float</code> precision.
+ <code>-fexcess-precision=fast</code> restores previous behavior.
+ </li>
<li>Several C++23 features have been implemented:
<ul>
<li><a href="https://wg21.link/p2324">P2324R1</a>, Labels at the end of
Jakub
next reply other threads:[~2023-02-09 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 16:20 Jakub Jelinek [this message]
2023-02-10 9:06 ` Gerald Pfeifer
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=Y+UdYvqGpAggRqVD@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).