[wasm][asm.js] Allow asm.js->wasm codegen in unsafe-eval situations.

[wasm][asm.js] Allow asm.js->wasm codegen in unsafe-eval situations.

A recent change to disallow wasm compilation in contexts where
CSP unsafe-eval would disallow eval also ended up banning asm.js there:
https://codereview.chromium.org/2646713002

This ends up banning non-evaled asm.js even in some places it should be
allowed.

NOTE: Although asm.js code converted to wasm generates an intermediate wasm
module. asm.js code evaled in a disallowed context can't even get
that far (as it's stoped at the eval site).

BUG=683867
R=mtrofin@chromium.org,titzer@chromium.org,adamk@chromium.org

Review-Url: https://codereview.chromium.org/2656463004
Cr-Commit-Position: refs/heads/master@{#42616}
Committed: https://chromium.googlesource.com/v8/v8/+/e53f6469d90b08e8042b120438702a0666f0d331

[bradnelson, 2017-01-24 04:25:48]

The CQ bit was checked by bradnelson@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-24 04:25:52]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[bradn, 2017-01-24 04:26:10]

bradnelson@google.com changed reviewers:
+ bradnelson@google.com

[Mircea Trofin, 2017-01-24 04:40:53]

lgtm

[bradn, 2017-01-24 04:43:02]

The CQ bit was unchecked by bradnelson@google.com

[bradn, 2017-01-24 04:43:03]

The CQ bit was checked by bradnelson@google.com

[commit-bot: I haz the power, 2017-01-24 04:43:08]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-24 05:00:36]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1485232983382390, "parent_rev":
"23442ed450fa22ea094f5c7434c18313451862b6", "commit_rev":
"e53f6469d90b08e8042b120438702a0666f0d331"}

[commit-bot: I haz the power, 2017-01-24 05:00:41]

Description was changed from

==========
[wasm][asm.js] Allow asm.js->wasm codegen in unsafe-eval situations.

A recent change to disallow wasm compilation in contexts where
CSP unsafe-eval would disallow eval also ended up banning asm.js there:
https://codereview.chromium.org/2646713002

This ends up banning non-evaled asm.js even in some places it should be
allowed.

NOTE: Although asm.js code converted to wasm generates an intermediate wasm
module. asm.js code evaled in a disallowed context can't even get
that far (as it's stoped at the eval site).

BUG=683867
R=mtrofin@chromium.org,titzer@chromium.org,adamk@chromium.org
==========

to

==========
[wasm][asm.js] Allow asm.js->wasm codegen in unsafe-eval situations.

A recent change to disallow wasm compilation in contexts where
CSP unsafe-eval would disallow eval also ended up banning asm.js there:
https://codereview.chromium.org/2646713002

This ends up banning non-evaled asm.js even in some places it should be
allowed.

NOTE: Although asm.js code converted to wasm generates an intermediate wasm
module. asm.js code evaled in a disallowed context can't even get
that far (as it's stoped at the eval site).

BUG=683867
R=mtrofin@chromium.org,titzer@chromium.org,adamk@chromium.org

Review-Url: https://codereview.chromium.org/2656463004
Cr-Commit-Position: refs/heads/master@{#42616}
Committed:
https://chromium.googlesource.com/v8/v8/+/e53f6469d90b08e8042b120438702a0666f...
==========

[commit-bot: I haz the power, 2017-01-24 05:00:42]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/e53f6469d90b08e8042b120438702a0666f...