From: Timur Tabi <timur@kernel.org>
To: Timur Tabi <timur@kernel.org>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Octal constants confuse spatch
Date: Mon, 25 Feb 2019 17:22:26 -0600 [thread overview]
Message-ID: <CAOZdJXW=Zivu348-fCuSDUSFYTNeKVuQMectJ8_tH0V-CCfpRQ@mail.gmail.com> (raw)
In-Reply-To: <CAOZdJXWCvqVG52s3HiwH7e_yJ0ijeX41fGyv6hspXdY79wVMYw@mail.gmail.com>
On Mon, Feb 25, 2019 at 5:06 PM Timur Tabi <timur@kernel.org> wrote:
> Sorry, bad copy-paste. I meant
>
> #define FLD_SET_DRF(a, b, c, d, e) 1
Ok, now I found something weird.
If I put the #define on the top of the source file (test.c), it doesn't work.
But if I put it in a header file specified by --macro-file-builtins,
it does work.
So it seems to me that spatch is parsing the macros in the
--macro-file-builtins header file differently than the macros in the
source file itself. That doesn't explain why it doesn't like 0080,
though.
Anyway, I seem to be unblocked for now, but this might be something to
look into.
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-02-25 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 22:56 [Cocci] Octal constants confuse spatch Timur Tabi
2019-02-25 23:06 ` Timur Tabi
2019-02-25 23:22 ` Timur Tabi [this message]
2019-02-26 6:25 ` Julia Lawall
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='CAOZdJXW=Zivu348-fCuSDUSFYTNeKVuQMectJ8_tH0V-CCfpRQ@mail.gmail.com' \
--to=timur@kernel.org \
--cc=cocci@systeme.lip6.fr \
/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).