From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] testsuite: Remove KFAILs for c++/11702
Date: Tue, 29 Jun 2010 21:14:00 -0000 [thread overview]
Message-ID: <20100629211447.GA9907@host0.dyn.jankratochvil.net> (raw)
Hi,
now that c++/11702 is fixed I believe we should remove its KFAILs.
Tested on x86_64-fedora13-linux-gnu on updates,{-testing} and with GCC HEAD.
Probably obvious but asking for approval.
Thanks,
Jan
2010-06-29 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.cp/namespace.exp (print C::OtherFileClass::cOtherFileClassVar)
(print ::C::OtherFileClass::cOtherFileClassVar): Remove KFAIL for
c++/11702.
--- a/gdb/testsuite/gdb.cp/namespace.exp
+++ b/gdb/testsuite/gdb.cp/namespace.exp
@@ -186,17 +186,7 @@ if {[test_compiler_info {gcc-[0-3]-*}]
setup_xfail *-*-*
}
gdb_test "whatis ::C::OtherFileClass::cOtherFileClassType" "type = short"
-
-set test "print C::OtherFileClass::cOtherFileClassVar"
-gdb_test_multiple $test $test {
- -re "\\$\[0-9\].* = 318\r\n$gdb_prompt $" {
- pass $test
- }
- -re "static field cOtherFileClassVar has been optimized out\r\n$gdb_prompt $" {
- setup_kfail "c++/11702" "*-*-*"
- fail $test
- }
-}
+gdb_test "print C::OtherFileClass::cOtherFileClassVar" " = 318"
# FSF GCC <=4.4 creates unqualified DIE "cOtherFileClassVar" ignoring the
# namespace the same way older GDB did.
@@ -206,16 +196,7 @@ gdb_test_multiple $test $test {
-re "No symbol \"cOtherFileClassVar\" in current context\\.\r\n$gdb_prompt $" {
pass $test
- gdb_test_multiple $test2 $test2 {
- -re "\\$\[0-9\].* = 318\r\n$gdb_prompt $" {
- pass $test2
- }
- -re "static field cOtherFileClassVar has been optimized out\r\n$gdb_prompt $" {
- setup_kfail "c++/11702" "*-*-*"
- fail $test2
- }
- }
-
+ gdb_test $test2 " = 318"
}
-re "\\$\[0-9\].* = 318\r\n$gdb_prompt $" {
if {[test_compiler_info {gcc-[0-3]-*}]
next reply other threads:[~2010-06-29 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 21:14 Jan Kratochvil [this message]
2010-06-30 15:35 ` Tom Tromey
2010-06-30 15:59 ` Jan Kratochvil
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=20100629211447.GA9907@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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