GitLab

This is a new implementation of DesktopCloudPolicyStore. It has
- Different path of policy cache
  The policy files are store as
    "$user_data_dir/Policy/Machine Level User Cloud Policy" and
     "$user_data_dir/Policy/Machine Level User Cloud Policy Signing Key".
- Global dm_token and client_id
  It will load the policy cache from disk iff the global token is existed.
  And it will validate the dm_token and client_id with the global ones after
  store/load.

Bug: 812641
Change-Id: If02ad77388fc197f20dc25c04c1f852e1827253a
Reviewed-on: https://chromium-review.googlesource.com/940442
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541582}

Bug: 810806
Change-Id: I9bbea1cb50278a31fe4c95c6cf6c730ad9e37abc
Reviewed-on: https://chromium-review.googlesource.com/944509Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541581}

mini_installer is a "special" target that avoids linking against
vcruntime by defining a custom entry point. In normal Windows builds,
exe_and_shlib_deps will be empty, so depending on it has no effect. But
when building with use_custom_libcxx=true, exe_and_shlib_deps depends
on libc++, which in turn depends on vcruntime, leading to undefined
symbol errors at link time when the custom entry point is used.

This change avoids the dependency on exe_and_shlib_deps unless the
custom entry point is disabled, i.e. when we are linking with asan.

Bug: 801780
Change-Id: Ieff8004ef14c9fda20ff23234cab364ae949afbe
Reviewed-on: https://chromium-review.googlesource.com/952068
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541580}

Pepper CDM support is deprecated, so is ppapi CDM adapter binary. This
CL removes all CDM adapter related code from CdmHostFiles.

Also removes all CDM related code from PpapiThread, including CDM host
verification code that uses CdmHostFiles.

Bug: 772160
Change-Id: I727063d60eeccc60330c10c2fa9339bdc72813a3
Reviewed-on: https://chromium-review.googlesource.com/947923
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541579}

The histogram name for sink type selection was not the same as the one
in histograms.xml, and was not being recorded as a result. This CL
fixes that.

Bug: 783850
Change-Id: Ia6c1d983c8933ae9c0dedd83cbe0d1ef7df13db1
Reviewed-on: https://chromium-review.googlesource.com/951895Reviewed-by: Derek Cheng <imcheng@chromium.org>
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541578}

This change refactors the Web Bluetooth test API to use the
DeviceUUIDs helper class defined in BluetoothDevice. Additionally,
this change finishes the implementation of SimulateGATTServicesChanged,
and as a result, tests are updated to set the next discovery response
before calling this interface.

BUG=719826

Change-Id: I0f986eb7afe6fbf7ebaa80ac4b633d46a027b80d
Reviewed-on: https://chromium-review.googlesource.com/939984
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541577}

Several changes to the bindings [1] landed while the change that added the
mock writer was in review [2].  The mock writer wasn't rerun right before it
landed, so its output is out-of-sync with the bindings metadata.

Rerun the generator to fix things up. This is a prerequisite for a change
I want to make to the generator.

1: https://chromium-review.googlesource.com/c/chromium/src/+/766687,
   https://chromium-review.googlesource.com/c/chromium/src/+/779087
2: https://chromium-review.googlesource.com/c/chromium/src/+/772810

Bug: 761432,550065
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I1ad3658c8f92bdd587d1659bb21d58ac71a549f6
Reviewed-on: https://chromium-review.googlesource.com/953382Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541576}

This is a mechanical replace plus some line breaking.

Done because https://github.com/GoogleChromeLabs/webidl-diff uses these
URLs to decide where to go look for specs with IDL to scrape.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I929161a414e825ce6bf2e17ea295a0af78e30fd7
Reviewed-on: https://chromium-review.googlesource.com/952539Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541575}

The non-numbered variants are used in other places, so this is not new.

Purpose is to avoid finding these URLs in
https://github.com/GoogleChromeLabs/webidl-diff.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I59731c0588df176f18390c21a792b2ec99ba42fc
Reviewed-on: https://chromium-review.googlesource.com/952530Reviewed-by: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541574}

Chrome version for Windows is updated.
On the previous commit I had entered a wrong Chrome version 540270.
Updated with the correct version of 540272.

