-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[MS ABI]: Support preserve_none in MS ABI #96487
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 1 commit
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2962,7 +2962,10 @@ void MicrosoftCXXNameMangler::mangleCallingConvention(CallingConv CC) { | |
// ::= J # __export __fastcall | ||
// ::= Q # __vectorcall | ||
// ::= S # __attribute__((__swiftcall__)) // Clang-only | ||
// ::= T # __attribute__((__swiftasynccall__)) | ||
// ::= W # __attribute__((__swiftasynccall__)) | ||
// ::= U # __attribute__((__preserve_most__)) | ||
// ::= V # __attribute__((__preserve_none__)) // | ||
// Clang-only | ||
// // Clang-only | ||
// ::= w # __regcall | ||
// ::= x # __regcall4 | ||
|
@@ -2986,6 +2989,9 @@ void MicrosoftCXXNameMangler::mangleCallingConvention(CallingConv CC) { | |
case CC_Swift: Out << 'S'; break; | ||
case CC_SwiftAsync: Out << 'W'; break; | ||
case CC_PreserveMost: Out << 'U'; break; | ||
case CC_PreserveNone: | ||
Out << 'V'; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is not a good long term solution. I emailed the relevant external Microsoft mailing list for discussing these issues and CC'd some folks to inquire about a better long term solution, but we can continue with this approach for now. |
||
break; | ||
case CC_X86RegCall: | ||
if (getASTContext().getLangOpts().RegCall4) | ||
Out << "x"; | ||
|
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
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,28 @@ | ||
// RUN: %clang_cc1 -triple x86_64-unknown-windows-msvc -fdeclspec -emit-llvm %s -o - | FileCheck %s | ||
// RUN: %clang_cc1 -triple aarch64-unknown-windows-msvc -fdeclspec -emit-llvm %s -o - | FileCheck %s | ||
|
||
void __attribute__((__preserve_none__)) f() {} | ||
// CHECK-DAG: @"?f@@YVXXZ" | ||
|
||
void (__attribute__((__preserve_none__)) *p)(); | ||
// CHECK-DAG: @"?p@@3P6VXXZEA | ||
|
||
namespace { | ||
void __attribute__((__preserve_none__)) __attribute__((__used__)) f() { } | ||
} | ||
// CHECK-DAG: @"?f@?A0x{{[^@]*}}@@YVXXZ" | ||
|
||
namespace n { | ||
void __attribute__((__preserve_none__)) f() {} | ||
} | ||
// CHECK-DAG: @"?f@n@@YVXXZ" | ||
|
||
struct __declspec(dllexport) S { | ||
S(const S &) = delete; | ||
S & operator=(const S &) = delete; | ||
void __attribute__((__preserve_none__)) m() { } | ||
}; | ||
// CHECK-DAG: @"?m@S@@QEAVXXZ" | ||
|
||
void f(void (__attribute__((__preserve_none__))())) {} | ||
// CHECK-DAG: @"?f@@YAXP6VXXZ@Z" |
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
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.
The default case here should be a proper compiler error, not an unreachable, since there's no good way to prevent arbitrary calling conventions from reaching the mangler.
If you search this file, you can find examples of "cannot yet mangle". Please copy that error handling pattern and use it in the default case for this switch to improve handling of cases like this in the future.
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.
Done