Tracking Issue for extended_varargs_abi_support
#100189
Labels
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
F-extended_varargs_abi_support
`#![feature(extended_varargs_abi_support)]`
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
Soveu
added
the
C-tracking-issue
WaffleLapkin
added
T-compiler
3 tasks
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 13, 2024
…rochenkov Varargs support for system ABI This PR allows functions with the `system` ABI to be variadic (under the `extended_varargs_abi_support` feature tracked in rust-lang#100189). On x86 windows, the `system` ABI is equivalent to `C` for variadic functions. On other platforms, `system` is already equivalent to `C`. Fixes rust-lang#110505
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 13, 2024
Rollup merge of rust-lang#119587 - beepster4096:system_varargs, r=petrochenkov Varargs support for system ABI This PR allows functions with the `system` ABI to be variadic (under the `extended_varargs_abi_support` feature tracked in rust-lang#100189). On x86 windows, the `system` ABI is equivalent to `C` for variadic functions. On other platforms, `system` is already equivalent to `C`. Fixes rust-lang#110505
crawfxrd
added a commit
to crawfxrd/yuffie
that referenced
this issue
Jun 6, 2024
These two functions are defined as variadic (use `...`) which is currently only available for the `C` and `cdecl` ABIs. Make them unavailable until the feature is stabilized for `efiapi`. Ref: rust-lang/rust#100189 Signed-off-by: Tim Crawford <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for extending available ABIs for var-args functions.
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
extended_varargs_abi_support#116161Implementation history
extended_varargs_abi_support#116161The text was updated successfully, but these errors were encountered: