From: Grace Sainsbury <graces@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: PATCH: indent m68k-tdep.c
Date: Mon, 17 Jun 2002 12:35:00 -0000 [thread overview]
Message-ID: <3D0E3A0B.674F1B69@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
This indents m68k-tdep.c using gdb_indent.sh. Is it ok to commit?
Grace Sainsbury
2002-06-17 Grace Sainsbury <graces@redhat.com>
* m68k-tdep.c: Reindent.
[-- Attachment #2: indent_m68k.diff --]
[-- Type: text/plain, Size: 3491 bytes --]
Index: m68k-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/m68k-tdep.c,v
retrieving revision 1.14
diff -u -r1.14 m68k-tdep.c
--- m68k-tdep.c 1 Dec 2001 23:06:46 -0000 1.14
+++ m68k-tdep.c 17 Jun 2002 18:59:07 -0000
@@ -81,11 +81,11 @@
return frame_info->frame + 12;
else if (frameless_look_for_prologue (frame_info))
{
- /* Check for an interrupted system call */
- if (frame_info->next && frame_info->next->signal_handler_caller)
- return frame_info->next->frame + 16;
- else
- return frame_info->frame + 4;
+ /* Check for an interrupted system call */
+ if (frame_info->next && frame_info->next->signal_handler_caller)
+ return frame_info->next->frame + 16;
+ else
+ return frame_info->frame + 4;
}
else
return frame_info->frame;
@@ -226,7 +226,8 @@
}
if (fsr.regs[PS_REGNUM])
{
- write_register (PS_REGNUM, read_memory_integer (fsr.regs[PS_REGNUM], 4));
+ write_register (PS_REGNUM,
+ read_memory_integer (fsr.regs[PS_REGNUM], 4));
}
write_register (FP_REGNUM, read_memory_integer (fp, 4));
write_register (PC_REGNUM, read_memory_integer (fp + 4, 4));
@@ -278,7 +279,7 @@
If so, ensure we don't go past it. If not, assume "infinity". */
sal = find_pc_line (ip, 0);
- limit = (sal.end) ? sal.end : (CORE_ADDR) ~ 0;
+ limit = (sal.end) ? sal.end : (CORE_ADDR) ~0;
while (ip < limit)
{
@@ -298,7 +299,7 @@
else if (op == P_FMOVM)
ip += 10; /* Skip fmovm */
else
- break; /* Found unknown code, bail out. */
+ break; /* Found unknown code, bail out. */
}
return (ip);
}
@@ -314,7 +315,7 @@
/* First possible address for a pc in a call dummy for this frame. */
CORE_ADDR possible_call_dummy_start =
- (frame_info)->frame - CALL_DUMMY_LENGTH - FP_REGNUM * 4 - 4 - 8 * 12;
+ (frame_info)->frame - CALL_DUMMY_LENGTH - FP_REGNUM * 4 - 4 - 8 * 12;
int nextinsn;
memset (saved_regs, 0, sizeof (*saved_regs));
@@ -367,7 +368,7 @@
next_addr += read_memory_integer (pc += 2, 4), pc += 4;
}
- for ( ; ; )
+ for (;;)
{
nextinsn = 0xffff & read_memory_integer (pc, 2);
regmask = read_memory_integer (pc + 2, 2);
@@ -519,7 +520,7 @@
register values. */
void
-supply_gregset (gregset_t *gregsetp)
+supply_gregset (gregset_t * gregsetp)
{
register int regi;
register greg_t *regp = (greg_t *) gregsetp;
@@ -533,7 +534,7 @@
}
void
-fill_gregset (gregset_t *gregsetp, int regno)
+fill_gregset (gregset_t * gregsetp, int regno)
{
register int regi;
register greg_t *regp = (greg_t *) gregsetp;
@@ -562,7 +563,7 @@
idea of the current floating point register values. */
void
-supply_fpregset (fpregset_t *fpregsetp)
+supply_fpregset (fpregset_t * fpregsetp)
{
register int regi;
char *from;
@@ -583,7 +584,7 @@
them all. */
void
-fill_fpregset (fpregset_t *fpregsetp, int regno)
+fill_fpregset (fpregset_t * fpregsetp, int regno)
{
int regi;
char *to;
@@ -636,9 +637,8 @@
buf = alloca (TARGET_PTR_BIT / TARGET_CHAR_BIT);
sp = read_register (SP_REGNUM);
- if (target_read_memory (sp + SP_ARG0, /* Offset of first arg on stack */
- buf,
- TARGET_PTR_BIT / TARGET_CHAR_BIT))
+ if (target_read_memory (sp + SP_ARG0, /* Offset of first arg on stack */
+ buf, TARGET_PTR_BIT / TARGET_CHAR_BIT))
return 0;
jb_addr = extract_address (buf, TARGET_PTR_BIT / TARGET_CHAR_BIT);
next reply other threads:[~2002-06-17 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 12:35 Grace Sainsbury [this message]
2002-06-17 13:04 ` Andrew Cagney
2002-06-18 14:37 ` Michael Snyder
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=3D0E3A0B.674F1B69@redhat.com \
--to=graces@redhat.com \
--cc=gdb-patches@sources.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