This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] fortran: Testsuite, fix different type naming across compilers.
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Bernhard Heckel <bernhard dot heckel at intel dot com>
- Cc: keiths at redhat dot com, gdb-patches at sourceware dot org
- Date: Thu, 14 Apr 2016 10:22:19 +0100
- Subject: Re: [PATCH] fortran: Testsuite, fix different type naming across compilers.
- Authentication-results: sourceware.org; auth=none
- References: <1460615844-12363-1-git-send-email-bernhard dot heckel at intel dot com>
Bernhard Heckel <bernhard.heckel@intel.com> writes:
> +
> +if ![info exists int4] then {
> + set int4 "(int4|integer\\(kind=4\\)|INTEGER\\(4\\))"
> +}
I'd like to define a processing for each type, and return the right
thing according to the compiler info, like
proc fortran_int { } {
if {[test_compiler_info {gcc-4-1-*}]} {
return "int4"
} elseif {[test_compiler_info {gcc-4-[3-5]-*}]} {
return "integer\\(kind=4\\)"
} elseif { TEST_COMPILER_FOR_IFORT } {
return "INTEGER\\(4\\)"
} else {
....
}
}
however, I don't know how to do TEST_COMPILER_FOR_IFORT.
> \ No newline at end of file
Add a newline.
--
Yao (éå)