Tracking Issue for riscv-interrupt-{m,s} ABIs

[sethp]

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

Similar to #38487, #69664 , and #40180 the intent is to plumb the existing riscv interrupt handler support in LLVM through the front-end. It would enable writing e.g.

extern "riscv-interrupt-m" fn machine_mode_handler() {
    ...
}

to produce a function with a prologue/epilogue suitable for being the target of a hardware interrupt.

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

• Implement the RFC
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

XXX --- list all the "unresolved questions" found in the RFC to ensure they are
not forgotten

Implementation history

#111891

[Jules-Bertholet]

@rustbot label O-riscv