public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95620] [10/11 Regression] relocation truncated to fit: R_X86_64_PC32 against `.bss'
Date: Fri, 26 Jun 2020 13:00:36 +0000	[thread overview]
Message-ID: <bug-95620-4-aUBG1mTUSI@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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Martin Liška from comment #2)
> 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
         ^^^^ This should be .largecomm.

[hjl@gnu-cfl-2 tmp]$ cat x.s
        .local  a
        .largecomm a,2830270464,32
[hjl@gnu-cfl-2 tmp]$ gcc -c x.s 
[hjl@gnu-cfl-2 tmp]$ readelf -SsW  x.o
There are 9 section headers, starting at offset 0x160:

Section Headers:
  [Nr] Name              Type            Address          Off    Size   ES Flg
Lk Inf Al
  [ 0]                   NULL            0000000000000000 000000 000000 00     
0   0  0
  [ 1] .text             PROGBITS        0000000000000000 000040 000000 00  AX 
0   0  1
  [ 2] .data             PROGBITS        0000000000000000 000040 000000 00  WA 
0   0  1
  [ 3] .bss              NOBITS          0000000000000000 000040 000000 00  WA 
0   0  1
  [ 4] .lbss             NOBITS          0000000000000000 000040 a8b28000 00
WAl  0   0 32
  [ 5] .note.gnu.property NOTE            0000000000000000 000040 000030 00   A
 0   0  8
  [ 6] .symtab           SYMTAB          0000000000000000 000070 0000a8 18     
7   7  8
  [ 7] .strtab           STRTAB          0000000000000000 000118 000003 00     
0   0  1
  [ 8] .shstrtab         STRTAB          0000000000000000 00011b 000045 00     
0   0  1
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings), I (info),
  L (link order), O (extra OS processing required), G (group), T (TLS),
  C (compressed), x (unknown), o (OS specific), E (exclude),
  l (large), p (processor specific)

Symbol table '.symtab' contains 7 entries:
   Num:    Value          Size Type    Bind   Vis      Ndx Name
     0: 0000000000000000     0 NOTYPE  LOCAL  DEFAULT  UND 
     1: 0000000000000000     0 SECTION LOCAL  DEFAULT    1 
     2: 0000000000000000     0 SECTION LOCAL  DEFAULT    2 
     3: 0000000000000000     0 SECTION LOCAL  DEFAULT    3 
     4: 0000000000000000 0xa8b28000 OBJECT  LOCAL  DEFAULT    4 a
     5: 0000000000000000     0 SECTION LOCAL  DEFAULT    4 
     6: 0000000000000000     0 SECTION LOCAL  DEFAULT    5 
[hjl@gnu-cfl-2 tmp]$

  parent reply	other threads:[~2020-06-26 13:00 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
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 [this message]
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-aUBG1mTUSI@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).