From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Pekka Enberg <penberg@kernel.org>,
linux-sparse@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Garzik <jgarzik@redhat.com>
Subject: Re: [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend
Date: Thu, 02 Feb 2012 11:54:04 +1100 [thread overview]
Message-ID: <1328144044.28487.91.camel@pasglop> (raw)
In-Reply-To: <CANeU7Q=3mA3sjaj+rV=79qZxM_bYxDBUdMV4dECHprpKzey1Lg@mail.gmail.com>
On Wed, 2012-02-01 at 16:09 -0800, Christopher Li wrote:
>
> Ok, this patch definitely works. However, I think there is ways to get the
> type without this patch. The more general question is, how to get type of
> any given pseudo register. Currently it is a bit twisted but that information
> should be accessible. I believe that has been discuss on the mail list
> before. That is why we have insn->type. LLVM want to know every type
> of every value in the back end any way. If we are going to do proper
> llvm style "get element pointer" in the back end, we need to access type
> of every pesudo register.
We also should probably store the LLVM Ref of the type once "converted"
into the original struct symbol so that we don't have to re-create it or
all the time (thinking especially of typedef'ed function pointers) or
search for it by name (functions).
Cheers,
Ben.
next prev parent reply other threads:[~2012-02-02 0:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 9:55 [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend Pekka Enberg
2012-02-01 9:55 ` [RFC/PATCH 2/2] sparse, llvm: Fix varargs functions Pekka Enberg
2012-02-01 10:47 ` Benjamin Herrenschmidt
2012-02-01 13:58 ` Jeff Garzik
2012-02-02 0:09 ` [RFC/PATCH 1/2] sparse, llvm: Make function declaration accessible to backend Christopher Li
2012-02-02 0:54 ` Benjamin Herrenschmidt [this message]
2012-02-02 6:28 ` Pekka Enberg
2012-02-02 1:03 ` Jeff Garzik
2012-02-02 1:22 ` Benjamin Herrenschmidt
2012-02-02 1:33 ` Christopher Li
2012-02-02 1:50 ` Benjamin Herrenschmidt
2012-02-02 2:10 ` Christopher Li
2012-02-03 9:09 ` Pekka Enberg
2012-02-03 11:31 ` Benjamin Herrenschmidt
2012-02-04 12:20 ` Christopher Li
2012-02-04 12:56 ` Pekka Enberg
2012-02-04 15:27 ` Linus Torvalds
2012-02-04 15:34 ` Pekka Enberg
2012-02-02 1:22 ` Christopher 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=1328144044.28487.91.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jgarzik@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@kernel.org \
--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).