hanchenye-llvm-project

History

Filipe Cabecinhas 090a237f29 New round of fixes for "Always compile debuginfo-tests for the host triple" clang tests were breaking, at least when compiling clang only, from an installed llvm. Make the lit.cfg script deal with the case when we don't have a host_triple available. llvm-svn: 220152		2014-10-18 23:47:59 +00:00
..
README.txt	…
aggregate-indirect-arg.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
block_var.m	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
blocks.m	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
ctor.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
dbg-arg.c	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
foreach.m	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
forward-declare-class.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
llgdb.py	cleanup comments and remove an obsolete workaround	2014-10-13 18:04:10 +00:00
nested-struct.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
sret.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
static-member-2.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00
static-member.cpp	New round of fixes for "Always compile debuginfo-tests for the host triple"	2014-10-18 23:47:59 +00:00

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.