On 10/8/18 18:55, Federico Schwindt wrote:
>
> It might be a bit earlier but personally knowing the where and when for the
> next VDD will help immensely to sort the time off at work and whatnot,
> especially the date.
>
> Do we have any ideas or suggestions?
I thought that the time frame
In message
, Federico
Schwindt writes:
>It might be a bit earlier but personally knowing the where and when for the
>next VDD will help immensely to sort the time off at work and whatnot,
>especially the date.
>
>Do we have any ideas or suggestions?
I've been wanting to visit London
Hey,
It might be a bit earlier but personally knowing the where and when for the
next VDD will help immensely to sort the time off at work and whatnot,
especially the date.
Do we have any ideas or suggestions?
Best.
___
varnish-dev mailing list
> So now the question is how this looks for other platforms. @All, Please send
> your results!
$ ./double
real: 0.004972s / 10 = 49.715042ns - tst val 153899435413393.562500
mono: 0.003554s / 10 = 35.541058ns - tst val 1075376231.264834
printf %.6f: 0.059387s / 10 = 593.865160ns - tst
In message <6e3db4b7-5817-4c60-8c20-f4dce1ebf...@schokola.de>, Nils Goroll
writes:
>> printf("%ju.%06ju",
>> (uint64_t)floor(foo),
>> (uint64_t)floor((foo*1e6)) % 100UL);
>
>nice trick. On Linux, this gets us down to the same order of magnitude as a
> printf("%ju.%06ju",
> (uint64_t)floor(foo),
> (uint64_t)floor((foo*1e6)) % 100UL);
nice trick. On Linux, this gets us down to the same order of magnitude as a
%lu.%06lu with uint64_t
On SmartOS the gain is not that significant, but we knew this before from
