llvm/test/Verifier, branch stablehttp://llvm.orghttps://git.amat.us/llvm/atom/test/Verifier?h=stable2013-01-16T21:38:56Z[IR] Add 'Append' and 'AppendUnique' module flag behaviors.2013-01-16T21:38:56ZDaniel Dunbardaniel@zuster.org2013-01-16T21:38:56Zurn:sha1:5db391c67d0922f4ab2ba57c07def19759c801a4
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@172659 91177308-0d34-0410-b5e6-96231b3b80d8
[IR] Add verification for module flags with the "require" behavior.2013-01-15T20:52:06ZDaniel Dunbardaniel@zuster.org2013-01-15T20:52:06Zurn:sha1:12bfff440700c58bc67e9f9d8f99121632022cf1
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@172549 91177308-0d34-0410-b5e6-96231b3b80d8
[IR] Add verifier support for llvm.module.flags.2013-01-15T01:22:53ZDaniel Dunbardaniel@zuster.org2013-01-15T01:22:53Zurn:sha1:8dd938ed179267b2a3a5206c78e89530967f45a5
- Also, update the LangRef documentation on module flags to match the
implementation.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@172498 91177308-0d34-0410-b5e6-96231b3b80d8
Assert that dominates is not given a multiple edge. Finding out if we have2012-08-17T18:21:28ZRafael Espindolarafael.espindola@gmail.com2012-08-17T18:21:28Zurn:sha1:d5118c8f78a05ad0b426b6032138d1d934b77c8d
multiple edges between two blocks is linear. If the caller is iterating all
edges leaving a BB that would be a square time algorithm. It is more efficient
to have the callers handle that case.
Currently the only callers are:
* GVN: already avoids the multiple edge case.
* Verifier: could only hit this assert when looking at an invalid invoke. Since
it already rejects the invoke, just avoid computing the dominance for it.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@162113 91177308-0d34-0410-b5e6-96231b3b80d8
The normal edge of an invoke is not allowed to branch to a block with a2012-08-10T20:55:20ZEli Friedmaneli.friedman@gmail.com2012-08-10T20:55:20Zurn:sha1:6b951b25c35f739ee0a1b5a4615718220830817d
landingpad. Enforce it in the verifier, and fix the regression tests to match.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@161697 91177308-0d34-0410-b5e6-96231b3b80d8
Fix a typo (the the => the)2012-07-23T08:51:15ZSylvestre Ledrusylvestre@debian.org2012-07-23T08:51:15Zurn:sha1:c8e41c591741b3da1077f7000274ad040bef8002
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@160621 91177308-0d34-0410-b5e6-96231b3b80d8
Fix the remaining TCL-style quotes found in the testsuite. This is2012-07-02T19:09:46ZChandler Carruthchandlerc@gmail.com2012-07-02T19:09:46Zurn:sha1:1de43ede8904e08de37f601c9bab0b70f71156e1
another mechanical change accomplished though the power of terrible Perl
scripts.
I have manually switched some "s to 's to make escaping simpler.
While I started this to fix tests that aren't run in all configurations,
the massive number of tests is due to a really frustrating fragility of
our testing infrastructure: things like 'grep -v', 'not grep', and
'expected failures' can mask broken tests all too easily.
Essentially, I'm deeply disturbed that I can change the testsuite so
radically without causing any change in results for most platforms. =/
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159547 91177308-0d34-0410-b5e6-96231b3b80d8
Convert the uses of '|&' to use '2>&1 |' instead, which works on old2012-07-02T18:37:59ZChandler Carruthchandlerc@gmail.com2012-07-02T18:37:59Zurn:sha1:49589f0d0e35f643e697ab7ae8a51a530d38b0d8
versions of Bash. In addition, I can back out the change to the lit
built-in shell test runner to support this.
This should fix the majority of fallout on Darwin, but I suspect there
will be a few straggling issues.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159544 91177308-0d34-0410-b5e6-96231b3b80d8
Convert all tests using TCL-style quoting to use shell-style quoting.2012-07-02T12:47:22ZChandler Carruthchandlerc@gmail.com2012-07-02T12:47:22Zurn:sha1:4177e6fff50552908bab510f1e896fa974a6f155
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
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159525 91177308-0d34-0410-b5e6-96231b3b80d8
Make tests which first provide a negative assertion via 'not', then2012-07-02T12:23:19ZChandler Carruthchandlerc@gmail.com2012-07-02T12:23:19Zurn:sha1:563add96ce541e02ef976c4948b640f0a1462967
a pipeline, and then a positive assertion via grep, use two RUN lines
instead.
Supporting these complex ideas of 'success' and 'failure' across
multiple stages of a pipeline is brittle in the shell world, and would
block switching to ShTest format; it only worked due to contrivances
introduced by the TclTest format.
Writing this as two separate RUN lines seems clearer in any event.
This is another step toward completely removing TclTests from lit.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159524 91177308-0d34-0410-b5e6-96231b3b80d8