public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pedretti.fabio at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/97368] New: randomly build failure for mesa with lto on armhf
Date: Sun, 11 Oct 2020 13:17:00 +0000 [thread overview]
Message-ID: <bug-97368-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97368
Bug ID: 97368
Summary: randomly build failure for mesa with lto on armhf
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: pedretti.fabio at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
When building mesa git (actually on b7d16a) I get randomly build failures on
armhf.
gcc is the one currently on Ubuntu groovy (10.2.0-13ubuntu1).
I don't get this build error with gcc 9, or on other architectures (amd64 arm64
i386 ppc64el s390x) even with the same gcc 10.
This is the actual error:
during RTL pass: reload
../src/compiler/nir/nir_loop_analyze.h: In function ‘contains_other_jump’:
../src/compiler/nir/nir_loop_analyze.h:71:1: internal compiler error:
Segmentation fault
71 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions.
lto-wrapper: fatal error: c++ returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
Full build log here:
https://launchpadlibrarian.net/501568575/buildlog_ubuntu-groovy-armhf.mesa_20.3~git2010110730.b7d16a~oibaf~g_BUILDING.txt.gz
next reply other threads:[~2020-10-11 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 13:17 pedretti.fabio at gmail dot com [this message]
2020-10-11 13:51 ` [Bug c/97368] " pedretti.fabio at gmail dot com
2020-10-11 14:03 ` pedretti.fabio at gmail dot com
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=bug-97368-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).