From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Brown <david.brown@hesbynett.no>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Atomic accesses on ARM microcontrollers
Date: Fri, 9 Oct 2020 18:28:24 -0500 [thread overview]
Message-ID: <20201009232824.GM2672@gate.crashing.org> (raw)
In-Reply-To: <945d5e74-b449-3746-6560-996d0437db76@hesbynett.no>
Hi!
On Fri, Oct 09, 2020 at 08:28:05PM +0200, David Brown wrote:
> For 8-bit, 16-bit and 32-bit types, atomic accesses are just simple
> loads and stores. These are generated fine.
>
> But for 64-bit and above, there are library calls to a compiler-provided
> library.
> Is there any way I can replace this library with my own code here, while
> still using the language atomics?
Add something in libgcc/config/arm/ ?
You might need to add something specific to some configuration (in some
t-* file), or maybe add another command line flag.
It sounds like you have to add more constraints on what atomic can be
used for than what is specified currently.
Segher
next prev parent reply other threads:[~2020-10-09 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 18:28 David Brown
2020-10-09 23:28 ` Segher Boessenkool [this message]
2020-10-10 12:39 ` Jonathan Wakely
2020-10-10 19:43 ` David Brown
2020-10-10 20:18 ` Jonathan Wakely
2020-10-11 10:54 ` David Brown
2020-10-12 7:17 ` David Brown
2020-10-12 21:44 ` Patrick Oppenlander
[not found] ` <b29b1595-9441-68eb-f257-244a35082c82@winterflaw.net>
2020-10-10 19:43 ` David Brown
2020-10-10 20:09 ` Jonathan Wakely
[not found] ` <bdf0f96f-0377-bee7-c02e-9704f0bea6a5@winterflaw.net>
2020-10-11 12:16 ` David Brown
[not found] ` <24c49c76-43c3-9a0d-6b02-a4340b1fccba@winterflaw.net>
2020-10-11 12:51 ` David Brown
2020-10-13 11:46 ` Richard Earnshaw
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=20201009232824.GM2672@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david.brown@hesbynett.no \
--cc=gcc-help@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).