1. 16 May, 2016 2 commits
  2. 13 May, 2016 1 commit
  3. 12 May, 2016 1 commit
  4. 03 May, 2016 1 commit
  5. 28 Apr, 2016 1 commit
  6. 21 Mar, 2016 2 commits
    • caitpotter88's avatar
      [parser] implement error reporting for Scanner · e6f4b749
      caitpotter88 authored
      Enables the Scanner to provide a better error message when errors occur
      in escape sequences, numbers, strings, etc.
      
      BUG=v8:4829, v8:3230
      LOG=N
      R=adamk@chromium.org, littledan@chromium.org
      
      Review URL: https://codereview.chromium.org/1793913002
      
      Cr-Commit-Position: refs/heads/master@{#34966}
      e6f4b749
    • vogelheim's avatar
      Revert of Parser: Make skipping HTML comments optional. (patchset #6 id:140001... · 09ac4f29
      vogelheim authored
      Revert of Parser: Make skipping HTML comments optional. (patchset #6 id:140001 of https://codereview.chromium.org/1801203002/ )
      
      Reason for revert:
      Violates ES6 spec (crbug.com/4850), and implementation was over-eager. Will revert for now.
      
      Original issue's description:
      > Parser: Make skipping HTML comments optional.
      >
      > API change: This adds a new flag skip_html_comments to v8::ScriptOriginOptions. This flag controls whether V8 will attempt to honour HTML-style comments in JS sources.
      >
      > (That is: Gracefully ignore <!-- ... ---> in JS sources, which was a popular technique in the early days of JavaScript, to prevent non-JS-enabled browsers from displaying script sources to uses.)
      >
      > The flag defaults to 'true' when using v8::ScriptOrigin constructor, which preserves the existing behaviour. Embedders which are happy with the existing behaviour will thus not need any changes.
      >
      > BUG=chromium:573887
      > LOG=Y
      >
      > Committed: https://crrev.com/91d344288aa51ed03eaaa1cb3e368ac1e82f0173
      > Cr-Commit-Position: refs/heads/master@{#34904}
      
      TBR=jochen@chromium.org,rossberg@chromium.org
      # Not skipping CQ checks because original CL landed more than 1 days ago.
      BUG=chromium:573887, v8:4850
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1817163003
      
      Cr-Commit-Position: refs/heads/master@{#34958}
      09ac4f29
  7. 18 Mar, 2016 2 commits
  8. 01 Mar, 2016 1 commit
  9. 27 Jan, 2016 1 commit
  10. 08 Jan, 2016 1 commit
  11. 26 Nov, 2015 1 commit
  12. 25 Nov, 2015 1 commit
    • bmeurer's avatar
      [es6] Correct parsing of regular expression literal flags. · 2732a6ad
      bmeurer authored
      ES6 section 12.2.8.1 states that flags for regular expression literals
      must be checked during parsing and invalid flags are early errors. This
      change adapts the Scanner and (Pre)Parser to act according to the spec.
      
      This is also a prerequisite to unify the handling of literal creation
      (for Objects, Arrays, Regexps, and at some point Classes).
      
      R=yangguo@chromium.org
      
      Review URL: https://codereview.chromium.org/1472323002
      
      Cr-Commit-Position: refs/heads/master@{#32273}
      2732a6ad
  13. 17 Nov, 2015 1 commit
  14. 21 Oct, 2015 1 commit
    • vogelheim's avatar
      Always dispose backing store. · 7770e021
      vogelheim authored
      (With a v8::Vector, the client is responsible for memory management.
       I think there can be a situation where the Vector has a char[1] backing
       store with '\0' in it, in which case the current code would leak.
       If we always Dispose() the backing store this should be avoided.
       Since dispose will delete[] the actual backing store, this should
       also work then the backing store is nullptr.)
      
      R=jochen@chromium.org
      BUG=chromium:525885
      LOG=N
      
      Review URL: https://codereview.chromium.org/1410543005
      
      Cr-Commit-Position: refs/heads/master@{#31446}
      7770e021
  15. 30 Sep, 2015 1 commit
  16. 28 Aug, 2015 1 commit
    • littledan's avatar
      Sloppy-mode let parsing · decc7b09
      littledan authored
      This patch makes 'let' a contextual keyword in both strict and sloppy mode.
      It behaves as a keyword when used at the beginning of a StatementListItem
      or lexical declaration at the beginning of a for statement, if it is followed
      by an identifier, [ or {. Implementing this change requires an extra token
      look-ahead by the parser which is only invoked in certain cases (so as to
      avoid parsing RegExps as ECMAScript tokens). This might result in a slowdown
      of the scanner, but performance testing of this patch hasn't yet found much
      of a regression.
      
      BUG=v8:3305
      LOG=Y
      R=adamk,vogelheim
      
      Review URL: https://codereview.chromium.org/1315673009
      
      Cr-Commit-Position: refs/heads/master@{#30451}
      decc7b09
  17. 20 Aug, 2015 1 commit
    • mstarzinger's avatar
      Separate UnicodeCache out into an own file. · 4e39437a
      mstarzinger authored
      This make inclusion of unicode-inl.h in object.h absolete. Now most
      compilation units don't require that header. It also breaks a cycle
      within declarations of the scanner.h header.
      
      This tries to remove includes of "-inl.h" headers from normal ".h"
      headers, thereby reducing the chance of any cyclic dependencies and
      decreasing the average size of our compilation units.
      
      Note that this change still leaves 3 violations of that rule in the
      code, checked with the "tools/check-inline-includes.sh" tool.
      
      R=yangguo@chromium.org
      
      Review URL: https://codereview.chromium.org/1287893006
      
      Cr-Commit-Position: refs/heads/master@{#30268}
      4e39437a
  18. 12 Aug, 2015 1 commit
    • mstarzinger's avatar
      Remove inline header includes from non-inline headers (1). · 00a07bc1
      mstarzinger authored
      This tries to remove includes of "-inl.h" headers from normal ".h"
      headers, thereby reducing the chance of any cyclic dependencies and
      decreasing the average size of our compilation units.
      
      Note that this change still leaves 7 violations of that rule in the
      code. However there now is the "tools/check-inline-includes.sh" tool
      detecting such violations.
      
      R=bmeurer@chromium.org
      
      Review URL: https://codereview.chromium.org/1283033003
      
      Cr-Commit-Position: refs/heads/master@{#30125}
      00a07bc1
  19. 05 Aug, 2015 2 commits
  20. 30 Jun, 2015 1 commit
  21. 26 Jun, 2015 1 commit
  22. 06 May, 2015 1 commit
  23. 04 May, 2015 1 commit
  24. 27 Apr, 2015 1 commit
  25. 22 Apr, 2015 1 commit
  26. 31 Mar, 2015 1 commit
  27. 23 Mar, 2015 1 commit
  28. 13 Mar, 2015 1 commit
  29. 12 Mar, 2015 1 commit
  30. 11 Mar, 2015 1 commit
  31. 04 Mar, 2015 1 commit
  32. 03 Mar, 2015 2 commits
  33. 05 Feb, 2015 1 commit
  34. 08 Jan, 2015 1 commit
  35. 18 Dec, 2014 1 commit