--nfp configure option still alive?

--nfp configure option still alive?

[Lior Balkohen]

is the --nfp configure option still alive for targets which do not
have an fpu or we can omit this option also for targets without fpu?

Re: --nfp configure option still alive?

[Nick Clifton]

Hi Lior,

> is the --nfp configure option still alive for targets which do not
> have an fpu or we can omit this option also for targets without fpu?

The answer is probably "no", but in order to be sure, can say for which 
target you want to configure without fpu support ?

Cheers
   Nick

Re: --nfp configure option still alive?

[Mike Frysinger]

On Friday 30 September 2005 10:50 am, Nick Clifton wrote:
> Hi Lior,
>
> > is the --nfp configure option still alive for targets which do not
> > have an fpu or we can omit this option also for targets without fpu?
>
> The answer is probably "no", but in order to be sure, can say for which
> target you want to configure without fpu support ?

i glanced through the binutils sources recently and couldnt actually find 
anywhere that the option was utilized ...

--nfp sets the 'with_fp' variable to 'no' in all the configure scripts, but 
'with_fp' doesnt seem to be checked at any point

ive been doing softfloat arm recently and havent had to do anything different 
with binutils to have it work properly compared to hardfloat arm ...
-mike

Re: --nfp configure option still alive?

[Nick Clifton]

Hi Lior,

> powerpc-linux (IBM PowerPC 405 Embedded Core with no FPU). I used to
> build gcc with --with-float=soft and --with-cpu=405 and everthing is
> ok, but I'm not sure about passing a --nfp to the configure script of
> binutils, and I just read in this script "--nfp is obsolete; use
> --without-fp".
> 
> I'm confused now.

Right, the answer is "no the --nfp switch is not used by binutils for 
the PowerPC target (any CPU)".  In fact looking at the GCC configure 
files as well, it appears that this switch is not used there either.

The reason for the "--nfp is obsolete" comment being present in the 
configure files is that it is added there automatically when then 
configure file is generated from the configure.in file.  The autoconf 
program probably does not need to insert this comment any more (or the 
lines that handle --nfp) but it is safest to leave them in case someone 
has a very old configure command line lying around somewhere.

Cheers
   Nick