Change-Id: I6b14cf4ce08e7ece73397eeef0e4f15521ae85e5
Reviewed-on: https://chromium-review.googlesource.com/952115Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541573}

This reverts commit c838bf40.

Reason for revert: virtual/threaded/animations/hit-testing/composited-with-hit-testing.html fails in Debug, flaky in Release

Builders failed on: 
- WebKit Linux Trusty (dbg): 
 https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Trusty%20%28dbg%29

- Win7 Tests (dbg)(1):   https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29

Flakiness Dashboard:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=virtual%2Fthreaded%2Fanimations%2Fhit-testing%2Fcomposited-with-hit-testing.html

Bug: 819591

Original change's description:
> Web Animations: use WTF::Optional for Animation::start_time_
> 
> Bug: 791086
> Change-Id: I916508fc5cf0c16543decd3f8197d034f2a4e6d8
> Reviewed-on: https://chromium-review.googlesource.com/941963
> Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#541223}

TBR=flackr@chromium.org,smcgruer@chromium.org

Change-Id: I2094317fbf67d28bb5c32124a7d3fa62c7323a3b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 791086
Reviewed-on: https://chromium-review.googlesource.com/953363Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541572}

Bug: 819645
Change-Id: Iff4fbf906aa5e066db462aa41365e158969bc9b2
Reviewed-on: https://chromium-review.googlesource.com/953065
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541571}

The way GTK theming is plumbed through is very subtle, and we don't
know yet how that should influence new color schemes.

This CL tries to isolate (and make explicit) the complexity required
for GTK theming on Desktop Linux by introducing OmniboxTint::NATIVE,
as distinct from LIGHT and DARK used everywhere else.

Bug: 819425, 801583
Change-Id: I34ad8113f5e66843dab685c3ce3470dd7bd7f675
Reviewed-on: https://chromium-review.googlesource.com/952503
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541570}

Replaces the whole call chain for ShowUnhandledTapUIIfNeeded
between Blink and Chrome/WebView with Mojo messaging.

Removes the Blink WebTappedInfo class in favor of a new UnhandledTapInfo
that sends a Mojo construct of the same name to the Browser which
has a service installed via a RenderHostFrame observer.

All functionality should remain unchanged.

NEW CODE:
The CSTabHelper now creates an UnhandledTapWebContentsObserver that
connects the Mojo service via UnhandledTapNotifierImpl.  That Impl
calls back through Java to the CSTabHelper to the CSManager to notify
that a Tap has occurred.  The CSTabHelper ignores these notifications
when CS is disabled.

The mojo message is only sent to the browser if the tap is unhandled
and the other required conditions are met.

UPDATED TESTS:
Test notification is now done through mojo messaging, so we now only
know if the tap was unhandled, not whether the page changed or other
details about why the tap was unhandled.

Updated the test page by adding nodes that do not trigger, and removed
the mousemove handler since it's unrelated to tap handling.

BUG=754862

TBR=dcheng@chromium, yfriedman@chromium.org, kinuko@chromium.org

Original CL:

Reviewed-on: https://chromium-review.googlesource.com/841544Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Change-Id: I824837419cd4116b26b32170009e7a7c3308d109
Reviewed-on: https://chromium-review.googlesource.com/952679
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541569}

We should (finally) remove support for manifest v1. One of the last
significant dependencies is that a lot of our tests aren't manifest v2
yet.

This CL updates the majority of manifest files under
chrome/test/data/extensions/manifest_tests (which are not usually
named manifest.json).

This CL only modifies files that update cleanly (i.e., no other
test updates necessary). A separate CL will address those.

Bug: 816679
Change-Id: Id8b03de2bd26a70d313e85cf56433e3788686e2d
Reviewed-on: https://chromium-review.googlesource.com/950225Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541568}

Implement platform-specific ProtectedMemory behavior, specifically implement
setting memory read-only/read-write, checking whether a given pointer points to
read-only memory, and identifying the beginning and end points for the protected
memory section.

Bug: 771365
Change-Id: I814ed932f3b57dc674ae342f79622fc84c92c351
Reviewed-on: https://chromium-review.googlesource.com/765009Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Brett Wilson <brettw@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541567}

BUG=

