From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Require c++11 where necessary
Date: Tue, 21 May 2019 14:34:00 -0000 [thread overview]
Message-ID: <20190521143405.GA21005@delia> (raw)
Hi,
When building gdb on ubuntu 16.04 with gcc 5.4.0, and running the gdb
testsuite we run into failures due test-cases requiring at least c++11.
Fix this by adding -std=c++11 to those test-cases.
Tested on x86_64-linux.
Committed to trunk.
Thanks,
- Tom
[gdb/testsuite] Require c++11 where necessary
gdb/testsuite/ChangeLog:
2019-05-21 Tom de Vries <tdevries@suse.de>
* gdb.arch/amd64-eval.exp: Require c++11.
* gdb.base/max-depth.exp: Same.
* gdb.compile/compile-cplus-array-decay.exp: Same.
* gdb.cp/meth-typedefs.exp: Same.
* gdb.cp/subtypes.exp: Same.
* gdb.cp/temargs.exp: Same.
---
gdb/testsuite/gdb.arch/amd64-eval.exp | 2 +-
gdb/testsuite/gdb.base/max-depth.exp | 3 +++
gdb/testsuite/gdb.compile/compile-cplus-array-decay.exp | 2 +-
gdb/testsuite/gdb.cp/meth-typedefs.exp | 3 ++-
gdb/testsuite/gdb.cp/subtypes.exp | 3 ++-
gdb/testsuite/gdb.cp/temargs.exp | 3 ++-
6 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/gdb/testsuite/gdb.arch/amd64-eval.exp b/gdb/testsuite/gdb.arch/amd64-eval.exp
index beef46ad13..4b5c28e7ce 100644
--- a/gdb/testsuite/gdb.arch/amd64-eval.exp
+++ b/gdb/testsuite/gdb.arch/amd64-eval.exp
@@ -20,7 +20,7 @@
standard_testfile .cc
if { [prepare_for_testing "failed to prepare" $testfile $srcfile \
- { debug c++ }] } {
+ { debug c++ additional_flags=-std=c++11 }] } {
return -1
}
diff --git a/gdb/testsuite/gdb.base/max-depth.exp b/gdb/testsuite/gdb.base/max-depth.exp
index b3b78762eb..99f3c98d8f 100644
--- a/gdb/testsuite/gdb.base/max-depth.exp
+++ b/gdb/testsuite/gdb.base/max-depth.exp
@@ -39,6 +39,9 @@ proc compile_and_run_tests { lang } {
# Create the additional flags.
set flags "debug"
lappend flags $lang
+ if { "$lang" == "c++" } {
+ lappend flags "additional_flags=-std=c++11"
+ }
set dir "$lang"
set binfile [standard_output_file ${dir}/${testfile}]
diff --git a/gdb/testsuite/gdb.compile/compile-cplus-array-decay.exp b/gdb/testsuite/gdb.compile/compile-cplus-array-decay.exp
index 80be4c2ac6..2f2f1c31af 100644
--- a/gdb/testsuite/gdb.compile/compile-cplus-array-decay.exp
+++ b/gdb/testsuite/gdb.compile/compile-cplus-array-decay.exp
@@ -25,7 +25,7 @@ if {[skip_cplus_tests]} {
}
if {[prepare_for_testing $testfile $testfile $srcfile \
- {debug nowarnings c++}]} {
+ {debug nowarnings c++ additional_flags=-std=c++11}]} {
return -1
}
diff --git a/gdb/testsuite/gdb.cp/meth-typedefs.exp b/gdb/testsuite/gdb.cp/meth-typedefs.exp
index 76a8fc9780..0883154584 100644
--- a/gdb/testsuite/gdb.cp/meth-typedefs.exp
+++ b/gdb/testsuite/gdb.cp/meth-typedefs.exp
@@ -35,7 +35,8 @@ if {[skip_cplus_tests]} { continue }
# Tests for c++/12266 et al
standard_testfile .cc
-if {[prepare_for_testing "failed to prepare" $testfile $srcfile {c++ debug}]} {
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile \
+ {c++ debug additional_flags=-std=c++11}]} {
return -1
}
diff --git a/gdb/testsuite/gdb.cp/subtypes.exp b/gdb/testsuite/gdb.cp/subtypes.exp
index 913006cf50..a0b6bcd0ef 100644
--- a/gdb/testsuite/gdb.cp/subtypes.exp
+++ b/gdb/testsuite/gdb.cp/subtypes.exp
@@ -23,7 +23,8 @@ load_lib "cp-support.exp"
standard_testfile .cc subtypes-2.cc
if {[prepare_for_testing "failed to prepare" $testfile \
- [list $srcfile $srcfile2] {debug c++}]} {
+ [list $srcfile $srcfile2] \
+ {debug c++ additional_flags=-std=c++11}]} {
return -1
}
diff --git a/gdb/testsuite/gdb.cp/temargs.exp b/gdb/testsuite/gdb.cp/temargs.exp
index 702e972ed6..a1fbaf1d11 100644
--- a/gdb/testsuite/gdb.cp/temargs.exp
+++ b/gdb/testsuite/gdb.cp/temargs.exp
@@ -23,7 +23,8 @@ if {[skip_cplus_tests]} {
standard_testfile .cc
-if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} {
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile \
+ {debug c++ additional_flags=-std=c++11}]} {
return -1
}
reply other threads:[~2019-05-21 14:34 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=20190521143405.GA21005@delia \
--to=tdevries@suse.de \
--cc=gdb-patches@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