linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Give the constant pseudo value a size
Date: Mon, 14 Aug 2017 18:35:17 +0100	[thread overview]
Message-ID: <CACXZuxeteW+qcbMzbV1zazPL-YKJmvpA46G4PQ4dJoG7DO1M+Q@mail.gmail.com> (raw)
In-Reply-To: <CANeU7Q=gK9fgX6RkHdOmnvSB8iEEsJzC-RCgXfu=Y6gED=pUxg@mail.gmail.com>

Hi Chris,

On 14 August 2017 at 18:23, Christopher Li <sparse@chrisli.org> wrote:
> On Mon, Aug 14, 2017 at 1:11 PM, Dibyendu Majumdar
> <mobile@majumdar.org.uk> wrote:
>> The push approach has the benefit that it makes clear what arguments
>> are being passed in a call. Previously this information was not
>> revealed in the Sparse linearized dump. It would be a shame to lose
>> that information - perhaps you could still dump the arguments along
>> with a call?
>
> Are you sure?
> Here is what I have for RC5:
> ./test-linearize cse.c
>
> .L414:
> load.64     %r1052 <- 0[insn]
> call.64     %r1053 <- try_to_cse, %arg1, %r1044(last), %r1052
> store.64    %r1053 -> 0[insn]
> phisrc.64   %phi474 <- %r1053
> br          .L413
>
> You can see exactly what is the calling arguments. There is an pseudo_list
> for the arguments.
>

Ah okay - I don't see that in dmrC output. It must have been removed
as part of the push change.

Regards
Dibyendu

      reply	other threads:[~2017-08-14 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13  4:18 [PATCH] Give the constant pseudo value a size Christopher Li
2017-08-14 17:11 ` Dibyendu Majumdar
2017-08-14 17:23   ` Christopher Li
2017-08-14 17:35     ` Dibyendu Majumdar [this message]

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=CACXZuxeteW+qcbMzbV1zazPL-YKJmvpA46G4PQ4dJoG7DO1M+Q@mail.gmail.com \
    --to=mobile@majumdar.org.uk \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).