public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Alan Hayward <Alan.Hayward@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH 1/7]: SVE: Add CLOBBER_HIGH expression
Date: Tue, 28 Nov 2017 15:17:00 -0000	[thread overview]
Message-ID: <5ce2c3e4-776b-7fad-cd3f-2c60230315bc@redhat.com> (raw)
In-Reply-To: <CAFiYyc1iu_BYV6EiNBtC_RMqZfBt9eOjGHAHn6a5aWwYP=DgWg@mail.gmail.com>

On 11/28/2017 04:55 AM, Richard Biener wrote:

>>> Or consider a stream of code containing two tls_desc calls (ok, the compiler might
>>> optimise one of the tls calls away, but this approach should be reusable for other exprs).
>>> Between the two set(x,x)’s x is considered live so the register allocator can’t use that
>>> register.
>>> Given that we are applying this to all the neon registers, the register allocator now throws
>>> an ICE because it can’t find any free hard neon registers to use.
>> Given your statements it sounds like the liveness infrastructure is
>> making those neon regs globally live when it sees the low part subreg
>> self-set.  Let's confirm that one way or the other and see where it
>> takes us.
> 
> Indeed in (set (subreg:neon reg1) (subreg:neon reg1)) it appears that
> the lowpart of reg1
> is used and thus it is live but liveness analysis can (and should)
> simply ignore such sets.
My suggestion was going to be to peek a bit at the life analysis code if
indeed my suspicion was true.

Jeff

  reply	other threads:[~2017-11-28 15:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 12:34 Alan Hayward
2017-11-16 18:15 ` Jeff Law
2017-11-16 18:39   ` Richard Biener
2017-11-16 18:57     ` Alan Hayward
2017-11-17 19:45       ` Jeff Law
2017-11-20 15:42         ` Alan Hayward
2017-11-21  6:19           ` Jeff Law
2017-11-22 11:41             ` Alan Hayward
2017-11-22 17:44               ` Jeff Law
2017-11-23 11:25                 ` Alan Hayward
2017-11-27 17:47                   ` Jeff Law
2017-11-28 11:58                     ` Richard Biener
2017-11-28 15:17                       ` Jeff Law [this message]
2017-11-30 11:16                     ` Alan Hayward
2017-12-12 11:11                       ` Alan Hayward
2017-12-19 10:12                         ` Alan Hayward
2017-12-19 16:27                           ` Jeff Law
2018-01-12 12:14                             ` Alan Hayward
2018-01-24 12:20                               ` Alan Hayward

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=5ce2c3e4-776b-7fad-cd3f-2c60230315bc@redhat.com \
    --to=law@redhat.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=richard.guenther@gmail.com \
    /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).