On Tue, 15 Oct 2024, Matthew Malcomson wrote:
> Seems that the testsuite and build system are the main things to watch
> out for here right?
Yes, as illustrated by the draft patch linked from bug 81358 comment 11.
--
Joseph S. Myers
josmy...@redhat.com
n
Cc: Jonathan Wakely ; gcc-patches@gcc.gnu.org
Subject: Re: libstdc++ fetch_add & fenv -- ecosystem questions
External email: Use caution opening links or attachments
On Mon, 14 Oct 2024, Matthew Malcomson wrote:
> 4. __atomic_feraiseexcept should be a builtin to avoid previously
On Mon, 14 Oct 2024, Matthew Malcomson wrote:
> 4. __atomic_feraiseexcept should be a builtin to avoid previously
> unnecessary requirement to link libatomic.
libatomic should be linked by default (with --as-needed); see bug 81358.
But if your concern is e.g. libstdc++.so having DT_NEEDED fo
27;m unfamiliar with.
From: Jonathan Wakely
Sent: 14 October 2024 2:36 PM
To: Matthew Malcomson
Cc: Joseph Myers ; gcc-patches@gcc.gnu.org
Subject: Re: libstdc++ fetch_add & fenv -- ecosystem questions
External email: Use caution opening links or attachments
O
On Mon, 14 Oct 2024 at 14:35, Jonathan Wakely wrote:
>
> N.B. please CC the libstdc++ list for libstdc++ topics.
>
> On Mon, 14 Oct 2024 at 14:00, Matthew Malcomson wrote:
> >
> > After getting GCC to handle floating point exceptions I'm now noticing that
> > the `targetm.atomic_assign_expand_fe
N.B. please CC the libstdc++ list for libstdc++ topics.
On Mon, 14 Oct 2024 at 14:00, Matthew Malcomson wrote:
>
> After getting GCC to handle floating point exceptions I'm now noticing that
> the `targetm.atomic_assign_expand_fenv` hook tends to use the library
> function `__atomic_feraiseexce
