From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Problem with objdump -x on sparc32
Date: Wed, 22 Aug 2001 04:47:00 -0000 [thread overview]
Message-ID: <hoofp8co59.fsf@gee.suse.de> (raw)
HJ,
with binutils 2.11.90.0.27 on sparc32 I get the following running
objdump -x:
[...]
SYMBOL TABLE:
0000000000000000 l d .text 0000000000000000
0000000000000000 l d *ABS* 0000000000000000
[...]
RELOCATION RECORDS FOR [.text]:
OFFSET TYPE VALUE
00000018 R_SPARC_WDISP22 sun4c_fault
00000024 R_SPARC_WDISP22 bad_instruction
[...]
00000280 R_SPARC_32 .text+0x0001788c
00000284 R_SPARC_32 .text+0x000178b0
This means a symbol table output with 64 bit symbols but a relocation
table with 32 bits. This seems to have been caused by a recent patch
by you.
This breaks compilation of the sparc32 kernel. The btfixupprep.c
program (part of the Linux kernel in arch/sparc/boot/) expects that
both symbol table and offset have the same size. I can hack
btfixupprep.c but looking at the output I do wonder why we're not
consistent, it looks really broken now to me.
IMO we should use the same width for printing of both symbol table and
relocation records.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2001-08-22 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 4:47 Andreas Jaeger [this message]
2001-08-22 11:47 ` H . J . Lu
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=hoofp8co59.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=binutils@sources.redhat.com \
--cc=jakub@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).