maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Verifier/swifterror.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

44 lines
1.5 KiB
LLVM
Raw Normal View History

Swift Calling Convention: add swifterror attribute. A ``swifterror`` attribute can be applied to a function parameter or an AllocaInst. This commit does not include any target-specific change. The target-specific optimization will come as a follow-up patch. Differential Revision: http://reviews.llvm.org/D18092 llvm-svn: 265189
2016-04-02 05:41:15 +08:00
; RUN: not llvm-as %s -o /dev/null 2>&1 | FileCheck %s
%swift_error = type {i64, i8}
; CHECK: swifterror value can only be loaded and stored from, or as a swifterror argument!
; CHECK: %swift_error** %error_ptr_ref
; CHECK: %t = getelementptr inbounds %swift_error*, %swift_error** %error_ptr_ref, i64 1
define float @foo(%swift_error** swifterror %error_ptr_ref) {
%t = getelementptr inbounds %swift_error*, %swift_error** %error_ptr_ref, i64 1
ret float 1.0
}
; CHECK: swifterror argument for call has mismatched alloca
; CHECK: %error_ptr_ref = alloca %swift_error*
; CHECK: %call = call float @foo(%swift_error** swifterror %error_ptr_ref)
define float @caller(i8* %error_ref) {
entry:
%error_ptr_ref = alloca %swift_error*
store %swift_error* null, %swift_error** %error_ptr_ref
%call = call float @foo(%swift_error** swifterror %error_ptr_ref)
ret float 1.0
}
[Verifier] Check type of swifterror alloca Per LangRef, swifterror alloca must be a pointer. Not checking this may result in a verifier error after transforms instead, so make sure it's discarded early.
2022-03-11 21:51:20 +08:00
; CHECK: swifterror alloca must have pointer type
define void @swifterror_alloca_invalid_type() {
%a = alloca swifterror i128
ret void
}
; CHECK: swifterror alloca must not be array allocation
define void @swifterror_alloca_array() {
%a = alloca swifterror i8*, i64 2
ret void
}
Swift Calling Convention: add swifterror attribute. A ``swifterror`` attribute can be applied to a function parameter or an AllocaInst. This commit does not include any target-specific change. The target-specific optimization will come as a follow-up patch. Differential Revision: http://reviews.llvm.org/D18092 llvm-svn: 265189
2016-04-02 05:41:15 +08:00
; CHECK: Cannot have multiple 'swifterror' parameters!
declare void @a(i32** swifterror %a, i32** swifterror %b)
[Verifier] Improve incompatible attribute type check A couple of attributes had explicit checks for incompatibility with pointer types. However, this is already handled generically by the typeIncompatible() check. We can drop these after adding SwiftError to typeIncompatible(). However, the previous implementation of the check prints out all attributes that are incompatible with a given type, even though those attributes aren't actually used. This has the annoying result that the error message changes every time a new attribute is added to the list. Improve this by explicitly finding which attribute isn't compatible and printing just that.
2021-07-15 02:58:52 +08:00
; CHECK: Attribute 'swifterror' applied to incompatible type!
Swift Calling Convention: add swifterror attribute. A ``swifterror`` attribute can be applied to a function parameter or an AllocaInst. This commit does not include any target-specific change. The target-specific optimization will come as a follow-up patch. Differential Revision: http://reviews.llvm.org/D18092 llvm-svn: 265189
2016-04-02 05:41:15 +08:00
declare void @b(i32 swifterror %a)
; CHECK: Attribute 'swifterror' only applies to parameters with pointer to pointer type!
declare void @c(i32* swifterror %a)