---

Hi all,

The reason for my most recent question on the list was that I was investigating if gccgo targeting aarch64 would work. It turns out that it's really close (to building and working for trivial programs, at least): it depends on libatomic which explicitly does not support AArch64, but when you try to build it, it appears to work fine. Hence this patch.

Would it be possible for someone to:

a) test this for me, or b) explain to me how to test it myself, and/or c) send this upstream, or d) offer advice on how to get it upstream myself?

I'd sort of prefer the "explain to me" versions as I also want to run the gccgo/libgo tests :)

If someone knows why libatomic unsupports aarch64, that'd be even better (maybe it's just that the sync intrinsics it uses weren't supported by gcc on aarch64 at the time?).

Cheers, mwh

libatomic/configure.tgt | 5 ----- 1 file changed, 5 deletions(-)

diff --git a/libatomic/configure.tgt b/libatomic/configure.tgt index b9e5d6c..7eaab38 100644 --- a/libatomic/configure.tgt +++ b/libatomic/configure.tgt @@ -95,11 +95,6 @@ fi

# Other system configury case "${target}" in - aarch64*) - # This is currently not supported in AArch64. - UNSUPPORTED=1 - ;; - arm*-*-linux*) # OS support for atomic primitives. config_path="${config_path} linux/arm posix"