This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++ Warnings on trunk

From: Ian Lance Taylor <iant at google dot com>
To: NightStrike <nightstrike at gmail dot com>
Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, "Kai Tietz" <ktietz70 at googlemail dot com>, "Kai Tietz" <Kai dot Tietz at onevision dot com>, "gcc\ at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Tue, 08 Jul 2008 10:11:06 -0700
Subject: Re: C++ Warnings on trunk
References: <b609cb3b0807080932w38b4fc7ft99fcf02b6a734aa5@mail.gmail.com> <m3myksxqv1.fsf@google.com> <b609cb3b0807080958p46c49003i31f04bd4ab9a4523@mail.gmail.com>

NightStrike <nightstrike@gmail.com> writes:

> On 7/8/08, Ian Lance Taylor <iant@google.com> wrote:
>> NightStrike <nightstrike@gmail.com> writes:
>>
>> > I was under the impression that these would be cleaned up before the
>> > -W options were applied to the trunk.
>>
>> It's pretty hard to clean up all the warnings for every possible
>> target.  Also these are only warnings--this code is not compiled with
>> -Werror.
>>
>> In this case, I argue that this code is always compiled with a C
>> compiler, and should never be compiled by a C++ compiler.  Therefore,
>> I believe it is wrong for this code to be compiled with the
>> -Wc++-compat warning enabled.  This should be fixed somewhere in the
>> configure script and/or Makefile.
>
> Is someone currently taking care of that?

I don't know.  It doesn't break the build and as such should be fixed
soon but does not need to be fixed immediately.

Ian

References:
- C++ Warnings on trunk
  - From: NightStrike
- Re: C++ Warnings on trunk
  - From: Ian Lance Taylor
- Re: C++ Warnings on trunk
  - From: NightStrike

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]