- 15 May, 2018 21 commits
-
-
Clemens Hammacher authored
We were always using the instance we were currently building. If the start function is an exported wasm function of another instance, use the exporting instance instead. R=titzer@chromium.org Bug: chromium:843120 Change-Id: I141d272b947bef8e903be7208ddf6ce344e754c4 Reviewed-on: https://chromium-review.googlesource.com/1059620 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#53190}
-
jgruber authored
The (currently four, soon five) RelocIterator constructors contain basically identical logic. Refactor that into a basic version that all other constructors call. Bug: v8:6666 Change-Id: Ice7b4891d5e539ff6fe63337fc52d480d85dc270 Reviewed-on: https://chromium-review.googlesource.com/1059109 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#53189}
-
Igor Sheludko authored
In particular: * number of pointer fields * number embedder fields * number boxed fields * number of unboxed double field * number of raw data fields Bug: v8:7703 Change-Id: I22a310d941317a0f34f67536e55fbfab5f5354cd Reviewed-on: https://chromium-review.googlesource.com/1056532Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#53188}
-
Clemens Hammacher authored
Since the code around that is quite fragile, and I plan to refactor it, just add some tests to ensure that everything is and keeps working as intended. R=mstarzinger@chromium.org Bug: v8:7758 Change-Id: Ib3814b93b465286d70b5669ed0161eecb9fc925a Reviewed-on: https://chromium-review.googlesource.com/1059616Reviewed-by:
-
Tobias Tebbi authored
The sysroot only contains headers for gcc6, not gcc4.8 which is the version installed on the coverage bots. Bug: chromium:837238 Change-Id: Ifd9b53dae510b969b4ef5ec8c1c2684eb92a94fa Reviewed-on: https://chromium-review.googlesource.com/1059150Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#53186}
-
Clemens Hammacher authored
{ImportedFunctionEntry} offers two {set} methods: One takes a {JSReceiver*}, the other one a {WasmInstanceObject*}. Since {WasmInstanceObject} inherits from {JSReceiver}, it's quite easy to confuse the two if the instance is hold as e.g. {JSObject}. Hence, rename the methods to remove this ambiguity. R=titzer@chromium.org Bug: v8:7758 Change-Id: I06617a565faa561d3afc70085e0df3b528c715bb Reviewed-on: https://chromium-review.googlesource.com/1059147Reviewed-by: -
Clemens Hammacher authored
The interpreter entry was sometimes referred to as "interpreter stub" or "interpreter wrapper". Use the term "interpreter entry" consistently. R=titzer@chromium.org Bug: v8:7754 Change-Id: Ia06449c91300fca454c6afd5c82a789749d6b7d0 Reviewed-on: https://chromium-review.googlesource.com/1058794Reviewed-by:
-
Marja Hölttä authored
BUG=v8:7308 Change-Id: I12a38a6099f0ffd8718dc5cb77433baa75bc0411 Reviewed-on: https://chromium-review.googlesource.com/1059110 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#53183}
-
Clemens Hammacher authored
For generating the WasmCompileLazy builtin, we need to know the list of parameter registers in wasm. Instead of duplicating this, just use the existing array from wasm-linkage.h. R=titzer@chromium.org Change-Id: Ib552af7b6a3defbc9c8b48390244bf943306a4b7 Reviewed-on: https://chromium-review.googlesource.com/1057310Reviewed-by:
-
sreten.kovacevic authored
Since `at` register is used a lot in macro-assembler-mips, change usage of this register with `kScratchReg` and `kScratchReg2`. Also, remove TODO comments for unaligned memory access, since there is nothing that can be done about it. Change-Id: Ibf55c04a1f53521f34dfb483294de3010a0120c6 Reviewed-on: https://chromium-review.googlesource.com/1059347Reviewed-by:
Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Cr-Commit-Position: refs/heads/master@{#53181}
-
Marja Hölttä authored
Moving asserts from helpers to the call sites, so the failure messages are more helpful. BUG=v8:7308 Change-Id: I1da491d408c2e2a1017b1d3fe484b7b3d877a2cf Reviewed-on: https://chromium-review.googlesource.com/1058802Reviewed-by:
-
Sergiy Byelozyorov authored
This is needed since depot_tools may not be in PATH on LUCI bots. Using the copy of depot_tools that contains the recipes is also incorrect as it is not guaranteed to contain binaries that do not have corresponding recipe API, which does not apply to script called from a recipe. This also protects our release scripts from breaking due to arbitrary changes to depot_tools. Chromium also pins depot_tools for similar reasons: https://cs.chromium.org/chromium/src/DEPS?l=525&rcl=f24fa931ae08b0e42aae2d13034229088179da7f R=machenbach@chromium.org Bug: chromium:831171 Change-Id: I393052b1c489d25e2e3fa173149635448e9bd2dc Reviewed-on: https://chromium-review.googlesource.com/1054676Reviewed-by:
-
Marja Hölttä authored
BUG=v8:7308 Change-Id: I7720dbc84ce3e614f025759224e2d8d7ffa7a952 Reviewed-on: https://chromium-review.googlesource.com/1052013 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
-
Théotime Grohens authored
and comparison with a JS implementation using TypedArray Change-Id: Ifec9c19f23e182db25ad3e54edc3f60c6e6048f4 Reviewed-on: https://chromium-review.googlesource.com/1057729Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Théotime Grohens <theotime@google.com> Cr-Commit-Position: refs/heads/master@{#53177}
-
Michael Achenbach authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/1fd2d08..b61b6b6 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/3059fd7..e853531 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/a6f06bf..045e7f9 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/de94aab..51de78a Also added fixes for fuchsia-sdk and additional DEPS entry. TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Bug: chromium:840669 Change-Id: Ic0370c56e98118780f02758e5ea057bb9026bacd Reviewed-on: https://chromium-review.googlesource.com/1049305 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#53176}
-
Kanghua Yu authored
Change-Id: I647a1c175fb1a4f6fa764cc68c7b9c94d3b65817 Reviewed-on: https://chromium-review.googlesource.com/1053688 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#53175}
-
Sergiy Byelozyorov authored
This will aid with quickly finding the needed builder and verifying whether a given test definition is already present or not. R=machenbach@chromium.org No-Try: true Change-Id: I5a9b74925fa2bfb27f29434bb43045394b20cf18 Reviewed-on: https://chromium-review.googlesource.com/1053772 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
Simon Zünd authored
This CL changes the generated C++ code for LabeledStatementBlocks to only emit labels if they are used. Prior to this CL, when a label was only used on one path of an if constexpr expression, and not at all anywhere else, the try/label construct would BIND a label that was not used, causing a CSA verification error. R=tebbi@chromium.org Change-Id: Ia81a0cd081b84528c95bbdbdb98b9ab51928e13f Reviewed-on: https://chromium-review.googlesource.com/1057247Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Daniel Clifford <danno@chromium.org> Commit-Queue: Simon Zünd <szuend@google.com> Cr-Commit-Position: refs/heads/master@{#53173}
-
Michael Achenbach authored
NOTRY=true TBR=sergiyb@chromium.org Bug: chromium:837238 Change-Id: Ib10cb178b707eace50d77d20a732a106904167fb Reviewed-on: https://chromium-review.googlesource.com/1058790Reviewed-by:
-
Kanghua Yu authored
On IA architecture, arithmetic and shifting operations set the flags according to the computation result. subl rsi,0x1 REX.W movq rbx,[rbx+0x17] cmpl rsi, 0 <-- TO BE REDUCED jnz 0x3f54d2dcef0 ==> REX.W movq rbx,[rbx+0x17] subl rsi,0x1 jnz 0x3f54d2dcef0 & orl rdx,rbx cmpl rdx,0x0 <-- TO BE REDUCED jnz 0x3f54d22b0f5 ==> orl rdx,rbx jnz 0x3f54d22b0f5 Bug: chromium:842497, chromium:842501 Change-Id: I4e2c40861b76ac3f508b01ee27249e85eab3222f Reviewed-on: https://chromium-review.googlesource.com/1057351Reviewed-by:Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Kanghua Yu <kanghua.yu@intel.com> Cr-Commit-Position: refs/heads/master@{#53171}
-
Sathya Gunasekaran authored
Splitting out hash table into a separate file in b934607d caused a performance regression. This inlines GetHash and GetSimpleHash to fix the regression. Bug: chromium:840694, v8:6443 Change-Id: I0466fa017a179ef2375cec4ddec8f04dfba75921 Reviewed-on: https://chromium-review.googlesource.com/1058446 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#53170}
-
- 14 May, 2018 19 commits
-
-
Sathya Gunasekaran authored
Bug: v8:7732 Change-Id: Id7f28e6975a4180573da3981e3e6de312e39f785 Reviewed-on: https://chromium-review.googlesource.com/1049485Reviewed-by:
-
Vasili Skurydzin authored
Change-Id: I05bd981c8050a6f59446be660d449320979ceaea Reviewed-on: https://chromium-review.googlesource.com/1053957Reviewed-by:
-
Junliang Yan authored
Port 5dfe23a4 Original Commit Message: When encountering a LoadStackPointer input to a comparison, generate a register LocationOperand that points to the stack pointer. This can avoid unnecessary spilling of the stack pointer. R=georgia.kouveli@arm.com, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: Ie3fecf70f78c234fefad86fec74820a61f3d227b Reviewed-on: https://chromium-review.googlesource.com/1057965Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#53167}
-
Sathya Gunasekaran authored
Bug: v8:6443, v8:7569 Change-Id: I61677e75f23c604ba7ad0ea110aa57578dcadb89 Reviewed-on: https://chromium-review.googlesource.com/1047957 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Vasili Skurydzin authored
Implement atomic compare exchange and atomic bin OPs for PPC and s390 Change-Id: I8f89a0ebb912082c4c1e6b9a3daf64f28c114010 Reviewed-on: https://chromium-review.googlesource.com/1013861Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#53165}
-
Maya Lekova authored
Bug: chromium:842101 R=neis@chromium.org Change-Id: I4a142b28682ba73cbf3398e74c15614fa491ad40 Reviewed-on: https://chromium-review.googlesource.com/1057627 Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#53164}
-
Michael Starzinger authored
This makes the fact that {WasmSharedModuleData} is shared across instances explicit by hanging this {shared} reference off the module object instead of the instance-specific {WasmCompiledModule} object. R=titzer@chromium.org Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I99bf3d855d6283bdc48373f0f8e2df1990905d3f Reviewed-on: https://chromium-review.googlesource.com/1051909 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: -
Georg Neis authored
Bug: chromium:831822 Change-Id: I4d6fba6dd37a1a3f1d9b3ebcf2a88e2753d8dcf1 Reviewed-on: https://chromium-review.googlesource.com/1057269 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
-
Georgia Kouveli authored
When encountering a LoadStackPointer input to a comparison, generate a register LocationOperand that points to the stack pointer. This can avoid unnecessary spilling of the stack pointer. Change-Id: Ifd1a5aaf22c9c594e653cf4689ba46587811c4d0 Reviewed-on: https://chromium-review.googlesource.com/1055568Reviewed-by:
-
Théotime Grohens authored
Change-Id: I971fe8a5aaadd6360f589451433848ed67e49813 Reviewed-on: https://chromium-review.googlesource.com/1054232Reviewed-by:
-
Simon Zünd authored
This CL disables a DCHECK in RemoveArrayHoles that was triggered for JSArrays that have read-only elements in the prototype chain. The DCHECK is not removed because it will be re-enabled later when the copying from the prototype chain (during sorting) will be done for JSArrays as well. R=cbruni@chromium.org Bug: chromium:840855 Change-Id: Ia278bd2f060df094f477b4efbc3f5bdafd7ea7a8 Reviewed-on: https://chromium-review.googlesource.com/1057588Reviewed-by:
-
Clemens Hammacher authored
Liftoff currently does not support all asm.js code, and tier-up does not work with lazy compilation. Hence, disable Liftoff for asm.js in general. We will look at this later, when we have better tier-up. R=titzer@chromium.org Bug: v8:6600 Change-Id: I00d9e27d861067b22c0738ade7070538ee8c919c Reviewed-on: https://chromium-review.googlesource.com/1047245Reviewed-by:
-
Clemens Hammacher authored
Instead of unconditionally copying the script name into a heap-allocated char vector, use existing storage if possible. Also, try to avoid materializing the script name for computing its length. R=titzer@chromium.org Change-Id: If0e8ac95ecbbb4e7463d9e4a4cdb5579270bcdaf Reviewed-on: https://chromium-review.googlesource.com/1051230Reviewed-by:
-
Clemens Hammacher authored
Minor performance optimization: A {WasmDecoder} instantiated with {validate == false} does not need to check {decoder->ok()}. R=titzer@chromium.org Change-Id: Ieac8b18432453e1cfe9ee66a15a5e2145570436e Reviewed-on: https://chromium-review.googlesource.com/1057567Reviewed-by: -
Michael Starzinger authored
Now that {WasmCode} objects are no longer specific to an instance, it is no longer needed to patch code when the last instance is finalized. The code specialization in {WasmCompiledModule::Reset} is no longer needed. R=clemensh@chromium.org Change-Id: I430e7f7258d309916de1188d47677c7feb8123b0 Reviewed-on: https://chromium-review.googlesource.com/1057488Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#53155}
-
Clemens Hammacher authored
A std::unique_ptr of array type uses the "delete[]" operator to delete the memory, hence we should use "new[]" to allocate it. I sometimes get this reported locally, even though I have "alloc_dealloc_mismatch=0" in ASAN_OPTIONS. So why not just fix it. R=marja@chromium.org Bug: v8:7754 Change-Id: I026287a0e0ee4b9560c4fc7333267e738392b13f Reviewed-on: https://chromium-review.googlesource.com/1057230Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#53154}
-
Pierre Langlois authored
The --trace-turbo flag would cause a crash when compiling a WASM_FUNCTION. It was caused by assuming the OptimizedCompilationInfo had a SharedFunctionInfo attached if the code isn't a stub and wasm functions are not considered as such. In order to test this, we've added a new flag to specify were to dump JSON files: --trace-turbo-path. This is used to make sure we do not leave lots of files behind in the top-level directory. It should be useful as standalone feature too. Change-Id: Ia9442638d28100bea45a8683fb233803cc5393f2 Reviewed-on: https://chromium-review.googlesource.com/1030555 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
jgruber authored
The flag hash is used by code caching to recognize incompatible V8 configurations. When the flag hash differs, the cache is thrown out. Code produced by embed/noembed builds is incompatible, and thus needs to change the flag hash as well. Bug: v8:6666, v8:7739 Change-Id: Icae8c6dc39b2eab491d28b2155f67103acf68181 Reviewed-on: https://chromium-review.googlesource.com/1057331Reviewed-by:
Mythri Alle <mythria@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#53152}
-
Marja Hölttä authored
This gets rid of the weakness hacks which were needed for remembering that maps as handlers are weak, and other handles are strong. BUG=v8:7308 Change-Id: I7fd3252ba67350803e2207dc12bbdf6abbae7e23 Reviewed-on: https://chromium-review.googlesource.com/1055449Reviewed-by:
-
