10:38 a.m.
I thought the gcc 12 related issues with ppc64le had been fixed but perhaps
not in all cases?
On the original rebuild[1] two tests failed (segfaulting) but on my latest
attempt with the new gcc 12 build[2] I now have 3 tests segfaulting.
Thanks,
Richard
[1] https://kojipkgs.fedoraproject.org//work/tasks/5159/81985159/build.log
[2] https://kojipkgs.fedoraproject.org//work/tasks/7933/82147933/build.log
10:39 a.m.
On Sun, Jan 30, 2022 at 9:38 AM Richard Shaw <hobbes1069(a)gmail.com> wrote:
I thought the gcc 12 related issues with ppc64le had been fixed but
perhaps not in all cases?
On the original rebuild[1] two tests failed (segfaulting) but on my latest attempt with
the new gcc 12 build[2] I now have 3 tests segfaulting.
Did you ever figure this out? I have similar symptoms with the clisp
package: one test segfaults on ppc64le only. I experimented with
various build flags and found that adding -fno-inline-small-functions
makes the test pass. I haven't had time to dig into any further than
that yet.
--
Jerry James
http://www.jamezone.org/
10:52 a.m.
On Tue, Feb 1, 2022 at 10:40 AM Jerry James <loganjerry(a)gmail.com> wrote:
On Sun, Jan 30, 2022 at 9:38 AM Richard Shaw
<hobbes1069(a)gmail.com> wrote:
> I thought the gcc 12 related issues with ppc64le had been fixed but
perhaps not in all cases?
>
> On the original rebuild[1] two tests failed (segfaulting) but on my
latest attempt with the new gcc 12 build[2] I now have 3 tests segfaulting.
Did you ever figure this out? I have similar symptoms with the clisp
package: one test segfaults on ppc64le only. I experimented with
various build flags and found that adding -fno-inline-small-functions
makes the test pass. I haven't had time to dig into any further than
that yet.
No, I haven't tried building on one of the packager ppc boxes to
investigate further. Fighting other gcc 12 / python 3.10/3.11 issues :)
Did you add the flag for ppc64le only? I'll try and see if it fixes things
for me as well.
Thanks,
Richard
10:59 a.m.
On Tue, Feb 1, 2022 at 9:53 AM Richard Shaw <hobbes1069(a)gmail.com> wrote:
No, I haven't tried building on one of the packager ppc boxes to
investigate further. Fighting other gcc 12 / python 3.10/3.11 issues :)
Did you add the flag for ppc64le only? I'll try and see if it fixes things for me as
well.
Yes, for ppc64le only. The bigger hammer of -fno-inline-functions
also does the job. The challenge with clisp is that the sources are
written in Lisp, then converted to C and passed to the compiler, so
I'm looking at machine-generated C code rather than human-written C
code. Lots of fun. :-)
--
Jerry James
http://www.jamezone.org/
2:35 p.m.
What's the best way to modify the flags? I tried this but it bombed out...
%ifarch ppc64le
%global optflags "%{optflags} -fno-inline-small-functions"
%endif
Thanks,
Richard
2:41 p.m.
On Tue, 1 Feb 2022 14:35:52 -0600
Richard Shaw <hobbes1069(a)gmail.com> wrote:
What's the best way to modify the flags? I tried this but it
bombed out...
%ifarch ppc64le
%global optflags "%{optflags} -fno-inline-small-functions"
%endif
I believe you need to omit the quotes
Dan
815
days inactive
817
days old
6 comments
3 participants
participants (3)
-
Dan Horák -
Jerry James -
Richard Shaw