From: Christopher Li <sparse@chrisli.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] do not ignore attribute 'noreturn'...
Date: Mon, 14 Sep 2009 13:47:40 -0700 [thread overview]
Message-ID: <70318cbf0909141347p47c8a277ja6f9d18ae3c6fcbd@mail.gmail.com> (raw)
In-Reply-To: <200909142144.37273.kdudka@redhat.com>
On Mon, Sep 14, 2009 at 12:44 PM, Kamil Dudka <kdudka@redhat.com> wrote:
> It sounds like a tough challenge to me :-)
>
> I am playing with the SPARSE API now. Any chance to pass in a unique ID
> to each symbol? (as equivalent to DECL_UID from <gcc/tree.h>) I can of course
> manage an ptr/ID mapping at application level. I am only curious if this is
Can you clarify why do you need to use the UID instead of the pointer of
symbol? One reason I can see is that if you want to dump the AST tree
into objects on disk. Other application can read it back and load into
memory. If the symbol already exist in the memory, you should be able to
use pointer directly.
BTW, I have code to dump most of the struct into disk already. I think
I send to the list before. Of course I can create a branch for it. Reading
is not completed yet.
Chris
next prev parent reply other threads:[~2009-09-14 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:30 [PATCH] do not ignore attribute 'noreturn' Kamil Dudka
2009-08-28 21:44 ` Christopher Li
2009-09-14 17:27 ` Christopher Li
2009-09-14 17:32 ` Kamil Dudka
2009-09-14 17:55 ` Christopher Li
2009-09-14 19:44 ` Kamil Dudka
2009-09-14 20:47 ` Christopher Li [this message]
2009-09-14 21:13 ` Kamil Dudka
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=70318cbf0909141347p47c8a277ja6f9d18ae3c6fcbd@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.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).