From: Jeff Garzik <jeff@garzik.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH v2] sparse: add LLVM code generation backend
Date: Mon, 27 Apr 2009 21:21:30 -0400 [thread overview]
Message-ID: <49F65A1A.50300@garzik.org> (raw)
In-Reply-To: <70318cbf0904271804i4b8a14cbqfa62f521dc7258a3@mail.gmail.com>
Christopher Li wrote:
> On Mon, Apr 27, 2009 at 5:32 PM, Jeff Garzik <jeff@garzik.org> wrote:
>> Not true -- I can walk SYM_STRUCT of the function arguments' base_type
>> passed to a SYM_FN. Similarly so for struct-based variable declarations.
>>
>> With that information, you can easily back-reference lvalue uses to the
>> original struct.
>
> Let say I follow this route, isn't that you can apply the same trick for the
> linearize instruction case? struct instruction has a type member give a
> pointer to C type.
>
> I still don't see a reason why you have to use your own AST recursive
> code.
You mean, besides the reasons already listed? Namely, no upstream
changes are required, and I already have something that works.
Sure, the same trick can be applied. But that requires a total backend
rewrite plus dealing with linearize obstacles already described (ref
linearize_load_gen, linearize_store_gen). Thus it is obviously a lot
more work, with additional obstacles (patching upstream, which affects
existing users), just get back to achieving the same result :)
Jeff
next prev parent reply other threads:[~2009-04-28 1:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 20:58 [PATCH v2] sparse: add LLVM code generation backend Jeff Garzik
2009-04-27 19:15 ` Christopher Li
2009-04-27 22:39 ` Jeff Garzik
2009-04-27 23:27 ` Christopher Li
2009-04-28 0:32 ` Jeff Garzik
2009-04-28 1:04 ` Christopher Li
2009-04-28 1:21 ` Jeff Garzik [this message]
2009-04-28 2:15 ` Christopher Li
2009-04-28 22:59 ` Christopher Li
2009-04-29 22:25 ` 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=49F65A1A.50300@garzik.org \
--to=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.