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 tree-optimization/100453] [12 Regression] wrong code at -O1 and above since r12-434
Date: Sat, 15 May 2021 08:28:23 +0000 [thread overview]
Message-ID: <bug-100453-4-R04vg3VPbJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100453-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100453
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:
https://gcc.gnu.org/g:af42043e6618e69187b47f37dac870763c01e20f
commit r12-809-gaf42043e6618e69187b47f37dac870763c01e20f
Author: Martin Jambor <mjambor@suse.cz>
Date: Sat May 15 10:11:12 2021 +0200
Revert "tree-sra: Avoid refreshing into const base decls (PR 100453)"
This reverts commit ca9bb74a5f856ccdceb4797f18b0a4ac8f49d069.
...because of Ada issues I did not catch with original testing.
gcc/ChangeLog:
2021-05-12 Martin Jambor <mjambor@suse.cz>
Revert:
PR tree-optimization/100453
* tree-sra.c (sra_modify_assign): All const base accesses do not
need refreshing, not just those from decl_pool.
(sra_modify_assign): Do not refresh into a const base decl.
gcc/testsuite/ChangeLog:
2021-05-12 Martin Jambor <mjambor@suse.cz>
Revert:
PR tree-optimization/100453
* gcc.dg/tree-ssa/pr100453.c: New test.
next prev parent reply other threads:[~2021-05-15 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 14:11 [Bug tree-optimization/100453] New: wrong code at -O1 and above zhendong.su at inf dot ethz.ch
2021-05-06 17:34 ` [Bug tree-optimization/100453] [12 Regression] wrong code at -O1 and above since r12-434 jakub at gcc dot gnu.org
2021-05-11 12:24 ` ebotcazou at gcc dot gnu.org
2021-05-12 16:43 ` jamborm at gcc dot gnu.org
2021-05-13 12:25 ` jamborm at gcc dot gnu.org
2021-05-13 13:04 ` ebotcazou at gcc dot gnu.org
2021-05-13 21:27 ` cvs-commit at gcc dot gnu.org
2021-05-13 21:29 ` jamborm at gcc dot gnu.org
2021-05-14 16:24 ` ebotcazou at gcc dot gnu.org
2021-05-15 8:28 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-15 8:33 ` jamborm at gcc dot gnu.org
2021-05-16 21:06 ` ebotcazou at gcc dot gnu.org
2021-06-09 21:32 ` pinskia at gcc dot gnu.org
2021-06-15 15:10 ` jamborm at gcc dot gnu.org
2021-06-16 7:25 ` pinskia at gcc dot gnu.org
2021-06-16 11:24 ` cvs-commit at gcc dot gnu.org
2021-06-16 11:31 ` jamborm 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-100453-4-R04vg3VPbJ@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).