From: Jason Merrill <jason@redhat.com>
To: John Darrington <john@darrington.wattle.id.au>
Cc: gcc-patches@sourceware.org
Subject: Re: [PATCH] Add a dwarf unit type to represent 24 bit values.
Date: Mon, 10 Sep 2018 15:41:00 -0000 [thread overview]
Message-ID: <CADzB+2k8V89O9-CT_ESMhBOq42g-2LuNN69bEQt1MgePzYsLPQ@mail.gmail.com> (raw)
In-Reply-To: <20180910144248.puqiz5icxktn4o4n@jocasta.intra>
On Mon, Sep 10, 2018 at 3:42 PM, John Darrington
<john@darrington.wattle.id.au> wrote:
> On Mon, Sep 10, 2018 at 03:36:26PM +0100, Jason Merrill wrote:
> On Mon, Aug 27, 2018 at 8:20 PM, John Darrington
> <john@darrington.wattle.id.au> wrote:
> > * include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]: New member.
>
>
> What's the rationale? Do you have a separate patch that uses this new macro?
>
> Yes. I there is an upcoming patch for GDB. See
> https://sourceware.org/ml/gdb-patches/2018-08/msg00731.html
This looks like support for reading fixed 3-byte values from the
exception handling unwind information. Do you expect this information
to ever need to store 3-byte values? The offsets in the unwind info
don't need to correspond exactly to target word sizes, and if you use
an assembler that supports it (such as GNU as), the table will use
variable-length encoding anyway.
Jason
next prev parent reply other threads:[~2018-09-10 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180827192040.16550-1-john@darrington.wattle.id.au>
2018-08-27 19:21 ` John Darrington
2018-09-08 13:58 ` John Darrington
2018-09-10 14:36 ` Jason Merrill
2018-09-10 14:42 ` John Darrington
2018-09-10 15:41 ` Jason Merrill [this message]
2018-09-13 5:49 ` John Darrington
2018-09-13 17:42 ` Jason Merrill
2018-09-19 19:34 ` John Darrington
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=CADzB+2k8V89O9-CT_ESMhBOq42g-2LuNN69bEQt1MgePzYsLPQ@mail.gmail.com \
--to=jason@redhat.com \
--cc=gcc-patches@sourceware.org \
--cc=john@darrington.wattle.id.au \
/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).