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 r11-10459] Daily bump. Date: Mon, 9 Jan 2023 00:21:04 +0000 (GMT) [thread overview] Message-ID: <20230109002105.58ADF3858D35@sourceware.org> (raw) https://gcc.gnu.org/g:7b126dd558e2437d1bda5b731c19a8b26388326b commit r11-10459-g7b126dd558e2437d1bda5b731c19a8b26388326b Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Jan 9 00:20:24 2023 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 9 +++++++++ 3 files changed, 20 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index bcc46c04f3c..6a739acb152 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230108 +20230109 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 4edfc801749..a8cabf47e21 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,13 @@ +2023-01-08 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-12-23 Harald Anlauf <anlauf@gmx.de> + + PR fortran/108131 + * array.c (match_array_element_spec): Avoid too early simplification + of matched array element specs that can lead to a misinterpretation + when used as array bounds in array declarations. + 2022-12-18 Paul Thomas <pault@gcc.gnu.org> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 214eeac29c1..af82f76f39f 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,12 @@ +2023-01-08 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-12-23 Harald Anlauf <anlauf@gmx.de> + + PR fortran/108131 + * gfortran.dg/pr103505.f90: Adjust expected patterns. + * gfortran.dg/pr108131.f90: New test. + 2023-01-06 Francois-Xavier Coudert <fxcoudert@gcc.gnu.org> Backported from master:
reply other threads:[~2023-01-09 0:21 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=20230109002105.58ADF3858D35@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).