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-10254] Daily bump. Date: Wed, 14 Sep 2022 00:22:14 +0000 (GMT) [thread overview] Message-ID: <20220914002214.196973858407@sourceware.org> (raw) https://gcc.gnu.org/g:7f1021b5a1bbcfff3606b86d0e0e6bb6e827a62b commit r11-10254-g7f1021b5a1bbcfff3606b86d0e0e6bb6e827a62b Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Sep 14 00:21:39 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 3ab9ae22f92..21befd25789 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220913 +20220914 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index af65189d7b5..961a2246213 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,22 @@ +2022-09-13 Kewen Lin <linkw@linux.ibm.com> + + Backported from master: + 2022-09-07 Kewen Lin <linkw@linux.ibm.com> + + PR testsuite/106345 + * lib/target-supports.exp (check_effective_target_powerpc_sqrt): Add + a function definition to avoid pedwarn about empty translation unit. + (check_effective_target_has_arch_pwr5): Likewise. + (check_effective_target_has_arch_pwr6): Likewise. + (check_effective_target_has_arch_pwr7): Likewise. + (check_effective_target_has_arch_pwr8): Likewise. + (check_effective_target_has_arch_pwr9): Likewise. + (check_effective_target_has_arch_pwr10): Likewise. + (check_effective_target_has_arch_ppc64): Likewise. + (check_effective_target_ppc_float128): Likewise. + (check_effective_target_ppc_float128_insns): Likewise. + (check_effective_target_powerpc_vsx): Likewise. + 2022-09-12 Peter Bergner <bergner@linux.ibm.com> Backported from master:
reply other threads:[~2022-09-14 0:22 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=20220914002214.196973858407@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).