From: Eli Zaretskii <eliz@gnu.org>
To: Mark Wielaard <mark@klomp.org>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [RFC] Deprecate stabs
Date: Fri, 20 Jan 2023 15:47:04 +0200 [thread overview]
Message-ID: <83y1pxmi7b.fsf@gnu.org> (raw)
In-Reply-To: <ee4112c16ec742e9d6bb0a47b264a148c3402fb2.camel@klomp.org> (message from Mark Wielaard on Fri, 20 Jan 2023 13:48:27 +0100)
> From: Mark Wielaard <mark@klomp.org>
> Cc: gdb-patches@sourceware.org
> Date: Fri, 20 Jan 2023 13:48:27 +0100
>
> On Thu, 2023-01-19 at 20:00 +0200, Eli Zaretskii wrote:
> > > From: Tom Tromey <tom@tromey.com>
> > > Cc: Tom Tromey <tom@tromey.com>
> > > Date: Thu, 19 Jan 2023 10:41:56 -0700
> > >
> > > I think it's time to deprecate stabs, and plan to remove all support
> > > for them. Stabs are long since obsolete and are not really maintained
> > > in gdb. GCC deprecated them in 12 and will remove them as well.
> >
> > IMO, we should remove support for stabs _after_ GCC, not before and
> > not together with it. Not sure if "GDB 15" fits that.
>
> stabs support was deprecated in GCC 12 [1] and has been removed in GCC
> 13 [2], which is in pre-release state (stage 4) now. So the above plan
> actually trails GCC by two releases. So I would actually recommend
> adding a deprecation notice in GDB 13 and removal in GDB 14.
I see no reason to rush with removal of features. Someone could still
be using them. And users don't necessarily upgrade to the latest
version of GCC as soon as it is released, they could go on using an
older version for some years.
We should be friendlier to our users than MS and Google.
next prev parent reply other threads:[~2023-01-20 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:41 Tom Tromey
2023-01-19 18:00 ` Eli Zaretskii
2023-01-20 12:48 ` Mark Wielaard
2023-01-20 13:47 ` Eli Zaretskii [this message]
2023-02-11 2:26 ` Tom Tromey
2023-02-11 8:29 ` Eli Zaretskii
2023-02-14 16:36 ` Simon Marchi
2023-02-12 12:53 ` Mark Wielaard
2023-07-06 17:44 ` Pedro Alves
2023-08-30 17:48 ` Tom Tromey
2023-08-30 17:58 ` Eli Zaretskii
2023-08-30 19:15 ` Kevin Buettner
2023-08-30 20:47 ` John Baldwin
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=83y1pxmi7b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.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).