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-9420] Daily bump. Date: Tue, 28 Dec 2021 00:18:51 +0000 (GMT) [thread overview] Message-ID: <20211228001851.15E3C3858C39@sourceware.org> (raw) https://gcc.gnu.org/g:3b2b18144c7225384f4c623d78a11497e989a807 commit r11-9420-g3b2b18144c7225384f4c623d78a11497e989a807 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Tue Dec 28 00:18:15 2021 +0000 Daily bump. Diff: --- gcc/ChangeLog | 10 ++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 28 ++++++++++++++++++++++++++++ gcc/testsuite/ChangeLog | 25 +++++++++++++++++++++++++ 4 files changed, 64 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 3ea3bb2cb1a..ffcc827a5ec 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,13 @@ +2021-12-27 John David Anglin <danglin@gcc.gnu.org> + + * config/pa/pa-protos.h: Delete + pa_maybe_emit_compare_and_swap_exchange_loop() declaration. + * config/pa/pa.c (pa_expand_compare_and_swap_loop): Delete. + (pa_maybe_emit_compare_and_swap_exchange_loop): Delete. + * config/pa/pa.md (atomic_storeq): Use __sync_lock_test_and_set + instead of pa_maybe_emit_compare_and_swap_exchange_loop. + (atomic_storehi, atomic_storesi, atomic_storedi): Likewise. + 2021-12-16 Martin Sebor <msebor@redhat.com> PR middle-end/101751 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 1092928a364..0802d0e2c51 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20211227 +20211228 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 4365d315946..fc20bf1baa4 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,31 @@ +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-12-22 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103776 + * match.c (match_case_selector): Reject expressions in CASE + selector which are not scalar. + +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-12-22 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103778 + * check.c (is_c_interoperable): A BOZ literal constant is not + interoperable. + +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-11-18 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/101329 + * check.c (is_c_interoperable): Reject NULL() as it is not + interoperable. + 2021-12-19 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 80130a4560a..33487e8a597 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,28 @@ +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-12-22 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103776 + * gfortran.dg/select_10.f90: New test. + +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-12-22 Harald Anlauf <anlauf@gmx.de> + + PR fortran/103778 + * gfortran.dg/illegal_boz_arg_3.f90: New test. + +2021-12-27 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2021-11-18 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/101329 + * gfortran.dg/pr101329.f90: New test. + 2021-12-19 Harald Anlauf <anlauf@gmx.de> Backported from master:
reply other threads:[~2021-12-28 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=20211228001851.15E3C3858C39@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).