Revert of Back PaintRecord with PaintOpBuffer instead of SkPicture

Revert of Back PaintRecord with PaintOpBuffer instead of SkPicture (patchset #49 id:950001 of https://codereview.chromium.org/2768143002/ )

Reason for revert:
Breaks peach_pit-tot-chrome-pfq-informational Build #5967: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/5967

Original issue's description:
> Back PaintRecord with PaintOpBuffer instead of SkPicture
> 
> Change the backing of PaintRecord to be a data structure implemented in
> cc/paint instead of using SkPicture directly.  This new class cribs heavily
> from SkLiteDL.
> 
> PaintRecord used to be a typedef to an SkPicture but now is a typedef to
> a PaintOpBuffer.  (This leaves some flexibility to change this in the
> future to an interface without having to modify all of Chromium again.)
> 
> PaintOpBuffer stores a contiguous array of ops, with the ops stored
> in place.  As an optimization, the first op is stored locally in the
> PaintOpBuffer itself to avoid extra allocations for small pictures.
> 
> This patch moves slow path counting from a gpu analysis canvas into
> PaintOpBuffer directly.  As ops are recorded, slow paths are counted, and
> a PaintRecord now knows how many ops it has.  This is about a 1.5% savings
> for record time (gpu analysis was 2% and 0.5% overhead to record later).
> 
> This patch also implements the SkRecordNoopSaveLayerDrawRestores
> optimization from Skia at raster time.  This takes save layer (just
> opacity) / draw / restore commands and turns them into draws with
> opacity.  It moves that optimization from Blink at record time inside of
> CompositingRecorder and moves it to both DisplayItemList::RasterItem
> and PaintOpBuffer::playback (since a save could be either a DisplayItem
> or a PaintOp).  It's not as robust as Skia's solution and so misses
> a few cases that Skia catches, but the rasterize and record on 10k
> page agreed that performance was good enough.
> 
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> 
> Review-Url: https://codereview.chromium.org/2768143002
> Cr-Commit-Position: refs/heads/master@{#467335}
> Committed: https://chromium.googlesource.com/chromium/src/+/f5a5ed867ba06ae56f8fc299a9eb194471277eec

TBR=chrishtr@chromium.org,danakj@chromium.org,mtklein@chromium.org,thakis@chromium.org,vitalybuka@chromium.org,vmpstr@chromium.org,enne@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Review-Url: https://codereview.chromium.org/2839343002
Cr-Commit-Position: refs/heads/master@{#467497}
Committed: https://chromium.googlesource.com/chromium/src/+/afc38d533169c0fb576d2def6f5a37943784100f

[Qiang(Joe) Xu, 2017-04-26 22:57:18]

The CQ bit was checked by warx@chromium.org

[Qiang(Joe) Xu, 2017-04-26 22:57:18]

Created Revert of Back PaintRecord with PaintOpBuffer instead of SkPicture

[commit-bot: I haz the power, 2017-04-26 22:58:20]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-26 22:59:55]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493247438047530, "parent_rev":
"145b24f9355dc8a7c59bfb93f3634eef1d555784", "commit_rev":
"afc38d533169c0fb576d2def6f5a37943784100f"}

[commit-bot: I haz the power, 2017-04-26 23:00:39]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493247438047530, "parent_rev":
"145b24f9355dc8a7c59bfb93f3634eef1d555784", "commit_rev":
"afc38d533169c0fb576d2def6f5a37943784100f"}

[commit-bot: I haz the power, 2017-04-26 23:00:42]

Description was changed from

