Skip to content

rustfmt doesn't recognize x86-interrupt calling convention #1375

Closed
@phil-opp

Description

@phil-opp

rustfmt throws the following error if the source contains functions using the new x86-interrupt calling convention (see rust-lang/rust#39832):

error: invalid ABI: expected one of [cdecl, stdcall, fastcall, vectorcall, aapcs, win64, sysv64, ptx-kernel, msp430-interrupt, Rust, C, system, rust-intrinsic, rust-call, platform-intrinsic, unadjusted], found `x86-interrupt`
  --> /….rs:73:8
   |
73 | extern "x86-interrupt" fn divide_by_zero_handler(stack_frame: &mut ExceptionStackFrame) {
   |  

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugPanic, non-idempotency, invalid code, etc.good first issueIssues up for grabs, also good candidates for new rustfmt contributors

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions