Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: GDB on SGI Irix 6.5
Date: Mon, 30 Apr 2001 10:01:00 -0000	[thread overview]
Message-ID: <3AED9A6D.CA01D20E@cygnus.com> (raw)
In-Reply-To: <3405-Thu19Apr2001160546+0300-eliz@is.elta.co.il>

>   - Should I make the change in tm-irix5.h, or should I leave it alone
>     and create irix6x.h?  The issue here is that perhaps Irix 5 did
>     work like tm-irix5.h says, and I won't want to break that.

I think everyone has agreed on tm-irix6.h.

>   - What should I do about the different ABIs?  At least 3 come to
>     mind: O32, N32, and N64.  They have subtly different layouts of
>     registers, so if I need to set things up for more than a single
>     ABI, I'll need to know what's the current say-so about how this
>     should be done (e.g., does gdbarch has some functionality for
>     dynamically computing the registers array?).

By subtle differences in registers do you mean the register use or
layout?

mips-tdep.c:mips_gdbarch_init() is hopefully already detecting the ABI
and setting things up to handle the register usage differences.

With regard to register layout, the MIPS still, unfortunatly, uses a
static configuration.  multi-arch can support dynamic register layouts,
it is just not implemented for MIPS.

	Andrew


  reply	other threads:[~2001-04-30 10:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09  0:08 Eli Zaretskii
2001-04-09  6:53 ` Daniel Berlin
2001-04-17 10:38 ` Andrew Cagney
2001-04-18  9:29   ` Eli Zaretskii
2001-04-19  6:08     ` Eli Zaretskii
2001-04-30 10:01       ` Andrew Cagney [this message]
2001-04-30 11:28         ` Eli Zaretskii
2001-04-19 18:06 David B Anderson
2001-04-21 11:12 ` Eli Zaretskii
2001-04-21 12:09   ` Paul Hilfinger
2001-04-21 13:09 ` David B Anderson
2001-04-21 13:19   ` Eli Zaretskii
2001-05-17  8:58   ` Eli Zaretskii
2001-05-17  9:15     ` Eli Zaretskii
2001-05-17  9:26       ` Daniel Berlin
2001-05-17  9:28         ` Eli Zaretskii
2001-05-17  9:41           ` Daniel Berlin
2001-05-17 11:33             ` Eli Zaretskii
2001-05-17 11:47               ` Daniel Berlin
2001-05-17 10:15 David B Anderson
2001-05-17 11:40 ` Eli Zaretskii
2001-06-13  1:53 Eli Zaretskii
     [not found] <Pine.SUN.3.91.1010612152328.3699B-100000@is>
     [not found] ` <3B266F35.50007@cygnus.com>
     [not found]   ` <15142.30117.72465.686304@kwikemart.cygnus.com>
2001-06-13  1:55     ` Eli Zaretskii
2001-06-13 13:35     ` David B Anderson
2001-06-13 21:19       ` Daniel Berlin
     [not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii
2001-06-13 13:05   ` Andrew Cagney
     [not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14  0:52 ` Eli Zaretskii
2001-06-14 10:05   ` Daniel Berlin

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=3AED9A6D.CA01D20E@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --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