public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-1126] Daily bump. Date: Mon, 31 May 2021 00:17:03 +0000 (GMT) [thread overview] Message-ID: <20210531001704.CD7103857815@sourceware.org> (raw) https://gcc.gnu.org/g:e21e93407202e62a10c372595076c593c561bb11 commit r12-1126-ge21e93407202e62a10c372595076c593c561bb11 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon May 31 00:16:25 2021 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 4 ++++ libstdc++-v3/ChangeLog | 6 ++++++ 3 files changed, 11 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 30eeb7399e7..9bfad84bae8 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20210530 +20210531 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 2fc8b6f1b00..95857ccfa8c 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,7 @@ +2021-05-30 Gerald Pfeifer <gerald@pfeifer.com> + + * gfortran.texi (BOZ literal constants): Fix typo. + 2021-05-28 Tobias Burnus <tobias@codesourcery.com> * dump-parse-tree.c (show_iterator): New. diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 879b2ecea8c..e50aeb9217a 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2021-05-30 Gerald Pfeifer <gerald@pfeifer.com> + + * doc/xml/manual/abi.xml: Remove dead reference to "Intel + Compilers for Linux: Compatibility with GNU Compilers" article. + * doc/html/manual/abi.html: Regenerate. + 2021-05-26 François Dumont <fdumont@gcc.gnu.org> * include/debug/formatter.h
reply other threads:[~2021-05-31 0:17 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=20210531001704.CD7103857815@sourceware.org \ --to=gccadmin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).