public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Deprecate stabs
Date: Thu, 6 Jul 2023 18:44:23 +0100	[thread overview]
Message-ID: <0d183bc4-8c59-ac65-91c3-3477e7bb2546@palves.net> (raw)
In-Reply-To: <20230119174156.654402-1-tom@tromey.com>

Hi!

This subject came up on IRC today.

On 2023-01-19 17:41, Tom Tromey wrote:
> 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.


Meanwhile, half a year passed, and GCC 13 is out.

My position with stabs for years had been that, as long as GCC needs it for some ports,
we should keep it.  Since GCC has since removed support for stabs, I think we're now
free to remove it too.

I think we should mark stabs deprecated for GDB 14.  We can discuss more when to actually
remove it, but IMO, the sooner we mark it deprecated, the sooner people will be aware of our
intentions.  FWIW, I do support removing it in GDB 15.

Pedro Alves

> ---
>  gdb/NEWS | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index c0aac212e30..317f6536bc0 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -5,6 +5,9 @@
>  
>  * MI version 1 has been removed.
>  
> +* Support for the stabs debugging format is deprecated, and it will be
> +  removed in GDB 15.
> +
>  * GDB has initial built-in support for the Debugger Adapter Protocol.
>    This support requires that GDB be built with Python scripting
>    enabled.


  parent reply	other threads:[~2023-07-06 17:46 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
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 [this message]
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=0d183bc4-8c59-ac65-91c3-3477e7bb2546@palves.net \
    --to=pedro@palves.net \
    --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).