public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: richard clark <richard.xnu.clark@gmail.com>
To: gcc-help@gcc.gnu.org
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
Date: Tue, 2 Jan 2024 11:29:27 +0800	[thread overview]
Message-ID: <CAJNi4rO+Dw5qYDtyJVbuo0OqAoXpGq_Qq6xjH9cvMCAUnW+77g@mail.gmail.com> (raw)

Hi,

I have a strong power arm64 box, and the linux distro is ubuntu 22.04,
the native gcc version is:

$ gcc --version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

It will abort the kernel build with the complaint by 'make Image':
ld: Unexpected GOT/PLT entries detected!
ld: Unexpected run-time procedure linkages detected!
ld: ID map text too big or misaligned
ld: drivers/net/nvidia_eth.o: in function `osi_lock_irq_enabled':
osi_hal.c:(.text+0x3cc): undefined reference to `__aarch64_cas4_sync'
...

But the cross-compile with aarch64-linux-gnu-gcc on the x86 box
doesn't show the above error message.
Any comments/suggestions? Thanks very much!

Richard

             reply	other threads:[~2024-01-02  3:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  3:29 richard clark [this message]
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
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=CAJNi4rO+Dw5qYDtyJVbuo0OqAoXpGq_Qq6xjH9cvMCAUnW+77g@mail.gmail.com \
    --to=richard.xnu.clark@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).