- 23 May, 2019 35 commits
-
-
Clemens Hammacher authored
The {new_potentially_dead_code_size_} counter is used to decide when to trigger the next GC. Without resetting, we will trigger lots of GCs once the counter hits the limit, see "V8.WasmModuleNumberOfCodeGCsTriggered" counter. R=mstarzinger@chromium.org Bug: v8:8217 Change-Id: I046b84d1f67f8cadb02fd3f876bb8c645e24edee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627340Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61795}
-
Andreas Haas authored
The indirect function table only exists for table 0 at the moment. Therefore we should initialize it only for table 0. R=mstarzinger@chromium.org Bug: chromium:964607 Change-Id: I88a3a5cb5ebec7f0456adc2cebdf5cc499b22761 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624804Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#61794}
-
Milad Farazmand authored
Port 878ccb33 Original Commit Message: This CL was generated by an automatic clang AST rewriter using this matcher expression: callExpr( callee( cxxMethodDecl( hasName("operator->"), ofClass(isSameOrDerivedFrom("v8::internal::Object")) ) ), argumentCountIs(1) ) The "->" at the expression location was then rewritten to ".". R=clemensh@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: Ibe92f0332da0e478f213880462b4d3460f8260c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627569Reviewed-by: Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#61793}
-
Michael Starzinger authored
This makes the WebAssembly function constructor return a proper function object. Note that the returned object is not yet callable, only the prototype structure is in place. R=jkummerow@chromium.org TEST=mjsunit/wasm/type-reflection BUG=v8:7742 Change-Id: If6a3d0ae7078b5526606eef1b8fd4815353b850b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627343 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#61792}
-
Clemens Hammacher authored
The previous logic published whenever a TurboFan function was *finished*. Since we compile big functions first, the first TurboFan compilation can take quite some time, and we will only publish previously compiled Liftoff functions once that first TurboFan compilation is done. This CL changes that logic to publish all previous results *before* starting a TurboFan compilation. Drive-by: Add some trace events for interesting events. R=ahaas@chromium.org Bug: v8:8916, chromium:966351, chromium:944755 Change-Id: I669d6ea16bdc3f29685df153a7ed45875c28a843 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627532Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61791}
-
Yang Guo authored
NOPRESUBMIT=true TBR=mstarzinger@chromium.org Bug: v8:9247 Change-Id: I4cd6b79a1c2cba944f6f23caed59d4f1a4ee358b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624217 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#61790}
-
Michaël Zasso authored
Fixes the following error caught by the Node.js CI: ../deps/v8/src/api.cc:8943:10: error: no viable conversion from returned value of type 'unique_ptr<v8::internal::MicrotaskQueue, default_delete<v8::internal::MicrotaskQueue>>' to function return type 'unique_ptr<v8::MicrotaskQueue, default_delete<v8::MicrotaskQueue>>' return microtask_queue; ^~~~~~~~~~~~~~~ Change-Id: Ic09dab46bb8f87a2b3b59f5836e0883bfe0e9681 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627533 Commit-Queue: Michaël Zasso <mic.besace@gmail.com> Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61789}
-
Toon Verwaest authored
This was accidentally dropped when unifying the internalization code. Change-Id: I2fd7127f85f0e3e9abd1ae834130f0c9da37363e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627529Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#61788}
-
Jakob Gruber authored
These were added to support specific cross-compile scenarios that should now be covered by the --target-os and --target-arch flags. Bug: v8:9103 Change-Id: I848f4f39cecc83f9ec8529c4f8855662059e3dc5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624219 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#61787}
-
Clemens Hammacher authored
We now have a src/d8 directory, and having "d8" in .gitignore makes git ignore all new files in this directory, and also hides the directory in some IDEs. R=yangguo@chromium.org No-Try: true Change-Id: I3106378417c1fe9ebc369275eb52d5438cee8825 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627530Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61786}
-
Jakob Gruber authored
Split out embedded file writers for AIX, Windows, and macOS. These are no longer selected by compile-time defines (e.g. V8_OS_WIN, V8_TARGET_ARCH_X64) but by --target-os and --target-arch runtime flags. Bug: v8:9103 Change-Id: I5d5cac15e48b5c743d74f8a382606a6194ba7865 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624216 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#61785}
-
Simon Zünd authored
This CL adds all fields to StackFrameInfo that are necessary to stringify a stack trace frame. This is another step towards disentangling symbolizing and serializing: - Symbolization collects all the necessary strings, numbers and flags for a stack trace frame. - Serialization turns the symbolized stack trace frame into a string. Drive-by: Moves the lazy initialization of StackFrameInfo into the private getter. Bug: v8:8742 Change-Id: Ic3e0fb6b3d0f0e260014af44380f1f30216b1b26 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627346Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61784}
-
Peter Marshall authored
I accidentally broke this with the last CL because the FYI bot does not block landing. Add initialization of perfetto when building with perfetto enabled. Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng Bug: v8:8339 Change-Id: I10378b72bff731fac6caa75df37a355df4b804dc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627345 Auto-Submit: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#61783}
-
Jakob Gruber authored
Introduce a single point to emit CodeCreateEvents for all builtins in Isolate::Init. At this location, we cover both the case of builtin generation (e.g. in mksnapshot) and deserialized builtins (in standard builds), whereas previously we only emitted events post-builtin-generation. In order to preserve behavior for bytecode handler events, pack the bytecode and operand scale into our existing builtin metadata table. Drive-by: Update way-out-of-date comment in the static initializer check. Bug: v8:8674 Change-Id: Iced8f73568e920846cde6f7b0a9c1e61844258ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627337 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Dan Elphick <delphick@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61782}
-
Georg Neis authored
When encountering uninitialized feedback, mark the environment as dead such that we skip over the following bytecodes. Start full processing again when we reach a bytecode that is either a jump target or an exception handler entry. For now, don't support this optimization when compiling for OSR. Bug: v8:7790 Change-Id: I8177b7fa31ea43d205a2708310b0b0e67302001e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1621930 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#61781}
-
Peter Marshall authored
This is a reland of a03ed626 Removed the added test which was failing on win32. The test was unrelated to the CL; we can add it later. Original change's description: > [tracing] Add a configurable output stream for perfetto tracing > > Add the ability to provide perfetto with an output stream for the JSON > consumer rather than hardcode it. D8 will use this interface exclusively > once the old trace controller is removed. > > Also add a test for scope-managed trace events and their duration - this > was leftover from a previous CL. > > Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng > Bug: v8:8339 > Change-Id: I1c45e17e528b549a4cfdaecabd33c7ac4ab4af77 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1611801 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#61753} TBR=jgruber@chromium.org, ulan@chromium.org Bug: v8:8339 Change-Id: I3442a4d111e12947c107e7d0c226ae934acd06e4 Cq-Include-Trybots: luci.v8.try:v8_linux64_perfetto_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627334Reviewed-by: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#61780}
-
Georg Neis authored
Change-Id: Ib1233607236c991af0125f0197b9f89b10b4519d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1625990 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#61779}
-
Tobias Tebbi authored
This avoids the generation of fake external classes. Bug: v8:7793 Change-Id: I9744b299d3ec474d72b298b4f6143f95e345d1d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1625991Reviewed-by: Simon Zünd <szuend@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#61778}
-
Georg Neis authored
We were sometimes printing the data pointer, and sometimes the handle location. This CL always uses the existing operator<< overload to print ObjectRefs, which currently means printing the data pointer. Bug: v8:7790 Change-Id: Ic5e2dad075678d2250bc0bcb170046d055680572 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1625989Reviewed-by: Michael Stanton <mvstanton@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Auto-Submit: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#61777}
-
Clemens Hammacher authored
R=leszeks@chromium.org No-Try: true Bug: v8:9183 Change-Id: I9372bdc5d3789a1bbc50ef2737577c4f60173bce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627342Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61776}
-
Frederik Gossen authored
The python script allows to read the custom section "compilationHints" from a Wasm module. It prints all hints to standard out. Bug: v8:9003 Change-Id: Ife8173e3267557d8adf4b6739f45060d386f25dd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619764 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#61775}
-
Clemens Hammacher authored
This fixes compile errors after https://crrev.com/c/1624788. TBR=jkummerow@chromium.org No-Try: true Bug: v8:9183, v8:3770 Change-Id: I982e77e86389163f1549bbb02621b17972bbc158 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627336Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61774}
-
Peter Marshall authored
This is only used by ElementsKindToString(!). Implement ElementsKindToString with a big 'ol switch. The compiler will give us an error if we forget an ElementsKind. Bug: v8:9183 Change-Id: I1ed73ecac33aa7318a97f31794473d9afa16961c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624802 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61773}
-
Benedikt Meurer authored
The tests need to properly hold on to the original fast-mode map, otherwise the GC might clear that, and so the NormalizedMapCache lookup would fail due to that. Bug: chromium:963411, v8:9114, v8:9183, v8:9267 Change-Id: Ic41ed363959a5c182c74097767dc14c366076e17 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627333Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#61772}
-
Benedikt Meurer authored
The `FunctionTemplate::SetHiddenPrototype()` API was deprecated beginning of the year and all uses in Node.js and Chrome have been removed appropriately. This removes the implementation of the method and the bit in the `FunctionTemplateInfo`, but retains the bit in the Map for now. That will be cleaned up as a second step later. Bug: v8:9183, v8:9267 Change-Id: I9aa2fc484b3321f4f42a29a0a38d72a6d30054a7 Cq-Include-Trybots: luci.chromium.try:linux-rel,win7-rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627329 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61771}
-
Benedikt Meurer authored
There's a `Map::IsDictionaryMap()` method in addition to the `Map::is_dictionary_map()`, which apparently do very different things: The former checks whether the instance type of the Map is in a certain range (FIRST_DICTIONARY_TYPE to LAST_DICTIONARY_TYPE), while the latter checks the `is_dictionary_map` bit (which means that the backing store for the properties of a JSObject is in slow mode). To make matters worse there's also `CodeStubAssembler::IsDictionaryMap()`, which does the bit check similar to `Map::is_dictionary_map()`. And to make matters even worse the FIRST_DICTIONARY_TYPE to LAST_DICTIONARY_TYPE range also contains instance types for classes that aren't subclass of `Dictionary` (despite a comment stating the opposite). So in conclusion it's best to remove the confusing `Map::IsDictionaryMap()` method, which is anyways wrong, and just test explicitly for `NameDictionary`, `NumberDictionary` or `GlobalDictionary` in the appropriate places. Bug: v8:9183 Change-Id: If35f73261e3cc96938ebf499bf32be3ec725288b Cq-Include-Trybots: luci.chromium.try:linux-rel,win7-rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627330 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61770}
-
Yang Guo authored
TBR=bmeurer@chromium.org,leszeks@chromium.org Bug: v8:9247 Change-Id: I8d14d0192ea8c705f8274e8e61a162531826edb6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624220Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#61769}
-
Clemens Hammacher authored
For consistency, {Object} members should only be accessed via ".". CL https://crrev.com/c/1624209 cleaned up the code base already. This CL removes the now dead operator. R=jkummerow@chromium.org Bug: v8:9183, v8:3770 Change-Id: I599dcd49d79bfc68f970fe872b64b3b2680cddd5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624788 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#61768}
-
Yang Guo authored
R=szuend@chromium.org Change-Id: I7d8eb6f26dd0cecd749a66cd2b240ff27cbba985 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1621927 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61767}
-
Yang Guo authored
Bug: v8:9247 Change-Id: Iaed837e146603c37b0ad64605405c442154cf1b0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624222 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#61766}
-
Sigurd Schneider authored
The type of the argument makes it clear what we're internalizing, and this allows us to choose either one based on a template parameter. Change-Id: I6d7865e7fdef364f6cf10ff9267034df182d7539 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624212 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61765}
-
Clemens Hammacher authored
This CL was generated by an automatic clang AST rewriter using this matcher expression: callExpr( callee( cxxMethodDecl( hasName("operator->"), ofClass(isSameOrDerivedFrom("v8::internal::Object")) ) ), argumentCountIs(1) ) The "->" at the expression location was then rewritten to ".". R=jkummerow@chromium.org TBR=mstarzinger@chromium.org,verwaest@chromium.org,yangguo@chromium.org Bug: v8:9183, v8:3770 No-Try: true No-Tree-Checks: true Change-Id: I0a7ecabdeafe51d0cf427f5280af0c7cab96869e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624209Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61764}
-
Jun Lim authored
In fast mode, this CL try to avoid calling substring in @@match. For an ATOM type regexp, hold the literal string to search for before the loop and reuse the string instead of calling substring in the loop. Change-Id: Ice314ebf146261cf206c21cb1530a2a44d3c42ae Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1618435Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#61763}
-
Yang Guo authored
Bug: v8:9247 Change-Id: I0023200c54fa6499ae4e2cf5e4c89407cc35f187 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624218Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Stanton <mvstanton@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61762}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/0742a14..97564df Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/9ea486b..6884242 Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/chromium/llvm-project/libcxx/+log/9b96c3d..5938e05 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/535dc1d..4d346fb Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/c7e440c..181e44c Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/2db48c7..9d46446 Rolling v8/tools/swarming_client: https://chromium.googlesource.com/infra/luci/client-py/+log/1b65f4e..779c4f0 TBR=machenbach@chromium.org,sergiyb@chromium.org,tmrts@chromium.org Change-Id: I7b2824622066da423b7f7584338a42e06902701d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627110Reviewed-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@{#61761}
-
- 22 May, 2019 5 commits
-
-
Mathias Bynens authored
https://github.com/tc39/ecma262/issues/1530 https://github.com/tc39/test262/pull/2161 Bug: v8:7834, v8:9131 Change-Id: I9c5efe9d6eec6c5dabc120d1b1089341ed5b1088 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1625992 Commit-Queue: Mathias Bynens <mathias@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Auto-Submit: Mathias Bynens <mathias@chromium.org> Reviewed-by: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#61760}
-
Frank Tang authored
Adds "calendar" and "numberingSystem" options for Intl.DateTimeForamt and "numberingSystem" for Intl.NumberFormat. Plan to flip to ship in early June (after m76 branch) for chrome m77. Spec: https://github.com/tc39/ecma402/pull/175 I2I: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/v8-dev/ftang%7Csort:date/v8-dev/7sk-rEHuCY4/n7kH0WzyAwAJ Tests: test262/intl402/NumberFormat/numbering-system-options test262/intl402/DateTimeFormat/numbering-system-calendar-options intl/number-format/check-numbering-system intl/date-format/check-numbering-system intl/date-format/check-calendar Bug: v8:9154 Change-Id: I80020b9af6bf9c87f5a1efc7aac3080e723eea34 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1622728Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#61759}
-
Toon Verwaest authored
Change-Id: Ibb3f6d5a0f2f24ff5359ca280f058a20c8215ac1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624801 Auto-Submit: Toon Verwaest <verwaest@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#61758}
-
Paolo Severini authored
Function win64_unwindinfo::RegisterNonABICompliantCodeRange() calls LoadNtdllUnwindingFunctions() to dynamically load from ntdll a couple of functions that are not available on Windows 7. Unfortunately there is a race condition in LoadNtdllUnwindingFunctions() that can cause a crash when multiple isolates are initialized concurrently. This can be fixed using base::CallOnce(). Bug: v8:9204 Change-Id: I5c57708ab5f16e9ef9f897efce1ccdf591e2f828 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1623592Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#61757}
-
Z Duong Nguyen-Huu authored
Bug: v8:8996 Change-Id: Icb454f8ff5f0964b019f360e71119158341307de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1622743 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61756}
-