From: Richard Biener <richard.guenther@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
Jakub Jelinek <jakub@redhat.com>, Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libatomic: Provide gthr.h default implementation
Date: Wed, 31 May 2023 09:27:52 +0200 [thread overview]
Message-ID: <CAFiYyc0St8CBShsq+b-9y+t+kHS2rVAK8DNy4yz7CET9prcN=g@mail.gmail.com> (raw)
In-Reply-To: <e07888c3-9d69-d005-4f4e-46849654c2b2@embedded-brains.de>
On Wed, May 31, 2023 at 7:31 AM Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> On 30.05.23 13:17, Richard Biener wrote:
> > The alternative would be to provide the required subset of atomic
> > library functions from libgcov.a and emit calls to that directly?
> > The locked data isn't part of any ABI so no compatibility guarantee
> > needs to be maintained?
>
> So, if atomic operations are not available in hardware, then I should
> emit calls to libgcov.a which would use gthr.h to implement them? I
> guess that I can to this, but it needs a bit of time.
Before doing that it would be nice to get buy-in from others - maybe
my ABI concern for libatomic isn't shared by others.
> Should I add the libgcov functions to builtin_decl_explicit()?
No, they shouldn't be any different from other libgcov functions.
Richard.
>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.huber@embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax: +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2023-05-31 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 16:02 Sebastian Huber
2023-01-10 15:38 ` Sebastian Huber
2023-05-23 9:27 ` Sebastian Huber
2023-05-30 9:53 ` Richard Biener
2023-05-30 10:17 ` Sebastian Huber
2023-05-30 11:17 ` Richard Biener
2023-05-31 5:31 ` Sebastian Huber
2023-05-31 7:27 ` Richard Biener [this message]
2023-09-11 13:02 ` Sebastian Huber
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='CAFiYyc0St8CBShsq+b-9y+t+kHS2rVAK8DNy4yz7CET9prcN=g@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=sebastian.huber@embedded-brains.de \
/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).