Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jiang Jilin <freephp@gmail.com>
Cc: Hui Zhu <teawater@gmail.com>, Michael Snyder <msnyder@vmware.com>,
		gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add xgetbv/xsetbv instructions support for precord.
Date: Sat, 10 Oct 2009 04:59:00 -0000	[thread overview]
Message-ID: <20091010045945.GF5272@adacore.com> (raw)
In-Reply-To: <7d77a27d0910091945l1de79c02u1f111bd3b193b144@mail.gmail.com>

> Another question: when to verify whether regression occurs, is 'make
> check' enough? or have to test all other *.exp in
> /usr/share/dejagnu/baseboards?

No, just once run before and one run after with the same board file
should be enough.

Just because I'm not familiar with these board files, wouldn't it
have been nice to have the information directly embedded somewhere
in the GDB testsuite library? At AdaCore, our own gdb-testsuite
knows what each target supports, so it knows whether a test might
be relevant or not.  From what I can tell, the testsuite does not
run the precord testcases unless I use the precord.exp board file.

-- 
Joel


  reply	other threads:[~2009-10-10  4:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 13:37 Jiang Jilin
2009-10-09 17:21 ` Joel Brobecker
     [not found]   ` <7d77a27d0910091838l76217714m92a55afc2fdf25f3@mail.gmail.com>
2009-10-10  2:33     ` Joel Brobecker
2009-10-10  2:46       ` Jiang Jilin
2009-10-10  4:59         ` Joel Brobecker [this message]
2009-10-10  7:57       ` Hui Zhu
2009-10-10  8:10         ` Jiang Jilin
2009-10-10  8:14         ` Jiang Jilin
2009-10-09 22:26 ` Michael Snyder
2009-10-12  8:00   ` Jiang Jilin
2009-10-12 15:43     ` Michael Snyder
2009-10-13  8:48       ` Jiang Jilin

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=20091010045945.GF5272@adacore.com \
    --to=brobecker@adacore.com \
    --cc=freephp@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=teawater@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