On 19 January 2016 at 18:04, Adhemerval Zanella
wrote:
> I do see some x86_64 specialized implementation being used currently
> (sysdeps/x86_64/fpu/s_{sin,cos}f.S for instance). The sincos implementations
> is still used (sysdeps/x86_64/fpu/s_sincosf.S).
>
> What you referring that glibc has dropp
On 19-01-2016 03:49, Siddhesh Poyarekar wrote:
> On 19 January 2016 at 00:06, Adhemerval Zanella
> wrote:
>> No one has posted any patch or stirred discussions about it. The complex
>> function in libm are usually coded in in C to be platform neutral, with
>> some specific function being optimi
On 19 January 2016 at 00:06, Adhemerval Zanella
wrote:
> No one has posted any patch or stirred discussions about it. The complex
> function in libm are usually coded in in C to be platform neutral, with
> some specific function being optimized (rounding, etc.). x86_64 also have
> some assembly i
Hi Virendra,
On 18-01-2016 15:54, Virendra Kumar Pathak wrote:
> Hi Linaro Toochain Group,
>
> I have few questions on glibc+libm w.r.t aarch64.
> If possible, please provide some insight, otherwise kindly redirect me to the
> concerned person/forum.
>
> 1.It seems from the community patches th
Hi Linaro Toochain Group,
I have few questions on glibc+libm w.r.t aarch64.
If possible, please provide some insight, otherwise kindly redirect me to
the concerned person/forum.
1.It seems from the community patches that ARM/Linaro is optimizing glibc
functions such as memcpy/memmove, string for
