From: Andrew Pinski <pinskia@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH] [PR 81245] Fix tree-if-conv calling of update_stmt after fold_stmt
Date: Thu, 29 Jun 2017 20:12:00 -0000 [thread overview]
Message-ID: <CA+=Sn1nEo5FF4zAYD_ojNuDJ9v2Qh=RAw-XQ0B9W=F8S8EpKxg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hi,
As described in the bug, tree-if-conv is calling update_stmt on an
old stmt which might have been removed from the IR already
(transforming of an assignment to a call in this case). This fixes
the problem by calling update_stmt on the new statement that fold_stmt
might have created.
OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.
Thanks,
Andrew Pinski
ChangeLog:
* tree-if-conv.c (predicate_scalar_phi): Update new_stmt if fold_stmt
returned true.
testsuite/ChangeLog:
* gcc.dg/torture/pr81245.c: New testcase.
[-- Attachment #2: fixifcvt.diff.txt --]
[-- Type: text/plain, Size: 1214 bytes --]
Index: testsuite/gcc.dg/torture/pr81245.c
===================================================================
--- testsuite/gcc.dg/torture/pr81245.c (nonexistent)
+++ testsuite/gcc.dg/torture/pr81245.c (working copy)
@@ -0,0 +1,16 @@
+/* { dg-options "-ffast-math" } */
+/* { dg-do compile } */
+/* This test used to crash the vectorizer as the ifconvert pass
+ used to convert the if to copysign but called update_stmt on
+ the old statement after calling fold_stmt. */
+double sg[18];
+void f(void)
+{
+ for (int i = 0 ;i < 18;i++)
+ {
+ if (sg[i] < 0.0)
+ sg[i] = -1.0;
+ else
+ sg[i] = 1.0;
+ }
+}
Index: tree-if-conv.c
===================================================================
--- tree-if-conv.c (revision 249769)
+++ tree-if-conv.c (working copy)
@@ -1853,7 +1853,8 @@
new_stmt = gimple_build_assign (res, rhs);
gsi_insert_before (gsi, new_stmt, GSI_SAME_STMT);
gimple_stmt_iterator new_gsi = gsi_for_stmt (new_stmt);
- fold_stmt (&new_gsi, ifcvt_follow_ssa_use_edges);
+ if (fold_stmt (&new_gsi, ifcvt_follow_ssa_use_edges))
+ new_stmt = gsi_stmt (new_gsi);
update_stmt (new_stmt);
if (dump_file && (dump_flags & TDF_DETAILS))
next reply other threads:[~2017-06-29 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 20:12 Andrew Pinski [this message]
2017-06-30 8:20 ` Richard Biener
2017-06-30 20:40 ` Andrew Pinski
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='CA+=Sn1nEo5FF4zAYD_ojNuDJ9v2Qh=RAw-XQ0B9W=F8S8EpKxg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@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).