From: Andreas Schwab <schwab@suse.de>
To: Josef Wolf <jw@raven.inka.de>
Cc: gdb@sources.redhat.com
Subject: Re: Need Help for bringing m68k-based bdm target-patches form gdb-5.2.1 to gdb-5.3
Date: Mon, 11 Aug 2003 09:36:00 -0000 [thread overview]
Message-ID: <je65l4cz7r.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030810204748.GA24206@raven.inka.de> (Josef Wolf's message of "Sun, 10 Aug 2003 22:47:48 +0200")
Josef Wolf <jw@raven.inka.de> writes:
|> IMHO, seeing this registers would be a great benefit when you go behind
|> user-only code (e.g in the embedded world). If I understand correctly, it
|> would not be a great deal to support them. So why not to support?
If you have a target that provides them, sure.
|> But this means you need to know the "inside meanings" when you want to
|> assign different numbers. And that is exactly my problem. I don't know
|> those "insight meanings" and I can't find any place where the
|> "insight meanings" are described.
Just add the new registers after the existing one, not inbetween. Simple
as that.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2003-08-11 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 22:36 Josef Wolf
2003-08-05 21:50 ` Josef Wolf
2003-08-06 16:09 ` Andrew Cagney
2003-08-06 22:17 ` Josef Wolf
2003-08-09 14:31 ` Andrew Cagney
2003-08-10 21:16 ` Josef Wolf
2003-08-06 18:22 ` Andreas Schwab
2003-08-06 20:55 ` Josef Wolf
2003-08-07 6:08 ` Andreas Schwab
2003-08-07 14:35 ` Andrew Cagney
2003-08-10 20:59 ` Josef Wolf
2003-08-10 20:48 ` Josef Wolf
2003-08-11 9:36 ` Andreas Schwab [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=je65l4cz7r.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sources.redhat.com \
--cc=jw@raven.inka.de \
/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