From: Christopher Li <sparse@chrisli.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-sparse@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: sparse: Why test-parse shows "+=" as a store?
Date: Mon, 27 Apr 2009 16:39:55 -0700 [thread overview]
Message-ID: <70318cbf0904271639w20cc0300ge2e3ac0638c698dd@mail.gmail.com> (raw)
In-Reply-To: <49F6386D.5050809@garzik.org>
On Mon, Apr 27, 2009 at 3:57 PM, Jeff Garzik <jeff@garzik.org> wrote:
>
> Well, I'll tell you what. If you or somebody else wants to volunteer to
> make key sparse & linearize changes, then I will work on a linearize LLVM
> backend.
>
> Absent that, the motivation is lower, considering I have a current, working
> approach that does not require any upstream changes.
Unless I am missing some thing. I don't see your back end generate
GET_ELEMENT_PTR instruction in LLVM. So you should be able to use existing
linearize instruction to generate what your patch does, without up stream
changes.
To generate GET_ELEMENT_PTR properly require upstream changes, but
your patch doesn't do that either.
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
next prev parent reply other threads:[~2009-04-27 23:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 20:52 sparse: Why test-parse shows "+=" as a store? Jeff Garzik
2009-04-27 6:04 ` Christopher Li
2009-04-27 10:28 ` Jeff Garzik
2009-04-27 17:45 ` Christopher Li
2009-04-27 17:53 ` Christopher Li
2009-04-27 22:57 ` Jeff Garzik
2009-04-27 23:39 ` Christopher Li [this message]
2009-04-28 0:24 ` Jeff Garzik
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=70318cbf0904271639w20cc0300ge2e3ac0638c698dd@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).