- 17 Nov, 2015 14 commits
-
-
yangguo authored
Revert of Experimental support for RegExp lookbehind. (patchset #18 id:340001 of https://codereview.chromium.org/1418963009/ ) Reason for revert: gc stress breaks due to string_start_minus_one not being set correctly. Original issue's description: > Experimental support for RegExp lookbehind. > > R=erikcorry@chromium.org, littledan@chromium.org > BUG=v8:4545 > LOG=N > > Committed: https://crrev.com/37632606bbce1418238b13fd90cb6ef6705871cd > Cr-Commit-Position: refs/heads/master@{#32029} TBR=littledan@chromium.org,erikcorry@chromium.org,erikcorry@google.com NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:4545 Review URL: https://codereview.chromium.org/1451373003 Cr-Commit-Position: refs/heads/master@{#32032}
-
ahaas authored
and ppc64. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1438013003 Cr-Commit-Position: refs/heads/master@{#32031}
-
ishell authored
Minor cleanup in VisitorId selection. Review URL: https://codereview.chromium.org/1448313002 Cr-Commit-Position: refs/heads/master@{#32030}
-
yangguo authored
R=erikcorry@chromium.org, littledan@chromium.org BUG=v8:4545 LOG=N Review URL: https://codereview.chromium.org/1418963009 Cr-Commit-Position: refs/heads/master@{#32029}
-
jarin authored
Review URL: https://codereview.chromium.org/1452113002 Cr-Commit-Position: refs/heads/master@{#32028}
-
ishell authored
Review URL: https://codereview.chromium.org/1453043003 Cr-Commit-Position: refs/heads/master@{#32027}
-
mythria authored
Adds implementation and tests for following operators in bytecode graph builder: -VisitLoadICSloppy -VisitLoadICStrict -VisitLoadICSloppyWide -VisitLoadICStrictWide The current implementation introduces empty frame states for frame state inputs expected by these operations. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1419373007 Cr-Commit-Position: refs/heads/master@{#32026}
-
jarin authored
BUG=chromium:556543 LOG=n Review URL: https://codereview.chromium.org/1450883003 Cr-Commit-Position: refs/heads/master@{#32025}
-
zhengxing.li authored
port e5edd66d (r32022) original commit message: This is the first part to refactoring the JSNativeContextSpecialization class, which has grown way too big recently. Also don't collect cross context feedback for the CallIC in general. Neither TurboFan nor Crankshaft can make any use of cross context JSFunction feedback that is collected by the CallIC, so there's no point in gathering that feedback at all (it just complicates the checking that is necessary in the compilers). What we should do instead at some point (when Crankshaft becomes less important) is to collect the SharedFunctionInfo as feedback for those cases. BUG= Review URL: https://codereview.chromium.org/1453033002 Cr-Commit-Position: refs/heads/master@{#32024}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1442643009 Cr-Commit-Position: refs/heads/master@{#32023}
-
bmeurer authored
This is the first part to refactoring the JSNativeContextSpecialization class, which has grown way too big recently. Also don't collect cross context feedback for the CallIC in general. Neither TurboFan nor Crankshaft can make any use of cross context JSFunction feedback that is collected by the CallIC, so there's no point in gathering that feedback at all (it just complicates the checking that is necessary in the compilers). What we should do instead at some point (when Crankshaft becomes less important) is to collect the SharedFunctionInfo as feedback for those cases. R=yangguo@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1451273002 Cr-Commit-Position: refs/heads/master@{#32022}
-
v8-autoroll authored
Rolling v8/buildtools to 277db9302c7ff55beee2a9daf380675dc03bea83 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1454553003 Cr-Commit-Position: refs/heads/master@{#32021}
-
adamk authored
- Removed PASS/FAIL line for arrow/rest params test which should now pass. - Moved soon-to-be-changed tests about built-in prototypes as plain objects to INVALID section (and noted that they'll be fixed with the next test262 roll). R=littledan@chromium.org Review URL: https://codereview.chromium.org/1450243002 Cr-Commit-Position: refs/heads/master@{#32020}
-
dusan.m.milosavljevic authored
TEST= BUG= Review URL: https://codereview.chromium.org/1453573002 Cr-Commit-Position: refs/heads/master@{#32019}
-
- 16 Nov, 2015 18 commits
-
-
dusan.m.milosavljevic authored
TEST= BUG= Review URL: https://codereview.chromium.org/1446363002 Cr-Commit-Position: refs/heads/master@{#32018}
-
balazs.kilvady authored
BUG=chromium:555543 LOG=N Review URL: https://codereview.chromium.org/1448033002 Cr-Commit-Position: refs/heads/master@{#32017}
-
adamk authored
All uses of Token::INIT also have access to the relevant VariableMode, so there's no reason to have more than one token representing an initializing assignment. Review URL: https://codereview.chromium.org/1431873006 Cr-Commit-Position: refs/heads/master@{#32016}
-
mbrandy authored
Port 34b7b21d Original commit message: If inline allocation fails, we can just use the %NewObject fallback, which will do the right thing. We don't need a dedicated fallback to %AllocateInNewSpace. R=bmeurer@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1448063002 Cr-Commit-Position: refs/heads/master@{#32015}
-
jochen authored
BUG=none R=verwaest@chromium.org,rossberg@chromium.org,bmeurer@chromium.org,neis@chromium.org LOG=y Review URL: https://codereview.chromium.org/1413463006 Cr-Commit-Position: refs/heads/master@{#32014}
-
ofrobots authored
While all allocated objects need to have correct alignment, this requirement doesn't make a lot of sense for the allocation limit. Removing this assertion would makes it possible to make the inline-allocation-observers accurate. This could be done in other ways, but removing this assertion is the most elegant way to go about it. R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/1444883003 Cr-Commit-Position: refs/heads/master@{#32013}
-
bmeurer authored
This adds support for load/store access to FAST_HOLEY_ELEMENTS and FAST_HOLEY_SMI_ELEMENTS backing stores. We don't currently fully support the double holes, because we make some difficult assumptions in Crankshaft there. R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1448903002 Cr-Commit-Position: refs/heads/master@{#32012}
-
jochen authored
BUG=4134 R=epertoso@chromium.org LOG=n Review URL: https://codereview.chromium.org/1451733002 Cr-Commit-Position: refs/heads/master@{#32011}
-
mlippautz authored
Revert of Reland "[heap] Turn on parallel compaction" (patchset #1 id:1 of https://codereview.chromium.org/1444283002/ ) Reason for revert: Looks like tasks are still scheduled during isolate shutdown after waiting for remaining tasks: https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20arm64%20-%20sim%20-%20MSAN/builds/5310/ Original issue's description: > Reland "[heap] Turn on parallel compaction" > > This reverts commit e6820480. > > BUG=chromium:524425 > LOG=N > CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg;tryserver.v8:v8_linux_gc_stress_dbg;tryserver.v8:v8_mac_gc_stress_dbg;tryserver.v8:v8_linux64_msan_rel;tryserver.v8:v8_linux64_tsan_rel > > Committed: https://crrev.com/c82d2323ffd5c399ba37da389ba0cdc72f46c97f > Cr-Commit-Position: refs/heads/master@{#32009} TBR=hpayer@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:524425 Review URL: https://codereview.chromium.org/1445093002 Cr-Commit-Position: refs/heads/master@{#32010}
-
mlippautz authored
This reverts commit e6820480. BUG=chromium:524425 LOG=N CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg;tryserver.v8:v8_linux_gc_stress_dbg;tryserver.v8:v8_mac_gc_stress_dbg;tryserver.v8:v8_linux64_msan_rel;tryserver.v8:v8_linux64_tsan_rel Review URL: https://codereview.chromium.org/1444283002 Cr-Commit-Position: refs/heads/master@{#32009}
-
yangguo authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1448803003 Cr-Commit-Position: refs/heads/master@{#32008}
-
mlippautz authored
This way we can properly cancel them on the main thread in case they never get scheduled by the platform. BUG=chromium:524425 LOG=N CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg;tryserver.v8:v8_linux_gc_stress_dbg;tryserver.v8:v8_mac_gc_stress_dbg;tryserver.v8:v8_linux64_msan_rel;tryserver.v8:v8_linux64_tsan_rel;tryserver.v8:v8_mac64_asan_rel Review URL: https://codereview.chromium.org/1446523003 Cr-Commit-Position: refs/heads/master@{#32007}
-
jkummerow authored
Next step: expose it to JS and test it. BUG=v8:1543 LOG=n R=cbruni@chromium.org Review URL: https://codereview.chromium.org/1439353004 Cr-Commit-Position: refs/heads/master@{#32006}
-
ahaas authored
The TiesEven rounding mode rounds float64 numbers to the nearest integer. If there are two nearest integers, then the number is rounded to the even one. This is the default rounding mode according to IEEE~754. I implemented the operator on ia32, x64, arm, arm64, mips, and mips64. I think there is a bug in the current implementation of the ppc simulator, which kept me from implementing the operator on ppc. According to my understanding of the ppc instruction manual, the FRIN instruction provides the right behavior for Float64RoundTiesEven. In the simulator, however, FRIN provides a different semantics. If there are two nearest integers, then the simulator returns the one which is further away form 0. Review URL: https://codereview.chromium.org/1440293002 Cr-Commit-Position: refs/heads/master@{#32005}
-
ahaas authored
I implemented it on x64, ia32, arm, arm64, mips, mips64, and ppc. Review URL: https://codereview.chromium.org/1444583002 Cr-Commit-Position: refs/heads/master@{#32004}
-
bmeurer authored
Extend the ElementAccessInfo machinery with support for elements kind transitions, which can be either in-place updates of the map (i.e. when going from FAST_SMI_ELEMENTS to FAST_ELEMENTS) or instance migrations utilizing the TransitionElementsKindStub. R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1452563002 Cr-Commit-Position: refs/heads/master@{#32003}
-
zhengxing.li authored
port 34b7b21d (r32000) original commit message: If inline allocation fails, we can just use the %NewObject fallback, which will do the right thing. We don't need a dedicated fallback to %AllocateInNewSpace. BUG= Review URL: https://codereview.chromium.org/1451603002 Cr-Commit-Position: refs/heads/master@{#32002}
-
zhengxing.li authored
port ff283f7d (r31987) original commit message: * Limit triggering of tail calls to explicit use of a new inline runtime function %_TailCall. %_TailCall works just like %_Call except for using tail-calling mechanics (currently only in TF). * Remove hack that recognized some specific usages of %_Call and converted them into tail calls. * Support tail calls for all calls where the number of callee stack parameters is less than or equal to the number of caller stack parameters. * Use the gap resolver to swizzle parameters and registers to tail calls. BUG= Review URL: https://codereview.chromium.org/1445023002 Cr-Commit-Position: refs/heads/master@{#32001}
-
- 15 Nov, 2015 3 commits
-
-
bmeurer authored
If inline allocation fails, we can just use the %NewObject fallback, which will do the right thing. We don't need a dedicated fallback to %AllocateInNewSpace. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1440193003 Cr-Commit-Position: refs/heads/master@{#32000}
-
paul.lind authored
From 60e7ea8a / https://codereview.chromium.org/1409993012 BUG= Review URL: https://codereview.chromium.org/1442143003 Cr-Commit-Position: refs/heads/master@{#31999}
-
v8-autoroll authored
Rolling v8/build/gyp to 33b351b2eda8facc464c89213fc8cd9919666c05 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1441243006 Cr-Commit-Position: refs/heads/master@{#31998}
-
- 14 Nov, 2015 1 commit
-
-
mlippautz authored
This change binds each {Cancelable} task to a so-called {CancelableTaskManager}, which is then used to handle concurrent cancelation as well as synchronizing shutdown for already running tasks. Since ownership of tasks is transferred to the platform executing a task (destructor), handling in the manager uses integer ids. Note that this also mitigates (modulo integer size) the ABA problem. All handling of {Cancelable} tasks is now encapsulated into the corresponding manager, which is instantiated for each isolate. R=hpayer@chromium.org BUG=chromium:524425 LOG=N CQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg;tryserver.v8:v8_linux_gc_stress_dbg;tryserver.v8:v8_mac_gc_stress_dbg;tryserver.v8:v8_linux64_msan_rel;tryserver.v8:v8_linux64_tsan_rel;tryserver.v8:v8_mac64_asan_rel Review URL: https://codereview.chromium.org/1409993012 Cr-Commit-Position: refs/heads/master@{#31997}
-
- 13 Nov, 2015 4 commits
-
-
mbrandy authored
Commit 20f3a077 broke platforms using embedded constant pools due to assumptions regarding stack frame layout. R=mtrofin@chromium.org, bmeurer@chromium.org, jarin@chromium.org, michael_dawson@ca.ibm.com BUG=v8:4548 LOG=n Review URL: https://codereview.chromium.org/1442273002 Cr-Commit-Position: refs/heads/master@{#31996}
-
adamk authored
The previous code did not properly check for harmony const when doing the dynamic redeclaration check. This was masked in the test because each eval had an initializer, and the initializer was what triggered the exception. This patch tightens the test by removing initializers and fixes the bug in DeclareLookupSlot. Also change the test to use assertThrows where possible. BUG=v8:4550 LOG=n Review URL: https://codereview.chromium.org/1437003006 Cr-Commit-Position: refs/heads/master@{#31995}
-
mbrandy authored
Port ff283f7d Original commit message: * Limit triggering of tail calls to explicit use of a new inline runtime function %_TailCall. %_TailCall works just like %_Call except for using tail-calling mechanics (currently only in TF). * Remove hack that recognized some specific usages of %_Call and converted them into tail calls. * Support tail calls for all calls where the number of callee stack parameters is less than or equal to the number of caller stack parameters. * Use the gap resolver to swizzle parameters and registers to tail calls. R=danno@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG=v8:4076 LOG=n Review URL: https://codereview.chromium.org/1442143002 Cr-Commit-Position: refs/heads/master@{#31994}
-
mlippautz authored
There is no need to require kRingbufferMaxSize samples for estimating the compaction speed, as the number is already quite stable with a single sample (which may include timings from compacting multiple pages). R=hpayer@chromium.org BUG=chromium:524425 LOG=N Review URL: https://codereview.chromium.org/1440423002 Cr-Commit-Position: refs/heads/master@{#31993}
-