🚀 go-pugleaf

A suggestion for inline_able-function evaluation criterion:

   Upon several occasions, I have given functions the inline attribute
   and have been informed that they are too large to be made inline.
   However, if they had been made inline, the combination of copy
   propagation and dead code elimination would have reduced the size
   of the resulting version of the function by a factor as large as six
   in one case.

   If it is essential that explicitly declared inline functions not be
   larger than some particular size, is it possible to calculate code size
   after dead code elimination?

   More realistically, might it be possible to manually override the
   default limit on the size of functions that may be made inline?
   Or maybe, impose no size restriction for functions that are explicitly
   declared inline?

   Some good examples are the manually unrolled BLAS from LINPACK,
   especially scopy().

---
Jim Meyering      meyering@cs.utexas.edu