public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/autopar_devel] tree-optimization/95308 - really avoid forward propagating of &TMR Date: Sat, 22 Aug 2020 21:33:47 +0000 (GMT) [thread overview] Message-ID: <20200822213347.1AD603857C46@sourceware.org> (raw) https://gcc.gnu.org/g:90865dd34e94407f9f3ebd86e40bf44e6e968e0d commit 90865dd34e94407f9f3ebd86e40bf44e6e968e0d Author: Richard Biener <rguenther@suse.de> Date: Mon May 25 13:48:57 2020 +0200 tree-optimization/95308 - really avoid forward propagating of &TMR This fixes a hole that still allowed forwarding of TARGET_MEM_REF addresses. 2020-05-25 Richard Biener <rguenther@suse.de> PR tree-optimization/95308 * tree-ssa-forwprop.c (pass_forwprop::execute): Generalize test for TARGET_MEM_REFs. * g++.dg/torture/pr95308.C: New testcase. Diff: --- gcc/ChangeLog | 6 ++++++ gcc/testsuite/ChangeLog | 5 +++++ 2 files changed, 11 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 150dc096c7a..d5844590274 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2020-05-25 Richard Biener <rguenther@suse.de> + + PR tree-optimization/95308 + * tree-ssa-forwprop.c (pass_forwprop::execute): Generalize + test for TARGET_MEM_REFs. + 2020-05-25 Richard Biener <rguenther@suse.de> PR tree-optimization/95295 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index cba153f166e..dfb92ec5748 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-05-25 Richard Biener <rguenther@suse.de> + + PR tree-optimization/95308 + * g++.dg/torture/pr95308.C: New testcase. + 2020-05-25 Richard Biener <rguenther@suse.de> PR tree-optimization/95295
next reply other threads:[~2020-08-22 21:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-22 21:33 Giuliano Belinassi [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-08-22 21:33 Giuliano Belinassi
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=20200822213347.1AD603857C46@sourceware.org \ --to=giulianob@gcc.gnu.org \ --cc=gcc-cvs@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).