Hi Remi
On Wed, Jul 30, 2025 at 12:49:26PM +, Remi Machet wrote:
>
> Hi,
>
> Thank you for your reply and looking into it.
>
> I don't see anything trivial thus this is probably best left for a subsequent
> cleanup.
>
> Can we assume libatomic depends on libgcc? If that is ok then it migh
On 7/30/25 13:25, Yury Khrustalev wrote:
External email: Use caution opening links or attachments
Hi Remi
On Wed, Jul 23, 2025 at 01:53:13PM +, Remi Machet wrote:
On 7/23/25 04:45, Yury Khrustalev wrote:
...
-#if __has_include()
-#include
-#else
+/* The following struct is ABI-correc
Hi Remi
On Wed, Jul 23, 2025 at 01:53:13PM +, Remi Machet wrote:
>
> On 7/23/25 04:45, Yury Khrustalev wrote:
>
> ...
>
> -#if __has_include()
> -#include
> -#else
> +/* The following struct is ABI-correct description of the 2nd argument for an
> + ifunc resolver as per SYSVABI spec (see
> -Original Message-
> From: Yury Khrustalev
> Sent: Wednesday, July 23, 2025 9:45 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Andrew Pinski ; Richard Sandiford
> ; Tamar Christina ;
> Alfie Richards ; Alice Carlotti
> ;
> Victor Do Nascimento
> Subject: [PATCH v2 1/3] aarch64: Stop using
On 7/23/25 04:45, Yury Khrustalev wrote:
External email: Use caution opening links or attachments
This optional header is used to bring in the definition of the
struct __ifunc_arg_t type. Since it has been added to glibc only
recently, the previous implementation had to check whether this
heade
