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: LLVM for m68k completed (but not merged)
Date: Sun, 21 Jun 2020 22:12:04 +0200 [thread overview]
Message-ID: <7840bdc7-db9c-8638-c462-bbe03d4c5545@physik.fu-berlin.de> (raw)
Hi!
I just received the news that the m68k backend for LLVM has been finished [1].
It has not been merged upstream yet (that will take some time), but it should
be usable now. I'm currently test-building it on Debian/m68k and it would probably
a good idea if more people give it a spin to help finding issues.
One issue I found is that CycleTimer has not been implemented. A quick fix is to
use the definition used by MIPS, i.e.:
diff --git a/llvm/utils/benchmark/src/cycleclock.h b/llvm/utils/benchmark/src/cycleclock.h
index 1b0f09359c9..88b7805faaf 100644
--- a/llvm/utils/benchmark/src/cycleclock.h
+++ b/llvm/utils/benchmark/src/cycleclock.h
@@ -161,7 +161,7 @@ inline BENCHMARK_ALWAYS_INLINE int64_t Now() {
struct timeval tv;
gettimeofday(&tv, nullptr);
return static_cast<int64_t>(tv.tv_sec) * 1000000 + tv.tv_usec;
-#elif defined(__mips__)
+#elif defined(__mips__) || defined(__m68k__)
// mips apparently only allows rdtsc for superusers, so we fall
// back to gettimeofday. It's possible clock_gettime would be better.
struct timeval tv;
Thanks,
Adrian
> [1] https://github.com/M680x0/M680x0-mono-repo
--
.''`. 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 reply other threads:[~2020-06-21 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:12 John Paul Adrian Glaubitz [this message]
2020-06-23 15:34 ` LLVM for m68k completed (but not merged) John Paul Adrian Glaubitz
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=7840bdc7-db9c-8638-c462-bbe03d4c5545@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).