1. 11 May, 2011 1 commit
  2. 18 Mar, 2011 3 commits
  3. 15 Feb, 2011 1 commit
  4. 12 Jan, 2011 1 commit
  5. 19 Oct, 2010 3 commits
  6. 30 Aug, 2010 1 commit
  7. 19 Apr, 2010 1 commit
  8. 09 Apr, 2010 1 commit
  9. 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
  10. 07 Jan, 2010 1 commit
  11. 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
  12. 26 Oct, 2009 1 commit
  13. 02 Sep, 2009 1 commit
  14. 31 Aug, 2009 1 commit
  15. 25 May, 2009 1 commit
  16. 04 May, 2009 1 commit
  17. 23 Apr, 2009 1 commit
  18. 26 Nov, 2008 1 commit
  19. 09 Sep, 2008 1 commit
  20. 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
  21. 03 Jul, 2008 1 commit