Skip to content
  1. Dec 03, 2012
    • Chandler Carruth's avatar
      Use the new script to sort the includes of every file under lib. · ed0881b2
      Chandler Carruth authored
      Sooooo many of these had incorrect or strange main module includes.
      I have manually inspected all of these, and fixed the main module
      include to be the nearest plausible thing I could find. If you own or
      care about any of these source files, I encourage you to take some time
      and check that these edits were sensible. I can't have broken anything
      (I strictly added headers, and reordered them, never removed), but they
      may not be the headers you'd really like to identify as containing the
      API being implemented.
      
      Many forward declarations and missing includes were added to a header
      files to allow them to parse cleanly when included first. The main
      module rule does in fact have its merits. =]
      
      llvm-svn: 169131
      ed0881b2
  2. Nov 28, 2012
    • Eli Bendersky's avatar
      Add backreference matching capabilities to Support/Regex, with · 10f22d70
      Eli Bendersky authored
      appropriate unit tests. This change in itself is not expected to
      affect any functionality at this point, but it will serve as a
      stepping stone to improve FileCheck's variable matching capabilities.
      
      Luckily, our regex implementation already supports backreferences,
      although a bit of hacking is required to enable it. It supports both
      Basic Regular Expressions (BREs) and Extended Regular Expressions
      (EREs), without supporting backrefs for EREs, following POSIX strictly
      in this respect. And EREs is what we actually use (rightly). This is
      contrary to many implementations (including the default on Linux) of
      POSIX regexes, that do allow backrefs in EREs.
      
      Adding backref support to our EREs is a very simple change in the
      regcomp parsing code. I fail to think of significant cases where it
      would clash with existing things, and can bring more versatility to
      the regexes we write. There's always the danger of a backref in a
      specially crafted regex causing exponential matching times, but since
      we mainly use them for testing purposes I don't think it's a big
      problem. [it can also be placed behind a flag specific to FileCheck,
      if needed].
      
      For more details, see:
      
      * http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-November/055840.html
      * http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20121126/156878.html
      
      llvm-svn: 168802
      10f22d70
  3. Apr 09, 2011
  4. Jul 15, 2010
  5. Feb 17, 2010
  6. Sep 26, 2009
  7. Sep 24, 2009
  8. Aug 30, 2009
Loading