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-11297] Daily bump. Date: Thu, 28 Mar 2024 00:19:02 +0000 (GMT) [thread overview] Message-ID: <20240328001902.B0B493858D20@sourceware.org> (raw) https://gcc.gnu.org/g:c7e5c857e67694b5826b6e9c0a067491166ba7a0 commit r11-11297-gc7e5c857e67694b5826b6e9c0a067491166ba7a0 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Thu Mar 28 00:18:40 2024 +0000 Daily bump. Diff: --- gcc/ChangeLog | 24 ++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 33 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 20daea0db36..c85fb61b681 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,27 @@ +2024-03-27 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2024-03-05 Richard Sandiford <richard.sandiford@arm.com> + + PR sanitizer/97696 + * asan.c (asan_expand_mark_ifn): Allow the length to be a poly_int. + +2024-03-27 Richard Sandiford <richard.sandiford@arm.com> + + * config/aarch64/arm_neon.h (vld1_s8_x4, vld1_s16_x4, vld1_s32_x4): + (vld1_u8_x4, vld1_u16_x4, vld1_u32_x4, vld1_f16_x4, vld1_f32_x4): + (vld1_p8_x4, vld1_p16_x4, vld1_s64_x4, vld1_u64_x4, vld1_p64_x4): + (vld1_f64_x4): Avoid using a union of a 256-bit structure and 512-bit + XImode integer. Instead use the same approach as the vld4 intrinsics. + (vst1_s8_x4, vst1_s16_x4, vst1_s32_x4, vst1_u8_x4, vst1_u16_x4): + (vst1_u32_x4, vst1_f16_x4, vst1_f32_x4, vst1_p8_x4, vst1_p16_x4): + (vst1_s64_x4, vst1_u64_x4, vst1_p64_x4, vst1_f64_x4, vld1_bf16_x4): + (vst1_bf16_x4): Likewise for stores. + (vst1q_s8_x4, vst1q_s16_x4, vst1q_s32_x4, vst1q_u8_x4, vst1q_u16_x4): + (vst1q_u32_x4, vst1q_f16_x4, vst1q_f32_x4, vst1q_p8_x4, vst1q_p16_x4): + (vst1q_s64_x4, vst1q_u64_x4, vst1q_p64_x4, vst1q_f64_x4) + (vst1q_bf16_x4): Rename val parameter to __val. + 2024-03-17 Iain Sandoe <iain@sandoe.co.uk> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 4597046e092..aab2708ffdd 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20240327 +20240328 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 47c160b25ee..dcbb6543849 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2024-03-27 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2024-03-05 Richard Sandiford <richard.sandiford@arm.com> + + PR sanitizer/97696 + * gcc.target/aarch64/sve/pr97696.c: New test. + 2024-03-20 Harald Anlauf <anlauf@gmx.de> Backported from master:
reply other threads:[~2024-03-28 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=20240328001902.B0B493858D20@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).