From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: yao@codesourcery.com
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [PATCH] Fix kfail in gdb.base/callfuncs.exp
Date: Tue, 23 Oct 2012 08:36:00 -0000 [thread overview]
Message-ID: <201210230836.q9N8aZHO017504@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <50864048.4010400@codesourcery.com> (message from Yao Qi on Tue, 23 Oct 2012 14:59:20 +0800)
> Date: Tue, 23 Oct 2012 14:59:20 +0800
> From: Yao Qi <yao@codesourcery.com>
>
> On 10/15/2012 07:46 PM, Yao Qi wrote:
> > gdb/testsuite:
> >
> > 2012-10-15 Yao Qi<yao@codesourcery.com>
> >
> > * gdb.base/callfuncs.exp (do_function_calls): KFAIL some test
> > for x86 with -m64.
>
> Ping. http://sourceware.org/ml/gdb-patches/2012-10/msg00212.html
I don't think decoupling the triplet from the setup_kfail this way is
a good idea.
next prev parent reply other threads:[~2012-10-23 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 11:46 Yao Qi
2012-10-23 6:59 ` ping: " Yao Qi
2012-10-23 8:36 ` Mark Kettenis [this message]
2012-10-23 10:06 ` Yao Qi
2012-10-23 18:22 ` Mark Kettenis
2012-10-24 7:45 ` Yao Qi
2012-10-23 18:41 ` Tom Tromey
2012-10-24 7:43 ` Yao Qi
2012-10-24 14:56 ` Tom Tromey
2012-10-25 14:55 ` Yao Qi
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=201210230836.q9N8aZHO017504@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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