Hi, > Ugh... not so good. According to Oliver on the bug, this just make the assert go away and doesn't actually fix anything. Likely this is needed but not sufficient.
So as far as I understand Oliver found the bad commit in xorg glamor: https://bugs.freedesktop.org/show_bug.cgi?id=107287 So at the moment we should fix just this "assertion" issue for Intel because "rendering" issue came from xorg/glamor and there is no "rendering" issue in Intel part. Please correct me if I incorrect. Regards, Andrii. On Tue, Jul 10, 2018 at 8:04 PM, Olivier Fourdan <[email protected]> wrote: > Hi, > > On Tue, 10 Jul 2018 at 18:56, Jason Ekstrand <[email protected]> wrote: > > > > Ugh... not so good. According to Oliver on the bug, this just make the > assert go away and doesn't actually fix anything. Likely this is needed > but not sufficient. > > Well, maybe not even needed, at least in my case I don't hit that > assert() with the current Mesa code (from either master and 18.1), > I've just seen that happening with past commits while doing the > bisection in git... So adding this now wouldn't help with bisection > (again, in my case, not sure about others). > > All I meant pointing at this assert() failure is that it breaks the > bisection in git as I am unable to tell if the rendering is correct or > not as it makes the test program abort. > > Cheers, > Olivier >
_______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
