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-10423] Daily bump. Date: Fri, 16 Dec 2022 00:21:01 +0000 (GMT) [thread overview] Message-ID: <20221216002101.F0F89385841D@sourceware.org> (raw) https://gcc.gnu.org/g:dd83fe934958f2f229eb3a2107864232f00123c4 commit r11-10423-gdd83fe934958f2f229eb3a2107864232f00123c4 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Dec 16 00:20:21 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 11 +++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 7 +++++++ 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index cf1de8ba9be..6d38ed30fd4 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,14 @@ +2022-12-15 Sebastian Pop <spop@amazon.com> + + PR target/98776 + * config/aarch64/aarch64-protos.h (aarch64_output_patchable_area): + Declared. + * config/aarch64/aarch64.c (aarch64_print_patchable_function_entry): + Emit an UNSPECV_PATCHABLE_AREA pseudo instruction. + (aarch64_output_patchable_area): New. + * config/aarch64/aarch64.md (UNSPECV_PATCHABLE_AREA): New. + (patchable_area): Define. + 2022-12-12 Richard Biener <rguenther@suse.de> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 414c306c21c..0891de734e9 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221215 +20221216 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index b32d4b85576..d9a760fd254 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,10 @@ +2022-12-15 Sebastian Pop <spop@amazon.com> + + PR target/98776 + * gcc.target/aarch64/pr98776.c: New. + * gcc.target/aarch64/pr92424-2.c: Adjust pattern. + * gcc.target/aarch64/pr92424-3.c: Adjust pattern. + 2022-12-12 Richard Biener <rguenther@suse.de> Backported from master:
reply other threads:[~2022-12-16 0:21 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=20221216002101.F0F89385841D@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).