Note, anytime you see "(?+0x###)" in a X backtrace, you've encountered
this issue.
With this patch it becomes "(?+0x0)". Nothing big, but it reduces
some noise that
might be confused for signal.
See all these bugs (beware, the queries may be slow):
On Tue, Jan 23, 2018 at 10:27 AM, Michel Dänzer <mic...@daenzer.net> wrote:
> On 2018-01-23 04:26 PM, Chris Wilson wrote:
>> Quoting Jeffrey Smith (2018-01-23 15:15:10)
>>> On Mon, Jan 22, 2018 at 3:01 PM, Chris Wilson <ch...@chris-wilson.co.uk>
>>> wrote:
&
On Mon, Jan 22, 2018 at 3:01 PM, Chris Wilson wrote:
> Quoting Adam Jackson (2018-01-22 20:09:52)
>> On Sat, 2017-12-23 at 19:26 +0100, Clemens Eisserer wrote:
>> > Hi there,
>> >
>> > Glamor's gradient acceleration code is broken in case RepeatReflect is
>> > used,
On Mon, Jan 22, 2018 at 3:01 PM, Chris Wilson wrote:
> Quoting Adam Jackson (2018-01-22 20:09:52)
>> On Sat, 2017-12-23 at 19:26 +0100, Clemens Eisserer wrote:
>> > Hi there,
>> >
>> > Glamor's gradient acceleration code is broken in case RepeatReflect is
>> > used,
On Wed, Dec 27, 2017 at 9:38 PM, Keith Packard <kei...@keithp.com> wrote:
> Jeffrey Smith <whydo...@gmail.com> writes:
>
>> GetTimeInMillis uses the CLOCK_MONOTONIC_COARSE clock if
>> available and the precision is high enough. That clock is supposed
>>
On Wed, Dec 27, 2017 at 1:26 PM, Keith Packard wrote:
> Jeff Smith writes:
>
>> Prior to commit a779fda2 (xwayland: Use the CLOCK_MONOTONIC clock),
>> GetTimeInMillis() and GetTimeInMicros() had separate clockid's. As a
>> part of making them available to
On Wed, Dec 27, 2017 at 3:53 AM, Mark Kettenis wrote:
>> From: Jeff Smith
>> Date: Tue, 26 Dec 2017 22:10:54 -0600
>>
>> When clock_gettime(CLOCK_MONOTONIC) fails, xserver falls back on
>> gettimeofday(). However, gettimeofday() is deprecated in