maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGenCXX/microsoft-abi-eh-terminate.cpp

17 lines
945 B
C++
Raw Normal View History

[WinEH] Make sure terminate handlers have funclet operands Calls to the terminate handler must be annotated within the exception region they are within. llvm-svn: 261751
2016-02-25 01:02:45 +08:00
// RUN: %clang_cc1 -std=c++11 -emit-llvm %s -o - -triple=x86_64-pc-windows-msvc -mconstructor-aliases -fexceptions -fcxx-exceptions -fms-compatibility-version=18.00 | FileCheck -check-prefix=MSVC2013 -check-prefix=CHECK %s
// RUN: %clang_cc1 -std=c++11 -emit-llvm %s -o - -triple=x86_64-pc-windows-msvc -mconstructor-aliases -fexceptions -fcxx-exceptions -fms-compatibility-version=19.00 | FileCheck -check-prefix=MSVC2015 -check-prefix=CHECK %s
[MS ABI] Update EH emission for MSVC 2015 compatibility MSVC 2015 renamed the symbol found by name lookup for 'std::terminate' so we cannot rely on using '?terminate@@YAXXZ'. Furthermore, it seems that 2015 will be the first release of MSVC which permits inlining a function which is noexcept into a function which isn't. This is implemented by creating a cleanup for the invoker which jumps to __std_terminate. Clang's implementation of this aspect of the MSVC scheme is slightly less efficient in this respect because we use a catch handler configured as a catch-all handler instead. llvm-svn: 236961
2015-05-11 05:38:26 +08:00
void may_throw();
void never_throws() noexcept(true) {
may_throw();
}
[WinEH] Remove NewMSEH and enable its behavior by default Testing has shown that it is at least as reliable as the old landingpad pattern matching code. llvm-svn: 249647
2015-10-08 09:13:52 +08:00
// CHECK-LABEL: define void @"\01?never_throws@@YAXXZ"()
// CHECK-SAME: personality i8* bitcast (i32 (...)* @__CxxFrameHandler3 to i8*)
[MS ABI] Update EH emission for MSVC 2015 compatibility MSVC 2015 renamed the symbol found by name lookup for 'std::terminate' so we cannot rely on using '?terminate@@YAXXZ'. Furthermore, it seems that 2015 will be the first release of MSVC which permits inlining a function which is noexcept into a function which isn't. This is implemented by creating a cleanup for the invoker which jumps to __std_terminate. Clang's implementation of this aspect of the MSVC scheme is slightly less efficient in this respect because we use a catch handler configured as a catch-all handler instead. llvm-svn: 236961
2015-05-11 05:38:26 +08:00
// CHECK: invoke void @"\01?may_throw@@YAXXZ"()
[WinEH] Make sure terminate handlers have funclet operands Calls to the terminate handler must be annotated within the exception region they are within. llvm-svn: 261751
2016-02-25 01:02:45 +08:00
// CHECK: %[[cp:.*]] = cleanuppad within none []
[MS ABI] Don't rely on terminatepad We'd like to remove support for terminatepad from LLVM. To do this, we need to move Clang off of it first. The intent behind terminatepad was to carefully model exception specifications for the MSVC personality. However, we don't support exception specifications for the MSVC personality and neither does MSVC. Instead, MSVC supports all-or-nothing exception specifications. We can model this limited usage using cleanuppads which call std::terminate. Differential Revision: http://reviews.llvm.org/D15478 llvm-svn: 255521
2015-12-15 02:34:18 +08:00
// MSVC2013: call void @"\01?terminate@@YAXXZ"()
// MSVC2015: call void @__std_terminate()
[WinEH] Make sure terminate handlers have funclet operands Calls to the terminate handler must be annotated within the exception region they are within. llvm-svn: 261751
2016-02-25 01:02:45 +08:00
// CHECK-SAME: [ "funclet"(token %[[cp]]) ]
[MS ABI] Update EH emission for MSVC 2015 compatibility MSVC 2015 renamed the symbol found by name lookup for 'std::terminate' so we cannot rely on using '?terminate@@YAXXZ'. Furthermore, it seems that 2015 will be the first release of MSVC which permits inlining a function which is noexcept into a function which isn't. This is implemented by creating a cleanup for the invoker which jumps to __std_terminate. Clang's implementation of this aspect of the MSVC scheme is slightly less efficient in this respect because we use a catch handler configured as a catch-all handler instead. llvm-svn: 236961
2015-05-11 05:38:26 +08:00
// CHECK-NEXT: unreachable