public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114995] C++23 Assume keyword not being used for vectorization Date: Wed, 08 May 2024 21:52:06 +0000 [thread overview] Message-ID: <bug-114995-4-DbEdIRJwkX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114995-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114995 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aldyh at gcc dot gnu.org, | |amacleod at redhat dot com, | |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The above examples just show misunderstanding what __builtin_assume_aligned is and what it is not. You need to use the result of the built-in function in the accesses to be able to use the alignment information, if you just try to compare __builtin_assume_aligned (x, 32) == x, it will just fold as always true. The design of the builtin is to attach the alignment information to the result of the builtin function only. CCing Aldy/Andrew for whether prange can or could be taught to handle the assume cases with uintptr_t and bitwise and + comparison.
next prev parent reply other threads:[~2024-05-08 21:52 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-08 20:14 [Bug tree-optimization/114995] New: " pratikc at live dot co.uk 2024-05-08 20:18 ` [Bug tree-optimization/114995] " pinskia at gcc dot gnu.org 2024-05-08 20:20 ` pinskia at gcc dot gnu.org 2024-05-08 20:26 ` pratikc at live dot co.uk 2024-05-08 20:29 ` pinskia at gcc dot gnu.org 2024-05-08 20:33 ` pinskia at gcc dot gnu.org 2024-05-08 20:53 ` pratikc at live dot co.uk 2024-05-08 21:52 ` jakub at gcc dot gnu.org [this message] 2024-05-09 19:59 ` pratikc at live dot co.uk 2024-05-14 9:00 ` aldyh at gcc dot gnu.org 2024-05-14 9:04 ` aldyh at gcc dot gnu.org 2024-05-14 9:15 ` aldyh at gcc dot gnu.org 2024-05-15 10:33 ` cvs-commit at gcc dot gnu.org 2024-05-15 10:34 ` aldyh 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-114995-4-DbEdIRJwkX@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).