1. 30 Sep, 2016 1 commit
  2. 20 Jul, 2016 1 commit
  3. 09 Jun, 2016 1 commit
    • lpy's avatar
      Move hashmap into src/base. · 2fd55667
      lpy authored
      We ported hashmap.h into libsampler as a workaround before, so the main focus of
      this patch is to reduce code duplication. This patch moves the hashmap into
      src/base as well as creates DefaultAllocationPolicy using malloc and free.
      
      BUG=v8:5050
      LOG=n
      
      Review-Url: https://codereview.chromium.org/2010243003
      Cr-Commit-Position: refs/heads/master@{#36873}
      2fd55667
  4. 24 May, 2016 1 commit
  5. 19 May, 2016 1 commit
  6. 16 Feb, 2016 1 commit
  7. 10 Feb, 2016 1 commit
    • mlippautz's avatar
      [heap] Move to page lookups for SemiSpace, NewSpace, and Heap containment methods · cfbd2561
      mlippautz authored
      Preparing the young generation for (real) non-contiguous backing memory, this
      change removes object masks that are used to compute containment in semi and new
      space. The masks are replaced by lookups for object tags and page headers, where
      possible.
      
      Details:
      - Use the fast checks (page header lookups) for containment in regular code.
      - Use the slow version that masks out the page start adress and iterates all
        pages of a space for debugging/verification.
      - The slow version works for off-heap/unmapped memory.
      - Encapsulate all checks for the old->new barrier in Heap::RecordWrite().
      
      BUG=chromium:581412
      LOG=N
      
      Review URL: https://codereview.chromium.org/1632913003
      
      Cr-Commit-Position: refs/heads/master@{#33857}
      cfbd2561
  8. 22 Jan, 2016 1 commit
    • mbrandy's avatar
      Introduce BUILTIN_CALL_PAIR. · 433e8848
      mbrandy authored
      This change allows the PPC simulator to execute on PPC hardware where,
      due to calling conventions, we must distinguish between Object* and
      ObjectPair return values.
      
      We find this useful as another available option for debugging certain
      problems.  While not strictly necessary for Intel platforms, we hope
      that this is less offensive now that BUILTIN_CALL_TRIPLE has been
      added.
      
      BUG=
      R=rmcilroy@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
      
      Review URL: https://codereview.chromium.org/1604653006
      
      Cr-Commit-Position: refs/heads/master@{#33475}
      433e8848
  9. 15 Jan, 2016 1 commit
    • rmcilroy's avatar
      [Interpreter] Add ForInPrepare runtime function which returns a ObjectTriple. · 84f8a506
      rmcilroy authored
      Adds a ForInPrepare Runtime function which returns a triple of
      cache_type, cache_array and cache_length.
      
      This requires adding support to CEntryStub to call runtime functions
      which return a ObjectTriple - a struct containing three Object*
      pointers. Also did some cleanup of the x64 CEntryStub to avoid
      replicated code.
      
      Replaces the interpreter's use of the ad-hock InterpreterForInPrepare
      Runtime function with ForInPrepare in preparation for fixing deopt in
      BytecodeGraphBuilder for ForIn (which will be done in a followup CL).
      
      MIPS port contributed by Balazs Kilvady <balazs.kilvady@imgtec.com>.
      
      BUG=v8:4280
      LOG=N
      
      Review URL: https://codereview.chromium.org/1576093004
      
      Cr-Commit-Position: refs/heads/master@{#33334}
      84f8a506
  10. 26 Nov, 2015 1 commit
  11. 25 Nov, 2015 1 commit
  12. 23 Nov, 2015 1 commit
  13. 23 Sep, 2015 1 commit
    • bmeurer's avatar
      [builtin] Refactor Invoke to deal with any kind of callable. · 634d1d86
      bmeurer authored
      Now both Execution::Call and Execution::New can deal with any
      kind of target and will raise a proper exception if the target is not
      callable (which is not yet spec compliant for New, as we would
      have to check IsConstructor instead, which we don't have yet).
      
      Now we no longer need to do any of these weird call/construct
      delegate gymnastics in C++, and we finally have a single true
      bottleneck for Call/Construct abstract operations in the code
      base, with only a few special handlings left in the compilers to
      optimize the JSFunction case.
      
      R=jarin@chromium.org
      BUG=v8:4430, v8:4413
      LOG=n
      
      Review URL: https://codereview.chromium.org/1360793002
      
      Cr-Commit-Position: refs/heads/master@{#30874}
      634d1d86
  14. 22 Sep, 2015 1 commit
    • bmeurer's avatar
      [builtins] Add support for NewTarget to Execution::New. · 1dfac69f
      bmeurer authored
      Introduce new builtins Construct and ConstructFunction (in line
      with the Call and CallFunction builtins that we already have) as
      proper bottleneck for Construct and [[Construct]] on JSFunctions.
      Use these builtins to support passing NewTarget from C++ to
      JavaScript land.
      
      Long-term we want the CallConstructStub to be used for
      gathering feedback on entry to construction chain (i.e. the
      initial new Foo), and use the Construct builtins to do the
      actual work inside the construction chain (i.e. calling into
      super and stuff).
      
      MIPS and MIPS64 ports contributed by akos.palfi@imgtec.com.
      
      R=jarin@chromium.org
      BUG=v8:4430
      LOG=n
      
      Review URL: https://codereview.chromium.org/1359583002
      
      Cr-Commit-Position: refs/heads/master@{#30857}
      1dfac69f
  15. 24 Aug, 2015 1 commit
  16. 17 Aug, 2015 1 commit
  17. 12 Aug, 2015 1 commit
    • jfb's avatar
      Security: disable nontemporals. · a904b569
      jfb authored
      The operations were available on ARM64 and x86-32 but were unused.
      
      It has been conjectured that nontemporals can be used for rowhammer-like bitflips more easily than regular load/store operations. It is therefore desirable to avoid generating these instructions in the future.
      
      R= titzer, jochen, jln, Mark Seaborn, ruiq
      
      Review URL: https://codereview.chromium.org/1276113002
      
      Cr-Commit-Position: refs/heads/master@{#30139}
      a904b569
  18. 17 Jun, 2015 1 commit
  19. 01 Jun, 2015 1 commit
  20. 20 May, 2015 1 commit
    • svenpanne's avatar
      Fixed various simulator-related space leaks. · 84aa494e
      svenpanne authored
      Alas, this involved quite a bit of copy-n-paste between the
      architectures, but this is caused by the very convoluted
      relationships, lifetimes and distribution of responsibilities. This
      should really be cleaned up by moving code around and using STL maps,
      but that's not really a priority right now.
      
      Bonus: Fixed leaks in the ARM64 disassembler tests.
      
      Review URL: https://codereview.chromium.org/1132943007
      
      Cr-Commit-Position: refs/heads/master@{#28496}
      84aa494e
  21. 15 May, 2015 1 commit
  22. 20 Jan, 2015 1 commit
  23. 08 Dec, 2014 1 commit
  24. 22 Oct, 2014 1 commit
  25. 22 Sep, 2014 1 commit
  26. 09 Sep, 2014 1 commit
    • Jacob.Bramley@arm.com's avatar
      Reland r23732: ARM64: Fix and improve --trace-sim register trace. · 3dbb3c39
      Jacob.Bramley@arm.com authored
      - Use standard names (except that our GREY is the standard BLACK).
      - Make non-bold colours explicit, otherwise the boldness can carry over
        into subsequent colour declarations.
      - I've moved some colours around to make them consistent. Register value
        updates (which are very common) now stand out less than they did,
        making the less-common (and arguably more important) debug
        announcements appear brighter.
        - FP registers and values are now magenta.
        - Integer registers and values are now cyan.
        - Memory accesses are now blue.
      - LOG_WRITE prints the source register for stores.
      - Loads are logged with a format similar to that used for stores.
        Specifically, the memory address is printed alongside the new register
        value.
      - Updates to D registers print the raw bits as well as the double value.
        Updates to S registers print the raw bits as well as the float value.
        (Previously, we printed both double and float interpretations of the
        bits, which was a bit cluttered.)
      
      BUG=
      R=svenpanne@chromium.org
      
      Review URL: https://codereview.chromium.org/551823004
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23802 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      3dbb3c39
  27. 08 Sep, 2014 1 commit
  28. 05 Sep, 2014 1 commit
    • Jacob.Bramley@arm.com's avatar
      ARM64: Fix and improve --trace-sim register trace. · d0054c75
      Jacob.Bramley@arm.com authored
      - Use standard names (except that our GREY is the standard BLACK).
      - Make non-bold colours explicit, otherwise the boldness can carry over
        into subsequent colour declarations.
      - I've moved some colours around to make them consistent. Register value
        updates (which are very common) now stand out less than they did,
        making the less-common (and arguably more important) debug
        announcements appear brighter.
        - FP registers and values are now magenta.
        - Integer registers and values are now cyan.
        - Memory accesses are now blue.
      - LOG_WRITE prints the source register for stores.
      - Loads are logged with a format similar to that used for stores.
        Specifically, the memory address is printed alongside the new register
        value.
      - Updates to D registers print the raw bits as well as the double value.
        Updates to S registers print the raw bits as well as the float value.
        (Previously, we printed both double and float interpretations of the
        bits, which was a bit cluttered.)
      
      BUG=
      R=ulan@chromium.org
      
      Review URL: https://codereview.chromium.org/548473002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23732 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      d0054c75
  29. 03 Sep, 2014 1 commit
  30. 26 Aug, 2014 1 commit
  31. 20 Aug, 2014 1 commit
    • wingo@igalia.com's avatar
      Support symbol-named properties in API · e929f5fe
      wingo@igalia.com authored
      Add new "Name" type to API that is a supertype of Symbol and String.
      
      Object::SetDeclaredAccessor, Object::SetAccessorProperty, Template::Set,
      Template::SetAccessorProperty, and Template::SetDeclaredAccessor now
      take a Name as the property name instead of a String.
      
      Add Object::SetAccessor, Template::SetNativeDataProperty, and
      ObjectTemplate::SetAccessor overloads that can define accessors for
      symbol-named properties.
      
      R=dcarney@chromium.org, rossberg@chromium.org
      BUG=v8:3394
      TEST=cctest/test-api/TestSymbolProperties
      LOG=Y
      
      Review URL: https://codereview.chromium.org/459413002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23247 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e929f5fe
  32. 04 Aug, 2014 2 commits
  33. 30 Jul, 2014 1 commit
  34. 07 Jul, 2014 1 commit
  35. 30 Jun, 2014 1 commit
  36. 20 Jun, 2014 1 commit
  37. 12 Jun, 2014 1 commit
  38. 03 Jun, 2014 1 commit
  39. 23 May, 2014 1 commit