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-9488] Daily bump. Date: Mon, 24 Jan 2022 00:18:43 +0000 (GMT) [thread overview] Message-ID: <20220124001843.A036E3858C3A@sourceware.org> (raw) https://gcc.gnu.org/g:11581a272eb9be86e6f47c09cbe9a8f1a211864a commit r11-9488-g11581a272eb9be86e6f47c09cbe9a8f1a211864a Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Jan 24 00:18:05 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 12 ++++++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 1c9ace69750..da164bfdd32 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220123 +20220124 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 21a5bf22655..9ab4b3e44b7 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,15 @@ +2022-01-23 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-01-15 Harald Anlauf <anlauf@gmx.de> + + PR fortran/83079 + * target-memory.c (gfc_interpret_character): Result length is + in bytes and thus depends on the character kind. + * trans-intrinsic.c (gfc_conv_intrinsic_transfer): Compute correct + string length for the result of the TRANSFER intrinsic and for + temporaries for the different character kinds. + 2022-01-20 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index f06e6a14044..a0dc0222ce3 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-01-23 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-01-15 Harald Anlauf <anlauf@gmx.de> + + PR fortran/83079 + * gfortran.dg/transfer_char_kind4.f90: New test. + 2022-01-20 Harald Anlauf <anlauf@gmx.de> Backported from master:
reply other threads:[~2022-01-24 0:18 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=20220124001843.A036E3858C3A@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).