Direct call to eval passes strict mode through.

src/compilation-cache.h

Index: src/compilation-cache.h
diff --git a/src/compilation-cache.h b/src/compilation-cache.h
index 37e21be99d4ac471a8f865320d7be4c74f810f8b..2618d545bc705e59d07d712cabd5dbde29c57872 100644
--- a/src/compilation-cache.h
+++ b/src/compilation-cache.h
@@ -51,7 +51,8 @@ class CompilationCache {
   // contain a script for the given source string.
   static Handle<SharedFunctionInfo> LookupEval(Handle<String> source,

[Martin Maly, 2011/02/02 23:56:22]

compiled pieces of eval code are cached so we must consider strict as part of
the equality comparison on the compiled snippets. Consider:
a.js:

eval("function arguments(){};");

b.js:

"use strict";
eval("function arguments(){};");

When executing both files (d8 a.js b.js) the second eval would experience cache
hit and code would never be compiled, error never reported etc.

[Lasse Reichstein, 2011/02/03 12:36:01]

Good catch. We wouldn't want that.

                                                Handle<Context> context,
-                                               bool is_global);
+                                               bool is_global,
+                                               bool is_strict);
 
   // Returns the regexp data associated with the given regexp if it
   // is in cache, otherwise an empty handle.