X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Message-ID: <4C492114.4030200@iki.fi>
Date: Fri, 23 Jul 2010 07:56:52 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1
MIME-Version: 1.0
To: djgpp AT delorie DOT com
CC: Allan <mu8ja0i AT earthlink DOT net>
Subject: Re: ANNOUNCE: DJGPP port of GMP-5.0.1
References: <201007202032 DOT o6KKWEKS015930 AT delorie DOT com> <88GdnSjfOr77k9TRnZ2dnUVZ_h6dnZ2d AT earthlink DOT com>
In-Reply-To: <88GdnSjfOr77k9TRnZ2dnUVZ_h6dnZ2d@earthlink.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

  07/23/2010 06:37 AM, Allan kirjoitti:
>
> Thanks a lot. In the gmp documentation it encourages you to build for 
> the actual processor it will run on. For example I have a Pentium 4 
> processor so I reconfigured using `--build=pentium4-pc-msdosdjgpp'. 
> Then as you already know in `gmp.h' the result will be 
> `-mtune=pentium4 -march=pentium4' and when you compile mpfr and mpc it 
> uses these values in CFLAGS. However I overkill and reconfigure both 
> mpfr and mpc sources anyway. All tests passed using both GCC 4.4.2 and 
> GCC 4.4.4.

I don't think it is necessary unless You want to optimize executable 
size to be as small as possible. I used configure option --enable-fat 
when configured GMP.

  See
     http://gmplib.org/manual/Build-Options.html
  for details.

  As result GMP is expected to choose fastest code for actual processor 
at runtime. Of course there could still be some small gain in speed if 
You configure for pentium4-pc-msdosdjgpp and run only on that. I would 
expect such difference to be however very small and also to diminish 
when values grows longer.

Andris