From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Changes to *_*regset functions
Date: Fri, 13 Jul 2001 12:35:00 -0000
Message-id: <1010713193513.ZM20388@ocotillo.lan>
References: <20010713102605.A32410@nevyn.them.org> <3B4F4223.8030405@cygnus.com> <ac131313@cygnus.com>
X-SW-Source: 2001-07/msg00136.html

On Jul 13,  2:46pm, Andrew Cagney wrote:

> > Along with the cross-core handling, and eventually cross-thread support, I
> > want to multi-arch supply_gregset/fill_gregset/supply_fpregset/fill_fpregset,
> > and make them target rather than native functions where possible.  The issue,
> > of course, is that the *regset_t and *reg_t types are not available to us
> > when cross compiling, and attempting to make them available seems the wrong
> > way to go.
> 
> 
> Do they belong in gdbarch?  gdbarch contains things that describe the 
> target systems ISA, ABI, ...
> 
> Something like supply_gregset() might use gdbarch.  I don't know that it 
> belongs in multi-arch.

For Daniel's purposes, supply_gregset() does need to be multi-arch. 
Imagine wanting to debug UnixWare, Solaris/x86, Linux, and FreeBSD
core files from a NetBSD/PPC platform.  In other words, think of the
core file format as an extension of the ABI.

Kevin