From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Trying to understand linearized output
Date: Sun, 12 Mar 2017 18:00:33 +0000 [thread overview]
Message-ID: <CACXZuxdevCRT1VNrPRC1VXSH5nHQj17F9aPpDHOQU++Uu_384A@mail.gmail.com> (raw)
In-Reply-To: <20170312172050.24fwpfamwb3iivru@macpro.local>
On 12 March 2017 at 17:20, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> On Sun, Mar 12, 2017 at 05:15:54PM +0000, Dibyendu Majumdar wrote:
>> On 12 March 2017 at 17:10, Luc Van Oostenryck
>> <luc.vanoostenryck@gmail.com> wrote:
>> > On Sun, Mar 12, 2017 at 02:11:37PM +0000, Dibyendu Majumdar wrote:
>> >> ...
>> >>
>> >> My question is:
>> >>
>> >> phisrc.64 %phi98(current) <- %r333
>> >>
>> >> The phi98 above is presumably referencing a pseudo which has number
>> >> 98. But this is not part of this function, so I am confused. Does this
>> >> look right?
>> >
>> > I didn't checked all the details by it looks right.
>> >
>> > The %phi98 is not referencing a pseudo which has the number 98.
>> > It is a pseudo numbered 98 and which is of type PSEUDO_PHI.
>> > Those kind of pseudos are exclusively created by 'phisrc' instructions
>> > and used by 'phi' instructions.
>> > Here this %phi98 is used by the phi instructions at block .L127
>> >
>> > These 'phi' instructions are the core of the SSA representation of
>> > intermediate code. If needed Wikipedia gives a good introduction:
>> > https://en.wikipedia.org/wiki/Static_single_assignment_form
>>
>>
>> Thanks. I am familiar with phi instructions in LLVM, but the phisrc
>> instructions in Sparse are new to me.
>
> Good. I wasn't sure.
>
> Those phisrc are unimportant, you can consider them as a kind of 'move'
> which is only but systematically used for each pseudo feeded to a phi
> instruction. They ahev no special semantic, they just make some things
> little bit easier for sparse.
>
I got confused by the numbering initially as I was expecting all
pseudos within a single function to be numbered sequentially.
So I should just read following :
phisrc.64 %phi98(current) <- %r333
As:
%phi98(current) = %r333
And 98 just happens to be the identifier for the pseudo, and 'phi' is
just to help the reader know that the value will go into a phi
instruction later. Is that correct?
Regards
Dibyendu
next prev parent reply other threads:[~2017-03-12 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 14:11 Trying to understand linearized output Dibyendu Majumdar
2017-03-12 17:10 ` Luc Van Oostenryck
2017-03-12 17:15 ` Dibyendu Majumdar
2017-03-12 17:20 ` Luc Van Oostenryck
2017-03-12 18:00 ` Dibyendu Majumdar [this message]
2017-03-12 19:27 ` 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=CACXZuxdevCRT1VNrPRC1VXSH5nHQj17F9aPpDHOQU++Uu_384A@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@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 NNTP newsgroup(s).