Hi,
> http://build-failures.rhaalovely.net/powerpc/2019-09-17/net/fastnetmon.log
Upstream introduced since 1.1.4 a cmake flag allowing the use of
__atomic* functions instead of unsupported __sync* ones.
Once provided, it builds fine on macppc [0]. I have not bumped
REVISION, it never had a pack
On 2019-10-06, Charlene Wendling wrote:
> Upstream introduced since 1.1.4 a cmake flag allowing the use of
> __atomic* functions instead of unsupported __sync* ones.
>
> Once provided, it builds fine on macppc [0]. I have not bumped
> REVISION, it never had a package built before that.
I admit
On Mon, 7 Oct 2019 15:50:14 - (UTC)
Christian Weisgerber wrote:
> On 2019-10-06, Charlene Wendling wrote:
>
> > Upstream introduced since 1.1.4 a cmake flag allowing the use of
> > __atomic* functions instead of unsupported __sync* ones.
> >
> > Once provided, it builds fine on macppc [0].
On 2019-10-07, Charlene Wendling wrote:
>> I admit I haven't followed the subject of __atomic* at all.
>> What's the reason to enable the use of these primitives only for
>> powerpc/hppa and not on all archs?
>
> GCC has no 64-bits __sync* operators support on macppc and hppa, the
> newer __atomi
On Tue, 8 Oct 2019 20:21:37 - (UTC)
Christian Weisgerber wrote:
[...]
> More generally, I assume if an arch supports (1) 64-bit __sync*
> primitives and (2) __atomic* primitives, then it will also have
> 64-bit __atomic*.
>
> > +# Use __atomic* function instead of __sync* ones, allowing to
