Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Use dwarf assembler in gdb.dwarf2/implptr-64bit.exp
Date: Tue, 24 Jan 2017 19:21:00 -0000	[thread overview]
Message-ID: <m3o9yw2rim.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <1485250945-17594-3-git-send-email-yao.qi@linaro.org> (Yao Qi's	message of "Tue, 24 Jan 2017 09:42:25 +0000")

On Tue, Jan 24 2017, Yao Qi wrote:

> diff --git a/gdb/testsuite/gdb.dwarf2/implptr-64bit.exp b/gdb/testsuite/gdb.dwarf2/implptr-64bit.exp
> index b4dcbde..9565579 100644
> --- a/gdb/testsuite/gdb.dwarf2/implptr-64bit.exp
> +++ b/gdb/testsuite/gdb.dwarf2/implptr-64bit.exp

Looks generally OK to me, except...

> +		variable_label: variable {

...this causes FAILs on one of my systems unless replacing the
"variable" above by "DW_TAG_variable".  Note that "variable" is a Tcl
command.

> +		    { name v }
> +		    { location {
> +			DW_OP_implicit_value 0x1 0x1 0x1 0x1
> +		    } SPECIAL_expr}
> +		    { type :$struct_label "DW_FORM_ref$ref_addr_size" }
> +		}
> +
> +		if { !$two_cu } {
> +		    subprogram {
> +			{ name main }
> +			{ low_pc main addr }
> +			{ high_pc "main+0x100" addr }
> +			{ type %$int_label }
> +			{ external 1 flag }
> +		    } {
> +			variable {

Same here.

> diff --git a/gdb/testsuite/lib/dwarf.exp b/gdb/testsuite/lib/dwarf.exp
> index 1883c86..db51f5d 100644
> --- a/gdb/testsuite/lib/dwarf.exp
> +++ b/gdb/testsuite/lib/dwarf.exp

Looks OK to me as well, except a nit:

> +			switch -regexp -- $value {
> +			    {^0x[[:xdigit:]]{1}$} {_op .byte $value}
> +			    {^0x[[:xdigit:]]{2}$} {_op .byte $value}

I'd rather replace the above two lines by a single one, to emphasize
that both cases are handled in the same way:

			    {^0x[[:xdigit:]]{1,2}$} {_op .byte $value}

--
Andreas


  reply	other threads:[~2017-01-24 19:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 19:24 [PATCH] Big-endian targets: don't ignore offset into DW_OP_implicit_value Andreas Arnez
2017-01-19 17:44 ` Yao Qi
2017-01-19 18:21   ` Andreas Arnez
2017-01-24  9:42     ` [PATCH 0/2] Add DW_OP_implicit_value in dwarf assembler Yao Qi
2017-01-24  9:43       ` [PATCH 2/2] Use dwarf assembler in gdb.dwarf2/implptr-64bit.exp Yao Qi
2017-01-24 19:21         ` Andreas Arnez [this message]
2017-01-25 16:26           ` Yao Qi
2017-01-24  9:43       ` [PATCH 1/2] Handle DW_OP_GNU_implicit_pointer in dwarf assembler Yao Qi
2017-01-25 22:12 ` [PATCH] Big-endian targets: don't ignore offset into DW_OP_implicit_value Yao Qi
2017-01-27 19:35   ` Andreas Arnez
2017-02-01  9:09     ` Andreas Arnez
2017-02-01  9:16       ` Yao Qi

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=m3o9yw2rim.fsf@oc1027705133.ibm.com \
    --to=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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