From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: gcc-rust@gcc.gnu.org
Cc: debian-superh@lists.debian.org,
"j-core@lists.j-core.org" <j-core@lists.j-core.org>
Subject: Test results for gccrs on Debian unstable sh4
Date: Wed, 9 Jun 2021 15:49:48 +0200 [thread overview]
Message-ID: <4927f8d2-2259-b4c8-fb2d-722aa59727e1@physik.fu-berlin.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
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'
--
.''`. 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
[-- Attachment #2: rust-sh4.log.gz --]
[-- Type: application/gzip, Size: 59641 bytes --]
next reply other threads:[~2021-06-09 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 13:49 John Paul Adrian Glaubitz [this message]
2021-06-10 1:46 ` Oleg Endo
2021-06-11 11:25 ` Philip Herron
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=4927f8d2-2259-b4c8-fb2d-722aa59727e1@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 \
/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).