[test] Make msan work for v8 stand-alone.

[test] Make msan work for v8 stand-alone.

The msan configuration can be used in combination with
v8_use_snapshot=false.

BUG=chromium:425187
LOG=n

Committed: https://crrev.com/a65ef0d53fc28b0908f228938c6d84effa83c596
Cr-Commit-Position: refs/heads/master@{#28064}

[Michael Achenbach, 2014-12-19 10:32:19]

machenbach@chromium.org changed reviewers:
+ earthdok@chromium.org, jochen@chromium.org, svenpanne@chromium.org

[Sven Panne, 2014-12-19 12:02:20]

lgtm

[Michael Achenbach, 2014-12-19 12:17:15]

Note: This is blocked on moving libc++.gyp to a common depsable place like
buildtools.

[earthdok, 2014-12-19 15:54:02]

https://codereview.chromium.org/802583003/diff/1/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/802583003/diff/1/build/standalone.gypi#newcod...
build/standalone.gypi:222: '-Wl,--as-needed',
this should be in "ldflags!", not "ldflags"

[jochen (gone - plz use gerrit), 2015-01-12 14:23:32]

https://codereview.chromium.org/802583003/diff/80001/build/standalone.gypi
File build/standalone.gypi (left):

https://codereview.chromium.org/802583003/diff/80001/build/standalone.gypi#ol...
build/standalone.gypi:221: '-fno-omit-frame-pointer',
why these changes?

[Michael Achenbach, 2015-04-27 09:08:39]

PTAL at patch 6. This compiles with v8 nosnap builds.

https://codereview.chromium.org/802583003/diff/100001/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/802583003/diff/100001/build/standalone.gypi#n...
build/standalone.gypi:331: 'cflags+': [
Without the additional cflags -fPIC and the removal of -fno-exceptions we run
into compile errors in libc++ and libc++abi.

[Michael Achenbach, 2015-04-27 10:12:43]

The CQ bit was checked by machenbach@chromium.org

[Michael Achenbach, 2015-04-27 10:12:43]

The patchset sent to the CQ was uploaded after l-g-t-m from
svenpanne@chromium.org
Link to the patchset: https://codereview.chromium.org/802583003/#ps100001
(title: "Rework from scratch")

[commit-bot: I haz the power, 2015-04-27 10:12:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/802583003/100001

[commit-bot: I haz the power, 2015-04-27 10:14:29]

Committed patchset #6 (id:100001)

[commit-bot: I haz the power, 2015-04-27 10:14:40]

Patchset 6 (id:??) landed as
https://crrev.com/a65ef0d53fc28b0908f228938c6d84effa83c596
Cr-Commit-Position: refs/heads/master@{#28064}

[Michael Achenbach, 2015-04-27 11:14:19]

A revert of this CL (patchset #6 id:100001) has been created in
https://codereview.chromium.org/1104073002/ by machenbach@chromium.org.

The reason for reverting is: Compile failures:
http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20s....

[earthdok, 2015-05-05 14:40:47]

https://codereview.chromium.org/802583003/diff/100001/build/standalone.gypi
File build/standalone.gypi (right):

https://codereview.chromium.org/802583003/diff/100001/build/standalone.gypi#n...
build/standalone.gypi:41: 'msan_track_origins%': 1,
I suggest '2' here. The performance difference is small enough that we no longer
encourage the use of track_origins=1. We don't have any configurations in
Chromium that use it.

https://codereview.chromium.org/802583003/diff/100001/build/standalone.gypi#n...
build/standalone.gypi:331: 'cflags+': [
On 2015/04/27 09:08:39, Michael Achenbach wrote:
> Without the additional cflags -fPIC and the removal of -fno-exceptions we run
> into compile errors in libc++ and libc++abi.

This is very strange. -fPIC should be implied by -fsanitize=memory, and we
certainly don't need exceptions. Can you paste the errors you see? (or how to
reproduce this)