public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/101448] Use GCC 9.3.0 to build Ceph crimson-osd on Arm64, linker failed for relocation truncated to fit: R_AARCH64_CALL26 against symbol Date: Fri, 16 Jul 2021 11:02:38 +0000 [thread overview] Message-ID: <bug-101448-4-kiMZXO7QLr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101448-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101448 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Closing as this is not a compiler bug. If there's a problem anywhere it is that the linker needs to implement mitigation strategies for very large code bases, but even that is an enhancement rather than a strict bug.
prev parent reply other threads:[~2021-07-16 11:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-14 10:42 [Bug c++/101448] New: Use GCC 9.3.0 to build Ceph crimson-osd, linker failed for "relocation truncated to fit" " kevin.zhao at linaro dot org 2021-07-14 12:52 ` [Bug target/101448] " rguenth at gcc dot gnu.org 2021-07-14 14:41 ` [Bug target/101448] Use GCC 9.3.0 to build Ceph crimson-osd on Arm64, linker failed for relocation truncated to fit: R_AARCH64_CALL26 " kevin.zhao at linaro dot org 2021-07-14 15:25 ` rearnsha at gcc dot gnu.org 2021-07-15 9:42 ` xinliang.liu at linaro dot org 2021-07-15 11:12 ` kevin.zhao at linaro dot org 2021-07-15 17:54 ` rearnsha at gcc dot gnu.org 2021-07-16 2:44 ` kevin.zhao at linaro dot org 2021-07-16 11:02 ` rearnsha at gcc dot gnu.org [this message]
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-101448-4-kiMZXO7QLr@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).