Skip to content
  1. Apr 10, 2013
    • Reid Kleckner's avatar
      [test] Use lit's shell test runner on Windows · d16abb77
      Reid Kleckner authored
      Summary:
      I did a local comparison between using bash and using lit's runner, and
      more of the suite passes with lit than passes with bash.  Most of the
      bash failures have to do with /dev/null, which is nonsensical on
      Windows, but the lit runner handles it.
      
      The lit shell runner is also much faster than bash, so I would expect
      most Windows devs would want it by default.
      
      The behavior can be overridden on any OS by setting
      LIT_USE_INTERNAL_SHELL to 0 or 1 in the environment.
      
      Reviewers: chapuni, ddunbar
      
      CC: llvm-commits, timurrrr
      
      Differential Revision: http://llvm-reviews.chandlerc.com/D559
      
      llvm-svn: 179173
      d16abb77
  2. Apr 04, 2013
  3. Mar 27, 2013
  4. Mar 26, 2013
  5. Mar 15, 2013
  6. Mar 13, 2013
  7. Jan 16, 2013
    • Peter Collingbourne's avatar
      Introduce llvm::sys::getProcessTriple() function. · a51c6ed6
      Peter Collingbourne authored
      In r143502, we renamed getHostTriple() to getDefaultTargetTriple()
      as part of work to allow the user to supply a different default
      target triple at configure time.  This change also affected the JIT.
      However, it is inappropriate to use the default target triple in the
      JIT in most circumstances because this will not necessarily match
      the current architecture used by the process, leading to illegal
      instruction and other such errors at run time.
      
      Introduce the getProcessTriple() function for use in the JIT and
      its clients, and cause the JIT to use it.  On architectures with a
      single bitness, the host and process triples are identical.  On other
      architectures, the host triple represents the architecture of the
      host CPU, while the process triple represents the architecture used
      by the host CPU to interpret machine code within the current process.
      For example, when executing 32-bit code on a 64-bit Linux machine,
      the host triple may be 'x86_64-unknown-linux-gnu', while the process
      triple may be 'i386-unknown-linux-gnu'.
      
      This fixes JIT for the 32-on-64-bit (and vice versa) build on non-Apple
      platforms.
      
      Differential Revision: http://llvm-reviews.chandlerc.com/D254
      
      llvm-svn: 172627
      a51c6ed6
  8. Nov 21, 2012
  9. Nov 01, 2012
  10. Oct 30, 2012
  11. Oct 26, 2012
  12. Oct 19, 2012
  13. Oct 18, 2012
  14. Oct 05, 2012
  15. Oct 03, 2012
  16. Oct 02, 2012
  17. Jul 03, 2012
    • NAKAMURA Takumi's avatar
      llvm/test/lit.cfg: Retweak for Win32 to fix testing. · 2a4930c9
      NAKAMURA Takumi authored
        - execute_external should be;
          - Not on Win32.
          - Using bash.
          In reverse, "execute_internal" shoud be (Win32 && !bash).
      
        - lit.getBashPath() behaves differently before and after tweaking $PATH.
      
      I will add a few explanations there later.
      
      llvm-svn: 159641
      2a4930c9
  18. Jul 02, 2012
    • Chandler Carruth's avatar
      Convert all tests using TCL-style quoting to use shell-style quoting. · a5a29f97
      Chandler Carruth authored
      This was done through the aid of a terrible Perl creation. I will not
      paste any of the horrors here. Suffice to say, it require multiple
      staged rounds of replacements, state carried between, and a few
      nested-construct-parsing hacks that I'm not proud of. It happens, by
      luck, to be able to deal with all the TCL-quoting patterns in evidence
      in the LLVM test suite.
      
      If anyone is maintaining large out-of-tree test trees, feel free to poke
      me and I'll send you the steps I used to convert things, as well as
      answer any painful questions etc. IRC works best for this type of thing
      I find.
      
      Once converted, switch the LLVM lit config to use ShTests the same as
      Clang. In addition to being able to delete large amounts of Python code
      from 'lit', this will also simplify the entire test suite and some of
      lit's architecture.
      
      Finally, the test suite runs 33% faster on Linux now. ;]
      For my 16-hardware-thread (2x 4-core xeon e5520): 36s -> 24s
      
      llvm-svn: 159525
      a5a29f97
    • Chandler Carruth's avatar
      Switch a bunch of Linker tests from using elaborate echo productions to · 8bdfe1ec
      Chandler Carruth authored
      just provide and reference separate input files from an Inputs
      subdirectory. This pattern works very well in the Clang tree and is
      easier to understand in my opinion. It also has fewer limitations and
      will remove one particularly annoying use of TCL-style {} quoting from
      the testsuite.
      
      Also teach the LLVM lit configuration to avoid recursing into 'Inputs'
      subdirectories. This wasn't required for the previous 'Inputs'
      subdirectories used due to fortuitous suffix patterns.
      
      This is the first step to completely removing support for TCL-style tests.
      
      llvm-svn: 159520
      8bdfe1ec
  19. Jun 28, 2012
    • Chandler Carruth's avatar
      Remove 'site.exp' building from both CMake and configure+make. · bf2b400f
      Chandler Carruth authored
      This is another vestige of the DejaGNU roots. There were FIXMEs in the
      lit setup to add a 'lit.site.cfg', which has been around for quite some
      time now, so I've properly switched the handling of the 4 things
      actually used in site.exp to go through lit.site.cfg now. No more
      parsing of the .exp file, one fewer configure-style generated file,
      etc., etc.
      
      llvm-svn: 159313
      bf2b400f
  20. Apr 19, 2012
    • Michael J. Spencer's avatar
      Remove llvm-ld and llvm-stub (which is only used by llvm-ld). · 9125493e
      Michael J. Spencer authored
      llvm-ld is no longer useful and causes confusion and so it is being removed.
      
      * Does not work very well on Windows because it must call a gcc like driver to
        assemble and link.
      * Has lots of hard coded paths which are wrong on many systems.
      * Does not understand most of ld's options.
      * Can be partially replaced by llvm-link | opt | {llc | as, llc -filetype=obj} |
        ld, or fully replaced by Clang.
      
      I know of no production use of llvm-ld, and hacking use should be
      replaced by Clang's driver.
      
      llvm-svn: 155147
      9125493e
  21. Apr 13, 2012
  22. Mar 25, 2012
    • Eli Bendersky's avatar
      Continue cleanup of LIT, getting rid of the remaining artifacts from dejagnu · f3308605
      Eli Bendersky authored
      * Removed test/lib/llvm.exp - it is no longer needed 
      * Deleted the dg.exp reading code from test/lit.cfg. There are no dg.exp files
        left in the test suite so this code is no longer required. test/lit.cfg is
        now much shorter and clearer 
      * Removed a lot of duplicate code in lit.local.cfg files that need access to
        the root configuration, by adding a "root" attribute to the TestingConfig
        object. This attribute is dynamically computed to provide the same
        information as was previously provided by the custom getRoot functions. 
      * Documented the config.root attribute in docs/CommandGuide/lit.pod
      
      llvm-svn: 153408
      f3308605
  23. Feb 16, 2012
  24. Jan 16, 2012
  25. Nov 28, 2011
  26. Nov 05, 2011
  27. Oct 27, 2011
  28. Oct 06, 2011
  29. Oct 04, 2011
  30. Sep 21, 2011
  31. Aug 30, 2011
  32. Jun 23, 2011
    • Andrew Trick's avatar
      lit support for REQUIRES: asserts. · 67ff0718
      Andrew Trick authored
      Take #2. Don't piggyback on the existing config.build_mode. Instead,
      define a new lit feature for each build feature we need (currently
      just "asserts"). Teach both autoconf'd and cmake'd Makefiles to define
      this feature within test/lit.site.cfg. This doesn't require any lit
      harness changes and should be more robust across build systems.
      
      llvm-svn: 133664
      67ff0718
  33. Feb 24, 2011
    • NAKAMURA Takumi's avatar
      test/lit.cfg: Add PATHEXT to 'substitution', to recognize tools on Windows... · cb1b5ff9
      NAKAMURA Takumi authored
      test/lit.cfg: Add PATHEXT to 'substitution', to recognize tools on Windows hosts. Thanks to Danil Malyshev!
      
      Some tests on Windows use the "not" utility and fail with an error "program not executable". The reason for this error is that the name of the executable file sended to the "not" without the extension.
      
      llvm-svn: 126383
      cb1b5ff9
  34. Feb 22, 2011
  35. Feb 09, 2011
  36. Jan 05, 2011
  37. Jan 04, 2011
Loading