gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ✘gpsd .23.2~rc1


From: Gary E. Miller
Subject: Re: ✘gpsd .23.2~rc1
Date: Tue, 12 Apr 2022 21:25:24 -0700

Yo Hal!

On Tue, 12 Apr 2022 21:14:56 -0700
Hal Murray <halmurray@sonic.net> wrote:

> gem@rellim.com said:
> > When you start gpsd with -D 3, do you see a message like this at
> > the top:   
> 
> gpsd:WARN: This system has a 32-bit time_t.  This gpsd will fail at 
> 2038-01-19T03:14:07Z.

You have other issues...

> gpsd:WARN: FLT_EVAL_METHOD is 2, s/b 0

THat is what Fred was saying.  Non standard floating point

The non-standard part is that it uses long doubles in some places,
instead of doubles, for speed.  After this release, it might be worth
converting gpsd to use long doubles instead of doubles.

That side steps that preventing "excess precision" may slow things down.

> Checking if compiler accepts --disable-excess-fp-precision... no

That is gcc only, you are on clang.

> Checking if compiler accepts -fexcess-precision=standard... yes

Confirming you have clang.  And that command line option is supposed to
fix the FLT_EVAL_METHOD, but there are a few known holes in the fix.
That you found.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

Attachment: pgpNa9BQaE_nA.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]