- 06 May, 2016 25 commits
-
-
akos.palfi authored
MIPS: Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code. Port 117a56b7 BUG= Review-Url: https://codereview.chromium.org/1959653002 Cr-Commit-Position: refs/heads/master@{#36081}
-
cbruni authored
callstats.html in combination with callstats.py can be used to get an in-depth view on where we spend time in v8. Furthermore, with callstats.html we can compare different versions of v8/chrome and see where and how performnce evolved. Drive-by-fix: add missing copyrights header to ic-explorer.html and format ic-explorer.html BUG= Review-Url: https://codereview.chromium.org/1947413004 Cr-Commit-Position: refs/heads/master@{#36080}
-
ulan authored
This removes: - PersistentBase::SetWeak that takes WeakCallbackData. The embedders should use the version that takes WeakCallbackInfo. - PersistentBase::SetPhantom. The embedders should SetWeak that takes WeakCallbackInfo. Functions in DefaultPersistentValueMapTraits are changed to accept WeakCallbackInfo instead of WeakCallbackData. BUG=chromium:609808 LOG=NO Review-Url: https://codereview.chromium.org/1953263002 Cr-Commit-Position: refs/heads/master@{#36079}
-
jochen authored
We just deleted a persistent the line before, so make sure the context is cleared up before disposing the isolate R=ulan@chromium.org BUG= Review-Url: https://codereview.chromium.org/1953253003 Cr-Commit-Position: refs/heads/master@{#36078}
-
ulan authored
BUG=chromium:609808 LOG=NO Review-Url: https://codereview.chromium.org/1954033002 Cr-Commit-Position: refs/heads/master@{#36077}
-
mattloring authored
Hydrogen logs are ambiguous if multiple functions share the same name. This change adds file names to this output. Functions are now named <file_name>:<function_name> to reduce this ambiguity. R=ofrobots@google.com BUG= Review-Url: https://codereview.chromium.org/1913973004 Cr-Commit-Position: refs/heads/master@{#36076}
-
ishell authored
Deoptimizer is now able to reconstruct topmost accessor and constructor frames. BUG=chromium:608278, v8:4698 LOG=N TBR=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/1936043002 Cr-Commit-Position: refs/heads/master@{#36075}
-
ulan authored
BUG=chromium:609808 LOG=NO Review-Url: https://codereview.chromium.org/1949393006 Cr-Commit-Position: refs/heads/master@{#36074}
-
cbruni authored
- Cleanup CL to remove unused parameters in elements.cc. Additionally use fields from the KeyAccumulator wherever possible. - Make method names in KeyAccumulator more consistent BUG= Review-Url: https://codereview.chromium.org/1944703002 Cr-Commit-Position: refs/heads/master@{#36073}
-
jochen authored
BUG=chromium:609107 R=machenbach@chromium.org LOG=n Review-Url: https://codereview.chromium.org/1955723003 Cr-Commit-Position: refs/heads/master@{#36072}
-
jkummerow authored
Because not initializing fields can be, you know, dangerous. Review-Url: https://codereview.chromium.org/1952703002 Cr-Commit-Position: refs/heads/master@{#36071}
-
nikolaos authored
R=cbruni@chromium.org BUG= LOG=N Review-Url: https://codereview.chromium.org/1922873004 Cr-Commit-Position: refs/heads/master@{#36070}
-
mstarzinger authored
R=jarin@chromium.org Review-Url: https://codereview.chromium.org/1945363002 Cr-Commit-Position: refs/heads/master@{#36069}
-
mstarzinger authored
This moves all the machinery for tracing inlined function that is specific to Crankshaft into the appropriate component. Only the old side-channel via a list of InlinedFunctionInfo structs remained within the CompilationInfo for now. In the long run we will reconstruct that information from the deoptimization data on the code objects. R=bmeurer@chromium.org Review-Url: https://codereview.chromium.org/1944323002 Cr-Commit-Position: refs/heads/master@{#36068}
-
clemensh authored
This changes different locations to extract the reference to the wasm object and the function index from the stack trace, and make it available through all the APIs which process stack traces. The javascript CallSite object now has the new methods isWasm(), getWasmObject() and getWasmFunctionIndex(); the byte offset is available via getPosition(). Function names of wasm frames should be fully functional with this commit, position information works reliably for calls, but not for traps like unreachable or out-of-bounds accesses. R=titzer@chromium.org, yangguo@chromium.org Review-Url: https://codereview.chromium.org/1909353002 Cr-Commit-Position: refs/heads/master@{#36067}
-
titzer authored
Revert of [turbofan] Take the immediate size in account when narrowing ia32/x64 word comparison operators. (patchset #2 id:20001 of https://codereview.chromium.org/1948453002/ ) Reason for revert: Breaks WASM; please also add tests when relanding. Original issue's description: > [turbofan] Take the immediate size in account when narrowing ia32/x64 word comparison operators. > > Before this patch, we would emit a cmp or test with a memory operand only if both of the operands in the IR were loads. Now if either of them is a load and the other one is an immediate, we can use a memory operand if the load representation machine size is wide enough to represent the latter. > > Committed: https://crrev.com/a0543313dbd46b0c2e72c91ee3488a7dc6db73e4 > Cr-Commit-Position: refs/heads/master@{#36009} TBR=bmeurer@chromium.org,jfb@chromium.org,epertoso@chromium.org # Not skipping CQ checks because original CL landed more than 1 days ago. Review-Url: https://codereview.chromium.org/1959603002 Cr-Commit-Position: refs/heads/master@{#36066}
-
machenbach authored
BUG=v8:4280 LOG=N NOTRY=true TBR=rmcilroy@chromium.org Review-Url: https://codereview.chromium.org/1956663002 Cr-Commit-Position: refs/heads/master@{#36065}
-
machenbach authored
BUG=v8:4995 LOG=n NOTRY=true TBR=thakis@chromium.org, titzer@chromium.org Review-Url: https://codereview.chromium.org/1955013002 Cr-Commit-Position: refs/heads/master@{#36064}
-
bmeurer authored
This operator was initially designed to handle arbitrary effect merging for effect relaxation, but we don't do that (at least currently). So no need to keep the dead operator around. R=jarin@chromium.org Review-Url: https://codereview.chromium.org/1954983002 Cr-Commit-Position: refs/heads/master@{#36063}
-
mbrandy authored
R=bmeurer@chromium.org, jarin@chromium.org BUG= Review-Url: https://codereview.chromium.org/1945303003 Cr-Commit-Position: refs/heads/master@{#36062}
-
zhengxing.li authored
port d2efbf25 (r36000) original commit message: BUG= Review-Url: https://codereview.chromium.org/1947363002 Cr-Commit-Position: refs/heads/master@{#36061}
-
jochen authored
I want to stop using d8 from the chromium build, so we could potentially use it for running tests. BUG=chromium:609107 R=machenbach@chromium.org LOG=n Review-Url: https://codereview.chromium.org/1944353002 Cr-Commit-Position: refs/heads/master@{#36060}
-
v8-autoroll authored
Rolling v8/build to 119d5305247498fdd8a215b8e2b6c50223ac7d4b Rolling v8/tools/clang to 0bb0462a91310d88ab9d124d8db54a70c9e1d1b0 TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/1953813004 Cr-Commit-Position: refs/heads/master@{#36059}
-
zhengxing.li authored
X87: Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code. port 117a56b7 (r36044) original commit message: - Add new RelocInfo mode WASM_MEMORY_SIZE_REFERENCE in the assembler and add relocation information to immediates in compare instructions. - Use relocatable constants for MemSize/BoundsCheck in the wasm compiler BUG= Review-Url: https://codereview.chromium.org/1947413003 Cr-Commit-Position: refs/heads/master@{#36058}
-
zhengxing.li authored
X87: [turbofan] Take the immediate size in account when narrowing ia32/x64 word comparison operators. port a0543313 (r36009) original commit message: Before this patch, we would emit a cmp or test with a memory operand only if both of the operands in the IR were loads. Now if either of them is a load and the other one is an immediate, we can use a memory operand if the load representation machine size is wide enough to represent the latter. BUG= Review-Url: https://codereview.chromium.org/1954963002 Cr-Commit-Position: refs/heads/master@{#36057}
-
- 05 May, 2016 9 commits
-
-
jyan authored
S390: Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code. port 117a56b7 Original commit message: - Add new RelocInfo mode WASM_MEMORY_SIZE_REFERENCE in the assembler and add relocation information to immediates in compare instructions. - Use relocatable constants for MemSize/BoundsCheck in the wasm compiler R=gdeepti@chromium.org, joransiu@ca.ibm.com, mbrandy@us.ibm.com, bjaideep@ca.ibm.com, michael_dawson@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/1955593003 Cr-Commit-Position: refs/heads/master@{#36056}
-
mtrofin authored
BUG= Review-Url: https://codereview.chromium.org/1931293005 Cr-Commit-Position: refs/heads/master@{#36055}
-
bjaideep authored
PPC: Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code. Port 117a56b7 Original commit message: - Add new RelocInfo mode WASM_MEMORY_SIZE_REFERENCE in the assembler and add relocation information to immediates in compare instructions. - Use relocatable constants for MemSize/BoundsCheck in the wasm compiler R=gdeepti@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, mbrandy@us.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/1948263003 Cr-Commit-Position: refs/heads/master@{#36054}
-
akos.palfi authored
Port 81cb8411 BUG= Review-Url: https://codereview.chromium.org/1957463002 Cr-Commit-Position: refs/heads/master@{#36053}
-
titzer authored
R=bradnelson@chromium.org,rossberg@chromium.org BUG= Review-Url: https://codereview.chromium.org/1951013002 Cr-Commit-Position: refs/heads/master@{#36052}
-
zhengxing.li authored
port af677d7b (r35998) original commit message: https://codereview.chromium.org/1938213002 added xchg_b and xchg_w, but didn't add it to the disassembler, and there were no tests that caught it. BUG= Review-Url: https://codereview.chromium.org/1947843002 Cr-Commit-Position: refs/heads/master@{#36051}
-
v8-autoroll authored
Rolling v8/build to f80756f5df1d90cf1113a2ce335147482e36f65e Rolling v8/buildtools to 731bdb2af8b5839450605ddebdcf5de749cf9d17 Rolling v8/tools/clang to ee715658a19a60fc73b02532a077d9c96f291331 Rolling v8/tools/gyp to 02b145a1a4f4e1c62e8bae06045caf852d9ef17f TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Review-Url: https://codereview.chromium.org/1945103004 Cr-Commit-Position: refs/heads/master@{#36050}
-
zhengxing.li authored
port 81cb8411 (r35993) original commit message: BUG= Review-Url: https://codereview.chromium.org/1947833002 Cr-Commit-Position: refs/heads/master@{#36049}
-
zhengxing.li authored
port fa570e55 (r35963) original commit message: BUG= Review-Url: https://codereview.chromium.org/1952583002 Cr-Commit-Position: refs/heads/master@{#36048}
-
- 04 May, 2016 6 commits
-
-
adamk authored
R=littledan@chromium.org BUG=v8:4974 LOG=n Review-Url: https://codereview.chromium.org/1949223002 Cr-Commit-Position: refs/heads/master@{#36047}
-
adamk authored
Scope analysis is over-conservative when treating variable resolutions as possibly-shadowed by a sloppy eval. In the attached bug, this comes into play since catch scopes have different behavior with respect to the "calls eval" in eager vs lazy compilation (in the latter, they are never marked as "calls eval" because CatchContexts don't have an associated ScopeInfo). This patch changes the scope-type check to also eliminate a few other cases where shadowing isn't possible, such as non-declaration block scopes. BUG=chromium:608279 LOG=n Review-Url: https://codereview.chromium.org/1950803002 Cr-Commit-Position: refs/heads/master@{#36046}
-
mike authored
As per the ES2015 spec, the value `-0` should be converted to `+0` prior to invocation of the species constructor. BUG=v8:4988 LOG=N R=littledan@chromium.org Review-Url: https://codereview.chromium.org/1950073002 Cr-Commit-Position: refs/heads/master@{#36045}
-
gdeepti authored
Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code. - Add new RelocInfo mode WASM_MEMORY_SIZE_REFERENCE in the assembler and add relocation information to immediates in compare instructions. - Use relocatable constants for MemSize/BoundsCheck in the wasm compiler R=titzer@chromium.org, yangguo@chromium.org, bradnelson@chromium.org Review-Url: https://codereview.chromium.org/1921203002 Cr-Commit-Position: refs/heads/master@{#36044}
-
mbrandy authored
TEST=mjsunit/array-constructor R=joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com, bjaideep@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/1947233002 Cr-Commit-Position: refs/heads/master@{#36043}
-
alph authored
BUG=v8:4959 LOG=N Review-Url: https://codereview.chromium.org/1949693003 Cr-Commit-Position: refs/heads/master@{#36042}
-