From: Jeff Law <jeffreyalaw@gmail.com>
To: "John David Anglin" <dave.anglin@bell.net>,
"Martin Liška" <mliska@suse.cz>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][V3] 32-bit PA-RISC with HP-UX: remove deprecated ports
Date: Wed, 31 Aug 2022 11:24:00 -0600 [thread overview]
Message-ID: <3cf72707-54c1-009c-0fb2-bc63a8c991a0@gmail.com> (raw)
In-Reply-To: <cb1924f9-a769-2063-3624-916d8acacec7@bell.net>
On 8/31/2022 10:40 AM, John David Anglin wrote:
> On 2022-08-31 11:35 a.m., Jeff Law wrote:
>> It looks like you removed the pa-bsd and pa-osf targets too. Those
>> were so niche that I doubt anyone else would notice.
> That should be okay. I have never heard of anyone building these.
> There is no config for these in config.gcc.
Right. Those were used almost exclusively by my former colleagues at
the U of Utah and their industry partners. All the relevant projects
and machines have long since been retired.
>
> hppa*-*-openbsd* and hppa*-*-netbsd* are still somewhat used.
Right. I mentally lump these in with the -linux port.
Jeff
next prev parent reply other threads:[~2022-08-31 17:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 7:15 [PATCH] " Martin Liška
2022-08-26 7:20 ` Andreas Schwab
2022-08-26 7:22 ` Martin Liška
2022-08-26 19:09 ` John David Anglin
2022-08-26 19:09 ` John David Anglin
2022-08-28 16:34 ` John David Anglin
2022-08-28 16:34 ` John David Anglin
2022-08-29 14:06 ` Martin Liška
2022-08-29 14:06 ` Martin Liška
2022-08-30 18:39 ` John David Anglin
2022-08-30 18:39 ` John David Anglin
2022-08-30 19:00 ` John David Anglin
2022-08-30 19:00 ` John David Anglin
2022-08-30 19:51 ` John David Anglin
2022-08-30 19:51 ` John David Anglin
2022-08-31 0:13 ` Jeff Law
2022-08-31 0:32 ` John David Anglin
2022-08-31 7:21 ` [PATCH][V3] " Martin Liška
2022-08-31 15:35 ` Jeff Law
2022-08-31 16:40 ` John David Anglin
2022-08-31 17:24 ` Jeff Law [this message]
2022-09-01 13:08 ` John David Anglin
2022-09-01 13:08 ` John David Anglin
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=3cf72707-54c1-009c-0fb2-bc63a8c991a0@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).