From: Michael Snyder <msnyder@redhat.com>
To: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: [RFC] Time for a shared linux-nat.c module?
Date: Tue, 23 Apr 2002 13:33:00 -0000 [thread overview]
Message-ID: <3CC5C242.D975892F@redhat.com> (raw)
I notice that there are now a bunch of <arch>-linux-tdep.c
modules, and that some of them share a bunch of duplicate code.
I'm wondering if it isn't time to create a linux-nat.c module,
shared by all host architectures, into which we can move
some of this code instead of maintaining separate, duplicate
versions.
Michael
next reply other threads:[~2002-04-23 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 13:33 Michael Snyder [this message]
2002-04-23 14:29 ` Kevin Buettner
2002-04-23 22:03 ` David S. Miller
2002-04-24 8:27 ` [RFA] Add glibc-tdep (was Re: [RFC] Time for a shared linux-nat.c module?) David S. Miller
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=3CC5C242.D975892F@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@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