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. ed1a8d0621f5f5dee4d869393b9155f475d360f7 Date: Thu, 4 Mar 2021 20:52:02 +0000 (GMT) [thread overview] Message-ID: <20210304205202.DE87D385702E@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 ed1a8d0621f5f5dee4d869393b9155f475d360f7 (commit) from 80dc53f6b38d697b169fad9ce3b8787ce1c6768c (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 ed1a8d0621f5f5dee4d869393b9155f475d360f7 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 4 20:51:52 2021 +0000 Add <thread> to libstdc++ header dependency changes diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html index 83227c74..4d27c163 100644 --- a/htdocs/gcc-11/porting_to.html +++ b/htdocs/gcc-11/porting_to.html @@ -112,6 +112,9 @@ be included explicitly when compiled with GCC 11: (for <code>std::pair</code>, <code>std::tuple_size</code>, <code>std::index_sequence</code> etc.) </li> +<li> <code><thread></code> + (for members of namespace <code>std::this_thread</code>.) +</li> </ul> <h3 id="Old-iostream-Members">Old iostream Members</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/porting_to.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-03-04 20: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=20210304205202.DE87D385702E@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: 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).