From: Andrew Cagney <ac131313@cygnus.com>
To: Christian Groessler <chris@groessler.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] z8k fixes
Date: Sun, 02 Jun 2002 07:58:00 -0000 [thread overview]
Message-ID: <3CFA32A2.6030607@cygnus.com> (raw)
In-Reply-To: <87adrcq6v7.fsf@panther.aladdin.de>
> 2002-05-07 Christian Groessler <chris@groessler.org>
>
> * z8k-tdep.c (z8k_print_register_hook): Fix display of 32 and
> 64 bit register contents for little endian hosts.
>
I've checked this part in. The list.c part:
> 2002-05-07 Christian Groessler <chris@groessler.org>
>
> * list.c: Regenerated with current opcodes/z8k-opc.h.
>
has got me curious. Is there a reason to even generate the file list.c
(instead of just keeping it internal?).
As an aside, are there a pre-packaged z8k toolchain and a set of GDB
test results available?
Andrew
next prev parent reply other threads:[~2002-06-02 14:58 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 [this message]
2002-06-05 14:09 ` Christian Groessler
2002-06-05 14:59 ` Andrew Cagney
2002-06-05 16:29 ` Christian Groessler
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=3CFA32A2.6030607@cygnus.com \
--to=ac131313@cygnus.com \
--cc=chris@groessler.org \
--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