From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org
Subject: Re: Testsuite failures on ppc64, sparc64 and s390x (64-bit BE)
Date: Tue, 7 Jan 2020 00:33:49 +0100 [thread overview]
Message-ID: <4080b37c-5897-c58e-1741-ad18dfe3cb10@physik.fu-berlin.de> (raw)
In-Reply-To: <2ce6a111-73ac-d8ac-e3a9-25286423535f@virtuell-zuhause.de>
On 1/7/20 12:31 AM, Thomas Braun wrote:
> On 04.01.2020 21:58, brian m. carlson wrote:
>
>> I got rid of my UltraSPARC hardware when I last moved, so I won't be
>> looking into this further, but it seems unlikely to me that the problem
>> is in Git when the only non-Windows C change between the two versions is
>> a one-line file name change.
>>
>
> Just in case someone is interested. Last year I've created a QEMU image
> using MIPS big-endian hardware [1]. It is still on debian stretch and
> like **slow** but does not require additional hardware.
FWIW, the GCC compile farm is supposed to get a new beefy MIPS server
soon as well so I have been told.
But as mentioned earlier, there is already a SPARC T5 in the GCC compile
farm which is open to use for any open-source developer [1].
Adrian
> [1] https://gcc.gnu.org/wiki/CompileFarm
--
.''`. 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 prev parent reply other threads:[~2020-01-06 23:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 20:14 Testsuite failures on ppc64, sparc64 and s390x (64-bit BE) John Paul Adrian Glaubitz
2020-01-04 20:58 ` brian m. carlson
2020-01-04 21:07 ` John Paul Adrian Glaubitz
2020-01-06 23:31 ` Thomas Braun
2020-01-06 23:33 ` John Paul Adrian Glaubitz [this message]
2020-01-04 22:14 ` John Paul Adrian Glaubitz
2020-01-04 22:48 ` brian m. carlson
2020-01-04 23:13 ` John Paul Adrian Glaubitz
2020-02-09 0:58 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4080b37c-5897-c58e-1741-ad18dfe3cb10@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=thomas.braun@virtuell-zuhause.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).