From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb@sources.redhat.com, brobecker@act-europe.fr
Subject: Re: Proposal: obsolete target hppa*-hp-hpux10.*
Date: Thu, 08 Jan 2004 04:12:00 -0000 [thread overview]
Message-ID: <200401080411.i084BtKY016377@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20040108025031.4FA984B35A@berman.michael-chastain.com> from "Michael Elizabeth Chastain" at Jan 7, 2004 09:50:31 pm
> . There is at least one user (Dave A), which means that there are
> probably more users.
>
> Philosophically, I see the issue as priorities. It takes work to
> maintain and QA gdb on hpux 10.20. It takes work even if gdb on hpux
> 11.11 is already working. I would rather spend my attention somewhere
> else, and so would everybody else in the world, judging by the level of
> activity.
I'm willing to see if I can resolve the build problems under HP-UX 10.20.
As far as the code generated by GCC and the debug information, there is
almost no difference between HP-UX 10 and 11. We have weak symbol support
and and a different way of running initializer, but that's it. I don't
particularly care about HP compiler support. There's still a fair number
of PA 1.1 workstations running. They were really the peak in PA-RISC
technology and they have proved to be extremely reliable. On the other
hand, I agree that there isn't much point in spending a lot of effort
on the machines.
The 10.20 machine that I use for GCC testing is mainly used for support
of a space experiment that probably will be supported by NASA and ESA
through to the end of 2007. I'm not particularly interested in moving
the software and licenses to a newer machine. So, I will probably try
to keep the machine operational until the end of the mission. Anyway,
I probably will support 10.20 in GCC until 3.5 is released.
I think if Michael can improve gdb under HP-UX 11, we would also see
benefits under HP-UX 10.
Carlos O'Donell has made a New Years resolution to spend a good
portion of his time on gdb for hppa-linux. He has done an excellent
job in improving glibc. Matthew Wilcox has offered a bounty for a
gdb maintainer for hppa-linux:
<http://lists.parisc-linux.org/pipermail/parisc-linux/2004-January/022061.html>.
I managed to build gdb 6.0 under hppa-linux starting from the debian
patches. It only took a couple of small patches. My initial impression
is that it works better than 5.3, particularly with ada code. I did
have a problem with an undefined dwarf2 DIE.
In summary, I'm hopeful that the gdb support for PA-RISC can be improved
in 2004.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2004-01-08 4:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 2:50 Michael Elizabeth Chastain
2004-01-08 4:12 ` John David Anglin [this message]
2004-01-08 17:12 ` Andrew Cagney
2004-01-08 18:04 ` John David Anglin
2004-01-08 18:42 Michael Elizabeth Chastain
2004-01-08 18:53 ` John David Anglin
2004-01-08 19:42 Michael Elizabeth Chastain
2004-01-08 20:30 ` John David Anglin
2004-01-11 15:25 ` Andrew Cagney
2004-01-11 22:06 Michael Elizabeth Chastain
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=200401080411.i084BtKY016377@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=brobecker@act-europe.fr \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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