From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Frank Hunleth <fhunleth@troodon-software.com>
Cc: Will Newton <will.newton@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] erlang: support builds when gcc __atomic_* exist
Date: Wed, 28 Jul 2021 23:35:13 +0200 [thread overview]
Message-ID: <20210728233513.4097848b@windsurf> (raw)
In-Reply-To: <20210508222419.586915-1-fhunleth@troodon-software.com>
On Sat, 8 May 2021 18:24:19 -0400
Frank Hunleth <fhunleth@troodon-software.com> wrote:
> While Erlang will use it's own atomic operations, it can also use gcc
> __atomic_* builtins. This is now listed in Erlang's HOWTO/INSTALL.md.
>
> This change was necessary on RISC-V, since Erlang didn't have a built-in
> implementation, but it was able to use gcc's __atomic_* functions.
>
> Signed-off-by: Frank Hunleth <fhunleth@troodon-software.com>
> ---
> package/erlang/Config.in | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Thanks Frank for the patch. I have applied to master. However, I think
the patch may be incomplete. Indeed, on some CPU architectures, the
atomic intrinsics are implemented in a separate library provided by
gcc, called libatomic, and one need to link against it to use those
intrinsics.
Could you try to do a build of Erlang on SPARCv8 for example ?
I suppose it will fail, and if it does, could you add some logic in
erlang.mk to link against libatomic when BR2_TOOLCHAIN_HAS_LIBATOMIC=y
(of course assuming the Erlang build system doesn't do that by itself,
of course).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-28 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 22:24 [Buildroot] [PATCH 1/1] erlang: support builds when gcc __atomic_* exist Frank Hunleth
2021-07-28 21:35 ` Thomas Petazzoni [this message]
2021-08-02 12:46 ` Frank Hunleth
2021-08-02 12:55 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210728233513.4097848b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fhunleth@troodon-software.com \
--cc=will.newton@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox