public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.collison at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/61033] [4.8/4.9 Regression] Infinite loop in variable tracking
Date: Thu, 21 May 2015 02:10:00 -0000 [thread overview]
Message-ID: <bug-61033-4-x3l21G147h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61033-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61033
Michael Collison <michael.collison at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|michael.collison at linaro dot org |mkuvyrkov at gcc dot gnu.org
--- Comment #12 from Michael Collison <michael.collison at linaro dot org> ---
GCC is looping infinitely in attempting to solve a data flow problem in
vt_find_locations. My working theory is that compute_bb_dataflow is incorrectly
asserting some value has changed. I have reduced my case to a candidate set of
basic blocks and a (candiate) RTL location this is continually removed/added.
The rtl location is:
dataflow difference found: removal of:
name: D#255
offset 0
(mem/f/c:SI (value/u:SI 106:3955 @0x22cb2f8/0x23424a0) [3 result.d+0 S4
A32])
I understand that the argument to 'VALUE" is a cselib_val_struct but I don't
know how to map this back to a insn that is causing the problem. Any thoughts
on how I might debug thus further?
next prev parent reply other threads:[~2015-05-21 2:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 4:40 [Bug debug/61033] New: " michael.collison at linaro dot org
2014-08-04 15:42 ` [Bug debug/61033] " ktkachov at gcc dot gnu.org
2014-08-04 15:45 ` ktkachov at gcc dot gnu.org
2014-08-04 18:07 ` [Bug debug/61033] [4.8/4.9 Regression] " cbaylis at gcc dot gnu.org
2014-08-04 18:43 ` cbaylis at gcc dot gnu.org
2014-08-04 18:55 ` michael.collison at linaro dot org
2014-08-19 16:25 ` dcb314 at hotmail dot com
2014-08-19 16:33 ` dcb314 at hotmail dot com
2014-11-19 13:28 ` rguenth at gcc dot gnu.org
2014-12-10 12:58 ` rguenth at gcc dot gnu.org
2014-12-19 13:33 ` jakub at gcc dot gnu.org
2015-05-21 2:10 ` michael.collison at linaro dot org [this message]
2015-06-23 8:28 ` rguenth at gcc dot gnu.org
2015-06-26 20:03 ` [Bug debug/61033] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:32 ` jakub 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-61033-4-x3l21G147h@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).