public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103100] [11/12 Regression] unaligned access generated with memset or {} and -O2 -mstrict-align Date: Fri, 05 Nov 2021 13:26:46 +0000 [thread overview] Message-ID: <bug-103100-4-QEKM4FMfUk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103100-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103100 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Mine. This should fix it (untested): diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c index 699c105a42a..5d0872be4ef 100644 --- a/gcc/config/aarch64/aarch64.c +++ b/gcc/config/aarch64/aarch64.c @@ -23584,7 +23584,9 @@ aarch64_expand_setmem (rtx *operands) over writing. */ opt_scalar_int_mode mode_iter; FOR_EACH_MODE_IN_CLASS (mode_iter, MODE_INT) - if (GET_MODE_BITSIZE (mode_iter.require ()) <= MIN (n, copy_limit)) + if (GET_MODE_BITSIZE (mode_iter.require ()) <= MIN (n, copy_limit) + && (!STRICT_ALIGNMENT + || MEM_ALIGN (dst) >= GET_MODE_ALIGNMENT (mode_iter.require ()))) cur_mode = mode_iter.require (); gcc_assert (cur_mode != BLKmode);
next prev parent reply other threads:[~2021-11-05 13:26 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-05 12:52 [Bug target/103100] New: unaligned access generated when zero-initializing large locals with SIMD-instructions " felix at breitweiser dot de 2021-11-05 12:58 ` [Bug target/103100] " pinskia at gcc dot gnu.org 2021-11-05 13:17 ` pinskia at gcc dot gnu.org 2021-11-05 13:21 ` [Bug target/103100] [11/12 Regression] unaligned access generated with memset or {} " pinskia at gcc dot gnu.org 2021-11-05 13:26 ` pinskia at gcc dot gnu.org [this message] 2021-11-05 13:27 ` pinskia at gcc dot gnu.org 2021-11-05 13:35 ` rguenth at gcc dot gnu.org 2021-11-05 13:38 ` pinskia at gcc dot gnu.org 2021-11-06 5:26 ` pinskia at gcc dot gnu.org 2021-11-18 8:50 ` pinskia at gcc dot gnu.org 2021-11-19 1:55 ` pinskia at gcc dot gnu.org 2022-01-26 2:30 ` pinskia at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-06-09 10:28 ` [Bug target/103100] [11/12/13 " pinskia at gcc dot gnu.org 2023-01-19 13:28 ` rguenth at gcc dot gnu.org 2023-01-20 13:59 ` rearnsha at gcc dot gnu.org 2023-01-23 7:29 ` felix at breitweiser dot de 2023-01-23 7:37 ` sam at gentoo dot org 2023-01-31 17:49 ` pinskia at gcc dot gnu.org 2023-01-31 17:51 ` pinskia at gcc dot gnu.org 2023-01-31 18:24 ` rearnsha at gcc dot gnu.org 2023-02-10 3:54 ` pinskia at gcc dot gnu.org 2023-03-24 12:09 ` pinskia at gcc dot gnu.org 2023-04-05 19:25 ` pinskia at gcc dot gnu.org 2023-05-29 10:06 ` [Bug target/103100] [11/12/13/14 " jakub at gcc dot gnu.org 2023-09-20 13:53 ` wilco at gcc dot gnu.org 2023-11-30 13:49 ` cvs-commit at gcc dot gnu.org
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=bug-103100-4-QEKM4FMfUk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).