From: Richard Henderson <rth@redhat.com>
To: Alan Modra <amodra@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: alpha-linux gas testsuite failure
Date: Fri, 17 Sep 2010 19:45:00 -0000 [thread overview]
Message-ID: <4C93C559.5010105@redhat.com> (raw)
In-Reply-To: <20100917051307.GB16874@bubble.grove.modra.org>
On 09/16/2010 10:13 PM, Alan Modra wrote:
> Hi Richard,
> In case you haven't noticed, alpha-linux is failing one gas test.
>
> ../as-new -o dump.o /src/binutils-current/gas/testsuite/gas/elf/dwarf2-2.s
> Executing on host: sh -c {../as-new -o dump.o /src/binutils-current/gas/testsuite/gas/elf/dwarf2-2.s 2>&1} /dev/null gas.out (tim
> spawn [open ...]
> /home/alan/build/gas/alpha-linux/gas/testsuite/../../binutils/readelf -w dump.o
> Executing on host: sh -c {/home/alan/build/gas/alpha-linux/gas/testsuite/../../binutils/readelf -w dump.o >dump.out 2>gas.stderr}
> spawn [open ...]
> regexp_diff match failure
> regexp "^ <10> DW_AT_high_pc : 0x. $"
> line " <10> DW_AT_high_pc : 0x10 "
> regexp_diff match failure
> regexp "^ <44> DW_AT_high_pc : 0x. $"
> line " <44> DW_AT_high_pc : 0x10 "
> FAIL: DWARF2 2
>
> It's not just a testsuite oddity. Relocs are being generated against
> a local symbol and the value of the sym is also appearing in the
> addend. Since you don't use bfd_elf_generic_reloc on alpha, you get
> to write lots of horrible stuff in tc_gen_reloc and/or md_apply_fix to
> work around bfd_install_relocation brain damage..
>
I don't see this failure. I'm not even sure I'm getting that far.
First off, --nocompress-debug-sections doesn't work. I still get
[ 8] .zdebug_abbrev PROGBITS 0000000000000000 000000dc
000000000000004d 0000000000000000 0 0 1
At present all I can get is
$ ../../binutils/readelf -wi dump.o
Contents of the .debug_info section:
Compilation Unit @ offset 0x0:
Length: 0x4e (32-bit)
Version: 2
Abbrev Offset: 0
Pointer Size: 4
<0><b>: Abbrev Number: 1
readelf: Warning: DIE at offset b refers to abbreviation number 1 which does not exist
But the relocations themselves appear sane:
Relocation section '.rela.debug_info' at offset 0x878 contains 6 entries:
Offset Info Type Sym. Value Sym. Name + Addend
000000000006 000e00000001 R_ALPHA_REFLONG 0000000000000000 .Labbrev1_begin + 0
00000000000c 000f00000001 R_ALPHA_REFLONG 0000000000000000 .Lline1_begin + 0
000000000010 000900000001 R_ALPHA_REFLONG 0000000000000008 .Lend_text1 + 8
000000000014 000600000001 R_ALPHA_REFLONG 0000000000000004 .Lbegin_text1 + 4
000000000040 000700000001 R_ALPHA_REFLONG 0000000000000004 .Lbegin_func_cu1 + 4
000000000044 000800000001 R_ALPHA_REFLONG 0000000000000008 .Lend_func_cu1 + 8
So I'm not sure what problem you're seeing.
Do note that ".L" is *not* a local symbol prefix on Alpha.
For that you have to use "$". So it's quite expected that
these aren't reduced to ".text + offset". But that should
not really affect anything; readelf ought to be able to
cope, I should think.
r~
next parent reply other threads:[~2010-09-17 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100917051307.GB16874@bubble.grove.modra.org>
2010-09-17 19:45 ` Richard Henderson [this message]
2010-09-18 0:13 ` Alan Modra
2010-09-19 22:33 ` Richard Henderson
2010-09-19 22:48 ` Richard Henderson
2010-09-20 2: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=4C93C559.5010105@redhat.com \
--to=rth@redhat.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.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).