<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - cairo-tor-scan-converter is off by half of a subrow." href="https://bugs.freedesktop.org/show_bug.cgi?id=84396#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - cairo-tor-scan-converter is off by half of a subrow." href="https://bugs.freedesktop.org/show_bug.cgi?id=84396">bug 84396</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Better. Realised we could do_full_row if insert new edges at the beginning of the fullrow (and have no other edge operations within the row), which fixed up the issue with switching from subsampling to analytic within bug-seams and simple-edges. commit 950f1e7103a3b4f3405fbb3ee2844ed24b902834 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Thu Oct 2 07:52:05 2014 +0100 tor: Enable analytic processing for starting rows If all the edges start at the very beginning of the whole row, we can merge them and include check for intersections/endings during the row. This allows us to enable fast analytic processing for even the very first row on pixel aligned vertices. Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a> Still the rasteriser is not symmetric though. :|</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>