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 r12-8502] Daily bump. Date: Wed, 22 Jun 2022 00:19:45 +0000 (GMT) [thread overview] Message-ID: <20220622001945.7710B383DB94@sourceware.org> (raw) https://gcc.gnu.org/g:1ad2ee21827faafa4cade25cbfabb05ab55573ee commit r12-8502-g1ad2ee21827faafa4cade25cbfabb05ab55573ee Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Jun 22 00:19:10 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 451298a70cf..71f9e429988 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2022-06-21 H.J. Lu <hjl.tools@gmail.com> + + Backported from master: + 2022-06-20 H.J. Lu <hjl.tools@gmail.com> + + PR target/105960 + * config/i386/i386.cc (ix86_function_ok_for_sibcall): Return + false if PIC register is used when calling ifunc functions. + 2022-06-20 Uros Bizjak <ubizjak@gmail.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 774b03215ac..effad93f720 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220621 +20220622 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 80b75968ec2..caab75f2c84 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-06-21 H.J. Lu <hjl.tools@gmail.com> + + Backported from master: + 2022-06-20 H.J. Lu <hjl.tools@gmail.com> + + PR target/105960 + * gcc.target/i386/pr105960.c: New test. + 2022-06-20 Uros Bizjak <ubizjak@gmail.com> Backported from master:
reply other threads:[~2022-06-22 0:19 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=20220622001945.7710B383DB94@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).