- 21 Feb, 2012 1 commit
-
-
ulan@chromium.org authored
R=rossberg@chromium.org Review URL: https://chromiumcodereview.appspot.com/9428001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10780 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 20 Feb, 2012 1 commit
-
-
jkummerow@chromium.org authored
Hidden behind --type-info-threshold=X flag, usage dependent on experimental profiler. Review URL: https://chromiumcodereview.appspot.com/9403009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10753 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 13 Feb, 2012 1 commit
-
-
svenpanne@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9389005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10685 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 26 Jan, 2012 1 commit
-
-
danno@chromium.org authored
BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9073007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10523 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Jan, 2012 1 commit
-
-
erik.corry@gmail.com authored
version. We don't want to randomize the stub cache. Review URL: http://codereview.chromium.org/9174023 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10402 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 13 Jan, 2012 1 commit
-
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/9139051 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10399 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 10 Jan, 2012 1 commit
-
-
svenpanne@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10371 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Jan, 2012 1 commit
-
-
ulan@chromium.org authored
BUG= TEST= Review URL: http://codereview.chromium.org/9008012 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10348 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Dec, 2011 1 commit
-
-
danno@chromium.org authored
Also several bugs with Smi/double elements handling and make Ensure* routines more flexible. BUG=none TEST=test/mjsunit/array-construct-transition.js Review URL: http://codereview.chromium.org/8820014 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10218 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 Nov, 2011 1 commit
-
-
keuchel@chromium.org authored
This CL introduces a third mode next to the non-strict (henceforth called 'classic mode') and 'strict mode' which is called 'extended mode' as in the current ES.next specification drafts. The extended mode is based on the 'strict mode' and adds new functionality to it. This means that most of the semantics of these two modes coincide. The 'extended mode' is entered instead of the 'strict mode' during parsing when using the 'strict mode' directive "use strict" and when the the harmony-scoping flag is active. This should be changed once it is fully specified how the 'extended mode' is entered. This change introduces a new 3 valued enum LanguageMode (see globals.h) corresponding to the modes which is mostly used by the frontend code. This includes the following components: * (Pre)Parser * Compiler * SharedFunctionInfo, Scope and ScopeInfo * runtime functions: StoreContextSlot, ResolvePossiblyDirectEval, InitializeVarGlobal, DeclareGlobals The old enum StrictModeFlag is still used in the backend when the distinction between the 'strict mode' and the 'extended mode' does not matter. This includes: * SetProperty runtime function, Delete builtin * StoreIC and KeyedStoreIC * StubCache Review URL: http://codereview.chromium.org/8417035 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10062 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Nov, 2011 1 commit
-
-
fschneider@chromium.org authored
BUG=none TEST=none Review URL: http://codereview.chromium.org/8473002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10034 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Nov, 2011 1 commit
-
-
svenpanne@chromium.org authored
Replaced FIRST_PHANTOM_PROPERTY_TYPE by a predicate. Removed the (hopefully) last default cases for switches on PropertyType. Benchmarks show that both changes are performace-neutral. Now every value of PropertyType should either be handled by an explicit case in a switch or by an equality operator. Therefore, the C++ compiler should finally be able to tell us which places to touch when changing PropertyType. Review URL: http://codereview.chromium.org/8506004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9930 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Nov, 2011 1 commit
-
-
keuchel@chromium.org authored
Both classes have been merged into a single ScopeInfo class that implements the functionality from both. This CL does not adapt the broken gdb-jit interface. Review URL: http://codereview.chromium.org/8352039 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9868 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 25 Oct, 2011 1 commit
-
-
mstarzinger@chromium.org authored
This implementation extends the internal ObjectHashTable to be able to hold arbitrary objects (e.g. Smis, Strings, ...) as keys by applying specialized hashing functions to primitive types. Equality of keys is defined using the internal SameValue function. R=rossberg@chromium.org BUG=v8:1622 TEST=mjsunit/harmony/collections Review URL: http://codereview.chromium.org/8372027 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9777 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Oct, 2011 1 commit
-
-
vegorov@chromium.org authored
R=erik.corry@gmail.com Review URL: http://codereview.chromium.org/8360004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9735 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 19 Oct, 2011 1 commit
-
-
danno@chromium.org authored
BUG=none TEST=test/mjsunit/array-literal.js Review URL: http://codereview.chromium.org/8258015 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9698 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 17 Oct, 2011 1 commit
-
-
lrn@chromium.org authored
Make instanceof work correctly. BUG=v8:893 Review URL: http://codereview.chromium.org/8199004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9659 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 10 Oct, 2011 1 commit
-
-
fschneider@chromium.org authored
Fix a use of the hole value and the undefined value before initialization when initializing V8. Before we just read a NULL value from them. Review URL: http://codereview.chromium.org/8130002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9557 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 06 Oct, 2011 1 commit
-
-
kmillikin@chromium.org authored
Instead of expecting Object** arrays at the outermost level, expect Handle<Object> arrays and reinterpret_cast them only just before invoking the generated code. R=rossberg@chromium.org,fschneider@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/8133020 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9537 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Oct, 2011 1 commit
-
-
rossberg@chromium.org authored
R=ricow@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/8138003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9524 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 23 Sep, 2011 1 commit
-
-
svenpanne@chromium.org authored
In some special (but probably very common) cases we can do better than loading from a global cell for these global properties by emitting the corresponding constant directly. This opens up opportunities for further improvements, coming in a separate CL... Review URL: http://codereview.chromium.org/7992002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9409 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Sep, 2011 2 commits
-
-
danno@chromium.org authored
Activated by the flag --smi-only-arrays Currently not crankshaft support, using flag on non-ia32 platforms will lead to write barrier misses and crashes. BUG=none TEST=elements_kind.js Review URL: http://codereview.chromium.org/7901016 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9392 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
Rehome some Object/JSReceiver/JSObject methods. R=ricow@chromium.org,kmillikin@chromium.org BUG=v8:1543 TEST= Review URL: http://codereview.chromium.org/7795055 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9381 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Sep, 2011 1 commit
-
-
fschneider@chromium.org authored
Original code review: http://codereview.chromium.org/7889046/ Review URL: http://codereview.chromium.org/7978028 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9365 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 Sep, 2011 1 commit
-
-
danno@chromium.org authored
Support sharing maps after an changing an object's ElementsKind for element kinds other then external elements. R=svenpanne@chromium.org BUG=none TEST=external-arrays.js Review URL: http://codereview.chromium.org/7862036 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9304 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 13 Sep, 2011 1 commit
-
-
rossberg@chromium.org authored
Introduce new %Apply native. Extend Execution::Call to optionally handle receiver rewriting (needed for %Apply). Fix Function.prototype.bind for functions that have .apply modified. R=kmillikin@chromium.org BUG=v8:1543 TEST= Review URL: http://codereview.chromium.org/7623011 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9258 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Sep, 2011 1 commit
-
-
danno@chromium.org authored
R=jkummrow@chromium.org BUG=none TEST=none Review URL: http://codereview.chromium.org/7787007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9214 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 11 Aug, 2011 1 commit
-
-
keuchel@chromium.org authored
BUG= TEST= Review URL: http://codereview.chromium.org/7549008 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8911 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 28 Jul, 2011 1 commit
-
-
mstarzinger@chromium.org authored
R=vitalyr@chromium.org TEST=cctest/test-dictionary Review URL: http://codereview.chromium.org/7385006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8761 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 18 Jul, 2011 1 commit
-
-
rossberg@chromium.org authored
R=ager@chromium.org BUG=v8:1543 TEST= Review URL: http://codereview.chromium.org/7391001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 05 Jul, 2011 1 commit
-
-
ricow@chromium.org authored
Due to issues relating mostly to chrome extensions we have lately been running into OOMs that are caused by our executable space running out. This change introduces flushing of code from regexps if we have not used the code for 5 mark sweeps. The approach is different from the normal function code flusing. Here we make a copy of the code inside the data array, and exchange the original code with a smi determined by the sweep_generation (a new heap variable increased everytime we do mark sweep/compact). If we encounter a smi in EnsureCompiled we simply reinstate the code object. If, in the marking phase of mark sweep, we find a regexp that already have a smi in the code field, and this is more than 5 generations old we flush the code from the saved index. Review URL: http://codereview.chromium.org/7282026 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8532 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 29 Jun, 2011 1 commit
-
-
kmillikin@chromium.org authored
Before: allocation of a catch or with context fetched the closure to store in the context from the previous context in the context chain. Now: the closure is passed explicitly. R=ager@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7275022 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8453 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 27 Jun, 2011 1 commit
-
-
lrn@chromium.org authored
Review URL: http://codereview.chromium.org/7240025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8426 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 22 Jun, 2011 1 commit
-
-
sandholm@chromium.org authored
Review URL: http://codereview.chromium.org/7230006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8369 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 16 Jun, 2011 1 commit
-
-
karlklose@chromium.org authored
This reverts commit ceb31498b9d69edca3260820fb4047045891ce6d. TBR=kmillikin@chromium.org Review URL: http://codereview.chromium.org/7172030 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8308 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 15 Jun, 2011 1 commit
-
-
karlklose@chromium.org authored
Review URL: http://codereview.chromium.org/7167006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8300 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 14 Jun, 2011 1 commit
-
-
kmillikin@chromium.org authored
Before, they had no extra slots and an extension object with one named property. Now, they use the extension slot for the property name and have an extra slot for the thrown object. This increases the size of the context itself, but removes overall allocation and eliminates a level of indirection. R=ager@chromium.org Review URL: http://codereview.chromium.org/7152002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8277 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Jun, 2011 2 commits
-
-
kmillikin@chromium.org authored
Introduce separate maps for function and with contexts. Use the function context map for testing whether a context is a function context (global contexts are no longer function contexts). Split the paths for allocating with and catch contexts. Rename some functions. Generally refactor code to make it simpler. R=ager@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7003058 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8231 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
Under a flag without IC or Crankshaft support. BUG=none TEST=none Review URL: http://codereview.chromium.org/7089002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8229 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 24 May, 2011 1 commit
-
-
ricow@chromium.org authored
The current json parser and scanner inherits fromt he normal scanners and parsers, which are more complicated than we need for parsing json. The supplied scanner works directly on the string supplied and has a fast case mode for scanning only ascii characters (it will simply create a substring or a symbol directly from the existing string). To allow for creating symbols from a substring I have added a SubStringAsciiSymbolKey that creates the hash based from our string without extracting the sub-string. In case we need to add the symbol it simply creates the symbol directly from the characters inside the given string. Review URL: http://codereview.chromium.org/7039037 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8029 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-