-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Naked functions do not require unsafety #32489
Labels
A-naked
Area: `#[naked]`, prologue and epilogue-free, functions, https://git.io/vAzzS
C-bug
Category: This is a bug.
I-needs-decision
Issue: In need of a decision.
requires-nightly
This issue requires a nightly compiler in some way.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
Comments
cc #32408 |
nagisa
added
the
A-naked
Area: `#[naked]`, prologue and epilogue-free, functions, https://git.io/vAzzS
label
Jun 2, 2016
Mark-Simulacrum
added
C-bug
Category: This is a bug.
I-needs-decision
Issue: In need of a decision.
labels
Jul 24, 2017
Triage: still reproduces today |
jonas-schievink
added
requires-nightly
This issue requires a nightly compiler in some way.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
labels
Dec 25, 2019
@nagisa @steveklabnik I propose we reject this bug in light of the Constrained Naked RFC. There is nothing which prevents a naked function from being safe. |
tmiasko
added a commit
to tmiasko/rust
that referenced
this issue
Jan 21, 2022
Transition unsupported naked functions future incompatibility lint into an error: * Naked functions must contain a single inline assembly block. Introduced as future incompatibility lint in 1.50 rust-lang#79653. Change into an error fixes a soundness issue described in rust-lang#32489. * Naked functions must not use any forms of inline attribute. Introduced as future incompatibility lint in 1.56 rust-lang#87652.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 22, 2022
…nctions, r=Amanieu Reject unsupported naked functions Transition unsupported naked functions future incompatibility lint into an error: * Naked functions must contain a single inline assembly block. Introduced as future incompatibility lint in 1.50 rust-lang#79653. Change into an error fixes a soundness issue described in rust-lang#32489. * Naked functions must not use any forms of inline attribute. Introduced as future incompatibility lint in 1.56 rust-lang#87652. Closes rust-lang#32490. Closes rust-lang#32489. r? `@Amanieu` `@npmccallum` `@joshtriplett`
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 22, 2022
…nctions, r=Amanieu Reject unsupported naked functions Transition unsupported naked functions future incompatibility lint into an error: * Naked functions must contain a single inline assembly block. Introduced as future incompatibility lint in 1.50 rust-lang#79653. Change into an error fixes a soundness issue described in rust-lang#32489. * Naked functions must not use any forms of inline attribute. Introduced as future incompatibility lint in 1.56 rust-lang#87652. Closes rust-lang#32490. Closes rust-lang#32489. r? ``@Amanieu`` ``@npmccallum`` ``@joshtriplett``
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-naked
Area: `#[naked]`, prologue and epilogue-free, functions, https://git.io/vAzzS
C-bug
Category: This is a bug.
I-needs-decision
Issue: In need of a decision.
requires-nightly
This issue requires a nightly compiler in some way.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
RFC states that naked functions must either not contain any “safe” blocks or be unsafe themselves. Currently, code like
is accepted.
The text was updated successfully, but these errors were encountered: