1. 08 Aug, 2022 1 commit
  2. 01 Aug, 2022 1 commit
    • Nico Weber's avatar
      Make bitfields only as wide as necessary for enums · d15d49b0
      Nico Weber authored
      clang now complains when a BitField for an enum is too wide.
      We could suppress this, but it seems kind of useful from an
      uninformed distance, so I made a few bitfields smaller instead.
      
      (For AddressingMode, since its size is target-dependent, I added
      an explicit underlying type to the enum instead, which suppresses
      the diag on a per-enum basis.)
      
      This is without any understanding of the code I'm touching.
      Especially the change in v8-internal.h feels a bit risky to me.
      
      Bug: chromium:1348574
      Change-Id: I73395de593045036b72dadf4e3147b5f7e13c958
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3794708
      Commit-Queue: Nico Weber <thakis@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
      Auto-Submit: Nico Weber <thakis@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#82109}
      d15d49b0
  3. 29 Jul, 2022 1 commit
    • Clemens Backes's avatar
      [wasm] Allocate the lazy compile table anywhere · e2c3e4f2
      Clemens Backes authored
      The jump table and far jump table are allocated once per code space, but
      the lazy compile table only needs to exist exactly once, and it does not
      really matter in which code space we allocate it.
      Before dynamic tiering, we could always allocate it in the initial code
      space (which was empty at the point when we allocated it), but with
      deserialization of a partially tiered module we can end up in a
      situation where we first deserialize some TurboFan functions into the
      initial code space, and when we later try to allocate the lazy compile
      table (when we encounter the first non-serialized function) we do not
      have enough space any more in the initial code space.
      
      This CL allows to allocate the lazy compile jump table in any code space
      to avoid that failure.
      
      R=thibaudm@chromium.org
      
      Bug: chromium:1348472, chromium:1348214
      Change-Id: I58c9a8a6541f2ab7df26ddfd1b65d31cc99337fc
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3792607Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
      Commit-Queue: Clemens Backes <clemensb@chromium.org>
      Cr-Commit-Position: refs/heads/main@{#82086}
      e2c3e4f2
  4. 27 Jul, 2022 1 commit
  5. 26 Jul, 2022 3 commits
  6. 14 Jul, 2022 1 commit
  7. 13 Jul, 2022 3 commits
  8. 12 Jul, 2022 2 commits
  9. 08 Jul, 2022 3 commits
  10. 06 Jul, 2022 1 commit
  11. 05 Jul, 2022 3 commits
  12. 29 Jun, 2022 4 commits
  13. 27 Jun, 2022 1 commit
  14. 15 Jun, 2022 1 commit
  15. 14 Jun, 2022 3 commits
  16. 13 Jun, 2022 2 commits
  17. 11 Jun, 2022 1 commit
  18. 10 Jun, 2022 1 commit
  19. 09 Jun, 2022 1 commit
  20. 08 Jun, 2022 2 commits
  21. 07 Jun, 2022 1 commit
  22. 31 May, 2022 1 commit
  23. 30 May, 2022 1 commit
  24. 26 May, 2022 1 commit