Warning message when using sparse
in [Kernel]
|
Prev: Compat-wireless for 2.6.32.y, 2.6.33.y, 2.6.34.y and 2.6.35-rc updated
Next: linux-next: manual merge of the wireless tree with the net tree
From: Larry Finger on 8 Jul 2010 22:00 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 Larry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jiri Slaby on 9 Jul 2010 16:50 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Larry Finger on 9 Jul 2010 17:30 Obviously, I pulled the wrong git tree. I got the one from the wiki. When I built the one from the kernel.org tree, all is well. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jiri Slaby on 9 Jul 2010 17:30 On 07/09/2010 11:22 PM, Larry Finger wrote: > Obviously, I pulled the wrong git tree. I got the one from the wiki. > When I built the one from the kernel.org tree, all is well. Both are from kernel.org. But the one I sent is a Chris'es "fork" with my and other fixes. -- js -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christopher Li on 9 Jul 2010 18:10
On Fri, Jul 9, 2010 at 2:26 PM, Jiri Slaby <jirislaby(a)gmail.com> wrote: > On 07/09/2010 11:22 PM, Larry Finger wrote: >> Obviously, I pulled the wrong git tree. I got the one from the wiki. >> When I built the one from the kernel.org tree, all is well. > > Both are from kernel.org. But the one I sent is a Chris'es "fork" with > my and other fixes. > Yes, you caught me slacking off. It is time to cut a new release and flush all the bits into the official tree. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |