public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Silence warnings about obsolete -gstabs Date: Wed, 12 Oct 2022 15:02:26 +0000 (GMT) [thread overview] Message-ID: <20221012150226.E51CC3851164@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=632ecf33a181029be7f1b7efdc687fd3dbb1a1d0 commit 632ecf33a181029be7f1b7efdc687fd3dbb1a1d0 Author: Tom de Vries <tdevries@suse.de> Date: Wed Oct 12 17:02:15 2022 +0200 [gdb/testsuite] Silence warnings about obsolete -gstabs When running test-case gdb.base/gdbindex-stabs.exp on openSUSE Tumbleweed (with gcc 12) I get: ... gdb compile failed, gdb/testsuite/gdb.base/gdbindex-stabs.c: warning: \ STABS debugging information is obsolete and not supported anymore ... Silence the warning by passing quiet to gdb_compile. Likewise in two other test-cases. Diff: --- gdb/testsuite/gdb.base/gdbindex-stabs.exp | 2 +- gdb/testsuite/gdb.dwarf2/dw2-ranges.exp | 2 +- gdb/testsuite/gdb.stabs/gdb11479.exp | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gdb/testsuite/gdb.base/gdbindex-stabs.exp b/gdb/testsuite/gdb.base/gdbindex-stabs.exp index 955666d6323..2df8fe9fe44 100644 --- a/gdb/testsuite/gdb.base/gdbindex-stabs.exp +++ b/gdb/testsuite/gdb.base/gdbindex-stabs.exp @@ -21,7 +21,7 @@ set srcfile_dwarf ${testfile}-dwarf.c set objfile_stabs [standard_output_file ${testfile}.o] set objfile_dwarf [standard_output_file ${testfile}-dwarf.o] -if {[gdb_compile "${srcdir}/${subdir}/${srcfile_stabs}" ${objfile_stabs} object {additional_flags=-gstabs}] != "" +if {[gdb_compile "${srcdir}/${subdir}/${srcfile_stabs}" ${objfile_stabs} object {additional_flags=-gstabs quiet}] != "" || [gdb_compile "${srcdir}/${subdir}/${srcfile_dwarf}" ${objfile_dwarf} object {additional_flags=-gdwarf-2}] != "" || [gdb_compile "${objfile_stabs} ${objfile_dwarf}" ${binfile} executable {nodebug}] != ""} { untested "failed to compile" diff --git a/gdb/testsuite/gdb.dwarf2/dw2-ranges.exp b/gdb/testsuite/gdb.dwarf2/dw2-ranges.exp index e2d6d75044c..b7b3223b587 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-ranges.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-ranges.exp @@ -51,7 +51,7 @@ if {[gdb_compile "${srcdir}/${subdir}/${srcfile2}" "${asmfile2}" assembly {}] != # STABS compilation is intentional as it tests the STABS lookup where is no # partial_symtab->psymtabs_addrmap supported for that CU (Compilation Unit) in # a file containing psymtabs_addrmap-supporting DWARF CUs. -if {[gdb_compile "${srcdir}/${subdir}/${srcfile3}" "${objfile3}" object {additional_flags=-gstabs}] != "" } { +if {[gdb_compile "${srcdir}/${subdir}/${srcfile3}" "${objfile3}" object {additional_flags=-gstabs quiet}] != "" } { return -1 } diff --git a/gdb/testsuite/gdb.stabs/gdb11479.exp b/gdb/testsuite/gdb.stabs/gdb11479.exp index c7a8c5b1738..f7231a6ee16 100644 --- a/gdb/testsuite/gdb.stabs/gdb11479.exp +++ b/gdb/testsuite/gdb.stabs/gdb11479.exp @@ -39,7 +39,7 @@ proc do_test {version} { gdb_test "print sizeof (*e)" "= \[1-9\]*" "sizeof (*e) in test $version" } -if { [prepare_for_testing "failed to prepare" $testfile $testfile.c {debug additional_flags=-gstabs}] == 0 } { +if { [prepare_for_testing "failed to prepare" $testfile $testfile.c {debug additional_flags=-gstabs quiet}] == 0 } { do_test forced_stabs }
reply other threads:[~2022-10-12 15:02 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=20221012150226.E51CC3851164@sourceware.org \ --to=vries@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).