From: Yao Qi <qiyaoltc@gmail.com>
To: Don Breazeal <donb@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, <palves@redhat.com>,
<lgustavo@codesourcery.com>
Subject: Re: [PATCH v2 1/2] Optzd-out ptr: New test for error handling
Date: Tue, 29 Mar 2016 11:58:00 -0000 [thread overview]
Message-ID: <86vb45sdh5.fsf@gmail.com> (raw)
In-Reply-To: <1459200820-24735-2-git-send-email-donb@codesourcery.com> (Don Breazeal's message of "Mon, 28 Mar 2016 14:33:39 -0700")
Don Breazeal <donb@codesourcery.com> writes:
> + DW_TAG_subprogram {
> + {DW_AT_name func01}
> + {DW_AT_type :$int_label}
> + {external 1 flag}
> + {low_pc func01_start addr}
> + {high_pc func01_end addr}
Please use MACRO_AT_func so that the low_pc and high_pc can be got correctly.
> + } {
> + DW_TAG_variable {
> + {DW_AT_name ptr}
> + {DW_AT_type :$pointer_label}
> + {DW_AT_location {} DW_FORM_block1}
> + }
> + }
> +
> + DW_TAG_subprogram {
> + {DW_AT_name main}
> + {DW_AT_type :$int_label}
> + {external 1 flag}
> + {low_pc main_start addr}
> + {high_pc main_end addr}
Likewise.
> + } {
> + }
--
Yao (齐尧)
next prev parent reply other threads:[~2016-03-29 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1456273154-28629-1-git-send-email-donb@codesourcery.com>
2016-02-24 1:14 ` [PATCH] Eliminate -var-create error for optzd ptr to struct Luis Machado
2016-02-24 16:31 ` Don Breazeal
2016-02-25 12:22 ` Pedro Alves
2016-03-28 21:33 ` [PATCH v2 0/2] Optzd-out ptr: Error handling improvement Don Breazeal
2016-03-28 21:34 ` [PATCH v2 2/2] Optzd-out ptr: Eliminate -var-create error Don Breazeal
2016-03-28 21:34 ` [PATCH v2 1/2] Optzd-out ptr: New test for error handling Don Breazeal
2016-03-29 11:58 ` Yao Qi [this message]
2016-03-29 17:13 ` Don Breazeal
2016-03-30 14:37 ` Yao Qi
2016-04-06 21:34 ` Don Breazeal
2016-03-29 12:01 ` [PATCH] Eliminate -var-create error for optzd ptr to struct Yao Qi
2016-03-29 17:14 ` Don Breazeal
2016-03-30 14:35 ` Yao Qi
2016-04-01 16:01 ` Don Breazeal
2016-04-04 10:42 ` Yao Qi
2016-04-04 17:16 ` Don Breazeal
2016-04-04 21:28 ` Don Breazeal
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=86vb45sdh5.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=donb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@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