public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: "Koning, Paul" <Paul.Koning@dell.com>,
	Richard Guenther <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Andreas Schwab <schwab@linux-m68k.org>,
	"dave.anglin@bell.net" <dave.anglin@bell.net>,
	"ni1d@arrl.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 13:06:19 -0600	[thread overview]
Message-ID: <81f5fede-d55a-da9b-aca7-3f461d4d32b3@gmail.com> (raw)
In-Reply-To: <0E74A665-3565-4E4A-8DD8-D9883EE14C49@dell.com>



On 9/13/2021 10:52 AM, Koning, Paul wrote:
>
>> On Sep 13, 2021, at 3:31 AM, Richard Biener <rguenther@suse.de> 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
> I'll admit that I don't know much about debug formats.  It is definitely the case that pdp11 output is a.out (it may be BSD 2.x style a.out -- which I think is somewhat different though it's been many years since I looked at that, and then only briefly).  I guess that constrains which debug formats can be used, but I don't know any details.
My recollection of aout stabs is mostly lost.  IIRC we'd emit .stabs 
directives to the assembler which would turn into symbol table entries.

Embedded stabs used the same underlying stab strings, but instead put 
the information into a special section.  That requires an object format 
that supports named sections, so it's a non-starter for a.out.

dwarf also requires named sections.  While in theory one could probably 
do something hackish like dwarf embedded in .stab directives, that just 
seems just awful.

>
> pdp11-elf was done as an experiment by someone else, in binutils.  I'll ask about the status of that.  If it's possible to deliver that, it would presumably enable DWARF support.  Is that all common code so it's a matter of enabling it, or would "DWARF machine details for pdp11" have to be defined?
That's going to be the best path forward.  Get the pdp11-elf bits 
working and the dwarf2 debugging stuff should come along for free.

Jeff


  reply	other threads:[~2021-09-13 19: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
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 [this message]
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=81f5fede-d55a-da9b-aca7-3f461d4d32b3@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=Paul.Koning@dell.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).