From: Xi Wang <xi.wang@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Xi Wang <xi.wang@gmail.com>
Subject: [RFC][PATCH 0/3] implement pseudo->ctype
Date: Mon, 4 Jun 2012 02:54:34 -0400 [thread overview]
Message-ID: <1338792878-25898-1-git-send-email-xi.wang@gmail.com> (raw)
This patchset tries to implement Chris's `counter RFC': adding ->ctype
to pseudo, while removing ->type and ->size from instruction. In this
way, it provides easy access to type information for backend.
The first patch adds ->ctype to struct pseudo and doesn't touch struct
instruction. It could be applied alone if we really want backward
compatibility.
The second patch does more destructive work. It removes ->type and
->size from struct instruction and updates client uses.
The third patch updates sparse-llvm in a naive way, which should have
been much simpler with the new ->ctype in pseudo. I guess in some cases
->ctype is even necessary. Consider the example below.
void foo(int x, ...);
foo(1, 2, 3LL);
Is it possible to get the types of the 2nd and 3rd arguments in current
code, which are simply PSEUDO_VAL?
Xi Wang (3):
add ->ctype to struct pseudo
remove ->type and ->size from struct instruction
sparse, llvm: sync with new struct instruction
cse.c | 6 +--
example.c | 12 ++---
flow.c | 12 ++---
linearize.c | 147 +++++++++++++++++++++++++--------------------------------
linearize.h | 17 ++++---
memops.c | 4 +-
simplify.c | 24 +++++-----
sparse-llvm.c | 50 ++++++++++----------
sparse.c | 2 +-
unssa.c | 3 +-
10 files changed, 131 insertions(+), 146 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-06-04 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 6:54 Xi Wang [this message]
2012-06-04 6:54 ` [RFC][PATCH 1/3] add ->ctype to struct pseudo Xi Wang
2012-06-04 6:54 ` [RFC][PATCH 2/3] remove ->type and ->size from struct instruction Xi Wang
2012-06-04 6:54 ` [RFC][PATCH 3/3] sparse, llvm: sync with new " Xi Wang
2012-06-08 11:50 ` [RFC][PATCH 0/3] implement pseudo->ctype Pekka Enberg
2012-06-08 15:39 ` Xi Wang
2012-06-09 1:35 ` Xi Wang
2012-06-09 10:42 ` Pekka Enberg
2012-06-09 11:52 ` Xi Wang
2012-06-09 12:06 ` Jeff Garzik
2012-06-09 12:12 ` Pekka Enberg
2012-06-21 10:00 ` Christopher Li
2012-06-22 2:08 ` Xi Wang
2012-06-22 17:59 ` 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=1338792878-25898-1-git-send-email-xi.wang@gmail.com \
--to=xi.wang@gmail.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).