- 12 Nov, 2015 18 commits
-
-
ahaas authored
The least significant bit of the input value may affect the result of the conversion through rounding. We OR the least significant with the second least significant bit to preserve it over the SHR instruction. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1435203003 Cr-Commit-Position: refs/heads/master@{#31969}
-
yangguo authored
BUG=chromium:554946 LOG=y R=jkummerow@chromium.org, jochen@chromium.org Review URL: https://codereview.chromium.org/1435083003 Cr-Commit-Position: refs/heads/master@{#31968}
-
mbrandy authored
This test, as written, is invalid on platforms which use function descriptors. See https://codereview.chromium.org/1377423002/ for background. R=mstarzinger@chromium.org, titzer@chromium.org, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1438803002 Cr-Commit-Position: refs/heads/master@{#31967}
-
adamk authored
Because the Scope will be optimized away by the call to FinalizeBlockScope in the case where there are no lexical declarations in the block, this should have no effect on anything downstream from the Parser, and simply removes duplicate parsing code. Due to the change from ParseStatement to ParseStatementListItem, this will result in slightly different error messages for lexical declarations in sloppy mode (until those are shipped). R=littledan@chromium.org, rossberg@chromium.org CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1433743005 Cr-Commit-Position: refs/heads/master@{#31966}
-
adamk authored
BUG=v8:2160 LOG=y Review URL: https://codereview.chromium.org/1438753002 Cr-Commit-Position: refs/heads/master@{#31965}
-
evan.lucas authored
Instead of basing matches off of whitespace, walk the inheritance chain and include any classes that inherit from Object. R=machenbach@chromium.org,jkummerow@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1435643002 Cr-Commit-Position: refs/heads/master@{#31964}
-
mbrandy authored
Remove hard-coded assumption of large object size threshold. This test fails on PPC in version 4.7 where the threshold is derived directly from the allocator's pagesize. R=hpayer@chromium.org, mstarzinger@chromium.org, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1440723002 Cr-Commit-Position: refs/heads/master@{#31963}
-
jkummerow authored
BUG=v8:1543 LOG=n Review URL: https://codereview.chromium.org/1438233002 Cr-Commit-Position: refs/heads/master@{#31962}
-
fedor authored
BUG= R=machenbach Review URL: https://codereview.chromium.org/1439763002 Cr-Commit-Position: refs/heads/master@{#31961}
-
bmeurer authored
Now JSIntrinsicLowering can also lower %_IsSpecObject intrinsics to a diamond. R=mstarzinger@chromium.org Review URL: https://codereview.chromium.org/1436943005 Cr-Commit-Position: refs/heads/master@{#31960}
-
ishell authored
This CL fixes several sources of non-predictability by making Platform::MonotonicallyIncreasingTime() the only bottleneck for all time-querying functions and providing PredictablePlatform implementation. Review URL: https://codereview.chromium.org/1415383004 Cr-Commit-Position: refs/heads/master@{#31959}
-
bmeurer authored
Only inline one candidate per iteration to make sure we really inline the stuff that is called most often. R=mstarzinger@chromium.org BUG=v8:4493, v8:4544 LOG=n Review URL: https://codereview.chromium.org/1439773003 Cr-Commit-Position: refs/heads/master@{#31958}
-
bmeurer authored
This adds initial support for fast inline allocations of JSObject instances. It currently has exactly the same limitations as Crankshaft. R=mstarzinger@chromium.org BUG=v8:4544 LOG=n Review URL: https://codereview.chromium.org/1441573004 Cr-Commit-Position: refs/heads/master@{#31957}
-
yangguo authored
R=jkummerow@chromium.org BUG=chromium:523919 LOG=N Review URL: https://codereview.chromium.org/1440983002 Cr-Commit-Position: refs/heads/master@{#31956}
-
mstarzinger authored
This passes both, the actual constructor and the original constructor, to nodes having the {JSCreate} operator. This is required for allocating properly subclassed implicit receiver objects. R=verwaest@chromium.org BUG=v8:4544 LOG=n Review URL: https://codereview.chromium.org/1434873004 Cr-Commit-Position: refs/heads/master@{#31955}
-
mstarzinger authored
This implements a first version of support for constructor call inlining in the inlining machinery. For now we can only inline calls where the actual constructor and the original constructor coincide (i.e. no super constructor calls). Note that the target of a super constructor call is loaded with a runtime call, so there is no way for it to be constant promoted at the moment. R=bmeurer@chromium.org BUG=v8:4544 LOG=n Review URL: https://codereview.chromium.org/1435873002 Cr-Commit-Position: refs/heads/master@{#31954}
-
bmeurer authored
With subclassing and @@toStringTag, %_ClassOf is not necessarily what you want for ES6 anymore, so better avoid relying on %_ClassOf in our builtins. R=yangguo@chromium.org Review URL: https://codereview.chromium.org/1439003002 Cr-Commit-Position: refs/heads/master@{#31953}
-
v8-autoroll authored
Rolling v8/tools/clang to 0b258f75323161e854038f30334e97ab6aa58eab TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1440623005 Cr-Commit-Position: refs/heads/master@{#31952}
-
- 11 Nov, 2015 20 commits
-
-
bradnelson authored
The ~ operator is de-sugared into true^x, which was being improperly handled. Adding tests of most bitwise operators and several error cases. BUG= https://code.google.com/p/v8/issues/detail?id=4203 TEST=test-asm-validator R=titzer@chromium.org,aseemgarg@chromium.org LOG=N Review URL: https://codereview.chromium.org/1432423003 Cr-Commit-Position: refs/heads/master@{#31951}
-
mbrandy authored
R=joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1440813002 Cr-Commit-Position: refs/heads/master@{#31950}
-
mbrandy authored
R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1440733002 Cr-Commit-Position: refs/heads/master@{#31949}
-
ofrobots authored
Presently the inline allocation step is a static value defined to be the minimum of the step sizes over all the observers. The step occur every (approx.) step byte. This is unfair to observers whose steps are not evenly divisible by the min step size. For example, consider two observers with steps sizes of 512 and 576 bytes. Across 16kb allocated, you would expect the first observer to be hit approximately 32 times, and the second observer to be hit approximately 28 times. In reality, the observers get notified 30 and 15 times respectively. The reason is that each step is 512 bytes, and since 576 is not evenly divisible by 512, it gets notified much less frequently. This CL fixes the problem by making the next step size be the minimum (over all observers) of the remaining bytes to get to the step, making the steps fair. BUG= R=hpayer@chromium.org,ulan@chromium.org Review URL: https://codereview.chromium.org/1427973006 Cr-Commit-Position: refs/heads/master@{#31948}
-
fedor authored
I have discovered need in those values when writing: https://github.com/indutny/llnode BUG= Review URL: https://codereview.chromium.org/1436473002 Cr-Commit-Position: refs/heads/master@{#31947}
-
ahaas authored
I don't see obvious implementations for mips64 and ppc64, so I would need help for these two platforms. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1436943002 Cr-Commit-Position: refs/heads/master@{#31946}
-
mbrandy authored
Check whether a trampoline pool should be emitted after unblocking. Otherwise, back-to-back sequences which block the trampoline pool can cause it to be out of reach. R=joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1433343002 Cr-Commit-Position: refs/heads/master@{#31945}
-
bmeurer authored
R=mstarzinger@chromium.org BUG=v8:4493 LOG=n Review URL: https://codereview.chromium.org/1432223002 Cr-Commit-Position: refs/heads/master@{#31944}
-
bmeurer authored
Extend the element access specialization to also allow non-JSArray fast packed elements, which now includes unaliased sloppy and strict arguments. R=jarin@chromium.org BUG=v8:4470 LOG=n Review URL: https://codereview.chromium.org/1433193003 Cr-Commit-Position: refs/heads/master@{#31943}
-
bmeurer authored
Change sloppy and strict arguments objects to FAST_ELEMENTS for their backing stores, which will allow us to optimize them easier. Also fixes a bug in the elements accessors that was triggered by this change. R=verwaest@chromium.org Review URL: https://codereview.chromium.org/1433133003 Cr-Commit-Position: refs/heads/master@{#31942}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1436813002 Cr-Commit-Position: refs/heads/master@{#31941}
-
jarin authored
Review URL: https://codereview.chromium.org/1439583002 Cr-Commit-Position: refs/heads/master@{#31940}
-
machenbach authored
This is for disabling 9.2.2. for release on arm64 (approximating a bit). BUG=v8:4280 LOG=N NOTRY=True TBR=rmcilroy@chromium.org Review URL: https://codereview.chromium.org/1432183002 Cr-Commit-Position: refs/heads/master@{#31939}
-
bmeurer authored
Support lowering of Function.prototype.call in the JSBuiltinReducer, which is actually straightforward because of the way we represent JS calls in TurboFan. Currently we cannot inline the actual target yet, since inlining still runs before typed lowering, but that will be possible as well soon(ish). R=jarin@chromium.org Review URL: https://codereview.chromium.org/1439533002 Cr-Commit-Position: refs/heads/master@{#31938}
-
paul.lind authored
Use 64-bit add for address. TEST=mjsunit/sparse-array.js, others. BUG= Review URL: https://codereview.chromium.org/1435793002 Cr-Commit-Position: refs/heads/master@{#31937}
-
v8-autoroll authored
Rolling v8/buildtools to 4a95614772d9bcbd8bc197e1d9bd034e088fc740 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review URL: https://codereview.chromium.org/1439503002 Cr-Commit-Position: refs/heads/master@{#31936}
-
zhengxing.li authored
port 1e277012 (r31914) original commit message: Avoid write barriers when storing values in the root set, and use cheaper write barriers for storing maps or tagged pointers. Also improve the generated code for write barriers, utilizing the out of line code mechanism that is available to TurboFan backends, which moves the unlikely case out of the hot path. BUG= Review URL: https://codereview.chromium.org/1435743003 Cr-Commit-Position: refs/heads/master@{#31935}
-
zhengxing.li authored
X87: Support fast-path allocation for subclass constructors with correctly initialized initial maps. port b9d25d86 (r31913) original commit message: BUG= Review URL: https://codereview.chromium.org/1434853002 Cr-Commit-Position: refs/heads/master@{#31934}
-
mbrandy authored
R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1409073016 Cr-Commit-Position: refs/heads/master@{#31933}
-
mostynb authored
Changing this value is not guaranteed to work yet, but it needs to be an arg in order to experiment with it. Review URL: https://codereview.chromium.org/1427343003 Cr-Commit-Position: refs/heads/master@{#31932}
-
- 10 Nov, 2015 2 commits
-
-
mbrandy authored
R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, dstence@us.ibm.com BUG= Review URL: https://codereview.chromium.org/1413833013 Cr-Commit-Position: refs/heads/master@{#31931}
-
http://crrev.com/1367953002epertoso authored
This CL is in preparation for the API change introduced in http://crrev.com/1407313004. BUG= Review URL: https://codereview.chromium.org/1434693008 Cr-Commit-Position: refs/heads/master@{#31930}
-