From: Mark Kettenis <kettenis@chello.nl>
To: thorpej@wasabisystems.com
Cc: gdb-patches@sources.redhat.com, obrien@freebsd.org
Subject: Re: [PATCH] Move Alpha BSD register supply/fill to alphabsd-tdep.c
Date: Sat, 11 May 2002 04:45:00 -0000 [thread overview]
Message-ID: <200205111145.g4BBjt711447@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20020510100446.E3435@dr-evil.shagadelic.org> (message from Jason R Thorpe on Fri, 10 May 2002 10:04:47 -0700)
It looks mostly OK to me. There is a code formatting problem though:
the extra spaces between "void" and the function name in the
prototypes in alpabsd-tdep.h. Oh, and can you please rename
alpha_bsd_* to alphabsd_*, for consistency?
Hmm, looking at the names you chose for the alpha_bsd_{fill,supply}_*
functions I'm wondering if we should unify the way these kind of
functions are defined for the targets that GDB supports. I think the
function signatures that you chose are right, i.e. the first argument
a char * to some data representing the values of a bunch of registers,
and the second argument a register number where -1 means "all
registers". Come to think of it, I should probably change the
i387_supply_* functions to have that same signature. About the naming
of the functions: I think the last part of the name should indicate
what exactly the first char * points to. I chose 'fsave' and 'fxsave'
for the i387_{fill,supply}_* functions. Therefore I would have chosen
'reg' and 'fpreg' for the alphabsd_{fill,supply}_* functions, since
the first argument is supposed to be a 'struct reg' or 'struct fpreg'.
Mark
next prev parent reply other threads:[~2002-05-11 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 10:04 Jason R Thorpe
2002-05-11 4:45 ` Mark Kettenis [this message]
2002-05-11 9:16 ` Jason R Thorpe
2002-05-11 10:36 ` David O'Brien
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=200205111145.g4BBjt711447@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=obrien@freebsd.org \
--cc=thorpej@wasabisystems.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