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/107107] [10/11/12/13 Regression] Wrong codegen from TBAA when stores to distinct same-mode types are collapsed?
Date: Sat, 01 Oct 2022 03:05:28 +0000 [thread overview]
Message-ID: <bug-107107-4-5pn2aNo83o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107107-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107107
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |tree-optimization
Summary|Wrong codegen from TBAA |[10/11/12/13 Regression]
|when stores to distinct |Wrong codegen from TBAA
|same-mode types are |when stores to distinct
|collapsed? |same-mode types are
| |collapsed?
Status|UNCONFIRMED |NEW
Target Milestone|--- |10.5
Last reconfirmed| |2022-10-01
Ever confirmed|0 |1
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note this has been to be a regression since tree level PRE is what is causing
the issue and that was added in GCC 4 or 4.1.
next prev parent reply other threads:[~2022-10-01 3:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 21:34 [Bug middle-end/107107] New: " bugdal at aerifal dot cx
2022-10-01 2:25 ` [Bug middle-end/107107] " bugdal at aerifal dot cx
2022-10-01 2:59 ` pinskia at gcc dot gnu.org
2022-10-01 3:02 ` pinskia at gcc dot gnu.org
2022-10-01 3:05 ` pinskia at gcc dot gnu.org [this message]
2022-10-01 3:05 ` [Bug tree-optimization/107107] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-01 17:08 ` amonakov at gcc dot gnu.org
2022-10-01 20:01 ` bugdal at aerifal dot cx
2022-10-06 9:02 ` rguenth at gcc dot gnu.org
2022-10-06 9:22 ` rguenth at gcc dot gnu.org
2022-10-06 10:07 ` cvs-commit at gcc dot gnu.org
2022-10-06 10:08 ` [Bug tree-optimization/107107] [10/11/12 " rguenth at gcc dot gnu.org
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2022-12-12 16:33 ` [Bug tree-optimization/107107] [10/11 " cvs-commit at gcc dot gnu.org
2023-01-26 13:05 ` [Bug tree-optimization/107107] [10 " cvs-commit at gcc dot gnu.org
2023-01-26 13:06 ` 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-107107-4-5pn2aNo83o@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).