From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Cc: iain@sandoe.co.uk
Subject: Re: [PATCH] Remove DARWIN_PREFER_DWARF and dead code
Date: Fri, 10 Sep 2021 09:16:03 -0600 [thread overview]
Message-ID: <bc338e5a-4155-3bba-efdf-72607ed6e32f@gmail.com> (raw)
In-Reply-To: <56ros87-62r2-rsr0-8p73-56r6265q6261@fhfr.qr>
On 9/10/2021 1:19 AM, Richard Biener via Gcc-patches wrote:
> This removes the always defined DARWIN_PREFER_DWARF and the code
> guarded by it being not defined, removing the possibility to
> default some i386 darwin configurations to STABS when it would
> not be defined.
>
> OK for trunk?
>
> Thanks,
> Richard.
>
> 2021-09-10 Richard Biener <rguenther@suse.de>
>
> * config/darwin.h (DARWIN_PREFER_DWARF): Do not define.
> * config/i386/darwin.h (PREFERRED_DEBUGGING_TYPE): Do not
> change based on DARWIN_PREFER_DWARF not being defined.
OK. I'm not too worried about supporting 32bit darwin 8 and earlier.
That's got to be at least a decade out of service at this point.
jeff
next prev parent reply other threads:[~2021-09-10 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 7:19 Richard Biener
2021-09-10 15:16 ` Jeff Law [this message]
2021-09-13 19:04 ` Iain Sandoe
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=bc338e5a-4155-3bba-efdf-72607ed6e32f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=rguenther@suse.de \
/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).