Re: Invert sense of NO_IMPLICIT_EXTERN_C

2018-07-03 Thread Jeff Law
On 07/03/2018 07:50 AM, Nathan Sidwell wrote: > could a global reviewer comment?  This touches a lot of target-specific > config files.  David has kindly checked AIX is ok, the known target > needing the functionality. > > https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01568.html So it's almost

Re: Invert sense of NO_IMPLICIT_EXTERN_C

2018-07-03 Thread Nathan Sidwell
could a global reviewer comment? This touches a lot of target-specific config files. David has kindly checked AIX is ok, the known target needing the functionality. https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01568.html nathan On 06/25/2018 12:48 PM, Nathan Sidwell wrote:

Re: Invert sense of NO_IMPLICIT_EXTERN_C

2018-06-25 Thread David Edelsohn
On Mon, Jun 25, 2018 at 12:48 PM Nathan Sidwell wrote: > > NO_IMPLICIT_EXTERN_C was introduced to tell the compiler that it didn't > need to fake up 'extern "C" { ... }' around system header files. Over > the years more and more system headers have become C++-aware, leading to > more targets

Invert sense of NO_IMPLICIT_EXTERN_C

2018-06-25 Thread Nathan Sidwell
NO_IMPLICIT_EXTERN_C was introduced to tell the compiler that it didn't need to fake up 'extern "C" { ... }' around system header files. Over the years more and more system headers have become C++-aware, leading to more targets defining this macro. Unfortunately because of the sense of this