Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Mar 2020 04:20:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        ppc@FreeBSD.org
Subject:   [Bug 225629] powerpc64 (POWER9) segfaults randomly (e.g., building lang/gcc5)
Message-ID:  <bug-225629-21-AQqnHlSkkU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-225629-21@https.bugs.freebsd.org/bugzilla/>
References:  <bug-225629-21@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225629

--- Comment #27 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Mark Linimon from comment #26)

It may be too many things were run into to
identify a "this problem" and too much context
has changed. For example, it started with
a report that had:

insn-extract.c: In function 'void insn_extract(rtx_insn*)':
insn-extract.c:3006: internal compiler error: internal consistency failure
Please submit a full bug report,
. . .

(not a SIGSEGV initially). There was evidence reported of:

pid 5555 (gmake), uid 0: exited on signal 11 (core dumped)
pid 5540 (gmake), uid 0: exited on signal 11 (core dumped)
pid 5530 (gmake), uid 0: exited on signal 6 (core dumped)
pid 5529 (sh), uid 0: exited on signal 11 (core dumped)
pid 3052 (make), uid 0: exited on signal 11 (core dumped)
pid 612 (sshd), uid 0: exited on signal 11
pid 671 (getty), uid 0: exited on signal 11 (core dumped)

(Those sure do not look like a compiler failing to run
to me.)

There was the vec_step issue. And so on.

Both gcc5 and gcc6 are gone, as is the system gcc 4.2.1
(on head). At least head has progressed to a different
powerpc64 ABI and an official llvm toolchain.

If there is anything still relevant here, it might only
be for FreeBSD 11 or 12 just due to the large context
difference for head's powerpc64.

It looks too complicated to sort out and a new submittal
of material might be better (if there is a need).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225629-21-AQqnHlSkkU>