[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56AEFFF1.1010404@bmw-carit.de>
Date: Mon, 1 Feb 2016 07:49:21 +0100
From: Daniel Wagner <daniel.wagner@...-carit.de>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
CC: <linux-kernel@...r.kernel.org>, <linux-rt-users@...r.kernel.org>,
<linux-kbuild@...r.kernel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Boqun Feng <boqun.feng@...il.com>
Subject: Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible
pointer check into error
On 01/29/2016 07:55 PM, Paul Gortmaker wrote:
> [Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible pointer check into error] On 29/01/2016 (Fri 13:17) Daniel Wagner wrote:
>
>> On 01/28/2016 03:44 PM, Daniel Wagner wrote:
>>> +# enforce correct pointer usage
>>> +KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types)
>>> +
>>
>> As it turns out there are a few fallouts by that one. I'll send fixes
>> for it.
>
> Did you try non-x86 builds with this applied? I'd be really surprised
> if there were just a few, once you did allyesconfig/allmodconfig for
> ARM, MIPS, PPC, etc.
I have tried this with non-x86 builds and apart of a few problems all
looked fine. As it turns out I was using too old cross tools from
kernel.org [1]. Luckily Fengguang's kbuild robot did catch a bunch of
them (see the patches in this series).
Since Thomas was also surprised that only a bunch of them showed up,
I'll better give it another go with more recent compilers.
cheers,
daniel
[1] https://www.kernel.org/pub/tools/crosstool
Powered by blists - more mailing lists