From: Jim Blandy <jimb@redhat.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gdb-patches@sources.redhat.com, uweigand@de.ibm.com
Subject: Re: [PATCH] S/390 port modernization 1/4
Date: Fri, 05 Dec 2003 04:29:00 -0000 [thread overview]
Message-ID: <vt2u14fyjm7.fsf@zenia.home> (raw)
In-Reply-To: <200312042145.WAA07842@faui1d.informatik.uni-erlangen.de>
Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de> writes:
> Jim Blandy wrote:
>
> > Would it be possible to have s390-nat.c simply use the structures from
> > s390-tdep.c? There's nothing wrong with having an s390-tdep.h file in
> > the gdb directory; that's the usual arrangement for native systems.
>
> As these offsets are core kernel ABI that will never change, I hadn't
> thought it necessary to avoid this duplication -- in particular as
> one of my goals was to disentangle the various components as much as
> possible ...
>
> But if you prefer a s390-tdep.h file, I can certainly do that.
I see. It's my feeling that -nat.c files are always, in some sense,
dependent on -tdep.c files anyway (although the reverse is not true).
And it seems to me that using exactly the same table in both places
does clarify the intent.
next prev parent reply other threads:[~2003-12-05 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 20:06 Ulrich Weigand
2003-12-04 21:01 ` Jim Blandy
2003-12-04 21:56 ` Ulrich Weigand
2003-12-05 4:21 ` Jim Blandy
2003-12-04 21:18 ` Jim Blandy
2003-12-04 21:45 ` Ulrich Weigand
2003-12-05 4:29 ` Jim Blandy [this message]
2003-12-04 21:43 ` Jim Blandy
2003-12-04 22:11 ` Ulrich Weigand
2003-12-05 4:30 ` Jim Blandy
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=vt2u14fyjm7.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=uweigand@de.ibm.com \
--cc=weigand@i1.informatik.uni-erlangen.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