From: Greg Hogan <code@greghogan.com>
To: Andreas Enge <andreas@enge.fr>
Cc: 74216-done@debbugs.gnu.org,
Sharlatan Hellseher <sharlatanus@gmail.com>,
bavier@posteo.net
Subject: bug#74216: [science team] flint build failure
Date: Tue, 12 Nov 2024 14:19:10 -0500 [thread overview]
Message-ID: <CA+3U0Zky_2VTJBu4KJ3SMy7TZhTVJdjbLpO+WqGEkU6BbRU1LQ@mail.gmail.com> (raw)
In-Reply-To: <ZzNfnK4Y3TiAUAE8@jurong>
On Tue, Nov 12, 2024 at 9:01 AM Andreas Enge <andreas@enge.fr> wrote:
>
> Hello Greg,
>
> Am Tue, Nov 05, 2024 at 03:43:31PM -0500 schrieb Greg Hogan:
> > flint fails to build for me with the following error unless I include
> > as an input a newer gcc version.
>
> out of curiosity, what is your exact build architecture and processor
> line? The package builds without problems on my rather old laptop, and
> on the Guix build farms.
AWS r7a, AMD EPYC (4th Gen) 9R14
> I have asked someone who knows the flint code well, and they said it
> means that gcc has trouble realising how to expand the assembly code
> into load and stores and computation on machines with less than 8
> registers. Apparently it is a combination of compiler versions and
> processor specifics.
>
> Apart from that, I think we can apply your patch without worries, but
> I am just curious about what is happening.
>
> What is mildly worrying is that we already use the "--disable-assembly"
> configure flag; this could be a bug in the flint configuration.
>
> Andreas
Thanks for investigating this issue and pointing me in the right
direction. Turns out the flint package builds successfully when
upgrading GCC from 11.4 to 11.5. It looks like the processor was too
new.
When considering reproducible builds, this is a bug when building on
future, unknown hardware. For a time-bomb we can set back the clock,
and here we would need processor emulation?
Marking as done since the fix is to update a core package.
Greg
prev parent reply other threads:[~2024-11-12 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 20:43 bug#74216: [science team] flint build failure Greg Hogan
2024-11-05 20:47 ` bug#74216: [PATCH science-team] gnu: flint: Update gcc version Greg Hogan
2024-11-12 14:01 ` bug#74216: [science team] flint build failure Andreas Enge
2024-11-12 19:19 ` Greg Hogan [this message]
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=CA+3U0Zky_2VTJBu4KJ3SMy7TZhTVJdjbLpO+WqGEkU6BbRU1LQ@mail.gmail.com \
--to=code@greghogan.com \
--cc=74216-done@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=bavier@posteo.net \
--cc=sharlatanus@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.