From: "Frank Ch. Eigler" <fche@redhat.com>
To: matthew green <mrg@cygnus.com>
Cc: sid@sources.redhat.com
Subject: Re: RFA: loader Elf64 loader & split insn/data accessors
Date: Sun, 14 Jan 2001 09:55:00 -0000 [thread overview]
Message-ID: <20010114125533.B28592@redhat.com> (raw)
In-Reply-To: <14951.979448688@cygnus.com>
Hi -
On Sun, Jan 14, 2001 at 04:04:48PM +1100, matthew green wrote:
: [...]
: OK, done. i still need to finish the debugger changes for this also.
:
: this is the debugger patch. it adds a new "debugger_bus_insn" to each
: component, default to the insn_bus (as "debugger_bus" defaults to the
: data_bus). [...]
Since this code does hard-code the bit-33 interpretation, I'd rather
not leave it mainstream for long. Do you swear, by penalty of certain
dehairization, that when the bus api enlargements occur, you will
unhackify this component?
Even if yes, code hygiene may make it worth it to identify this
extension with a new component type, such as "sw-debug-gdb-bit33hack",
even if the same (parametrized, inherited, or even completely
identical) C++ code implements both.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6YegVVZbdDOm/ZT0RAstqAJ0eJbXoez2xS+uTjDvB+Ub1Nr4/xACfZxDa
4KT2PCzMhAKSoVp6r6vrtsQ=
=gEsj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-01-14 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 4:01 matthew green
2001-01-13 5:41 ` Frank Ch. Eigler
2001-01-13 19:12 ` matthew green
2001-01-13 21:08 ` matthew green
2001-01-14 9:55 ` Frank Ch. Eigler [this message]
2001-01-15 8:28 ` debugger_bus_insn dead (was: re: RFA: loader Elf64 loader & split insn/data accessors) matthew green
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=20010114125533.B28592@redhat.com \
--to=fche@redhat.com \
--cc=mrg@cygnus.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).