public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107389] Always propagate __builtin_assume_aligned
Date: Tue, 08 Nov 2022 15:39:56 +0000 [thread overview]
Message-ID: <bug-107389-4-taE8020s98@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107389-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107389
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:7899582a059a9d8c25bfff305cd236d219dc4f20
commit r13-3810-g7899582a059a9d8c25bfff305cd236d219dc4f20
Author: Richard Biener <rguenther@suse.de>
Date: Tue Nov 8 13:49:16 2022 +0100
tree-optimization/107389 - honor __builtin_assume_alignment at -O0
The following makes sure to set alignment information on the LHS
of __builtin_assume_alignment calls even when not optimizing so
uses as arguments to builtin functions like memcpy or __atomic_load_n
can be reflected at RTL expansion time.
PR tree-optimization/107389
* gimple-low.cc (lower_builtin_assume_aligned): New.
(lower_stmt): Call it.
* gcc.dg/pr107389.c: New testcase.
next prev parent reply other threads:[~2022-11-08 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:57 [Bug c/107389] New: Alignment not inferred from type at -O0 rth at gcc dot gnu.org
2022-10-25 12:46 ` [Bug c/107389] " rguenth at gcc dot gnu.org
2022-10-25 12:52 ` rguenth at gcc dot gnu.org
2022-10-25 15:12 ` rth at gcc dot gnu.org
2022-10-26 8:15 ` [Bug middle-end/107389] Always propagate __builtin_assume_aligned rth at gcc dot gnu.org
2022-10-28 9:19 ` rguenth at gcc dot gnu.org
2022-10-28 9:30 ` rguenth at gcc dot gnu.org
2022-11-08 15:39 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-08 15:40 ` rguenth at gcc dot gnu.org
2022-11-28 22:15 ` pinskia 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-107389-4-taE8020s98@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).