From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH V2 0/2] fortran: Testsuite, fix different type naming across compilers.
Date: Fri, 15 Apr 2016 12:46:00 -0000 [thread overview]
Message-ID: <1460724297-23523-1-git-send-email-bernhard.heckel@intel.com> (raw)
This patch series supports detection of Intel compilers and fixes
failing fortran testcases due to different type naming.
Bernhard Heckel (2):
testsuite: Support detection of Intel compilers via
test_compiler_version.
fortran: Testsuite, fix different type naming across compilers.
gdb/testsuite/gdb.fortran/common-block.exp | 5 +-
gdb/testsuite/gdb.fortran/derived-type.exp | 13 ++---
gdb/testsuite/gdb.fortran/multi-dim.exp | 8 +--
gdb/testsuite/gdb.fortran/vla-datatypes.exp | 9 +--
gdb/testsuite/gdb.fortran/vla-ptype-sub.exp | 33 +++++------
gdb/testsuite/gdb.fortran/vla-ptype.exp | 21 +++----
gdb/testsuite/gdb.fortran/whatis_type.exp | 5 +-
gdb/testsuite/lib/compiler.c | 12 ++++
gdb/testsuite/lib/compiler.cc | 12 ++++
gdb/testsuite/lib/fortran.exp | 88 +++++++++++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 3 +
11 files changed, 158 insertions(+), 51 deletions(-)
mode change 100644 => 100755 gdb/testsuite/lib/compiler.c
mode change 100644 => 100755 gdb/testsuite/lib/compiler.cc
--
2.7.1.339.g0233b80
next reply other threads:[~2016-04-15 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 12:46 Bernhard Heckel [this message]
2016-04-15 12:47 ` [PATCH V2 2/2] " Bernhard Heckel
2016-04-15 14:41 ` Yao Qi
2016-04-18 7:15 ` Heckel, Bernhard
2016-04-15 12:47 ` [PATCH V2 1/2] testsuite: Support detection of Intel compilers via test_compiler_version Bernhard Heckel
2016-04-15 15:00 ` Yao Qi
2016-04-18 6:26 ` Heckel, Bernhard
2016-04-18 9:29 ` 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=1460724297-23523-1-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).