From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: gcc-rust@gcc.gnu.org
Subject: Test results for gccrs on Debian unstable ia64
Date: Wed, 2 Jun 2021 13:27:03 +0200 [thread overview]
Message-ID: <478d9956-a97f-5da2-b684-31d791c54fa3@physik.fu-berlin.de> (raw)
Hi!
I have started to test gccrs on various targets supported by Debian to see if
there are any portability issues with the code. The first target I have tested
is Debian unstable ia64.
I tested revision fd9e53249c6c269e68f9aca71b3d17b3ecee8e8a.
The code builds without any obvious issues and I was able to run the testsuite
with the following results:
=== 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.test/compile/compile.exp ...
Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/execute/execute.exp ...
FAIL: rust.test/execute/block_expr1.rs -O0 execution test
FAIL: rust.test/execute/block_expr1.rs -O1 execution test
FAIL: rust.test/execute/block_expr1.rs -O2 execution test
FAIL: rust.test/execute/block_expr1.rs -O3 -g execution test
FAIL: rust.test/execute/block_expr1.rs -Os execution test
FAIL: rust.test/execute/block_expr1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: rust.test/execute/block_expr1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
FAIL: rust.test/execute/empty_main.rs -O0 execution test
FAIL: rust.test/execute/empty_main.rs -O1 execution test
FAIL: rust.test/execute/empty_main.rs -O2 execution test
FAIL: rust.test/execute/empty_main.rs -O3 -g execution test
FAIL: rust.test/execute/empty_main.rs -Os execution test
FAIL: rust.test/execute/empty_main.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: rust.test/execute/empty_main.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
FAIL: rust.test/execute/func1.rs -O0 execution test
FAIL: rust.test/execute/func1.rs -O1 execution test
FAIL: rust.test/execute/func1.rs -O2 execution test
FAIL: rust.test/execute/func1.rs -O3 -g execution test
FAIL: rust.test/execute/func1.rs -Os execution test
FAIL: rust.test/execute/func1.rs -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
FAIL: rust.test/execute/func1.rs -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/unsupported/unsupported.exp ...
Running /home/glaubitz/gccrs/gcc/testsuite/rust.test/xfail_compile/xfail_compile.exp ...
=== rust Summary ===
# of expected passes 2347
# of unexpected failures 21
# of expected failures 26
make[2]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
make[1]: Leaving directory '/home/glaubitz/gccrs/build/gcc'
I will test on more targets throughout the next days.
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
next reply other threads:[~2021-06-02 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 11:27 John Paul Adrian Glaubitz [this message]
2021-06-02 12:41 ` Marc
2021-06-02 12:47 ` John Paul Adrian Glaubitz
2021-06-02 13:05 ` Marc
2021-06-02 13:08 ` John Paul Adrian Glaubitz
2021-06-02 16:14 ` John Paul Adrian Glaubitz
2021-06-02 16:58 ` Marc
2021-06-02 17:00 ` John Paul Adrian Glaubitz
2021-06-02 17:02 ` Marc
2021-06-02 20:39 ` 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=478d9956-a97f-5da2-b684-31d791c54fa3@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).