v8/test/cctest/interpreter
verwaest fd40570419 Don't do any special normalization if a boilerplate contains function literals.
This mechanism was used to ensure that functions ended up as constants on the map of prototypes defined using object literals, e.g.,:

function.prototype = {
  method: function() { ... }
}

Nowadays we treat prototypes specially, and make all their functions constants when an object turns prototype. Hence this special custom code isn't necessary anymore.

This also affects boilerplates that do not become prototypes. Their functions will not be constants but fields instead. Calling their methods will slow down. However, multiple instances of the same boilerplate will stay monomorphic. We'll have to see what the impact is for such objects, but preliminary benchmarks do not show this as an important regression.

BUG=chromium:593008
LOG=n

Review URL: https://codereview.chromium.org/1772423002

Cr-Commit-Position: refs/heads/master@{#34602}
2016-03-08 22:13:49 +00:00
..
bytecode_expectations Don't do any special normalization if a boilerplate contains function literals. 2016-03-08 22:13:49 +00:00
bytecode-expectations-printer.cc [Interpreter] Refactor bytecode generator test suite. 2016-02-25 12:07:19 +00:00
bytecode-expectations-printer.h [Interpreter] Refactor bytecode generator test suite. 2016-02-25 12:07:19 +00:00
generate-bytecode-expectations.cc [Interpreter] Silence runtime errors in generate-bytecode-expectations. 2016-03-01 10:43:22 +00:00
test-bytecode-generator.cc [Interpreter] Refactor bytecode generator test suite. 2016-02-25 12:07:19 +00:00
test-interpreter.cc [Interpreter] Removes TestNotEqualsStrict bytecode from interpreter. 2016-03-07 10:50:44 +00:00