> On Wed, 2020-07-29 at 14:13 +0100, sergio(a)serjux.com wrote:
> In general I want to have a very good
> indicator the issue is LTO related before I
> disable. THe build you referenced doesn't have any good indicators that LTO
> is
> the problem.
>
> For ppc64le is that the build was done with
On 31.07.2020 19:15, Jeff Law wrote:
> Umm, those builds look fine -- I don't see any failures in those builds.
Switching to GCC fixed these issues.
> I would not generally recommend switching compilers to work around issues of
> any
> kind.
I used Clang only as a workaround to issue with
On Thu, 2020-07-30 at 10:54 +0200, Vitaly Zaitsev via devel wrote:
> On 29.07.2020 15:59, Jeff Law wrote:
> > In general I want to have a very good indicator the issue is LTO related
> > before I
> > disable. THe build you referenced doesn't have any good indicators that
> > LTO is
> > the
On Thu, Jul 30, 2020 at 10:24:50AM -0500, Steven Munroe wrote:
> > For targets which do support the target attribute, each
> > function should be marked with the right set of options
> > before streaming it,
>
> Looking at the source (opencv 4.3.0) I can not find any usage of
> __attribute__
Jakub Jelinek writes:
> For targets which do support the target attribute, each
> function should be marked with the right set of options
> before streaming it,
Looking at the source (opencv 4.3.0) I can not find any usage of
__attribute__ ((target)) or #pragma ... optimization associated with
On Thu, Jul 30, 2020 at 09:02:43AM -0500, Steven Munroe wrote:
> Sergio writes:
>
> > Hello opencv [1] build also failed around LTO
>
> Looking at the build logs:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=48055082
>
> For the build.log that ends with:
>
> lto1: error:
Sergio writes:
> Hello opencv [1] build also failed around LTO
Looking at the build logs:
https://koji.fedoraproject.org/koji/taskinfo?taskID=48055082
For the build.log that ends with:
lto1: error: '__builtin_altivec_vadub' requires the '-mcpu=power9' option
lto1: fatal error: target specific
On 29.07.2020 15:59, Jeff Law wrote:
> In general I want to have a very good indicator the issue is LTO related
> before I
> disable. THe build you referenced doesn't have any good indicators that LTO
> is
> the problem.
My packages nheko and mtxclient are failed due to LTO. Can you check
On Wed, 2020-07-29 at 20:39 +0100, Sérgio Basto wrote:
> On Wed, 2020-07-29 at 12:19 -0500, Steven Munroe wrote:
> > Jeff Law wrote:
> >
> > > For ppc64le is that the build was done with p8, but there is one
> > > function (__builtin_altivec_vadub) that requires p9. This seems
> > > like a
On Wed, 2020-07-29 at 12:19 -0500, Steven Munroe wrote:
> Jeff Law wrote:
>
> > For ppc64le is that the build was done with p8, but there is one
> > function (__builtin_altivec_vadub) that requires p9. This seems
> > like a package bug at first glance, not an LTO issue.
>
> Yup
Jeff Law wrote:
> For ppc64le is that the build was done with p8, but there is one
> function (__builtin_altivec_vadub) that requires p9. This seems
> like a package bug at first glance, not an LTO issue.
Yup __builtin_altivec_vadub is POWER9_VECTOR only.
For P8/6 use something like this:
Law
> > Date: Jul 27 2020 22:46:22 +
> > Subject: Disable LTO for now
> >
> >
> > ---
> >
> > diff --git a/apt.spec b/apt.spec
> > index a555b62..282ddc8 100644
> > --- a/apt.spec
> > +++ b/apt.spec
> > @@ -14,7 +14,7
On Wed, 2020-07-29 at 14:13 +0100, ser...@serjux.com wrote:
> Hello opencv [1] build also failed around LTO
> What is your advise ? What is your advice?
In general I want to have a very good indicator the issue is LTO related before
I
disable. THe build you referenced doesn't have any good
f4bac7efd3c251ffb64107bc2f522c1d3c829b5c Mon Sep 17 00:00:00 2001
From: Jeff Law
Date: Jul 27 2020 22:46:22 +
Subject: Disable LTO for now
---
diff --git a/apt.spec b/apt.spec
index a555b62..282ddc8 100644
--- a/apt.spec
+++ b/apt.spec
@@ -14,7 +14,7 @@
Name: apt
Version:2.1.7
14 matches
Mail list logo
