public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: binutils@sources.redhat.com
Subject: PPC ld test failure
Date: Tue, 02 Apr 2002 03:51:00 -0000	[thread overview]
Message-ID: <hobsd2e2sx.fsf@gee.suse.de> (raw)


The vers14 test from ld fails for me on powerpc with HJ's latest
binutils release with:
/usr/src/packages/BUILD/binutils-2.12.90.0.3/build-dir/ld/../binutils/strip-new tmpdir/vers14.so
BFD: tmpdir/stJdPpsP: warning: allocated section `.data' not in segment

This looks broken to me, readelf on the file shows that .data is empty
but is in the segment:

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
  [ 0]                   NULL            00000000 000000 000000 00      0   0  0
  [ 1] .hash             HASH            00000094 000094 0000d4 04   A  2   0  4
  [ 2] .dynsym           DYNSYM          00000168 000168 000220 10   A  3  11  4
  [ 3] .dynstr           STRTAB          00000388 000388 000094 00   A  0   0  1
  [ 4] .gnu.version      VERSYM          0000041c 00041c 000044 02   A  2   0  2
  [ 5] .gnu.version_d    VERDEF          00000460 000460 000080 00   A  3   4  4
  [ 6] .rela.dyn         RELA            000004e0 0004e0 000048 0c   A  2   0  4
  [ 7] .text             PROGBITS        00000528 000528 000098 00  AX  0   0  4
  [ 8] .rodata           PROGBITS        000005c0 0005c0 000008 00   A  0   0  4
  [ 9] .data             PROGBITS        000105c8 0005c8 000000 00  WA  0   0  1
  [10] .dynamic          DYNAMIC         000105c8 0005c8 000090 08  WA  3   0  4
  [11] .got              PROGBITS        00010658 000658 000010 04  WA  0   0  4
  [12] .sdata2           PROGBITS        00010668 000668 000000 00   A  0   0  4
  [13] .sdata            PROGBITS        00010668 000668 000008 00  WA  0   0  4
  [14] .sbss             NOBITS          00010670 000670 000000 00  WA  0   0  1
  [15] .bss              NOBITS          00010670 000670 000000 00  WA  0   0  1
  [16] .comment          PROGBITS        00000000 000670 000046 00      0   0  1
  [17] .shstrtab         STRTAB          00000000 0006b6 00009c 00      0   0  1
  [18] .symtab           SYMTAB          00000000 000a74 0002b0 10     19  1a  4
  [19] .strtab           STRTAB          00000000 000d24 000114 00      0   0  1
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings)
  I (info), L (link order), G (group), x (unknown)
  O (extra OS processing required) o (OS specific), p (processor specific)

Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  LOAD           0x000000 0x00000000 0x00000000 0x005c8 0x005c8 R E 0x10000
  LOAD           0x0005c8 0x000105c8 0x000105c8 0x000a8 0x000a8 RW  0x10000
  DYNAMIC        0x0005c8 0x000105c8 0x000105c8 0x00090 0x00090 RW  0x4

Any ideas?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

             reply	other threads:[~2002-04-02 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02  3:51 Andreas Jaeger [this message]
2002-04-02 23:59 ` Alan Modra
2002-04-03  5:25   ` Alan Modra

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=hobsd2e2sx.fsf@gee.suse.de \
    --to=aj@suse.de \
    --cc=binutils@sources.redhat.com \
    /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).