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: Use -module option for Intel Fortran compilers
Date: Tue, 31 May 2022 14:45:18 +0000 (GMT)	[thread overview]
Message-ID: <20220531144518.787123857C6F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7c07eaec49caa6599401e3f27a23ee37862ed7b2

commit 7c07eaec49caa6599401e3f27a23ee37862ed7b2
Author: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
Date:   Tue May 31 16:43:43 2022 +0200

    gdb/testsuite: Use -module option for Intel Fortran compilers
    
    The '-J' option is not supported in Intel compilers (ifx and ifort).
    The Intel version of the flag is '-module' which serves the same purpose.

Diff:
---
 gdb/testsuite/lib/gdb.exp | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 746f0cf779c..6fbf74442c9 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -4458,12 +4458,16 @@ proc gdb_compile {source dest type options} {
     }
 
     # Place (and look for) Fortran `.mod` files in the output
-    # directory for this specific test.
+    # directory for this specific test.  For Intel compilers the -J
+    # option is not supported so instead use the -module flag.
     if { [lsearch -exact $options f90] != -1 } {
 	# Fortran compile.
 	set mod_path [standard_output_file ""]
 	if [test_compiler_info "gcc-*"] {
 	    lappend new_options "additional_flags=-J${mod_path}"
+	} elseif { [test_compiler_info {icc-*}]
+		   || [test_compiler_info {intel-*}] } {
+	    lappend new_options "additional_flags=-module ${mod_path}"
 	}
     }


                 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=20220531144518.787123857C6F@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: 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).