linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josht@linux.vnet.ibm.com>
To: David Given <dg@cowlark.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Adding type information to instructions
Date: Mon, 07 Jul 2008 10:42:41 -0700	[thread overview]
Message-ID: <1215452561.3003.21.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <486EB59C.100@cowlark.com>

On Sat, 2008-07-05 at 00:43 +0100, David Given wrote:
> I've been having trouble finding the types of pseudos; the approach I've
> been using, which is to follow the chain of pseudo's definers until I
> find an instruction with enough type information to use, turns out to
> fail utterly on OP_LOAD instructions; I can't find any way of getting
> enough information from the opcode's arguments to determine the type of
> the target.
> 
> As a result, I've had to make a minor patch to the lineariser code.
> Given that the lineariser knows the information I need at the point
> where it generates the instruction, it would seem to make sense to tag
> the instruction with the type. This is made quite easy by the way that
> the lineariser has a allocate-typed-instruction function.
> 
> Patch enclosed; it's very simple.
> 
> Does this seem like a reasonable approach? Is it something that would be
> useful to have in the base builds? Are there any ramifications I should
> be aware of?

I can't think of any fundamental reason not to do this, other than the
standard reason of data structure size.  However, I'd like to hear
something from others on the list before accepting this patch.

- Josh Triplett



  reply	other threads:[~2008-07-07 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 23:43 Adding type information to instructions David Given
2008-07-07 17:42 ` Josh Triplett [this message]
2008-07-07 20:08   ` Chris Li

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=1215452561.3003.21.camel@josh-work.beaverton.ibm.com \
    --to=josht@linux.vnet.ibm.com \
    --cc=dg@cowlark.com \
    --cc=linux-sparse@vger.kernel.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).