From: Jaskaran Singh <jaskaransingh7654321@gmail.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "linux-kernel-mentees@lists.linuxfoundation.org"
<linux-kernel-mentees@lists.linuxfoundation.org>,
"cocci@systeme.lip6.fr" <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [PATCH 1/2] parsing_c: Align C AST and Cocci AST for const pointer variants
Date: Sat, 08 Feb 2020 18:11:17 +0530 [thread overview]
Message-ID: <6f51f690d06cdd2278900480bd079cd90895ec43.camel@gmail.com> (raw)
In-Reply-To: <88e09c8a-e39f-2722-9f87-333d2c14a7a2@web.de>
On Sat, 2020-02-08 at 09:30 +0100, Markus Elfring wrote:
> > For a pointer, the C parser constructed an AST dissimilar from that
> > of the Cocci AST. This caused failures in matching with certain
> > pointer types. For example, for the following case:
> >
> > char *1 const *2 id;
> >
> > The C AST constructed would be:
> > const Pointer1 -> Pointer2 -> char
> >
> > The Cocci AST constructed would be:
> > Pointer2 -> const Pointer1 -> char
>
> Which software development tools support to check such information?
>
A little collection of scripts/tools I've written[1], and the
invaluable OCaml debugger :)
Cheers,
Jaskaran.
[1]http://github.com/jajajasalu2/cocci-type-test-suite
> Regards,
> Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-02-08 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 8:30 [Cocci] [PATCH 1/2] parsing_c: Align C AST and Cocci AST for const pointer variants Markus Elfring
2020-02-08 12:41 ` Jaskaran Singh [this message]
2020-02-08 12:56 ` [Cocci] Linux dev-tools: Handling complex types and attributes in Coccinelle Markus Elfring
2020-02-08 12:56 ` Markus Elfring
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=6f51f690d06cdd2278900480bd079cd90895ec43.camel@gmail.com \
--to=jaskaransingh7654321@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel-mentees@lists.linuxfoundation.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).