On Wed, 2010-05-05 at 10:42 -0700, H.J. Lu wrote: > On Wed, May 5, 2010 at 10:18 AM, Steve Ellcey <s...@cup.hp.com> wrote: > > > > I was wondering if anyone has built GCC using a CFLAGS (and CXXFLAGS) > > setting > > that causes GCC to generate code that is not compatibile with the default > > GCC output. Basically, I am building GCC on ia64-hp-hpux11.31 where I set > > CFLAGS and CXXFLAGS to "-mlp64" to generate 64 bit code instead of the > > default 32 bit code. During the build libiberty is built in 64 bit mode but > > then the object files that go into genmodes (genmodes.o, errors.o, etc) are > > compiled without using CFLAGS and the link of genmodes fails because > > genmodes.o and errors.o are in 32 bit mode and libiberty is in 64 bit mode. > > > > I am using > > # CC="gcc -m32" CXX="g++ -m32" ...../configure .... > > to bootstrap 32bit gcc on 64bit Linux.
I am curious, if you do this does the resulting compiler generate 32 bit code by default? And I assume that if you don't specify CC and CXX with the -m32 flags then the compiler generates 64 bit code by default, right? Steve Ellcey s...@cup.hp.com
