From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: MOD_TYPEDEF unused?
Date: Tue, 13 Jun 2017 15:55:22 -0700 [thread overview]
Message-ID: <CANeU7QnKLFhYJFZ3bfsJ=kpvMOjoQXghv6EwoPksBZAVAoHvsQ@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxcVHQrRNtKGS8mURVuHPUDhwsyF7AFnnvCBpbHb2AwQpQ@mail.gmail.com>
On Tue, Jun 13, 2017 at 3:01 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
> Hi,
>
> I was looking at the output of c2xml (actually modified version used
> in dmrC project) - and saw that typedefs are not marked in any way.
> Digging deeper I found that typedef symbols do not have the
> MOD_TYPEDEF set. MOD_USERTYPE is set though.
>
> Is there any harm in setting MOD_TYPEDEF also?
I take a look, nobody is actually using MOD_TYPEDEF any more.
It was used in the old code for parsing typedef types.
Of course there is no harm setting it, it might make more sense to
remove it.
Chris
next prev parent reply other threads:[~2017-06-13 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 22:01 MOD_TYPEDEF unused? Dibyendu Majumdar
2017-06-13 22:55 ` Christopher Li [this message]
2017-06-14 1:54 ` Luc Van Oostenryck
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='CANeU7QnKLFhYJFZ3bfsJ=kpvMOjoQXghv6EwoPksBZAVAoHvsQ@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
/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).