public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/95620] [10/11 Regression] relocation truncated to fit: R_X86_64_PC32 against `.bss' Date: Wed, 10 Jun 2020 07:21:50 +0000 [thread overview] Message-ID: <bug-95620-4-T5DRWDgQoo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95620-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95620 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Last reconfirmed| |2020-06-10 Resolution|INVALID |--- Ever confirmed|0 |1 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- So it's really problem as with LTO we don't put the large array into .lbss section: LTO: .file "<artificial>" .text .local a .comm a,2830270464,32 .local b .comm b,4,4 non-LTO mode: .globl a .section .lbss,"aw" .align 32 .type a, @object .size a, 2830270464 a: .zero 2830270464 So the symbol goes from .lbss section to .data section as LTO makes the symbol local.
next prev parent reply other threads:[~2020-06-10 7:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-09 20:53 [Bug lto/95620] New: " marxin at gcc dot gnu.org 2020-06-10 6:19 ` [Bug lto/95620] " marxin at gcc dot gnu.org 2020-06-10 7:21 ` marxin at gcc dot gnu.org [this message] 2020-06-26 12:09 ` [Bug target/95620] " rguenth at gcc dot gnu.org 2020-06-26 13:00 ` hjl.tools at gmail dot com 2020-06-26 21:03 ` hjl.tools at gmail dot com 2020-06-29 9:46 ` marxin at gcc dot gnu.org 2020-07-18 15:56 ` cvs-commit at gcc dot gnu.org 2020-07-18 15:57 ` hjl.tools at gmail dot com 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` [Bug target/95620] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 8:54 ` rguenth 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-95620-4-T5DRWDgQoo@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).