Summary: | www-client/firefox-45.2.0 - /usr/lib/gcc/hppa2.0-unknown-linux-gnu/4.9.3/include/g++-v4/bits/atomic_base.h:618: undefined reference to `__atomic_fetch_add_8' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | hppa |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | HPPA | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 585308 | ||
Attachments: | www-client:firefox-45.2.0:20160704-074500.log.xz |
Description
Jeroen Roovers (RETIRED)
2016-07-05 06:47:13 UTC
Is this a regression over 45.1? I didn't think the headers for spidermonkey's atomics changed any between 45.1 and 45.2.. (In reply to Ian Stakenvicius from comment #1) > Is this a regression over 45.1? I don't see a 45.1 ebuild and I never tried one on HPPA. RIGHT.. I forgot that this is the first 45.x series that received a stablereq. OK, so FYI upstream starting with 44.0 or so have essentially made jit a hard requirement -- the only way to build "working" code with it disabled is if all of the atomic operations are implemented for each platform. If jit works, then upstream already contains such code (which means amd64/x86/arm/arm64 are covered), and ppc/ppc64 do not have jit but do have workaround implementations in place. The rest (hppa, ia64, alpha, etc) need implementations. Given this is a non-trivial amount of work we may need to drop keywords on hppa and the other arches until someone with the time/energy/massochistic desire can implement the atomic ops. :/ Dropped HPPA keywording entirely. ~hppa keyword re-appeared in www-client/firefox-48.0 :) . |