Skip to content

Issues: rust-lang/rust

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Compile Error on AVR atmega328p with global_asm! in lib.rs needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. O-AVR Target: AVR processors (ATtiny, ATmega, etc.)
#134758 opened Dec 25, 2024 by xjnxjnxjn
[AVR] Large const lookup table is placed in data section C-bug Category: This is a bug. needs-triage This issue may need triage. Remove it if it has been sufficiently triaged. O-AVR Target: AVR processors (ATtiny, ATmega, etc.)
#134731 opened Dec 24, 2024 by imihajlow
avr-rjmp-offset is flaky on x86_64-mingw A-linkers Area: linkers... you gotta love linkers A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs A-testsuite Area: The testsuite used to check the correctness of rustc C-bug Category: This is a bug. C-external-bug Category: issue that is caused by bugs in software beyond our control I-flaky-test Issue: A test is flaky/unreliable/spuriously fails O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-windows-gnu Toolchain: GNU, Operating system: Windows T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#133480 opened Nov 25, 2024 by jieyouxu
Most extern "*-interrupt-*" fn should enforce 0-sized signatures A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-msp430 O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132837 opened Nov 10, 2024 by workingjubilee
Directly calling extern "riscv-interrupt-{m,s}" fn... compiles? A-ABI Area: Concerning the application binary interface (ABI) A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-riscv Target: RISC-V architecture T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132836 opened Nov 10, 2024 by workingjubilee
SIGILL compiler crash when using AVR inline assembly A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132158 opened Oct 25, 2024 by meclondrej
Create a generic AVR target: avr-unknown-unknown A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc O-AVR Target: AVR processors (ATtiny, ATmega, etc.) S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#131651 opened Oct 13, 2024 by Patryk27 Loading…
AVR: miscompilation, or stack overflow, when running cryptographic code A-codegen Area: Code generation A-LTO Area: Link-time optimization (LTO) C-bug Category: This is a bug. I-miscompile Issue: Correct Rust code lowers to incorrect machine code I-unsound Issue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/Soundness O-AVR Target: AVR processors (ATtiny, ATmega, etc.) P-low Low priority T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#109000 opened Mar 10, 2023 by xphoniex
emit-stack-sizes not reporting correct stack size A-CLI Area: Command-line interface (CLI) to the compiler A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#108741 opened Mar 4, 2023 by xphoniex
Consider simulation testing for math on 16-bit targets A-testsuite Area: The testsuite used to check the correctness of rustc C-discussion Category: Discussion or questions that doesn't represent real issues. E-needs-design This issue needs exploration and design to see how and if we can fix/implement it O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-msp430
#107612 opened Feb 2, 2023 by workingjubilee
ICE + other errors when trying to run cargo test on Arduino project, involving vcell C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ O-AVR Target: AVR processors (ATtiny, ATmega, etc.) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#104301 opened Nov 11, 2022 by linclelinkpart5
rustc segfaults when targeting AVR and compiling core in debug mode A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics. O-AVR Target: AVR processors (ATtiny, ATmega, etc.) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#101965 opened Sep 18, 2022 by faithanalog
[strict provenance] Rationalize "Oxford Casts" A-strict-provenance Area: Strict provenance for raw pointers O-AVR Target: AVR processors (ATtiny, ATmega, etc.) O-wasm Target: WASM (WebAssembly), http://webassembly.org/ T-lang Relevant to the language team, which will review and decide on the PR/issue.
#95489 opened Mar 30, 2022 by Gankra
Tracking Issue for the avr-interrupt/avr-non-blocking-interrupt calling convention/ABI A-hardware-interrupts Area: Code for handling the "interrupt ABI" of various processors B-unstable Blocker: Implemented in the nightly compiler and unstable. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC O-AVR Target: AVR processors (ATtiny, ATmega, etc.) S-tracking-needs-summary Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-lang Relevant to the language team, which will review and decide on the PR/issue. WG-embedded Working group: Embedded systems
#69664 opened Mar 3, 2020 by dylanmckay
1 of 3 tasks
ProTip! Add no:assignee to see everything that’s not assigned.