From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Debian m68k <debian-68k@lists.debian.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: LLVM for m68k completed (but not merged)
Date: Tue, 23 Jun 2020 17:34:40 +0200 [thread overview]
Message-ID: <131920ba-0da7-7cb7-43a4-f4e93179e5eb@physik.fu-berlin.de> (raw)
In-Reply-To: <7840bdc7-db9c-8638-c462-bbe03d4c5545@physik.fu-berlin.de>
Hi!
On 6/21/20 10:12 PM, John Paul Adrian Glaubitz wrote:
> I just received the news that the m68k backend for LLVM has been finished [1].
I have had a go at the code now and with some changes to clang, I can actually
cross-compile "Hello World" in C now, cross-compile it with clang and get a working
m68k executable [1].
> glaubitz@epyc:/tmp/llvm-build> ./bin/clang -target m68k-linux-gnu ~/hello.c -o hello.m68k
> glaubitz@epyc:/tmp/llvm-build> file hello.m68k
> hello.m68k: ELF 32-bit MSB executable, Motorola m68k, 68020, version 1 (SYSV), dynamically linked, interpreter /lib/ld.so.1, for GNU/Linux 3.2.0, not stripped
> glaubitz@epyc:/tmp/llvm-build> cp -av hello.m68k /local_scratch/glaubitz/
> 'hello.m68k' -> '/local_scratch/glaubitz/hello.m68k'
> glaubitz@epyc:/tmp/llvm-build> schroot -c sid-m68k-sbuild
> glaubitz@epyc:/tmp/llvm-build> uname -a
> Linux epyc 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23) m68k GNU/Linux
> glaubitz@epyc:/tmp/llvm-build> /glaubitz/hello.m68k
> Hello World!
> glaubitz@epyc:/tmp/llvm-build>
Adrian
> [1] https://github.com/M680x0/M680x0-mono-repo/pull/7
--
.''`. 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
next prev parent reply other threads:[~2020-06-23 15:34 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 [this message]
2020-06-24 1:07 ` Finn Thain
2020-06-24 7:42 ` John Paul Adrian Glaubitz
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=131920ba-0da7-7cb7-43a4-f4e93179e5eb@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--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).