From: Christopher Li <sparse@chrisli.org>
To: Thomas Schmid <Thomas.Schmid@br-automation.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Re: Re: Getting info from used typedef
Date: Wed, 20 Jan 2010 16:38:09 -0800 [thread overview]
Message-ID: <70318cbf1001201638g4b8708e0v94160b64ed2aa854@mail.gmail.com> (raw)
In-Reply-To: <OF83C748CA.F60373EF-ONC1257680.004D070F-C1257680.004D7110@br-automation.com>
On Wed, Dec 2, 2009 at 6:05 AM, Thomas Schmid
<Thomas.Schmid@br-automation.com> wrote:
>
> Thank you, but I'm sorry, that patch doesn't work for me.
I took another look into it. I think if you are just working on the
source code transform,
you should be able to skip the evaluation step which short cut the typedef.
Can you try again with the same patch, but in your program, using
__sparse(filename)
instead of sparse(filename) to get the symbols? Using __sparse will skip the
evaluation step. It should keep the typedef node unchanged.
> Is it really not necessary for compilers (or frontends) to hold the
> information about declarations with typedefs?
The back end only care about the type, not the name of type.
In fact, C type system need to evaluation the type to get ride of the
alias so it will not complain type mismatch due to typedef.
Chris
next prev parent reply other threads:[~2010-01-21 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:34 Handle __builtin_ms_va_list Michael Stefaniuc
2009-10-01 18:41 ` Christopher Li
2009-11-25 14:15 ` Getting info from used typedef Thomas Schmid
2009-11-30 23:41 ` Christopher Li
2009-12-01 12:30 ` Antwort: " Thomas Schmid
2009-12-01 18:49 ` Christopher Li
2009-12-02 14:05 ` Thomas Schmid
2010-01-21 0:38 ` Christopher Li [this message]
2010-01-26 15:28 ` Thomas Schmid
2010-01-29 1:21 ` Christopher Li
2010-02-02 8:52 ` Thomas Schmid
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=70318cbf1001201638g4b8708e0v94160b64ed2aa854@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=Thomas.Schmid@br-automation.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).