[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: gcc4_0 screwed...



> color.c:498: error: invalid lvalue in increment
> color.c:499: error: invalid lvalue in increment
> make[3]: *** [color.lo] Error 1
> 
>   for (x=0; x < (width / 4); x++) {
>     n1  = *(((unsigned int *) src1)++);
>     n2  = *(((unsigned int *) src2)++);
>     n3  = (n1 & 0xFF00FF00) >> 8;
>     n4  = (n2 & 0xFF00FF00) >> 8;
>     n1 &= 0x00FF00FF;
>     n2 &= 0x00FF00FF;
> 
> and that doesn't seem to be Âlazy codeÂ...

no it's just plain broken and invalid code; gcc won't be "fixed" to
accept this invalid code in the future..

> RTjpeg.c:101: error: invalid lvalue in assignment

>  (uint8_t)strm[0]=(uint8_t)(data[RTjpeg_ZZ[0]]>254) ? 254:((data
> [RTjpeg_ZZ[0]]<0)?0:data[RTjpeg_ZZ[0]]);

eh what does it mean to cast that strm[0] ???????
I think that's invalid code too

> I don't think that upgrading is a bad idea, but I do think that

I think you might just need a binutils upgrade just as well

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]