From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: implptrconst.exp error on 32-bit targets [Re: [3/4] fix DW_OP_GNU_implicit_pointer pointing to a constant]
Date: Mon, 13 May 2013 18:42:00 -0000 [thread overview]
Message-ID: <20130513184212.GA11756@host2.jankratochvil.net> (raw)
In-Reply-To: <87li7ibxf0.fsf@fleche.redhat.com>
On Mon, 13 May 2013 19:29:55 +0200, Tom Tromey wrote:
> Let me know what you think of this.
I find it correct.
As it uses DWARF-2 the DW_OP_GNU_implicit_pointer DIE offset has size like the
DWARF/inferior address size which you changed 8 -> 4 bytes now.
As was already discussed before using 32-bit addresses works even for 64-bit
archs except for - IIRC - Alpha, but that we just ignore.
This testcase in fact does not need any relocations, one could even keep there
the 64-bit address zize and rely on the fact that .debug_info in this testcase
will not contain any other CU and make the reference relative against label at
offset 0 of .debug_info (.Lcu1_begin). This will then work even with 64-bit
address sizes in 32-bit ELF file.
Thanks,
Jan
next prev parent reply other threads:[~2013-05-13 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 2:44 [3/4] fix DW_OP_GNU_implicit_pointer pointing to a constant Tom Tromey
2013-05-06 19:40 ` Tom Tromey
2013-05-12 15:14 ` implptrconst.exp error on 32-bit targets [Re: [3/4] fix DW_OP_GNU_implicit_pointer pointing to a constant] Jan Kratochvil
2013-05-13 17:30 ` Tom Tromey
2013-05-13 18:42 ` Jan Kratochvil [this message]
2013-05-13 19:32 ` Tom Tromey
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=20130513184212.GA11756@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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