Turn on GPU rasterization when --enable-bleeding-edge-rendering-fast-paths is true.

cc/base/switches.cc

Index: cc/base/switches.cc
diff --git a/cc/base/switches.cc b/cc/base/switches.cc
index 1fb7ac98e37d6b3b87e1431a530bd25cd16a291e..60fc6bfa594cb8b4953e9e3a96d834b5aa8fd273 100644
--- a/cc/base/switches.cc
+++ b/cc/base/switches.cc
@@ -30,6 +30,14 @@ const char kDisableImplSidePainting[] = "disable-impl-side-painting";
 // Enables LCD text.
 const char kEnableLCDText[] = "enable-lcd-text";
 
+// Enable bleeding-edge code to make Chrome draw content faster. The changes
+// behind this path are very likely to break lots of content.
+// ** DO NOT use this flag unless you know what you are doing. **
+// This is the same flag as the one defined in
+//  content/public/common/content_switches.cc.

[jamesr, 2014/02/22 00:30:04]

no.  if you want the behavior controlled by a content::, set it from content
code. you probably want content/renderer/gpu/render_widget_compositor.cc to set
the appropriate setting or, failing that, populate the appropriate flag for
render process's command line in render_process_host_impl

[chrishtr, 2014/02/22 00:33:11]

Ok, I  can do that, thanks for the pointer.

I don't understand these dependencies though. Why can
content/renderer/gpu/render_widget_compositor.cc see a content switch and also
this file, but not vice versa?

[chrishtr, 2014/02/22 00:38:43]

Done.

+const char kEnableBleedingEdgeRenderingFastPaths[] =
+    "enable-bleeding-edge-rendering-fast-paths";
+
 // Paint content on the compositor thread instead of the main thread.
 const char kEnableImplSidePainting[] = "enable-impl-side-painting";
 
@@ -172,6 +180,9 @@ bool IsGpuRasterizationEnabled() {
     return false;
   else if (command_line.HasSwitch(switches::kEnableGPURasterization))
     return true;
+  else if (command_line.HasSwitch(
+               switches::kEnableBleedingEdgeRenderingFastPaths))
+    return true;
 
   return false;
 }