On Thu, Mar 22, 2007 at 01:11:18PM -0400, Dave Jones wrote:
> So the good news is that this only seems to affect 0.2
> Current git doesn't segfault, but still emits lots of spew.
>
> Dave
>
> /usr/lib/gcc/powerpc64-linux/4.0.1/include/altivec.h:36:2: error: Use the "-maltivec" flag to enable PowerPC AltiVec support
> drivers/md/raid6altivec1.c:41:16: error: Expected ; at end of declaration
> drivers/md/raid6altivec1.c:41:16: error: got signed
The spew is cause by the vector extension which sparse know nothing about.
It is kind of expected.
I found a few place the kernel use "vector" as declarator. This introduce
ambiguity in expression:
(vector char) { x, x }
We look at 'vector', we can't decide it is a type or node yet. Because 'vector'
can be use as symbol. We have to look at the next token to decide if this is
cast expression or not.
Do we want to support vector in sparse?
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
