1. 14 May, 2016 1 commit
  2. 25 Apr, 2016 1 commit
  3. 12 Apr, 2016 1 commit
  4. 11 Apr, 2016 2 commits
  5. 08 Apr, 2016 2 commits
    • jfb's avatar
      Revert of Fix printf formats (patchset #8 id:140001 of... · 4c4fdc2d
      jfb authored
      Revert of Fix printf formats (patchset #8 id:140001 of https://codereview.chromium.org/1869433004/ )
      
      Reason for revert:
      One small issue easily fixed here: https://codereview.chromium.org/1867333003/
      
      But it looks like MSVS 2013 doesn't like some of the formats and exists with the unhelpful:
      Stderr:
      f:\dd\vctools\crt\crtw32\stdio\output.c(1125) : Assertion failed: ("Incorrect
      format specifier", 0)
      
      It's easier to revert for now, I'll dig more into the docs:
      https://msdn.microsoft.com/en-us/library/56e442dc(v=vs.120).aspx
      https://msdn.microsoft.com/en-us/library/tcxf1dw6(v=vs.120).aspx
      
      And then resubmit, making sure I run these bots.
      
      Original issue's description:
      > Fix printf formats
      >
      > The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL:
      >
      >  - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h.
      >  - Uses it appropriately.
      >  - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done).
      >  - Fixes a bunch of incorrect formats.
      >
      > R= jochen@chromium.org, bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org
      >
      > Committed: https://crrev.com/6ebf9fbb93d31f9be41156a3325d58704ed4933d
      > Cr-Commit-Position: refs/heads/master@{#35365}
      
      TBR=jochen@chromium.org,bmeurer@chromium.org,yangguo@chromium.org,ahaas@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1867383002
      
      Cr-Commit-Position: refs/heads/master@{#35366}
      4c4fdc2d
    • jfb's avatar
      Fix printf formats · 6ebf9fbb
      jfb authored
      The usage of __attribute__((format(x, y)) was either wrong or missing from multiple functions, leading to erroneous formats. This CL:
      
       - Imports PRINTF_FORMAT macro from Chrome's src/base/compiler-specific.h.
       - Uses it appropriately.
       - Imports Chrome's base/format_macros.h mainly to fix size_t formats (further cleanup could be done).
       - Fixes a bunch of incorrect formats.
      
      R= jochen@chromium.org, bmeurer@chromium.org, yangguo@chromium.org, ahaas@chromium.org
      
      Review URL: https://codereview.chromium.org/1869433004
      
      Cr-Commit-Position: refs/heads/master@{#35365}
      6ebf9fbb
  6. 10 Mar, 2016 1 commit
    • joransiu's avatar
      S390: Platform specific includes in common files · daea0e75
      joransiu authored
      Add S390 platform specific \#includes across various common files.
      Add S390 CPU features to enum.
      Add S390 implementation to extract sp/fp/pc from signal context.
      
      R=danno@chromium.org,jkummerow@chromium.org,jochen@chromium.org,jyan@ca.ibm.com,michael_dawson@ca.ibm.com,mbrandy@us.ibm.com
      BUG=
      
      Review URL: https://codereview.chromium.org/1777593003
      
      Cr-Commit-Position: refs/heads/master@{#34674}
      daea0e75
  7. 01 Mar, 2016 1 commit
  8. 26 Feb, 2016 1 commit
  9. 05 Feb, 2016 1 commit
  10. 02 Feb, 2016 1 commit
  11. 08 Jan, 2016 1 commit
  12. 01 Dec, 2015 1 commit
  13. 26 Nov, 2015 1 commit
  14. 05 Nov, 2015 1 commit
  15. 20 Oct, 2015 1 commit
    • mstarzinger's avatar
      [turbofan] Fix bailout for script context creation. · 62e04d33
      mstarzinger authored
      This fixes the bailout point used by JSCreateScriptContext nodes for
      top-level code. The bailout point differs from the Crankshaft one as
      parameter slots have not been copied and the context chain was not
      extended yet in TurboFan. Hence a new bailout id is required.
      
      R=ishell@chromium.org
      TEST=cctest/test-decls/CrossScript --turbo-inlining
      
      Review URL: https://codereview.chromium.org/1413933005
      
      Cr-Commit-Position: refs/heads/master@{#31399}
      62e04d33
  16. 01 Oct, 2015 1 commit
  17. 01 Sep, 2015 1 commit
  18. 28 Aug, 2015 1 commit
  19. 03 Aug, 2015 1 commit
    • bbudge's avatar
      SIMD.js Add the other SIMD Phase 1 types. · 7b9670b6
      bbudge authored
      Adds Int32x4, Bool32x4, Int16x8, Bool16x8, Int8x16, Bool8x16.
      Adds Simd128Value base heap object class.
      Changes heap/factory construction pattern to use arrays.
      Adds replaceLane functions to facilitate testing.
      
      NOPRESUBMIT=true
      (presubmit checks erroneously interpret array declaration in macro definition as variable size array.)
      
      LOG=Y
      BUG=v8:4124
      
      Review URL: https://codereview.chromium.org/1250733005
      
      Cr-Commit-Position: refs/heads/master@{#29974}
      7b9670b6
  20. 14 Jul, 2015 1 commit
  21. 22 Jun, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Revive the VectorSlotPair and also put feedback on JSCallFunction. · d4f70f8c
      bmeurer authored
      We resurrect the VectorSlotPair in order to be able to separate the
      feedback input for the compiler from the actual type feedback vector
      that is required to meet the IC requirements at runtime. This will allow
      us to for example use feedback from a different context or divide the
      type feedback vector into two separate vectors, without having to touch
      the compiler. It'll allow use to load the vector from the shared
      function info at runtime, while still consuming feedback in the
      compiler (i.e. we don't rely on the feedback vector node to be a heap
      constant).
      
      R=mvstanton@chromium.org
      
      Review URL: https://codereview.chromium.org/1198983002
      
      Cr-Commit-Position: refs/heads/master@{#29185}
      d4f70f8c
  22. 18 Jun, 2015 1 commit
  23. 02 Jun, 2015 1 commit
  24. 26 May, 2015 1 commit
    • erikcorry's avatar
      Move hash code from hidden string to a private symbol · eca5b5d7
      erikcorry authored
      * Hash code is now just done with a private own symbol instead of the hidden string, which predates symbols.
      * In the long run we should do all hidden properties this way and get rid of the
      hidden magic 0-length string with the zero hash code.  The advantages include
      less complexity and being able to do things from JS in a natural way.
      * Initially, the performance of weak set regressed, because it's a little harder
      to do the lookup in C++.  Instead of heroics in C++ to make things faster I
      moved some functionality into JS and got the performance back. JS is supposed to be good at looking up named properties on objects.
      * This also changes hash codes of Smis so that they are always Smis.
      
      Performance figures are in the comments to the code review.  Summary: Most of js-perf-test/Collections is neutral.  Set and Map with object keys are 40-50% better.  WeakMap is -5% and WeakSet is +9%.  After the measurements, I fixed global proxies, which cost 1% on most tests and 5% on the weak ones :-(.
      
      In the code review comments is a patch with an example of the heroics we could do in C++ to make lookup faster (I hope we don't have to do this.  Instead of checking for the property, then doing a new lookup to insert it, we could do one lookup and handle the addition immediately).  With the current benchmarks above this buys us nothing, but if we go back to doing more lookups in C++ instead of in stubs and JS then it's a win.
      
      In a similar vein we could give the magic zero hash code to the hash code
      symbol.  Then when we look up the hash code we would sometimes see the table
      with all the hidden properties.  This dual use of the field for either the hash
      code or the table with all hidden properties and the hash code is rather ugly,
      and this CL gets rid of it.  I'd be loath to bring it back.  On the benchmarks quoted above it's slightly slower than moving the hash code lookup to JS like in this CL.
      
      One worry is that the benchmark results above are more monomorphic than real
      world code, so may be overstating the performance benefits of moving to JS.  I
      think this is part of a general issue we have with handling polymorphic code in
      JS and any solutions there will benefit this solution, which boils down to
      regular property access. Any improvement there will lift all boats.
      
      R=adamk@chromium.org, verwaest@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/1149863005
      
      Cr-Commit-Position: refs/heads/master@{#28622}
      eca5b5d7
  25. 29 Apr, 2015 1 commit
  26. 21 Apr, 2015 1 commit
  27. 20 Apr, 2015 1 commit
  28. 10 Apr, 2015 1 commit
  29. 07 Apr, 2015 1 commit
  30. 24 Feb, 2015 1 commit
  31. 11 Feb, 2015 1 commit
  32. 05 Feb, 2015 1 commit
  33. 16 Jan, 2015 1 commit
  34. 13 Jan, 2015 1 commit
  35. 18 Dec, 2014 1 commit
  36. 05 Nov, 2014 1 commit
  37. 27 Oct, 2014 1 commit
  38. 20 Oct, 2014 1 commit