- 09 Aug, 2018 10 commits
-
-
Clemens Hammacher authored
R=titzer@chromium.org Bug: v8:6600 Change-Id: I2adb5a74cfdc6ec7e229f1ca1bd31d8209156617 Reviewed-on: https://chromium-review.googlesource.com/1167519Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#55002}
-
Simon Zünd authored
This CL fixes the copy-within JSTest benchmark so it works on Android. R=machenbach@chromium.org Change-Id: I63662f9ab00d0199614681a53118bc4079e697ff Reviewed-on: https://chromium-review.googlesource.com/1168488Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Simon Zünd <szuend@google.com> Cr-Commit-Position: refs/heads/master@{#55001}
-
Simon Zünd authored
This CL adds a baseline Torque implementation without fast-paths for Array.p.copyWithin. The JS version in array.js is removed. R=cbruni@chromium.org, jgruber@chromium.org Bug: v8:7624 Change-Id: Ie53047883a65dd9310ea8f8d0edb440f431044ea Reviewed-on: https://chromium-review.googlesource.com/1165223Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Simon Zünd <szuend@google.com> Cr-Commit-Position: refs/heads/master@{#55000}
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org No-Try: true Bug: chromium:775123 Change-Id: I8883be60cc4860fad572ba644bbc722972551eb3 Reviewed-on: https://chromium-review.googlesource.com/1168483Reviewed-by:
-
Michael Hablich authored
This reverts commit ff4fa92e. Reason for revert: blocks roll: https://chromium-review.googlesource.com/c/chromium/src/+/1167969 ... see https://chromium-swarm.appspot.com/task?id=3f344f7ada4e0110&refresh=10&show_raw=1 for stacktrace. Original change's description: > [builtins] Enable Torque Array.prototype.splice > > Before, splice was implemented with a C++ fast path and a > comprehensive JavaScript version. > > This impl. is entirely in Torque with a fastpath for SMI, > DOUBLE and OBJECT arrays, and a comprehensive slow path. > The same level of "sparse" array support as given by the > array.js implementation is included. > > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng > Change-Id: Ibfa3407ed75b9ad15ac54cce446b3952e38f90a9 > Reviewed-on: https://chromium-review.googlesource.com/1039190 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Commit-Queue: Michael Stanton <mvstanton@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54974} TBR=danno@chromium.org,yangguo@chromium.org,mvstanton@chromium.org,tebbi@chromium.org,szuend@google.com Change-Id: I900f667b30a0cf673ead9621618a9988cf85ffdf No-Presubmit: true No-Tree-Checks: true No-Try: true Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Reviewed-on: https://chromium-review.googlesource.com/1168902 Commit-Queue: Michael Hablich <hablich@chromium.org> Reviewed-by:
Michael Hablich <hablich@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#54998}
-
Michael Achenbach authored
NOTRY=true TBR=sergiyb@chromium.org Bug: chromium:866862 Change-Id: I52737a644c36f78b1803a443b89600bb7a114082 Reviewed-on: https://chromium-review.googlesource.com/1168485Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/8e67c4a..1f2ff68 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/ada05b3..8fa35d1 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/735f71d..dd5051f Rolling v8/third_party/fuchsia-sdk: https://chromium.googlesource.com/chromium/src/third_party/fuchsia-sdk/+log/c8d8248..1da4e38 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/ce468a1..d526632 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/42f0661..7302dfb TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Id550e6db520a917cf7eed91e5b65ba0cb39ea043 Reviewed-on: https://chromium-review.googlesource.com/1168653Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#54996}
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:838266 Change-Id: I7a8065038b4f62d10a1c0bc26df91566bdfec6bb Reviewed-on: https://chromium-review.googlesource.com/1154220 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#54995}
-
Frank Tang authored
Change-Id: I1fba76623d128748dfe001a2603ea5c8cebcc4eb Reviewed-on: https://chromium-review.googlesource.com/1161708Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#54994}
-
Sergiy Byelozyorov authored
TBR=machenbach@chromium.org No-Try: true Bug: chromium:838864 Change-Id: Id4881bd0cd01564cb969da7aad855a7ce6685bb8 Reviewed-on: https://chromium-review.googlesource.com/1168482 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
- 08 Aug, 2018 30 commits
-
-
Frank Tang authored
Bug: v8:7979 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: I367e7a7e93de267cf9b0718f193f5de3abfbf692 Reviewed-on: https://chromium-review.googlesource.com/1152556 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#54992}
-
Frank Tang authored
Spec: http://tc39.github.io/proposal-intl-list-format/ Design Doc: go/add-intl.listformat-to-v8 Test: intl/list-format/* R=gsathya@chromium.org, mvstanton@chromium.org Bug: v8:7871 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: I820c205ca842c228ffe37f7e1648667f30f80bd8 Reviewed-on: https://chromium-review.googlesource.com/1126683 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#54991}
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org Bug: chromium:863607 Change-Id: I999770d1dafbafe8bbe60b575a940f6feb90fae0 Reviewed-on: https://chromium-review.googlesource.com/1165551Reviewed-by:
-
Michael Achenbach authored
NOTRY=true Bug: chromium:872230 Change-Id: I15534f533e43cd4bdeedcdac204776178886c48d Reviewed-on: https://chromium-review.googlesource.com/1166916Reviewed-by:
-
Deepti Gandluri authored
Bug: v8:8005 Change-Id: I07774c23a332dac96e30d1bfe471db311de46496 Reviewed-on: https://chromium-review.googlesource.com/1166543Reviewed-by:
Bill Budge <bbudge@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#54988}
-
Sathya Gunasekaran authored
Also, fix one spec violation that checked for Name, but should just check for Strings. Bug: v8:8032, v8:7684 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Ib9ffa48b86b4da6e881eeec4eb24ec623345aae4 Reviewed-on: https://chromium-review.googlesource.com/1167042Reviewed-by:
-
Sigurd Schneider authored
This reverts commit f991465b. Reason for revert: test failure https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux64%20-%20internal%20snapshot/16696 Original change's description: > [wasm] Publish new code from the background threads. > > R=clemensh@chromium.org > BUG=v8:7921 > > Change-Id: Ib86cb5f742907b6e54365827facfc765867ca22e > Reviewed-on: https://chromium-review.googlesource.com/1156384 > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54985} TBR=mstarzinger@chromium.org,clemensh@chromium.org Change-Id: Id7b0f8ec208a0117f386e6e809ebe61125cf1119 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7921 Reviewed-on: https://chromium-review.googlesource.com/1167522Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#54986}
-
Michael Starzinger authored
R=clemensh@chromium.org BUG=v8:7921 Change-Id: Ib86cb5f742907b6e54365827facfc765867ca22e Reviewed-on: https://chromium-review.googlesource.com/1156384Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#54985}
-
Simon Zünd authored
This CL adds basic JS benchmarks for Array.p.copyWithin to get some feedback for the upcoming Torque implementation. R=jgruber@chromium.org Bug: v8:7624 Change-Id: Ic193a2b576d5fb7ac9f39db0379cece9144f979f Reviewed-on: https://chromium-review.googlesource.com/1167289Reviewed-by:
-
Predrag Rudic authored
Also, since trampoline code is position independent now, these builtins can be deleted from this list of Isolate dependent builtins. Bug: v8:7882 Change-Id: Ie65f739ebd3136993548e9737b22e7de0f09bf25 Reviewed-on: https://chromium-review.googlesource.com/1163513Reviewed-by:
Ivica Bogosavljevic <ibogosavljevic@wavecomp.com> Reviewed-by:
-
Jaroslav Sevcik authored
The idea is to compute the slack before compilation start. Then we check that the slack tracking decision is the same at the end of compilation. If it is, we just commit to that slack tracking (by calling function->CompleteInobjectSlackTrackingIfActive). If the slack tracking decision changed, we will retry the compilation. This has several pieces: - Expose computation of slack and instance size from the object model. - Add compilation dependency on the slack tracking result. - Change create lowering to use the dependency. - Fix array creation to use the slack tracking result's instance size. Bug: v8:7790 Change-Id: Id975300cfd6c1786733cd7cbf55cc507c05738b2 Reviewed-on: https://chromium-review.googlesource.com/1164957Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#54982}
-
Marja Hölttä authored
This also allows us to get rid of Context::self_weak_cell. BUG=v8:7308 Change-Id: I1b450385b674a4ad90c116648880fcbce6454c55 Reviewed-on: https://chromium-review.googlesource.com/1167186 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#54981}
-
Junliang Yan authored
Port d324382e and Port bd3f0a68 Original Commit Message: This is a reland of a462a785 Original change's description: > [turboassembler] Introduce hard-abort mode > > For checks and assertions (mostly for debug code, like stack alignment > or zero extension), we had two modes: Emit a call to the {Abort} > runtime function (the default), and emit a debug break (used for > testing, enabled via --trap-on-abort). > In wasm, where we cannot just call a runtime function because code must > be isolate independent, we always used the trap-on-abort behaviour. > This causes problems for our fuzzers, which do not catch SIGTRAP, and > hence do not detect debug code failures. > > This CL introduces a third mode ("hard abort"), which calls a C > function via {ExternalReference}. The C function still outputs the > abort reason, but does not print the stack trace. It then aborts via > "OS::Abort", just like the runtime function. > This will allow fuzzers to detect the crash and even find a nice error > message. > > Even though this looks like a lot of code churn, it is actually not. > Most added lines are new tests, and other changes are minimal. > > R=mstarzinger@chromium.org > > Bug: chromium:863799 > Change-Id: I77c58ff72db552d49014614436259ccfb49ba87b > Reviewed-on: https://chromium-review.googlesource.com/1142163 > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54592} R=clemensh@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I60023470fa07576fd313f628ade06e279d5f4927 Reviewed-on: https://chromium-review.googlesource.com/1165822 Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Reviewed-by:
-
Michael Lippautz authored
Implement independent write barrier for contents of objects. Change-Id: I739745f524245fa61b2b1cd01263cc8fe3a3d373 Reviewed-on: https://chromium-review.googlesource.com/1152909 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Camillo Bruni authored
Change-Id: I5effe97c53ccae3238a452fe2012926db45d2afe Reviewed-on: https://chromium-review.googlesource.com/1165222 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Michael Starzinger authored
R=sigurds@chromium.org Change-Id: I7df887f84024831b4c55b3468bd54429280dd14e Reviewed-on: https://chromium-review.googlesource.com/1167054Reviewed-by:
-
jgruber authored
This fills the padding between builtins in the embedded blob with a sequence of int3 instructions (ia32,x64). Drive-by: Unify code zapping. We can add better support for other architectures later. Bug: v8:6666 Change-Id: Ibcb120ec18a8062d7527e0c6fe5ca86869c0dad8 Reviewed-on: https://chromium-review.googlesource.com/1167050 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#54976}
-
Marja Hölttä authored
BUG=V8:7308 Change-Id: I4836aaca1474f08098120e6c17cc2b3bd65c70eb Reviewed-on: https://chromium-review.googlesource.com/1166914Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
-
Mike Stanton authored
Before, splice was implemented with a C++ fast path and a comprehensive JavaScript version. This impl. is entirely in Torque with a fastpath for SMI, DOUBLE and OBJECT arrays, and a comprehensive slow path. The same level of "sparse" array support as given by the array.js implementation is included. Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Ibfa3407ed75b9ad15ac54cce446b3952e38f90a9 Reviewed-on: https://chromium-review.googlesource.com/1039190Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Michael Starzinger authored
R=sigurds@chromium.org Change-Id: I1ca0e215da36400a8817bc8c8912ccfde8eca613 Reviewed-on: https://chromium-review.googlesource.com/1166911Reviewed-by:
-
Marja Hölttä authored
The parameter cannot be a WeakCell here anymore. BUG=v8:7308 Change-Id: Ie96312e0988e801d3bf52368d731e3b0cf9cc2dc Reviewed-on: https://chromium-review.googlesource.com/1167047Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#54972}
-
Michael Starzinger authored
This is the port of concurrent jump table patching support to ARM. It extends the corresponding stress test and changes the encoding of code targets in jump table slots to use constant pool entries. R=clemensh@chromium.org TEST=cctest/test-jump-table-assembler BUG=v8:8018 Change-Id: I4b709a7f14dace0f4eb9219f995d42ca607bb25f Reviewed-on: https://chromium-review.googlesource.com/1164952 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Predrag Rudic authored
In case of switching from non-optimized to optimized version of BranchLong macro, we forgot to take the instruction which is located in the branch delay slot of the unoptimized version and copy it to branch delay slot of the optimized version. This CL implements the missing functionality. Change-Id: I5e4adcccd0e85fd381a97eea8588e07bd8b045ef Reviewed-on: https://chromium-review.googlesource.com/1165082Reviewed-by:
-
Marja Hölttä authored
BUG=v8:7308 Change-Id: Icdbf7e786ce4ac19d73ab8e69bb57c0b19271b33 Reviewed-on: https://chromium-review.googlesource.com/1167043Reviewed-by:
-
Sergiy Byelozyorov authored
TBR=machenbach@google.om No-Try: true Bug: chromium:838864 Change-Id: Ic162e3fbd1c02b62cd8151bb5a598ca25db39d0b Reviewed-on: https://chromium-review.googlesource.com/1163721 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
DCHECKs (defined in src/logging.h) should not be used in third_party code. This CL removes the only such use. R=marja@chromium.org Bug: v8:7754, v8:7965 Change-Id: I44196bd2d85e459e27c6a897f039f741edf1e2e1 Reviewed-on: https://chromium-review.googlesource.com/1158684Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#54967}
-
Michael Starzinger authored
We instantiate the JumpTableAssembler in patching mode (i.e. directly on existing code without an intermittent buffer). In this mode it is not possible to record reloc information. This makes sure we no longer just blindly write into the non-existing buffer. R=clemensh@chromium.org BUG=v8:8028 Change-Id: I4abb8f06cf819fef608e901c4740263f0cecd08a Reviewed-on: https://chromium-review.googlesource.com/1166834 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Sathya Gunasekaran authored
This patch ports most of the Intl.Collator from JS to C++. The Intl.Collator object no longer stores all the resolved values. Instead these are looked up on demand as part of Intl.Collator.prototype.resolvedOptions(), saving several words. In the future, we can cache the result of the resolvedOptions as well. In this patch, we use ICU to do parsing of the unicode extension in the bcp47 language tag instead of using a custom extension parser. This patch also fixes several spec compliance bugs as well. Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Iaaa7be4a628404da1bd83d882e04a2c6de70ebd9 Bug: v8:5751, v8:7480 Reviewed-on: https://chromium-review.googlesource.com/1165084 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Michael Starzinger authored
R=sigurds@chromium.org Change-Id: I2f8210a386fa39030c7ffe4c7d0f25bd845c612a Reviewed-on: https://chromium-review.googlesource.com/1166908 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Shiyu Zhang authored
Partial constant pool aims at reducing code size and only takes effect for shareable constants. Different from ARM’s constant pool, partial constant pool does not emit constant pools at the end of each code object. Instead, it keeps the first shareable constant inlined in the instructions and uses rip-relative memory loadings for the same constants in subsequent instructions. These rip-relative memory loadings will target at the position of the first inlined constant. For example: REX.W movq r10,0x7f9f75a32c20 ; 10 bytes … REX.W movq r10,0x7f9f75a32c20 ; 10 bytes … turns into REX.W movq r10,0x7f9f75a32c20 ; 10 bytes … REX.W movq r10,[rip+0xffffff96] ; 7 bytes … Change-Id: I25a417f6d82da96024989bddf0451d7df9340c00 Reviewed-on: https://chromium-review.googlesource.com/1082231Reviewed-by:
-
