linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm issue with handling of phisrc instruction
Date: Wed, 22 Mar 2017 21:42:59 +0100	[thread overview]
Message-ID: <20170322204258.gpyewnksfccv5bta@macbook.local> (raw)
In-Reply-To: <CACXZuxfaQn+XApJpRY_63zf28VSeywj6R_kmy1sUHU3kEFpu-g@mail.gmail.com>

On Wed, Mar 22, 2017 at 06:55:37PM +0000, Dibyendu Majumdar wrote:
> Hi Luc,
> 
> On 22 March 2017 at 18:17, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> >>>>> I am trying to see if sparse-llvm can handle unsimplified IR output
> >>>>> from linearizer. I think there is a problem in how it handles phisrc.
> >>>>
> >>>> Does your non-simplified sparse IR contain the liveness information?
> >>>> I think those are needed for the handling of OP_PHI & OP_PHISOURCE
> >>>> in sparse-llvm.
> >>>>
> >>>
> >>> Probably not - I commented out everything in linearize_fn() from
> >>> simplify_symbol_usage() and downwards. Please tell me if this is
> >>> incorrect.
> >>
> >> As far as I understand, sparse-llvm needs track_pseudo_liveness().
> >>
> >
> > Tried that - it made no difference.
> >
> 
> If there is a single phisrc and phi instruction then is phisrc meant
> to have the phi in its user list?

Yes but again this may depends on the simplification for
its correctness.

Also, for phi-nodes liveness is a bit different, unintuitive at first,
the PSEUDO_PHI play no role in liveness. So, in IR code like:
   .L0
	phisrc	%phi1 <- ...
	...

   .L1
	phi	%r2 <- %phi1, %phi2

the "liveness between .L0 & .L1" is not made via %phi1 but with the
"real" pseudo: %r2 (.L0 defines %r2, .L1 needs %r2).
 
-- Luc

  reply	other threads:[~2017-03-22 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 16:46 sparse-llvm issue with handling of phisrc instruction Dibyendu Majumdar
2017-03-22 17:38 ` Luc Van Oostenryck
2017-03-22 18:05   ` Dibyendu Majumdar
2017-03-22 18:15     ` Luc Van Oostenryck
2017-03-22 18:17       ` Dibyendu Majumdar
2017-03-22 18:55         ` Dibyendu Majumdar
2017-03-22 20:42           ` Luc Van Oostenryck [this message]
2017-03-22 20:48             ` Dibyendu Majumdar
2017-03-22 21:38               ` Luc Van Oostenryck
2017-03-22 19:29         ` Luc Van Oostenryck
2017-03-22 19:46           ` Dibyendu Majumdar
2017-03-22 20:33             ` Dibyendu Majumdar
2017-03-22 20:46             ` Luc Van Oostenryck

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=20170322204258.gpyewnksfccv5bta@macbook.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mobile@majumdar.org.uk \
    /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 NNTP newsgroup(s).