public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65177] [5 Regression]: extend jump thread for finite state automata causes miscompilation
Date: Wed, 25 Feb 2015 23:05:00 -0000 [thread overview]
Message-ID: <bug-65177-4-6youmWyk5B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65177-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65177
Sebastian Pop <spop at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |UNCONFIRMED
Last reconfirmed|2015-02-25 00:00:00 |
Ever confirmed|1 |0
--- Comment #6 from Sebastian Pop <spop at gcc dot gnu.org> ---
The SEME region copier does not update the SSA correctly:
bb_53:
# i_1 = PHI <i_126(13), i_250(52)>
# sprv_5 = PHI <sprv_137(13), sprv_284(52)>
# .MEM_7 = PHI <.MEM_331(13), .MEM_337(52)>
# k_339 = PHI <k_84(13), k_285(52)>
# sprv_780 = PHI <1(13), 7(52)>
bb_104 is a copy of bb_53:
# i_672 = PHI <i_126(13)>
# sprv_437 = PHI <sprv_137(13)>
# .MEM_715 = PHI <.MEM_331(13)>
# k_716 = PHI <k_84(13)>
# sprv_717 = PHI <1(13)>
bb_64:
# _319 = PHI <0.0(55), 0.0(58), _313(61)>
# sprv_751 = PHI <sprv_5(55), 5(58), 8(61)>
# i_769 = PHI <i_1(55), i_766(58), i_767(61)>
# sprv_784 = PHI <sprv_780(55), sprv_781(58), 8(61)>
# k_790 = PHI <k_339(55), k_787(58), k_788(61)>
# .MEM_810 = PHI <.MEM_7(55), .MEM_807(58), .MEM_808(61)>
bb_106 a copy of bb_64:
# _594 = PHI <0.0(105)>
# sprv_515 = PHI <sprv_5(105)>
# i_516 = PHI <i_1(105)>
# sprv_567 = PHI <sprv_780(105)>
# k_541 = PHI <k_339(105)>
# .MEM_619 = PHI <.MEM_7(105)>
In bb_106, a copy of bb_64,
- # sprv_567 = PHI <sprv_780(105)>
we use the old value sprv_780 instead of the new value sprv_717 set in
bb_105:
- # sprv_515 = PHI <sprv_5(105)>
we use the old value sprv_5 instead of the new value sprv_437:
next prev parent reply other threads:[~2015-02-25 21:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:49 [Bug tree-optimization/65177] New: " marxin at gcc dot gnu.org
2015-02-23 15:58 ` [Bug tree-optimization/65177] " rguenth at gcc dot gnu.org
2015-02-23 16:19 ` trippels at gcc dot gnu.org
2015-02-23 17:41 ` marxin at gcc dot gnu.org
2015-02-23 17:48 ` spop at gcc dot gnu.org
2015-02-23 17:49 ` spop at gcc dot gnu.org
2015-02-25 21:33 ` mpolacek at gcc dot gnu.org
2015-02-25 23:05 ` spop at gcc dot gnu.org [this message]
2015-03-09 14:26 ` jakub at gcc dot gnu.org
2015-03-10 22:08 ` law at redhat dot com
2015-03-10 22:39 ` spop at gcc dot gnu.org
2015-03-10 22:42 ` spop at gcc dot gnu.org
2015-03-10 22:49 ` law at redhat dot com
2015-03-10 22:57 ` spop at gcc dot gnu.org
2015-03-10 23:03 ` law at redhat dot com
2015-03-11 16:27 ` spop at gcc dot gnu.org
2015-03-11 21:45 ` law at redhat dot com
2015-03-13 20:47 ` spop at gcc dot gnu.org
2015-03-13 21:05 ` spop at gcc dot gnu.org
2015-03-16 21:35 ` spop at gcc dot gnu.org
2015-03-17 19:05 ` law at redhat dot com
2015-03-17 20:15 ` spop at gcc dot gnu.org
2015-03-24 13:47 ` law at redhat dot com
2015-03-24 16:49 ` spop at gcc dot gnu.org
2015-03-25 23:26 ` spop at gcc dot gnu.org
2015-03-25 23:43 ` spop at gcc dot gnu.org
2015-10-28 9:01 ` yroux 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-65177-4-6youmWyk5B@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).