From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow DW_OP_GNU_uninit in dwarf_expr_require_composition
Date: Tue, 04 Oct 2016 17:33:00 -0000 [thread overview]
Message-ID: <6037e019-8bc0-ce3f-2a8f-a4d804bca01b@redhat.com> (raw)
In-Reply-To: <m3lh3zuf30.fsf@oc1027705133.ibm.com>
On 04/27/2016 06:38 PM, Andreas Arnez wrote:
> In DWARF expression handling, some operators are required to be either
> at the end of an expression or followed by a composition operator. So
> far only the operators DW_OP_reg0-31 were allowed to be followed by
> DW_OP_GNU_uninit instead, and particularly DW_OP_regx was not, which is
> obviously inconsistent.
>
> This patch allows DW_OP_GNU_uninit after all operators requiring a
> composition, to simplify the code and make it more consistent. This
> policy may be more permissive than necessary, but in the worst case just
> leads to a DWARF location description resulting in an uninitialized
> value instead of an error message.
Fine with me. DW_OP_GNU_uninit is underspecified, anyway.
>
> gdb/ChangeLog:
>
> * dwarf2expr.c (dwarf_expr_require_composition): Allow
> DW_OP_GNU_uninit.
> (execute_stack_op): Use dwarf_expr_require_composition instead of
> copying its logic.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-04 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 17:38 Andreas Arnez
2016-10-04 17:33 ` Pedro Alves [this message]
2016-10-05 10:42 ` Andreas Arnez
2016-10-09 17:36 ` Tom Tromey
2016-10-10 12:24 ` Andreas Arnez
2016-10-10 22:41 ` 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=6037e019-8bc0-ce3f-2a8f-a4d804bca01b@redhat.com \
--to=palves@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@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