On 31.05.23 09:27, Richard Biener wrote:
On Wed, May 31, 2023 at 7:31 AM Sebastian Huber
<sebastian.hu...@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.
I would be nice if I could add the multi-threaded gcov support for
targets lacking atomic operations in GCC 14 (for example 32-bit RISC-V).
I need a direction how to implement this. Should it be done through a
generic libatomic implementation based on gthr.h or through a special
function provided by libgcov?
Should I add the libgcov functions to builtin_decl_explicit()?
No, they shouldn't be any different from other libgcov functions.
Ok.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@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/
