From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Bernhard Heckel <bernhard.heckel@intel.com>
Subject: RE: [PATCH v3 3/6] Fortran: Ptype, print type extension.
Date: Thu, 24 Aug 2017 12:36:00 -0000 [thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF636294C3@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <86fucir1cg.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1887 bytes --]
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Yao Qi
> Sent: Wednesday, August 23, 2017 1:05 PM
> To: Wiederhake, Tim <tim.wiederhake@intel.com>
> Cc: gdb-patches@sourceware.org; Bernhard Heckel
> <bernhard.heckel@intel.com>
> Subject: Re: [PATCH v3 3/6] Fortran: Ptype, print type extension.
>
> Tim Wiederhake <tim.wiederhake@intel.com> writes:
>
> > +gdb_test_multiple $test %test {
>
> s/%test/$test
>
> > + -re "$output_pass\r\n$gdb_prompt $" {
> > + pass "$test"
> > + }
> > + -re "$output_xfail\r\n$gdb_prompt $" {
> > + xfail "gcc/49475"
> > + }
> > +}
> > set test "ptype wp%coo"
> > gdb_test_multiple "$test" "$test" {
> > -re "$real \\(3\\)\r\n$gdb_prompt $" {
> > @@ -80,11 +92,15 @@ gdb_test "p wp_vla(1)%point" " = \\( coo = \\(10,
> 12, 10\\) \\)"
> > gdb_test "p wp_vla(1)" " = \\( point = \\( coo = \\(10, 12, 10\\) \\),
> angle = 101 \\)"
> >
> > gdb_test "whatis wp_vla" "type = Type waypoint \\(3\\)"
> > -gdb_test "ptype wp_vla" \
> > - [multi_line "type = Type waypoint" \
> > - " Type point :: point" \
> > - " $real :: angle" \
> > - "End Type waypoint \\(3\\)"]
> > +set test "ptype wp_vla"
> > +gdb_test_multiple $test %test {
>
> Likewise.
Both applied locally.
> Patch is good to me.
Thanks!
Now #1 and #3 are OK'd;
#2, #4, #5, #6 still need review.
Regards,
Tim
>
> --
> Yao (é½å°§)
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
\x16º&Öéj×!zÊÞ¶êç×uïib²Ö«r\x18\x1dnr\x17¬
prev parent reply other threads:[~2017-08-24 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:07 [PATCH v3 0/6] Some Fortran Patches Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 5/6] Fortran: Enable setting breakpoint on nested functions Tim Wiederhake
2017-09-04 9:22 ` Yao Qi
2017-08-11 11:07 ` [PATCH v3 1/6] DWARF: Don't add nameless modules to partial symbol table Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 2/6] Fortran: Accessing fields of inherited types via fully qualified name Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 4/6] Dwarf: Fortran, support DW_TAG_entry_point Tim Wiederhake
2017-09-04 8:37 ` Yao Qi
2017-08-11 11:07 ` [PATCH v3 6/6] Fortran: Nested functions, add scope parameter Tim Wiederhake
2017-09-04 9:58 ` Yao Qi
2017-09-08 12:13 ` Wiederhake, Tim
2017-08-11 11:07 ` [PATCH v3 3/6] Fortran: Ptype, print type extension Tim Wiederhake
2017-08-23 11:05 ` Yao Qi
2017-08-24 12:36 ` Wiederhake, Tim [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=9676A094AF46E14E8265E7A3F4CCE9AF636294C3@IRSMSX106.ger.corp.intel.com \
--to=tim.wiederhake@intel.com \
--cc=bernhard.heckel@intel.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