Vincent Lefevre writes:
But shouldn't it be the goal of the compiler to generate the fastest
code for the target?
Yeah, that's a good idea. :-)
This might require more analysis than what we can expect from the
compiler, as (x >> 1) >> c is not the same thing as x >> (1+c) (at least
not if
Taner Sener writes:
checking how to define a 32-bit word... configure: error: cannot determine
how to define a 32-bit word
Well, how do you define a 32-bit word in this assembly variant?
(You might want to compile something like "int foo = 0xdeadbeef;" into
assembly and check the output to
