On Thu, Jan 7, 2016 at 7:41 PM, Toon Moene wrote:
> On 01/06/2016 07:46 PM, Toon Moene wrote:
>
>> Would it be possible to add an option -mveclibabi=glibc to cater for
>> this *for all languages*; or is this too low level (after all, the glibc
>> libmvec has code for multiple architectures). If so
On 01/06/2016 07:46 PM, Toon Moene wrote:
Would it be possible to add an option -mveclibabi=glibc to cater for
this *for all languages*; or is this too low level (after all, the glibc
libmvec has code for multiple architectures). If so, at what level
should this be implemented ?
It doesn't loo
On 01/06/2016 07:46 PM, Toon Moene wrote:
[ This is relevant for our code, because just the switch to *actual*
single precision exp/log/sin/cos implementations in glibc's libm
resulted in a decrease of the running time of our weather forecasting
code by 25 % (this was in glibc 2.16, IIR
All,
I noticed, around half a year ago, that the incredible team around glibc
found the time to implement vector math (libm) routines.
Previously, free software adherents like me were dependent on vendor
libraries via the -mveclibabi={svml|acml} (on Intel/AMD) for instance.
However, the exa
