Brown, Daniel wrote:
> Thanks for the clarification Roger, I guess it looks like I will need to
> modify the compiler settings locally then.
If you can modify the amalgamation source code, I would try updating
sqlite3IsNan() to use the standard C isnan() macro. DRH commented in
one of the
Database
Subject: Re: [sqlite] GCC -ffast-math safe version of sqlite3IsNaN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> In the process of upgrading to 3.6.1 I've run into the error on line
46
> of util.c about int sqlite3IsNaN(double x) not behaving consistently
> wit
Brown, Daniel wrote:
>Unfortunately our build system is automated and not particularly agile, it can
>be done but it would be preferred not to have to do that and to replace the
>offending function instead but I've never had to write a IsNaN test.
>
>
>
I had a look at the sourcecode for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> In the process of upgrading to 3.6.1 I've run into the error on line 46
> of util.c about int sqlite3IsNaN(double x) not behaving consistently
> with the GCC -ffast-math compiler option (which we have enabled), is
> there any
PROTECTED] On Behalf Of Michael Ruck
Sent: Tuesday, August 26, 2008 3:59 PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] GCC -ffast-math safe version of sqlite3IsNaN
Have you tried to compile the util.c/amalgamation file without -ffast-math
and
use it with your other sources
Have you tried to compile the util.c/amalgamation file without -ffast-math
and
use it with your other sources (compiled with -ffast-math)?
Mike
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von Brown, Daniel
> Gesendet: Mittwoch, 27. August
6 matches
Mail list logo
