public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Philip Herron <philip.herron@embecosm.com>,
	Oleg Endo <oleg.endo@t-online.de>
Cc: gcc-rust@gcc.gnu.org, debian-superh@lists.debian.org,
	"j-core@lists.j-core.org" <j-core@lists.j-core.org>
Subject: Re: Test results for gccrs on Debian unstable sh4
Date: Fri, 11 Jun 2021 14:31:06 +0200	[thread overview]
Message-ID: <9d45f9e6-d0ef-d423-98f8-5c2fd67d15ad@physik.fu-berlin.de> (raw)
In-Reply-To: <CAB2u+n3zVYogdzM_W-CON0CwgbQguHdKX_KgrYAc2WZnrRAiyw@mail.gmail.com>

Hi Philip!

On 6/11/21 1:25 PM, Philip Herron wrote:
>> Nice! Thanks for your efforts, Adrian!
>>
> 
> This is pretty neat, what was it like to compile GCC on that board?

It's an older board made in the early 2000s, so it has only 600 MHz which meant
building gccrs took a little longer. It's the same architecture as used in the
Sega Saturn and Sega Dreamcast.

FWIW, the J-Core project is working on open source reimplementations of the SuperH
architecture which is why this architecture still has a future despite Hitachi/Renesas
having lost interest in favor of ARM.

Adrian

-- 
 .''`.  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

      reply	other threads:[~2021-06-11 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 13:49 John Paul Adrian Glaubitz
2021-06-10  1:46 ` Oleg Endo
2021-06-11 11:25   ` Philip Herron
2021-06-11 12:31     ` 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=9d45f9e6-d0ef-d423-98f8-5c2fd67d15ad@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-superh@lists.debian.org \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=j-core@lists.j-core.org \
    --cc=oleg.endo@t-online.de \
    --cc=philip.herron@embecosm.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).