1. 17 Mar, 2017 1 commit
    • neis's avatar
      Disentangle assembler from isolate. · 94b088ca
      neis authored
      This is a first step towards moving Turbofan code generation off the main thread.
      
      Summary of the changes:
      - AssemblerBase no longer has a pointer to the isolate. Instead, its
        constructor receives the few things that it needs from the isolate (on most
        architectures this is just the serializer_enabled flag).
      - RelocInfo no longer has a pointer to the isolate. Instead, the functions
        that need it take it as an argument.  (There are currently still a few that
        implicitly access the isolate through a HeapObject.)
      - The MacroAssembler now explicitly holds a pointer to the isolate (before, it
        used to get it from the Assembler).
      - The jit_cookie also moved from AssemblerBase to the MacroAssemblers, since
        it's not used at all in the Assemblers.
      - A few architectures implemented parts of the Assembler with the help
        of a Codepatcher that is based on MacroAssembler.  Since the Assembler no
        longer has the isolate, but the MacroAssembler still needs it, this doesn't
        work anymore.  Instead, these Assemblers now use a new PatchingAssembler.
      
      BUG=v8:6048
      
      Review-Url: https://codereview.chromium.org/2732273003
      Cr-Commit-Position: refs/heads/master@{#43890}
      94b088ca
  2. 06 Mar, 2017 1 commit
    • Clemens Hammacher's avatar
      [wasm] Fix code specialization for empty memory buffer · 7d8a3028
      Clemens Hammacher authored
      From asm.js code we might get an empty ArrayBuffer as heap memory. In
      this case, both the old memory start and the new memory start will be
      nullptr. The size however has to be patched from default_size to 0.
      
      This CL changes code specialization to be able to either patch memory
      references, or patch memory sizes or both.
      
      R=titzer@chromium.org, ahaas@chromium.org
      BUG=chromium:698587
      
      Change-Id: I4d9d811d75cb83842f23df317e8e7fc02aeb5146
      Reviewed-on: https://chromium-review.googlesource.com/450257
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarAndreas Haas <ahaas@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#43613}
      7d8a3028
  3. 23 Feb, 2017 1 commit
  4. 10 Jan, 2017 1 commit
  5. 11 Nov, 2016 1 commit
  6. 04 May, 2016 1 commit
    • gdeepti's avatar
      Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers... · 117a56b7
      gdeepti authored
      Add new relocation type WASM_MEMORY_SIZE_REFERENCE, use relocatable pointers to update wasm memory size references in generated code.
       - Add new RelocInfo mode WASM_MEMORY_SIZE_REFERENCE in the assembler and add relocation information to immediates in compare instructions.
       - Use relocatable constants for MemSize/BoundsCheck in the wasm compiler
      
      R=titzer@chromium.org, yangguo@chromium.org, bradnelson@chromium.org
      
      Review-Url: https://codereview.chromium.org/1921203002
      Cr-Commit-Position: refs/heads/master@{#36044}
      117a56b7
  7. 12 Apr, 2016 2 commits
  8. 11 Apr, 2016 1 commit
  9. 01 Apr, 2016 2 commits