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

Activity

1. dylanmckay

   added

   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 RFC

   on Mar 3, 2020
2. dylanmckay commented on Mar 3, 2020

   

   dylanmckay

   on Mar 3, 2020

   ContributorAuthor

   More actions

   Raised to appease tidy in #69478.
3. jonas-schievink

   added

   B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.

   O-AVRTarget: AVR processors (ATtiny, ATmega, etc.)Target: AVR processors (ATtiny, ATmega, etc.)

   T-langRelevant to the language teamRelevant to the language team

   on Mar 3, 2020
4. jonas-schievink

   added

   WG-embeddedWorking group: Embedded systemsWorking group: Embedded systems

   on Mar 14, 2020
5. joshtriplett

   added

   S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.

   on Jul 13, 2022
6. joshtriplett commented on Jul 13, 2022

   

   joshtriplett

   on Jul 13, 2022

   Last edited by joshtriplett

   Member

   More actions

   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.
7. workingjubilee

   added

   A-hardware-interruptsArea: Code for handling the "interrupt ABI" of various processorsArea: Code for handling the "interrupt ABI" of various processors

   on Nov 10, 2024