From: Brian Ford <ford@vss.fsi.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Rename i386_xxx_reg_to_regnum
Date: Wed, 07 Apr 2004 21:06:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0404071557471.1086@thing1-200> (raw)
In-Reply-To: <vt28yh7bjnp.fsf@zenia.home>
On Wed, 7 Apr 2004, Jim Blandy wrote:
> Brian Ford writes:
> > On Wed, 7 Apr 2004, Mark Kettenis wrote:
> > > Brian Ford wrote:
> > >> I still propose we rename the _to_regnum functions, replacing
> > >> stabs and dwarf with dbx and svr4 to reduce confusion. I'll be happy
> > >> to make a patch :-).
> > >
> > > Please do so.
> >
> > Here is the semi-pre-approved rename patch. I decided not to make any
> > style changes.
> >
> > Jim, I hope you don't mind me putting words in your mouth, but I felt
> > your FIXME comment needed correction as a result of this, and the previous
> > change.
>
> Just change 'jimb' to 'ford', re-use whatever text you want, and make
> sure it really says what *you* want it to say; that's fine.
Ok. Do I really need to supply a new patch to do that? Or, can
whoever approves and commits it just do that please? And, it does say
what I wanted it to ;-).
> > 2004-04-07 Brian Ford <ford@vss.fsi.com>
> >
> > * i386-tdep.c: Correct register numbering scheme comments throughout.
> > (i386_stab_reg_to_regnum): Rename to i386_dbx_reg_to_regnum.
> > (i386_dwarf_reg_to_regnum): Rename to i386_svr4_reg_to_regnum.
>
> If you're trying to match the names in gcc/config/i386/i386.c,
> shouldn't the second one be called i386_svr4_dbx_reg_to_regnum?
I dunno. I think that might be more confusing. It's explicit in the
comment anyway, and I didn't want to be redundant.
I'd prefer to just leave it, but if someone else feels strongly, feel free
to change it on commit.
> Otherwise, looks good to me.
Thanks for the vote of confidence.
Let me know if I need to generate a new patch with the two changes above.
Call me lazy ;-).
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next prev parent reply other threads:[~2004-04-07 21:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 0:11 [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Brian Ford
2004-04-01 17:22 ` Jim Blandy
2004-04-01 18:00 ` Brian Ford
2004-04-01 21:29 ` Jim Blandy
2004-04-01 22:54 ` Brian Ford
2004-04-02 7:45 ` Eli Zaretskii
[not found] ` <Pine dot GSO dot 4 dot 58 dot 0404021000390 dot 21204 at thing1-200>
[not found] ` <2719-Fri02Apr2004213907+0300-eliz at gnu dot org>
[not found] ` <Pine dot GSO dot 4 dot 58 dot 0404021648050 dot 21204 at thing1-200>
2004-04-02 17:31 ` Brian Ford
2004-04-02 19:42 ` Eli Zaretskii
2004-04-02 23:15 ` Brian Ford
2004-04-03 9:08 ` Eli Zaretskii
2004-04-05 18:18 ` Jim Blandy
2004-04-05 21:57 ` Brian Ford
2004-04-18 16:33 ` Eli Zaretskii
2004-04-05 18:21 ` Jim Blandy
2004-04-05 22:46 ` Brian Ford
2004-04-18 17:00 ` Eli Zaretskii
2004-04-05 22:46 ` Jim Blandy
2004-04-05 23:19 ` Brian Ford
2004-04-05 23:38 ` Jim Blandy
2004-04-06 14:53 ` Brian Ford
2004-04-15 9:38 ` Eli Zaretskii
2004-04-06 23:24 ` Mark Kettenis
2004-04-07 16:25 ` Brian Ford
2004-04-07 18:02 ` Jim Blandy
2004-04-07 20:06 ` [PATCH] Rename i386_xxx_reg_to_regnum Brian Ford
2004-04-07 20:48 ` Jim Blandy
2004-04-07 21:06 ` Brian Ford [this message]
2004-04-07 21:41 ` Jim Blandy
2004-04-09 12:37 ` Mark Kettenis
2004-04-09 17:49 ` Brian Ford
2004-04-06 23:23 ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Mark Kettenis
2004-04-07 16:46 ` Jim Blandy
2004-04-18 16:48 ` Eli Zaretskii
2004-04-19 2:06 ` ix86 PE/COFF DWARF register numbering (was Re: [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp)) Brian Ford
2004-04-19 5:59 ` Eli Zaretskii
2004-04-19 16:34 ` ix86 PE/COFF DWARF register numbering Brian Ford
2004-04-19 12:42 ` [PATCH] i386_stab_reg_to_regnum (4 <-> 5, ebp <-> esp) Jim Blandy
2004-04-19 7:02 ` Eli Zaretskii
2004-04-02 19:33 ` Eli Zaretskii
2004-04-02 22:47 ` Brian Ford
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=Pine.GSO.4.58.0404071557471.1086@thing1-200 \
--to=ford@vss.fsi.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=kettenis@chello.nl \
/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