llvm-project/debuginfo-tests
Filipe Cabecinhas 63f2c2cb65 Always compile debuginfo-tests for the host triple
Since these tests expect a working debugger, always compile them for the
host triple, assuming a working debugger is present.

This enables us to compile and run them, even when clang is, by default,
a cross-compiler (but can still target the host).

llvm-svn: 219992
2014-10-16 23:43:34 +00:00
..
README.txt fix typos 2013-09-06 18:10:42 +00:00
aggregate-indirect-arg.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
block_var.m Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
blocks.m Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
ctor.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
dbg-arg.c Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
foreach.m Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
forward-declare-class.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
llgdb.py cleanup comments and remove an obsolete workaround 2014-10-13 18:04:10 +00:00
nested-struct.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
sret.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
static-member-2.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +00:00
static-member.cpp Always compile debuginfo-tests for the host triple 2014-10-16 23:43:34 +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.