On Mon, 18 Jun 2012, Steven Bosscher wrote:
The attached patch removes NO_IMPLICIT_EXTERN_C, and replaces its sole
user with IMPLICIT_EXTERN_C to avoid the double negations (#ifndef
NO_IMPLICIT_EXTERN_C, etc.).
Bootstrapped and tested on x86_64-unknown-linux-gnu. OK for trunk?
I saw it
Hello,
For targets that do not define NO_IMPLICIT_EXTERN_C, GCC assumes that
included system headers are implicitly wrapped in 'extern C {...}'.
I could not find where this target macro was introduced, but it is
very old (it is already mentioned in FSFChangeLog.10 for a change in
1995). AFAICT,
On Mon, 18 Jun 2012, Steven Bosscher wrote:
For targets that do not define NO_IMPLICIT_EXTERN_C, GCC assumes that
included system headers are implicitly wrapped in 'extern C {...}'.
I could not find where this target macro was introduced, but it is
very old (it is already mentioned in
On Mon, Jun 18, 2012 at 1:12 PM, Joseph S. Myers
jos...@codesourcery.com wrote:
On Mon, 18 Jun 2012, Steven Bosscher wrote:
For targets that do not define NO_IMPLICIT_EXTERN_C, GCC assumes that
included system headers are implicitly wrapped in 'extern C {...}'.
I could not find where this
On Mon, Jun 18, 2012 at 7:12 AM, Joseph S. Myers
jos...@codesourcery.com wrote:
On Mon, 18 Jun 2012, Steven Bosscher wrote:
For targets that do not define NO_IMPLICIT_EXTERN_C, GCC assumes that
included system headers are implicitly wrapped in 'extern C {...}'.
I could not find where this
