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:
vmin = vec_min (a, b); vmax = vec_max (a, b); result = vec_sub (vmax, vmin);
executes in 4 cycles.
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 __builtin_altivec_vadub is POWER9_VECTOR only.
For P8/6 use something like this:
vmin = vec_min (a, b); vmax = vec_max (a, b); result = vec_sub (vmax, vmin);
executes in 4 cycles.
but why it built 18 day ago, opencv-4.3.0-7 [2], with same source code and rpm spec [1] ?
[1] https://src.fedoraproject.org/rpms/opencv/commits/master
[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=47160403
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 package bug at first glance, not an LTO issue.
Yup __builtin_altivec_vadub is POWER9_VECTOR only.
For P8/6 use something like this:
vmin = vec_min (a, b); vmax = vec_max (a, b); result = vec_sub (vmax, vmin);
executes in 4 cycles.
but why it built 18 day ago, opencv-4.3.0-7 [2], with same source code and rpm spec [1] ?
All kinds of possibilities and speculating wouldn't be terribly helpful here. What remains is that there's code in there that requires p9, but the build is specifying p8 only and thus you get an error.
jeff
-
Jeff Law -
Steven Munroe -
Sérgio Basto