- 05 Feb, 2021 10 commits
-
-
Clemens Backes authored
Avoid duplicating the list of parameter registers to push in the WasmCompileLazy builtin by reusing the existing arrays from wasm-linkage.h. Also verify the computed results against different constants. R=zhin@chromium.org Bug: v8:11377 Change-Id: I727d4dcd1f1a0d3ae0e1a6ec03f0fb40c08564ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668767 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Zhi An Ng <zhin@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#72547}
-
Junliang Yan authored
Change-Id: I372d3ef6806b001e45b5522e5a91f20393bf75bc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2676627Reviewed-by:
Milad Fa <mfarazma@redhat.com> Commit-Queue: Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#72546}
-
Benedikt Meurer authored
In JSStackFrame::GetMethodName() we try to infer a useful method name to show for the closure to which the stack frame belongs. This is done by first considering the functions name, and checking if the receiver has a property with that name and if that property's value is the closure. In case the function doesn't have a name or the property's value is not the closure itself, we fall back to a reverse lookup of the closure within the object (and its prototypes). This CL speeds up this logic by attacking two problems: 1. The reverse lookup was performed by first using the KeyAccumulator to extract the names of all enumerable properties, and afterwards using the LookupIterator on each name, and testing the resulting property value against the closure. This is fairly slow and creates a lot of temporary objects and handles. We now look into the descriptor arrays or dictionary backing stores of the objects directly instead, which is easily 2-10x faster. 2. For the common case of `o.foo = function() { ... }` the parser already places an "inferred name" of `o.foo` onto the SharedFunctionInfo, which we can use as a hint to infer the name of the function instead of immediately falling back to the expensive reverse lookup. This repairs the regression reported in http://crbug.com/1069425 and recovers most of the slowdown reported in http://crbug.com/1077657 (there's still some overhead left from the async stack trace tracking). Fixed: chromium:1069425 Bug: chromium:1077657 Change-Id: I88d23ccad123906df70c5217e815493106e03ccf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2676635 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:Yang Guo <yangguo@chromium.org> Reviewed-by:
Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#72545}
-
Almothana Athamneh authored
Bug: v8:11385 Change-Id: Idbfafa2db7dd5a091796e7982c4181486dcc60fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2675928Reviewed-by:
Liviu Rau <liviurau@chromium.org> Commit-Queue: Almothana Athamneh <almuthanna@chromium.org> Cr-Commit-Position: refs/heads/master@{#72544}
-
Georg Neis authored
Change-Id: I6df71e7bbbcd726816826693b43d4acf30af21d2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2667186Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#72543}
-
Georgia Kouveli authored
This requires a small fix in {Push,Pop}CalleeSavedRegisters, where the return address was signed/authenticated at the wrong point, which meant the stack pointer used as modifier was different from the one the StackFrameIterator expected. Bug: v8:10026 Change-Id: Idebd2ee8f07312b5e99dd2ea5181fc7a7e4a87bc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2667861 Commit-Queue: Georgia Kouveli <georgia.kouveli@arm.com> Reviewed-by:Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#72542}
-
Paolo Severini authored
This is a reland of 6ada6a90 - Fixed a GC issue https://bugs.chromium.org/p/v8/issues/detail?id=11335: GC expected all arguments on the stack from code with CodeKind::TURBOFAN to be tagged objects. This is not the case now with inlined Wasm calls, and this information can be passed in SafepointEntry for each call site. - Disabled JS-to-Wasm inlining for calls inside try/catch. For more details, see updated doc: https://docs.google.com/document/d/1mXxYnYN77tK-R1JOVo6tFG3jNpMzfueQN1Zp5h3r9aM/edit# Bug: v8:11092 Original change's description: > Reland "Faster JS-to-Wasm calls" > > This is a reland of 860fcb1b > > - Disabled the tests for this feature in V8-lite mode (the original > change broke V8-lite tests). > - Also modified test console-profile-wasm.js that was brittle with this > change because it assumed that there was always a JS-to-Wasm wrapper > but this is not the case when the TurboFan compilation completes before > the Liftoff-compiled code starts to run. > > More changes in Patchset 8: > > - Moved inlining of the "JSToWasm Wrapper" away from simplified-lowering, > into a new phase, wasm-inlining that reuses the JSInliner reducer. > The doc > https://docs.google.com/document/d/1mXxYnYN77tK-R1JOVo6tFG3jNpMzfueQN1Zp5h3r9aM/edit# > describes the new logic. > > - Fixed a couple of small issues in wasm_compiler.cc to make sure that > the graph "JSToWasm Wrapper" subgraph has a valid Control chain; > this should solve the problem we had inlining the calls in functions > that can throw exception. Original change's description: > Faster JS-to-Wasm calls > > This replaces https://chromium-review.googlesource.com/c/v8/v8/+/2376165/. > > Currently JS-to-Wasm calls go through a wrapper/trampoline, built on > the basis of the signature of a Wasm function to call, and whose task > is to: > - set "thread_in_wasm_flag" to true > - convert the arguments from tagged types into Wasm native types > - calculate the address of the Wasm function to call and call it > - convert back the result from Wasm native types into tagged types > - reset "thread_in_wasm_flag" to false. > > This CL tries to improve the performance of JS-to-Wasm calls by > inlining the code of the JS-to-Wasm wrappers in the call site. > > It introduces a new IR operand, JSWasmCall, which replaces JSCall for > this kind of calls. A 'JSWasmCall' node is associated to > WasmCallParameters, which contain information about the signature of > the Wasm function to call. > > WasmWrapperGraphBuilder::BuildJSToWasmWrapper is modified to avoid > generating code to convert the types for the arguments > of the Wasm function, when the conversion is not necessary. > The actual inlining of the graph generated for this wrapper happens in > the simplified-lowering phase. > > A new builtin, JSToWasmLazyDeoptContinuation, is introduced to manage > lazy deoptimizations that can happen if the Wasm function callee calls > back some JS code that invalidates the compiled JS caller function. > Bug: v8:11092 Cq-Include-Trybots: luci.v8.try:v8_linux_arm_lite_rel_ng Change-Id: Ie052634598754feab4ff36d10fd04e008b5227a5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2649777 Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#72541}
-
Manos Koukoutos authored
The constructor_or_backpointer accessor of Map was not consistent with the torque-defined field constructor_or_back_pointer_or_native_context, leading to confusion. This CL brings them in sync, choosing the latter spelling. Change-Id: I3375c5f060bfd5e1e7cab195e3cca3d508c88154 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674011 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#72540}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/10e5511..ee7e404 Rolling v8/third_party/aemu-linux-x64: daCtImfwROvNf-7jcpyqZ6KMCGlIQv9BROkyXnulGioC..rNvRFA3R0THFzCnDKyJfVyqZysmcZ_To-ZfvXMhYKw8C Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/5c5a297..c8f9f36 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/6dc9cc3..e342fb1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/4ee065a..f18ba70 TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8195fa46a4f6f0acd52e3fa4d60cf084c6c82d07 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2677053Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#72539}
-
Junliang Yan authored
Change-Id: I8d331992330eeabc9aae564e4467c95764d605f0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2676623Reviewed-by:
-
- 04 Feb, 2021 19 commits
-
-
Ng Zhi An authored
This prototypes i32x4.widen_i8x16_s and i32x4.widen_i8x16_u for arm64. Bug: v8:11297 Change-Id: Ib9be5086c8ea98340c9bb1980c319626d7072c1e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2664994Reviewed-by:
-
Ng Zhi An authored
The previous instruction selection was too loose, it only required registers for the inputs. The codegen also used Unpcklps(dst, mask), and failed to use src at all. The test case was accidentally passing because dst == src (xmm0) by chance. We fix this bug requiring that for AVX, any register is fine, but for SSE, require dst == src. Also redefine Unpcklps to check dst == src in the no AVX case. Bug: v8:11265 Change-Id: I1988b2d2da8263512bf6e675e6297c50f55663f7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668918Reviewed-by:
-
Ng Zhi An authored
Implement these 6 instructions: - f64x2.convert_low_i32x4_s - f64x2.convert_low_i32x4_u - i32x4.trunc_sat_f64x2_s_zero - i32x4.trunc_sat_f64x2_u_zero - f32x4.demote_f64x2_zero - f64x2.promote_low_f32x4 The code sequences are exactly the same as on x64. Needed to add some more instructions, and we don't have macro lists for these instructions yet, so individually define them for now. We can factor them into lists in a future change. Bug: v8:11265 Change-Id: I606e1226201e3c5ecdc7e3f611315437e917d77c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668913Reviewed-by:
-
Toon Verwaest authored
Change-Id: I783c41ca4192d686454728b7c8356935bc67cc98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2675922 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Auto-Submit: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#72534}
-
Jakob Gruber authored
TranslationArrays (TA) are large and rarely used, thus could benefit from compression. This CL adds a --turbo-compress-translation-arrays flag (off by default) to experiment with that. Each optimized Code object has an associated translation array (Code->DeoptimizationData->TranslationArray). These translation arrays have roughly the same size as the Code object itself. They are used only rarely: when deoptimizing, and when traversing the stack and looking into optimized frames. Neither of these code paths are especially performance critical. TA's contain only immutable, untagged data. They are thus good candidates for compression. The trade-off is between TA memory consumption and time spent in decompression/compression. This CL keeps everything on the main thread, but it would also be possible to move compression (the more expensive operation by a factor of 5 to 10) to a worker thread. Numbers from a local Octane2 run: Sum of Code instructions sizes: 4.6MB Sum of uncompressed TA sizes: 4.1MB Sum of compressed TA sizes: 0.6MB Compression times depend on the selected compression quality, but roughly: Compression: 50ms (40us avg per compilation) Decompression: 7us avg per compilation Drive-by: Translation arrays currently use run-length encoding; I disabled this for when --turbo-compress-translation-arrays is enabled (no need to compress twice). Bug: v8:11354 Change-Id: I7828d7d91eb074816b383b02f883c5d7b7e318b7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2652497 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Michael Achenbach authored
We want to remove the gpu:none default as we want to switch to Mac Minis in the Mac pool that have gpus. This starts a 3-way change: 1. This CL: Add the gpu dimension for Mac source side. 2. Remove setting it as default for Mac in infra. 3. Flip the value for gpu source side. This requires merging to beta/stable. No-Try: true Bug: chromium:1174040 Change-Id: I81f2f5863593aa93fa668b4534d1116a11768f31 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673402 Auto-Submit: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#72532}
-
Thibaud Michaud authored
In the latest spec, catch_all is encoded as 0x05. This is the same opcode as "else", but they do not conflict because "else" is not valid in the context of a try block. The 0x0a opcode now corresponds to the "unwind" instruction, which currently has the same semantics as "catch_all". R=clemensb@chromium.org Bug: v8:11392 Change-Id: Ie9cd06c9a2001a02d8bea5be7a3c016e3a58ee3d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674007 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by:
-
Nico Hartmann authored
Change Isolate::code_coverage_mode to an atomic such that access from the background thread is safe. Bug: v8:11378 Change-Id: I26d6915b1662ba022ea6a173a87d184d3ac7cd3b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2666691 Commit-Queue: Nico Hartmann <nicohartmann@chromium.org> Reviewed-by:
-
Dominik Inführ authored
Sweeping was already restarted, ignore chunks that might be swept concurrently. Bug: chromium:1174007 Change-Id: I954bf4b25ddb27a612b9fd33bad1f1ba34358719 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674005Reviewed-by:
-
Frank Emrich authored
This CL adds PropertyDetails::ToByte and ::FromByte. These are not applicable to all PropertDetails, but only those for dictionary-backed properties with an (unused) enumeration index with value 0. The motivation for this is that those dictionare backing stores that don't store the enumeration order in the PropertyDetails but store it in the table itself (like OrderedNameDictionary and the upcoming SwissNameDictionary), can store PropertyDetails in an array of bytes. Bug: v8:11388 Change-Id: Id346b924cd7c67b2f33cbc7a7807eec31cefbeec Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2672029 Commit-Queue: Frank Emrich <emrich@google.com> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#72528}
-
Michael Lippautz authored
Platform::GetForegroundTaskRunner() can only be used after attaching an Isolate in V8. Work around that problem by getting the runner only when needed. Bug: chromium:1056170 Change-Id: If15ec691e7f5cf11be8b7a3bc18827246ac083d6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674009 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Omer Katz <omerkatz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Cr-Commit-Position: refs/heads/master@{#72527}
-
Clemens Backes authored
Instead of passing a bunch of objects and pointers to {GenerateLiftoffDebugSideTable}, just pass the WasmCode pointer for which the debug sidetable should be created. This requires changing the corresponding cctests to actually compile code, such that we can get a WasmCode pointer. R=thibaudm@chromium.org Bug: chromium:1172299 Change-Id: If42f06a545feb590f9c2377ce95e6214bbc6f566 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674006Reviewed-by:Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#72526}
-
Sathya Gunasekaran authored
ZoneChunkList has more overhead than a simple ZoneVector for storing uint8_t bytes. Bug: v8:9684 Change-Id: I5e22286f2628ae2010086e9d82cadbebb176dbee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2661459Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Frank Emrich authored
For dictionary mode objects, whether or not a property is constant was not tracked before. This CL makes the required non-Turbofan changes, guarded behind the new flag V8_DICT_PROPERTY_CONST_TRACKING. In addition, prototypes are not converted to fast mode objects if this flags is enabled. Bug: v8:11247 Change-Id: Ia5942733239a97560b6efc015f0e25a35fea3d7a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2566757 Commit-Queue: Frank Emrich <emrich@google.com> Reviewed-by:
-
Clemens Backes authored
Creating a PatchingAssembler has significant overhead, including a dynamic allocation for the assembler buffer implementation. In the case of {Assembler::bind} we just need it to overwrite a machine word. Hence avoid creating the PatchingAssembler for this trivial work and just use Memcpy directly. R=jkummerow@chromium.org Change-Id: I83510cfd7ebdb0d0c378df548b442eabf3727aeb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668827Reviewed-by: -
Jakob Gruber authored
... and mark it as never-serialized wrt turbofan serialization. Until this CL, the JSRegExp type was used as both for plain user-visible regexp objects, and for internal regexp boilerplate descriptions. Boilerplates are special: they are never exposed to the user, they are only referenced from the feedback vector, they are immutable. To clarify this distinction, this CL introduces a dedicated struct type RegExpBoilerplateDescription to hold the regexp boilerplate description. This makes Turbofan serialization simpler: boilerplates can be accessed through direct reads since they are immutable. TF has no special requirements on JSRegExp objects (it never reads into these objects) and thus serializing only the references as a JSObjectRef is fine. Bug: v8:7790 Change-Id: I33b337fcfcf861a02bc6be6d0c6311d07cf05718 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2656257Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Liu Yu authored
Port: 07b03b83 Bug: v8:10026 Change-Id: Ia9e5f420253a4fb3726a4064ed2471684af610e3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2670168 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Commit-Queue: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Cr-Commit-Position: refs/heads/master@{#72521}
-
Liu Yu authored
Port: e2aa734a Bug: v8:11002 Change-Id: I8564a810938a07031afab20bd5448f048d4bb5de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674182 Auto-Submit: Liu yu <liuyu@loongson.cn> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/base/trace_event/common: https://chromium.googlesource.com/chromium/src/base/trace_event/common/+log/9b27757..71cb2ac Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/dc9dc45..10e5511 Rolling v8/third_party/aemu-linux-x64: _nJMIPzu-ykpL-XPjf14IZ3CAFT3iQRtsbzyiSm9u7QC..daCtImfwROvNf-7jcpyqZ6KMCGlIQv9BROkyXnulGioC Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/4920147..5c5a297 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/8c95595..6dc9cc3 Rolling v8/third_party/icu: https://chromium.googlesource.com/chromium/deps/icu/+log/f4147b2..70dd9a6 Rolling v8/third_party/instrumented_libraries: https://chromium.googlesource.com/chromium/src/third_party/instrumented_libraries/+log/4d38670..0964a78 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/ec98581..4ee065a TBR=machenbach@chromium.org,tmrts@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I0ae82b75d2cf91fbbde2cb242fd49fa3493bbede Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674325Reviewed-by:
-
- 03 Feb, 2021 11 commits
-
-
Ng Zhi An authored
Bug: v8:11347,v8:11348 Change-Id: I47ba950b80197d1d769d93aa68266131be9bf31d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2666146Reviewed-by:
-
Ng Zhi An authored
Load lane instructions also need a v128 input. Bug: chromium:1173488 Change-Id: I45e4c4f8fc93a5b3246ac4d1b07925b41cbe3e89 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673275Reviewed-by:
-
Milad Fa authored
Port 8798b3ef Port 1d3c80d3 Original Commit Message: - Fixes some incorrect assumptions about padding in the code generation. Slots may have apparent extra padding when allocation fragments go unused. - Reworks 32 bit push code to simplify skipping slot gaps when 'push' instructions are used. - Adds a ElementSizeInPointers function on machine representations. R=bbudge@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I076ae8396434610c52fed040ace5e0f49ea3ef88 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673142 Commit-Queue: Milad Fa <mfarazma@redhat.com> Reviewed-by:
Junliang Yan <junyan@redhat.com> Cr-Commit-Position: refs/heads/master@{#72516}
-
Bill Budge authored
- Stack adjustment was in slots, when it should be in bytes. Bug: v8:11391 Change-Id: Ia791f2b637337279be62d66377f9b5be35f31839 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2674062Reviewed-by:
-
Ng Zhi An authored
These didn't have the right suffix (i32 instead of i32x4). Also, names are longer now, so when tracing them, give the names column more space. Bug: v8:11384 Change-Id: Id11e0d23b344310121ae4e2e5910528cab2d6f73 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673264Reviewed-by:
-
Ng Zhi An authored
Bug: v8:11391 Change-Id: Icb4b6b04cc0591f9b27256f7b58daed6c4fdffa2 No-Try: true No-Tree-Checks: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673276 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#72513}
-
Zhi An Ng authored
This reverts commit 64471ba9. Reason for revert: Fails on nosse3/nosse4 https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux/40643/overview Original change's description: > [wasm-simd] Update spec tests > > We can also unmark some SIMD tests as failed since we are now inline > with spec. > > Bug: v8:11331 > Change-Id: I4b98ae068008c55535dbbbf0312a55aa03e7e83d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668060 > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72507} TBR=ahaas@chromium.org,zhin@chromium.org Change-Id: I11a6670e42956bdcc66c371d2d852623030948b4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:11331 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673265Reviewed-by:
-
Junliang Yan authored
Change-Id: Ifa2b160e42bad2b3ae93a3c310d5fa158ffbd286 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2672705Reviewed-by:
-
Milad Fa authored
Implementation for PPC will be added in a later CL. Port dd90d107 Original Commit Message: Code sequence from https://github.com/WebAssembly/simd/pull/379, and exactly the same as x64, with minor tweaks for ExternalReferenceAsOperand. R=zhin@chromium.org, joransiu@ca.ibm.com, junyan@redhat.com, midawson@redhat.com BUG= LOG=N Change-Id: I2be8a9cf04d0b327c15f47c2575877925238353c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2672706Reviewed-by:
-
Ng Zhi An authored
roundpd requires SSE4.1. Bug: v8:11265 Change-Id: I1b5d322946de44f57026b09ec406d32128e5b3bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2668916Reviewed-by:
-
Shu-yu Guo authored
There is a bug in the top-level await spec draft such that async strongly connected components are not always evaluated before their depending modules. See https://github.com/tc39/proposal-top-level-await/pull/161 for full discussion and spec fix. Bug: v8:11376 Change-Id: I88bf06afb2e9a5d8d0b757de8276f1d1242a875e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2667772Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#72508}
-
