From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: gcc-rust@gcc.gnu.org
Subject: Test results for gccrs on Debian unstable ppc64 (big-endian)
Date: Wed, 2 Jun 2021 14:49:35 +0200 [thread overview]
Message-ID: <9c7c39ea-1cc1-2218-f469-f02cbcaa484f@physik.fu-berlin.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Hi!
Trying to build revision fd9e53249c6c269e68f9aca71b3d17b3ecee8e8a on 64-bit
PowerPC (big-endian) succeeds. The testsuite passes without any issues.
Attaching the log file, quick summary below:
=== 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 /home/glaubitz/gccrs/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/compile.exp ...
Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/torture/compile.exp ...
Running /home/glaubitz/gccrs/gcc/testsuite/rust/compile/xfail/xfail.exp ...
Running /home/glaubitz/gccrs/gcc/testsuite/rust/execute/torture/execute.exp ...
=== rust Summary ===
# of expected passes 2368
# of expected failures 26
make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
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
[-- Attachment #2: rust-ppc64.log.gz --]
[-- Type: application/gzip, Size: 56004 bytes --]
reply other threads:[~2021-06-02 12:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9c7c39ea-1cc1-2218-f469-f02cbcaa484f@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=gcc-rust@gcc.gnu.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).