1. 28 Aug, 2013 1 commit
  2. 05 Jul, 2013 1 commit
  3. 03 Jul, 2013 1 commit
  4. 28 Jun, 2013 1 commit
  5. 07 Jun, 2013 1 commit
  6. 06 Jun, 2013 1 commit
  7. 24 Apr, 2013 1 commit
  8. 13 Mar, 2013 1 commit
  9. 11 Mar, 2013 1 commit
  10. 09 Jan, 2013 2 commits
  11. 21 Nov, 2012 1 commit
  12. 14 Jun, 2012 1 commit
  13. 11 Jun, 2012 1 commit
  14. 06 Jun, 2012 1 commit
  15. 04 Jun, 2012 1 commit
  16. 22 May, 2012 2 commits
  17. 02 Apr, 2012 1 commit
    • erikcorry's avatar
      Regexp: Improve the speed that we scan for an initial point where a non-anchored · f14b93a5
      erikcorry authored
      regexp can match by using a Boyer-Moore-like table.  This is done by identifying
      non-greedy non-capturing loops in the nodes that eat any character one at a time.
      For example in the middle of the regexp /foo[\s\S]*?bar/ we find such a loop.
      There is also such a loop implicitly inserted at the start of any non-anchored
      regexp.
      
      When we have found such a loop we look ahead in the nodes to find the set of
      characters that can come at given distances.  For example for the regexp
      /.?foo/ we know that there are at least 3 characters ahead of us, and the sets
      of characters that can occur are [any, [f, o], [o]].  We find a range in the
      lookahead info where the set of characters is reasonably constrained.  In our
      example this is from index 1 to 2 (0 is not constrained).  We can now look 3
      characters ahead and if we don't find one of [f, o] (the union of [f, o] and
      [o]) then we can skip forwards by the range size (in this case 2).
      
      For Unicode input strings we do the same, but modulo 128.
      
      We also look at the first string fed to the regexp and use that to get a hint
      of the character frequencies in the inputs.  This affects the assessment of
      whether the set of characters is 'reasonably constrained'.
      
      We still have the old lookahead mechanism, which uses a wide load of multiple
      characters followed by a mask and compare to determine whether a match is
      possible at this point.
      Review URL: http://codereview.chromium.org/9965010
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11204 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      f14b93a5
  18. 30 Mar, 2012 1 commit
  19. 12 Mar, 2012 1 commit
  20. 06 Mar, 2012 1 commit
  21. 05 Mar, 2012 1 commit
  22. 28 Feb, 2012 1 commit
  23. 16 Jan, 2012 1 commit
  24. 19 Oct, 2011 1 commit
  25. 03 Oct, 2011 1 commit
  26. 15 Sep, 2011 1 commit
  27. 29 Aug, 2011 1 commit
  28. 26 Aug, 2011 1 commit
  29. 31 May, 2011 2 commits
  30. 11 May, 2011 2 commits
  31. 10 May, 2011 1 commit
  32. 01 Apr, 2011 1 commit
  33. 30 Mar, 2011 1 commit
  34. 22 Mar, 2011 1 commit
  35. 18 Mar, 2011 2 commits