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-10344] Daily bump. Date: Sat, 29 Oct 2022 00:20:52 +0000 (GMT) [thread overview] Message-ID: <20221029002052.7D4623858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:dd27a84503b724b5a0b4d2bf53f5bb79219e774d commit r11-10344-gdd27a84503b724b5a0b4d2bf53f5bb79219e774d Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sat Oct 29 00:20:13 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 9 +++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 7109ae30352..06511cc68c5 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221028 +20221029 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index b0000a0dc47..9be2fb499ce 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,12 @@ +2022-10-28 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-10-26 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103413 + * symbol.c (gfc_type_compatible): A boz-literal-constant has no type + and thus is not considered compatible to any type. + 2022-10-23 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 9fc0742da9e..44f00568a0d 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-10-28 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-10-26 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103413 + * gfortran.dg/illegal_boz_arg_4.f90: New test. + 2022-10-26 Philipp Tomsich <philipp.tomsich@vrull.eu> Backported from master:
reply other threads:[~2022-10-29 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=20221029002052.7D4623858C2C@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).