Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Date
Msg-id 200601112103.k0BL34t21956@candle.pha.pa.us
Whole thread Raw
In response to Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
List pgsql-bugs
Tom Lane wrote:
> "F. Laupretre" <flconseil@yahoo.fr> writes:
> > In order for the check to be done correctly, we have to provide a
> > program that the compiler cannot optimize, ie where it cannot detect
> > that the call is useless, even if it is very very smart. Here is a
> > patch with such a program.
>
> I haven't got a lot of faith in your proposed patch --- with
> sufficiently aggressive optimization, the compiler might inline
> the is_f() function, no?  After looking at the modern version of
> AC_CHECK_FUNC, I'm thinking that the best answer is to make the
> finite() result affect the program's exit status.  Would you try
> this version of the check and see if it works for you?
>
> AC_TRY_LINK([#include <math.h>],
>             [return finite(1.0) ? 0 : 1;],
>             [AC_DEFINE(HAVE_FINITE, 1, [Define to 1 if you have finite().])
> AC_MSG_RESULT(yes)],
>             [AC_MSG_RESULT(no)])

Could any other configure tests fail in this way?

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol
Next
From: Tom Lane
Date:
Subject: Re: BUG #2162: Same as bug #1679 - finite() - unresolved symbol