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

The <code>__mspabi_fltlif</code> implementation of MSP430 seems to be wrong?

O-msp430

Status: Open.

#109210 In rust-lang/rust;

· 823984418 opened on Mar 16, 2023

Consider simulation testing for math on 16-bit targets

A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustc

C-discussionCategory: Discussion or questions that doesn't represent real issues.Category: Discussion or questions that doesn't represent real issues.

E-needs-designThis issue needs exploration and design to see how and if we can fix/implement itThis issue needs exploration and design to see how and if we can fix/implement it

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

O-msp430

Status: Open.

#107612 In rust-lang/rust;

· workingjubilee opened on Feb 2, 2023

Inlined function duplication across complex branches when <code>extern "Rust"</code> is used with LTO and <code>opt-level="s"</code>

A-LTOArea: Link-time optimization (LTO)Area: Link-time optimization (LTO)

C-optimizationCategory: An issue highlighting optimization opportunities or PRs implementing suchCategory: An issue highlighting optimization opportunities or PRs implementing such

I-heavyIssue: Problems and improvements with respect to binary size of generated code.Issue: Problems and improvements with respect to binary size of generated code.

O-ArmTarget: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 stateTarget: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state

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.

#102295 In rust-lang/rust;

· cr1901 opened on Sep 26, 2022

Can't compile core for msp430 - LLVM ERROR

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.

A-target-specsArea: Compile-target specificationsArea: Compile-target specifications

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

O-msp430

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.

WG-embeddedWorking group: Embedded systemsWorking group: Embedded systems

Status: Open.

#45835 In rust-lang/rust;

· japaric opened on Nov 7, 2017

Tracking issue for the <code>msp430-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-msp430

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.

#38487 In rust-lang/rust;

· japaric opened on Dec 20, 2016