Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Grace Sainsbury <graces@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] m68k multi-arch: frame_saved_regs
Date: Fri, 21 Jun 2002 08:03:00 -0000	[thread overview]
Message-ID: <3D134021.1060508@cygnus.com> (raw)
In-Reply-To: <20020621102211.A22931@tomago.toronto.redhat.com>

Just some tweaks (Eli might have to correct me :-)

> 2002-06-20  Grace Sainsbury  <graces@redhat.com>
> 
>         * m68k-tdep.c (m68k_frame_init_saved_regs): Replaced
>         m68k_find_saved_regs.

I think a ChangeLog uses present tense ``Replace m68k...''.

>         (m68k_pop_frame): Removed saved_regs structure, and replaced
>         references to it with frasme->saved_regs.
>         (m68k_gdbarch_init): Added function calls to initialize the
>         gdbarch structure. 
>         * config/m68k/tm-m68k.h: Removed FRAME_FIND_SAVED_REGS and
>         macros associated with CALL_DUMMY

Remember to provide the complete list.  At some stage in the future 
someone will be looking at this and wondering exactly which macros they 
were.  This sometimes leads to very long ChangeLog entries but we live 
with that :-).  Trailing period.

* config/.....h (RFRAME)FIND_SAVED_REGS): Remove.
(CALL_DUMMY): Delete.
...

+m68k_fix_call_dummy(char *dummy, CORE_ADDR pc, CORE_ADDR fun, int nargs,

Just, suggest running the file through indent (``..._dummy (...'').

That wacks the hardest ones! ya.
Andrew



  reply	other threads:[~2002-06-21 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21  7:22 Grace Sainsbury
2002-06-21  8:03 ` Andrew Cagney [this message]
2002-06-21  8:27   ` Grace Sainsbury
2002-06-21  8:42     ` Andrew Cagney
2002-06-21  9:27 ` Jason R Thorpe

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=3D134021.1060508@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=graces@redhat.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