public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 110c00930de9064671c58225c0dd381504949a43 Date: Thu, 2 Mar 2023 09:52:17 +0000 (GMT) [thread overview] Message-ID: <20230302095217.C17D63858CDB@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 110c00930de9064671c58225c0dd381504949a43 (commit) from 338214b83e6656087a661187cdbc58abb9d3fb30 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 110c00930de9064671c58225c0dd381504949a43 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Mar 2 10:52:04 2023 +0100 Document excess precision. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 811d9bdf..410594ae 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -236,6 +236,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 mainly affects + IA-32/x86-64 using x87 math and in some cases on Motorola 68000, + where <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 ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 15 +++++++++++++++ 1 file changed, 15 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-03-02 9:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230302095217.C17D63858CDB@sourceware.org \ --to=jakub@sourceware.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).