From: Pedro Alves <palves@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, brobecker@adacore.com
Cc: gdb@sourceware.org
Subject: Re: VAX Ultrix? (Re: GDB dropping support for mips-irix and alpha-tru64)
Date: Wed, 15 Oct 2014 13:22:00 -0000 [thread overview]
Message-ID: <543E7520.8060207@redhat.com> (raw)
In-Reply-To: <201410131603.s9DG3sAq002782@glazunov.sibelius.xs4all.nl>
On 10/13/2014 05:03 PM, Mark Kettenis wrote:
>> Date: Mon, 13 Oct 2014 06:38:09 -0700
>> From: Joel Brobecker <brobecker@adacore.com>
>>
>>> Going over the supported hosts in configure.host, I noticed we still
>>> "support" VAX Ultrix / 4.2BSD:
>>>
>>> vax-*-bsd*) gdb_host=vax ;;
>>> vax-*-ultrix*) gdb_host=vax ;;
>>>
>>> Does it make sense to keep support for old Ultrix given we're
>>> dropping OSF/1 / Tru64?
>>
>> Wikipedia says that VAX production ceased in 2005. The last VAX-specific
>> patch I can see being submitted to gdb-patches is us mentioning support
>> for VAX floats in the Ada mode (which we removed in 2010). VAX VMS was
>> removed in 2010 from BFD. There seems to be some regular activity around
>> VAX on the GCC side, though, but Ultrix itself seems to be no longer be
>> supported.
>
> There are probably quite a few VAXen still running. Just learned last
> week there are still some radiotelescopes around running a VAX to
> control the telescope. But they're probably running VMS on those
> though. If you want, there's the SIMH simulator.
>
>> So this seems to indicate that we will be able to remove support
>> for Ultrix.
>
> FWIW, I kept the VAX Ultrix and VAX 4.2BSD code around as an example
> of how a classic ptrace(2) implementation works. Helped me a great
> bit when refactoring inf-ptrace.c back in the days. Linux really
> turned ptrace(2) into a mess...
For my own education, which code are you referring to though?
The PT_READ_U / PT_WRITE_U bits in inf-ptrace.c?
>
> Other than the educational value, there is no point in keeping Ultrix
> and BSD4.2 support alive. I'm pretty sure that GDB has become too
> bloated to compile and/or run on these systems.
>
>>> Below's the table I was building, listing the full set of
>>> supported hosts, according to configure.host, mapping OS to triplet.
>>
>>> | HP-UX | hppa*-*-hpux* |
>>> | HP-UX | ia64-*-hpux* |
>>
>> I suspect that HP-UX will no longer find any takers. AdaCore had to
>> step-up many many years go to keep those alive. The situation is
>> different today, and we are stepping down.
>
> It'd be somewhat sad to see inf-ttrace.c go. IMHO ttrace(2) is by far
> the best example of how to do a proper threads-aware debugger interface.
Yeah, I agree here.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-10-15 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 18:52 GDB dropping support for mips-irix and alpha-tru64 Joel Brobecker
2014-09-11 20:53 ` Joel Sherrill
2014-09-12 0:30 ` Joel Brobecker
2014-09-12 0:33 ` Andrew Pinski
2014-09-12 1:11 ` Joel Sherrill
2014-09-12 9:53 ` Matthew Fortune
2014-10-11 14:36 ` VAX Ultrix? (Re: GDB dropping support for mips-irix and alpha-tru64) Pedro Alves
2014-10-13 13:38 ` Joel Brobecker
2014-10-13 13:57 ` Maciej W. Rozycki
2014-10-13 15:02 ` Pedro Alves
2014-10-13 16:04 ` Mark Kettenis
2014-10-15 13:22 ` Pedro Alves [this message]
2014-10-17 13:47 ` GDB is removing VAX Ultrix support Pedro Alves
2014-10-24 17:12 ` Support for VAX Ultrix removed Pedro Alves
2014-10-24 17:11 ` GDB dropping support for mips-irix and alpha-tru64 Pedro Alves
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=543E7520.8060207@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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).