[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <878qv5739u.fsf@igel.home>
Date: Thu, 03 Oct 2024 14:57:17 +0200
From: Andreas Schwab <schwab@...ux-m68k.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, Tony Ambardar
<tony.ambardar@...il.com>, Daniel Borkmann <daniel@...earbox.net>,
Miguel Ojeda <ojeda@...nel.org>, Jiri Olsa <jolsa@...nel.org>, Andrew
Morton <akpm@...ux-foundation.org>, Arnd Bergmann <arnd@...db.de>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] compiler-gcc.h: Disable __retain on gcc-11
On Okt 03 2024, Geert Uytterhoeven wrote:
> Hi Andreas,
>
> On Thu, Oct 3, 2024 at 2:34 PM Andreas Schwab <schwab@...ux-m68k.org> wrote:
>> On Okt 03 2024, Geert Uytterhoeven wrote:
>> > On Thu, Oct 3, 2024 at 2:11 PM Andreas Schwab <schwab@...ux-m68k.org> wrote:
>> >> On Okt 03 2024, Miguel Ojeda wrote:
>> >> > Otherwise, does it mean we need a build-time test?
>> >>
>> >> A simple gcc version test definitely does not suffice.
>> >>
>> >> The suport for retain also depends on HAVE_INITFINI_ARRAY_SUPPORT, which
>> >> is usually enabled by default (depends on glibc support, but that is
>> >> much older), but can be disabled with --disable-initfini-array.
>> >
>> > FTR, no --disable-initfini-array seen here:
>>
>> --disable-initfini-array is the default for cross compilers.
>
> Apparently not for cross compilers targeting riscv64?
Yes, targets in the aarch64 era or newer enable initfini_array by
default. Also, gcc 12+ generally defaults to --enable-initfini-array on
Linux as well.
--
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
Powered by blists - more mailing lists