All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 3] Add instruction to pseudo user tracking.
Date: Tue, 16 Jan 2007 20:48:21 -0800	[thread overview]
Message-ID: <45ADAA95.4010202@freedesktop.org> (raw)
In-Reply-To: <20070117023616.GC962@chrisli.org>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

Christopher Li wrote:
> The current way of tracking pseudo register user is by
> keeping a list of the address of the pseudo_t member.
> This address can be in part of the instruction member, the
> worse case is in the argument list of the call instruction.
> 
> As the comment for address_taken() said, using the container
> to get instruction pointer is wrong. It use to work with instruction
> that relate to symbol address. But that is not true any more. Even
> worse, it is very hard to track the pseudo usage other than symbol
> address. The only reason symbol address used to works for call instruction
> is because call instruction did not directly use the symbol address.
> 
> I bit the bullet and just add the instruction pointer to pair with
> the pseudo user pointer. So it will work with the case that the
> user instruction is call as well.

Good call; merged.  Thanks.

- Josh Triplett



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2007-01-17  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  2:36 [PATCH 3] Add instruction to pseudo user tracking Christopher Li
2007-01-17  4:48 ` Josh Triplett [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=45ADAA95.4010202@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.