llvm-6502/test/FrontendC/cstring-align.c

// RUN: %llvmgcc %s -S -Os -o - | llc -march=x86 -mtriple=i386-apple-darwin10 | FileCheck %s

extern void func(const char *, const char *);

void long_function_name() {
  func("%s: the function name", __func__);
}

// CHECK: .align 4
// CHECK: ___func__.
// CHECK: .asciz "long_function_name"
Remove explicit uses of -emit-llvm, the test infrastructure adds it automatically. Use -S with llvm-gcc rather than -c, so tests can work when llvm-gcc is really dragonegg (which can output IR with -S but not -c). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@120158 91177308-0d34-0410-b5e6-96231b3b80d8 2010-11-25 21:24:35 +00:00			`// RUN: %llvmgcc %s -S -Os -o - \| llc -march=x86 -mtriple=i386-apple-darwin10 \| FileCheck %s`
Testcase for r89415. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@89417 91177308-0d34-0410-b5e6-96231b3b80d8 2009-11-20 00:32:16 +00:00
			`extern void func(const char , const char );`

			`void long_function_name() {`
			`func("%s: the function name", __func__);`
			`}`

Another test that uses -m64. Here too it looks like it can be removed. Not that the XTARGET wasn't doing anything since it does nothing without an accompanying XFAIL. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@113484 91177308-0d34-0410-b5e6-96231b3b80d8 2010-09-09 12:48:04 +00:00			`// CHECK: .align 4`
			`// CHECK: ___func__.`
			`// CHECK: .asciz "long_function_name"`