unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [aarch64] sbcl build failure
Date: Wed, 31 Mar 2021 01:26:20 -0400	[thread overview]
Message-ID: <YGQH/NzvQl0IXMkN@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=oY9OsjByWRKsc=3hH-Lpi4sR9qBk0mBQ70kKLBhLihtA@mail.gmail.com>

On Wed, Mar 31, 2021 at 12:15:01AM +0200, Vincent Legoll wrote:
> I'm looking at the following cl-zstd build failure:
> https://ci.guix.gnu.org/build/133326/details
> which is caused by sbcl build failure that I
> reproduced locally.

During the recent staging cycle, I noticed a huge number of SBCL build
failures, especially when emulating aarch64 on x86_64.
 
> I diffed the CI build log output with my local
> attempt and got the same thing modulo timings
> [1] and other harmless stuff.
> 
> [1] the Odroid N2 looks roughly 3x faster than the CI
> on this specific build / test (total 30 mins vs 90).

If it was an emulated build, that's more or less expected. The emulation
is very slow.

Comparing the Overdrive 1000 (4 x Cortex-A57, 25 watts TDP) to the
Odroid N2 (4 x Cortex-A73 and 2 x Cortex-A53, only 5 watts TDP), I'd
guess the Overdrive will complete the compilation more quickly, despite
the older design and lower core count.

I'm retrying the build now on one of the Overdrives.


  reply	other threads:[~2021-03-31  5:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 22:15 [aarch64] sbcl build failure Vincent Legoll
2021-03-31  5:26 ` Leo Famulari [this message]
2021-03-31 15:29   ` Leo Famulari
2021-03-31 15:54     ` Pierre Neidhardt

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YGQH/NzvQl0IXMkN@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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://git.savannah.gnu.org/cgit/guix.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).