1. 13 Dec, 2019 1 commit
  2. 07 May, 2019 1 commit
    • Mythri A's avatar
      Reland [ic] Remove the check for fast prototypes in LoadIC_Uninitialized · 9fe37d23
      Mythri A authored
      This is a reland of d14ed12e
      with fix for test failures in lite mode.
      
      When handling load named properties (without feedback vectors) we used
      to miss to runtimes if the prototypes aren't set. This was because we
      wanted to give the prototype a chance to become fast, since most prototypes
      start in slow mode but move to fast after the initial setup. Though this
      check is not really useful when we don't have feedback vectors, and once
      feedback vectors are allocated we will turn the prototypes fast anyway.
      
      Bug: v8:8394, v8:8860
      Change-Id: I5c7b5061e1d9068c72d6f0eea47517880940a054
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1591772Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Mythri Alle <mythria@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61267}
      9fe37d23
  3. 27 Feb, 2017 1 commit
  4. 22 Nov, 2016 1 commit
  5. 08 Jun, 2016 1 commit
    • jkummerow's avatar
      Keep prototype maps in dictionary mode until ICs see them · be0494ba
      jkummerow authored
      Adding properties to prototypes is faster when we don't force their
      maps into fast mode yet. Once a prototype shows up in the IC system,
      its setup phase is likely over, and it makes sense to transition it
      to fast properties.
      This patch speeds up the microbenchmark in the bug by 20x.
      Octane-Typescript sees a 3% improvement.
      
      BUG=chromium:607010
      
      Review-Url: https://codereview.chromium.org/2036493006
      Cr-Commit-Position: refs/heads/master@{#36828}
      be0494ba
  6. 26 Nov, 2015 1 commit
  7. 07 Apr, 2015 1 commit
  8. 22 Oct, 2014 1 commit
  9. 07 Aug, 2014 1 commit
  10. 04 Aug, 2014 1 commit
  11. 21 Jan, 2014 1 commit
  12. 07 Nov, 2013 1 commit
  13. 19 Sep, 2013 1 commit
  14. 11 Dec, 2012 1 commit
  15. 15 Jun, 2012 1 commit
  16. 06 Jun, 2012 1 commit
  17. 31 May, 2012 1 commit
  18. 30 May, 2012 1 commit
  19. 24 Jan, 2012 1 commit
  20. 07 Dec, 2010 1 commit
  21. 17 May, 2010 1 commit
    • mark@chromium.org's avatar
      Allow build-time selection between ia32 and x86_64 in the GYP/Xcode Mac · e9b5d785
      mark@chromium.org authored
      Chromium build.
      
      v8.gyp no longer sets any V8_TARGET_ARCH_* macro on the Mac. Instead, the
      proper V8_TARGET_ARCH_* macro will be set by src/globals.h in the same way as
      the V8_HOST_ARCH_* macro when it detects that no target macro is currently
      defined. The Mac build will attempt to compile all ia32 and x86_64 .cc files.
      #ifdef guards in each of these target-specific source files prevent their
      compilation when the associated target is not selected. For completeness,
      these #ifdef guards are also provided for the arm and mips .cc files.
      
      BUG=706
      TEST=x86_64 Mac GYP/Xcode-based Chromium build (still depends on other changes)
      Review URL: http://codereview.chromium.org/2133003
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4666 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e9b5d785
  22. 01 Mar, 2010 1 commit
  23. 04 Feb, 2010 1 commit
  24. 21 Dec, 2009 1 commit
  25. 27 Aug, 2009 2 commits
  26. 15 Jun, 2009 1 commit
  27. 05 Jun, 2009 1 commit
    • kmillikin@chromium.org's avatar
      Simplify the processing of deferred code in the code generator. Our · bd82b972
      kmillikin@chromium.org authored
      deferred code snippets are highly stylized.  They always make a call
      to a stub or the runtime and then return.  This change takes advantage
      of that.
      
      Creating a deferred code object now captures a snapshot of the
      registers in the virtual frame.  The registers are automatically saved
      on entry to the deferred code and restored on exit.
      
      The clients of deferred code must ensure that there is no change to
      the registers in the virtual frame (eg, by allocating which can cause
      spilling) or to the stack pointer.  That is currently the case.
      
      As a separate change, I will add either code to verify this constraint
      or else code to forbid any frame effect.
      
      The deferred code itself does not use the virtual frame or register
      allocator (or even the code generator).  It is raw macro assembler
      code.
      Review URL: http://codereview.chromium.org/118226
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2112 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      bd82b972
  28. 27 May, 2009 1 commit
  29. 31 Mar, 2009 3 commits
  30. 27 Mar, 2009 1 commit
  31. 16 Jan, 2009 1 commit
  32. 14 Jan, 2009 1 commit
  33. 26 Sep, 2008 1 commit
  34. 09 Sep, 2008 1 commit
  35. 22 Aug, 2008 1 commit
    • christian.plesner.hansen's avatar
      Included mjsunit JavaScript test suite and C++ unit tests. · c42f5829
      christian.plesner.hansen authored
      In the shell sample don't print the result of executing a script, only
      evaluating expressions.
      
      Fixed issue when building samples on Windows using a shared V8
      library.  Added visibility option on Linux build which makes the
      generated library 18% smaller.
      
      Changed build system to accept multiple build modes in one build and
      generate seperate objects, libraries and executables for each mode.
      
      Removed deferred negation optimization (a * -b => -(a * b)) since this
      visibly changes operand conversion order.
      
      Improved parsing performance by introducing stack guard in preparsing.
      Without a stack guard preparsing always bails out with stack overflow.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c42f5829
  36. 03 Jul, 2008 1 commit