linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christopher Li <sparse@chrisli.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 20:24:51 -0400	[thread overview]
Message-ID: <49F64CD3.2040100@garzik.org> (raw)
In-Reply-To: <70318cbf0904271639w20cc0300ge2e3ac0638c698dd@mail.gmail.com>

Christopher Li wrote:
> 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.

That is because the v2 backend is largely integer only, and did not do 
much with structs.


> To generate GET_ELEMENT_PTR properly require upstream changes, but
> your patch doesn't do that either.

Quoting the email to which you replied:  "I just managed to figure out[...]"

There are many changes beyond the v2 patch posted already, but this is 
only at the "confirmed a theory with test code" stage, not yet even 
included in any local repository.

	Jeff




      reply	other threads:[~2009-04-28  0:24 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
2009-04-28  0:24           ` Jeff Garzik [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=49F64CD3.2040100@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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).