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 06:19:56 +0000 [thread overview]
Message-ID: <bug-95620-4-6jOLnoBSjI@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
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
So we basically change assembly in the following way:
$ diff -u good.s bad.s -U999
--- good.s 2020-06-09 23:37:35.755366723 +0200
+++ bad.s 2020-06-09 23:37:36.771361476 +0200
@@ -1,13 +1,13 @@
.file "<artificial>"
.text
.globl main
.type main, @function
main:
.LFB1:
movl b(%rip), %edx
.LFE1:
.size main, .-main
- .local b
- .comm b,4,4
.local a
.comm a,2430270464
+ .local b
+ .comm b,4,4
and logically the relocation for 'b(%rip)' now has to go over the huge 'a'
array.
It's invalid to me, I would recommend using -mcmodel=large.
next prev parent reply other threads:[~2020-06-10 6:19 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 ` marxin at gcc dot gnu.org [this message]
2020-06-10 7:21 ` [Bug lto/95620] " marxin at gcc dot gnu.org
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-6jOLnoBSjI@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: 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).