From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2205) id 38BF0387102A; Sat, 14 Mar 2020 09:41:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 38BF0387102A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1584178909; bh=wKs+UMYPqt1zxwIvnXTRpLhlzvm0BiQ2+JiFFu6uuWY=; h=From:To:Subject:Date:From; b=kcgEDv1fAg9hrpT8WiqjIp7T9sqNbDOWAh3AsdT2R4nsfym2rJBTtp33g5hRPu5oE iuuVezgzWFVzmjzKC66X58kv0fNwoBewIYEpXvxtB9OyCJPaahE3IYNEfbhxXUkAwU xzndwLb3v6FK2xzBltlQbmq2ed1HXOtjRcLtdhT0= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Tom de Vries To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix unrecognized debug output level 'statement-frontiers' message X-Act-Checkin: binutils-gdb X-Git-Author: Tom de Vries X-Git-Refname: refs/heads/master X-Git-Oldrev: 09546b56ede31ca2b401e9b03466e8e1fb84d85f X-Git-Newrev: 2ac70237d2458fb2eb5e73de6bb02a396b5bada0 Message-Id: <20200314094149.38BF0387102A@sourceware.org> Date: Sat, 14 Mar 2020 09:41:49 +0000 (GMT) X-BeenThere: gdb-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Mar 2020 09:41:49 -0000 https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2ac70237d2458fb2eb5e73de6bb02a396b5bada0 commit 2ac70237d2458fb2eb5e73de6bb02a396b5bada0 Author: Tom de Vries Date: Sat Mar 14 10:41:46 2020 +0100 [gdb/testsuite] Fix unrecognized debug output level 'statement-frontiers' message When running testcase gdb.cp/step-and-next-inline.exp, I get: ... Running src/gdb/testsuite/gdb.cp/step-and-next-inline.exp ... gdb compile failed, g++: error: unrecognized debug output level \ 'statement-frontiers' gdb compile failed, g++: error: unrecognized debug output level \ 'statement-frontiers' === gdb Summary === # of untested testcases 2 ... Fix this by using a new gdb_caching_proc supports_statement_frontiers. Tested on x86_64-linux, with gcc 7.5.0 (which does not support -gstatement-frontiers) and with gcc 8.4.0 (which does support -gstatement-frontiers). gdb/testsuite/ChangeLog: 2020-03-14 Tom de Vries * lib/gdb.exp (supports_statement_frontiers): New proc. * gdb.cp/step-and-next-inline.exp: Use supports_statement_frontiers. Diff: --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.cp/step-and-next-inline.exp | 4 ++++ gdb/testsuite/lib/gdb.exp | 11 +++++++++++ 3 files changed, 20 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 9f65a4eaa82..a9c28522511 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-03-14 Tom de Vries + + * lib/gdb.exp (supports_statement_frontiers): New proc. + * gdb.cp/step-and-next-inline.exp: Use supports_statement_frontiers. + 2020-03-14 Tom de Vries * gdb.base/printcmds.exp: Add missing quoting for "print diff --git a/gdb/testsuite/gdb.cp/step-and-next-inline.exp b/gdb/testsuite/gdb.cp/step-and-next-inline.exp index acec48ba81d..3733fa75570 100644 --- a/gdb/testsuite/gdb.cp/step-and-next-inline.exp +++ b/gdb/testsuite/gdb.cp/step-and-next-inline.exp @@ -15,6 +15,10 @@ standard_testfile .cc +if { ![supports_statement_frontiers] } { + return -1 +} + # Compile the test source with USE_NEXT_INLINE_H defined (when # use_header is true), or not defined. proc do_test { use_header } { diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index ae2d810a1eb..b14b3a968e1 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -6947,5 +6947,16 @@ gdb_caching_proc skip_ctf_tests { } executable "additional_flags=-gt"] } +# Return 1 if compiler supports -gstatement-frontiers. Otherwise, +# return 0. + +gdb_caching_proc supports_statement_frontiers { + return [gdb_can_simple_compile supports_statement_frontiers { + int main () { + return 0; + } + } executable "additional_flags=-gstatement-frontiers"] +} + # Always load compatibility stuff. load_lib future.exp