From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Lots of "error: multiple storage classes" warnings on the Linux kernel
Date: Fri, 20 Aug 2010 10:37:39 +0200 [thread overview]
Message-ID: <1282293459.10440.223.camel@thorin> (raw)
In-Reply-To: <20100819192656.GA19303@merkur.ravnborg.org>
On Don, 2010-08-19 at 21:26 +0200, Sam Ravnborg wrote:
> On Thu, Aug 19, 2010 at 02:53:12PM +0200, Bernd Petrovitsch wrote:
[...]
> > While investigating something completely different, I noticed lots of
> > "error: multiple storage classes" warnings, e.g.
> > ---- snip ----
> > CHECK security/keys/keyring.c
> > include/linux/sched.h:831:12: error: multiple storage classes: extern weak
> > security/keys/keyring.c:75:1: error: multiple storage classes: extern weak
> > security/keys/keyring.c:471:1: error: multiple storage classes: extern weak
> > security/keys/keyring.c:899:1: error: multiple storage classes: extern weak
> > security/keys/keyring.c:974:1: error: multiple storage classes: extern weak
> > security/keys/keyring.c:1033:1: error: multiple storage classes: extern weak
> > ---- snip ----
> > [ The ": extern weak" is from me to see which are actually set. ]
> >
> > Is this warning correct that way (and the source should be fixed) or is
> > the warning in that wrong?
>
> Can you cook up a small code snippet that
> exhibit this without all the kernel macros etc?
Of course.
> This would make it easier for the sparse folks to understand.
---- snip ----
{341}echo 'extern int __attribute__((weak)) foobar(void);' | sparse -f -
-:1:12: error: multiple storage classes: extern weak
---- snip ----
is a minimal example shows that.
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
prev parent reply other threads:[~2010-08-20 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 12:53 Lots of "error: multiple storage classes" warnings on the Linux kernel Bernd Petrovitsch
2010-08-19 19:26 ` Sam Ravnborg
2010-08-20 8:37 ` Bernd Petrovitsch [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=1282293459.10440.223.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=linux-sparse@vger.kernel.org \
--cc=sam@ravnborg.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).