From: Mark Kettenis <kettenis@chello.nl>
To: drow@mvista.com
Cc: mludvig@suse.cz, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Re: Analyzing AMD64 corefiles on i386
Date: Wed, 09 Jul 2003 21:46:00 -0000 [thread overview]
Message-ID: <200307092145.h69LjKDD000417@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20030709180801.GA23865@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 9 Jul 2003 14:08:01 -0400)
Date: Wed, 9 Jul 2003 14:08:01 -0400
From: Daniel Jacobowitz <drow@mvista.com>
> Not as such. We can't allow public functions with the names
> supply_gregset and fill_gregset in *-tdep.c files. Therefore these
> functions should be renamed, and supply_gregset and fill_gregset
> should be kept in your *-nat.c file. You'll probably want to rewrite
> those functions such that they call the new functions in *-tdep.c.
I don't see the harm. They need to be multi-arched instead of called
by name, eventually, but it's no extra work to rename them at that
time.
Not renaming them makes it impossible to build an i386 native GDB that
can also debug amd64.
> Personally I wouldn't define all those constants if the only place
> where they'll be used is the regmap array, but that's a matter of
> taste.
I'm guessing it makes it easier to at-a-glance compare with
<sys/reg.h>. I did the same thing.
That's a valid reason. Probably deserves a comment such that nobody
gratuitously re-orders the defines.
Mark
next prev parent reply other threads:[~2003-07-09 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F0ABC85.1080700@suse.cz>
[not found] ` <200307081445.h68EjBWJ000503@elgar.kettenis.dyndns.org>
2003-07-09 11:03 ` Michal Ludvig
2003-07-09 11:56 ` Andreas Schwab
2003-07-09 13:40 ` Mark Kettenis
2003-07-09 13:38 ` Mark Kettenis
2003-07-09 18:08 ` Daniel Jacobowitz
2003-07-09 19:52 ` Andrew Cagney
2003-07-09 21:46 ` Mark Kettenis [this message]
2003-07-10 10:05 ` Michal Ludvig
2003-07-14 19:26 ` Mark Kettenis
2003-07-15 11:34 ` Michal Ludvig
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=200307092145.h69LjKDD000417@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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