about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/errors.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-01-06 05:23:55 +0000
committerbors <bors@rust-lang.org>2025-01-06 05:23:55 +0000
commitfd98df8f1423e5f9d12fae44ec2a6ae062783a7b (patch)
treebd1613e41c90e13693a45b1e032297b034f18a2d /compiler/rustc_codegen_llvm/src/errors.rs
parent56f9e6f935f9b0d6e83092a0f86d4dbeb878f17d (diff)
parentf985a37c57bfb33e23ea1c586e0ba03365fe47a3 (diff)
downloadrust-fd98df8f1423e5f9d12fae44ec2a6ae062783a7b.tar.gz
rust-fd98df8f1423e5f9d12fae44ec2a6ae062783a7b.zip
Auto merge of #135085 - knickish:m68k_unknown_none, r=workingjubilee
add m68k-unknown-none-elf target

r? `@workingjubilee`

The existing `m68k-unknown-linux-gnu` target builds `std` by default, requires atomics, and has a base cpu with an fpu. A smaller/more embedded target is desirable both to have a baseline target for the ISA, as well to make debugging easier for working on the llvm backend. Currently this target is using the `M68010` as the minimum CPU due, but as missing features are merged into the `M68k` llvm backend I am hoping to lower this further.

I have been able to build very small crates using a toolchain built against this target (together with a later version of `object`) using the configuration described in the target platform-support documentation, although getting anything of substantial complexity to build quickly hits errors in the llvm backend
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions