Question about the highly optimized aspects of libc implementation
Mon Dec 4 08:12:00 GMT 2017
On 4 December 2017 at 06:45, Will Hawkins <firstname.lastname@example.org> wrote:
> Are there any places where, I know this sounds crazy, but functions
> are invoked with push/jump (or straight jumps) because, for instance
> they are tail calls or somehow the return address is known statically?
That's not uncommon - ancillary memcpy functions (such as mempcpy,
__memcpy_chk) get implemented that way and I'm sure there are other
such routines in there.
More information about the Libc-help