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 20:32:26 -0400 [thread overview]
Message-ID: <49F64E9A.2030009@garzik.org> (raw)
In-Reply-To: <70318cbf0904271627w25df616di12e5b1454e89764f@mail.gmail.com>
Christopher Li wrote:
> On Mon, Apr 27, 2009 at 3:39 PM, Jeff Garzik <jeff@garzik.org> wrote:
>> You can see the above code was taken verbatim from show-parse.c, and is
>> probably nothing more than a check the original author (Linus?) felt
>> appropriate at the time, for show-parse.c. I wouldn't read too much into
>> its presence in s2l-gen.c -- maybe those checks can simply be deleted.
>
> I did not explain it clear it enough. It is not about the code is not
> used. My point is:
>
> 1) linearize instruction does not lose the information you care about
> generating better LLVM code. The evaluation does.
> 2) By writing your own AST recursive code, it does not gain more
> information than what you can already do with current linearize
> instruction. The EXPR_DEREF is processed in evaluation stage.
> The structure laid you care about is already gone by the time your
> s2l-gen about to emit LLVM byte codes. You did not generate any
> GET_ELEMENT_PTR in your LLVM byte code, right?
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.
Jeff
next prev parent reply other threads:[~2009-04-28 0:32 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 [this message]
2009-04-28 1:04 ` Christopher Li
2009-04-28 1:21 ` Jeff Garzik
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=49F64E9A.2030009@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 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).