public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106892] [11/12/13 Regression] Wrong code at -O3 on x86_64-linux-gnu since r11-963-g80d6f89e78fc3b77
Date: Fri, 09 Sep 2022 12:43:48 +0000 [thread overview]
Message-ID: <bug-106892-4-fCzGo2DgUz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106892-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106892
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:a8b0b13da7379feb31950a9d2ad74b98a29c547f
commit r13-2560-ga8b0b13da7379feb31950a9d2ad74b98a29c547f
Author: Richard Biener <rguenther@suse.de>
Date: Fri Sep 9 12:06:38 2022 +0200
tree-optimization/106722 - avoid invalid pointer association in predcom
When predictive commoning builds a reference for iteration N it
prematurely associates a constant offset into the MEM_REF offset
operand which can be invalid if the base pointer then points
outside of an object which alias-analysis does not consider valid.
PR tree-optimization/106722
* tree-predcom.cc (ref_at_iteration): Do not associate the
constant part of the offset into the MEM_REF offset
operand, across a non-zero offset.
* gcc.dg/torture/pr106892.c: New testcase.
next prev parent reply other threads:[~2022-09-09 12:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 21:37 [Bug c/106892] New: Wrong code at -O3 on x86_64-linux-gnu shaohua.li at inf dot ethz.ch
2022-09-08 22:02 ` [Bug c/106892] " jakub at gcc dot gnu.org
2022-09-09 7:40 ` rguenth at gcc dot gnu.org
2022-09-09 7:53 ` shaohua.li at inf dot ethz.ch
2022-09-09 8:15 ` rguenth at gcc dot gnu.org
2022-09-09 8:20 ` marxin at gcc dot gnu.org
2022-09-09 8:20 ` jakub at gcc dot gnu.org
2022-09-09 8:31 ` [Bug c/106892] [11/12/13 Regression] Wrong code at -O3 on x86_64-linux-gnu since r11-963-g80d6f89e78fc3b77 rguenth at gcc dot gnu.org
2022-09-09 8:32 ` [Bug middle-end/106892] " rguenth at gcc dot gnu.org
2022-09-09 9:05 ` rguenth at gcc dot gnu.org
2022-09-09 9:31 ` rguenth at gcc dot gnu.org
2022-09-09 10:04 ` rguenth at gcc dot gnu.org
2022-09-09 12:43 ` rguenth at gcc dot gnu.org [this message]
2022-09-10 13:14 ` [Bug middle-end/106892] [11/12 " mikpelinux at gmail dot com
2022-09-12 7:53 ` marxin at gcc dot gnu.org
2022-10-11 12:06 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:28 ` [Bug middle-end/106892] [11 " cvs-commit at gcc dot gnu.org
2022-10-17 13:29 ` rguenth 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-106892-4-fCzGo2DgUz@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).