From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp]
Date: Wed, 24 Oct 2012 13:48:00 -0000 [thread overview]
Message-ID: <20121024134828.GA24180@host2.jankratochvil.net> (raw)
In-Reply-To: <201210231827.q9NIRdld028342@glazunov.sibelius.xs4all.nl>
On Tue, 23 Oct 2012 20:27:40 +0200, Mark Kettenis wrote:
> Just fixed the bugs. Committed as obvious.
It is a testsuite results regression in -m32 mode:
--- 20121023Build-gdbcvs-f18/fedora-18-x86_64/out/gdb-m32.sum 2012-10-23 03:34:35.546531678 +0200
+++ 20121024Build-gdbcvs-f18/fedora-18-x86_64/out/gdb-m32.sum 2012-10-24 03:52:42.269267826 +0200
-KPASS: gdb.base/callfuncs.exp: call inferior func with struct - returns float _Complex (PRMS gdb/12796)
-KFAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns double _Complex (PRMS: gdb/12796)
-KFAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns long double _Complex (PRMS: gdb/12796)
+PASS: gdb.base/callfuncs.exp: call inferior func with struct - returns float _Complex
+FAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns double _Complex
+FAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns long double _Complex
This is because setup_kfail_for_target is broken by design.
Checked in its workaround.
There are more incorrect uses of setup_kfail_for_target but they already KPASS
so asked in BZ for them:
http://sourceware.org/bugzilla/show_bug.cgi?id=13808#c1
http://sourceware.org/bugzilla/show_bug.cgi?id=12790#c1
Regards,
Jan
http://sourceware.org/ml/gdb-cvs/2012-10/msg00100.html
--- src/gdb/testsuite/ChangeLog 2012/10/23 18:25:24 1.3423
+++ src/gdb/testsuite/ChangeLog 2012/10/24 13:45:50 1.3424
@@ -1,3 +1,8 @@
+2012-10-24 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * gdb.base/callfuncs.exp (do_function_calls): Fix
+ setup_kfail_for_target for -m32 mode.
+
2012-10-23 Mark Kettenis <kettenis@gnu.org>
* gdb.base/callfuncs.exp: PR gdb/12796, gdb/12798 and gdb/12800
--- src/gdb/testsuite/gdb.base/callfuncs.exp 2012/10/23 18:25:25 1.54
+++ src/gdb/testsuite/gdb.base/callfuncs.exp 2012/10/24 13:45:51 1.55
@@ -245,11 +245,15 @@
gdb_test "p t_structs_fc(struct_val1)" ".*= 3 \\+ 3 \\* I" \
"call inferior func with struct - returns float _Complex"
- setup_kfail_for_target gdb/12783 "i?86-*-*"
+ if [is_x86_like_target] {
+ setup_kfail gdb/12783 "*-*-*"
+ }
gdb_test "p t_structs_dc(struct_val1)" ".*= 4 \\+ 4 \\* I" \
"call inferior func with struct - returns double _Complex"
- setup_kfail_for_target gdb/12783 "i?86-*-*"
+ if [is_x86_like_target] {
+ setup_kfail gdb/12783 "*-*-*"
+ }
gdb_test "p t_structs_ldc(struct_val1)" "= 5 \\+ 5 \\* I" \
"call inferior func with struct - returns long double _Complex"
}
next prev parent reply other threads:[~2012-10-24 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:27 [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp Mark Kettenis
2012-10-24 13:48 ` Jan Kratochvil [this message]
2012-10-24 14:35 ` [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp] Mark Kettenis
2012-10-24 14:50 ` Jan Kratochvil
2012-10-24 15:05 ` Mark Kettenis
2012-10-24 16:19 ` Tom Tromey
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=20121024134828.GA24180@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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