From: Jeff Law <jeffreyalaw@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
David Edelsohn <dje.gcc@gmail.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Default debug format for AVR
Date: Thu, 8 Apr 2021 08:41:23 -0600 [thread overview]
Message-ID: <6ee7a0a1-1c2f-97a5-b169-e01ea4439f17@gmail.com> (raw)
In-Reply-To: <8e6f1f9b-13cf-c82c-a67b-b35cde4e2e31@polymtl.ca>
On 4/8/2021 8:06 AM, Simon Marchi via Gcc wrote:
> On 2021-04-08 9:11 a.m., David Edelsohn wrote:
>>>> AIX continues to use and support STABS, although it is transitioning
>>>> to DWARF. If this is intended as a general statement about removal of
>>>> STABS support in GCC,
>>> Yes, it is.
>>>
>>> Richard.
>> Richard,
>>
>> It is inappropriate to unilaterally make this decision without
>> discussion with all affected ports and maintainers, without warning,
>> and without deprecation. I request that you rescind this decision.
>>
>> It is somewhat ironic to act as a dictator when we are having a
>> discussion about dictatorial behavior in GCC leadership.
> I don't really want to start such a debate about GCC politics. If stabs
> is not ready to be deleted, that's fine. But it would be good to go
> through all targets for which it is the default (like avr), and see if
> they are ready to be switched to DWARF. That's a baby step towards
> eventually deleting it.
Agreed. I'd bet AIX is the outlier here and that most, if not all,
other ports that may currently be stabs-by-default can switch to
dwarf-by-default with no significant fallout. So we fix everything we
can while we wait for AIX to move forward.
jeff
next prev parent reply other threads:[~2021-04-08 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 1:24 Simon Marchi
2021-04-05 19:36 ` Jim Wilson
2021-04-05 20:54 ` Simon Marchi
2021-04-06 10:33 ` Richard Biener
2021-04-07 23:17 ` David Edelsohn
2021-04-08 6:03 ` Richard Biener
2021-04-08 13:11 ` David Edelsohn
2021-04-08 14:06 ` Simon Marchi
2021-04-08 14:41 ` Jeff Law [this message]
2021-04-08 16:09 ` David Edelsohn
2021-04-08 16:46 ` David Edelsohn
2021-04-13 16:04 ` Jeff Law
2021-04-08 14:05 ` Richard Biener
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=6ee7a0a1-1c2f-97a5-b169-e01ea4439f17@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=simon.marchi@polymtl.ca \
/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).