From: "Koning, Paul" <Paul.Koning@dell.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Richard Guenther <rguenther@suse.de>,
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: Thu, 16 Sep 2021 16:46:16 +0000 [thread overview]
Message-ID: <AB96C731-6390-43B0-9FCE-7E5F6484B7AC@dell.com> (raw)
In-Reply-To: <3b13a7c8-dd7a-c5a9-1767-47fe649329e8@gmail.com>
> On Sep 16, 2021, at 11:05 AM, Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
> On 9/16/2021 1:41 AM, Richard Biener wrote:
>> ...
>> That said - yes, I'd consider a.out purely legacy and not fit
>> for the future. But it never came up on the radar of standing
>> in the way of modernizing GCC in any area.
> I'd definitely consider a.out & SOM as purely legacy. As long as they continue to work, great, but I wouldn't make any significant investment in either. And yes, there are mechanisms in collect2 to support things like global initializers/finalizers on a.out systems.
"Legacy" sounds fine. My main concern was whether it was, or is likely to become soon, "deprecated" or "unsupported". For an old platform to use legacy formats is perfectly sensible, for it to use deprecated mechanisms is not.
For this to work, if there are no supported debug formats for the object format in question -- which will be the case for a.out with STABS going away -- that would mean you'd get output without debug symbols. There was a suggestion that this wouldn't be allowed and that it would be grounds for removing such platforms. I'd rather not see things tied like that.
paul
prev parent reply other threads:[~2021-09-16 16:46 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
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 [this message]
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=AB96C731-6390-43B0-9FCE-7E5F6484B7AC@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).