From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Debian m68k <debian-68k@lists.debian.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: LLVM for m68k completed (but not merged)
Date: Wed, 24 Jun 2020 09:42:04 +0200 [thread overview]
Message-ID: <c2547ebd-a071-fb28-788a-a0bed476c04a@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.LNX.2.22.394.2006241039120.8@nippy.intranet>
Hi Finn!
On 6/24/20 3:07 AM, Finn Thain wrote:
> Very impressive! I imagine that creating an LLVM backend would be a
> massive undertaking.
>
> Does this backend bring any benefits compared with gcc? E.g. will it help
> gain support for other languages, like rust?
Yes, my primary goal was to be able to use Rust on m68k. I have already
started on the Rust part [1]. And now I need an m68k expert to help
with the ABI part [2].
> Do you know if anyone has run the LLVM unit tests on Motorola silicon?
Not that I know of. I have successfully built LLVM natively on qemu-m68k, but
clang currently doesn't work properly [3]. I have not looked into details yet
why that doesn't work.
Adrian
> [1] https://github.com/glaubitz/rust/tree/m68k-linux
> [2] https://github.com/glaubitz/rust/blob/m68k-linux/src/librustc_target/abi/call/m68k.rs
> [3] https://github.com/M680x0/M680x0-mono-repo/issues/10
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2020-06-24 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:12 LLVM for m68k completed (but not merged) John Paul Adrian Glaubitz
2020-06-23 15:34 ` John Paul Adrian Glaubitz
2020-06-24 1:07 ` Finn Thain
2020-06-24 7:42 ` John Paul Adrian Glaubitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2547ebd-a071-fb28-788a-a0bed476c04a@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=fthain@telegraphics.com.au \
--cc=linux-m68k@lists.linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).