Re: Question about use of sizetype in i386.c declared in stor-layout.c

4 msg	Rebuild GCC 4.2
1 msg	inappropriate disclaimers (Was: Re: Installing ...
1 msg	[tuples] Mainline merge (@126872)
2 msg	bootstrap broken on trunk r126866
1 msg	BB_RTL flag assertion on basic_block-s when dum...
15 msg	GCC with formal testing docs
3 msg	MacOS X Ada patches?
10 msg	paranoia on PowerPC
1 msg	gcc-4.1-20070723 is now available
4 msg	-Warray-bounds issue
4 msg	Compiler support for write barrier insertion ?

Question about use of sizetype in i386.c declar...
\ Kai Tietz (23 Jul 2007)
. \ Andreas Schwab (23 Jul 2007)
. . \ Kai Tietz (23 Jul 2007)
. . . \ Andreas Schwab (23 Jul 2007)

9 msg	debugging info considered harmful to lto.
2 msg	GCC for Symbian
4 msg	Refactoring tool
6 msg	assembly: control flow graphs (and optimizations)
5 msg	top-level configure
4 msg	GCC 4.2 branch open
2 msg	[Fwd: Re: Problem compiling NONMEM with mingw g...
1 msg	gcc-4.3-20070720 is now available

Subject:	Re: Question about use of sizetype in i386.c declared in stor-layout.c
Group:	Gcc
From:	Andreas Schwab
Date:	23 Jul 2007

Kai Tietz <Kai.Tietz> writes:

> Hmm... Ok, but why in stor-layout.c in initialize_sizetypes () SImode is
> explicit used ?

See stor-layout.c:set_sizetype and c-common.c:c_common_nodes_and_builtins.

Andreas.

--
Andreas Schwab, SuSE Labs, schwab
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."