From: Zack Weinberg <zack@codesourcery.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RS6000 buried treasure - NO_IMPLICIT_EXTERN_C
Date: Fri, 08 Nov 2002 11:20:00 -0000 [thread overview]
Message-ID: <20021108192055.GB1194@egil.codesourcery.com> (raw)
In-Reply-To: <200211081556.KAA21772@makai.watson.ibm.com>
On Fri, Nov 08, 2002 at 10:56:24AM -0500, David Edelsohn wrote:
> >
> > I am inclined to enable NO_IMPLICIT_EXTERN_C for the entire directory,
> > in rs6000.h. What few targets this is inappropriate for -- I'm
> > willing to bet that's either none, or only AIX 3.1 -- can #undef it
> > again.
> >
> > Comments?
>
> I could see placing this in sysv4.h, but not rs6000.h. I do not
> believe that GCC's fixincludes completely addresses the C++ issues in the
> AIX header files. IBM Visual Age C++ distributes its own system header
> files.
Defining or not defining NO_IMPLICIT_EXTERN_C addresses only one C++
issue with system headers. It should be defined by all targets where
the system headers already wrap declarations in extern "C" { ... }
when appropriate, and not defined otherwise. Is it really the case
that no AIX release provides extern "C" markers?
zw
next prev parent reply other threads:[~2002-11-08 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 20:50 Zack Weinberg
2002-11-08 7:56 ` David Edelsohn
2002-11-08 11:20 ` Zack Weinberg [this message]
2002-11-08 11:35 ` Dale Johannesen
2002-11-08 13:14 ` Stan Shebs
2002-11-08 13:48 ` Zack Weinberg
2002-11-08 14:23 ` David Edelsohn
2002-11-08 11:10 ` Mark Mitchell
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=20021108192055.GB1194@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=dje@watson.ibm.com \
--cc=gcc-patches@gcc.gnu.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).