In my OpenBSD/amd64 system, the code becomes
    if (0)
        outname.on_valu &= ~(((0xFFFFFFFF)<<32)<<32);
The 0xFFFFFFFF is a 32-bit int, so the left shift by 32 is out of
range and causes the gcc warning.
The intent might be to clear any sign-extended bits, if the assignment
outname.on_valu = valu did sign extension.  Old C had no unsigned
long, so .on_valu would have been long.  The code is obsolete because
h/out.h now declares .on_valu as uint32_t.
		
	
					 | 
			||
|---|---|---|
| .. | ||
| build.lua | ||
| comm0.h | ||
| comm1.h | ||
| comm2.y | ||
| comm3.c | ||
| comm4.c | ||
| comm5.c | ||
| comm6.c | ||
| comm7.c | ||
| comm8.c | ||
| proto.make | ||