Searched hist:"8009 c566df29a567fbd1ec08b901fda938ecc5ef" (Results 1 – 2 of 2) sorted by relevance
| /freebsd/lib/libc/i386/string/ |
| H A D | memmove.S | diff 8009c566df29a567fbd1ec08b901fda938ecc5ef Sun Apr 20 14:46:12 CEST 1997 Bruce Evans <bde@FreeBSD.org> Use separate routines for memmove() and memcpy(). This lets me drop
the (buggy) support for alternative entry points. ALTENTRY() was only
used for memmove(). Optimizing for space was particularly silly because
memcpy() is rarely used (gcc normally inlines it).
Obtained from: NetBSD
diff 8009c566df29a567fbd1ec08b901fda938ecc5ef Sun Apr 20 14:46:12 CEST 1997 Bruce Evans <bde@FreeBSD.org> Use separate routines for memmove() and memcpy(). This lets me drop
the (buggy) support for alternative entry points. ALTENTRY() was only
used for memmove(). Optimizing for space was particularly silly because
memcpy() is rarely used (gcc normally inlines it).
Obtained from: NetBSD
|
| H A D | Makefile.inc | diff 8009c566df29a567fbd1ec08b901fda938ecc5ef Sun Apr 20 14:46:12 CEST 1997 Bruce Evans <bde@FreeBSD.org> Use separate routines for memmove() and memcpy(). This lets me drop
the (buggy) support for alternative entry points. ALTENTRY() was only
used for memmove(). Optimizing for space was particularly silly because
memcpy() is rarely used (gcc normally inlines it).
Obtained from: NetBSD
diff 8009c566df29a567fbd1ec08b901fda938ecc5ef Sun Apr 20 14:46:12 CEST 1997 Bruce Evans <bde@FreeBSD.org> Use separate routines for memmove() and memcpy(). This lets me drop
the (buggy) support for alternative entry points. ALTENTRY() was only
used for memmove(). Optimizing for space was particularly silly because
memcpy() is rarely used (gcc normally inlines it).
Obtained from: NetBSD
|