From: Christopher Li <sparse@chrisli.org>
To: Thomas Schmid <Thomas.Schmid@br-automation.com>
Cc: linux-sparse@vger.kernel.org, linux-sparse-owner@vger.kernel.org
Subject: Re: Re: Re: Re: Getting info from used typedef
Date: Thu, 28 Jan 2010 17:21:18 -0800 [thread overview]
Message-ID: <70318cbf1001281721p1b0df85ey63e58062dd7d809@mail.gmail.com> (raw)
In-Reply-To: <OFCC691C46.FB86BED9-ONC12576B7.0053EA67-C12576B7.0054F94E@br-automation.com>
On Tue, Jan 26, 2010 at 7:28 AM, Thomas Schmid
<Thomas.Schmid@br-automation.com> wrote:
>
> Yes, that seems to help, thank you very much.
> I think because of the missing evaluation step, it is now a little bit
> more tricky
> to get out the elements of an struct or enum, but it will work.
> Do I lose anything else, skipping the evaluation step?
You don't have the type evaluation. I don't think your source code
transform program
cares.
>
> Is it possible to commit your change (
> 0001-hacking-preserve-typedef-name.patch) in source?
> - I didn't recognize any change in behaviour when using the function
> sparse().
How about make it an hidden options? It does not make sense for compiler
to care about the typedef name. I will send out a review later.
Chris
next prev parent reply other threads:[~2010-01-29 1:21 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
2010-01-26 15:28 ` Thomas Schmid
2010-01-29 1:21 ` Christopher Li [this message]
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=70318cbf1001281721p1b0df85ey63e58062dd7d809@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=Thomas.Schmid@br-automation.com \
--cc=linux-sparse-owner@vger.kernel.org \
--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).