From: "Koning, Paul" <Paul.Koning@dell.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Richard Guenther <rguenther@suse.de>,
Jeff Law <jeffreyalaw@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
"ni1d@arrl.net" <ni1d@arrl.net>
Subject: Re: [PATCH][v2] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Wed, 15 Sep 2021 17:18:58 +0000 [thread overview]
Message-ID: <6EA7BCA4-6F50-419B-8A4E-B0FC64F8C096@dell.com> (raw)
In-Reply-To: <e516a3ed-c47e-64ac-e207-36fad473da84@bell.net>
> On Sep 15, 2021, at 11:55 AM, John David Anglin <dave.anglin@bell.net> wrote:
>
> On 2021-09-15 10:06 a.m., Richard Biener wrote:
>>> 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.
> I tend to think targets without any support for debug information should be removed. There is
> some time before GCC 13. This provides a chance for the target to implement DWARF support.
I suppose. But for pdp11 at least, DWARF and ELF are both somewhat unnatural and anachronistic. PDP11 unixes use much older debug formats, and DEC operating systems are more primitive still (no debug symbols at all, of any kind). So for that case at least, supporting the target but without debug symbols would not be a crazy option.
Of course, it would be neat to be able to debug PDP-11 code with GDB...
paul
next prev parent reply other threads:[~2021-09-15 17:19 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
2021-09-15 15:55 ` John David Anglin
2021-09-15 17:18 ` Koning, Paul [this message]
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=6EA7BCA4-6F50-419B-8A4E-B0FC64F8C096@dell.com \
--to=paul.koning@dell.com \
--cc=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).