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] Replace remaining -gt with -gctf
Date: Wed, 12 Oct 2022 15:02:21 +0000 (GMT)	[thread overview]
Message-ID: <20221012150221.D3A573851400@sourceware.org> (raw)

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

commit 3c74d321be66cb94bbdeb7da36111b46d2f4a578
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Oct 12 17:02:15 2022 +0200

    [gdb/testsuite] Replace remaining -gt with -gctf
    
    With test-cases gdb.base/cvexpr.exp and gdb.base/whatis.exp I run into:
    ...
    gdb compile failed, gcc: error: unrecognized debug output level 't'
    ...
    
    This is due to using additional_flags=-gt.
    
    Commit ffb3f587933 ("CTF: multi-CU and archive support") replaced
    additional_flags=-gt with additional_flags=-gctf in gdb.ctf/*.exp and
    gdb.base/ctf-*.exp.
    
    Do the same in these two test-cases.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.base/cvexpr.exp | 2 +-
 gdb/testsuite/gdb.base/whatis.exp | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.base/cvexpr.exp b/gdb/testsuite/gdb.base/cvexpr.exp
index e7ff730e92f..d8437b94c61 100644
--- a/gdb/testsuite/gdb.base/cvexpr.exp
+++ b/gdb/testsuite/gdb.base/cvexpr.exp
@@ -494,7 +494,7 @@ proc do_test {dir options} {
 # Build up the set of debug formats for which we will run this test.
 set specs { {dwarf {debug}} }
 if ![skip_ctf_tests] {
-    lappend specs {ctf {"additional_flags=-gt"}}
+    lappend specs {ctf {"additional_flags=-gctf"}}
 }
 
 # Setup and run the test for each debug format.
diff --git a/gdb/testsuite/gdb.base/whatis.exp b/gdb/testsuite/gdb.base/whatis.exp
index 2bce3f5cdcb..c19c149f012 100644
--- a/gdb/testsuite/gdb.base/whatis.exp
+++ b/gdb/testsuite/gdb.base/whatis.exp
@@ -588,7 +588,7 @@ proc do_test {dir options} {
 # Build up the set of debug formats for which we will run this test.
 set specs { {dwarf {debug}} }
 if ![skip_ctf_tests] {
-    lappend specs {ctf {"additional_flags=-gt"}}
+    lappend specs {ctf {"additional_flags=-gctf"}}
 }
 
 # Setup and run the test for each debug format.

                 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=20221012150221.D3A573851400@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: 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).