From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com
Subject: Which HPPA targets do we still support?
Date: Tue, 05 Nov 2002 18:00:00 -0000 [thread overview]
Message-ID: <20021106020308.GM5164@gnat.com> (raw)
I was looking at configure.tgt to see the list of OSABI I would need to
add in osabi.[hc], and found a list that's a bit longer than I expected:
hppa*-*-bsd*) gdb_target=hppabsd ;;
hppa*-*-pro*) gdb_target=hppapro ;;
hppa*64*-*-hpux11*) gdb_target=hppa64 ;;
hppa*-*-hpux*) gdb_target=hppahpux ;;
hppa*-*-hiux*) gdb_target=hppahpux ;;
hppa*-*-osf*) gdb_target=hppaosf ;;
hppa*-*-*) gdb_target=hppa ;;
So far, the only target that I knew of was the hppa*-*-hpux*.
I did not know that hppa*-*-bsd* and hppa*-*-osf* existed.
I did not know about the hppa*-*-pro* either...
All I have access to are 2 HP/UX machines, with 11.00 and 10.20 (but
this machine is very slow)... While doing the multi-arch conversion,
I'll try not to break the other targets, but that's going to be a hard
battle. A second pair of eyes from a multiarch guru will be greatly
appreciated. Maybe I should send a message to gdb@sources to check if
some people are still using all these targets?
Is the list above the correct list to look at to get the list of new
OSABI enums? I would like to suggest the addition of
GDB_OSABI_HPPA
GDB_OSABI_HPPA_64
GDB_OSABI_HPPA_BSD
GDB_OSABI_HPPA_HPUX
GDB_OSABI_HPPA_OSF
GDB_OSABI_HPPA_PRO
Does this look ok?
Thanks,
--
Joel
next reply other threads:[~2002-11-06 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 18:00 Joel Brobecker [this message]
2002-11-05 19:20 ` Daniel Jacobowitz
2002-11-06 13:23 ` Andrew Cagney
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=20021106020308.GM5164@gnat.com \
--to=brobecker@gnat.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