Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Kazu Hirata <kazu@cs.umass.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb/h8300-tdep.c: Fix formatting.
Date: Tue, 21 May 2002 07:57:00 -0000	[thread overview]
Message-ID: <15594.24613.553337.147740@localhost.redhat.com> (raw)
In-Reply-To: <20020520.144021.08316187.kazu@cs.umass.edu>

Kazu Hirata writes:
 > Hi,
 > 
 > Attached is a patch to fix formatting.  Committed as obvious.
 > 
 > Kazu Hirata

Thanks.
Elena


 > 
 > 2002-05-20  Kazu Hirata  <kazu@cs.umass.edu>
 > 
 > 	* h8300-tdep.c: Fix formatting.
 > 
 > Index: h8300-tdep.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/h8300-tdep.c,v
 > retrieving revision 1.12
 > diff -u -r1.12 h8300-tdep.c
 > --- h8300-tdep.c	17 May 2002 19:39:52 -0000	1.12
 > +++ h8300-tdep.c	20 May 2002 18:38:22 -0000
 > @@ -54,19 +54,18 @@
 >  #define IS_MOVK_R5(x) (x==0x7905)
 >  #define IS_SUB_R5SP(x) (x==0x1957)
 >  
 > -
 >  /* The register names change depending on whether the h8300h processor
 >     type is selected. */
 >  
 >  static char *original_register_names[] = REGISTER_NAMES;
 >  
 > -static char *h8300h_register_names[] =
 > -{"er0", "er1", "er2", "er3", "er4", "er5", "er6",
 > - "sp", "ccr","pc", "cycles", "exr", "tick", "inst"};
 > +static char *h8300h_register_names[] = {
 > +  "er0", "er1", "er2", "er3", "er4", "er5", "er6",
 > +  "sp", "ccr", "pc", "cycles", "exr", "tick", "inst"
 > +};
 >  
 >  char **h8300_register_names = original_register_names;
 >  
 > -
 >  /* Local function declarations.  */
 >  
 >  static CORE_ADDR examine_prologue ();
 > @@ -766,7 +765,6 @@
 >    set_register_names ();
 >  }
 >  
 > -
 >  static void
 >  set_machine (char *args, int from_tty)
 >  {
 > @@ -824,8 +822,6 @@
 >    specify_exec_file_hook (set_machine_hook);
 >  }
 >  
 > -
 > -
 >  void
 >  h8300_print_register_hook (int regno)
 >  {
 > @@ -880,11 +876,11 @@
 >        frame_register_read (selected_frame, regno, b);
 >        l = b[REGISTER_VIRTUAL_SIZE (EXR_REGNUM) - 1];
 >        printf_unfiltered ("\t");
 > -      printf_unfiltered ("T-%d - - - ",  (l & 0x80) != 0);
 > +      printf_unfiltered ("T-%d - - - ", (l & 0x80) != 0);
 >        printf_unfiltered ("I2-%d ", (l & 4) != 0);
 >        printf_unfiltered ("I1-%d ", (l & 2) != 0);
 >        printf_unfiltered ("I0-%d", (l & 1) != 0);
 > -     }
 > +    }
 >  }
 >  
 >  void


      reply	other threads:[~2002-05-21 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 11:41 Kazu Hirata
2002-05-21  7:57 ` Elena Zannoni [this message]

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=15594.24613.553337.147740@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kazu@cs.umass.edu \
    /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