public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r9-10023] Daily bump. Date: Fri, 22 Apr 2022 00:20:33 +0000 (GMT) [thread overview] Message-ID: <20220422002033.5C8E23856DC3@sourceware.org> (raw) https://gcc.gnu.org/g:973a5c6e57339606653b84fdacb3edf1ec583a21 commit r9-10023-g973a5c6e57339606653b84fdacb3edf1ec583a21 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Apr 22 00:19:51 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 8 ++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index d4ff129236b..091485d1ee5 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220421 +20220422 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index cbcfa8126cb..d7ac606e099 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,11 @@ +2022-04-21 Fritz Reese <foreese@gcc.gnu.org> + + Backported from master: + 2022-04-21 Fritz Reese <foreese@gcc.gnu.org> + + PR fortran/105310 + * trans-expr.c (gfc_conv_union_initializer): Pass vec* by reference. + 2022-02-04 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 29535de3dd8..2d2c834c1f1 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-04-21 Fritz Reese <foreese@gcc.gnu.org> + + Backported from master: + 2022-04-21 Fritz Reese <foreese@gcc.gnu.org> + + PR fortran/105310 + * gfortran.dg/dec_union_12.f90: New test. + 2022-04-06 Alex Coplan <alex.coplan@arm.com> PR target/99977
reply other threads:[~2022-04-22 0:20 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=20220422002033.5C8E23856DC3@sourceware.org \ --to=gccadmin@gcc.gnu.org \ --cc=gcc-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).