Change-Id: If0e07f2a53c084f3fdedc5e9b78a76aab5402048
Reviewed-on: https://chromium-review.googlesource.com/953207Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541566}

There will be a StrictMode violation in a callback in PopUpInfo.onClick.
Fixing by disabling StrictMode during the call.

For more details please refer to the bug, this can be reverted if the
root cause is the CL mentioned in the comment #3 in the bug.

Bug: 819410
Change-Id: Ib79f83835b7938b327daec30e884a03924e7e32e
Reviewed-on: https://chromium-review.googlesource.com/952673Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Yafei Duan <romax@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541565}

TBR=stgao@chromium.org

Bug: 819683
Change-Id: I48ea37df344775b577d1231286a20f46584b7634
Reviewed-on: https://chromium-review.googlesource.com/953130Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541564}

https://chromium.googlesource.com/angle/angle.git/+log/7618eaf9ad45..e4c5a23b1148

$ git log 7618eaf9a..e4c5a23b1 --date=short --no-merges --format='%ad %ae %s'
2018-03-02 jmadill Vulkan: Always use LOAD for RenderPass attachments.
2018-03-06 tobine Roll (1/2) LVL version forward and disable VANGLE
2018-03-02 cwallez Allow rectangle textures to be sample with texture() in ESSL3

Created with:
  roll-dep src/third_party/angle
BUG=757974


The AutoRoll server is located here: https://angle-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=ynovikov@chromium.org

Change-Id: Iec15cbc5752aebe0c3da0b7788b784db67df6e85
Reviewed-on: https://chromium-review.googlesource.com/952961Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#541563}

We are not using PPAPI to host CDMs anymore. Hence no need to specify
PepperType for KeySystems.

Bug: 772160
Change-Id: Ie9d2f34ef49e93b0039e9e3718ee95392289281a
Reviewed-on: https://chromium-review.googlesource.com/947808
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541562}

Bug: 786190
Change-Id: Ie97d20c6893865d876ea39083861e5400493de42
Reviewed-on: https://chromium-review.googlesource.com/833390
Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541561}

Updates MojoCreateMessage, MojoSerializeMessage, MojoSetMessageContext
(nee MojoAttachMessageContext), and MojoGetMessageContext to support a
versioned options structure.

Reworks MojoSetMessageContext to support a zero value as context
removal, and gets rid of the RELEASE flag on MojoGetMessageContext,
because this seems like a better API.

TBR=dcheng@chromium.org

Bug: 819046
Change-Id: I090554f484c1d6427a53496463e5de6bcd386bbd
Reviewed-on: https://chromium-review.googlesource.com/952284
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541560}

Removes the experiment percentage from the VR tests on the K CQ bot.
This would make failures blocking, except there was a typo so failures
were already blocking.

Bug: 709620
Change-Id: I8d7727cd92d8e400540f1f9937cf60832ac8e536
Reviewed-on: https://chromium-review.googlesource.com/952334Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541559}

Retrieves context with #getApplicationContext

Bug: 807728
Change-Id: Ic44fae78c07519819289deefcb4f5f5fb28dc858
Reviewed-on: https://chromium-review.googlesource.com/946742
Commit-Queue: Daniel Park <danielpark@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541558}

Added chrome://media-router-internals page to show Media Router debug info.

Bug: 687380
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I28f2e996b9643acf92a07bc0e213c075882a8a6c
Reviewed-on: https://chromium-review.googlesource.com/929997
Commit-Queue: Bin Zhao <zhaobin@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541557}

The original change was to enable TLS in QuicFramerTest. This
restructures how that is enabled and when we check for invalid use of
PROTOCOL_TLS1_3.

Change-Id: I91eaea8d305675fb9279c312f12a9e34efb61cbc
Reviewed-on: https://chromium-review.googlesource.com/952568Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Nick Harper <nharper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541556}

This is required in order to back-fill builds that are broken
for a specific revision range.

Change-Id: Id505fca3b641575b854b48df728b78951c28fbcb
Reviewed-on: https://chromium-review.googlesource.com/949385
Commit-Queue: Prasad Vuppalapu <prasadv@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541555}

Board data is useful for grouping crashes that are specific to particular
hardware. It is available in manual crash reports, but is not currently
included in silent feedback reports.

