This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mknumeric_limits
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: mknumeric_limits
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 19 Feb 2001 19:29:27 +0100
- Cc: Jeffrey A Law <law at redhat dot com>, bkoz at redhat dot com, gcc at gcc dot gnu dot org, gdr at codesourcery dot com
- Organization: CodeSourcery, LLC
- References: <26137.982602104@slagheap.cygnus.com> <20010219133055.A9709@disaster.jaj.com>
Phil Edwards <pedwards@disaster.jaj.com> writes:
| I trust Benjamin and Gabriel will correct any mistakes I'm about to make. :-)
|
| On Mon, Feb 19, 2001 at 10:01:44AM -0700, Jeffrey A Law wrote:
| > First, it seems rather odd to be using "uname" like that, unless this code
| > is supposed to be run on the build machine.
| >
| > Second, by using uname instead of a triplet, we lose the ability to
| > select behavior on the triplet. This is important when you consider
| > systems like the PA which have two completely different toolchains that
| > can not interoperate with each other.
|
| That fragment predates just about everything else, such as configure.host
| and configure.target, which are recent and use triplets.
Phil is right, mknumeric_limits goes back to early 1999 when we were
doing things the hard way.
| ... mknumeric_limits
| could be changed to use those, or maybe could call the generated tests_flags
| script. (Gaby? Sanity check?)
Any patch is welcome.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com