public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sources.redhat.com
Subject: LSI 33k ?
Date: Tue, 06 May 2003 12:34:00 -0000	[thread overview]
Message-ID: <1030506123427.ZM24517@localhost.localdomain> (raw)

Does anyone know anything about the LSI 33k?  Okay, more specifically, did
support for this core ever actually work in GDB?

In mips-tdep.c, I see the following:

    /* Names of LSI 33k registers.  */

    char *mips_lsi33k_reg_names[] = {
            "epc",      "hi",   "lo",   "sr",   "cause","badvaddr",
            "dcic", "bpc",  "bda",  "",     "",     "",     "",      "",
            "",     "",     "",     "",     "",     "",     "",      "",
            ...

With the exception of IRIX, the first line for all of the other regname
sets look like this:

	    "sr",	"lo",	"hi",	"bad",	"cause","pc",

I'm not concerned about IRIX, because BADVADDR_REGNUM, CAUSE_REGNUM,
PC_REGNUM, etc. are redefined in the appropriate tm-*.h file.

The LSI 33k rearranges these registers, apparently even the PC_REGNUM
value, but nowhere do I see a PC_REGNUM definition that's specific to
the LSI 33k.  This is bad because if the LSI 33k registers are really
laid out as indicated by lsi33_reg_names[], then there's no way that
GDB is actually obtaining the correct PC value whenever it uses PC_REGNUM.
(It'll be using the "baddvaddr" value...)

I thought for a while that perhaps the LSI 33k was simply bit-rotted,
but after doing some digging in the old Cygnus CVS repository, I don't
see how it could have ever worked.

Does anyone know?

Kevin

             reply	other threads:[~2003-05-06 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:34 Kevin Buettner [this message]
2003-05-06 18:27 ` Stan Shebs

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=1030506123427.ZM24517@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).