From: Philip Herron <philip.herron@embecosm.com>
To: Oleg Endo <oleg.endo@t-online.de>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
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 12:25:02 +0100 [thread overview]
Message-ID: <CAB2u+n3zVYogdzM_W-CON0CwgbQguHdKX_KgrYAc2WZnrRAiyw@mail.gmail.com> (raw)
In-Reply-To: <f1c21d4d5bb7cc1471148792943a5ced57805872.camel@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
On Thu, 10 Jun 2021 at 02:49, Oleg Endo <oleg.endo@t-online.de> wrote:
> On Wed, 2021-06-09 at 15:49 +0200, John Paul Adrian Glaubitz wrote:
> > Hi!
> >
> > Just built revision ff4715d79e2c17d270db8b94315aa6b574f48994 on Debian
> unstable sh4
> > (SuperH) on my Renesas SH-7785LCR evaluation board.
> >
> > Testsuite passes without any issues, attaching the full log.
> >
> > CC'ing two SuperH-related mailing list in case someone is interested.
> >
> > Adrian
> > === rust tests ===
> >
> > Schedule of variations:
> > unix
> >
> > Running target unix
> > Using /usr/share/dejagnu/baseboards/unix.exp as board description file
> for target.
> > Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> target.
> > Using /srv/glaubitz/gccrs/gcc/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> > Running /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ...
> > Running
> /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ...
> > Running /srv/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp
> ...
> > Running
> /srv/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ...
> >
> > === rust Summary ===
> >
> > # of expected passes 2415
> > # of expected failures 15
> > make[2]: Leaving directory '/srv/glaubitz/gccrs/build/gcc'
> > make[1]: Leaving directory '/srv/glaubitz/gccrs/build/gcc'
> >
>
>
> Nice! Thanks for your efforts, Adrian!
>
> Cheers,
> Oleg
>
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust
This is pretty neat, what was it like to compile GCC on that board?
--Phil
[-- Attachment #2: Type: text/html, Size: 2389 bytes --]
next prev parent reply other threads:[~2021-06-11 11:25 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 [this message]
2021-06-11 12:31 ` 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=CAB2u+n3zVYogdzM_W-CON0CwgbQguHdKX_KgrYAc2WZnrRAiyw@mail.gmail.com \
--to=philip.herron@embecosm.com \
--cc=debian-superh@lists.debian.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=j-core@lists.j-core.org \
--cc=oleg.endo@t-online.de \
/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).