llvm/test/TableGen/UnsetBitInit.td

// RUN: llvm-tblgen %s
// XFAIL: vg_leak
class x {
  field bits<32> A;
}

class y<bits<2> B> : x {
  let A{21-20} = B;
}

def z : y<{0,?}>;
s/tblgen/llvm-tblgen/g in a few missed places, including the tests git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@141294 91177308-0d34-0410-b5e6-96231b3b80d8 2011-10-06 13:39:59 +00:00			`// RUN: llvm-tblgen %s`
Add support for XFAILing valgrind runs with memory leak checking independently of runs without leak checking. We add -vg to the triple for non-checked runs, or -vg_leak for checked runs. Also use this to XFAIL the TableGen tests, since tablegen leaks like a sieve. This includes some valgrindArgs refactoring. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@99103 91177308-0d34-0410-b5e6-96231b3b80d8 2010-03-20 23:08:45 +00:00			`// XFAIL: vg_leak`
Fix pr5470. Tablegen handles template arguments by temporarily setting their values, resolving references to them, and then removing the definitions. If a template argument is set to an undefined value, we need to resolve references to that argument to an explicit undefined value. The current code leaves the reference to the template argument as it is, which causes an assertion failure later when the definition of the template argument is removed. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@89581 91177308-0d34-0410-b5e6-96231b3b80d8 2009-11-22 03:58:57 +00:00			`class x {`
			`field bits<32> A;`
			`}`

			`class y<bits<2> B> : x {`
			`let A{21-20} = B;`
			`}`

			`def z : y<{0,?}>;`