From: Jiri Slaby <jirislaby@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Warning message when using sparse
Date: Fri, 09 Jul 2010 22:47:21 +0200 [thread overview]
Message-ID: <4C378AD9.1070602@gmail.com> (raw)
In-Reply-To: <4C3680D1.5070601@lwfinger.net>
On 07/09/2010 03:52 AM, Larry Finger wrote:
> On recent kernels, sparse reports the following message for every source
> file that is processed. The warning does not seem to affect the results.
> I'm not sure when the problem started, but I think it was with 2.6.35-rc1.
>
>
> CHECK drivers/staging/rtl8712/rtl871x_rf.c
> /home/finger/linux-2.6/arch/x86/include/asm/cpufeature.h:297:21: error:
> Expected ( after asm
> /home/finger/linux-2.6/arch/x86/include/asm/cpufeature.h:297:21: error:
> got goto
>
Yeah, I posted a support for that already:
http://git.kernel.org/?p=devel/sparse/chrisl/sparse.git;a=summary
The patch is not 100% correct, it doesn't support asm volatile goto and
similar.
What distro you use? I will fix it in opensuse (which provide gcc 4.5
already), if there will be no new release of sparse.
regards,
--
js
next prev parent reply other threads:[~2010-07-09 20:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 1:52 Warning message when using sparse Larry Finger
2010-07-09 20:47 ` Jiri Slaby [this message]
2010-07-09 21:22 ` Larry Finger
2010-07-09 21:26 ` Jiri Slaby
2010-07-09 22:04 ` Christopher Li
2010-07-10 8:39 ` [PATCH 1/2] parser: fix and simplify support of asm goto Jiri Slaby
2010-07-10 18:36 ` Chris Li
2010-07-10 18:36 ` Chris Li
2010-07-10 8:39 ` [PATCH 2/2] parser: define __builtin_unreachable Jiri Slaby
2010-07-10 9:07 ` Josh Triplett
2010-07-13 7:52 ` Chris Li
2010-07-13 7:52 ` Chris Li
2010-07-13 18:12 ` Josh Triplett
2010-07-13 18:49 ` Chris Li
2010-07-13 18:49 ` Chris Li
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=4C378AD9.1070602@gmail.com \
--to=jirislaby@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.