Search results

All interrupt ABIs should enforce either <code>()</code> or <code>!</code> as return types

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

O-msp430

O-riscvTarget: RISC-V architectureTarget: RISC-V architecture

O-x86_32Target: x86 processors, 32 bit (like i686-*) (IA-32)Target: x86 processors, 32 bit (like i686-*) (IA-32)

O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132841 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

Directly calling <code>"msp430-interrupt" fn</code> should also be invalid

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

O-msp430

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132839 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

Most <code>extern "*-interrupt-*" fn</code> should enforce 0-sized signatures

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

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

O-msp430

O-riscvTarget: RISC-V architectureTarget: RISC-V architecture

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132837 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

Directly calling <code>extern "riscv-interrupt-{m,s}" fn</code>... compiles?

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

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

O-riscvTarget: RISC-V architectureTarget: RISC-V architecture

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132836 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

<code>extern "x86-interrupt" fn</code> allows absurd signatures

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

O-x86_32Target: x86 processors, 32 bit (like i686-*) (IA-32)Target: x86 processors, 32 bit (like i686-*) (IA-32)

O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132835 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

Directly calling <code>"x86-interrupt" fn</code> should be invalid

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

O-x86_32Target: x86 processors, 32 bit (like i686-*) (IA-32)Target: x86 processors, 32 bit (like i686-*) (IA-32)

O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#132834 In rust-lang/rust;

· workingjubilee opened on Nov 10, 2024

ICE: <code>Tried to make Ignore indirect</code>

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

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

S-has-mcveStatus: A Minimal Complete and Verifiable Example has been found for this issueStatus: A Minimal Complete and Verifiable Example has been found for this issue

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#126418 In rust-lang/rust;

· matthiaskrgr opened on Jun 13, 2024

ICE: <code>used byval ABI for unsized layout</code>

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

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

F-unsized_fn_params`#![feature(unsized_fn_params)]``#![feature(unsized_fn_params)]`

I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#124806 In rust-lang/rust;

· matthiaskrgr opened on May 6, 2024

Tracking Issue for <code>riscv-interrupt-{m,s}</code> ABIs

A-ABIArea: Concerning the application binary interface (ABI)Area: Concerning the application binary interface (ABI)

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

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

O-riscvTarget: RISC-V architectureTarget: RISC-V architecture

S-tracking-needs-documentationStatus: Needs documentation.Status: Needs documentation.

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.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#111889 In rust-lang/rust;

· sethp opened on May 23, 2023

Tracking Issue for the <code>avr-interrupt</code>/<code>avr-non-blocking-interrupt</code> calling convention/ABI

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

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

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

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

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.

T-langRelevant to the language teamRelevant to the language team

WG-embeddedWorking group: Embedded systemsWorking group: Embedded systems

Status: Open.

#69664 In rust-lang/rust;

· dylanmckay opened on Mar 3, 2020

SIGSEGV during compilation of extern x86-interrupt fn with u128 param

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

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

C-bugCategory: This is a bug.Category: This is a bug.

F-abi_x86_interrupt

I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.

O-x86_32Target: x86 processors, 32 bit (like i686-*) (IA-32)Target: x86 processors, 32 bit (like i686-*) (IA-32)

O-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)

requires-nightlyThis issue requires a nightly compiler in some way.This issue requires a nightly compiler in some way.

T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.

Status: Open.

#63018 In rust-lang/rust;

· bjorn3 opened on Jul 26, 2019

Tracking issue for the <code>x86-interrupt</code> calling convention

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

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

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

F-abi_x86_interrupt

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.

T-langRelevant to the language teamRelevant to the language team

Status: Open.

#40180 In rust-lang/rust;

· phil-opp opened on Mar 1, 2017