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 tree-optimization/112711] [14 Regression] SRA seems to ignore writes when using __builtin_assume_aligned
Date: Sat, 25 Nov 2023 20:04:16 +0000 [thread overview]
Message-ID: <bug-112711-4-Kk2KZI03x5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112711-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-11-25
Target Milestone|--- |14.0
Summary|[14 Regression] possibly |[14 Regression] SRA seems
|wrong code in bswap32(int) |to ignore writes when using
|on llvm-16.0.6 test suite |__builtin_assume_aligned
Component|target |tree-optimization
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Keywords| |alias
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It has nothing to do with __builtin_bswap32 really but rather
__builtin_assume_aligned and the memcpy.
SRA does not detect:
_9 = __builtin_assume_aligned (&data, 1);
MEM <unsigned int> [(char * {ref-all})_9] = 3451308718;
_1 = data[0];
The store to _9 as touching data ...
next prev parent reply other threads:[~2023-11-25 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 19:44 [Bug middle-end/112711] New: [14 Regression] possibly wrong code in bswap32(int) on llvm-16.0.6 test suite slyfox at gcc dot gnu.org
2023-11-25 20:04 ` pinskia at gcc dot gnu.org [this message]
2023-11-25 20:05 ` [Bug tree-optimization/112711] [14 Regression] SRA seems to ignore writes when using __builtin_assume_aligned pinskia at gcc dot gnu.org
2023-11-25 20:35 ` slyfox at gcc dot gnu.org
2023-11-27 8:07 ` [Bug tree-optimization/112711] [14 Regression] SRA seems to ignore writes when using __builtin_assume_aligned since r14-5831-gaae723d360ca26 rguenth at gcc dot gnu.org
2023-11-27 8:16 ` jamborm at gcc dot gnu.org
2023-11-27 18:17 ` jamborm at gcc dot gnu.org
2023-11-29 15:25 ` cvs-commit at gcc dot gnu.org
2023-11-29 15:27 ` jamborm at gcc dot gnu.org
2023-11-29 16:03 ` slyfox 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-112711-4-Kk2KZI03x5@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: link
Be 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).