From: Nathan Sidwell <nathan@acm.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Deprecate not defining NO_IMPLICIT_EXTERN_C
Date: Thu, 22 Mar 2018 12:16:00 -0000 [thread overview]
Message-ID: <9a3c085a-68ea-37b4-a135-58a774540ef3@acm.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1803212119020.3411@digraph.polyomino.org.uk>
On 03/21/2018 05:28 PM, Joseph Myers wrote:
> My list from 2005 of targets not defining NO_IMPLICIT_EXTERN_C then is
> <https://gcc.gnu.org/ml/gcc/2005-05/msg00377.html>.
Thanks for the link. I see you floated inverting the sense of the
switch -- which would be good, as it appears we still can't remove it.
> I think this should become a target hook, where the default is
> implicit_extern_c returning false and only AIX (and any other OSes
> requiring it) sets the hook to return true.
Yeah, I guess target hook might be the way to go these days.
Anyway, clearly a post-gcc8 thing.
nathan
--
Nathan Sidwell
prev parent reply other threads:[~2018-03-22 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 12:32 Nathan Sidwell
2018-03-21 14:18 ` Richard Earnshaw (lists)
2018-03-21 14:38 ` David Edelsohn
2018-03-21 15:42 ` Nathan Sidwell
2018-03-21 21:33 ` Joseph Myers
2018-03-22 12:16 ` Nathan Sidwell [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=9a3c085a-68ea-37b4-a135-58a774540ef3@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).