- 19 May, 2020 14 commits
-
-
Ulan Degenbaev authored
Allocation observers are not thread-safe, so the allocation steps should be invoked only on the main thread. Bug: v8:10536 Change-Id: I90e809fa230d18cce135f4bea67b62ef616ca593 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207189Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#67891}
-
Santiago Aboy Solanes authored
Bug: v8:9708, v8:10506, v8:6949 Change-Id: I701ad51273e14db8a5185ff130e8d8593dce1ba4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202911Reviewed-by:
Mythri Alle <mythria@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#67890}
-
Dominik Inführ authored
Locking the space mutex isn't required in PagedSpace::Expand. Bug: v8:10315 Change-Id: I6fac74e3c4fc6f4f2228af37729839b6ff23bc64 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207183 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#67889}
-
Jakob Gruber authored
Call_WithFeedback CallWithArrayLike_WithFeedback CallWithSpread_WithFeedback ConstructWithArrayLike_WithFeedback ConstructWithSpread_WithFeedback These are used in generic lowering if --turbo-nci is passed. Bug: v8:8888 Change-Id: I78b56a1f358fa7c213e375eeb2feaa65432adfdb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2199352Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#67888}
-
Santiago Aboy Solanes authored
Return type still needs TNodification. It can be Object or Float64T. Bug: v8:10506, v8:6949 Change-Id: I71e7ae28f3039b2e1c5c2a5c2e383c335cdec38a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204281Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#67887}
-
Santiago Aboy Solanes authored
Used to be named FastFixedArrayForEachBody. Rename to remove the 'fixed' part since it can also be a PropertyArray (i.e not a FixedArray). Rename BuildFastFixedArrayForEach to also remove the 'fixed'. Bug: v8:10506, v8:6949 Change-Id: I840edf802d334b9ca930f3022553c476e2dca34a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202910Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Cr-Commit-Position: refs/heads/master@{#67886}
-
Clemens Backes authored
This reverts commit 3cc981cb. Reason for revert: TSan failures: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN/31572 Original change's description: > [wasm][debug] Fix tier down during streaming compilation > > If the debugger is enabled while streaming compilation is happening, we > won't correctly tier down to Liftoff. This is because during streaming > compilation, we always compile for no debugging. Fixing that is a bit > tricky, since when the debugger is enabled, functions can either already > have finished compiling, or they are currently being compiled, or their > wire bytes are not received yet. > Instead of handling this correctly while streaming compilation is > running, we just recompile the whole module with Liftoff after streaming > compilation finished. > > For testing this, we use the existing tests for async compilation, and > enable --wasm-test-streaming, which compiles via the streaming decoder > even in the async compilation case. > > R=thibaudm@chromium.org > > Bug: v8:10531 > Change-Id: I0177248a9ad2e90f83faee965d6746de05423f1f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207133 > Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67882} TBR=clemensb@chromium.org,thibaudm@chromium.org Change-Id: I26e750c6c6d0783b5e4a0f19a5462a5fbe99a742 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:10531 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207186Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#67885}
-
Marja Hölttä authored
In this case, we'll already have values in "errors" in PerformPromiseAny step 8.d. Bug: v8:9808 Change-Id: I5bb0cba41887f4bbdab3bb15e8f52dd94acec9c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204277 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#67884}
-
Richard Stotz authored
We implement the conversions via C functions (external references) because 64-bit conversions are difficult to implement on ia32 and would not be significantly faster. Bug: v8:10520 Change-Id: I3573d30bf6b3d558f708c7e0273f027c30a1a771 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202988 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#67883}
-
Clemens Backes authored
If the debugger is enabled while streaming compilation is happening, we won't correctly tier down to Liftoff. This is because during streaming compilation, we always compile for no debugging. Fixing that is a bit tricky, since when the debugger is enabled, functions can either already have finished compiling, or they are currently being compiled, or their wire bytes are not received yet. Instead of handling this correctly while streaming compilation is running, we just recompile the whole module with Liftoff after streaming compilation finished. For testing this, we use the existing tests for async compilation, and enable --wasm-test-streaming, which compiles via the streaming decoder even in the async compilation case. R=thibaudm@chromium.org Bug: v8:10531 Change-Id: I0177248a9ad2e90f83faee965d6746de05423f1f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207133Reviewed-by:
Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#67882}
-
Shu-yu Guo authored
I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/raep1X9R_SE/m/V8ofHrBdAgAJ Bug: v8:9801 Change-Id: I55e71b37f23ec91a01771f5584d11bc4e5939da4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207920 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Auto-Submit: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#67881}
-
Jakob Gruber authored
So far this is mainly a readability improvement to specify expectations on the packed argument. In the future we should also check signedness during bytecode generation. Drive-by: Update DCHECK to allow signed args to CHECK_CURRENT_POSITION. Bug: chromium:1083450 Change-Id: I9376ec691b51eb251c972309ad65dd6c04eec3ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207137 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#67880}
-
Jakob Gruber authored
Verify that `current` always points inside, or just past the end of the subject string. Bug: chromium:1083450 Change-Id: I27ba49cbfd0aa93cd2e305efafc23b155c98a49b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207136Reviewed-by:
-
Ng Zhi An authored
The lowering for anytrue was assuming that the input nodes are all integers. The regression test added in https://crrev.com/c/2194471 calls anytrue with float operands, this was causing the lowering to generate cmpl instructions with a float register and an immediate, which is wrong. The fix is to use GetReplacementsWithType on the input nodes, but only if the input were floats, since we use Word32Equal. Drive-by clean up of comments in the aforementioned regression test. Bug: v8:10535 Change-Id: I4de89516c178e9003a4c745808d831be87918381 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2203400 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#67878}
-
- 18 May, 2020 26 commits
-
-
Ng Zhi An authored
Bug: v8:9886 Change-Id: I22af3c19ef6371d31f0f95c58730ceb3e7effafa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207653Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#67877}
-
Hannes Payer authored
Change-Id: I70328a944b78591d106d752197b096cb86c32573 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2206735 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
Ng Zhi An authored
The codegen uses a bunch of vpmax to try and keep set bits around. The datatype for vpmax does not need to change for each instruction, since vpmax U32 will persist set bits just as well. This simplifies the instruction sequences for S1x8 and S1x16 anytrue. I added a test to check a special case when a f64x2 contains -0.0 (top bit set). A previous attempt to optimize codegen used floating point compare, which does not distinguish between 0.0 and -0.0. So -0.0 will compare equals to 0.0, and incorrect return 0 for anytrue. Change-Id: I66013796af08a666009e6b2d774ea7ee7bdfe1ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2203113 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
Milad Farazmand authored
Port 99e4ef48 Original Commit Message: Only for arm and arm64 now. The ia32 and x64 ones are more complicated and will be included in subsequent changes. R=zhin@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I3bcdae0d47d2e024cfb6e80ba460306ec5e2d434 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2205884Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#67874}
-
Ng Zhi An authored
This is a reland of edf90ee8 The fix here is to call GetUnusedRegister with {}, in liftoff-assembler-ia32.h emit_i8x16_shri_u. Original change's description: > [wasm-simd][liftoff][ia32][x64] Implement i8x16 shr > > The code sequence is the same as TurboFan, only wrapped in a template to > share the implementation. > > Bug: v8:9909 > Change-Id: I9c1b37bbfafe91d1bd8edd7f9dafd86ff1c07623 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202723 > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Reviewed-by: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67842} Bug: v8:9909 Change-Id: Id56a612cd6580c68a5129e71d7a0e7b29d64b368 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204080Reviewed-by:
-
Ng Zhi An authored
Making them private was a way to hide the constructor, we can explicitly delete them, which give a better compilation error message as well. Also see: https://stackoverflow.com/q/55205874 Bug: v8:10488 Change-Id: I8a116637608fcc6a93d6fc4f5ee014d2db863669 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204156Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#67872}
-
Manos Koukoutos authored
- Add a default, move, and copy constructor for SsaEnv and use them when possible. - Bring the Split method signature in line with Steal and Unimplemented. Changes: Change-Id: I626142fbd1c1ed15c1852b9bfc8b39a0e936b839 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204278 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
-
Dan Elphick authored
Moves several functions missed in https://chromium-review.googlesource.com/c/v8/v8/+/2203206. Bug: v8:10473, v8:10506 Change-Id: I882410cefe496054b71db24a65133224dc52f23c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207144 Commit-Queue: Dan Elphick <delphick@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Maya Lekova authored
Bug: v8:9994 Change-Id: I662182a252c2aab053f6c821bf281f613316700a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207143 Commit-Queue: Maya Lekova <mslekova@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
-
Richard Stotz authored
Bug: v8:10520 Change-Id: If24a2d74b6e1837b4c29383e4c537e872404e0a4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2201764 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
-
Maya Lekova authored
Enhance gcmole --verbose printing with the GC suspect. Bug: v8:9986 Change-Id: Ia1454d4edec334eabb31a764583e4ee559f0fe07 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207174Reviewed-by:
-
Richard Stotz authored
Bug: v8:10520 Change-Id: Iad8d35e58b766a9e4d3013f90fd4d7fb68708fa7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2201577 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
-
Clemens Backes authored
Asynchronicity can be tricky, in particular if the debugger is enabled while wasm compilation is happening. We seem to have open issues in streaming compilation there. As a first step, which CL adds more tests for async compilation (non-streaming). R=thibaudm@chromium.org Bug: v8:10531 Change-Id: Idf16790a91aad437ceb981485512a2f52b791bac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2206736Reviewed-by:
-
Jakob Gruber authored
This is a reland of 69f42d40 Original change's description: > [nci] Add Construct_WithFeedback builtin > > This builtin essentially acts like InterpreterAssembler::Construct. It > collects full feedback, then tail-calls either the array constructor > or the construct builtin. > > For now, it is only used in generic lowering, if the --turbo-nci flag > is passed. One of the next steps will be to measure performance impact > of feedback collection. If minimal, we may want to enable it > unconditionally in generic lowering. > > Bug: v8:8888 > Change-Id: I8a460a2b5954c26fa72658045a8423c5eee6b611 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2198775 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Auto-Submit: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67850} Tbr: neis@chromium.org Bug: v8:8888 Change-Id: Ib1a81da998c848d63c0119b3a4e90fc917b15e94 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2206738 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#67864}
-
Richard Stotz authored
Bug: v8:10520 Change-Id: Id06c35f8004519cd778af12ad67aaee2d506609a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2207135 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
-
Omer Katz authored
Bug: chromium:1056170 Change-Id: I8f1fbf1f9995fbd3f89564542209b828bf7118ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2190428Reviewed-by:
Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#67862}
-
Santiago Aboy Solanes authored
There are some 'mode' still pending removal. Bug: v8:9708, v8:10506, v8:6949 Change-Id: Ie1dc0397241bf046ac9737666e700b98018b2ff5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202906 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
Jakob Gruber authored
This reverts commit 69f42d40. Reason for revert: The last PS introduced a bug https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20-%20fyi/15897. Original change's description: > [nci] Add Construct_WithFeedback builtin > > This builtin essentially acts like InterpreterAssembler::Construct. It > collects full feedback, then tail-calls either the array constructor > or the construct builtin. > > For now, it is only used in generic lowering, if the --turbo-nci flag > is passed. One of the next steps will be to measure performance impact > of feedback collection. If minimal, we may want to enable it > unconditionally in generic lowering. > > Bug: v8:8888 > Change-Id: I8a460a2b5954c26fa72658045a8423c5eee6b611 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2198775 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Auto-Submit: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#67850} TBR=neis@chromium.org,jgruber@chromium.org,tebbi@chromium.org Change-Id: I3af168373978d773385b9eda9bc1e243e3cbea09 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8888 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2206737Reviewed-by:
-
Jakob Gruber authored
... and other unused methods. Bug: v8:9708 Change-Id: Ie3658878024fcddcd5503c6462e5ad873eba19b0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2206733 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Auto-Submit: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#67859}
-
Richard Stotz authored
Bug: v8:10520 Change-Id: I0b4867d9b705058536b0f4640a9a87059db3aca7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2201576 Commit-Queue: Richard Stotz <rstz@chromium.org> Reviewed-by:
-
Dan Elphick authored
Splits out MemoryAllocator and CodeRangeAddressHint into memory-allocator.h Bug: v8:10473, v8:10506 Change-Id: I0855f23dd0374ddd68493ee05af7a3a00c84660d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2203206 Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#67857}
-
Thibaud Michaud authored
R=ahaas@chromium.org Bug: v8:10408 Change-Id: I1ca62c1cdf3025dcd0df7cdbe6735cc3491c48e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2201578 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
-
Clemens Backes authored
We constantly fight against scrambled output with --print-wasm-code and other flags. Passing --single-threaded only partially mitigates this, because there could still be multiple isolates (e.g. Workers), and we sometimes failed to really execute in a single thread if that flag was set. Hence this CL solves the problem in a more fundamental way: Whenever a {StdoutStream} is constructed, it implicitly takes a global recursive mutex. The recursive mutex is needed because we still have some printing methods that don't take a stream as parameter, and instead create their own instance of {StdoutStream}, which should not crash of course. The overhead of taking a mutex should be acceptable, since output to stdout mostly happens if special tracing flags have been passed, and is slow anyway. This CL ensures that the {StdoutStream} is used at least for --print-code, --print-wasm-code, and --trace-turbo-graph. More flags can later be ported on demand. The {JSHeapBroker} class was modified to not contain a {StdoutStream}, but instead create one on demand. R=mlippautz@chromium.org, tebbi@chromium.org CC=ahaas@chromium.org Bug: v8:10506 Change-Id: Ib9cf8d76aa79553b4215bb7775e6d47a8179aafa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2201767Reviewed-by:Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#67855}
-
Jakob Kummerow authored
When the intention is to handle every case, *and* when we can be reasonably sure that no invalid enum values will occur (e.g. from reading untrusted data), then we shouldn't have a "default:" case in a switch statement so that the compiler will warn us when a case is missing. Bug: v8:10506 Change-Id: Iefdebd54802611e7ec3479afa3c4e6506f97a095 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204284 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Ulan Degenbaev authored
This moves page post-processinng into NotifyOldGenerationExpansion and introduces a new CanExpandOldGenerationBackground. Bug: v8:10536 Change-Id: I54761226487434955f8a0dadf7c4dbb31c7955e7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2204283Reviewed-by:
-
Santiago Aboy Solanes authored
Bug: v8:10506 Change-Id: I171a587176f4a1a3c98d407e8b6a3b63bbf1ad6a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2202993 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
-
