From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH 3/4] fortran: Testsuite, fix typos in vla-value.
Date: Mon, 21 Aug 2017 12:20:00 -0000 [thread overview]
Message-ID: <1503317966-12486-4-git-send-email-tim.wiederhake@intel.com> (raw)
In-Reply-To: <1503317966-12486-1-git-send-email-tim.wiederhake@intel.com>
From: Bernhard Heckel <bernhard.heckel@intel.com>
xxxx-yy-zz Bernhard Heckel <bernhard.heckel@intel.com>
gdb/testsuite/ChangeLog:
* gdb.fortran/vla-ptype.exp: Fix typos.
* gdb.fortran/vla-value.exp: Same.
---
gdb/testsuite/gdb.fortran/vla-ptype.exp | 6 +++---
gdb/testsuite/gdb.fortran/vla-value.exp | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/testsuite/gdb.fortran/vla-ptype.exp b/gdb/testsuite/gdb.fortran/vla-ptype.exp
index 2dd51e5..c8e72e9 100644
--- a/gdb/testsuite/gdb.fortran/vla-ptype.exp
+++ b/gdb/testsuite/gdb.fortran/vla-ptype.exp
@@ -39,7 +39,7 @@ gdb_test "ptype vla1(3, 6, 9)" "no such vector element \\\(vector not allocated\
"ptype vla1(3, 6, 9) not initialized"
gdb_test "ptype vla2(5, 45, 20)" \
"no such vector element \\\(vector not allocated\\\)" \
- "ptype vla1(5, 45, 20) not initialized"
+ "ptype vla2(5, 45, 20) not initialized"
gdb_breakpoint [gdb_get_line_number "vla1-allocated"]
gdb_continue_to_breakpoint "vla1-allocated"
@@ -63,7 +63,7 @@ gdb_continue_to_breakpoint "vla2-filled"
gdb_test "ptype vla2" "type = $real \\\(7,42:50,13:35\\\)" \
"ptype vla2 filled"
gdb_test "ptype vla2(5, 45, 20)" "type = $real" \
- "ptype vla1(5, 45, 20) filled"
+ "ptype vla2(5, 45, 20) filled"
gdb_breakpoint [gdb_get_line_number "pvla-associated"]
gdb_continue_to_breakpoint "pvla-associated"
@@ -77,7 +77,7 @@ gdb_continue_to_breakpoint "pvla-re-associated"
gdb_test "ptype pvla" "type = $real \\\(7,42:50,13:35\\\)" \
"ptype pvla re-associated"
gdb_test "ptype vla2(5, 45, 20)" "type = $real" \
- "ptype vla1(5, 45, 20) re-associated"
+ "ptype vla2(5, 45, 20) re-associated"
gdb_breakpoint [gdb_get_line_number "pvla-deassociated"]
gdb_continue_to_breakpoint "pvla-deassociated"
diff --git a/gdb/testsuite/gdb.fortran/vla-value.exp b/gdb/testsuite/gdb.fortran/vla-value.exp
index 3dd1aae..60022c5 100644
--- a/gdb/testsuite/gdb.fortran/vla-value.exp
+++ b/gdb/testsuite/gdb.fortran/vla-value.exp
@@ -61,7 +61,7 @@ gdb_test "print &vla1" \
gdb_test "print vla1(3, 6, 9)" " = 1311" "print allocated vla1(3,6,9)"
gdb_test "print vla1(1, 3, 8)" " = 1311" "print allocated vla1(1,3,8)"
gdb_test "print vla1(9, 9, 9) = 999" " = 999" \
- "print allocated vla1(9,9,9)=1"
+ "print allocated vla1(9,9,9)=999"
# Try to access values in allocated VLA after specific assignment
gdb_breakpoint [gdb_get_line_number "vla1-filled"]
--
2.7.4
next prev parent reply other threads:[~2017-08-21 12:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 12:20 [PATCH 0/4] More Fortran Patches Tim Wiederhake
2017-08-21 12:20 ` [PATCH 1/4] Fix indentation for printing Fortran types with pointers Tim Wiederhake
2017-09-04 13:35 ` Yao Qi
2017-09-08 13:19 ` Wiederhake, Tim
2017-08-21 12:20 ` Tim Wiederhake [this message]
2017-09-04 13:26 ` [PATCH 3/4] fortran: Testsuite, fix typos in vla-value Yao Qi
2017-09-08 13:17 ` Wiederhake, Tim
2017-08-21 12:20 ` [PATCH 2/4] Fortran: Testsuite, fix differences in type naming Tim Wiederhake
2017-09-04 13:25 ` Yao Qi
2017-09-08 13:17 ` Wiederhake, Tim
2017-08-21 12:20 ` [PATCH 4/4] Remove C/C++ relevant code in Fortran specific file Tim Wiederhake
2017-09-04 13:32 ` Yao Qi
2017-09-08 13:18 ` Wiederhake, Tim
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=1503317966-12486-4-git-send-email-tim.wiederhake@intel.com \
--to=tim.wiederhake@intel.com \
--cc=bernhard.heckel@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).