public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Nils-Christian Kempke <nckempke@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Fix fortran types for Intel compilers. Date: Tue, 31 May 2022 14:45:23 +0000 (GMT) [thread overview] Message-ID: <20220531144523.89FE0395A023@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c8df10fc707ec1f30767d96f508a99b8c0f901aa commit c8df10fc707ec1f30767d96f508a99b8c0f901aa Author: Felix Willgerodt <felix.willgerodt@intel.com> Date: Tue May 31 16:43:43 2022 +0200 gdb/testsuite: Fix fortran types for Intel compilers. Newer Intel compilers emit their dwarf type name in a slightly different format. Therefore, this needs adjustment to make more tests pass in the Fortran testsuite. Co-authored-by: Abdul Basit Ijaz <abdul.b.ijaz@intel.com> Co-authored-by: Nils-Christian Kempke <nils-christian.kempke@intel.com> Diff: --- gdb/testsuite/lib/fortran.exp | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/gdb/testsuite/lib/fortran.exp b/gdb/testsuite/lib/fortran.exp index a97c6eeb4e3..9531d393a1b 100644 --- a/gdb/testsuite/lib/fortran.exp +++ b/gdb/testsuite/lib/fortran.exp @@ -38,6 +38,8 @@ proc fortran_int4 {} { return "integer" } elseif {[test_compiler_info {icc-*}]} { return "INTEGER\\(4\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "INTEGER\\*4" } else { return "unknown" } @@ -52,6 +54,8 @@ proc fortran_int8 {} { return "integer\\*8" } elseif {[test_compiler_info {icc-*}]} { return "INTEGER\\(8\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "INTEGER\\*8" } else { return "unknown" } @@ -66,6 +70,8 @@ proc fortran_real4 {} { return "real" } elseif {[test_compiler_info {icc-*}]} { return "REAL\\(4\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "REAL\\*4" } else { return "unknown" } @@ -80,6 +86,8 @@ proc fortran_real8 {} { return "double precision" } elseif {[test_compiler_info {icc-*}]} { return "REAL\\(8\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "REAL\\*8" } else { return "unknown" } @@ -94,6 +102,8 @@ proc fortran_complex4 {} { return "complex" } elseif {[test_compiler_info {icc-*}]} { return "COMPLEX\\(4\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "COMPLEX\\*8" } else { return "unknown" } @@ -108,6 +118,8 @@ proc fortran_complex8 {} { return "double complex" } elseif {[test_compiler_info {icc-*}]} { return "COMPLEX\\(8\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "COMPLEX\\*16" } else { return "unknown" } @@ -122,6 +134,8 @@ proc fortran_complex16 {} { return "quad complex" } elseif {[test_compiler_info {icc-*}]} { return "COMPLEX\\(16\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "COMPLEX\\*32" } else { return "unknown" } @@ -136,6 +150,8 @@ proc fortran_logical4 {} { return "logical" } elseif {[test_compiler_info {icc-*}]} { return "LOGICAL\\(4\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "LOGICAL\\*4" } else { return "unknown" } @@ -150,6 +166,8 @@ proc fortran_character1 {} { return "character" } elseif {[test_compiler_info {icc-*}]} { return "CHARACTER\\(1\\)" + } elseif {[test_compiler_info {intel-*}]} { + return "CHARACTER\\*1" } else { return "unknown" }
reply other threads:[~2022-05-31 14:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220531144523.89FE0395A023@sourceware.org \ --to=nckempke@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).