This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: followup on question about gcc compiling and linking


hopefully people will correct me ...

On Tue, Dec 13, 2005 at 09:59:27AM -0500, Robert P. J. Day wrote:
> /usr/lib/crti.o (call_gmon_start, _init, _fini)

crti.o is for function prologues
crtn.o is for function epilogues
in glibc, they are generated from the initfini.c files

> /usr/lib/gcrt1.o (_start, __gmon_start__)

code for initializing profiling/graphing routines ... see the gprof
utility from binutils for more info

> .../4.0.2/crtbegin.o (__do_global_dtors_aux)
> .../4.0.2/crtend.o (__do_global_ctors_aux)

code for initializing compiler related stuff i believe

> /usr/lib/libc_nonshared.a (__libc_csu_init, __libc_csu_fini)

the C library constructors/deconstructors

>   is there a decent write-up on all of this somewhere?  and what are
> those other crt*.o files for?

there prob is but i dont know of one ... wouldnt mind starting a little
file to doc these though ...

> p.s.  what do those occasional "S" and "T" suffixes mean on some
> object files?

S is used to indicate objects which are used with PIEs ... dunno what
T or M is for ...
-mike

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]