Closed Bug 1842933 Opened 2 years ago Closed 2 years ago

arm_neon.h:10357:1: error: inlining failed in call to ‘always_inline’ ‘vld1_u8’: target specific option mismatch

Categories

(Core :: Audio/Video, defect)

defect

Tracking

()

RESOLVED FIXED
117 Branch
Tracking Status
firefox-esr115 --- fixed
firefox115 --- wontfix
firefox116 --- wontfix
firefox117 --- fixed

People

(Reporter: glandium, Assigned: glandium)

Details

Attachments

(1 file)

When building with --with-system-libvpx, building for linux armhf fails with:

In file included from /<<PKGBUILDDIR>>/third_party/aom/aom_dsp/arm/blend_a64_mask_neon.c:12:
/usr/lib/gcc/arm-linux-gnueabihf/12/include/arm_neon.h: In function ‘load_u8_8x8’:
/usr/lib/gcc/arm-linux-gnueabihf/12/include/arm_neon.h:10357:1: error: inlining failed in call to ‘always_inline’ ‘vld1_u8’: target specific option mismatch
10357 | vld1_u8 (const uint8_t * __a)
      | ^~~~~~~
In file included from /<<PKGBUILDDIR>>/third_party/aom/aom_dsp/arm/blend_a64_mask_neon.c:19:
/<<PKGBUILDDIR>>/third_party/aom/av1/common/arm/mem_neon.h:52:9: note: called from here
   52 |   *s7 = vld1_u8(s);
      |         ^~~~~~~~~~
/usr/lib/gcc/arm-linux-gnueabihf/12/include/arm_neon.h:10357:1: error: inlining failed in call to ‘always_inline’ ‘vld1_u8’: target specific option mismatch
10357 | vld1_u8 (const uint8_t * __a)
      | ^~~~~~~
/<<PKGBUILDDIR>>/third_party/aom/av1/common/arm/mem_neon.h:50:9: note: called from here
   50 |   *s6 = vld1_u8(s);
      |         ^~~~~~~~~~

Back when libaom was added, VPX_ASFLAGS was more or less the only
variable that had the right set of flags for NEON support, which
justified its use. However, it's not set when building against system
libvpx.

Bug 1791482 improved things, though, and VPX_ASFLAGS, as far as NEON is
concerned, is now only re-exporting NEON_FLAGS, with the same caveat that
VPX_ASFLAGS is empty when building against system libvpx.

So we should use NEON_FLAGS instead of VPX_ASFLAGS.

Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/2cb4675f1ae9 Use NEON_FLAGS instead of VPX_ASFLAGS for libaom neon code. r=firefox-build-system-reviewers,andi

Comment on attachment 9343377 [details]
Bug 1842933 - Use NEON_FLAGS instead of VPX_ASFLAGS for libaom neon code.

ESR Uplift Approval Request

  • If this is not a sec:{high,crit} bug, please state case for ESR consideration: Build failure in some configurations (armhf linux with --with-system-libvpx)
  • User impact if declined: See above.
  • Fix Landed on Version: 117
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): NPOTB
Attachment #9343377 - Flags: approval-mozilla-esr115?
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch

Comment on attachment 9343377 [details]
Bug 1842933 - Use NEON_FLAGS instead of VPX_ASFLAGS for libaom neon code.

Approved for 115.1esr.

Attachment #9343377 - Flags: approval-mozilla-esr115? → approval-mozilla-esr115+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: