From: Segher Boessenkool <segher@kernel.crashing.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: richard clark <richard.xnu.clark@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
gcc-help@gcc.gnu.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
Date: Tue, 9 Jan 2024 02:26:47 -0600 [thread overview]
Message-ID: <20240109082647.GJ19790@gate.crashing.org> (raw)
In-Reply-To: <4ee8067e72028b070d92e10fa33ddde3a498cb48.camel@xry111.site>
On Tue, Jan 09, 2024 at 04:09:20PM +0800, Xi Ruoyao wrote:
> If GCC is configured with things like --with-arch=something, libgcc can
> contain (FP/vector) instructions unsafe to use in kernel w/o special
> handling.
No, it can not. Please file a bug (<https://gcc.gnu.org/bugs.html>) if
this happens to you. Thanks!
--with-arch= only sets the *default* options, the user can override this
always (with an -march= option, say).
> If libgcc is so vital GCC needs to provide a way to make it work for a
> set of compiler switches incompatible with any pre-built multilib. For
> example, installing the source of libgcc into /usr/lib/gcc and provide a
> tool to build a libgcc.a with the specified options.
That is how things are supposed to work, already. Either libgcc uses
only instructions that work everywhere, or libgcc is multilibbed, things
like that. In all normal cases this is completely transparent to the
compiler user.
Segher
next prev parent reply other threads:[~2024-01-09 8:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 3:29 richard clark
2024-01-02 8:53 ` richard clark
2024-01-04 18:18 ` Mark Rutland
2024-01-08 1:28 ` richard clark
2024-01-08 10:51 ` Mark Rutland
2024-01-08 10:56 ` Xi Ruoyao
2024-01-09 2:55 ` richard clark
2024-01-09 3:05 ` Xi Ruoyao
2024-01-09 6:04 ` richard clark
2024-01-09 7:48 ` Segher Boessenkool
2024-01-09 8:09 ` Xi Ruoyao
2024-01-09 8:26 ` Segher Boessenkool [this message]
2024-01-10 5:59 ` richard clark
2024-01-10 14:10 ` Segher Boessenkool
2024-01-11 1:42 ` richard clark
2024-01-11 11:26 ` Mark Rutland
2024-01-15 9:23 ` richard clark
2024-01-09 2:52 ` richard clark
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=20240109082647.GJ19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=richard.xnu.clark@gmail.com \
--cc=xry111@xry111.site \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).