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] [2/2] tests: Add test case to match const pointer variants
Date: Fri, 07 Feb 2020 11:45:13 +0530 [thread overview]
Message-ID: <6e7b556fe05500b5c4f0852b5a7b65f9c762f5ad.camel@gmail.com> (raw)
In-Reply-To: <964378a7-ddd3-a1f8-e567-f3c4392b14a5@web.de>
On Fri, 2020-02-07 at 07:07 +0100, Markus Elfring wrote:
> > Would the following be a better subject?
>
> The alternative is nicer.
>
>
> Will other implementation details become also more interesting?
>
> The information “Align C AST and Cocci AST” was provided.
> https://lore.kernel.org/cocci/20200205130327.6812-2-jaskaransingh7654321@gmail.com/
> https://systeme.lip6.fr/pipermail/cocci/2020-February/006840.html
>
> * Should the potential for differences in these “AST” be checked any
> more?
>
An effort is already being made to do this by me and Julia :)
> * How can such items be compared safely?
>
Not sure what you mean. If you mean how the two ASTs can be compared,
it's just a process of data collection and debugging.
Cheers,
Jaskaran.
>
> Is there a need to extend the test format?
> https://github.com/coccinelle/coccinelle/issues/134
>
> Regards,
> Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-02-07 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 18:55 [Cocci] [PATCH 2/2] tests: Add test case for matching pointers to const pointers (and variants) Markus Elfring
2020-02-06 11:58 ` Jaskaran Singh
2020-02-06 14:00 ` Julia Lawall
2020-02-06 15:43 ` [Cocci] [2/2] tests: Add test case to match const pointer variants Markus Elfring
2020-02-07 6:07 ` Markus Elfring
2020-02-07 6:15 ` Jaskaran Singh [this message]
2020-02-07 6:24 ` 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=6e7b556fe05500b5c4f0852b5a7b65f9c762f5ad.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).