This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: isinf
- From: Andreas Schwab <schwab at suse dot de>
- To: Michael Veksler <VEKSLER at il dot ibm dot com>
- Cc: Eric Botcazou <ebotcazou at libertysurf dot fr>, gcc at gcc dot gnu dot org,Hiroshi Fujishima <hiroshi dot fujishima at gmail dot com>,Joe Buck <Joe dot Buck at synopsys dot com>
- Date: Thu, 14 Jul 2005 10:59:06 +0200
- Subject: Re: isinf
- References: <OFC182F25F.CB9B8299-ON4325703E.002AD458-4325703E.002BA172@il.ibm.com>
Michael Veksler <VEKSLER@il.ibm.com> writes:
> Maybe there is a simpler way? For example:
>
> volatile int a;
> volatile double b;
> int main ()
> {
> a = isinf (b);
> return 0;
> }
>
> This way the compiler must not assume anything about 'b',
> making it impossible to optimizes the call to isinf.
Why not just use AC_HAVE_FUNCS(isinf)? IIUC this is part of a configure
script, although whether it is autoconf generated is not clear so far.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."