- 26 Mar, 2015 16 commits
-
-
pcc authored
This variant avoids a constant pool entry, which can be problematic when LTO'ing. It is also slightly shorter. R=bmeurer@chromium.org,Jacob.Bramley@arm.com BUG=chromium:453195 LOG=n Review URL: https://codereview.chromium.org/986643004 Cr-Commit-Position: refs/heads/master@{#27474}
-
verwaest authored
Instead of CanRetainOtherContext, we now manually blacklist all access-checked objects. BUG= Review URL: https://codereview.chromium.org/1020803004 Cr-Commit-Position: refs/heads/master@{#27473}
-
yangguo authored
Revert of Revert of Debugger: deduplicate shared function info when setting script break points. (patchset #1 id:1 of https://codereview.chromium.org/999273003/) Reason for revert: Reland since the failure has been fixed in https://codereview.chromium.org/1035523005/ Original issue's description: > Revert of Debugger: deduplicate shared function info when setting script break points. (patchset #4 id:60001 of https://codereview.chromium.org/998253005/) > > Reason for revert: > Code caching failures. > > Original issue's description: > > Debugger: deduplicate shared function info when setting script break points. > > > > Also fix Debug.showBreakPoints for multiple break points at the same location. > > > > BUG=v8:3960 > > LOG=N > > > > Committed: https://crrev.com/73b17a71a22564c0b66d9aa7c00948c748f5b290 > > Cr-Commit-Position: refs/heads/master@{#27444} > > TBR=mstarzinger@chromium.org > NOPRESUBMIT=true > NOTREECHECKS=true > NOTRY=true > BUG=v8:3960 > > Committed: https://crrev.com/9b29d008dfcc00bf56be8040add1d2c5e404673b > Cr-Commit-Position: refs/heads/master@{#27448} TBR=mstarzinger@chromium.org BUG=v8:3960 LOG=N Review URL: https://codereview.chromium.org/1037013002 Cr-Commit-Position: refs/heads/master@{#27472}
-
yangguo authored
R=jochen@chromium.org Review URL: https://codereview.chromium.org/1035523005 Cr-Commit-Position: refs/heads/master@{#27471}
-
titzer authored
BUG= Review URL: https://codereview.chromium.org/1021713005 Cr-Commit-Position: refs/heads/master@{#27470}
-
titzer authored
R=jarin@chromium.org BUG= Review URL: https://codereview.chromium.org/1037913002 Cr-Commit-Position: refs/heads/master@{#27469}
-
titzer authored
R=bmeurer@chromium.org BUG= Review URL: https://codereview.chromium.org/1019803005 Cr-Commit-Position: refs/heads/master@{#27468}
-
ishell authored
BUG=chromium:470801 LOG=Y Review URL: https://codereview.chromium.org/1020853022 Cr-Commit-Position: refs/heads/master@{#27467}
-
yurys authored
Before this patch the embedder could assign timestamp to the last interval after calling GetHeapStats. This would be slightly different from the timstamps assigned by v8 internally and written into heap snapshot. This patch allow to avoid this small discrepancy by returning timestamp along with last heap stats update. BUG=chromium:467222 LOG=Y Review URL: https://codereview.chromium.org/1037803002 Cr-Commit-Position: refs/heads/master@{#27466}
-
svenpanne authored
LOG=n Review URL: https://codereview.chromium.org/1013753016 Cr-Commit-Position: refs/heads/master@{#27465}
-
yangguo authored
R=ulan@chromium.org Review URL: https://codereview.chromium.org/1005053004 Cr-Commit-Position: refs/heads/master@{#27464}
-
michael_dawson authored
The value returned on AIX for platform.machine() is not the best value to map the architecture from. Use platform.system to determine if we are on AIX and if so set host_arch to ppc64 as AIX 6.1 (the earliest supported) only provides a 64 bit kernel AIX was reporting warning that offset may be used uninitialized modified: build/detect_v8_host_arch.py modified: build/standalone.gypi modified: src/hydrogen-bce.cc R=mbrandy@us.ibm.com, jkummerow@chromium.org BUG= Review URL: https://codereview.chromium.org/1006583004 Cr-Commit-Position: refs/heads/master@{#27463}
-
v8-autoroll authored
Rolling v8/tools/clang to ea2f0a2d96ffc6f5a51c034db704ccc1a6543156 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1032223004 Cr-Commit-Position: refs/heads/master@{#27462}
-
chunyang.dai authored
port 6689cc27 (r27377) original commit message: Handlers should be in charge of this work. The change uncovered a bug in vector-ics related to keyed loads into strings. It's important for StringCharCodeAtGenerator, a helper used in full code and in LoadIndexedStringStub (a handler) to protect the vector and slot registers when it makes a runtime call to convert a HeapNumber to a Smi. It's still possible for the handler to MISS after this call, perhaps due to out of bounds access. In that case, the vector and slot registers need to be delivered safely to the MISS handler. BUG= Review URL: https://codereview.chromium.org/1033733005 Cr-Commit-Position: refs/heads/master@{#27461}
-
chunyang.dai authored
port d21fd154 (r27316) original commit message: [es6] implement Reflect.apply() & Reflect.construct() BUG= Review URL: https://codereview.chromium.org/1021723006 Cr-Commit-Position: refs/heads/master@{#27460}
-
chunyang.dai authored
port bef80fcf (r27344) original commit message: [es6] generate rest parameters correctly for subclass constructors BUG= Review URL: https://codereview.chromium.org/1033643002 Cr-Commit-Position: refs/heads/master@{#27459}
-
- 25 Mar, 2015 24 commits
-
-
kozyatinskiy authored
This method uses in messages.js in GetSourceLine and GetPositionInLine. This methods uses in v8::Message API methods and there is no documentation about it. Method looks obsolete. One of the strange side effect is shown by attached issue. BUG=chromium:468781 TBR=yangguo@chromium.org LOG=Y Review URL: https://codereview.chromium.org/1033973002 Cr-Commit-Position: refs/heads/master@{#27458}
-
machenbach authored
Revert of add access checks to receivers on function callbacks (patchset #5 id:80001 of https://codereview.chromium.org/1036743004/) Reason for revert: This seems to lead to lots of timeouts of layout tests, e.g.: http://build.chromium.org/p/client.v8/builders/V8-Blink%20Linux%2064/builds/2807 Original issue's description: > add access checks to receivers on function callbacks > > R=verwaest@chromium.org > BUG=468451 > LOG=N > > Committed: https://crrev.com/255528710b0a128eef7b66827d9ac43e44650ff4 > Cr-Commit-Position: refs/heads/master@{#27452} TBR=verwaest@chromium.org,dcarney@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=468451 Review URL: https://codereview.chromium.org/1023783009 Cr-Commit-Position: refs/heads/master@{#27457}
-
jacob.bramley authored
This fixes warnings on some compilers. BUG= Review URL: https://codereview.chromium.org/1038623002 Cr-Commit-Position: refs/heads/master@{#27456}
-
titzer authored
R=vogelheim@chromium.org BUG= Review URL: https://codereview.chromium.org/1023753008 Cr-Commit-Position: refs/heads/master@{#27455}
-
titzer authored
R=mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/1026023004 Cr-Commit-Position: refs/heads/master@{#27454}
-
michael_dawson authored
Port 38a719f9 Original commit message: This switches full-codegen to no longer push and pop StackHandler markers onto the operand stack, but relies on a range-based handler table instead. We only use StackHandlers in JSEntryStubs to mark the transition from C to JS code. Note that this makes deoptimization and OSR from within any try-block work out of the box, makes the non-exception paths faster and should overall be neutral on the memory footprint (pros). On the other hand it makes the exception paths slower and actually throwing and exception more expensive (cons). TEST=cctest/test-run-jsexceptions/DeoptTry R=yangguo@chromium.org, R=mbrandy@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1035533004 Cr-Commit-Position: refs/heads/master@{#27453}
-
dcarney authored
R=verwaest@chromium.org BUG=468451 LOG=N Review URL: https://codereview.chromium.org/1036743004 Cr-Commit-Position: refs/heads/master@{#27452}
-
ulan authored
BUG=chromium:450824 LOG=NO Review URL: https://codereview.chromium.org/1038663002 Cr-Commit-Position: refs/heads/master@{#27451}
-
machenbach authored
BUG=v8:3838 LOG=n TBR=ulan@chromium.org Review URL: https://codereview.chromium.org/1012993007 Cr-Commit-Position: refs/heads/master@{#27450}
-
yurys authored
The method was deprecated a while ago: https://crrev.com/87e4bba31eabfd3b12e42b5886dc9da08d2daf13 LOG=Y BUG=YES API=Remove v8::Isolate::ClearInterrupt Review URL: https://codereview.chromium.org/1032623007 Cr-Commit-Position: refs/heads/master@{#27449}
-
yangguo authored
Revert of Debugger: deduplicate shared function info when setting script break points. (patchset #4 id:60001 of https://codereview.chromium.org/998253005/) Reason for revert: Code caching failures. Original issue's description: > Debugger: deduplicate shared function info when setting script break points. > > Also fix Debug.showBreakPoints for multiple break points at the same location. > > BUG=v8:3960 > LOG=N > > Committed: https://crrev.com/73b17a71a22564c0b66d9aa7c00948c748f5b290 > Cr-Commit-Position: refs/heads/master@{#27444} TBR=mstarzinger@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:3960 Review URL: https://codereview.chromium.org/999273003 Cr-Commit-Position: refs/heads/master@{#27448}
-
mstarzinger authored
This adapts the debugger so that the first break event starting the stepping process can come from optimized code. TurboFan supports a debugger statement and hence can be the top-most frame whenever the Debug::HandleDebugBreak handler is triggered. R=yangguo@chromium.org TEST=mjsunit/debug,cctest/test-debug Review URL: https://codereview.chromium.org/1038613002 Cr-Commit-Position: refs/heads/master@{#27447}
-
michael_dawson authored
R=mbrandy@us.ibm.com, svenpanne@chromium.org BUG= Review URL: https://codereview.chromium.org/1035723003 Cr-Commit-Position: refs/heads/master@{#27446}
-
machenbach authored
NOTRY=true Review URL: https://codereview.chromium.org/1030813003 Cr-Commit-Position: refs/heads/master@{#27445}
-
yangguo authored
Also fix Debug.showBreakPoints for multiple break points at the same location. BUG=v8:3960 LOG=N Review URL: https://codereview.chromium.org/998253005 Cr-Commit-Position: refs/heads/master@{#27444}
-
balazs.kilvady authored
Port 38a719f9 Original commit message: This switches full-codegen to no longer push and pop StackHandler markers onto the operand stack, but relies on a range-based handler table instead. We only use StackHandlers in JSEntryStubs to mark the transition from C to JS code. Note that this makes deoptimization and OSR from within any try-block work out of the box, makes the non-exception paths faster and should overall be neutral on the memory footprint (pros). On the other hand it makes the exception paths slower and actually throwing and exception more expensive (cons). TEST=cctest/test-run-jsexceptions/DeoptTry BUG= Review URL: https://codereview.chromium.org/1037743002 Cr-Commit-Position: refs/heads/master@{#27443}
-
alexandre.rames authored
BUG= Review URL: https://codereview.chromium.org/1003383004 Cr-Commit-Position: refs/heads/master@{#27442}
-
dusan.milosavljevic authored
TEST= BUG= Review URL: https://codereview.chromium.org/1031113002 Cr-Commit-Position: refs/heads/master@{#27441}
-
mstarzinger authored
This switches full-codegen to no longer push and pop StackHandler markers onto the operand stack, but relies on a range-based handler table instead. We only use StackHandlers in JSEntryStubs to mark the transition from C to JS code. Note that this makes deoptimization and OSR from within any try-block work out of the box, makes the non-exception paths faster and should overall be neutral on the memory footprint (pros). On the other hand it makes the exception paths slower and actually throwing and exception more expensive (cons). R=yangguo@chromium.org TEST=cctest/test-run-jsexceptions/DeoptTry Review URL: https://codereview.chromium.org/1010883002 Cr-Commit-Position: refs/heads/master@{#27440}
-
verwaest authored
BUG=chromium:434952 LOG=n Review URL: https://codereview.chromium.org/1035613003 Cr-Commit-Position: refs/heads/master@{#27439}
-
dslomov authored
R=verwaest@chromium.org BUG=chromium:470113 LOG=N Review URL: https://codereview.chromium.org/1034523002 Cr-Commit-Position: refs/heads/master@{#27438}
-
mstarzinger authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/1029583009 Cr-Commit-Position: refs/heads/master@{#27437}
-
dcarney authored
TBR=verwaest@chromium.org BUG= Review URL: https://codereview.chromium.org/1036843002 Cr-Commit-Position: refs/heads/master@{#27436}
-
mvstanton authored
Tests for non-clearing of weak cells in LoadICs weren't running when vector ICs are enabled. R=ulan@chromium.org BUG= Review URL: https://codereview.chromium.org/1032843002 Cr-Commit-Position: refs/heads/master@{#27435}
-