From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: ptx preliminary rtl patches [1/4]
Date: Thu, 30 Oct 2014 23:38:00 -0000 [thread overview]
Message-ID: <5452B457.2020904@redhat.com> (raw)
In-Reply-To: <20141030173615.GA22655@gate.crashing.org>
On 10/30/14 11:36, Segher Boessenkool wrote:
> On Thu, Sep 11, 2014 at 03:24:54PM +0200, Bernd Schmidt wrote:
>> The nvptx backend is somewhat unusual in that call insns set a pseudo.
>> The combiner is surprised by this and allows combining them into other
>> insns, which remain as INSN rather than CALL_INSN. Aborts ensue.
>
> distribute_notes has code for when I2 is a CALL. This suggests that
> on some other targets there can be useful combinations made, so it
> isn't in that case terribly nice to disable all combinations with CALLs
> as I0 or I1 or I2.
>
> Or it's dead code :-)
Most likely it's dead code.
jeff
next prev parent reply other threads:[~2014-10-30 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 13:25 Bernd Schmidt
2014-10-29 23:58 ` Bernd Schmidt
2014-10-30 3:47 ` Jeff Law
2014-10-30 18:38 ` Segher Boessenkool
2014-10-30 23:38 ` Jeff Law [this message]
2014-10-31 17:27 ` Bernd Schmidt
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=5452B457.2020904@redhat.com \
--to=law@redhat.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--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).