From: Richard Biener <rguenther@suse.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, schwab@linux-m68k.org, ni1d@arrl.net
Subject: Re: [PATCH][v2] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Wed, 15 Sep 2021 16:06:56 +0200 (CEST) [thread overview]
Message-ID: <r6p03o40-3322-psp4-8p82-6r20rsnqrp77@fhfr.qr> (raw)
In-Reply-To: <263956ec-73dc-b92a-e009-87da7d4f141f@bell.net>
On Wed, 15 Sep 2021, John David Anglin wrote:
> On 2021-09-15 2:26 a.m., Richard Biener wrote:
> >> I believe the 32-bit SOM target should be deprecated. I'm the only one maintaining it and I had some health issues earlier this year.
> >> The current versions should suffice for several years.
> > Do you think it's worth keeping the 32bit pa hpux targets for another
> > release but guarded with --enable-obsolete or can we remove those
> > configurations right away?
> I would choose --enable-obsolete. Currently, things more or less work except for modules.
OK, I see.
> >
> > In the current setting configurations that do not support DWARF will
> > get no debug info with -g (with a warning that this happens) and
> > STABS debug info with -gstabs (with a warning about its deprecation).
> > That might not be the final outcome for GCC 12 but it's the minimal
> > change I'm working towards.
> Is there a simple way to enable -gstabs in build?
Currently not. If we're retaining more than pdp11 with a non-DWARF
config I'm considering to allow STABS by default for those without
diagnostics for GCC 12.
With GCC 13 we'll definitely either remove the configurations or
leave the target without any support for debug info.
Richard.
next prev parent reply other threads:[~2021-09-15 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 7:31 Richard Biener
2021-09-13 13:24 ` Jeff Law
2021-09-13 13:47 ` Richard Biener
2021-09-13 13:53 ` Jeff Law
2021-09-13 14:58 ` John David Anglin
2021-09-13 15:05 ` Jeff Law
2021-09-13 15:44 ` John David Anglin
2021-09-13 15:52 ` Jeff Law
2021-09-15 6:26 ` Richard Biener
2021-09-15 13:27 ` John David Anglin
2021-09-15 14:06 ` Richard Biener [this message]
2021-09-15 15:55 ` John David Anglin
2021-09-15 17:18 ` Koning, Paul
2021-09-13 16:52 ` Koning, Paul
2021-09-13 19:06 ` Jeff Law
2021-09-15 20:23 ` Koning, Paul
2021-09-16 7:41 ` Richard Biener
2021-09-16 15:05 ` Jeff Law
2021-09-16 16:46 ` Koning, Paul
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=r6p03o40-3322-psp4-8p82-6r20rsnqrp77@fhfr.qr \
--to=rguenther@suse.de \
--cc=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=ni1d@arrl.net \
--cc=schwab@linux-m68k.org \
/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).