This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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]

Re: regress and -m64

From: Bradley Lucier <lucier at math dot purdue dot edu>
To: howarth at bromo dot msbb dot uc dot edu (Jack Howarth)
Cc: Bradley Lucier <lucier at math dot purdue dot edu>, gcc at gcc dot gnu dot org
Date: Mon, 28 Aug 2006 13:27:47 -0400
Subject: Re: regress and -m64
References: <20060828161055.4CA96110019@bromo.msbb.uc.edu>

On Aug 28, 2006, at 12:10 PM, Jack Howarth wrote:

   Why don't you try a normal multi-lib build without any
extra flags.

What extra flags? The configure command is

../configure --prefix=/pkgs/gcc-mainline --with-gmp=/opt/local/ -- with-mpfr=/opt/local/

which is totally generic (one needs to specify gmp and mpfr libraries to get fortran to build).

I build with

make -j 4 bootstrap >& build.log

which is completely generic.

Or do you mean the -mcpu=970 in the test options?

Oh, when you do your make check from the top level of the
build directory use this form of the command...
make -k check RUNTESTFLAGS='--target_board="unix{,-m64}"'

my make check is

make -k -j 8 check RUNTESTFLAGS="--target_board 'unix{-mcpu=970/-m64}'"

I don't see any reason to check the 32-bit stuff that the regression checker checks at least once a day.

Brad

Follow-Ups:
- Re: regress and -m64
  - From: Bradley Lucier

References:
- Re: regress and -m64
  - From: Jack Howarth

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