GCC compile models -- theory of operation?

1 msg	Choosing the right TLS access model
1 msg	Custom __attribute__ like functionality
9 msg	poor optimisation case
3 msg	Bugzilla host/build/target triplet fields too s...
1 msg	section-anchors support for darwin?
1 msg	gcc-4.3-20070803 is now available
1 msg	Link start address
12 msg	ARM constant folding bug?
2 msg	vect failures at -m64 on darwin
8 msg	[CFG] what are class 3 edges ?

GCC compile models -- theory of operation?
\ Jonathan S. Shapiro (3 Aug 2007)
. \ Dave Korn (3 Aug 2007)
. . \ Jonathan S. Shapiro (3 Aug 2007)
. . . \ Dave Korn (3 Aug 2007)
. \ Daniel Jacobowitz (3 Aug 2007)
. . \ Jonathan S. Shapiro (3 Aug 2007)
. . . \ Daniel Jacobowitz (3 Aug 2007)
. . . \ Ian Lance Taylor (3 Aug 2007)
. . . . \ Jonathan S. Shapiro (3 Aug 2007)
. . . . . \ Ian Lance Taylor (3 Aug 2007)

2 msg	New download mirror
4 msg	C++ frontend can not handle vector pointer cons...
1 msg	Summary of the BOF regarding the general policy...
1 msg	Megtaláltam az oldalt
6 msg	missing libtool sources?
2 msg	printing cfg
2 msg	Re: [tuples] heads up. you need to specify --en...
1 msg	The Linux binutils 2.17.50.0.18 is released
17 msg	ICE on valid code, cse related

Subject:	GCC compile models -- theory of operation?
Group:	Gcc
From:	Jonathan S. Shapiro
Date:	3 Aug 2007

We're targeting a new OS with GCC. I've done some of these before, but
I've run into one issue I don't recognize, and a second that I have
obviously messed up. I have looked at "Using and Porting" and "GCC
Internals". The answers may be there, but I did not find them --
pointers welcome.

1. Versions of crtbegin

There are three versions of crtbegin: crtbegin.o, crtbeginS.o,
crtbeginT.o. 'S' is for shared/PIE -- I understand about that. Can
somebody explain what the distinction is between crtbeginT.o and
crtbegin.o?

2. Is there a simple way to configure the compiler so that the default
compilation model (in the absence of command-line directives) is
--static? If not, which of the various specfile macros need to be
updated? I know how to write specfile lines, I just want to make sure
that I don't miss one somewhere.

3. At least on i386, there are GOT sections appearing in
crt{begin,end}.o and libgcc.a. Our target does not have any dynamic
linking/loading support AT ALL. Are these sections fully resolved after
link time?

Thanks

Jonathan Shapiro