On Fri, May 24 2019, Steven Munroe wrote: > In the current state, these libraries are only required for unit tests, but > could be used for applications that need those constant values.
OK, if it can be useful for applications, than it's probably better to distribute it, right away. > [...] So the current build is looking ahead to a configuration > that provides a space vs performance trade-off. > > Fro example muludq < > https://munroesj52.github.io/vec__int128__ppc_8h.html#aee5c5b2998ef105b4c6f39739748ffa8> > where the POWER8 implementation runs 132 bytes. It is even bigger for > POWER7 and only 80 bytes for POWER9. > > The threshold for in-lining is a matter of some debate. > > So I expect that eventually pveclib will need the option to move some > operations for some -mcpu= values to use library calls. And some > performance oriented applications will want to inline every thing > regardless. OK. All good points to ship the shared library. > For now I want to make pveclib available as-is to users. Then if someone > complains about code size we can add the controls/configuration to adjust. As-is sounds good to me. :) With this information, I think the package is ready to be submitted to the Debian Archive. However, since we are under the freeze, that might take a while, but I'll get the process started. Thanks, Steve! Cheers, Gabriel.
