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] testsuite, fortran: Add '-debug-parameters all' when using ifx/ifort Date: Tue, 31 May 2022 14:45:59 +0000 (GMT) [thread overview] Message-ID: <20220531144559.0C1B4395A011@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4212a8c90777ba7c5fdc09d4022a1fb353851b4f commit 4212a8c90777ba7c5fdc09d4022a1fb353851b4f Author: Nils-Christian Kempke <nils-christian.kempke@intel.com> Date: Tue May 31 16:43:44 2022 +0200 testsuite, fortran: Add '-debug-parameters all' when using ifx/ifort In order for ifx and ifort to emit all debug entries, even for unused parameters in modules we have to define the '-debug-parameters all' flag. This commit adds it to the ifx-*/ifort-* specific flags in gdb.exp. Diff: --- gdb/testsuite/lib/gdb.exp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 87f0a36fe7d..402450152ac 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -4473,6 +4473,8 @@ proc gdb_compile {source dest type options} { # Place (and look for) Fortran `.mod` files in the output # directory for this specific test. For Intel compilers the -J # option is not supported so instead use the -module flag. + # Additionally, Intel compilers need the -debug-parameters flag set to + # emit debug info for all parameters in modules. if { !$getting_compiler_info && [lsearch -exact $options f90] != -1 } { # Fortran compile. set mod_path [standard_output_file ""] @@ -4481,6 +4483,7 @@ proc gdb_compile {source dest type options} { } elseif { [test_compiler_info {ifort-*} f90] || [test_compiler_info {ifx-*} f90] } { lappend new_options "additional_flags=-module ${mod_path}" + lappend new_options "additional_flags=-debug-parameters all" } }
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=20220531144559.0C1B4395A011@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).