From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: palves@redhat.com (Pedro Alves),
gdb-patches@sourceware.org (GDB Patches)
Subject: Re: eliminate deprecated_insert_raw_breakpoint. what's left.
Date: Wed, 10 Sep 2014 14:45:00 -0000 [thread overview]
Message-ID: <201409101445.s8AEjILM007935@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20140910122952.GM28404@adacore.com> from "Joel Brobecker" at Sep 10, 2014 05:29:52 AM
Joel Brobecker wrote:
> > > I would be surprised if anyone still cared about IRIX anymore.
> > > I enjoyed working on that system, but I no longer have access
> > > to it, so can't support it anymore.
> >
> > I see that IRIX seems to be in "Retired Mode" as of 12/31/2013:
> > http://www.sgi.com/tech/irix/?_mips_support.html
>
> And I saw yesterday on the binutils mailing-list that IRIX support
> was removed from GCC already. I think these are all pretty strong
> indicators.
>
> > Do we have a current process to formally obsolete/remove support
> > for old systems?
> >
> > [ I guess another candidate to remove might be Alpha OSF/1 ... ]
>
> Here is what I found:
> https://sourceware.org/gdb/wiki/Internals%20Obsoleting-code
>
> I agree we can obsolete Alpha OSF/1 as well.
Once OSF/1 and IRIX are gone, I hope all of the ECOFF/mdebug debug
format support can go as well (mipsread.c, mdebugread.c etc.) ...
The process documented in the Wiki is a bit weird (adding OBSOLETE
to *every line* of those files ???) and it seems we didn't follow
it in the last major round of obsoleting code either:
https://sourceware.org/ml/gdb-announce/2007/msg00000.html
I think using a process along similar lines might be best.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2014-09-10 14:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 17:46 Pedro Alves
2014-09-08 19:24 ` Joel Brobecker
2014-09-08 21:34 ` Joel Brobecker
2014-09-08 22:50 ` Pedro Alves
2014-09-09 0:25 ` Peter Schauer
2014-09-09 0:16 ` Peter Schauer
2014-09-09 11:39 ` Ulrich Weigand
2014-09-09 12:38 ` Peter Schauer
2014-09-09 21:25 ` Ulrich Weigand
2014-09-10 12:21 ` Joel Brobecker
2014-09-10 13:15 ` Ulrich Weigand
2014-09-10 15:22 ` Pedro Alves
2014-09-09 21:48 ` Ulrich Weigand
2014-09-10 12:29 ` Joel Brobecker
2014-09-10 14:45 ` Ulrich Weigand [this message]
2014-09-10 15:21 ` Pedro Alves
2014-09-10 15:50 ` Joel Brobecker
2014-09-10 16:00 ` Sergio Durigan Junior
2014-09-10 16:36 ` Ulrich Weigand
2014-09-10 18:59 ` New deprecation procedure Pedro Alves
2014-09-11 19:03 ` Joel Brobecker
2014-09-12 8:51 ` Ulrich Weigand
2014-09-10 15:50 ` eliminate deprecated_insert_raw_breakpoint. what's left Maciej W. Rozycki
2014-09-10 16:12 ` [IRIX] eliminate deprecated_insert_raw_breakpoint uses Pedro Alves
2014-09-10 22:44 ` Joel Brobecker
2014-09-10 23:02 ` Pedro Alves
2014-09-11 3:27 ` Joel Brobecker
2014-09-12 19:34 ` Pedro Alves
2014-09-12 20:23 ` Joel Brobecker
2014-10-07 0:25 ` eliminate deprecated_insert_raw_breakpoint. what's left Stan Shebs
2014-09-09 17:33 ` Pedro Alves
[not found] <alpine.DEB.1.10.1409101553070.27075@tp.orcam.me.uk>
2014-09-10 16:45 ` Ulrich Weigand
2014-09-10 19:11 ` Maciej W. Rozycki
2014-09-11 11:50 ` Ulrich Weigand
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=201409101445.s8AEjILM007935@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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