From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Permit DW_OP_GNU_uninit to be used with DW_OP_piece
Date: Sun, 11 Jun 2023 18:28:24 -0600 [thread overview]
Message-ID: <87cz21ed7b.fsf@tromey.com> (raw)
In-Reply-To: <20230611155306.54bc163b@f38-zws-nv> (Kevin Buettner's message of "Sun, 11 Jun 2023 15:53:06 -0700")
Kevin> The test case stayed the same, but this is what the change to
Kevin> gdb/dwarf2/expr.c ended up looking like:
...
FWIW see dwarf_expr_require_composition
Tom
prev parent reply other threads:[~2023-06-12 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 18:31 Kevin Buettner
2023-06-05 13:17 ` Tom Tromey
2023-06-11 22:53 ` Kevin Buettner
2023-06-12 0:28 ` 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=87cz21ed7b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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).