On 3/31/18, Philip Prindeville <philipp_subx_at_redfish-solutions.com> wrote:

> Couple of questions. One is a broader question about tweaking the API so
> that it uses fewer “doubles” for get curl_easy_getinfo() call, in particular
> using fixed point since you might be running on a platform such as an
> embedded router with a MIPS-32 or ARMv6 CPU which doesn’t have
> floating-point… but is reasonably capable of 64-bit operations (shifting,
> adding, subtracting, etc).

Does your toolchain not support software floating-point? I'm curious
because I work with an armv5 that does have hardware floating point
(if only we could get our hardware vendor to give us a toolchain with
hard-float…).

> So we might want to express times as uint64_t’s as (tv.tv_sec * 1000000) +
> tv.usec.

If we're allowing for platforms without any kind of floating-point
support, should we also allow for platforms that don't support 64-bit
ints?

Perhaps we could copy the local system's struct timespec
<http://en.cppreference.com/w/c/chrono/timespec>?

Harold

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-04-02