From: Luis Machado <lgustavo@codesourcery.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [BZ 21005] Add support for Intel 64 rdrand and rdseed record/replay
Date: Mon, 16 Jan 2017 19:30:00 -0000 [thread overview]
Message-ID: <4bc2fb38-49be-09cf-bb18-e5c1a9401628@codesourcery.com> (raw)
In-Reply-To: <20170113121620.GA28060@E107787-LIN>
On 01/13/2017 06:16 AM, Yao Qi wrote:
> On 17-01-13 02:58:11, Luis Machado wrote:
>>
>> I tested this by hand with quite a few lines of inline asm. I thought we
>> had arch-specific tests in testsuite/, but it looks like we don't exercise
>> every little instruction with record/replay, so no testcase. Let me know
>> if one is required.
>>
>
> gdb.reverse/insn-reverse.exp is intended to exercise each instruction with
> record/replay. You can add the instructions in gdb.reverse/insn-reverse.c.
>
I've sent an RFC for gdb.reverse/insn-reverse.c. Meanwhile i've fixed a
gotcha with this patch and have a working testcase, pending the
approval/disapproval of the RFC.
prev parent reply other threads:[~2017-01-16 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:58 Luis Machado
2017-01-13 12:16 ` Yao Qi
2017-01-16 19:30 ` Luis Machado [this message]
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=4bc2fb38-49be-09cf-bb18-e5c1a9401628@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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