summaryrefslogtreecommitdiffstats
path: root/llvm/utils/lit/TestFormats.py
Commit message (Collapse)AuthorAgeFilesLines
* lit: Sink code into a 'lit' package.Daniel Dunbar2009-12-261-189/+0
| | | | llvm-svn: 92168
* lit: Improve error when gtest discovery fails.Daniel Dunbar2009-12-151-3/+8
| | | | llvm-svn: 91458
* lit: Fix exclude dirs functionality.Daniel Dunbar2009-11-181-2/+3
| | | | llvm-svn: 89210
* Make X86-64 in the Large model always emit 64-bit calls.Jeffrey Yasskin2009-11-161-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The large code model is documented at http://www.x86-64.org/documentation/abi.pdf and says that calls should assume their target doesn't live within the 32-bit pc-relative offset that fits in the call instruction. To do this, we turn off the global-address->target-global-address conversion in X86TargetLowering::LowerCall(). The first attempt at this broke the lazy JIT because it can separate the movabs(imm->reg) from the actual call instruction. The lazy JIT receives the address of the movabs as a relocation and needs to record the return address from the call; and then when that call happens, it needs to patch the movabs with the newly-compiled target. We could thread the call instruction into the relocation and record the movabs<->call mapping explicitly, but that seems to require at least as much new complication in the code generator as this change. To fix this, we make lazy functions _always_ go through a call stub. You'd think we'd only have to force lazy calls through a stub on difficult platforms, but that turns out to break indirect calls through a function pointer. The right fix for that is to distinguish between calls and address-of operations on uncompiled functions, but that's complex enough to leave for someone else to do. Another attempt at this defined a new CALL64i pseudo-instruction, which expanded to a 2-instruction sequence in the assembly output and was special-cased in the X86CodeEmitter's emitInstruction() function. That broke indirect calls in the same way as above. This patch also removes a hack forcing Darwin to the small code model. Without far-call-stubs, the small code model requires things of the JITMemoryManager that the DefaultJITMemoryManager can't provide. Thanks to echristo for lots of testing! llvm-svn: 88984
* lit: Factor a new OneCommandPerFileTest out of SyntaxCheckTest.Daniel Dunbar2009-11-151-11/+40
| | | | | | | - Used for running a single fixed command on a directory of files, with the option of deriving a temporary input file from the test source. llvm-svn: 88844
* Remove duplicate implementation of excludes functionality, and support excludingDaniel Dunbar2009-11-151-14/+6
| | | | | | | | dirnames. Also, add support for the 'unsupported' config property. llvm-svn: 88838
* lit: Drop require_and_and support.Daniel Dunbar2009-11-081-4/+2
| | | | llvm-svn: 86447
* Teach lit's SyntaxCheckTest two new tricks:Douglas Gregor2009-11-051-1/+16
| | | | | | | - skip .svn directories - add a set of excluded filenames so we can easily skip tests llvm-svn: 86185
* Support GoogleTest's "typed tests"Jeffrey Yasskin2009-10-181-0/+4
| | | | | | | | | | (http://code.google.com/p/googletest/wiki/GoogleTestAdvancedGuide#Typed_Tests) in lit.py. These tests have names like "ValueMapTest/0.Iteration", which broke when lit.py os.path.join()ed them onto the path and then assumed it could os.path.split() them back off. This patch shifts path components from the testPath to the testName until the testPath exists. llvm-svn: 84387
* lit: Add a custom test format for use in clang.Daniel Dunbar2009-09-161-0/+53
| | | | llvm-svn: 81987
* lit: Give test formats control over test discovery.Daniel Dunbar2009-09-141-0/+91
llvm-svn: 81751
OpenPOWER on IntegriCloud