forked from OSchip/llvm-project
![]() This is still broken because it causes certain tests to be run twice with slightly different configurations, which is wrong in some cases. You can observe this by running: ninja -nv check-all | grep debuginfo-tests And seeing that it passes clang/test and clang/test/debuginfo-tests to lit, which causes it to run debuginfo-tests twice. The fix is going to involve either: a) figuring out that we're running in this "deprecated" configuration, and then deleting the clang/test/debuginfo-tests path, which should cause it to behave identically to before, or: b) make lit smart enough that it doesn't descend into a sub-suite if that sub-suite already has a lit.cfg file. llvm-svn: 318486 |
||
---|---|---|
.. | ||
README.txt | ||
aggregate-indirect-arg.cpp | ||
asan-blocks.c | ||
asan.c | ||
block_var.m | ||
blocks.m | ||
ctor.cpp | ||
dbg-arg.c | ||
foreach.m | ||
forward-declare-class.cpp | ||
lit.local.cfg | ||
llgdb.py | ||
nested-struct.cpp | ||
nrvo-string.cpp | ||
safestack.c | ||
sret.cpp | ||
stack-var.c | ||
static-member-2.cpp | ||
static-member.cpp | ||
vla.c |
README.txt
-*- rst -*- This is a collection of tests to check debugging information generated by compiler. This test suite can be checked out inside clang/test folder. This will enable 'make test' for clang to pick up these tests. Typically, test cases included here includes debugger commands and intended debugger output as comments in source file using DEBUGGER: and CHECK: as prefixes respectively. For example:: define i32 @f1(i32 %i) nounwind ssp { ; DEBUGGER: break f1 ; DEBUGGER: r ; DEBUGGER: p i ; CHECK: $1 = 42 entry: } is a testcase where the debugger is asked to break at function 'f1' and print value of argument 'i'. The expected value of 'i' is 42 in this case.