Re: Build regressions/improvements in v4.14-rc3

2017-10-08 Thread Thomas Meyer
On Sun, Oct 08, 2017 at 09:50:53AM +1100, Michael Ellerman wrote:
> Thomas Meyer  writes:
> 
> > On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
> >> Thomas Meyer  writes:
> >> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> >> ...
> >> >> 
> >> >> I've switched it to using one of the toolchains from Free Electrons,
> >> >> which is built with glibc, and that seems to be working:
> >> >> 
> >> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> >> >> 
> >> >> 
> >> >> Let me know if that's no good.
> >> >
> >> > Cool, excellent! Look good.
> >> >
> >> > Is it also possible to add an allyesconfig and allmodconfig for UML?
> >> 
> >> Sure.
> >> 
> >>   http://kisskb.ellerman.id.au/kisskb/config/484/
> >>   http://kisskb.ellerman.id.au/kisskb/config/485/
> >> 
> >> They don't build :D
> >> 
> >>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file 
> >> or directory
> >> 
> >> 
> >> Can I just disable that driver? I'd prefer not to install too many host
> >> packages just to get UML building.
> >
> > Yes, please disable all CONFIG_UML_NET_* drivers.
> > allmodconfig for UML is good to catch drivers which actually
> > should depend on HAS_IOMEM...
> 
> OK, I did that, and also turned off GCOV, now I get:
> 
>   ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] 
> undefined!
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/13175206/
>

Hi,

build looks good. Thanks for the setup!

Above problem is known, but I guess the driver is unmaintained:
See https://patchwork.kernel.org/patch/9893071/

> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-08 Thread Thomas Meyer
On Sun, Oct 08, 2017 at 09:50:53AM +1100, Michael Ellerman wrote:
> Thomas Meyer  writes:
> 
> > On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
> >> Thomas Meyer  writes:
> >> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> >> ...
> >> >> 
> >> >> I've switched it to using one of the toolchains from Free Electrons,
> >> >> which is built with glibc, and that seems to be working:
> >> >> 
> >> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> >> >> 
> >> >> 
> >> >> Let me know if that's no good.
> >> >
> >> > Cool, excellent! Look good.
> >> >
> >> > Is it also possible to add an allyesconfig and allmodconfig for UML?
> >> 
> >> Sure.
> >> 
> >>   http://kisskb.ellerman.id.au/kisskb/config/484/
> >>   http://kisskb.ellerman.id.au/kisskb/config/485/
> >> 
> >> They don't build :D
> >> 
> >>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file 
> >> or directory
> >> 
> >> 
> >> Can I just disable that driver? I'd prefer not to install too many host
> >> packages just to get UML building.
> >
> > Yes, please disable all CONFIG_UML_NET_* drivers.
> > allmodconfig for UML is good to catch drivers which actually
> > should depend on HAS_IOMEM...
> 
> OK, I did that, and also turned off GCOV, now I get:
> 
>   ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] 
> undefined!
> 
> http://kisskb.ellerman.id.au/kisskb/buildresult/13175206/
>

Hi,

build looks good. Thanks for the setup!

Above problem is known, but I guess the driver is unmaintained:
See https://patchwork.kernel.org/patch/9893071/

> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-07 Thread Michael Ellerman
Thomas Meyer  writes:

> On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
>> Thomas Meyer  writes:
>> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
>> ...
>> >> 
>> >> I've switched it to using one of the toolchains from Free Electrons,
>> >> which is built with glibc, and that seems to be working:
>> >> 
>> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
>> >> 
>> >> 
>> >> Let me know if that's no good.
>> >
>> > Cool, excellent! Look good.
>> >
>> > Is it also possible to add an allyesconfig and allmodconfig for UML?
>> 
>> Sure.
>> 
>>   http://kisskb.ellerman.id.au/kisskb/config/484/
>>   http://kisskb.ellerman.id.au/kisskb/config/485/
>> 
>> They don't build :D
>> 
>>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file 
>> or directory
>> 
>> 
>> Can I just disable that driver? I'd prefer not to install too many host
>> packages just to get UML building.
>
> Yes, please disable all CONFIG_UML_NET_* drivers.
> allmodconfig for UML is good to catch drivers which actually
> should depend on HAS_IOMEM...

OK, I did that, and also turned off GCOV, now I get:

  ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] 
undefined!

http://kisskb.ellerman.id.au/kisskb/buildresult/13175206/

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-07 Thread Michael Ellerman
Thomas Meyer  writes:

> On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
>> Thomas Meyer  writes:
>> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
>> ...
>> >> 
>> >> I've switched it to using one of the toolchains from Free Electrons,
>> >> which is built with glibc, and that seems to be working:
>> >> 
>> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
>> >> 
>> >> 
>> >> Let me know if that's no good.
>> >
>> > Cool, excellent! Look good.
>> >
>> > Is it also possible to add an allyesconfig and allmodconfig for UML?
>> 
>> Sure.
>> 
>>   http://kisskb.ellerman.id.au/kisskb/config/484/
>>   http://kisskb.ellerman.id.au/kisskb/config/485/
>> 
>> They don't build :D
>> 
>>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file 
>> or directory
>> 
>> 
>> Can I just disable that driver? I'd prefer not to install too many host
>> packages just to get UML building.
>
> Yes, please disable all CONFIG_UML_NET_* drivers.
> allmodconfig for UML is good to catch drivers which actually
> should depend on HAS_IOMEM...

OK, I did that, and also turned off GCOV, now I get:

  ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] 
undefined!

http://kisskb.ellerman.id.au/kisskb/buildresult/13175206/

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-05 Thread Thomas Meyer
On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
> Thomas Meyer  writes:
> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> ...
> >> 
> >> I've switched it to using one of the toolchains from Free Electrons,
> >> which is built with glibc, and that seems to be working:
> >> 
> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> >> 
> >> 
> >> Let me know if that's no good.
> >
> > Cool, excellent! Look good.
> >
> > Is it also possible to add an allyesconfig and allmodconfig for UML?
> 
> Sure.
> 
>   http://kisskb.ellerman.id.au/kisskb/config/484/
>   http://kisskb.ellerman.id.au/kisskb/config/485/
> 
> They don't build :D
> 
>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file or 
> directory
> 
> 
> Can I just disable that driver? I'd prefer not to install too many host
> packages just to get UML building.

Yes, please disable all CONFIG_UML_NET_* drivers.
allmodconfig for UML is good to catch drivers which actually
should depend on HAS_IOMEM...

mfg
thomas

> 
> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-05 Thread Thomas Meyer
On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
> Thomas Meyer  writes:
> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> ...
> >> 
> >> I've switched it to using one of the toolchains from Free Electrons,
> >> which is built with glibc, and that seems to be working:
> >> 
> >>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> >> 
> >> 
> >> Let me know if that's no good.
> >
> > Cool, excellent! Look good.
> >
> > Is it also possible to add an allyesconfig and allmodconfig for UML?
> 
> Sure.
> 
>   http://kisskb.ellerman.id.au/kisskb/config/484/
>   http://kisskb.ellerman.id.au/kisskb/config/485/
> 
> They don't build :D
> 
>   arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file or 
> directory
> 
> 
> Can I just disable that driver? I'd prefer not to install too many host
> packages just to get UML building.

Yes, please disable all CONFIG_UML_NET_* drivers.
allmodconfig for UML is good to catch drivers which actually
should depend on HAS_IOMEM...

mfg
thomas

> 
> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-04 Thread Michael Ellerman
Thomas Meyer  writes:
> On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
...
>> 
>> I've switched it to using one of the toolchains from Free Electrons,
>> which is built with glibc, and that seems to be working:
>> 
>>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
>> 
>> 
>> Let me know if that's no good.
>
> Cool, excellent! Look good.
>
> Is it also possible to add an allyesconfig and allmodconfig for UML?

Sure.

  http://kisskb.ellerman.id.au/kisskb/config/484/
  http://kisskb.ellerman.id.au/kisskb/config/485/

They don't build :D

  arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file or 
directory


Can I just disable that driver? I'd prefer not to install too many host
packages just to get UML building.

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-04 Thread Michael Ellerman
Thomas Meyer  writes:
> On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
...
>> 
>> I've switched it to using one of the toolchains from Free Electrons,
>> which is built with glibc, and that seems to be working:
>> 
>>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
>> 
>> 
>> Let me know if that's no good.
>
> Cool, excellent! Look good.
>
> Is it also possible to add an allyesconfig and allmodconfig for UML?

Sure.

  http://kisskb.ellerman.id.au/kisskb/config/484/
  http://kisskb.ellerman.id.au/kisskb/config/485/

They don't build :D

  arch/um/drivers/vde_user.c:8:24: fatal error: libvdeplug.h: No such file or 
directory


Can I just disable that driver? I'd prefer not to install too many host
packages just to get UML building.

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-03 Thread Thomas Meyer
On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> Geert Uytterhoeven  writes:
> 
> > Hi Thomas,
> >
> > On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
> >> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> >>> Below is the list of build error/warning regressions/improvements in
> >>> v4.14-rc3[1] compared to v4.13[2].
> >>
> >> a question regarding the um-defconfig build:
> >> http://kisskb.ellerman.id.au/kisskb/target/2974/
> >>
> >> The error thrown looks like a libc installation error. can this be fixed
> >> on the build server?
> >
> > I'll let Michael answer that question...
> 
> Thanks for the report.
> 
> I think the problem is simply that the toolchain has no libc, so it
> can't build UML (?).

Yes, UML needs a libc.

> 
> I've switched it to using one of the toolchains from Free Electrons,
> which is built with glibc, and that seems to be working:
> 
>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> 
> 
> Let me know if that's no good.

Cool, excellent! Look good.

Is it also possible to add an allyesconfig and allmodconfig for UML?

Many thanks for looking into this.

with kind regards
thomas

> 
> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-03 Thread Thomas Meyer
On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> Geert Uytterhoeven  writes:
> 
> > Hi Thomas,
> >
> > On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
> >> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> >>> Below is the list of build error/warning regressions/improvements in
> >>> v4.14-rc3[1] compared to v4.13[2].
> >>
> >> a question regarding the um-defconfig build:
> >> http://kisskb.ellerman.id.au/kisskb/target/2974/
> >>
> >> The error thrown looks like a libc installation error. can this be fixed
> >> on the build server?
> >
> > I'll let Michael answer that question...
> 
> Thanks for the report.
> 
> I think the problem is simply that the toolchain has no libc, so it
> can't build UML (?).

Yes, UML needs a libc.

> 
> I've switched it to using one of the toolchains from Free Electrons,
> which is built with glibc, and that seems to be working:
> 
>   http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/
> 
> 
> Let me know if that's no good.

Cool, excellent! Look good.

Is it also possible to add an allyesconfig and allmodconfig for UML?

Many thanks for looking into this.

with kind regards
thomas

> 
> cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-03 Thread Michael Ellerman
Geert Uytterhoeven  writes:

> Hi Thomas,
>
> On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
>> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
>>> Below is the list of build error/warning regressions/improvements in
>>> v4.14-rc3[1] compared to v4.13[2].
>>
>> a question regarding the um-defconfig build:
>> http://kisskb.ellerman.id.au/kisskb/target/2974/
>>
>> The error thrown looks like a libc installation error. can this be fixed
>> on the build server?
>
> I'll let Michael answer that question...

Thanks for the report.

I think the problem is simply that the toolchain has no libc, so it
can't build UML (?).

I've switched it to using one of the toolchains from Free Electrons,
which is built with glibc, and that seems to be working:

  http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/


Let me know if that's no good.

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-03 Thread Michael Ellerman
Geert Uytterhoeven  writes:

> Hi Thomas,
>
> On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
>> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
>>> Below is the list of build error/warning regressions/improvements in
>>> v4.14-rc3[1] compared to v4.13[2].
>>
>> a question regarding the um-defconfig build:
>> http://kisskb.ellerman.id.au/kisskb/target/2974/
>>
>> The error thrown looks like a libc installation error. can this be fixed
>> on the build server?
>
> I'll let Michael answer that question...

Thanks for the report.

I think the problem is simply that the toolchain has no libc, so it
can't build UML (?).

I've switched it to using one of the toolchains from Free Electrons,
which is built with glibc, and that seems to be working:

  http://kisskb.ellerman.id.au/kisskb/buildresult/13171418/


Let me know if that's no good.

cheers


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
Hi Thomas,

On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v4.14-rc3[1] compared to v4.13[2].
>
> a question regarding the um-defconfig build:
> http://kisskb.ellerman.id.au/kisskb/target/2974/
>
> The error thrown looks like a libc installation error. can this be fixed
> on the build server?

I'll let Michael answer that question...

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
Hi Thomas,

On Mon, Oct 2, 2017 at 4:11 PM, Thomas Meyer  wrote:
> On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v4.14-rc3[1] compared to v4.13[2].
>
> a question regarding the um-defconfig build:
> http://kisskb.ellerman.id.au/kisskb/target/2974/
>
> The error thrown looks like a libc installation error. can this be fixed
> on the build server?

I'll let Michael answer that question...

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Thomas Meyer
On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.14-rc3[1] compared to v4.13[2].

Hi,

a question regarding the um-defconfig build:
http://kisskb.ellerman.id.au/kisskb/target/2974/

The error thrown looks like a libc installation error. can this be fixed
on the build server?

> Summarized:
>   - build errors: +8/-0
>   - build warnings: +1155/-6331
> 
> 
> Gr{oetje,eeting}s,
> 
>   Geert

with kind regards
thomas

> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- 
> ge...@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like 
> that.
>   -- Linus Torvalds


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Thomas Meyer
On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.14-rc3[1] compared to v4.13[2].

Hi,

a question regarding the um-defconfig build:
http://kisskb.ellerman.id.au/kisskb/target/2974/

The error thrown looks like a libc installation error. can this be fixed
on the build server?

> Summarized:
>   - build errors: +8/-0
>   - build warnings: +1155/-6331
> 
> 
> Gr{oetje,eeting}s,
> 
>   Geert

with kind regards
thomas

> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- 
> ge...@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like 
> that.
>   -- Linus Torvalds


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
On Mon, Oct 2, 2017 at 11:49 AM, Geert Uytterhoeven
 wrote:
> JFYI, when comparing v4.14-rc3[1] to v4.14-rc2[3], the summaries are:
>   - build errors: +2/-0

Just the eternal sh4/sh-randconfig noise.

> [1] 
> http://kisskb.ellerman.id.au/kisskb/head/9e66317d3c92ddaab330c125dfe9d06eee268aff/
>  (all 267 configs)
> [3] 
> http://kisskb.ellerman.id.au/kisskb/head/e19b205be43d11bff638cad4487008c48d21c103/
>  (all 267 configs)

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Re: Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
On Mon, Oct 2, 2017 at 11:49 AM, Geert Uytterhoeven
 wrote:
> JFYI, when comparing v4.14-rc3[1] to v4.14-rc2[3], the summaries are:
>   - build errors: +2/-0

Just the eternal sh4/sh-randconfig noise.

> [1] 
> http://kisskb.ellerman.id.au/kisskb/head/9e66317d3c92ddaab330c125dfe9d06eee268aff/
>  (all 267 configs)
> [3] 
> http://kisskb.ellerman.id.au/kisskb/head/e19b205be43d11bff638cad4487008c48d21c103/
>  (all 267 configs)

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
Below is the list of build error/warning regressions/improvements in
v4.14-rc3[1] compared to v4.13[2].

Summarized:
  - build errors: +8/-0
  - build warnings: +1155/-6331

JFYI, when comparing v4.14-rc3[1] to v4.14-rc2[3], the summaries are:
  - build errors: +2/-0
  - build warnings: +533/-404

Happy fixing! ;-)

Thanks to the linux-next team for providing the build service.

[1] 
http://kisskb.ellerman.id.au/kisskb/head/9e66317d3c92ddaab330c125dfe9d06eee268aff/
 (all 267 configs)
[2] 
http://kisskb.ellerman.id.au/kisskb/head/569dbb88e80deb68974ef6fdd6a13edb9d686261/
 (all 267 configs)
[3] 
http://kisskb.ellerman.id.au/kisskb/head/e19b205be43d11bff638cad4487008c48d21c103/
 (all 267 configs)


*** ERRORS ***

8 error regressions:
  + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: 'cached_to_uncached' 
undeclared (first use in this function):  => 99:17
  + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: implicit declaration 
of function 'cpu_context' [-Werror=implicit-function-declaration]:  => 192:2
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
'per_cpu_secondary_mm' undeclared (first use in this function):  => 81:10
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
implicit declaration of function 'per_cpu' 
[-Werror=implicit-function-declaration]:  => 81:2
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
implicit declaration of function 'smp_processor_id' 
[-Werror=implicit-function-declaration]:  => 79:12
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
unknown type name 'per_cpu_secondary_mm':  => 22:37
  + /home/kisskb/slave/src/drivers/net/ethernet/intel/i40e/i40e_ethtool.c: 
error: implicit declaration of function 'cmpxchg64' 
[-Werror=implicit-function-declaration]:  => 4150:6
  + error: "__cmpxchg_u64" [drivers/net/ethernet/intel/i40e/i40e.ko] 
undefined!:  => N/A


*** WARNINGS ***

