From: Yao Qi <qiyaoltc@gmail.com>
To: Bernhard Heckel <bernhard.heckel@intel.com>
Cc: keiths@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] fortran: Testsuite, fix different type naming across compilers.
Date: Thu, 14 Apr 2016 09:22:00 -0000 [thread overview]
Message-ID: <868u0go88k.fsf@gmail.com> (raw)
In-Reply-To: <1460615844-12363-1-git-send-email-bernhard.heckel@intel.com> (Bernhard Heckel's message of "Thu, 14 Apr 2016 08:37:24 +0200")
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 (齐尧)
prev parent reply other threads:[~2016-04-14 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 6:37 Bernhard Heckel
2016-04-14 9:22 ` Yao Qi [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=868u0go88k.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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