This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug string/18858] _HAVE_STRING_ARCH_xxx aren't defined for i386 nor x86_64
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 07 Mar 2016 05:28:17 +0000
- Subject: [Bug string/18858] _HAVE_STRING_ARCH_xxx aren't defined for i386 nor x86_64
- Auto-submitted: auto-generated
- References: <bug-18858-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18858
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to H.J. Lu from comment #4)
> (In reply to Carlos O'Donell from comment #3)
> > (In reply to joseph@codesourcery.com from comment #1)
> > > I think _HAVE_STRING_ARCH_mempcpy is expected to be defined only when
> > > mempcpy is an alternative entry point to memcpy, as otherwise using
> > > mempcpy will increase cache usage and so inlining the expansion in terms
> > > of memcpy is expected to be more efficient.
> >
> > I think this needs to be backed up by some more performance measurements by
> > Intel.
>
> Did we have inline mempcpy performance measurements on Intel machines when
> the change was made?
Yes, Ondrej ran some numbers:
https://sourceware.org/ml/libc-alpha/2015-05/msg00575.html
--
You are receiving this mail because:
You are on the CC list for the bug.