Stop compiling and printing logging strings for CHECK() on Android.

This is a performance regression in general, and causes visible
regression when Blink used CHECK instead of their own RELEASE_ASSERT.

This behaviour was introduced in https://codereview.chromium.org/336413005

If Android continues to need something special here (radio silence
from previously-interested parties for the last few weeks), we should
print __FILE__ and __LINE__ or something, and not support the full
string logging that this patch reverts.

R=haraken, thakis@chromium.org
BUG=599867,596760, 378974

Review-Url: https://codereview.chromium.org/1937613002
Cr-Commit-Position: refs/heads/master@{#391613}


CrOS-Libchrome-Original-Commit: b9d5931295b7eab7bd2f029b8d896082b911d776
1 file changed
tree: 8dac20963e447c5855cbd98fb7133bf8eb6b0cac
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/