Kenneth Zadeck writes:
> I would like to see some comment to the effect that this to allow
> inlining for the common case for widest int and offset int without
> inlining the uncommon case for regular wide-int.
OK, how about:
/* If the precision is known at compile time to be greater than
I would like to see some comment to the effect that this to allow
inlining for the common case for widest int and offset int without
inlining the uncommon case for regular wide-int.
On 11/28/2013 12:38 PM, Richard Sandiford wrote:
Currently add and sub have no fast path for offset_int and w
Currently add and sub have no fast path for offset_int and widest_int,
they just call the out-of-line version. This patch handles the
single-HWI cases inline. At least on x86_64, this only adds one branch
per call; the fast path itself is straight-line code.
On the same fold-const.ii testcase, t
