Sent from my iPhone
> On Oct 6, 2018, at 5:43 PM, Daniel Eischen wrote:
>
>
>> On Oct 6, 2018, at 3:00 PM, Mike Crowe wrote:
>>
>> Thank you for your detailed responses and patch links. I'm sorry it's taken
>> me so long to respond. I
> On Oct 8, 2018, at 1:43 PM, enh wrote:
>
>> On Sat, Oct 6, 2018 at 12:09 PM Mike Crowe
>> wrote:
>>
>>> On Wednesday 12 September 2018 at 13:47:59 -0700, Tom Cherry wrote:
On Wed, Sep 12, 2018 at 11:56 AM Mike Crowe
wrote:
>
> We (libc team for Android) have observed t
> On Oct 27, 2018, at 12:14 PM, Mike Crowe wrote:
>
> On Tue, Oct 9, 2018 at 6:19 AM Mike Crowe wrote:
>>> So, my favourite solution is to invent an equivalent of
>>> pthread_cond_timedwait that accepts a clockid_t since it feels more
>>> future-proof, but adding the Android pthread_cond_timed
> On Oct 27, 2018, at 4:13 PM, Mike Crowe wrote:
>
>> On Saturday 27 October 2018 at 15:26:07 -0400, Daniel Eischen wrote:
>>
>>> On Oct 27, 2018, at 12:14 PM, Mike Crowe
>>> wrote:
>>> Looking through POSIX Base Specifications Issue 7, I
>&g
> On Nov 4, 2018, at 5:32 AM, Mike Crowe wrote:
>
> * The problem:
>
> POSIX functions that take an absolute time point as a timeout parameter use
> the CLOCK_REALTIME clock. This clock can be warped, particularly on
> personal or embedded devices, which makes it unsuitable for use for
> timeo
