public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "songmz1999 at foxmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/109245] New: aarch64 gcc defaults to -moutline-atomics but symbol ‘__aarch64_swp4_sync’ is hidden in libgcc.a Date: Wed, 22 Mar 2023 09:53:36 +0000 [thread overview] Message-ID: <bug-109245-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109245 Bug ID: 109245 Summary: aarch64 gcc defaults to -moutline-atomics but symbol ‘__aarch64_swp4_sync’ is hidden in libgcc.a Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: songmz1999 at foxmail dot com Target Milestone: --- I found an issue when compiling the connection process using the toolchain aarch64_gcc12.2.0_glibc2.31.0_fp with the error message: ~/aarch64_gcc12.2.0_glibc2.31.0_fp/aarch64-unknown-linux-gnueabi/bin/.ld: ../../../deploy/oms/bin/omsservice: hidden symbol `__aarch64_swp4_sync' in ~/aarch64_gcc12.2.0_glibc2.31.0_fp/bin/../lib/gcc/aarch64-unknown-linux-gnueabi/12.2.0/libgcc.a(swp_4_5.o) is referenced by DSO ~/aarch64_gcc12.2.0_glibc2.31.0_fp/aarch64-unknown-linux-gnueabi/bin/.ld: final link failed: bad value The solution I've found so far is to enable the -mno-outline-atomics parameter at compile time. But why does gcc have -moutline-atomics enabled by default, but when calling the function '__aarch64_swp4_sync', it is hidden in libgcc.a? Is there a better solution?
next reply other threads:[~2023-03-22 9:53 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-22 9:53 songmz1999 at foxmail dot com [this message] 2023-03-22 9:58 ` [Bug libgcc/109245] " jakub at gcc dot gnu.org 2023-03-22 10:25 ` pinskia at gcc dot gnu.org 2023-03-22 16:13 ` pinskia at gcc dot gnu.org 2024-02-21 0:42 ` pinskia at gcc dot gnu.org
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=bug-109245-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).