maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGenCoroutines/coro-promise-dtor.cpp

48 lines
1.3 KiB
C++
Raw Normal View History

[coroutines] [NFC] Add tests for return_void, unhandled_exception and promise dtor Summary: * Test that coroutine promise destructor is called. * Test that we call return_void on fallthrough * Test that we call unhandled exception in a try catch surrounding the body Reviewers: EricWF, GorNishanov Reviewed By: GorNishanov Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D33479 llvm-svn: 303748
2017-05-24 22:19:48 +08:00
// RUN: %clang_cc1 -std=c++14 -fcoroutines-ts -triple=x86_64-pc-windows-msvc18.0.0 -emit-llvm -o - %s -fexceptions -fcxx-exceptions -disable-llvm-passes | FileCheck %s
// -triple=x86_64-unknown-linux-gnu
#include "Inputs/coroutine.h"
namespace coro = std::experimental::coroutines_v1;
struct coro_t {
void* p;
~coro_t();
struct promise_type {
coro_t get_return_object();
coro::suspend_never initial_suspend();
coro::suspend_never final_suspend();
void return_void();
promise_type();
~promise_type();
void unhandled_exception();
};
};
struct Cleanup { ~Cleanup(); };
void may_throw();
coro_t f() {
Cleanup cleanup;
may_throw();
co_return;
}
Bring r325915 back. The tests that failed on a windows host have been fixed. Original message: Start setting dso_local for COFF. With this there are still some GVs where we don't set dso_local because setGVProperties is never called. I intend to fix that in followup commits. This is just the bare minimum to teach shouldAssumeDSOLocal what it should do for COFF. llvm-svn: 325940
2018-02-24 03:30:48 +08:00
// CHECK-LABEL: define dso_local void @"\01?f@@YA?AUcoro_t@@XZ"(
[coroutines] [NFC] Add tests for return_void, unhandled_exception and promise dtor Summary: * Test that coroutine promise destructor is called. * Test that we call return_void on fallthrough * Test that we call unhandled exception in a try catch surrounding the body Reviewers: EricWF, GorNishanov Reviewed By: GorNishanov Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D33479 llvm-svn: 303748
2017-05-24 22:19:48 +08:00
// CHECK: %gro.active = alloca i1
// CHECK: store i1 false, i1* %gro.active
// CHECK: invoke %"struct.coro_t::promise_type"* @"\01??0promise_type@coro_t@@QEAA@XZ"(
// CHECK: invoke void @"\01?get_return_object@promise_type@coro_t@@QEAA?AU2@XZ"(
// CHECK: store i1 true, i1* %gro.active
// CHECK: %[[IS_ACTIVE:.+]] = load i1, i1* %gro.active
// CHECK: br i1 %[[IS_ACTIVE]], label %[[CLEANUP1:.+]], label
// CHECK: [[CLEANUP1]]:
// CHECK: %[[NRVO:.+]] = load i1, i1* %nrvo
// CHECK: br i1 %[[NRVO]], label %{{.+}}, label %[[DTOR:.+]]
// CHECK: [[DTOR]]:
[MS] Always use base dtors in place of complete/vbase dtors when possible Summary: Previously we tried too hard to uphold the fiction that destructor variants work like they do on Itanium throughout the ABI-neutral parts of clang. This lead to MS C++ ABI incompatiblities and other bugs. Now, -mconstructor-aliases will no longer control this ABI detail, and clang -cc1's LLVM IR output will be this much closer to the clang driver's. Based on a patch by Zahira Ammarguellat: https://reviews.llvm.org/D39063 I've tried to move the logic that Zahira added into MicrosoftCXXABI.cpp. There is only one ABI-specific detail sticking out, and that is in CodeGenModule::getAddrOfCXXStructor, where we collapse complete dtors to base dtors in the MS ABI. This fixes PR32990. Reviewers: erichkeane, zahiraam, majnemer, rjmccall Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D44505 llvm-svn: 327732
2018-03-17 03:40:50 +08:00
// CHECK: call void @"\01??1coro_t@@QEAA@XZ"(