[prev in list] [next in list] [prev in thread] [next in thread] 

List:       glibc-help
Subject:    libc_hidden & weak_alias mechanism in vfork/clone/..
From:       mail () waldemar-brodkorb ! de (Waldemar Brodkorb)
Date:       2018-06-01 18:01:00
Message-ID: 20180601180127.GY2438 () waldemar-brodkorb ! de
[Download RAW message or body]

Hi Carlos,
Carlos O'Donell wrote,

> On 05/30/2018 07:30 PM, Waldemar Brodkorb wrote:
> > Hello glibc hackers,
> > 
> > I would like to understand why GNU C Library is using a lot of weak
> > aliases for C library functions like vfork or clone.
> > 
> > What is the reason for it?
> > 
> > Or in this case the assembly function name is __libc_vfork and
> > __vfork and vfork is somehow involved.
> > https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/riscv/vfork.S;h=6c53e93a928d736be73161954fd83bdb0672fd4f;hb=HEAD
> > 
> 
> Does this answer your question?
> 
> https://sourceware.org/glibc/wiki/Style_and_Conventions#Double-underscore_names_for_public_API_functions
> 

Thanks, mostly.
Does this mean that in vfork.S all two conventions are used in
combination to avoid namespace pollution and gather better
performance by avoiding internal function calls via PLT?

There are three symbols involved:
__libc_vfork()
__vfork()
vfork()

best regards
 Waldemar


[prev in list] [next in list] [prev in thread] [next in thread]