public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jim Wilson <jimw@sifive.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Default debug format for AVR
Date: Mon, 5 Apr 2021 16:54:47 -0400	[thread overview]
Message-ID: <3d21f80d-6747-23fc-ab2c-3ebb53d5dd45@polymtl.ca> (raw)
In-Reply-To: <CAFyWVaZiMGKidzC8iHhXvEXMVTtvFjkzX3Hr3_ptR=OpSG0kpQ@mail.gmail.com>

On 2021-04-05 3:36 p.m., Jim Wilson wrote:> On Sat, Apr 3, 2021 at 6:24 PM Simon Marchi via Gcc <gcc@gcc.gnu.org <mailto:gcc@gcc.gnu.org>> wrote:
> 
>     The default debug format (when using only -g) for the AVR target is
>     stabs.  Is there a reason for it not being DWARF, and would it be
>     possible to maybe consider possibly thinking about making it default to
>     DWARF?  I am asking because the support for stabs in GDB is pretty much
>     untested and bit-rotting, so I think it would be more useful for
>     everyone to use DWARF.
> 
> 
> I tried to deprecate the stabs support a little over 4 years ago.
>     https://gcc.gnu.org/pipermail/gcc-patches/2017-December/489296.html <https://gcc.gnu.org/pipermail/gcc-patches/2017-December/489296.html>
> There was a suggestion to change the error to a warning, but my startup company job kept me so busy I never had a chance to follow up on this.
> 
> I would like to see the stabs support deprecated and the later removed from gcc.  No new features have been added in a long time, and it is only being maintained in the sense that when it fails it is fixed to ignore source code constructs that it doesn't support.  The longer it survives in this state, the less useful it becomes.
> 
> Jim

You have 100% my suppose on this.  The longer stabs survives (especially
as the default for an arch), the longer some people who don't know the
intricacies of debug formats could use it without knowing, and that
does them a disservice.

Simon

  reply	other threads:[~2021-04-05 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04  1:24 Simon Marchi
2021-04-05 19:36 ` Jim Wilson
2021-04-05 20:54   ` Simon Marchi [this message]
2021-04-06 10:33     ` Richard Biener
2021-04-07 23:17       ` David Edelsohn
2021-04-08  6:03         ` Richard Biener
2021-04-08 13:11           ` David Edelsohn
2021-04-08 14:06             ` Simon Marchi
2021-04-08 14:41               ` Jeff Law
2021-04-08 16:09                 ` David Edelsohn
2021-04-08 16:46                   ` David Edelsohn
2021-04-13 16:04                   ` Jeff Law
2021-04-08 14:05           ` Richard Biener

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=3d21f80d-6747-23fc-ab2c-3ebb53d5dd45@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=jimw@sifive.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).