1. 14 May, 2019 2 commits
  2. 13 May, 2019 28 commits
  3. 12 May, 2019 1 commit
  4. 11 May, 2019 3 commits
  5. 10 May, 2019 6 commits
    • Igor Sheludko's avatar
      Revert "Reland "[ptr-compr][x64] Temporarily enable pointer compression on x64"" · 37d89edf
      Igor Sheludko authored
      This reverts commit d61a9347.
      
      Reason for revert: May cause UBSan failures
      
      Original change's description:
      > Reland "[ptr-compr][x64] Temporarily enable pointer compression on x64"
      >
      > This is a reland of 42beed97
      >
      > Relanding after fixing Chromium issues.
      >
      > Original change's description:
      > > [ptr-compr][x64] Temporarily enable pointer compression on x64
      > >
      > > ... and make sure that the x64 ptr-compr bots proceed testing V8 without
      > > pointer compression in order to keep testing the full pointer mode.
      > >
      > > Bug: v8:7703
      > > Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng,v8_linux64_tsan_rel
      > > Change-Id: Iee725deda813425a6f0722948b54976154f50909
      > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1497139
      > > Reviewed-by: Michael Hablich <hablich@chromium.org>
      > > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#60230}
      >
      > Bug: v8:7703
      > Change-Id: Ib1498609603cb03be2464043658131d5a2f1e012
      > Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng,v8_linux64_tsan_rel
      > Cq-Include-Trybots: luci.chromium.try:fuchsia_x64,linux-rel,mac-rel
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559850
      > Commit-Queue: Igor Sheludko <ishell@chromium.org>
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#61416}
      
      TBR=machenbach@chromium.org,ishell@chromium.org
      
      Change-Id: I77d8fe848e53cbea4be89429de967a5966ae7e48
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:7703
      Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng, v8_linux64_tsan_rel
      Cq-Include-Trybots: luci.chromium.try:fuchsia_x64, linux-rel, mac-rel
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1606500
      Commit-Queue: Igor Sheludko <ishell@chromium.org>
      Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61427}
      37d89edf
    • Andrew Grieve's avatar
      Discard CHECK failure messages for official builds to save binary size · 28df916b
      Andrew Grieve authored
      FATAL() calls with more than one argument are preserved.
      
      The rest of chrome does this as well. Stack traces and minidumps should
      be sufficient for analyzing the reason for crashes.
      
      This saves 110kb for Android arm32.
      
      Bug: chromium:958807
      Change-Id: I88a1ec82f1ed7bd5e7dbccf6d645d5584f16de82
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1598159
      Commit-Queue: Andrew Grieve <agrieve@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61426}
      28df916b
    • Ben Smith's avatar
      [wasm] Display wasm globals in the inspector · baf84940
      Ben Smith authored
      They are added under the global scope object, as follows:
      
        {
          "memory": ...,
          "globals": {
            "global#0": ...,
            "global#1": ...,
            "global#2": ...,
          }
        }
      
      We currently don't have any way to name globals in the wasm binary
      format, but it is possible to extend the name section with these names
      in the future.
      
      Bug: v8:6846
      Change-Id: I79fa4ed3d83964bc8e26d66516605d41e92b3d03
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1601829
      Commit-Queue: Ben Smith <binji@chromium.org>
      Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61425}
      baf84940
    • Johannes Henkel's avatar
      [DevTools] Detect if the state of the inspector session was encoded as CBOR. · 40257054
      Johannes Henkel authored
      In the longer run we only want the CBOR code path, for now we need to handle
      JSON as well. So we convert if possible.
      
      Change-Id: I726b737f4cd2602d4fb676ce7cf996fcd1ba33e9
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1598254Reviewed-by: 's avatarAlexei Filippov <alph@chromium.org>
      Commit-Queue: Johannes Henkel <johannes@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61424}
      40257054
    • Frank Tang's avatar
      Extend the tests for more Intl objects. · 02c19000
      Frank Tang authored
      Bug: v8:5751
      Change-Id: Icfd4b86499395b49f67a97e46d1b1b87ed9c01eb
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1605356Reviewed-by: 's avatarMathias Bynens <mathias@chromium.org>
      Commit-Queue: Frank Tang <ftang@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61423}
      02c19000
    • Seth Brenith's avatar
      [torque] Automatically generate verifier functions · e483fb27
      Seth Brenith authored
      This change generates functions that verify the things that Torque knows
      about objects and their fields. We still must implement each verifier
      function in objects-debug.cc, but we can call into the generated code to
      verify that field types match their Torque definitions. If no additional
      verification is required, we can use the macro USE_TORQUE_VERIFIER as a
      shorthand for a verifier that calls the corresponding generated
      function.
      
      A new annotation @noVerifier can be applied to both class and field
      definitions, to prevent generating verification code. This allows fully
      customized verification for complicated cases like
      JSFunction::prototype_or_initial_map, which might not exist at all, and
      JSObject::elements, which might be a one pointer filler map.
      
      Because Factory::InitializeJSObjectFromMap fills new objects with
      undefined values, and many verifiers need to deal with partially-
      initialized objects, the generated verifiers allow undefined values on
      every class deriving from JSObject. In cases where stricter checks were
      previously performed, they are kept in objects-debug.cc.
      
      Bug: v8:7793
      Change-Id: I84034efadca89ba0aceddf92e886ffbfaa4c23fa
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1594042
      Commit-Queue: Seth Brenith <seth.brenith@microsoft.com>
      Reviewed-by: 's avatarSigurd Schneider <sigurds@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61422}
      e483fb27