llvm-project/llvm/test/TableGen/ListSlices.td

// RUN: llvm-tblgen %s
// XFAIL: vg_leak

def A {
  list<int> B = [10, 20, 30, 4, 1, 1231, 20];
}

def B {
  list<int> X = [10, 20, 30, 4, 1, 1231, 20] [2-4,2,2,0-6];

  list<int> Y = X[4,5];
  int Z = X[4];

  list<int> C = A.B[1-4];

  list<list<int>> AA = [X, Y];

  int BB = AA[0][1];
}
s/tblgen/llvm-tblgen/g in a few missed places, including the tests llvm-svn: 141294 2011-10-06 21:39:59 +08: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. llvm-svn: 99103 2010-03-21 07:08:45 +08:00			`// XFAIL: vg_leak`
New testcase for list slicing llvm-svn: 15248 2004-07-27 09:00:56 +08:00
			`def A {`
			`list<int> B = [10, 20, 30, 4, 1, 1231, 20];`
			`}`

			`def B {`
			`list<int> X = [10, 20, 30, 4, 1, 1231, 20] [2-4,2,2,0-6];`

			`list<int> Y = X[4,5];`
			`int Z = X[4];`

			`list<int> C = A.B[1-4];`

			`list<list<int>> AA = [X, Y];`

			`int BB = AA[0][1];`
			`}`