From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Tony Ambardar <tony.ambardar@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Miguel Ojeda <ojeda@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] compiler-gcc.h: Disable __retain on gcc-11
Date: Thu, 03 Oct 2024 14:57:17 +0200 [thread overview]
Message-ID: <878qv5739u.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdVN9UyuUMFJUFb9hsKZ8=Uw=L0NEgS-kcoPDGbCk8XJnQ@mail.gmail.com> (Geert Uytterhoeven's message of "Thu, 3 Oct 2024 14:52:35 +0200")
On Okt 03 2024, Geert Uytterhoeven wrote:
> Hi Andreas,
>
> On Thu, Oct 3, 2024 at 2:34 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
>> On Okt 03 2024, Geert Uytterhoeven wrote:
>> > On Thu, Oct 3, 2024 at 2:11 PM Andreas Schwab <schwab@linux-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@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-10-03 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 7:24 [PATCH v2] compiler-gcc.h: Disable __retain on gcc-11 Geert Uytterhoeven
2024-10-02 12:18 ` Miguel Ojeda
2024-10-02 17:00 ` Andreas Schwab
2024-10-03 7:57 ` Geert Uytterhoeven
2024-10-03 8:42 ` Andreas Schwab
2024-10-03 8:57 ` Geert Uytterhoeven
2024-10-03 9:02 ` Andreas Schwab
2024-10-03 11:02 ` Miguel Ojeda
2024-10-03 12:11 ` Andreas Schwab
2024-10-03 12:18 ` Geert Uytterhoeven
2024-10-03 12:34 ` Andreas Schwab
2024-10-03 12:52 ` Geert Uytterhoeven
2024-10-03 12:57 ` Andreas Schwab [this message]
2024-12-31 14:19 ` Geert Uytterhoeven
2024-10-03 12:28 ` Miguel Ojeda
2024-10-03 12:42 ` Miguel Ojeda
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=878qv5739u.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel@iogearbox.net \
--cc=geert@linux-m68k.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=tony.ambardar@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.