[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2375c9f90909220705m6767ace3y5b431d1aa26ef945@mail.gmail.com>
Date: Tue, 22 Sep 2009 22:05:08 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: Julia Lawall <julia@...u.dk>, jdike@...toit.com,
user-mode-linux-user@...ts.sourceforge.net,
user-mode-linux-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 5/5] arch/um: remove duplicate structure field
initialization
On Tue, Sep 22, 2009 at 12:26 AM, Segher Boessenkool
<segher@...nel.crashing.org> wrote:
>> "
>> The initialization shall occur in initializer list order, each
>> initializer provided for a particular subobject overriding any
>> previously listed initializer for the same subobject [...]
>> "
>>
>> I am wondering why gcc doesn't (can't?) complain about this?
>
> Does -Woverride-init (included in -Wextra / -W) not work? If so, please
> file a bug report.
Hmm, right, it works, but it seems that Linux kernel doesn't use it.
Maybe we should add it? :-/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists