-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[CGData][Merger] Avoid merging the attached call target #121030
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
37 changes: 37 additions & 0 deletions
37
llvm/test/CodeGen/AArch64/cgdata-no-merge-attached-call-garget.ll
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
; This test verifies that two similar functions, f1 and f2, are not merged | ||
; when their attached call targets differ, since these targets cannot be parameterized. | ||
|
||
; RUN: llc -mtriple=arm64-apple-darwin -enable-global-merge-func=true < %s | FileCheck %s | ||
|
||
; CHECK-NOT: _f1.Tgm | ||
; CHECK-NOT: _f2.Tgm | ||
|
||
target datalayout = "e-m:o-i64:64-i128:128-n32:64-S128" | ||
target triple = "arm64-apple-darwin" | ||
|
||
define i64 @f1(ptr %0) { | ||
%2 = call ptr @g1(ptr %0, i32 0) minsize [ "clang.arc.attachedcall"(ptr @llvm.objc.unsafeClaimAutoreleasedReturnValue) ] | ||
tail call void (...) @llvm.objc.clang.arc.noop.use(ptr %2) | ||
%3 = call i64 @g2(ptr %2) | ||
tail call void @objc_release(ptr %2) | ||
%4 = tail call i64 @g3(i64 %3) | ||
ret i64 %4 | ||
} | ||
|
||
define i64 @f2(ptr %0) { | ||
%2 = call ptr @g1(ptr %0, i32 0) minsize [ "clang.arc.attachedcall"(ptr @llvm.objc.retainAutoreleasedReturnValue) ] | ||
tail call void (...) @llvm.objc.clang.arc.noop.use(ptr %2) | ||
%3 = call i64 @g2(ptr %2) | ||
tail call void @objc_release(ptr %2) | ||
%4 = tail call i64 @g3(i64 %3) | ||
ret i64 %4 | ||
} | ||
|
||
declare ptr @g1(ptr, i32) | ||
declare i64 @g2(ptr) | ||
declare i64 @g3(i64) | ||
|
||
declare void @llvm.objc.clang.arc.noop.use(...) | ||
declare ptr @llvm.objc.unsafeClaimAutoreleasedReturnValue(ptr) | ||
declare ptr @llvm.objc.retainAutoreleasedReturnValue(ptr) | ||
declare void @objc_release(ptr) |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a general method to determine whether a bundle is unsafe to optimize? If so, we can avoid enumerating all of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not familiar with the bundle. Conservatively, we could bail out all bundle cases, but for now I bail out the known case only. I think if we run into invalid cases, the compilation will fail/crash so we can follow up.