- 16 Feb, 2015 17 commits
-
-
ishell@chromium.org authored
TBR=verwaest@chromium.org Review URL: https://codereview.chromium.org/923943003 Cr-Commit-Position: refs/heads/master@{#26668}
-
ishell authored
Previous approach for property reconfiguration was to create a free-floating map with generalized representations of all fields. This patch does it right. When property is reconfigured either by changing its kind (kData <-> kAccessor) or its attributes it implies creation of a new branch in transition tree. If such a branch already existed before reconfiguration then it should be merged with the old (or source) branch of the transition tree. Merging procedure includes all the heavy machinery such as property location changes (kDescriptor -> kField), field representation/field type generalization, map deprecation, etc. Review URL: https://codereview.chromium.org/888623002 Cr-Commit-Position: refs/heads/master@{#26667}
-
titzer authored
R=jarin@chromium.org LOG=Y BUG=chromium:458876 Review URL: https://codereview.chromium.org/917383004 Cr-Commit-Position: refs/heads/master@{#26666}
-
jarin authored
BUG=chromium:458987 LOG=n R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/932603002 Cr-Commit-Position: refs/heads/master@{#26665}
-
svenpanne authored
The heuristic is quite naive at the moment (build a frame iff the register allocator needed spill slots), we can improve that later. Review URL: https://codereview.chromium.org/933603002 Cr-Commit-Position: refs/heads/master@{#26664}
-
rodolph.perfetta authored
BUG= Review URL: https://codereview.chromium.org/927083002 Cr-Commit-Position: refs/heads/master@{#26663}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/932583002 Cr-Commit-Position: refs/heads/master@{#26662}
-
jarin authored
BUG=chromium:454158 LOG=n R=bmeurer@chromium.org Review URL: https://codereview.chromium.org/922623002 Cr-Commit-Position: refs/heads/master@{#26661}
-
yangguo authored
R=vogelheim@chromium.org BUG=chromium:441896 LOG=N Review URL: https://codereview.chromium.org/922573003 Cr-Commit-Position: refs/heads/master@{#26660}
-
machenbach authored
BUG=chromium:457022 TBR=tandrii@chromium.org NOTRY=true LOG=n TEST=./script_test.py Review URL: https://codereview.chromium.org/918953003 Cr-Commit-Position: refs/heads/master@{#26659}
-
tfarina authored
See more information in the gn-dev mailing list: https://groups.google.com/a/chromium.org/d/msg/gn-dev/j-P5hlvZ13M/4CSw2WworlkJ Also in https://chromium.googlesource.com/chromium/src/+/61a6fca4bca5438bf4338184c29fded55e5f240e BUG=374271 R=machenbach@chromium.org LOG=N Review URL: https://codereview.chromium.org/917243002 Cr-Commit-Position: refs/heads/master@{#26658}
-
machenbach authored
BUG=chromium:451975 TBR=tandrii@chromium.org NOTRY=true LOG=n TEST=./script_test.py Review URL: https://codereview.chromium.org/925313002 Cr-Commit-Position: refs/heads/master@{#26657}
-
ishell authored
This avoids potential mess with different compilation modes. Review URL: https://codereview.chromium.org/934533002 Cr-Commit-Position: refs/heads/master@{#26656}
-
svenpanne authored
Removed useless (and in the future incorrect) DCHECKs on the way. Review URL: https://codereview.chromium.org/921443004 Cr-Commit-Position: refs/heads/master@{#26655}
-
svenpanne authored
Use simple old-skool constructors instead. Note that the long repeated member initializer lists could be reduced a bit by using C++11's brace-or-equal initializers, which are actually recommended by the Google C++ style guide in this case, but the ARM toolchain is still buggy in this area (see patch sets 1 and 2). :-/ Review URL: https://codereview.chromium.org/913993004 Cr-Commit-Position: refs/heads/master@{#26654}
-
yangguo authored
and "Just visit young array buffers during scavenge. Additionally keep the views in new space in a separate global list and move them to the corresponding array buffers when they get promoted." This reverts commit 295ab278 and commit bd61a85f. TBR=hpayer@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/929973002 Cr-Commit-Position: refs/heads/master@{#26653}
-
v8-autoroll authored
Rolling v8/tools/clang to 21c0f1864716dbe8d8d4061c18efbde7c49b6a6a TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/930743002 Cr-Commit-Position: refs/heads/master@{#26652}
-
- 15 Feb, 2015 5 commits
-
-
balazs.kilvady authored
Added new INTERNAL_REFERENCE_ENCODED RelocInfo type to differentiate MIPS existing use of internal references in instructions from the new raw pointer reference needed for dd(Label*). BUG= TEST=cctest/test-assembler-mips/jump_tables1, cctest/test-assembler-mips/jump_tables2, cctest/test-assembler-mips/jump_tables3, cctest/test-run-machops/RunSwitch1 Review URL: https://codereview.chromium.org/922043005 Cr-Commit-Position: refs/heads/master@{#26651}
-
machenbach authored
Revert of Don't always bail out of GenerateTypedArrayInitialize (patchset #1 id:1 of https://codereview.chromium.org/922393003/) Reason for revert: Speculative revert. This CL seems to break octane. Original issue's description: > Don't always bail out of GenerateTypedArrayInitialize > > In an innocuous cleanup patch, https://code.google.com/p/v8/source/detail?r=21621, > some boolean logic got mixed up and the Hydrogen code for TypedArrayInitialize > was changed to always bail out. This swaps the logic appropriately. > > Committed: https://crrev.com/907f0b6ce573333f1cbca00db5cb1df1ead175bb > Cr-Commit-Position: refs/heads/master@{#26643} TBR=dslomov@chromium.org,adamk@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review URL: https://codereview.chromium.org/929773002 Cr-Commit-Position: refs/heads/master@{#26650}
-
chunyang.dai authored
port 8bb2e397 (r26645). original commit message: BUG= Review URL: https://codereview.chromium.org/929763002 Cr-Commit-Position: refs/heads/master@{#26649}
-
chunyang.dai authored
port 5c119485 (r26478). original commit message: Assembler support for internal references. BUG= Review URL: https://codereview.chromium.org/920503002 Cr-Commit-Position: refs/heads/master@{#26648}
-
chunyang.dai authored
port 2707d4c9 (r26628). original commit message: This CL fixes tests that no longer valid and also fixes two issues: 1. 'super()' in non derived constructors. 2. Failure to step into derived constructors. BUG= Review URL: https://codereview.chromium.org/920543005 Cr-Commit-Position: refs/heads/master@{#26647}
-
- 14 Feb, 2015 2 commits
-
-
v8-autoroll authored
Rolling v8/buildtools to 5c5e924788fe40f7d6e0a3841ac572de2475e689 Rolling v8/tools/clang to d5f568673280ba9180bbf0b913b571786c9f352a TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/929643002 Cr-Commit-Position: refs/heads/master@{#26646}
-
caitpotter88 authored
LOG=Y BUG=v8:2159 R=dslomov@chromium.org, arv@chromium.org, marja@chromium.org Review URL: https://codereview.chromium.org/816913003 Cr-Commit-Position: refs/heads/master@{#26645}
-
- 13 Feb, 2015 11 commits
-
-
arv authored
With the new ES6 semantics super construct calls are only valid in a constructor in a derived class. This is something that is statically known and we report early SyntaxError in case it occurs. We therefore do not need to track this any more. BUG=v8:3330 LOG=N R=dslomov@chromium.org, adamk Review URL: https://codereview.chromium.org/924123002 Cr-Commit-Position: refs/heads/master@{#26644}
-
adamk authored
In an innocuous cleanup patch, https://code.google.com/p/v8/source/detail?r=21621, some boolean logic got mixed up and the Hydrogen code for TypedArrayInitialize was changed to always bail out. This swaps the logic appropriately. Review URL: https://codereview.chromium.org/922393003 Cr-Commit-Position: refs/heads/master@{#26643}
-
arv authored
The preparser needs to log the usage of super properties and then update the scope when we create the function later. BUG=v8:3888 LOG=N R=dslomov@chromium.org, marja Review URL: https://codereview.chromium.org/923683002 Cr-Commit-Position: refs/heads/master@{#26642}
-
arv authored
BUG=None LOG=N R=mstarzinger@chromium.org, dslomov@chromium.org Review URL: https://codereview.chromium.org/926013002 Cr-Commit-Position: refs/heads/master@{#26641}
-
bratell authored
StatisticsExtension::GetCounters() has grown to repeat a lot of code so to make it more maintainable and generate less machine code, make it data driven. This makes a 64 bit Linux build 50 KB smaller. Total change: -51677 bytes ========================== 1 shrunk, for a net change of -51677 bytes (64222 bytes before, 12545 bytes after) across 1 sources 279691 unchanged, totalling 51423668 bytes Per-source Analysis: ------------------------------------------------------------------------------------------------------------------- -51677 - Source: /home/bratell/src/chromium/src/v8/src/extensions/statistics-extension.cc - (gained 0, lost 51677) ------------------------------------------------------------------------------------------------------------------- Shrunk symbols: -51677: v8::internal::StatisticsExtension::GetCounters(v8::FunctionCallbackInfo<v8::Value> const&) type=t, (was 64222 bytes, now 12545 bytes) BUG= Review URL: https://codereview.chromium.org/912413003 Cr-Commit-Position: refs/heads/master@{#26640}
-
loislo authored
BUG=none LOG=n Review URL: https://codereview.chromium.org/922153002 Cr-Commit-Position: refs/heads/master@{#26639}
-
Ross McIlroy authored
The external_snapshot_blob is a global and might be accessed from multiple threads. Protect it with a lock. BUG=457656 LOG=N R=vogelheim@chromium.org Review URL: https://codereview.chromium.org/918213002 Cr-Commit-Position: refs/heads/master@{#26638}
-
Sven Panne authored
This removed some inconsistent/duplicated code and made the testing side entrance much simpler: Now it simply constructs a pipeline and hands off to the "tail" of the normal pipeline. R=danno@chromium.org Review URL: https://codereview.chromium.org/924823002 Cr-Commit-Position: refs/heads/master@{#26637}
-
loislo authored
It is a default option for some try bots. otherwise compilation fails on DCHECK(layout_descriptor->IsConsistentWithMap(*map)); BUG=none LOG=n Review URL: https://codereview.chromium.org/920993003 Cr-Commit-Position: refs/heads/master@{#26636}
-
Akos Palfi authored
Port 2707d4c9 Original commit message: This CL fixes tests that no longer valid and also fixes two issues: 1. 'super()' in non derived constructors. 2. Failure to step into derived constructors. BUG= R=paul.lind@imgtec.com Review URL: https://codereview.chromium.org/920173002 Cr-Commit-Position: refs/heads/master@{#26635}
-
Akos Palfi authored
Port fdcf3e59 BUG= R=paul.lind@imgtec.com Review URL: https://codereview.chromium.org/920543004 Cr-Commit-Position: refs/heads/master@{#26634}
-
- 12 Feb, 2015 5 commits
-
-
Erik Arvidsson authored
BUG=v8:3330 LOG=N R=dslomov@chromium.org Review URL: https://codereview.chromium.org/917933007 Cr-Commit-Position: refs/heads/master@{#26633}
-
Erik Arvidsson authored
BUG=v8:3885 LOG=N R=adamk@chromium.org, dslomov@chromium.org Review URL: https://codereview.chromium.org/916293004 Cr-Commit-Position: refs/heads/master@{#26632}
-
Dmitry Lomov authored
R=arv@chromium.org BUG=v8:3834 LOG=N Review URL: https://codereview.chromium.org/919643008 Cr-Commit-Position: refs/heads/master@{#26631}
-
loislo authored
1) create beefy RelocInfo table when cpu profiler is active, so if a function was optimized when profiler was active RelocInfo would get separate DeoptInfo for the each deopt case. 2) push DeoptInfo from CodeEntry to ProfileNode. When deopt happens we put the info collected on #1 into CodeEntry and record stack sample. On the sampling thread we grab the deopt data and append it to the corresponding ProfileNode deopts list. Sample profile dump. [Top down]: 0 (root) 0 #1 1 29 #2 1 test 29 #3 2 opt_function 29 #4 2 opt_function 29 #5 deopted at 118 with reason 'not a heap number' deopted at 137 with reason 'division by zero' BUG=452067 LOG=n Committed: https://crrev.com/ce8701b247d3c6604f24f17a90c02d17b4417f54 Cr-Commit-Position: refs/heads/master@{#26615} Review URL: https://codereview.chromium.org/919953002 Cr-Commit-Position: refs/heads/master@{#26630}
-
machenbach authored
This is needed as normal chromium checkouts don't fetch branch-heads. These branches will also be replicated by GitHub and are fetched when cloning from the repository. The expected object size will be the same or smaller than before as we currently push the same information onto the candidates branch (which already is in refs/heads). The only difference is the increasing number of refs in refs/heads. BUG=chromium:451975 TBR=tandrii@chromium.org NOTRY=true LOG=n TEST=./script_test.py TEST=tools/release/create_release.py -r machenbach@chromium.org -a machenbach@chromium.org --dry-run Review URL: https://codereview.chromium.org/914973002 Cr-Commit-Position: refs/heads/master@{#26629}
-