From: Christian Groessler <chris@groessler.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] z8k fixes
Date: Wed, 05 Jun 2002 16:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0206060119360.10633-100000@ds9.reckziegel.com> (raw)
In-Reply-To: <3CFE89E6.2070401@cygnus.com>
On Wed, 5 Jun 2002, Andrew Cagney wrote:
> > On Sun, 2 Jun 2002, Andrew Cagney wrote:
> >
> >
> >> As an aside, are there a pre-packaged z8k toolchain and a set of GDB
> >> test results available?
> >
> >
> > pre-packaged for what?
>
> I get the feeling I'm going to be multi-arching the z8k .... to do this
> I'm going to need a toolchain so I can test GDB against. That way I can
> ensure that the conversion doesn't break it.
Yes, ok, but my question was more in the direction: what host?
I'm using the z8k gcc which I found in some RedHat ecosTools archive.
There is a bug in there, so before using this please contact me.
> > Regarding the test results, there aren't. I think there is no testsuite
> > for z8k. How would I proceed creating one?
>
> GDB already has a dejagnu based testsuite. If you have a z8k cross
> compiler / assembler / linker installed, it should be possible to run
> the GDB testsuite for the z8k target.
(newbie alert!) How would I do this?
> (there is a little bit on the dejagnu testsuite in the gdb internals doco).
I'll look into this. Thanks.
regards,
chris
next prev parent reply other threads:[~2002-06-05 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 9:09 Christian Groessler
2002-05-19 21:42 ` Andrew Cagney
2002-06-02 7:58 ` Andrew Cagney
2002-06-05 14:09 ` Christian Groessler
2002-06-05 14:59 ` Andrew Cagney
2002-06-05 16:29 ` Christian Groessler [this message]
2002-06-06 8:56 ` Andrew Cagney
2002-06-06 14:08 ` Christian Groessler
2002-05-21 7:35 Christian Groessler
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=Pine.LNX.4.30.0206060119360.10633-100000@ds9.reckziegel.com \
--to=chris@groessler.org \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.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