llvm-project/clang/test/CodeGenCXX/pr18661.cpp

// RUN: %clang_cc1 %s -triple %itanium_abi_triple -fcxx-exceptions -fms-compatibility -emit-llvm -o - | FileCheck %s

extern "C" {
  void f();

  // In MS mode we don't validate the exception specification.
  void f() throw() {
  }
}

// PR18661: Clang would fail to emit function definition with mismatching
// exception specification, even though it was just treated as a warning.

// CHECK: define {{.*}}void @f()
Move EH spec mismatches under -fms-compatibility -fms-extensions is intended to enable conforming language extensions and -fms-compatibility is intended to language rule relaxations, so a user could plausibly compile with -fno-ms-compatibility on Windows while still using dllexport, for example. This exception specification validation behavior has been handled as a warning since before -fms-compatibility was added in 2011. I think it's just an oversight that it hasn't been moved yet. This will help users find conformance issues in their code such as those found in _com_ptr_t as described in https://llvm.org/PR42842. Reviewers: hans Subscribers: STL_MSFT, cfe-commits Differential Revision: https://reviews.llvm.org/D66770 llvm-svn: 370087 2019-08-27 17:52:03 +00:00			`// RUN: %clang_cc1 %s -triple %itanium_abi_triple -fcxx-exceptions -fms-compatibility -emit-llvm -o - \| FileCheck %s`
Don't mark decls with mismatching exception specs invalid in MS mode (PR18683) We accept these with a warning in MS mode, but we would previously mark them invalid, causing us not to emit code for them. Differential Revision: http://llvm-reviews.chandlerc.com/D2681 llvm-svn: 200815 2014-02-05 02:37:58 +00:00
			`extern "C" {`
			`void f();`

			`// In MS mode we don't validate the exception specification.`
			`void f() throw() {`
			`}`
			`}`

			`// PR18661: Clang would fail to emit function definition with mismatching`
			`// exception specification, even though it was just treated as a warning.`

Account for calling convention specifiers in function definitions in IR test cases Several tests wouldn't pass when executed on an armv7a_pc_linux triple due to the non-default arm_aapcs calling convention produced on the function definitions in the IR output. Account for this with the application of a little regex. Patch by Ying Yi. llvm-svn: 240971 2015-06-29 17:29:50 +00:00			`// CHECK: define {{.*}}void @f()`