From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Joel Brobecker <brobecker@ACT-Europe.FR>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix recent compilation errors in alpha-nat.c on alpha-osf
Date: Mon, 22 Apr 2002 08:56:00 -0000 [thread overview]
Message-ID: <20020422085618.F27275@dr-evil.shagadelic.org> (raw)
In-Reply-To: <20020422154234.F21070@act-europe.fr>; from brobecker@ACT-Europe.FR on Mon, Apr 22, 2002 at 03:42:34PM +0200
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Mon, Apr 22, 2002 at 03:42:34PM +0200, Joel Brobecker wrote:
> Ideas for a better fix are welcome.
I'll commit this; it mimmicks what I did in the other Alpha code.
* alpha-nat.c (get_longjmp_target): Use ALPHA_* constants
where needed.
(fetch_osf_core_registers): Likewise.
(supply_gregset): Likewise.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
[-- Attachment #2: alpha-patch --]
[-- Type: text/plain, Size: 1257 bytes --]
Index: alpha-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-nat.c,v
retrieving revision 1.9
diff -u -r1.9 alpha-nat.c
--- alpha-nat.c 21 Apr 2002 16:52:39 -0000 1.9
+++ alpha-nat.c 22 Apr 2002 15:50:30 -0000
@@ -63,7 +63,7 @@
get_longjmp_target (CORE_ADDR *pc)
{
CORE_ADDR jb_addr;
- char raw_buffer[MAX_REGISTER_RAW_SIZE];
+ char raw_buffer[ALPHA_MAX_REGISTER_RAW_SIZE];
jb_addr = read_register (ALPHA_A0_REGNUM);
@@ -101,7 +101,7 @@
OSF/1.2 core files. OSF5 uses different names for the register
enum list, need to handle two cases. The actual values are the
same. */
- static int core_reg_mapping[NUM_REGS] =
+ static int core_reg_mapping[ALPHA_NUM_REGS] =
{
#ifdef NCF_REGS
#define EFL NCF_REGS
@@ -127,7 +127,7 @@
EF_PC, -1
#endif
};
- static char zerobuf[MAX_REGISTER_RAW_SIZE] =
+ static char zerobuf[ALPHA_MAX_REGISTER_RAW_SIZE] =
{0};
for (regno = 0; regno < NUM_REGS; regno++)
@@ -222,7 +222,7 @@
{
register int regi;
register long *regp = ALPHA_REGSET_BASE (gregsetp);
- static char zerobuf[MAX_REGISTER_RAW_SIZE] =
+ static char zerobuf[ALPHA_MAX_REGISTER_RAW_SIZE] =
{0};
for (regi = 0; regi < 31; regi++)
next prev parent reply other threads:[~2002-04-22 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 6:42 Joel Brobecker
2002-04-22 8:49 ` Jason R Thorpe
2002-04-22 8:56 ` Jason R Thorpe [this message]
2002-04-23 3:14 ` Joel Brobecker
2002-04-23 3:55 ` David S. Miller
2002-04-23 10:56 ` Michael Snyder
2002-04-23 16:33 ` Andrew Cagney
2002-04-23 22:04 ` David S. Miller
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=20020422085618.F27275@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=brobecker@ACT-Europe.FR \
--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