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/member-function-pointer-cal...

29 lines
769 B
C++
Raw Normal View History

Fix another pointer-to-member function miscompile, this time when trying to call a virtual member function. llvm-svn: 95307
2010-02-05 01:08:48 +08:00
// RUN: %clang_cc1 %s -triple=x86_64-apple-darwin10 -emit-llvm -O3 -o - | FileCheck %s
Win64: Pass member pointers larger than 8 bytes by reference The Win64 ABI docs on MSDN say that arguments bigger than 8 bytes are passed by reference. Prior to this change, we were only applying this logic to RecordType arguments. This affects both the Itanium and Microsoft C++ ABIs. Reviewers: majnemer Differential Revision: http://reviews.llvm.org/D3587 llvm-svn: 207817
2014-05-02 08:51:20 +08:00
// RUN: %clang_cc1 %s -triple=x86_64-windows-gnu -emit-llvm -o - | FileCheck %s -check-prefix MINGW64
Fix another pointer-to-member function miscompile, this time when trying to call a virtual member function. llvm-svn: 95307
2010-02-05 01:08:48 +08:00
struct A {
virtual int vf1() { return 1; }
virtual int vf2() { return 2; }
};
int f(A* a, int (A::*fp)()) {
return (a->*fp)();
}
CHECK-LABEL-ify some code gen tests to improve diagnostic experience when tests fail. llvm-svn: 188447
2013-08-15 14:47:53 +08:00
// CHECK-LABEL: define i32 @_Z2g1v()
Relax the FileCheck assertions in this test a touch. Previously the test relied on an artifact of how the inliner and subsequent passes in clang's -O3 mode happen to treat basic blocks and the labels for the basic blocks. In my work on the inliner, and changed this fundamental assumption, and the label that was being checked on the entry basic block will no longer appear in opt builds. There was no reason to expect the label to always be present anyways, much to my regret. I've changed the test to just ensure that we return an immediate constant. If there are intervening instructions, that's bad, but not really that relevant to the test. I'd love it if others have a better way of checking that a function body contains only a 'ret' instruction that isn't dependent on whether or not the entry block receives a label... llvm-svn: 153243
2012-03-22 14:22:13 +08:00
// CHECK: ret i32 1
Win64: Pass member pointers larger than 8 bytes by reference The Win64 ABI docs on MSDN say that arguments bigger than 8 bytes are passed by reference. Prior to this change, we were only applying this logic to RecordType arguments. This affects both the Itanium and Microsoft C++ ABIs. Reviewers: majnemer Differential Revision: http://reviews.llvm.org/D3587 llvm-svn: 207817
2014-05-02 08:51:20 +08:00
// MINGW64-LABEL: define i32 @_Z2g1v()
// MINGW64: call i32 @_Z1fP1AMS_FivE(%struct.A* %{{.*}}, { i64, i64 }* %{{.*}})
Fix another pointer-to-member function miscompile, this time when trying to call a virtual member function. llvm-svn: 95307
2010-02-05 01:08:48 +08:00
int g1() {
A a;
return f(&a, &A::vf1);
}
CHECK-LABEL-ify some code gen tests to improve diagnostic experience when tests fail. llvm-svn: 188447
2013-08-15 14:47:53 +08:00
// CHECK-LABEL: define i32 @_Z2g2v()
Relax the FileCheck assertions in this test a touch. Previously the test relied on an artifact of how the inliner and subsequent passes in clang's -O3 mode happen to treat basic blocks and the labels for the basic blocks. In my work on the inliner, and changed this fundamental assumption, and the label that was being checked on the entry basic block will no longer appear in opt builds. There was no reason to expect the label to always be present anyways, much to my regret. I've changed the test to just ensure that we return an immediate constant. If there are intervening instructions, that's bad, but not really that relevant to the test. I'd love it if others have a better way of checking that a function body contains only a 'ret' instruction that isn't dependent on whether or not the entry block receives a label... llvm-svn: 153243
2012-03-22 14:22:13 +08:00
// CHECK: ret i32 2
Win64: Pass member pointers larger than 8 bytes by reference The Win64 ABI docs on MSDN say that arguments bigger than 8 bytes are passed by reference. Prior to this change, we were only applying this logic to RecordType arguments. This affects both the Itanium and Microsoft C++ ABIs. Reviewers: majnemer Differential Revision: http://reviews.llvm.org/D3587 llvm-svn: 207817
2014-05-02 08:51:20 +08:00
// MINGW64-LABEL: define i32 @_Z2g2v()
// MINGW64: call i32 @_Z1fP1AMS_FivE(%struct.A* %{{.*}}, { i64, i64 }* %{{.*}})
Fix another pointer-to-member function miscompile, this time when trying to call a virtual member function. llvm-svn: 95307
2010-02-05 01:08:48 +08:00
int g2() {
A a;
return f(&a, &A::vf2);
}