Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for the avr-interrupt/avr-non-blocking-interrupt calling convention/ABI #69664

Open
1 of 3 tasks
dylanmckay opened this issue Mar 3, 2020 · 2 comments
Open
1 of 3 tasks

Tracking Issue for the avr-interrupt/avr-non-blocking-interrupt calling convention/ABI #69664

dylanmckay opened this issue Mar 3, 2020 · 2 comments
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-lang Relevant to the language team, which will review and decide on the PR/issue. WG-embedded Working group: Embedded systems

Comments

@dylanmckay
Copy link
Contributor

dylanmckay commented Mar 3, 2020 •
edited by joshtriplett
Loading

This is a tracking issue for the RFC "XXX" (rust-lang/rfcs#NNN).
The feature gate for the issue is #![feature(FFF)].

Steps

Unresolved Questions

None yet.

Implementation history
@dylanmckay dylanmckay added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Mar 3, 2020
@dylanmckay
Copy link
Contributor Author

Raised to appease tidy in #69478.

@jonas-schievink jonas-schievink added B-unstable Blocker: Implemented in the nightly compiler and unstable. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) T-lang Relevant to the language team, which will review and decide on the PR/issue. labels Mar 3, 2020
@jonas-schievink jonas-schievink added the WG-embedded Working group: Embedded systems label Mar 14, 2020
@joshtriplett joshtriplett added the S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. label Jul 13, 2022
@joshtriplett
Copy link
Member

joshtriplett commented Jul 13, 2022 •
edited
Loading

In #40180 we mentioned wanting a (single) RFC for target-specific interrupt calling conventions, and that work is in progress in rust-lang/rfcs#3246; you may want to coordinate with that work in progress.

@sethp sethp mentioned this issue May 23, 2023
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-lang Relevant to the language team, which will review and decide on the PR/issue. WG-embedded Working group: Embedded systems
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@joshtriplett @jonas-schievink @dylanmckay