From: Rob Taylor <rob.taylor@codethink.co.uk>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: Pavel Roskin <proski@gnu.org>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-sparse@vger.kernel.org
Subject: Re: Finding all typedefs
Date: Thu, 02 Aug 2007 01:15:34 +0100 [thread overview]
Message-ID: <46B12226.1070802@codethink.co.uk> (raw)
In-Reply-To: <1185987691.3123.33.camel@josh-work.beaverton.ibm.com>
Josh Triplett wrote:
> On Wed, 2007-08-01 at 11:45 -0400, Pavel Roskin wrote:
>> On Fri, 2007-07-27 at 16:01 -0700, Randy Dunlap wrote:
>>> I asked Linus about 3 years ago for something that would dump
>>> global data sizes. It's attached (updated to recent sparse;
>>> it also has '-keywords' to warn about using C++ keywords, but you
>>> can ignore/delete that part). It may be fixable to do what you want,
>>> although I have no info on sparse symbol struct contents.
>>> Or maybe Josh et al can do what you want rather easily... :)
>> Sorry for delay. Thank you! I'm not sure I can reuse anything from
>> that code to dump typedefs.
>>
>> My point is, I want to write a script that would use existing software
>> to produce checkpatch.pl conforming code. If I need to hack anything,
>> I'd rather contribute to indent or astyle. In fact, it would be a much
>> better approach to recognize argument lists and format them differently,
>> rather than deal with a list of typedefs.
>>
>> I hoped that c2xml would give me typedefs, but it doesn't.
>
> It certainly should; I didn't realize that it didn't. I'll look into it
> and see if I can change that.
>
> CCing Rob (the author of c2xml) to see if he has any thoughts on this.
Well, the way a typedef appears in the c2xml output is a symbol with
type="node" and user-type="1", but this also applies to nodes that are
instances of typedefs. I still haven't figured out why I never get any
symbols with MOD_TYPEDEF set. I suspect parse.c:1225:8, though I don't
really understand this bit of code.
Another annoying thing is that the types are always resolved for
typedefs. i.e. for
typedef int foo;
foo bar;
the symbol for bar has a base type of int.
Any suggestions for how to solve this would be greatly appreciated :)
Thanks,
Rob Taylor
next prev parent reply other threads:[~2007-08-02 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 22:08 Finding all typedefs Pavel Roskin
2007-07-27 23:01 ` Randy Dunlap
2007-08-01 15:45 ` Pavel Roskin
2007-08-01 17:01 ` Josh Triplett
2007-08-02 0:15 ` Rob Taylor [this message]
2007-08-02 7:31 ` Antwort: " Thomas Schmid
2007-08-03 0:49 ` Rob Taylor
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=46B12226.1070802@codethink.co.uk \
--to=rob.taylor@codethink.co.uk \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.org \
--cc=rdunlap@xenotime.net \
/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).