Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(300)

Issue 2196803002: If scissor would be empty in GrClipMaskManager::SetupClipping indicate draw can be skipped. (Closed)

Created:
4 years, 4 months ago by bsalomon
Modified:
4 years, 4 months ago
CC:
reviews_skia.org
Base URL:
https://skia.googlesource.com/skia.git@master
Target Ref:
refs/heads/master
Project:
skia
Visibility:
Public.

Description

If scissor would be empty in GrClipMaskManager::SetupClipping indicate draw can be skipped. BUG=chromium:632185 GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2196803002 Committed: https://skia.googlesource.com/skia/+/6d9a213694cd30974f2d13261eade51cd6f1ee1f

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M src/gpu/GrClipMaskManager.cpp View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 11 (4 generated)
bsalomon
This fixes an issue where we compute an empty scissor rect (top==bottom) and then assert ...
4 years, 4 months ago (2016-07-29 17:54:42 UTC) #3
robertphillips
lgtm
4 years, 4 months ago (2016-07-29 18:01:10 UTC) #4
csmartdalton
On 2016/07/29 18:01:10, robertphillips wrote: > lgtm lgtm too. Curious, where does this happen? I ...
4 years, 4 months ago (2016-07-29 18:07:30 UTC) #5
bsalomon
On 2016/07/29 18:07:30, csmartdalton wrote: > On 2016/07/29 18:01:10, robertphillips wrote: > > lgtm > ...
4 years, 4 months ago (2016-07-29 18:10:01 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2196803002/1
4 years, 4 months ago (2016-07-29 18:10:22 UTC) #8
commit-bot: I haz the power
Committed patchset #1 (id:1) as https://skia.googlesource.com/skia/+/6d9a213694cd30974f2d13261eade51cd6f1ee1f
4 years, 4 months ago (2016-07-29 19:24:32 UTC) #10
csmartdalton
4 years, 4 months ago (2016-07-29 19:24:33 UTC) #11
Message was sent while issue was closed.
On 2016/07/29 18:10:01, bsalomon wrote:
> On 2016/07/29 18:07:30, csmartdalton wrote:
> > On 2016/07/29 18:01:10, robertphillips wrote:
> > > lgtm
> > 
> > lgtm too.
> > 
> > Curious, where does this happen? I would have thought GrReducedClip covered
> > every obvious case where this would happen by returning AllOut?
> 
> That's what I was trying to figure out when I stopped being able to reproduce
> it. I agree that GrReducedClip should return AllOut. If I can get this
> reproducing again I'll figure out how this exits ReduceClipStack.

Oh I see it now. Looking at the code..

GrReducedClip seems to catch all the cases of totally empty clip bounds.

However, I see that very narrow (<.5) non-aa clip rects can round to empty.
Also, any extremely narrow clip bounds (<GrClip::kBoundsTolerance) can round
"out" to empty if they are close enough to a pixel boundary.

Powered by Google App Engine
This is Rietveld 408576698