From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Abe <abe_skolnik@yahoo.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Kyrill Tkachov <kyrylo.tkachov@arm.com>,
Sebastian Pop <sebpop@gmail.com>
Subject: Re: using scratchpads to enhance RTL-level if-conversion: the new patch is almost ready to be prepared for merging to trunk, but not 100% ready yet
Date: Fri, 25 Sep 2015 20:15:00 -0000 [thread overview]
Message-ID: <5605A1B3.7000308@redhat.com> (raw)
In-Reply-To: <20150925191812.GA10463@gate.crashing.org>
On 09/25/2015 01:18 PM, Segher Boessenkool wrote:
> On Fri, Sep 25, 2015 at 10:09:23AM -0600, Jeff Law wrote:
>>>> So what that means is the presence or absence of debug information is
>>>> causing a difference in
>>>> the code you generate. That is (of course) bad and indicates a bug
>>> of some kind in your code.
>>>
>>>> I haven't put your code under a debugger or anything like that, but
>>>> this does jump out:
>>>
>>>> + rtx_insn* temp_src_insn = BB_HEAD (then_bb);
>>>> + if (temp_src_insn && NOTE_INSN_BASIC_BLOCK_P (temp_src_insn))
>>>> + temp_src_insn = NEXT_INSN (temp_src_insn); /* skip over a
>>>> start-of-BB note */
>>>
>>>> What if BB_HEAD (then_bb) is a DEBUG_INSN with -g enabled, but is a
>>>> NOTE_INSN_BASIC_BLOCK when -g is not enabled. That could cause
>>>> this kind of failure.
>
> I haven't looked at the full code, but NEXT_INSN is even more suspicious
> (you also need to skip the debug insns).
Yes, you're absolutely right. :-)
jeff
next prev parent reply other threads:[~2015-09-25 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 2:26 Abe
2015-09-24 6:29 ` Jeff Law
2015-09-24 15:45 ` Abe
2015-09-25 16:22 ` Jeff Law
2015-09-25 17:38 ` Abe Skolnik
2015-09-25 19:04 ` Jeff Law
2015-09-25 20:03 ` Segher Boessenkool
2015-09-25 20:15 ` Jeff Law [this message]
2015-09-25 21:24 ` Abe Skolnik
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=5605A1B3.7000308@redhat.com \
--to=law@redhat.com \
--cc=abe_skolnik@yahoo.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=sebpop@gmail.com \
--cc=segher@kernel.crashing.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).