tune&fat: run-time vs. compile-time constant thresholds

[bodrato at mail.dm.unipi.it]

Ciao,

Il Ven, 27 Aprile 2012 12:47 pm, Torbjorn Granlund ha scritto:
> bodrato at mail.dm.unipi.it writes:

>   #define ABOVE_THRESHOLD(size,thresh)					\
>     ((thresh) == 0							\
>      || ((thresh) != MP_SIZE_T_MAX					\
>          && (size) >= (thresh)))
>
>   Most of this code is disabled #if TUNE_PROGRAM_BUILD, but compiled for
>   fat-builds...
>
> With consequences not completely understood...

The consequence is: that ABOVE_THRESHOLD compiles in 6 branches, instead
of one or two...

> Improving the state of fat builds is important.  There are several
> things to improve, perhaps your effort addresses some of these?

> 4. In a shared lib fat build, don't do too many indirections (via our
>    tables addressed via GOT, with entries pointing to PLT entries...).

Probably, this one. I'll experiment.

Regards,
m

-- 
http://bodrato.it/papers/