From: Philip Herron <philip.herron@embecosm.com>
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 aarch64
Date: Thu, 3 Jun 2021 13:10:36 +0100 [thread overview]
Message-ID: <CAB2u+n05kjUZDQby8fRZSZwfecZZ9E7z9ixZE5u2s-sTCmtN8Q@mail.gmail.com> (raw)
In-Reply-To: <adf57084-4fc2-8690-5c04-0f2cf482820e@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]
That's likely a better solution. In fact, I started looking at that a while
back, but I haven't test/finished it:
```
language: c
arch:
- amd64
- ppc64le
- s390x
- arm64
os: linux
before_install:
- sudo apt-get install -y automake autoconf libtool autogen bison flex
libgmp3-dev libmpfr-dev libmpc-dev build-essential gcc-multilib
g++-multilib dejagnu
script:
- mkdir -p gccrs-build;
- cd gccrs-build; ../configure --enable-languages=rust
--disable-bootstrap --enable-multilib; make -j $(nproc); make check-rust
- cd gccrs-build; \
if grep "# of unexpected" gcc/testsuite/rust/rust.sum;\
then \
echo "some tests are not correct"; \
exit 1; \
else \
exit 0; \
fi
```
I might make an issue out of this, in the hopes someone can test and fix up
this initial travis.yml.
--Phil
On Thu, 3 Jun 2021 at 13:05, John Paul Adrian Glaubitz <
glaubitz@physik.fu-berlin.de> wrote:
> Hi Phil!
>
> On 6/3/21 1:58 PM, Philip Herron wrote:
> > I just had a thought it would be nice if we could keep a matrix of
> > different platforms gccrs has been tested on, and they could have states
> of:
> >
> > 1. Build Failure
> > 2. Test Failures link to log
> > 3. Tests pass, no unexpected results
> >
> > What if we maintained a section in the wiki for this?
> Sounds like a great idea. I think another idea would be to set up Travis
> which
> has support for a couple of architectures such as aarch64 and ppc64le.
>
> I'm not planning to keep repeating this manual build and testsuite runs,
> but I
> just want to get familiar with the project and fix some minor portability
> issues
> while I'm at it.
>
> I'm also particularly interested to see how well gccrs already works on
> various
> architectures. Getting Rust to work on more targets is very important for
> Debian
> as we have some architectures which are currently falling behind due to
> the lack
> of platform support in rustc.
>
> 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: Type: text/html, Size: 3001 bytes --]
next prev parent reply other threads:[~2021-06-03 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 11:28 John Paul Adrian Glaubitz
2021-06-03 11:58 ` Philip Herron
2021-06-03 12:05 ` John Paul Adrian Glaubitz
2021-06-03 12:10 ` Philip Herron [this message]
2021-06-03 19:05 ` Mark Wielaard
2021-06-03 22:16 ` 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=CAB2u+n05kjUZDQby8fRZSZwfecZZ9E7z9ixZE5u2s-sTCmtN8Q@mail.gmail.com \
--to=philip.herron@embecosm.com \
--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).