From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Remove Irix 6 workaround from DWARF abbrev reader
Date: Mon, 15 Mar 2021 01:25:54 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.2103150113290.33195@angie.orcam.me.uk> (raw)
In-Reply-To: <20210306170142.1960263-2-tom@tromey.com>
On Sat, 6 Mar 2021, Tom Tromey wrote:
> abbrev_table::read has a workaround for Irix 6. The last release of
> Irix was in 2006, and (according to Wikipedia) hardware produced after
> 2007 cannot run Irix. I think this workaround can safely be retired.
I missed this submission previously.
For the record, we dropped IRIX target support in GDB years ago, with
commit 3831839c089c ("Delete IRIX support"). It could have been useful to
have a reference to said commit included with the change description, alas
it didn't happen.
We continue having IRIX support in binutils, because the underlying ELF
format peculiarities continue being used by some embedded targets and just
removing the IRIX target triplets in these circumstances would be rather
pointless and merely an potential unnecessary complication for someone who
may still be using GNU binutils for IRIX. I suspect the OS may still have
a niche use, perhaps among the vintage computing enthusiasts.
Maciej
next prev parent reply other threads:[~2021-03-15 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 17:01 [PATCH 0/2] Two minor abbrev improvements Tom Tromey
2021-03-06 17:01 ` [PATCH 1/2] Remove Irix 6 workaround from DWARF abbrev reader Tom Tromey
2021-03-15 0:25 ` Maciej W. Rozycki [this message]
2021-03-18 14:12 ` Tom de Vries
2021-03-06 17:01 ` [PATCH 2/2] Constify abbrev_table::lookup_abbrev Tom Tromey
2021-03-08 4:00 ` [PATCH 0/2] Two minor abbrev improvements Simon Marchi
2021-03-13 18:04 ` Tom Tromey
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=alpine.DEB.2.21.2103150113290.33195@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).