From: Richard Biener <richard.guenther@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libatomic: Provide gthr.h default implementation
Date: Tue, 30 May 2023 11:53:28 +0200 [thread overview]
Message-ID: <CAFiYyc1HJCeyYPcQj=J5Tz4em0ZDXEvny3RH=J0POiiRnzmu_g@mail.gmail.com> (raw)
In-Reply-To: <1316c42f-a69d-ab56-296e-f617942d4759@embedded-brains.de>
On Tue, May 23, 2023 at 11:28 AM Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> On 10.01.23 16:38, Sebastian Huber wrote:
> > On 19/12/2022 17:02, Sebastian Huber wrote:
> >> Build libatomic for all targets. Use gthr.h to provide a default
> >> implementation. If the thread model is "single", then this
> >> implementation will
> >> not work if for example atomic operations are used for thread/interrupt
> >> synchronization.
> >
> > Is this and the related -fprofile-update=atomic patch something for GCC 14?
>
> Now that the GCC 14 development is in progress, what about this patch?
Sorry, there doesn't seem to be a main maintainer for libatomic and your patch
touches targets which didn't have it before.
Can you explain how this affects the ABI of targets not having (needing?!)
libatomic? It might help if you can say this is still opt-in and targets not
building libatomic right now would not with your patch and targets already
building libatomic have no changes with your patch.
That said - what kind of ABI implications has providing libatomic support
for a target that didn't do so before?
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-30 9:55 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 [this message]
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
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='CAFiYyc1HJCeyYPcQj=J5Tz4em0ZDXEvny3RH=J0POiiRnzmu_g@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).