From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: jimb@redhat.com (Jim Blandy)
Cc: weigand@i1.informatik.uni-erlangen.de (Ulrich Weigand),
gdb-patches@sources.redhat.com, uweigand@de.ibm.com
Subject: Re: [PATCH] S/390 port modernization 1/4
Date: Thu, 04 Dec 2003 22:11:00 -0000 [thread overview]
Message-ID: <200312042211.XAA07877@faui1d.informatik.uni-erlangen.de> (raw)
In-Reply-To: <vt2ptf4z2er.fsf@zenia.home> from "Jim Blandy" at Dec 04, 2003 04:41:32 PM
Jim Blandy wrote:
> The regset_from_core_section stuff is done exactly the way the i386
> and x86-64 do it, so I won't criticize it. But there are two things I
> wonder about:
>
> - Since core file formats are really OS-specific (ABI's often don't
> specify them), wouldn't it make more sense for the *-nat.c file to
> register an OS/ABI handler, and have that handler register the
> regset_from_core_section method?
Defining the core file format in *-nat.c would mean that a cross-gdb
wouldn't understand core files, right?
> - Why does everyone allocate the 'struct regset' objects dynamically?
> The regset layouts are structures in header files, so there's only a
> static set of them; one could simply define initialized instances of
> 'struct regset', and the regset_from_core_section method could
> return them. That seems simpler than allocating them dynamically,
> and caching them in the tdep structure.
OK, I'll change that.
Bye,
Ulrich
--
Dr. Ulrich Weigand
weigand@informatik.uni-erlangen.de
next prev parent reply other threads:[~2003-12-04 22:11 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
2003-12-04 21:43 ` Jim Blandy
2003-12-04 22:11 ` Ulrich Weigand [this message]
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=200312042211.XAA07877@faui1d.informatik.uni-erlangen.de \
--to=weigand@i1.informatik.uni-erlangen.de \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=uweigand@de.ibm.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