From: Tom Tromey <tom@tromey.com>
To: Ulrich Weigand via Gcc <gcc@gcc.gnu.org>
Cc: gdb@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: Issue with pointer types marked with scalar_storage_order
Date: Thu, 06 May 2021 13:45:06 -0600 [thread overview]
Message-ID: <87a6p7pry5.fsf@tromey.com> (raw)
In-Reply-To: <20210506123308.GA27332@oc3748833570.ibm.com> (Ulrich Weigand via Gcc's message of "Thu, 6 May 2021 14:33:08 +0200")
>>>>> "Ulrich" == Ulrich Weigand via Gcc <gcc@gcc.gnu.org> writes:
Ulrich> If we do want to byte-swap pointer types, then I guess we need
Ulrich> to still fix the debug info problem, which I guess would at a
Ulrich> minimum require extending DWARF to allow DW_AT_endianity as an
Ulrich> attribute to DW_TAG_pointer_type (and then probably also
Ulrich> DW_TAG_reference_type, DW_TAG_rvalue_reference_type,
Ulrich> DW_TAG_ptr_to_member_type and possibly others). Also, the
Ulrich> implementation in GDB would need to be changed accordingly.
Ulrich> Any comments or suggestions on what to do here?
This kind of extension is pretty normal in DWARF, so I think it isn't a
big deal to emit it. Consumers are ordinarily expected to simply ignore
things they don't understand.
Tom
prev parent reply other threads:[~2021-05-06 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 12:33 Ulrich Weigand via Gdb
2021-05-06 14:07 ` Eric Botcazou
2021-05-07 12:45 ` Ulrich Weigand via Gdb
2021-05-06 19:45 ` Tom Tromey [this message]
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=87a6p7pry5.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=uweigand@de.ibm.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