llvm-project/clang/test/CodeGenCXX/duplicate-mangled-name.cpp

// RUN: %clang_cc1 -triple %itanium_abi_triple -emit-llvm-only %s -verify

// rdar://15522601
class MyClass {
 static void meth();
};
void MyClass::meth() { } // expected-note {{previous}}
extern "C" {
  void _ZN7MyClass4methEv() { } // expected-error {{definition with same mangled name as another definition}}
}
Remove the -cxx-abi command-line flag. This makes the C++ ABI depend entirely on the target: MS ABI for -win32 triples, Itanium otherwise. It's no longer possible to do weird combinations. To be able to run a test with a specific ABI without constraining it to a specific triple, new substitutions are added to lit: %itanium_abi_triple and %ms_abi_triple can be used to get the current target triple adjusted to the desired ABI. For example, if the test suite is running with the i686-pc-win32 target, %itanium_abi_triple will expand to i686-pc-mingw32. Differential Revision: http://llvm-reviews.chandlerc.com/D2545 llvm-svn: 199250 2014-01-15 03:35:09 +08:00			`// RUN: %clang_cc1 -triple %itanium_abi_triple -emit-llvm-only %s -verify`
[test] Add test case I forgot to add for r195564. llvm-svn: 195572 2013-11-25 01:05:58 +08:00
			`// rdar://15522601`
			`class MyClass {`
			`static void meth();`
			`};`
In the case of mangling collisions, make an attempt to note both definitions involved. llvm-svn: 214606 2014-08-02 08:50:16 +08:00			`void MyClass::meth() { } // expected-note {{previous}}`
[test] Add test case I forgot to add for r195564. llvm-svn: 195572 2013-11-25 01:05:58 +08:00			`extern "C" {`
			`void _ZN7MyClass4methEv() { } // expected-error {{definition with same mangled name as another definition}}`
			`}`