From: David B Anderson <davea@quasar.engr.sgi.com>
To: gdb@sources.redhat.com
Cc: jkingdon@engr.sgi.com, ac131313@cygnus.co, eliz@is.elta.co.il
Subject: Re: GDB on SGI Irix 6.5
Date: Thu, 19 Apr 2001 18:06:00 -0000 [thread overview]
Message-ID: <200104200105.SAA29210@quasar.engr.sgi.com> (raw)
> - 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 suggest creating tm-irix6.h
IMO it's misleading to keep using the irix5 designation for irix6
and will lead to difficulty. But I'm far far from being an expert
on gdb, so take this with a grain of salt.
> - 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?).
The register layouts for n32 and 64 are the same.
Pointer and int are different sizes, but the registers
themselves are the same and designated the same.
The register set for o32 is different, and should be the same as for
irix5.
Recall that o32 uses the mdebug/third-eye format for debug info
while n32/64 uses dwarf2 exlusively for debug info
(should be irrelevant as far as registers go though).
I am not much help in determining the 'right way to do things' for
gdb, but if there is any way I can help with building or
testing or anything on IRIX6.5, let me know.
Regards,
David B. Anderson davea@sgi.com danderson@acm.org http://reality.sgi.com/davea/
next reply other threads:[~2001-04-19 18:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 18:06 David B Anderson [this message]
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
[not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14 0:52 ` Eli Zaretskii
2001-06-14 10:05 ` Daniel Berlin
[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
-- strict thread matches above, loose matches on Subject: below --
2001-06-13 1:53 Eli Zaretskii
2001-05-17 10:15 David B Anderson
2001-05-17 11:40 ` Eli Zaretskii
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
2001-04-30 11:28 ` Eli Zaretskii
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=200104200105.SAA29210@quasar.engr.sgi.com \
--to=davea@quasar.engr.sgi.com \
--cc=ac131313@cygnus.co \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=jkingdon@engr.sgi.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