Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: manjo@austin.ibm.com
Cc: gdb@sourceware.org
Subject: Re: Orphans to adopt?
Date: Tue, 17 May 2005 21:22:00 -0000	[thread overview]
Message-ID: <200505172121.j4HLLjsi002393@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0505171549450.3652@lazy> (message from Manoj Iyer on Tue, 17 May 2005 15:51:47 -0500 (CDT))

   Date: Tue, 17 May 2005 15:51:47 -0500 (CDT)
   From: Manoj Iyer <manjo@austin.ibm.com>

   > Hmm, powerpc could really, really use some cleanup, but hardly

   What type of clean up effort are we looking at for ppc. I am working on
   ppc & linux and I can spend some time on this.

A couple of things:

* It still needs to be gdb_bytified.

* There are still a few deprecated things used by rs6000/powerpc.
  Look for things that have deprecated in their name.

* There is still a tm.h for most/all rs6000/powerpc targets.
  Basically config/powerpc/tm-ppc-eabi.h and config/rs6000/tm-rs6000.h
  need to be cleaned out.

* The code could use some reorganisation, especially the way the
  architecture vector is constructed.  Some of the OS/ABI-specefic
  stuff is handled in rs6000-tdep.c, some of it is dealt with in
  OS-specific files like ppc-linux-tdep.c and pccnbsd-tdep.c.

A lot of the mess seems to stem from the fact that we still try to
support AIX 4 & 5 on POWER as well as PowerPC.  But it seems that none
of the core gdb developers have access to hardware.

Mark


  reply	other threads:[~2005-05-17 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 19:03 Stan Shebs
2005-05-17 19:07 ` Daniel Jacobowitz
2005-05-17 20:35 ` Mark Kettenis
2005-05-17 20:57   ` Manoj Iyer
2005-05-17 21:22     ` Mark Kettenis [this message]
2005-05-19 18:31       ` Andrew Cagney
2005-06-10 21:36         ` Mark Kettenis
2005-06-10 21:59           ` Manoj Iyer
     [not found] <1116408555.845.ezmlm@sources.redhat.com>
2005-05-24 12:33 ` E. Weddington

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=200505172121.j4HLLjsi002393@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb@sourceware.org \
    --cc=manjo@austin.ibm.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