From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@sonic.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New target am33-linux (mn10300)
Date: Sat, 30 Apr 2005 01:45:00 -0000 [thread overview]
Message-ID: <20050430014531.GA15951@nevyn.them.org> (raw)
In-Reply-To: <4272D60B.5050709@sonic.net>
On Fri, Apr 29, 2005 at 05:49:15PM -0700, Michael Snyder wrote:
> Index: mn10300-linux-tdep.c
> ===================================================================
> RCS file: mn10300-linux-tdep.c
> diff -N mn10300-linux-tdep.c
> *** /dev/null 1 Jan 1970 00:00:00 -0000
> --- mn10300-linux-tdep.c 30 Apr 2005 00:28:15 -0000
> ***************
> *** 0 ****
> --- 1,221 ----
> + /* Target-dependent code for the Matsushita MN10300 for GDB, the GNU debugger.
> + Copyright 2003
> + Free Software Foundation, Inc.
Welcome to 2005 :-) This has indeed been languishing...
> + /* Transliterated from <asm-mn10300/elf.h>... */
> + #define ELF_NGREG 27
> + #define ELF_NFPREG 32
> +
> + typedef unsigned char elf_greg_t[4];
> + typedef elf_greg_t elf_gregset_t[ELF_NGREG];
> +
> + typedef unsigned char elf_fpreg_t[4];
> + typedef struct
> + {
> + elf_fpreg_t fpregs[ELF_NFPREG];
> + unsigned char fpcr[4];
> + } elf_fpregset_t;
Past experience tells me that this is a bad idea; please pick names for
these types (and the other constants) which won't conflict with types
in the system headers.
> + /* Use a local version of this function to get the correct types for
> + regsets, until multi-arch core support is ready. */
> +
> + static void
> + fetch_core_registers (char *core_reg_sect, unsigned core_reg_size,
> + int which, CORE_ADDR reg_addr)
Lots of stray braces in this function. But also...
> + void
> + _initialize_mn10300_linux_tdep (void)
> + {
> + deprecated_add_core_fns (®set_core_fns);
> + }
... that's a pretty good hint that you should update this. Please see
i386_regset_from_core_section instead.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-30 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 0:50 Michael Snyder
2005-04-30 1:45 ` Daniel Jacobowitz [this message]
2005-04-30 11:03 ` Mark Kettenis
2005-04-30 13:58 ` Daniel Jacobowitz
2005-04-30 15:02 ` Mark Kettenis
2005-04-30 15:07 ` Daniel Jacobowitz
2005-05-01 18:33 ` Eli Zaretskii
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=20050430014531.GA15951@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@sonic.net \
/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