Add candidate Precompile combinations These Pipelines were generated by collecting all the Pipelines from the following stories and then ranking them by decreasing frequency: animometer_webgl_attrib_arrays, balls_javascript_canvas, canvas_05000_pixels_per_second, chip_tune, css_value_type_shadow, fill_shapes, ie_chalkboard, main_30fps_impl_60fps, new_tilings, transform_transitions_js_block, web_animations_staggered_infinite_iterations, wikipedia_2018 The graphite_precompile.cc file is specifically split out so candidate pipelines can be cut and pasted from Skia's ChromePrecompileTest.cpp unit test. Low-Coverage-Reason: EXPERIMENTAL_CODE Feature is not yet enabled Bug: skbug.com/358074434 Change-Id: I601c26a5015fea5bf8f9c891b54a46cb8a9bc854 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6347759 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Robert Phillips <robertphillips@google.com> Cr-Commit-Position: refs/heads/main@{#1434093}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.