This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Saturday 12 January 2008, Metuki Sabhe wrote: > On Jan 11, 2008 9:49 PM, Mike Frysinger <vapier@gentoo.org> wrote: > > On Friday 11 January 2008, Metuki Sabhe wrote: > > > what is the purpose of libc_pic.a ? > > > > it is a static archive of libc that is completely built as PIC > > > > > can you give an example of application that uses it ? > > > > it doesnt get installed so it only gets used by the glibc build system > > thank you Mike. I was wondering about libc_pic.a while looking for the > definition of __umoddi3(). Before I realized that function belongs to > libgcc, I found > it also in libc_pic.a... i doubt __umoddi3 is actually defined in libc_pic.a. more likely libc_pic.a has an undefined reference to __umoddi3. > I just wonder now whether libgcc can issue any system calls ? Now I really > think not. i think your definition of "system calls" is kind of vague. gcc most likely will never actually execute a system call directly, but rather go through the C library. there's no rules that say libgcc.a cannot call functions in the C library which cannot make system calls. in fact, objects in libgcc.a most likely will contain references to functions in the C library which will execute a system call. then again, i dont see why any of this matters whatsoever. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |