From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: schwab@linux-m68k.org, dave.anglin@bell.net, ni1d@arrl.net
Subject: Re: [PATCH][v2] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Mon, 13 Sep 2021 07:24:52 -0600 [thread overview]
Message-ID: <7c622dea-ac79-869e-23a0-7d363ec50947@gmail.com> (raw)
In-Reply-To: <66161527-98n2-3060-49ss-67oro67381nq@fhfr.qr>
On 9/13/2021 1:31 AM, Richard Biener wrote:
> This makes defaults.h choose DWARF2_DEBUG if PREFERRED_DEBUGGING_TYPE
> is not specified by the target and NO_DEBUG if DWARF is not supported.
>
> It also makes us warn when STABS is enabled and removes the corresponding
> diagnostic from the Ada frontend. The warnings are pruned from the
> testsuite output via prune_gcc_output.
>
> This leaves the following targets without debug support:
>
> pdp11-*-* pdp11 is a.out, dwarf support is difficult
> m68k*-*-openbsd* it looks like this is a.out as well, at least it does
> not pretend to support DWARF
> hppa[12]*-*-hpux10* does seem to not support DWARF
I would probably argue that hpux10 should just be removed, along with
hpux 7-9 if they haven't been already. It's the epitome of a dead platform.
> vax-*-openbsd* seems to be a.out as well, does not support DWARF
>
> behavior will be like
>
>> ./cc1 -quiet t.c -g
> cc1: warning: target system does not support debug output
>> ./cc1 -quiet t.c -gstabs
> t.c: warning: STABS debugging information is obsolete and not supported anymore
>
> that is, -g is unsupported but -gstabs will generate STABS (the above
> is for pdp11). It would be nice if maintainers could confirm the above
> listed configurations do not support DWARF and weight in whether to
> (apart from pdp11) the specific configurations can be obsoleted or
> adjusted. It looks like we do not have any openbsd maintainer.
> I've discussed the situation for pdp11 with Paul already at some point
> but we didn't reach any conclusion besides that it would be nice to
> move pdp11 to ELF.
>
>
> 2021-09-10 Richard Biener <rguenther@suse.de>
>
> gcc/
> * defaults.h (PREFERRED_DEBUGGING_TYPE): Choose DWARF2_DEBUG
> or NO_DEBUG.
> * toplev.c (process_options): Warn when STABS debugging is
> enabled.
>
> gcc/ada/
> * gcc-interface/misc.c (gnat_post_options): Do not warn
> about DBX_DEBUG use here.
>
> gcc/testsuite/
> * lib/prune.exp: Prune STABS obsoletion message.
OK
jeff
next prev parent reply other threads:[~2021-09-13 13:24 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 [this message]
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
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=7c622dea-ac79-869e-23a0-7d363ec50947@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=ni1d@arrl.net \
--cc=rguenther@suse.de \
--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).