From: Jakub Jelinek <jakub@redhat.com>
To: Jeff Law <law@redhat.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] combine: Fix PR80233
Date: Wed, 29 Mar 2017 20:48:00 -0000 [thread overview]
Message-ID: <20170329204425.GH17461@tucnak> (raw)
In-Reply-To: <a8f32295-e5dd-3706-590e-873292092911@redhat.com>
On Wed, Mar 29, 2017 at 02:35:32PM -0600, Jeff Law wrote:
> On 03/29/2017 12:23 PM, Segher Boessenkool wrote:
> > If combine has added an unconditional trap there will be a new basic
> > block as well. It will then end up considering the NOTE_INSN_BASIC_BLOCK
> > as the last_combined_insn, but then it tries to take the DF_INSN_LUID
> > of that and that dereferences a NULL pointer (since such a note is not
> > an INSN_P).
> >
> > This fixes it by not taking non-insns as last_combined_insn.
> >
> > Bootstrapped and tested on powerpc64-linux {-m32,-m64}.
> >
> >
> > Segher
> >
> >
> > 2017-03-29 Segher Boessenkool <segher@kernel.crashing.org>
> >
> > PR rtl-optimization/80233
> > * combine.c (combine_instructions): Only take NONDEBUG_INSN_P insns
> > as last_combined_insn. Do not test for BARRIER_P separately.
> >
> > gcc/testsuite/
> > PR rtl-optimization/80233
> > * gcc.c-torture/compile/pr80233.c: New testcase.
> No strong opinions on this vs Jakub's patch. I guess yours may walk more
> objects on the chain, but in doing so is more likely to find a useful
> LAST_COMBINED_INSN. Jakub's stops earlier, but is less likely to have
> stopped on something useful.
>
> Your call Segher.
I like Segher's latest patch. But it is his call anyway ;)
Jakub
next prev parent reply other threads:[~2017-03-29 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:47 Segher Boessenkool
2017-03-29 20:44 ` Jeff Law
2017-03-29 20:48 ` Jakub Jelinek [this message]
2017-03-29 20:49 ` Jeff Law
2017-03-29 20:56 ` Segher Boessenkool
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=20170329204425.GH17461@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).