On Mon, 22 Aug 2022 at 20:25:54 -0400, Jeremy Bicha wrote:
> mozjs102 fails to build on armhf
...
> In function ‘uint64_t js::jit::AtomicCmpXchg64SeqCst(uint64_t*,
> uint64_t, uint64_t)’,
> inlined from ‘static T
> js::jit::AtomicOperations::fetchAndSeqCst(T*, T) [with T = long long
> int]’ at
> /<<PKGBUILDDIR>>/js/src/jit/shared/AtomicOperations-shared-jit.h:337:1,
> inlined from ‘static T
> js::jit::AtomicOperations::fetchAndSeqCst(SharedMem<T*>, T) [with T =
> long long int]’ at
> /<<PKGBUILDDIR>>/js/src/jit/AtomicOperations.h:212:26,
> inlined from ‘virtual bool
> cls_testAtomicOperationsI64::run(JS::HandleObject)’ at
> /<<PKGBUILDDIR>>/js/src/jsapi-tests/testAtomicOperations.cpp:223:3:
> /<<PKGBUILDDIR>>/debian/build/js/src/jit/AtomicOperationsGenerated.h:240:17:
> error: ‘asm’ operand has impossible constraints
> 240 | asm volatile (
I'm doing a build on amdahl to get the contents of the generated header,
but it's going to take a while to get there.
The firefox source package is basically the same codebase and it compiled
successfully on armhf, which might be a useful data point?
smcv