Bug: 812226
Change-Id: I2d9a7290ec66c6abe1a3a69885150cd03c3c4d2e
Reviewed-on: https://chromium-review.googlesource.com/919083
Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541554}

DownloadFile can simply use the TaskRunner is was created on to post tasks.

BUG=803135

Change-Id: Idaccfba1c719d96a2fa11d933809ce4573004ee6
Reviewed-on: https://chromium-review.googlesource.com/952204
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Xing Liu <xingliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541553}

g_enable_for_testing is outdated and is currently used for allowing to fetch variation seed
from tests. Therefore the variable and corresponding function is renamed to match its meaning.

For variations_service_policy_browsertest and policy_browsertest the use is removed as they
don't need to fetch variation seed.

Change-Id: I145ce32e71efc2e9a7d47547e5d67fc7f839cee5
Reviewed-on: https://chromium-review.googlesource.com/944013
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541552}

Bug: 769401
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ic00aa9c4eada086ec810ae6167e614ed72e5a046
Reviewed-on: https://chromium-review.googlesource.com/953086
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541551}

This data type is useful for sending stats from the renderer to the
browser, in SubresourceResponseStarted methods.  Currently there are six
fields that are passed around, but soon there may be more in order to
get PageLoadMetrics working with the Network Service.

BUG=816684

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I26a62ebb5aa82f225a70fe54098433c5c3342941
Reviewed-on: https://chromium-review.googlesource.com/947582
Commit-Queue: Conley Owens <cco3@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541550}

Adding viz_browser_tests to the main viz_gtest suite. This will enable them on
the CQ.

TEST=viz_browser_tests

TBR=dpranke@chromium.org

Bug: 803148
Change-Id: If91ebaad6b116925ade56dbd68672cdc56c81fa2
Reviewed-on: https://chromium-review.googlesource.com/952983Reviewed-by: Jonathan Ross <jonross@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541549}

This patch rolls the Feed library forward to revision:
4dedff6189bbd8f3dc594ba3e2159ccdf929359a

This patch also fixes the BUILD.gn:
* adds missing files.
* reduces the number of targets, to simplify management.

Because none of the code is presently used, it has no impact on
DEX sizes. There is a minor impact on resources size (1kB).

Change-Id: Idcd00ea084c137f2b9d9f4bf46ea1051930b1b0c
Reviewed-on: https://chromium-review.googlesource.com/952185Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Commit-Queue: Filip Gorski <fgorski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541548}

Bug: 813540
Change-Id: I9338aa2475c15090b8a60729be25502eb866efb7
Reviewed-on: https://chromium-review.googlesource.com/952522Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541547}

This CL adds explicit assertNotNull to check results of
Instrumentation.waitForMonitorWithTimeout calls. It also removes
removeMonitor calls, as waitForMonitorWithTimeout removes the monitor
from the monitor list once it has been hit.

Bug: 758751
Change-Id: I217b6e78a2c91b9e2c2db1810c1a128195347e51
Reviewed-on: https://chromium-review.googlesource.com/952970Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541546}

BUG=chromium:811827
BUG=chromium:811806
BUG=chromium:811790
BUG=chromium:811825
BUG=chromium:811872
BUG=chromium:811829
BUG=chromium:811819
BUG=chromium:811810
BUG=chromium:811808
BUG=chromium:811832
BUG=chromium:811797

Change-Id: I96d2032cc7bb5f9e0ade06485fbf28941a2e47f5
Reviewed-on: https://chromium-review.googlesource.com/953085Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541545}

GCC does not support int32x4_t loading using braces wrapping 4 ints.
Instead we should use the NEON intrinsic to load from an array of
ints.

Bug: 819294
Change-Id: I13b877405273e4ebcc944d50c155ee29ff31cc99
Reviewed-on: https://chromium-review.googlesource.com/951773
Commit-Queue: Mike Klein <mtklein@chromium.org>
Reviewed-by: Mike Klein <mtklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541544}

Bug: None
Change-Id: Ibe78762cf8a01d326a3540e325fedfd16730c355
Reviewed-on: https://chromium-review.googlesource.com/951282Reviewed-by: Julia Tuttle <juliatuttle@chromium.org>
Commit-Queue: Randy Smith <rdsmith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541543}