* Florian Weimer:
> * Bin Cheng via Gcc:
>
>> Last question is why do we have __aarch64_have_lse_atomics(and some
>> other symbols) in both libgcc and glibc?
>>
>> #objdump -t /usr/lib64/libc.so.6 | grep "__aarch64_ldadd"
>>
>> 00111460 l F .text 0030
>> __aarch64_ldadd8_a
On Thu, Sep 17, 2020 at 12:56:59PM +0200, Florian Weimer via Gcc wrote:
> * Bin Cheng via Gcc:
>
> > Last question is why do we have __aarch64_have_lse_atomics(and some
> > other symbols) in both libgcc and glibc?
> >
> > #objdump -t /usr/lib64/libc.so.6 | grep "__aarch64_ldadd"
> >
> > 00
* Bin Cheng via Gcc:
> Last question is why do we have __aarch64_have_lse_atomics(and some
> other symbols) in both libgcc and glibc?
>
> #objdump -t /usr/lib64/libc.so.6 | grep "__aarch64_ldadd"
>
> 00111460 l F .text 0030
> __aarch64_ldadd8_acq
>
> 00111370 l
Hi,
Compiling below program:
#define STREAM_ARRAY_SIZE (1107296256)
double a[STREAM_ARRAY_SIZE],
b[STREAM_ARRAY_SIZE],
c[STREAM_ARRAY_SIZE];
typedef struct {
volatile int locked;
} spinlock_t;
volatile int cnt32=0;
volatile long cnt64=0;
void atom(){
__atomic_fetch_add(&cnt32,
