Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] Create new file mips-tdep.h
Date: Thu, 03 Oct 2002 19:25:00 -0000	[thread overview]
Message-ID: <20021004022613.GA16925@nevyn.them.org> (raw)
In-Reply-To: <1021004010349.ZM32674@localhost.localdomain>

On Thu, Oct 03, 2002 at 06:03:49PM -0700, Kevin Buettner wrote:
> I have some other changes under way in which I will need to know which
> mips ABI is in use.  I've moved struct gdbarch_tdep and the enums
> that it depends upon into a new header file.
> 
> Okay?

I think this is a good idea, though of course you'll need to wait for
Andrew - it may be some time, I believe.

This patch reminded me of something.  I don't really like the fact that
we have a "struct gdbarch_tdep" for every architecture; when we have a
multi-architecture GDB this will cause tremendous debugging confusion. 
How intrusive do you think it would be to opaquify it (I hope that's
not really a word) properly, and have a struct mips_gdbarch_tdep?

> 
> 	* Makefile.in (mips_tdep_h): Define.
> 	(mips-tdep.o): Remove osabi_h from dependency list.  Add mips_tdep_h
> 	to dependency list.
> 	* mips-tdep.h: New file.
> 	* mips-tdep.c (mips-tdep.h): Include.
> 	(osabi.h): Don't include (since it's included by mips-tdep.h).
> 	(enum mips_abi, enum_mips_fpu_type, struct gdbarch_tdep): Move
> 	definitions to mips-tdep.h.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-10-04  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 18:03 Kevin Buettner
2002-10-03 19:25 ` Daniel Jacobowitz [this message]
2002-10-21 12:08 ` Andrew Cagney
2002-10-21 12:15   ` Daniel Jacobowitz
2002-10-22  9:26     ` Kevin Buettner
2002-11-04 18:12 ` Andrew Cagney
2002-12-04 21:21   ` Kevin Buettner

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=20021004022613.GA16925@nevyn.them.org \
    --to=drow@mvista.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