Re: First successful cargo build - Re: Summary on what's blocking full Rust support on m68k
Jeffrey Walton <[email protected]> Wed, 20 May 2026 07:08:54 -0400
| Newsgroups | gmane.os.netbsd.ports.m68k,gmane.linux.debian.ports.68k,gmane.linux.ports.m68k |
|---|---|
| Message-ID | <CAH8yC8kmOL39PKZBk=JK4GbjPR6WcAUnr3JGCjN3aRKOtmJ6Dg@mail.gmail.com> |
On Wed, May 20, 2026 at 4:37=E2=80=AFAM John Paul Adrian Glaubitz <[email protected]> wrote: > > On Mon, 2026-05-18 at 15:03 +0200, John Paul Adrian Glaubitz wrote: > > I have used Google Gemini Code Assist now [1] in order to create a patc= h to add support for 32-bit > > relocations to the LLVM M68k backend. This time, the code makes use of = the full capabilities of > > 68020+ CPUs and does not the inefficient four-instruction method to imp= lement 32-bit accesses. > > > > I'm hesitant to send this in for review as this was basically written b= y Gemini under my supervision > > with a lot of testing of build tests. > > I was eventually able to build cargo for m68k-unknown-linux-gnu: > > (unstable-amd64-sbuild)glaubitz@esk:~/rust/build$ file ./x86_64-unknown-l= inux-gnu/stage2-tools/m68k-unknown-linux-gnu/release/cargo > ./x86_64-unknown-linux-gnu/stage2-tools/m68k-unknown-linux-gnu/release/ca= rgo: ELF 32-bit MSB pie executable, Motorola m68k, 68020, version 1 (SYSV),= dynamically linked, interpreter /lib/ld.so.1, > BuildID[sha1]=3D7e5bf08930f87b9eaee173cf163b067f620cb841, for GNU/Linux 3= .2.0, not stripped > (unstable-amd64-sbuild)glaubitz@esk:~/rust/build$ > > The binary runs on m68k but there is no output, unfortunately. Needs more= debugging. Congratulations! I'm still not convinced Rust can take over the world. It has too many poorly supported architectures and platforms, including m68k. Confer, <https://doc.rust-lang.org/nightly/rustc/platform-support.html>. Jeff