Bug 582910 – x11-drivers/xf86-video-intel-2.99.917_p20160507 - .../work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2044:1: error: inlining failed in call to always_inline 'emit_span_vertex': target specific option mismatch

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Pavel Kozlov 2016-05-13 13:29:19 UTC]

Created attachment 434180 [details]
emerge --info

I am trying to merge latest version of xf86-video-intel with USE="sna".

> [ebuild   R   ~] x11-drivers/xf86-video-intel-2.99.917_p20160507::gentoo  USE="dri dri3 sna* udev uxa -debug -xvmc" 0 KiB

It fails with the following error message.

> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c: In function 'emit_span_primitive':
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2044:1: error: inlining failed in call to always_inline 'emit_span_vertex': target specific option mismatch
 emit_span_vertex(struct sna *sna,
 ^
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2058:2: error: called from here
  emit_span_vertex(sna, op, box->x2, box->y2);
  ^
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2044:1: error: inlining failed in call to always_inline 'emit_span_vertex': target specific option mismatch
 emit_span_vertex(struct sna *sna,
 ^
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2061:2: error: called from here
  emit_span_vertex(sna, op, box->x1, box->y2);
  ^
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2044:1: error: inlining failed in call to always_inline 'emit_span_vertex': target specific option mismatch
 emit_span_vertex(struct sna *sna,
 ^
> /var/tmp/portage/x11-drivers/xf86-video-intel-2.99.917_p20160507/work/88733a7874f7c9b45da5d612802947a9de12893a/src/sna/gen4_vertex.c:2064:2: error: called from here
  emit_span_vertex(sna, op, box->x1, box->y1);
  ^

[Comment 1 Pavel Kozlov 2016-05-13 13:30:08 UTC]

Created attachment 434182 [details]
build log

[Comment 2 Pavel Kozlov 2016-06-28 14:55:58 UTC]

Still reproducible for version 2.99.917_p20160621

[Comment 3 Chí-Thanh Christopher Nguyễn 2016-06-28 15:53:22 UTC]

> CFLAGS="-Os -pipe -march=native"

What if you change this to -O2 and/or -march=haswell ?

[Comment 4 Pavel Kozlov 2016-06-29 10:04:24 UTC]

Compiled with options -O2.
Wow. So it is the only package (in my system) which is broken (not with all USE flags) with -Os. I prefer -Os because I have SSD with limited free space.

Is it possible to force one package in ebuild to build always with -O2 (no matter what are MAKEOPTS ?) Firefox is built that way as far as I remember, if I am not wrong.

Or better to just add this package to /etc/portage/package.env ?

[Comment 5 Chí-Thanh Christopher Nguyễn 2016-06-29 11:47:05 UTC]

-Os does occasionally cause breakage.

To work around this issue, we can inherit flag-o-matic and call replace-flags -Os -O2

But reporting the problem upstream so it can be addressed there is probably necessary.

[Comment 6 Rémi Cardona (RETIRED) 2016-06-29 20:46:56 UTC]

(In reply to Pavel Kozlov from comment #4)
> I prefer -Os because I have SSD with limited free space.

FYI, there are known cases where -Os actually creates bigger binaries than -O2.  The space savings are usually not worth the trouble one usually has with -Os, though the situation is much better than it was with older versions of gcc.

[Comment 7 Matthew Thode ( prometheanfire ) 2016-09-19 02:03:37 UTC]

guess I'm going to change to -O2 as well...

[Comment 8 Matthew Thode ( prometheanfire ) 2016-09-19 02:04:31 UTC]

also, 2.99.917_p20160829 is effected.

[Comment 9 Rick Farina (Zero_Chaos) 2016-09-20 02:12:13 UTC]

not really sure why no one else could do this, but I added flag-o-matic and replace-flags to the latest stable and testing to stop the breakage.  thanks for the report, I'll leave this bug open in case someone wants to send it upstream.

[Comment 10 Chí-Thanh Christopher Nguyễn 2016-09-20 09:10:32 UTC]

We were waiting for someone who sees this problem to report it upstream, so upstream can comment on the correct way to address this issue.

[Comment 11 Matt Turner 2017-01-29 18:19:39 UTC]

Please try the unstable version 2.99.917_p20161206 and report back.