[Deleted 923 lines about "warning: ... [-Wpointer-sign]" on parisc-allmodconfig]
[Deleted 6154 lines about "warning: -ffunction-sections disabled; it makes 
profiling impossible [enabled by default]" on parisc-allmodconfig]

1155 warning regressions:
  + /home/kisskb/slave/src/arch/powerpc/platforms/ps3/device-init.c: warning: 
the frame size of 2112 bytes is larger than 2048 bytes [-Wframe-larger-than=]:  
=> 888:1
  + /home/kisskb/slave/src/arch/x86/entry/vsyscall/vsyscall_64.c: warning: 
'syscall_nr' may be used uninitialized in this function [-Wuninitialized]:  => 
210:16
  + /home/kisskb/slave/src/arch/x86/events/amd/ibs.c: warning: 'config' may be 
used uninitialized in this function [-Wuninitialized]:  => 306:11
  + /home/kisskb/slave/src/arch/x86/kernel/cpu/intel_rdt_ctrlmondata.c: 
warning: 'data' may be used uninitialized in this function [-Wuninitialized]:  
=> 119:14, 68:14
  + /home/kisskb/slave/src/arch/x86/kernel/espfix_64.c: warning: 'rand' may be 
used uninitialized in this function [-Wuninitialized]:  => 118:22
  + /home/kisskb/slave/src/arch/x86/kernel/hw_breakpoint.c: warning: 'align' 
may be used uninitialized in this function [-Wuninitialized]: 361:20 => 361:2, 
361:20
  + /home/kisskb/slave/src/arch/x86/kernel/ksysfs.c: warning: 'size' may be 
used uninitialized in this function [-Wuninitialized]:  => 227:17
  + /home/kisskb/slave/src/block/bfq-iosched.c: warning: 'bfqd' may be used 
uninitialized in this function [-Wuninitialized]:  => 3746:2
  + /home/kisskb/slave/src/block/bfq-wf2q.c: warning: 'root' may be used 
uninitialized in this function [-Wuninitialized]:  => 812:24
  + /home/kisskb/slave/src/block/blk-cgroup.c: warning: the frame size of 1160 
bytes is larger than 1024 bytes [-Wframe-larger-than=]:  => 354:1
  + /home/kisskb/slave/src/block/blk-merge.c: warning: 'bbio' may be used 
uninitialized in this function [-Wuninitialized]:  => 284:2
  + /home/kisskb/slave/src/block/blk-sysfs.c: warning: 'val' may be used 
uninitialized in this function [-Wuninitialized]:  => 458:2
  + /home/kisskb/slave/src/block/bsg.c: warning: 'op' may be used uninitialized 
in this function [-Wuninitialized]:  => 236:5
  + /home/kisskb/slave/src/crypto/algif_aead.c: warning: 'crypto_aead_copy_sgl' 
uses dynamic stack allocation [enabled by default]:  => 91:1
  + /home/kisskb/slave/src/crypto/async_tx/async_tx.c: warning: 'chan' may be 
used uninitialized in this function [-Wuninitialized]:  => 258:18
  + /home/kisskb/slave/src/drivers/ata/libata-core.c: warning: 'native_sectors' 
may be used uninitialized in this function [-Wuninitialized]:  => 1377:3
  + /home/kisskb/slave/src/drivers/ata/libata-scsi.c: warning: 'dev' may be 
used uninitialized in this function [-Wuninitialized]:  => 4610:3
  + /home/kisskb/slave/src/drivers/ata/libata-scsi.c: warning: 
'last_failed_dev' may be used uninitialized in this function [-Wuninitialized]: 
 => 4610:3
  + /home/kisskb/slave/src/drivers/base/memory.c: warning: 'section_nr' may be 
used uninitialized in this function [-Wuninitialized]:  => 

Build regressions/improvements in v4.14-rc3

2017-10-02 Thread Geert Uytterhoeven
Below is the list of build error/warning regressions/improvements in
v4.14-rc3[1] compared to v4.13[2].

Summarized:
  - build errors: +8/-0
  - build warnings: +1155/-6331

JFYI, when comparing v4.14-rc3[1] to v4.14-rc2[3], the summaries are:
  - build errors: +2/-0
  - build warnings: +533/-404

Happy fixing! ;-)

Thanks to the linux-next team for providing the build service.

[1] 
http://kisskb.ellerman.id.au/kisskb/head/9e66317d3c92ddaab330c125dfe9d06eee268aff/
 (all 267 configs)
[2] 
http://kisskb.ellerman.id.au/kisskb/head/569dbb88e80deb68974ef6fdd6a13edb9d686261/
 (all 267 configs)
[3] 
http://kisskb.ellerman.id.au/kisskb/head/e19b205be43d11bff638cad4487008c48d21c103/
 (all 267 configs)


*** ERRORS ***

8 error regressions:
  + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: 'cached_to_uncached' 
undeclared (first use in this function):  => 99:17
  + /home/kisskb/slave/src/arch/sh/mm/cache-sh4.c: error: implicit declaration 
of function 'cpu_context' [-Werror=implicit-function-declaration]:  => 192:2
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
'per_cpu_secondary_mm' undeclared (first use in this function):  => 81:10
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
implicit declaration of function 'per_cpu' 
[-Werror=implicit-function-declaration]:  => 81:2
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
implicit declaration of function 'smp_processor_id' 
[-Werror=implicit-function-declaration]:  => 79:12
  + /home/kisskb/slave/src/arch/sparc/include/asm/mmu_context_64.h: error: 
unknown type name 'per_cpu_secondary_mm':  => 22:37
  + /home/kisskb/slave/src/drivers/net/ethernet/intel/i40e/i40e_ethtool.c: 
error: implicit declaration of function 'cmpxchg64' 
[-Werror=implicit-function-declaration]:  => 4150:6
  + error: "__cmpxchg_u64" [drivers/net/ethernet/intel/i40e/i40e.ko] 
