From: Marc <dkm@kataplop.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: Test results for gccrs on Debian unstable s390x
Date: Wed, 02 Jun 2021 22:13:01 +0200 [thread overview]
Message-ID: <87fsy0yqia.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <f5e6c1e5-8656-b8bc-eb7d-056a4bf5a280@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Wed, 2 Jun 2021 21:48:39 +0200")
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
> Hello!
>
> Just built gccrs revision 59b417323b25072aff2662f1f54f417f7b7ded61 on Debian unstable s390x.
>
> The testsuite fails with the following failures. Attaching the log file.
>
> Adrian
Hi again!
looks like all errors here (ICE) are the same as seen on 32-bits
debian, see https://github.com/Rust-GCC/gccrs/issues/467 .
Thanks for these tests!
Marc
next prev parent reply other threads:[~2021-06-02 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 19:48 John Paul Adrian Glaubitz
2021-06-02 20:13 ` Marc [this message]
2021-08-08 7:03 ` John Paul Adrian Glaubitz
2021-08-08 12:01 ` Mark Wielaard
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=87fsy0yqia.fsf@arrakis.kataplop.net \
--to=dkm@kataplop.net \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.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).