public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: remove get_compiler_info calls from gdb.exp and dwarf.exp Date: Thu, 9 Jun 2022 13:41:20 +0000 (GMT) [thread overview] Message-ID: <20220609134120.C29D1383DB88@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1562f64fec2ce6a31bc534be73e9e4180edbb600 commit 1562f64fec2ce6a31bc534be73e9e4180edbb600 Author: Andrew Burgess <aburgess@redhat.com> Date: Wed Jun 8 14:25:00 2022 +0100 gdb/testsuite: remove get_compiler_info calls from gdb.exp and dwarf.exp We don't need to call get_compiler_info before calling test_compiler_info; test_compiler_info includes a call to get_compiler_info. This commit cleans up lib/gdb.exp and lib/dwarf.exp a little by removing some unneeded calls to get_compiler_info. We could do the same cleanup throughout the testsuite, but I'm leaving that for another day. There should be no change in the test results after this commit. Diff: --- gdb/testsuite/lib/dwarf.exp | 8 -------- gdb/testsuite/lib/gdb.exp | 23 +---------------------- 2 files changed, 1 insertion(+), 30 deletions(-) diff --git a/gdb/testsuite/lib/dwarf.exp b/gdb/testsuite/lib/dwarf.exp index b05fdd58f66..3d0ea83aee7 100644 --- a/gdb/testsuite/lib/dwarf.exp +++ b/gdb/testsuite/lib/dwarf.exp @@ -110,14 +110,6 @@ proc build_executable_and_dwo_files { testname executable options args } { set binfile $executable } - set info_options "" - if { [lsearch -exact $options "c++"] >= 0 } { - set info_options "c++" - } - if [get_compiler_info ${info_options}] { - return -1 - } - set func gdb_compile if {[lsearch -regexp $options \ {^(pthreads|shlib|shlib_pthreads|openmp)$}] != -1} { diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 7b11dab870e..c9a30d88b2f 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -3238,10 +3238,6 @@ gdb_caching_proc skip_altivec_tests { } # Make sure we have a compiler that understands altivec. - if [get_compiler_info] { - warning "Could not get compiler info" - return 1 - } if [test_compiler_info gcc*] { set compile_flags "additional_flags=-maltivec" } elseif [test_compiler_info xlc*] { @@ -3357,10 +3353,6 @@ gdb_caching_proc skip_vsx_tests { } # Make sure we have a compiler that understands altivec. - if [get_compiler_info] { - warning "Could not get compiler info" - return 1 - } if [test_compiler_info gcc*] { set compile_flags "additional_flags=-mvsx" } elseif [test_compiler_info xlc*] { @@ -4781,11 +4773,8 @@ proc gdb_compile_shlib_1 {sources dest options} { } elseif { [lsearch -exact $options "f90"] >= 0 } { set info_options "f90" } - if [get_compiler_info ${info_options}] { - return -1 - } - switch -glob [test_compiler_info] { + switch -glob [test_compiler_info "" ${info_options}] { "xlc-*" { lappend obj_options "additional_flags=-qpic" } @@ -6964,16 +6953,6 @@ proc build_executable_from_specs {testname executable options args} { set binfile [standard_output_file $executable] - set info_options "" - if { [lsearch -exact $options "c++"] >= 0 } { - set info_options "c++" - } elseif { [lsearch -exact $options "f90"] >= 0 } { - set info_options "f90" - } - if [get_compiler_info ${info_options}] { - return -1 - } - set func gdb_compile set func_index [lsearch -regexp $options {^(pthreads|shlib|shlib_pthreads|openmp)$}] if {$func_index != -1} {
reply other threads:[~2022-06-09 13:41 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=20220609134120.C29D1383DB88@sourceware.org \ --to=aburgess@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).