From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: <jan.kratochvil@redhat.com>
Subject: Re: [patch] Remove HPUX
Date: Mon, 01 Dec 2014 14:21:00 -0000 [thread overview]
Message-ID: <547C794B.6030108@ericsson.com> (raw)
In-Reply-To: <20141016220028.GA25839@host2.jankratochvil.net>
On 2014-10-16 06:00 PM, Jan Kratochvil wrote:
> Hi,
>
> IIUC it is a pre-requisite for IPv6 support, some UNICes do not support
> getaddrinfo required for IPv6. But coincidentally such UNICes are no longer
> really supported by GDB. Therefore it was concluded we can remove all such
> UNICes and then we can implement IPv6 easily with getaddrinfo.
>
> In mail
> Re: getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections]
> Message-ID: <20140211034157.GG5485@adacore.com>
> https://sourceware.org/ml/gdb-patches/2014-02/msg00333.html
> Joel said:
> # [...] HP-UX [...] are probably de facto unmaintained, at this point.
>
> So I chose HP-UX first for this patch.
>
>
> # We should probably send an announcement if we ever implement a change
> # we know might be breaking some platforms, though.
>
> Not sure if anything should be really done for this part.
>
> I did not test it anyhow, not sure how, it still builds on Linux.
>
> I did not investigate too much which other parts of GDB could be removed
> along, there may be some dead code now (but it always has been).
I stumbled upon one of them in elfread.c (elf_symtab_read), a comment mentions a special case for hpux.
> I am not sure if somread.c really can be removed or not, I have removed it.
>
> The same patch is also available as a GIT branch at:
> https://sourceware.org/git/?p=archer.git;a=shortlog;h=refs/heads/jankratochvil/nohpux
>
> 24 files changed, 47 insertions(+), 7384 deletions(-)
>
>
> Thanks,
> Jan
next prev parent reply other threads:[~2014-12-01 14:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 23:00 Jan Kratochvil
2014-10-17 0:21 ` Michael Eager
2014-10-17 13:26 ` Joel Brobecker
2014-10-17 17:18 ` Michael Eager
2014-11-19 18:54 ` Jan Kratochvil
2014-11-19 19:39 ` Michael Eager
2014-11-21 9:32 ` Pedro Alves
2015-03-13 19:26 ` [commit] " Jan Kratochvil
2015-03-13 19:43 ` Pedro Alves
2015-03-13 19:46 ` Jan Kratochvil
2015-03-13 19:55 ` Pedro Alves
2015-03-13 19:57 ` Jan Kratochvil
2015-03-10 5:04 ` Sergio Durigan Junior
2015-03-10 14:23 ` Michael Eager
2014-11-21 3:20 ` Yao Qi
2015-03-13 19:17 ` [testsuite patch] Remove gdb.hp [Re: [patch] Remove HPUX] Jan Kratochvil
2015-03-18 14:58 ` Remove --xdb? (Re: [testsuite patch] Remove gdb.hp [Re: [patch] Remove HPUX]) Pedro Alves
2015-03-20 16:17 ` [commit] [testsuite patch] Remove gdb.hp Jan Kratochvil
2015-03-20 17:48 ` [patch] Re: Remove --xdb? (Re: [testsuite patch] Remove gdb.hp) Jan Kratochvil
2015-04-10 19:27 ` Pedro Alves
2015-04-11 17:06 ` [doc patch] Remove --xdb Jan Kratochvil
2015-04-11 17:40 ` Eli Zaretskii
2015-04-11 17:54 ` [commit] " Jan Kratochvil
2014-12-01 14:21 ` Simon Marchi [this message]
2015-03-11 21:57 ` [patch] Remove HPUX Jan Kratochvil
2015-03-12 17:05 ` Pedro Alves
2015-03-13 18:34 ` Jan Kratochvil
2015-03-13 19:40 ` 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=547C794B.6030108@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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