- 01 Jul, 2015 35 commits
-
-
littledan authored
Conditionally including Array and TypedArray methods seems to cause a slowdown in V8 context creation, possibly due to the new code added. BUG=chromium:504629 R=adamk@chromium.org LOG=Y Review URL: https://codereview.chromium.org/1215863003 Cr-Commit-Position: refs/heads/master@{#29430}
-
erikcorry authored
R=hpayer@chromium.org BUG= Review URL: https://codereview.chromium.org/1217813012 Cr-Commit-Position: refs/heads/master@{#29429}
-
adamk authored
This was added in https://chromium.googlesource.com/v8/v8/+/4a709dd65, but the only check for it that remained in the final patch is inside a DCHECK. It appears that the approach for checking use of class names in methods evolved quite a bit over the review of the original patch. Review URL: https://codereview.chromium.org/1219993002 Cr-Commit-Position: refs/heads/master@{#29428}
-
verwaest authored
BUG= Review URL: https://codereview.chromium.org/1220883006 Cr-Commit-Position: refs/heads/master@{#29427}
-
binji authored
This is more consistent with the DOM API, and is clearer w.r.t. which values are available in the lexical environment of the Worker. BUG=chromium:497295 R=jarin@chromium.org LOG=n Review URL: https://codereview.chromium.org/1218553004 Cr-Commit-Position: refs/heads/master@{#29426}
-
Djordje.Pesic authored
Disabling rsqrt and recip for mips32r1 in assembler, disassembler and simulator Review URL: https://codereview.chromium.org/1221663006 Cr-Commit-Position: refs/heads/master@{#29425}
-
Toon Verwaest authored
TBR=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1213683005. Cr-Commit-Position: refs/heads/master@{#29424}
-
verwaest authored
Checking for native context is faster than checking for global object. Additionally it speeds up the case were it actually is the native context, while not slowing down the alternative case. The bootstrapper only needs to access the native context from the native context, so this avoids the expensive fallback. BUG= Review URL: https://codereview.chromium.org/1214903017 Cr-Commit-Position: refs/heads/master@{#29423}
-
Toon Verwaest authored
TBR=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1220053002. Cr-Commit-Position: refs/heads/master@{#29422}
-
mbrandy authored
Port 7015fd20 Original commit message: Up until now the context register was listed explicitly in each stub's CallInterfaceDescriptor. This was problematic, because it was listed first in the list of register parameters--which is fine for Crankshaft, which is more or less built to handle the context as the first parameter-- but not ideal for TurboFan, which adds the context at the end of all function parameters. Now the context register is no longer in the register list and can be handled appropriately by both compilers. Specifically, this allows the FunctionType specified for each CallInterfaceDescriptor to exactly match the parameter register list. R=danno@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1218463004 Cr-Commit-Position: refs/heads/master@{#29421}
-
akos.palfi authored
Fixes debug mode assertions. TEST=cctest/test-run-machops/RunChangeUint32ToFloat64_B BUG= Review URL: https://codereview.chromium.org/1211143003 Cr-Commit-Position: refs/heads/master@{#29420}
-
verwaest authored
BUG=chromium:505998 LOG=n Review URL: https://codereview.chromium.org/1222543003 Cr-Commit-Position: refs/heads/master@{#29419}
-
Toon Verwaest authored
BUG= R=jkummerow@chromium.org Review URL: https://codereview.chromium.org/1215593005. Cr-Commit-Position: refs/heads/master@{#29418}
-
mstarzinger authored
This makes sure that all pointer fields in an entry in the optimized code map are considered weak, not just the code object. If just one field of an entry dies, then the whole entry dies. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1217813013 Cr-Commit-Position: refs/heads/master@{#29417}
-
mbrandy authored
This change makes the patching logic less prone to errors in the face of variable instruction mov sequences. R=dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1213383003 Cr-Commit-Position: refs/heads/master@{#29416}
-
mstarzinger authored
This extends the existing support for --noflush-optimized-code-cache mechanism to the newly added context-independent code entry in the optimized code map. Note that this machanism is still off by default. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1220883002 Cr-Commit-Position: refs/heads/master@{#29415}
-
verwaest authored
This change changes bootstrapping semantics for intercepted global objects. Unlike before, we'll now also call into the interceptor during bootstrapping. This affects properties loaded from within the runtime, such as global.Array and global.Symbol. The embedder will need to make sure that those values are the expected values during bootstrapping. BUG=chromium:505998 LOG=n Review URL: https://codereview.chromium.org/1220813005 Cr-Commit-Position: refs/heads/master@{#29414}
-
chunyang.dai authored
port 7a63bf77 (r29358). original commit message: This makes new.target work in [[Call]] and [[Construct]] of ordinary functions. We achieve this by introducing a new construct stub for functions that uses the new.target variable. The construct stub pushes the original constructor just above the receiver in the construct frame. BUG= Review URL: https://codereview.chromium.org/1217083004 Cr-Commit-Position: refs/heads/master@{#29413}
-
chunyang.dai authored
port 876ae425 (r29292). original commit message: The stack layout was different for different ports. BUG= Review URL: https://codereview.chromium.org/1219823002 Cr-Commit-Position: refs/heads/master@{#29412}
-
chunyang.dai authored
port 8a3cf4ec (r29310). BUG= Review URL: https://codereview.chromium.org/1213373002 Cr-Commit-Position: refs/heads/master@{#29411}
-
chunyang.dai authored
port 9e7af9ef (r29280). original commit message: It's useful for the megamorphic keyed store case to not require a vector and slot as input. Analogous to the load case, we have a dummy one-ic-slot vector to aid. Since the only kind of MISS is for megamorphic cache stub failures, we don't need the real vector. The reason is that megamorphic cache stub failures don't result in any change to the type feedback vector state. BUG= Review URL: https://codereview.chromium.org/1212653011 Cr-Commit-Position: refs/heads/master@{#29410}
-
chunyang.dai authored
port c1a4f747 (r29281). original commit message: The idea is that TurboFan can use this information for more intelligent inlining. BUG= Review URL: https://codereview.chromium.org/1213723005 Cr-Commit-Position: refs/heads/master@{#29409}
-
chunyang.dai authored
port a58ba8d8 (r29279). original commit message: This introduces some initial building blocks for calling out to C/C++ functions directly from TurboFan generated code objects. BUG= Review URL: https://codereview.chromium.org/1214903007 Cr-Commit-Position: refs/heads/master@{#29408}
-
chunyang.dai authored
This CL fixes the following situations: 1, Operands are -0.0 or 0.0. it always return right value. 1, Operands contains NaN. it always return right value. BUG= Review URL: https://codereview.chromium.org/1214893004 Cr-Commit-Position: refs/heads/master@{#29407}
-
chunyang.dai authored
port c019d7f4 (r29248). original commit message: Use big-boy Types to annotate interface descriptor parameters - Thread Type::FunctionType through stubs and the TF pipeline. - Augment Typer to decorate parameter nodes with types from a Type::FunctionType associated with interface descriptors. - Factor interface descriptors into platform-specific and platform-independent components so that all descriptors share a common Type::FunctionType for all platforms. BUG= Review URL: https://codereview.chromium.org/1210463002 Cr-Commit-Position: refs/heads/master@{#29406}
-
mstarzinger authored
R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1216153004 Cr-Commit-Position: refs/heads/master@{#29405}
-
hablich authored
R=machenbach@chromium.org BUG=494641 LOG=N NOTRY=true Review URL: https://codereview.chromium.org/1217173003 Cr-Commit-Position: refs/heads/master@{#29404}
-
mstarzinger authored
R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1218003003 Cr-Commit-Position: refs/heads/master@{#29403}
-
danno authored
Up until now the context register was listed explicitly in each stub's CallInterfaceDescriptor. This was problematic, because it was listed first in the list of register parameters--which is fine for Crankshaft, which is more or less built to handle the context as the first parameter-- but not ideal for TurboFan, which adds the context at the end of all function parameters. Now the context register is no longer in the register list and can be handled appropriately by both compilers. Specifically, this allows the FunctionType specified for each CallInterfaceDescriptor to exactly match the parameter register list. Review URL: https://codereview.chromium.org/1211333003 Cr-Commit-Position: refs/heads/master@{#29402}
-
bmeurer authored
This operator< overload is rather dangerous for handles. And we don't actually need a std::set in the chunk builder, since duplicates are automatically eliminated later when the code dependencies are committed. R=jarin@chromium.org Review URL: https://codereview.chromium.org/1214573004 Cr-Commit-Position: refs/heads/master@{#29401}
-
yangguo authored
We now consistently ignore native and extension scripts for debugging. Only native scripts and extension scripts can disallow lazy compilation. So we can make sure that break points are only set to code that are compiled with debug break slots. R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1216193002 Cr-Commit-Position: refs/heads/master@{#29400}
-
v8-autoroll authored
Rolling v8/third_party/icu to 1b697da5c2c0112e2b70e7e75d3e3d985f464a8f TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1217893007 Cr-Commit-Position: refs/heads/master@{#29399}
-
chunyang.dai authored
port 8196c28a (r29238). original commit message: JSConstructStub for subclass constructors instead locates new.target in a known location on the stack. BUG= Review URL: https://codereview.chromium.org/1207613003 Cr-Commit-Position: refs/heads/master@{#29398}
-
chunyang.dai authored
port 882055ff (r29082). The original CL covers part of X87 port. This CL addes the missing changes. original commit message: - fix truthfulness of comments - use InitializeFieldsWithFiller more consistently - use unsigned comparisons for pointers No change in functionality intended. Bonus: improve JavaScriptFrame::Print() for an enhanced debugging experience: BUG= Review URL: https://codereview.chromium.org/1210153007 Cr-Commit-Position: refs/heads/master@{#29397}
-
adamk authored
The enumerable expression in a for-in/of loop is supposed to have a TDZ for any lexically bound names in that loop (there can be more than one with destructuring). This patch accomplishes this with an almost-correct desugaring. The only thing missing is proper debugger support (the let declarations added by the desugaring, while invisible to code due to shadowing, are visible to the debugger). BUG=v8:4210 LOG=n Review URL: https://codereview.chromium.org/1218543003 Cr-Commit-Position: refs/heads/master@{#29396}
-
- 30 Jun, 2015 5 commits
-
-
bradnelson authored
The asm.js spec decides the type of numeric literals in several places based on if they contain a ".". http://asmjs.org/spec/latest/ Adding methods so that AST Literals can be checked for containg a dot. Adding a cctest that this information is available. LOG=N BUG= https://code.google.com/p/v8/issues/detail?id=4203 TEST=test-parsing R=rossberg@chromium.org,titzer@chromium.org Review URL: https://codereview.chromium.org/1201783003 Cr-Commit-Position: refs/heads/master@{#29395}
-
binji authored
BUG=chromium:497295 R=jarin@chromium.org LOG=n Review URL: https://codereview.chromium.org/1216023003 Cr-Commit-Position: refs/heads/master@{#29394}
-
machenbach authored
Revert of [test262-es6] Update to 2011-06-29 (patchset #1 id:1 of https://codereview.chromium.org/1220793005/) Reason for revert: [Sheriff] Runner has some infra failures: http://build.chromium.org/p/client.v8/builders/V8%20Linux64%20-%20debug/builds/4020/steps/Test262-es6%20-%20no%20variants/logs/stdio Original issue's description: > [test262-es6] Update to 2011-06-29 > > This includes one harness fix but introduces a few new failures. No > new bugs exposed though. > > BUG=N > LOG=N > R=littledan@chromium.org, adamk@chromium.org > > Committed: https://crrev.com/2e877628803f238dd33c3409413cd7778e36a2b6 > Cr-Commit-Position: refs/heads/master@{#29392} TBR=littledan@chromium.org,adamk@chromium.org,arv@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=N Review URL: https://codereview.chromium.org/1212163008 Cr-Commit-Position: refs/heads/master@{#29393}
-
arv authored
This includes one harness fix but introduces a few new failures. No new bugs exposed though. BUG=N LOG=N R=littledan@chromium.org, adamk@chromium.org Review URL: https://codereview.chromium.org/1220793005 Cr-Commit-Position: refs/heads/master@{#29392}
-
mbrandy authored
This resolves the mirror-object test failure. R=dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1214903009 Cr-Commit-Position: refs/heads/master@{#29391}
-