-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking Issue for extended_varargs_abi_support #100189
Copy link
Copy link
Closed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCF-extended_varargs_abi_support`#![feature(extended_varargs_abi_support)]``#![feature(extended_varargs_abi_support)]`S-tracking-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCF-extended_varargs_abi_support`#![feature(extended_varargs_abi_support)]``#![feature(extended_varargs_abi_support)]`S-tracking-design-concernsStatus: There are blocking design concerns.Status: There are blocking design concerns.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a tracking issue for extending available ABIs for var-args functions to support
aapcs,win64,sysv64andefiapi.The feature gate for the issue is
#![feature(extended_varargs_abi_support)].About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Stabilizereverted by Revert "Stabilizeextended_varargs_abi_support#116161extended_varargs_abi_support" #136897Implementation history
extended_varargs_abi_support#116161extended_varargs_abi_support" #136897extern_system_varargsfeature #136948Unresolved Questions
extern "system"be included? the original feature only described itself as applying toextern "efiapi",extern "sysv64", andextern "win64", and later the feature described itself as applying toextern "aapcs", but the only case whereextern "system"is meaningfully distinct is a case where it cannot be a vararg ABI. while MSVC sometimes translates__stdcallto be identical to the C ABI, we have previously rejected implementing MSVC's oddities:unsupported_calling_conventions#87678Footnotes
this was not recorded as part of the impl history until after it was discovered this feature was initially stabilized without an FCP. ↩