undefined!:  => N/A


*** WARNINGS ***

[Deleted 923 lines about "warning: ... [-Wpointer-sign]" on parisc-allmodconfig]
[Deleted 6154 lines about "warning: -ffunction-sections disabled; it makes 
profiling impossible [enabled by default]" on parisc-allmodconfig]

1155 warning regressions:
  + /home/kisskb/slave/src/arch/powerpc/platforms/ps3/device-init.c: warning: 
the frame size of 2112 bytes is larger than 2048 bytes [-Wframe-larger-than=]:  
=> 888:1
  + /home/kisskb/slave/src/arch/x86/entry/vsyscall/vsyscall_64.c: warning: 
'syscall_nr' may be used uninitialized in this function [-Wuninitialized]:  => 
210:16
  + /home/kisskb/slave/src/arch/x86/events/amd/ibs.c: warning: 'config' may be 
used uninitialized in this function [-Wuninitialized]:  => 306:11
  + /home/kisskb/slave/src/arch/x86/kernel/cpu/intel_rdt_ctrlmondata.c: 
warning: 'data' may be used uninitialized in this function [-Wuninitialized]:  
=> 119:14, 68:14
  + /home/kisskb/slave/src/arch/x86/kernel/espfix_64.c: warning: 'rand' may be 
used uninitialized in this function [-Wuninitialized]:  => 118:22
  + /home/kisskb/slave/src/arch/x86/kernel/hw_breakpoint.c: warning: 'align' 
may be used uninitialized in this function [-Wuninitialized]: 361:20 => 361:2, 
361:20
  + /home/kisskb/slave/src/arch/x86/kernel/ksysfs.c: warning: 'size' may be 
used uninitialized in this function [-Wuninitialized]:  => 227:17
  + /home/kisskb/slave/src/block/bfq-iosched.c: warning: 'bfqd' may be used 
uninitialized in this function [-Wuninitialized]:  => 3746:2
  + /home/kisskb/slave/src/block/bfq-wf2q.c: warning: 'root' may be used 
uninitialized in this function [-Wuninitialized]:  => 812:24
  + /home/kisskb/slave/src/block/blk-cgroup.c: warning: the frame size of 1160 
bytes is larger than 1024 bytes [-Wframe-larger-than=]:  => 354:1
  + /home/kisskb/slave/src/block/blk-merge.c: warning: 'bbio' may be used 
uninitialized in this function [-Wuninitialized]:  => 284:2
  + /home/kisskb/slave/src/block/blk-sysfs.c: warning: 'val' may be used 
uninitialized in this function [-Wuninitialized]:  => 458:2
  + /home/kisskb/slave/src/block/bsg.c: warning: 'op' may be used uninitialized 
in this function [-Wuninitialized]:  => 236:5
  + /home/kisskb/slave/src/crypto/algif_aead.c: warning: 'crypto_aead_copy_sgl' 
uses dynamic stack allocation [enabled by default]:  => 91:1
  + /home/kisskb/slave/src/crypto/async_tx/async_tx.c: warning: 'chan' may be 
used uninitialized in this function [-Wuninitialized]:  => 258:18
  + /home/kisskb/slave/src/drivers/ata/libata-core.c: warning: 'native_sectors' 
may be used uninitialized in this function [-Wuninitialized]:  => 1377:3
  + /home/kisskb/slave/src/drivers/ata/libata-scsi.c: warning: 'dev' may be 
used uninitialized in this function [-Wuninitialized]:  => 4610:3
  + /home/kisskb/slave/src/drivers/ata/libata-scsi.c: warning: 
'last_failed_dev' may be used uninitialized in this function [-Wuninitialized]: 
 => 4610:3
  + /home/kisskb/slave/src/drivers/base/memory.c: warning: 'section_nr' may be 
used uninitialized in this function [-Wuninitialized]:  =>