1. 17 Sep, 2019 1 commit
  2. 29 Jul, 2019 3 commits
    • Clemens Hammacher's avatar
      Reland "[utils] Make BitField final" · 0cabc6a0
      Clemens Hammacher authored
      This is a reland of 658ff200
      
      Original change's description:
      > [utils] Make BitField final
      > 
      > We have hundreds of classes that derive from {BitField} without adding
      > any functionality. This CL switches all such occurrences to 'using'
      > declarations instead.
      > 
      > Before:
      >   class MyBitField : public BitField<int, 6, 4, MyEnum> {};
      > After:
      >   using MyBitField = BitField<int, 6, 4, MyEnum>;
      > 
      > This might reduce compilation time by reducing the number of existing
      > classes.
      > 
      > The old pattern is forbidden now by making {BitField} final.
      > 
      > R=yangguo@chromium.org
      > 
      > Bug: v8:9396, v8:7629
      > Change-Id: I8a8364707e8eae0bb522af2459c160e3293eecbb
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1722565
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#62956}
      
      Bug: v8:9396, v8:7629
      Change-Id: Ic68541af9d1e8d0340691970922f282b24a9767f
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1724379Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62959}
      0cabc6a0
    • Clemens Hammacher's avatar
      Revert "[utils] Make BitField final" · 753a07db
      Clemens Hammacher authored
      This reverts commit 658ff200.
      
      Reason for revert: Fails no-i18n bot: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20noi18n%20-%20debug/27826
      
      Original change's description:
      > [utils] Make BitField final
      > 
      > We have hundreds of classes that derive from {BitField} without adding
      > any functionality. This CL switches all such occurrences to 'using'
      > declarations instead.
      > 
      > Before:
      >   class MyBitField : public BitField<int, 6, 4, MyEnum> {};
      > After:
      >   using MyBitField = BitField<int, 6, 4, MyEnum>;
      > 
      > This might reduce compilation time by reducing the number of existing
      > classes.
      > 
      > The old pattern is forbidden now by making {BitField} final.
      > 
      > R=​yangguo@chromium.org
      > 
      > Bug: v8:9396, v8:7629
      > Change-Id: I8a8364707e8eae0bb522af2459c160e3293eecbb
      > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1722565
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#62956}
      
      TBR=yangguo@chromium.org,clemensh@chromium.org
      
      Change-Id: I50234a09c77aa89fdcf1e01c2497cc08d3ac79a8
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: v8:9396, v8:7629
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1724377Reviewed-by: 's avatarClemens Hammacher <clemensh@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62958}
      753a07db
    • Clemens Hammacher's avatar
      [utils] Make BitField final · 658ff200
      Clemens Hammacher authored
      We have hundreds of classes that derive from {BitField} without adding
      any functionality. This CL switches all such occurrences to 'using'
      declarations instead.
      
      Before:
        class MyBitField : public BitField<int, 6, 4, MyEnum> {};
      After:
        using MyBitField = BitField<int, 6, 4, MyEnum>;
      
      This might reduce compilation time by reducing the number of existing
      classes.
      
      The old pattern is forbidden now by making {BitField} final.
      
      R=yangguo@chromium.org
      
      Bug: v8:9396, v8:7629
      Change-Id: I8a8364707e8eae0bb522af2459c160e3293eecbb
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1722565Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#62956}
      658ff200
  3. 27 May, 2019 1 commit
    • Clemens Hammacher's avatar
      [cleanup] Replace simple typedefs by using · a335f2ae
      Clemens Hammacher authored
      This replaces all typedefs that define types and not functions by the
      equivalent "using" declaration.
      
      This was done mostly automatically using this command:
      ag -l '\btypedef\b' src test | xargs -L1 \
           perl -i -p0e 's/typedef ([^*;{}]+) (\w+);/using \2 = \1;/sg'
      
      Patchset 2 then adds some manual changes for typedefs for pointer types,
      where the regular expression did not match.
      
      R=mstarzinger@chromium.org
      TBR=yangguo@chromium.org, jarin@chromium.org
      
      Bug: v8:9183
      Change-Id: I6f6ee28d1793b7ac34a58f980b94babc21874b78
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1631409
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61849}
      a335f2ae
  4. 24 May, 2019 1 commit
  5. 23 May, 2019 1 commit
  6. 04 Apr, 2019 1 commit
  7. 06 Mar, 2019 1 commit
    • Georg Neis's avatar
      [turbofan] Don't access heap in ReduceElementAccess · 4d39e342
      Georg Neis authored
      This CL builds on top of feedback preprocessing. It brokerizes
      all parts of element access reduction and disallows heap access there
      (except for debug tracing).
      
      To make this work without breaking tests (when concurrent inlining is
      enabled):
      - We don't inline functions that weren't serialized for compilation.
      - We don't optimize for constant typed-array receivers when the typed
        array wasn't serialized.
      
      This means that from now on --concurrent-inlining (and thus --future)
      may result in less optimization than the default configuration.
      
      Bug: v8:7790
      Change-Id: I22685258b7d841fc9183bf99775d3f09cd272927
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1495556
      Commit-Queue: Georg Neis <neis@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#60061}
      4d39e342
  8. 01 Mar, 2019 1 commit
  9. 13 Feb, 2019 1 commit
  10. 04 Dec, 2018 1 commit
  11. 22 Oct, 2018 1 commit
  12. 17 Oct, 2018 1 commit
  13. 16 Oct, 2018 1 commit
  14. 21 Sep, 2018 1 commit
  15. 20 Sep, 2018 1 commit
  16. 25 Jul, 2018 1 commit
  17. 17 Jan, 2017 2 commits
    • jochen's avatar
      Assert that context creation doesn't throw · 0389df51
      jochen authored
      Instead, it is supposed to just return an empty context if it failed.
      Also don't invoke interceptors (we don't for the parts that deserialize
      from the snapshot anyways).
      
      BUG=v8:5830
      R=yangguo@chromium.org
      
      Review-Url: https://codereview.chromium.org/2636903002
      Cr-Commit-Position: refs/heads/master@{#42404}
      0389df51
    • leszeks's avatar
      [ast] Remove internalization before AST rewriting · bb71555e
      leszeks authored
      This internalization was not necessary, since the rewriting does not use
      the .result name string.
      
      The subsequent internalization is still needed, so to simplify later
      refactoring, this CL also adds "releasing" of the disallow scopes and
      uses them here immediately before the second internalize. Notably, this
      means that the rewriting is now also in the disallow scopes.
      
      Driveby: Remove isolate from the rewriter's processor constructor.
      
      BUG=v8:5832
      
      Review-Url: https://codereview.chromium.org/2635913002
      Cr-Commit-Position: refs/heads/master@{#42403}
      bb71555e
  18. 26 Sep, 2016 1 commit
    • jgruber's avatar
      Enable component builds for fuzzers · 22606f0c
      jgruber authored
      V8 is collecting a growing amount of fuzzers, all of which take substantial
      space on the bots and in chromium build archives. This CL improves that
      situation by allowing component (shared library) builds for almost all fuzzers.
      
      The parser fuzzer is handled as an exception since it would require exporting a
      large number of additional functions.
      
      A component build results in about a 50-100x improvement in file size for each
      fuzzer (~50M-100M to around 1.1M).
      
      BUG=chromium:648864
      CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_compile_dbg_ng;master.tryserver.chromium.android:android_clang_dbg_recipe
      
      Review-Url: https://codereview.chromium.org/2360983002
      Cr-Commit-Position: refs/heads/master@{#39709}
      22606f0c
  19. 30 Sep, 2015 1 commit
  20. 08 Sep, 2015 1 commit
  21. 21 Oct, 2014 1 commit
  22. 29 Sep, 2014 1 commit
  23. 04 Aug, 2014 1 commit
  24. 16 Jul, 2014 1 commit
  25. 30 Jun, 2014 1 commit
  26. 03 Jun, 2014 1 commit
  27. 29 Apr, 2014 1 commit
  28. 28 Apr, 2014 1 commit
  29. 19 Mar, 2014 2 commits
  30. 12 Aug, 2013 1 commit
  31. 13 Jun, 2013 1 commit
  32. 05 Jun, 2013 1 commit
  33. 03 Jun, 2013 1 commit