Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 681928 - media-libs/zimg-2.7.5 - In file included from .../work/zimg-release-2.7.5/src/zimg/colorspace/x86/operation_impl_sse2.cpp:7:0: /usr/lib/gcc/i686-pc-linux-gnu/7.3.0/include/emmintrin.h:641:1: error: inlining failed in call to always_inline ‘__m128i _mm_...
Summary: media-libs/zimg-2.7.5 - In file included from .../work/zimg-release-2.7.5/src...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: Normal normal
Assignee: Gentoo Media-video project
URL:
Whiteboard:
Keywords:
Depends on: 821298
Blocks:
  Show dependency tree
 
Reported: 2019-03-28 14:22 UTC by Will Simoneau
Modified: 2023-05-26 09:52 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (einfo.txt,9.59 KB, text/plain)
2019-03-28 14:23 UTC, Will Simoneau 		Details
build log (build.log,103.36 KB, text/plain)
2019-03-28 14:23 UTC, Will Simoneau 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Will Simoneau 2019-03-28 14:22:07 UTC 
media-libs/zimg-2.7.5.ebuild uses CPU_FLAGS_X86="sse" to control the --{enable,disable}-x86simd flag passed to the configure script. This looks wrong even at face value: CPU_FLAGS_X86="sse" is supposed to control usage of SSE1 *only*.

On Pentium3 (CPU_FLAGS_X86="mmx mmxext sse"), this results in the build attempting to use SSE2 instructions even though the target does not support them.

Reproducible: Always

Steps to Reproduce:
Build media-libs/zimg-2.7.5 for an x86 target with >=SSE2 disabled.
Comment 1 Will Simoneau 2019-03-28 14:23:06 UTC 
Created attachment 571040 [details]
emerge --info
Comment 2 Will Simoneau 2019-03-28 14:23:41 UTC 
Created attachment 571042 [details]
build log
Comment 3 Pacho Ramos gentoo-dev 2019-04-19 17:15:52 UTC 
current stable also has this issue

what USE flag should be used instead ? :/
Comment 4 Will Simoneau 2019-04-22 13:25:11 UTC 
(In reply to Pacho Ramos from comment #3)
> current stable also has this issue
> 
> what USE flag should be used instead ? :/

Well, part of the problem is that the configure script only seems to provide an on/off flag:

  --disable-simd          Disable SIMD code. (default=no)