From: Christopher Li <sparse@chrisli.org>
To: Xi Wang <xi.wang@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [RFC][PATCH 0/3] implement pseudo->ctype
Date: Fri, 22 Jun 2012 10:59:51 -0700 [thread overview]
Message-ID: <CANeU7Q==MEahGWuUMFKybp4FQrUn4MBn=euhvF9wcFLTKHOvRw@mail.gmail.com> (raw)
In-Reply-To: <BDDFC596-BA52-41EA-8C7D-D35E620F8E6B@gmail.com>
On Thu, Jun 21, 2012 at 7:08 PM, Xi Wang <xi.wang@gmail.com> wrote:
> On Jun 21, 2012, at 6:00 PM, Christopher Li wrote:
> https://github.com/xiw/sparse/commit/7072002
>
> Then we have:
>
> and.64 %r2 <- %arg1, $0x1fffffff
> cast.32 %r3 <- (64) %r2
> ret.32 %r3
>
> Does this make sense? Or should we just provide an option to turn
> off all sparse simplifications, since backends usually have their own
> optimization passes?
Adding the cast from 64 to 32 bit make sense.
The sparse checker can still benefit from the simplifications. I think
it is OK we turn off those simplifications for sparse-llvm back end.
I want to have this module that, the back end can pick to chose
what kind of simplification/optimization done to the linearized
instructions.
I think the sparse-llvm back end need a different code path in the
front end for things like GEP any way.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-06-22 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 6:54 [RFC][PATCH 0/3] implement pseudo->ctype Xi Wang
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 [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='CANeU7Q==MEahGWuUMFKybp4FQrUn4MBn=euhvF9wcFLTKHOvRw@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=xi.wang@gmail.com \
/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).