public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 768ecbe7af00a219cfdff9fba96874a0fe9c94bb
Date: Thu, 14 Jan 2021 10:42:14 +0000 (GMT)	[thread overview]
Message-ID: <20210114104214.D1726385480D@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  768ecbe7af00a219cfdff9fba96874a0fe9c94bb (commit)
       via  b1448ab2ec847fd9a8283881f620d3ace0aea8ed (commit)
      from  6be6626d59e1c492d5e05606e5a6902feb9e5bac (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 768ecbe7af00a219cfdff9fba96874a0fe9c94bb
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 14 10:41:43 2021 +0000

    Document addition of <barrier> C++ header in C++11

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index e044d710..3527428f 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -307,7 +307,8 @@ a work-in-progress.</p>
       <li><code>std::bit_cast</code></li>
       <li><code>std::source_location</code></li>
       <li>Atomic wait and notify operations.</li>
-      <li><code>&lt;latch&gt;</code> and <code>&lt;semaphore&gt;</code></li>
+      <li><code>&lt;barrier&gt;</code>, <code>&lt;latch&gt;</code>,
+        and <code>&lt;semaphore&gt;</code></li>
       <li><code>&lt;syncstream&gt;</code></li>
       <li>Efficient access to <code>basic_stringbuf</code>'s buffer.</li>
     </ul>

commit b1448ab2ec847fd9a8283881f620d3ace0aea8ed
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jan 14 10:40:47 2021 +0000

    Add "porting to" notes for libstdc++ in GCC 11

diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html
index 4187dd8e..83227c74 100644
--- a/htdocs/gcc-11/porting_to.html
+++ b/htdocs/gcc-11/porting_to.html
@@ -141,6 +141,35 @@ change the code to not include the <code>&lt;tr1/functional&gt;</code> header,
 so that only <code>std::bind</code> is declared.
 </p>
 
+<h3 id="enable-threads">Enable multithreading to use std::thread</h3>
+<p>
+Programs must be linked to libpthread in order for <code>std::thread</code>
+to create new threads of execution.
+It is not sufficient to use <code>dlopen</code> to dynamically load
+<code>libpthread.so</code> at run-time.
+</p>
+
+<h3 id="strict-ansi">Do not undefine <code>__STRICT_ANSI__</code></h3>
+<p>
+The <code>__STRICT_ANSI__</code> macro is defined by the compiler to
+inform the C and C++ standard library headers when a strict language dialect
+is being used, e.g. <code>-std=c++17</code> or <code>-std=c11</code> rather
+than <code>-std=gnu++17</code> or <code>-std=gnu11</code>.
+</p>
+<p>
+If you undefine the <code>__STRICT_ANSI__</code> macro then you create an
+inconsistent state where the compiler is using a strict dialect but the
+standard library headers think that GNU extensions are enabled.
+The libstdc++ headers in GCC 11 cannot be used in this state and are likely
+to produce compilation errors.
+</p>
+<p>
+If you don't want the macro to be defined, don't use a <code>-std</code>
+option that causes it to be defined.
+Simply use a <code>-std=gnu++<em>NN</em></code> option instead of
+<code>-std=c++<em>NN</em></code>.
+</p>
+
 <!--
 <h2 id="fortran">Fortran language issues</h2>
 -->

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

Summary of changes:
 htdocs/gcc-11/changes.html    |  3 ++-
 htdocs/gcc-11/porting_to.html | 29 +++++++++++++++++++++++++++++
 2 files changed, 31 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-01-14 10:42 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=20210114104214.D1726385480D@sourceware.org \
    --to=redi@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).