1. 14 Jun, 2012 1 commit
  2. 12 Jun, 2012 2 commits
  3. 11 Jun, 2012 1 commit
  4. 24 Apr, 2012 1 commit
  5. 23 Apr, 2012 2 commits
  6. 05 Apr, 2012 1 commit
  7. 19 Mar, 2012 1 commit
  8. 12 Mar, 2012 1 commit
  9. 28 Feb, 2012 1 commit
  10. 27 Feb, 2012 1 commit
  11. 09 Feb, 2012 1 commit
  12. 24 Jan, 2012 1 commit
  13. 13 Jan, 2012 1 commit
  14. 10 Jan, 2012 1 commit
  15. 05 Dec, 2011 1 commit
  16. 03 Nov, 2011 1 commit
  17. 20 Oct, 2011 1 commit
  18. 03 Oct, 2011 1 commit
  19. 20 Sep, 2011 2 commits
  20. 19 Sep, 2011 1 commit
  21. 20 Jul, 2011 1 commit
    • whesse@chromium.org's avatar
      fix -Wunused-but-set-variable for gcc-4.6 on x64 · 47e03a00
      whesse@chromium.org authored
      * src/third_party/valgrind/valgrind.h: Update from upstream valgrind
        r11899, so as to get around some unused value warnings.  Also adds
        support for darwin.
      
        This version of valgrind.h differs from the original in that all
        instances of "unsigned long long int" have been replaced with
        "uint64_t", as the former is not allowed in ISO C++ 89.
      
        See https://bugs.kde.org/show_bug.cgi?id=211926 for the upstream bug
        report.
      
      * src/x64/cpu-x64.cc:
      * src/builtins.cc:
      * src/conversions-inl.h:
      * src/debug.cc:
      * src/frames.cc:
      * src/full-codegen.cc:
      * src/jsregexp.cc:
      * src/objects.cc:
      * src/parser.cc:
      * src/platform-linux.cc:
      * src/x64/code-stubs-x64.cc:
      * src/x64/deoptimizer-x64.cc:
      * src/x64/full-codegen-x64.cc:
      * src/x64/lithium-codegen-x64.cc:
      * src/x64/regexp-macro-assembler-x64.cc:
      * src/x64/stub-cache-x64.cc: Remove a number of assigned but
        unreferenced variables.
      
      * SConstruct (CCTEST_EXTRA_FLAGS): Punt on -Wunused-but-set-variable for
        the test suite.
      
      BUG=1291
      TEST=A build and tools/test.py passes.
      
      Review URL: http://codereview.chromium.org/7400023
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8688 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      47e03a00
  22. 13 Jul, 2011 1 commit
  23. 12 Jul, 2011 1 commit
  24. 29 Jun, 2011 1 commit
    • sgjesse@chromium.org's avatar
      Support debugger inspection of locals in optimized frames · 7d2be7c0
      sgjesse@chromium.org authored
      Optimized frames are now handled by the debugger. When discovering optimized frames during stack inspection in the debugger they are "deoptimized" using the normal deoptimization code and the deoptimizer output information is used to provide frame information to the debugger.
      
      Before this change the debugger reported each optimized frame as one frame no matter the number of inlined functuions that might have been called inside of it. Also all locals where reported as undefined. Locals can still be reposted as undefined when their value is not "known" by the optimized frame.
      
      As the structures used to calculate the output frames when deoptimizing are not GC safe the information for the debugger is copied to another structure (DeoptimizedFrameInfo) which is registered with the global deoptimizer data and processed during GC.
      
      R=fschneider@chromium.org
      
      BUG=v8:1140
      TEST=test/mjsunit/debug-evaluate-locals-optimized*
      
      Review URL: http://codereview.chromium.org//7230045
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8464 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7d2be7c0
  25. 24 May, 2011 1 commit
    • ager@chromium.org's avatar
      Fix calls of strict mode function with an implicit receiver. · 6f775f2f
      ager@chromium.org authored
      Only IA32 version for now. I'll start porting.
      
      Strict mode functions are to get 'undefined' as the receiver when
      called with an implicit receiver. Modes are bad! It forces us to have
      checks on all function calls.
      
      This change attempts to limit the cost by passing information about
      whether or not a call is with an implicit or explicit receiver in ecx
      as part of the calling convention. The cost is setting ecx on all
      calls and checking ecx on entry to strict mode functions.
      
      Implicit/explicit receiver state has to be maintained by ICs. Various
      stubs have to not clobber ecx or save and restore it.
      
      CallFunction stub needs to check if the receiver is implicit when it
      doesn't know from the context.
      
      Review URL: http://codereview.chromium.org/7039036
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8040 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      6f775f2f
  26. 26 Apr, 2011 1 commit
  27. 06 Apr, 2011 1 commit
  28. 05 Apr, 2011 3 commits
  29. 01 Apr, 2011 3 commits
  30. 23 Mar, 2011 2 commits
  31. 18 Mar, 2011 2 commits