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. 20a280fdead95b9a6e9071a6d167dac76cba616a
Date: Thu,  2 Mar 2023 14:23:35 +0000 (GMT)	[thread overview]
Message-ID: <20230302142335.571333858C83@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4790 bytes --]

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  20a280fdead95b9a6e9071a6d167dac76cba616a (commit)
       via  5b1016426388b6cbe02a9a5251ea56a4c57eb35b (commit)
      from  110c00930de9064671c58225c0dd381504949a43 (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 20a280fdead95b9a6e9071a6d167dac76cba616a
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Mar 2 15:23:15 2023 +0100

    Mention C++ excess precision in GCC 13 porting_to.

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 9a9a3147..5cbeefb6 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -120,5 +120,29 @@ the operand as an lvalue.<br>
    }
 </code></pre>
 
+<h3 id="excess-precision">Excess precision changes</h3>
+<p>GCC 13 implements in C++ <a href="changes.html#cxx">excess precision support</a>
+which has been before implemented just in the C front-end.  The new behavior is
+enabled by default in <code>-std=c++</code><em>NN</em> modes and e.g. when
+<code>FLT_EVAL_METHOD</code> is 1 or 2 affects behavior of floating point
+constants and expressions.  E.g. for <code>FLT_EVAL_METHOD</code> equal
+to 2 on ia32:
+
+<pre><code>
+#include <stdlib.h>
+void foo (void) { if (1.1f + 3.3f != 1.1L + 3.3L) abort (); }
+void bar (void) { double d = 4.2; if (d == 4.2) abort (); }
+</code></pre>
+
+will not abort with standard excess precision, because constants and expressions
+in <code>float</code> or <code>double</code> are evaluated in precision of
+<code>long double</code> and demoted only on casts or assignments, but will
+abort with fast excess precision, where whether something is evaluated in
+precision of <code>long double</code> or not depends on what evaluations are
+done in the i387 floating point stack or are spilled from it.
+
+The <code>-fexcess-precision=fast</code> option can be used to request the
+previous behavior.
+
 </body>
 </html>

commit 5b1016426388b6cbe02a9a5251ea56a4c57eb35b
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Mar 2 15:22:41 2023 +0100

    Mention some further finished C++23 papers in GCC13 and the assume attribute.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 410594ae..839b73d0 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -182,6 +182,10 @@ a work-in-progress.</p>
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html"><code>-fanalyzer</code></a>
     to detect misuses of file descriptors.
   </li>
+  <li>A new statement attribute for C++23 <a href="https://wg21.link/p1774r8">P1774R8</a> Portable
+      assumptions support also in C or older C++:
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#index-assume-statement-attribute"><code>__attribute__((assume(EXPR)));</code>
+  </li>
 </ul>
 
 <h3 id="c">C</h3>
@@ -290,6 +294,29 @@ a work-in-progress.</p>
 	Operator You Are Looking For
 	(<a href="https://gcc.gnu.org/PR106644">PR106644</a>)
       </li>
+      <li> <a href="https://wg21.link/p2362r3">P2362R3</a>, Remove non-encodable
+          wide character literals and multicharacter wide character literals
+	(<a href="https://gcc.gnu.org/PR106647">PR106647</a>)
+      </li>
+      <li> <a href="https://wg21.link/p2448r2">P2448R2</a>, Relaxing some
+          constexpr restrictions
+	(<a href="https://gcc.gnu.org/PR106649">PR106649</a>)
+      </li>
+      <li> <a href="https://wg21.link/p1467r9">P1467R9</a>, Extended
+          floating-point types and standard names
+	(<a href="https://gcc.gnu.org/PR106652">PR106652</a>)
+      </li>
+      <li> <a href="https://wg21.link/p1774r8">P1774R8</a>, Portable
+          assumptions
+	(<a href="https://gcc.gnu.org/PR106654">PR106654</a>)
+      </li>
+      <li> <a href="https://wg21.link/p2295r6">P2295R6</a>, Support for
+          UTF-8 as a portable source file encoding
+	(<a href="https://gcc.gnu.org/PR106655">PR106655</a>)
+      </li>
+      <li> <a href="https://wg21.link/p2589r1">P2589R1</a>, static operator[]
+	(<a href="https://gcc.gnu.org/PR107684">PR107684</a>)
+      </li>
     </ul>
   </li>
   <li>New warnings:

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html    | 27 +++++++++++++++++++++++++++
 htdocs/gcc-13/porting_to.html | 24 ++++++++++++++++++++++++
 2 files changed, 51 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-03-02 14:23 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=20230302142335.571333858C83@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: 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).