From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org, smatch@vger.kernel.org,
John Levon <john.levon@joyent.com>,
Alex Kogan <alex.kogan@oracle.com>
Subject: Re: [PATCH] function attributes apply to the function declaration
Date: Sat, 16 Nov 2019 23:50:24 +0100 [thread overview]
Message-ID: <20191116225024.kyxgkhkb2pixasnb@ltop.local> (raw)
In-Reply-To: <7ff5e01d-817b-d367-dc61-2b5ceec957f5@ramsayjones.plus.com>
On Sat, Nov 16, 2019 at 12:26:15AM +0000, Ramsay Jones wrote:
> Hi Luc,
>
> Just a quick heads up (since I can't look at this much for
> a few days now ...) that the current 'master' branch, when
> applied to git, causes 8 additional warnings.
>
> I have created a cut-down version of the code, thus:
...
> ... which causes the following warnings:
>
> $ ./sparse git-noreturn.c
> git-noreturn.c:17:25: warning: incorrect type in argument 1 (different modifiers)
> git-noreturn.c:17:25: expected void ( [noreturn] *routine )( ... )
> git-noreturn.c:17:25: got void ( [noreturn] * )( ... )
> git-noreturn.c:25:76: warning: incorrect type in initializer (different modifiers)
> git-noreturn.c:25:76: expected void ( *static [toplevel] [noreturn] die_routine )( ... )
> git-noreturn.c:25:76: got void ( [noreturn] * )( ... )
> $
>
> Sorry to just dump and run ... (hopefully, the above is useful
> information - I will add the test file as an attachment).
Hi Ramsay,
Thank you very much for reporting this and, yes, the information
above is very useful.
I've looked a bit at this and all I can say for the moment is that
it's a quite intricated problem. I fact there are several problems
which interact with each other more or less subltly.
-- Luc
prev parent reply other threads:[~2019-11-16 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 0:49 [PATCH] function attributes apply to the function declaration Luc Van Oostenryck
2019-11-16 0:26 ` Ramsay Jones
2019-11-16 22:50 ` Luc Van Oostenryck [this message]
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=20191116225024.kyxgkhkb2pixasnb@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=alex.kogan@oracle.com \
--cc=john.levon@joyent.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.com \
--cc=smatch@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).