Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add support for 64-bit MIPS GNU/Linux targets
Date: Tue, 07 Jan 2003 00:26:00 -0000	[thread overview]
Message-ID: <3E1A1E43.10201@redhat.com> (raw)
In-Reply-To: <20021223235639.GA6927@nevyn.them.org>

> +  register_addr_data =
>> +    register_gdbarch_data (init_register_addr_data, 0);
>> +
>>    gdbarch_register_osabi (bfd_arch_mips, 0, GDB_OSABI_LINUX,
>>  			  mips_linux_init_abi);
>>    add_core_fns (&regset_core_fns);
> 
> 
> Blech.  So, the way _I_ would have done this would have been to put
> this in the tdep structure.  In fact I have several patches which add
> similar methods to the tdep structure, for signal handling.  Of course,
> this is not compatible with the way Andrew asked to leave the tdep
> struct in mips-tdep.c.  This is OK for now, but hopefully we can get
> rid of it eventually.  We could multi-arch register_addr (is that
> appropriate?  It's a native-only function, isn't it?) to do that.
> 

Using the gdbarch data mechanism is a good idea - it keeps that 
architecture dependency local to that file.  It definitly doesn't belong 
in the tdep structure since nothing, other than this file, needs it.

Hmm, should the actual code live in mips-linux-nat.c though?

enjoy,
Andrew



  parent reply	other threads:[~2003-01-07  0:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 15:07 Kevin Buettner
2002-12-23 16:01 ` Daniel Jacobowitz
2002-12-23 22:37   ` Kevin Buettner
2002-12-24  9:25     ` Daniel Jacobowitz
2002-12-24 11:37       ` Kevin Buettner
2002-12-24 12:09         ` Daniel Jacobowitz
2002-12-24 19:25           ` Kevin Buettner
2003-01-07  0:26   ` Andrew Cagney [this message]
2003-01-07 23:16     ` Daniel Jacobowitz
2003-01-08  0:00       ` Andrew Cagney

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=3E1A1E43.10201@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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