Re: Configure enhancements

[Igor Schein <igor@txc.com>]

On Fri, Oct 18, 2002 at 02:12:45PM +0200, Bill Allombert wrote:
> On Thu, Oct 17, 2002 at 02:35:26PM -0400, Igor Schein wrote:
> > On Thu, Sep 26, 2002 at 06:34:31PM +0200, Bill Allombert wrote:
> > > On Wed, Sep 25, 2002 at 01:15:07PM -0400, Igor Schein wrote:
> > > > Hi,
> > > > 
> > > > I think there should be a provision in Configure to choose 32-
> > > > or 64-bit target, if the platform allows.  Here's a summary for dual
> > > > platforms:
> > > > 
> > > > 1) Solaris@sparc cc - need to specify -xarch=v9
> > > > 2) Solaris@sparc gcc - starting with version 3.1 supports dual target - need
> > > > to specify -m64
> > > > 3) HPUX@hppa cc - need to specify +DA2.0w
> > > > 4) HPUX@hppa gcc - doesn't support dual target, so autodetection works
> > > > fine.
> > > > 
> > > > I don't have access to IRIX anymore, but as of 4+ years ago, one needed
> > > > to use -64 for 64bit, -n32 for 32bit.
> > > 
> > > The simplest is to do
> > > CC="cc -xarch=v9" ./Configure
> > > and every will work automatically.
> > 
> > Not really, because default optimization flag for Sun compiler is
> > -fast, which cancels -xarch=v9, so I have to manually add -xarch=v9
> > after -fast in dft file.  I find it unnecessary.  Maybe we could add
> > -32/-64 flags to Configure to avoid manual labor?
> 
> That a different problem. What does -fast ?

-fast is a Sun Compiler macro, similar to Tru64, which expands into a
bunch of optimizations, including -xarch=native.  So if -fast gets
appended to cc -xarch=v9, -xarch=native takes priority over -xarch=v9.

Igor