yeah, i already tried various variants earlier today so i really didnt trythat hard with yours. (and i pointed out this mistake in the previous mail)

> That said, with that fixed, there's still something wrong. It does seem > like gcc has some very odd interaction there with __builtin_constant_p. > Odd.

yeah. I tried various integer arithmetic expressions (which the array trickrelies on) and it didnt work as expected - it's always zero. It only makesa difference when used in comparisons. (and that's where the kernel uses__builtin_constant_p quite heavily, and it works fine there.)