public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: cgd@sibyte.com (Chris G. Demetriou)
To: fche@redhat.com (Frank Ch. Eigler)
Cc: gdb@sourceware.cygnus.com
Subject: Re: How to adequately test 'sim' changes?
Date: Fri, 01 Dec 2000 13:00:00 -0000	[thread overview]
Message-ID: <5tsno726y9.fsf@highland.sibyte.com> (raw)
In-Reply-To: <o5g0k7hnk8.fsf@toenail.toronto.redhat.com>

fche@redhat.com (Frank Ch. Eigler) writes:
> : (1) What's the recommended method for testing 'sim' changes?  the
> : sim subtree seems to have a minimal testsuite, but I was hoping for
> : something more substantial?
> 
> For simulators without their own tests, we normally rely on the
> cross-gcc and cross-gdb tests.  For this, you'd need to build the
> remainder of the cross toolchain (compiler/binutils/debugger), and
> run the respective tests against the sim.

Are there any details on how to configure and run those tests against
the simulator?  I've not had much luck in that regard, to be honest,
so most of my runs of 'make check' don't actually do much...

Also, should i be building everything from a single tree, from a
single tree for binutils + debugger & separate tree for gcc, or is all
independent trees OK?


> [ targets ]

great.


> : thanks!
> 
> No, thank you!  (I presume you know about the copyright
> assignment/disclaimer procedure too.)

Yes; I (and any of other of my coworkers whose code will be submitted)
already have the proper assignment forms on file with the FSF, and
should be good to go to submit code and have it checked in once
accepted.

Getting that hairball taken care of was one of the first things I made
sure to do, when I embarked on this process.  8-)


chris

  reply	other threads:[~2000-12-01 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01 12:02 Chris G. Demetriou
2000-12-01 12:52 ` Frank Ch. Eigler
2000-12-01 13:00   ` Chris G. Demetriou [this message]
2000-12-01 13:08     ` Frank Ch. Eigler
2000-12-01 13:52       ` Chris G. Demetriou
2000-12-04 14:35   ` Chris G. Demetriou
2000-12-04 15:10     ` Andrew Cagney

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=5tsno726y9.fsf@highland.sibyte.com \
    --to=cgd@sibyte.com \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).