summaryrefslogtreecommitdiff
path: root/test/CodeGen/lineno-dbginfo.c
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2014-01-15 09:07:56 +0000
committerChandler Carruth <chandlerc@gmail.com>2014-01-15 09:07:56 +0000
commit254052a00dd24ffdd2d106ebc8c3da1e5cdde42e (patch)
tree7bea5d8a2281098e269efe0160fe78ac241380aa /test/CodeGen/lineno-dbginfo.c
parent5ca669059fce7754e2b2dd4b3728939aedc55ff0 (diff)
downloadclang-254052a00dd24ffdd2d106ebc8c3da1e5cdde42e.tar.gz
Switch this test from needlessly running the clang driver to directly
test the CC1 layer. This actually uncovered that the test semes to no longer be passing for the reasons intended. =[ The name of the test would lead me to believe that it should be testing the semantics of noreturn in the static analyzer.... but there are in fact no -verify assertions about noreturn that i can find. And the noreturn checker is no longer in 'alpha.core'. It is in 'core.builtins'. The test *does* have one assertion for a null dereference warning. This *also* isn't in 'alpha.core', but the driver inserts a pile of other checker packages, including 'core' which has this warning. So I have switch the RUN line to actually do the minimal thing that this test currently exercises, but someone who works on the static analyzer should probably look at this and either nuke it or move it to actually check the noreturn behavior. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@199307 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/CodeGen/lineno-dbginfo.c')
0 files changed, 0 insertions, 0 deletions