From: Jeff Law <jeffreyalaw@gmail.com>
To: John David Anglin <dave.anglin@bell.net>,
Richard Biener <rguenther@suse.de>
Cc: 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: Mon, 13 Sep 2021 09:05:45 -0600 [thread overview]
Message-ID: <bd556d4c-74de-1669-7509-d8d0b34439e5@gmail.com> (raw)
In-Reply-To: <f55756b0-f02e-29e1-a1a3-4323d22e3345@bell.net>
On 9/13/2021 8:58 AM, John David Anglin wrote:
> On 2021-09-13 9:53 a.m., Jeff Law wrote:
>>> It is in fact also hpux11*, thus all 32bit pa configs that do not support
>>> DWARF (for whatever reasons).
>> We used embedded stabs for SOM (the native format for 32bit PA). SOM is a variant of COFF and could easily support dwarf I would think since
>> it had support for fairly arbitrary sections. Hell, it was already supporting embedded stabs as well as HP's proprietary debugging format.
>>
>> But I'd consider 32bit SOM on hpux11 dead too :-)
> I don't disagree but 32bit SOM still builds on hpux11:
> https://gcc.gnu.org/pipermail/gcc-testresults/2021-August/718130.html
>
> Suspect the change will cause a lot of warnings.
It might, but with stabs going away something needs to be done with
these legacy systems. Either they need to move into the modern world,
deal with the diagnostic or get dropped.
>
> There is some support for hpux10/11 in qemu but it takes a lot of work to provide the build infrastructure needed for gcc.
I would think so.
>
> DWARF isn't supported because we lack named sections. That could be worked around
> but probably the gdb versions that work on 32-bit hpux11 wouldn't support DWARF.
I'd be a bit surprised if that were true. dwarf support has been around
a long long time in GDB. Hell, it was around when I did the original
64bit PA work back in the 90s.
Jeff
next prev parent reply other threads:[~2021-09-13 15:05 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 [this message]
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=bd556d4c-74de-1669-7509-d8d0b34439e5@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).