1. 15 Feb, 2011 1 commit
  2. 12 Jan, 2011 1 commit
  3. 25 Oct, 2010 1 commit
  4. 19 Oct, 2010 3 commits
  5. 07 Sep, 2010 1 commit
  6. 30 Aug, 2010 1 commit
  7. 13 Jul, 2010 1 commit
  8. 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
  9. 06 May, 2010 1 commit
  10. 19 Apr, 2010 1 commit
  11. 14 Apr, 2010 1 commit
  12. 09 Apr, 2010 1 commit
  13. 06 Apr, 2010 1 commit
  14. 19 Mar, 2010 1 commit
  15. 25 Feb, 2010 1 commit
  16. 26 Jan, 2010 1 commit
    • sgjesse@chromium.org's avatar
      Don't pass the "at start" parameter to native RegExp · cf78ed05
      sgjesse@chromium.org authored
      As the start index is already passed it is easy to calculate the "at start" boolean in generated code. Also as direct entry has been implemented this needs to be done in generated code anyway, and therefore might as well be moved to the generated code for RegExp. The "at start" value is now calcualted as a local variable on the native RegExp frame based on the value of the start index argument.
      
      The x64 version have been tested on both Linux and 64-bit Windows Vista.
      
      For ARM I have tested cctest/test-regexp on ARM hardware, but the rest of the tests have only been run on the ARM simulator.
      Review URL: http://codereview.chromium.org/554078
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3709 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      cf78ed05
  17. 18 Jan, 2010 1 commit
  18. 07 Jan, 2010 1 commit
  19. 06 Jan, 2010 1 commit
    • sgjesse@chromium.org's avatar
      Direct call to native RegExp code from JavaScript. · 429f3cf9
      sgjesse@chromium.org authored
      Calls to RegExp no longer have to be via a call to the runtime system. A new stub have been added which can handle this call in generated code. The stub checks all the parameters and creates RegExp entry frame in the same way as it is created by the runtime system. Bailout to the runtime system is done whenever an uncommon situation is encountered or when the static data used is not initialized. After running the native RegExp code the last match info is updated like in the runtime system.
      
      Currently only ASCII strings are handled.
      
      Added another argument to the RegExp entry frame. It indicated whether the call is direct from JavaScript code or through the runtime system. This information is used when RegExp execution is interrupted. If an interruption happens when RegExp code is called directly a retry is issued causing the interruption to be handled via the runtime system. The reason for this is that the direct call to RegExp code does not support garbage collection.
      Review URL: http://codereview.chromium.org/521028
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3542 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      429f3cf9
  20. 05 Nov, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Fix issue 493: Infinite loop when debug break is set when entering function.apply. · 41d6cae4
      sgjesse@chromium.org authored
      In the generated code for function.apply there was a loop checking the stack limit for interruption. This loop would call into the runtime system to handle interuption and keep running until there was no interruption. However if the interuption was debug break the runtime system would never clear the interruption as debug break is prevented in builtins are prevented and the assumption here was that returning with the debug break flag set would move execution forward.
      
      Renamed initial_jslimit and initial_climit to real_jslimit and real_climit. Renamed a few external references related to the stack limit as well.
      
      Exposed the real stack limit to generated code to make the stack check when entering function.apply use the real stack limit and not the stack limit which is changed to signal interruption.
      
      Added the real stack limit to the roots array.
      
      BUG=http://code.google.com/p/v8/issues/detail?id=493
      TEST=cctest/test-debug/DebugBreakFunctionApply
      Review URL: http://codereview.chromium.org/345048
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3229 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      41d6cae4
  21. 27 Oct, 2009 1 commit
  22. 26 Oct, 2009 1 commit
  23. 02 Sep, 2009 2 commits
  24. 31 Aug, 2009 1 commit
  25. 25 May, 2009 1 commit
  26. 23 Apr, 2009 1 commit
  27. 26 Nov, 2008 1 commit
  28. 09 Sep, 2008 1 commit
  29. 25 Jul, 2008 1 commit
    • kasper.lund's avatar
      Fixed bug in JSObject::GetPropertyAttributePostInterceptor where map... · 44510671
      kasper.lund authored
      Fixed bug in JSObject::GetPropertyAttributePostInterceptor where map transitions would count as properties.
      
      Allowed aliased eval invocations by treating them as evals in the global context. This may change in the future.
      
      Added support for accessing the last entered context through the API and renamed Context::Current to Context::GetCurrent and Context::GetSecurityContext to Context::GetCurrentSecurityContext.
      
      Fixed bug in the debugger that would cause the debugger scripts to be recursively loaded and changed all disabling of interrupts to be block-structured.
      
      Made snapshot data read-only to allow it to be more easily shared across multiple users of V8 when linked as a shared library.
      
      
      git-svn-id: http://v8.googlecode.com/svn/trunk@6 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      44510671
  30. 03 Jul, 2008 1 commit