==========
Revert of Back PaintRecord with PaintOpBuffer instead of SkPicture (patchset #49
id:950001 of https://codereview.chromium.org/2768143002/ )

Reason for revert:
Breaks peach_pit-tot-chrome-pfq-informational Build #5967:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot...

Original issue's description:
> Back PaintRecord with PaintOpBuffer instead of SkPicture
> 
> Change the backing of PaintRecord to be a data structure implemented in
> cc/paint instead of using SkPicture directly.  This new class cribs heavily
> from SkLiteDL.
> 
> PaintRecord used to be a typedef to an SkPicture but now is a typedef to
> a PaintOpBuffer.  (This leaves some flexibility to change this in the
> future to an interface without having to modify all of Chromium again.)
> 
> PaintOpBuffer stores a contiguous array of ops, with the ops stored
> in place.  As an optimization, the first op is stored locally in the
> PaintOpBuffer itself to avoid extra allocations for small pictures.
> 
> This patch moves slow path counting from a gpu analysis canvas into
> PaintOpBuffer directly.  As ops are recorded, slow paths are counted, and
> a PaintRecord now knows how many ops it has.  This is about a 1.5% savings
> for record time (gpu analysis was 2% and 0.5% overhead to record later).
> 
> This patch also implements the SkRecordNoopSaveLayerDrawRestores
> optimization from Skia at raster time.  This takes save layer (just
> opacity) / draw / restore commands and turns them into draws with
> opacity.  It moves that optimization from Blink at record time inside of
> CompositingRecorder and moves it to both DisplayItemList::RasterItem
> and PaintOpBuffer::playback (since a save could be either a DisplayItem
> or a PaintOp).  It's not as robust as Skia's solution and so misses
> a few cases that Skia catches, but the rasterize and record on 10k
> page agreed that performance was good enough.
> 
>
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> 
> Review-Url: https://codereview.chromium.org/2768143002
> Cr-Commit-Position: refs/heads/master@{#467335}
> Committed:
https://chromium.googlesource.com/chromium/src/+/f5a5ed867ba06ae56f8fc299a9eb...

TBR=chrishtr@chromium.org,danakj@chromium.org,mtklein@chromium.org,thakis@chr...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
==========

to

==========
Revert of Back PaintRecord with PaintOpBuffer instead of SkPicture (patchset #49
id:950001 of https://codereview.chromium.org/2768143002/ )

Reason for revert:
Breaks peach_pit-tot-chrome-pfq-informational Build #5967:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot...

Original issue's description:
> Back PaintRecord with PaintOpBuffer instead of SkPicture
> 
> Change the backing of PaintRecord to be a data structure implemented in
> cc/paint instead of using SkPicture directly.  This new class cribs heavily
> from SkLiteDL.
> 
> PaintRecord used to be a typedef to an SkPicture but now is a typedef to
> a PaintOpBuffer.  (This leaves some flexibility to change this in the
> future to an interface without having to modify all of Chromium again.)
> 
> PaintOpBuffer stores a contiguous array of ops, with the ops stored
> in place.  As an optimization, the first op is stored locally in the
> PaintOpBuffer itself to avoid extra allocations for small pictures.
> 
> This patch moves slow path counting from a gpu analysis canvas into
> PaintOpBuffer directly.  As ops are recorded, slow paths are counted, and
> a PaintRecord now knows how many ops it has.  This is about a 1.5% savings
> for record time (gpu analysis was 2% and 0.5% overhead to record later).
> 
> This patch also implements the SkRecordNoopSaveLayerDrawRestores
> optimization from Skia at raster time.  This takes save layer (just
> opacity) / draw / restore commands and turns them into draws with
> opacity.  It moves that optimization from Blink at record time inside of
> CompositingRecorder and moves it to both DisplayItemList::RasterItem
> and PaintOpBuffer::playback (since a save could be either a DisplayItem
> or a PaintOp).  It's not as robust as Skia's solution and so misses
> a few cases that Skia catches, but the rasterize and record on 10k
> page agreed that performance was good enough.
> 
>
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> 
> Review-Url: https://codereview.chromium.org/2768143002
> Cr-Commit-Position: refs/heads/master@{#467335}
> Committed:
https://chromium.googlesource.com/chromium/src/+/f5a5ed867ba06ae56f8fc299a9eb...

TBR=chrishtr@chromium.org,danakj@chromium.org,mtklein@chromium.org,thakis@chr...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Review-Url: https://codereview.chromium.org/2839343002
Cr-Commit-Position: refs/heads/master@{#467497}
Committed:
https://chromium.googlesource.com/chromium/src/+/afc38d533169c0fb576d2def6f5a...
==========

[commit-bot: I haz the power, 2017-04-26 23:00:47]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/afc38d533169c0fb576d2def6f5a...