Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, 11 Aug 2016 15:04:00 +0200 Arnd Bergmann wrote: > On Thursday, August 11, 2016 10:43:20 PM CEST Nicholas Piggin wrote: > > On Wed, 03 Aug 2016 22:13:28 +0200 > > Final ld time > > inclink > > real0m0.378s > > user0m0.304s > > sys 0m0.076s > > > > thinarc

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 11, 2016 10:43:20 PM CEST Nicholas Piggin wrote: > On Wed, 03 Aug 2016 22:13:28 +0200 > Arnd Bergmann wrote: > > > On Wednesday, August 3, 2016 2:44:29 PM CEST Segher Boessenkool wrote: > > > Hi Arnd, > > > > > > On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wed, 03 Aug 2016 22:13:28 +0200 Arnd Bergmann wrote: > On Wednesday, August 3, 2016 2:44:29 PM CEST Segher Boessenkool wrote: > > Hi Arnd, > > > > On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote: > > > From my first look, it seems that all of lib/*.o is now

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Saturday, August 6, 2016 2:17:16 PM CEST Nicholas Piggin wrote: > On Fri, 05 Aug 2016 21:16:00 +0200 > Arnd Bergmann wrote: > > > On Saturday, August 6, 2016 2:16:42 AM CEST Nicholas Piggin wrote: > > > > > > > > diff --git a/include/asm-generic/vmlinux.lds.h > > > >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Fri, 05 Aug 2016 21:16:00 +0200 Arnd Bergmann wrote: > On Saturday, August 6, 2016 2:16:42 AM CEST Nicholas Piggin wrote: > > > > > > diff --git a/include/asm-generic/vmlinux.lds.h > > > b/include/asm-generic/vmlinux.lds.h > > > index 0ec807d69f18..7a3ad269fa23 100644 > > >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Saturday, August 6, 2016 2:16:42 AM CEST Nicholas Piggin wrote: > > > > diff --git a/include/asm-generic/vmlinux.lds.h > > b/include/asm-generic/vmlinux.lds.h > > index 0ec807d69f18..7a3ad269fa23 100644 > > --- a/include/asm-generic/vmlinux.lds.h > > +++ b/include/asm-generic/vmlinux.lds.h >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Fri, 05 Aug 2016 18:01:13 +0200 Arnd Bergmann wrote: > On Friday, August 5, 2016 10:26:25 PM CEST Nicholas Piggin wrote: > > On Fri, 05 Aug 2016 12:17:27 +0200 > > Arnd Bergmann wrote: > > > > and I also get link errors for the .text.fixup section > > > for

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Friday, August 5, 2016 10:26:25 PM CEST Nicholas Piggin wrote: > On Fri, 05 Aug 2016 12:17:27 +0200 > Arnd Bergmann wrote: > > and I also get link errors for the .text.fixup section > > for any users of __put_user() in really large kernels: > >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Fri, 05 Aug 2016 12:17:27 +0200 Arnd Bergmann wrote: > On Friday, August 5, 2016 6:41:08 PM CEST Nicholas Piggin wrote: > > On Thu, 4 Aug 2016 12:06:41 -0500 > > Segher Boessenkool wrote: > > > > > On Thu, Aug 04, 2016 at 06:10:57PM +0200, Arnd

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Friday, August 5, 2016 6:41:08 PM CEST Nicholas Piggin wrote: > On Thu, 4 Aug 2016 12:06:41 -0500 > Segher Boessenkool wrote: > > > On Thu, Aug 04, 2016 at 06:10:57PM +0200, Arnd Bergmann wrote: > > > On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, 4 Aug 2016 12:06:41 -0500 Segher Boessenkool wrote: > On Thu, Aug 04, 2016 at 06:10:57PM +0200, Arnd Bergmann wrote: > > On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin wrote: > > > > > + __used \

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, Aug 04, 2016 at 06:10:57PM +0200, Arnd Bergmann wrote: > On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin wrote: > > > + __used \ > > + __attribute__((section("___kentry" "+" #sym ",\"a\",@note #"), used)) \ > > > I've just

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin wrote: > + __used \ > + __attribute__((section("___kentry" "+" #sym ",\"a\",@note #"), used)) \ I've just started testing this, but the first problem I ran into is that @ and #

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 11:54:18 PM CEST Nicholas Piggin wrote: > On Thu, 4 Aug 2016 22:31:39 +1000 > Nicholas Piggin wrote: > > On Thu, 04 Aug 2016 14:09:02 +0200 > > Arnd Bergmann wrote: > > > Nicolas Pitre has done some related work, adding him to Cc.

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, 4 Aug 2016 22:31:39 +1000 Nicholas Piggin wrote: > On Thu, 04 Aug 2016 14:09:02 +0200 > Arnd Bergmann wrote: > > Nicolas Pitre has done some related work, adding him to Cc. IIRC we have > > actually had multiple implementations of

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, 04 Aug 2016 14:09:02 +0200 Arnd Bergmann wrote: > On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin wrote: > > On Thu, 04 Aug 2016 12:37:41 +0200 Arnd Bergmann wrote: > > > On Thursday, August 4, 2016 11:00:49 AM CEST Arnd Bergmann wrote: > >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 9:47:13 PM CEST Nicholas Piggin wrote: > On Thu, 04 Aug 2016 12:37:41 +0200 Arnd Bergmann wrote: > > On Thursday, August 4, 2016 11:00:49 AM CEST Arnd Bergmann wrote: > > > I tried this > > > > > > diff --git a/scripts/link-vmlinux.sh

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thu, 04 Aug 2016 12:37:41 +0200 Arnd Bergmann wrote: > On Thursday, August 4, 2016 11:00:49 AM CEST Arnd Bergmann wrote: > > I tried this > > > > diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh > > index b5e40ed86e60..89bca1a25916 100755 > > ---

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 11:00:49 AM CEST Arnd Bergmann wrote: > I tried this > > diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh > index b5e40ed86e60..89bca1a25916 100755 > --- a/scripts/link-vmlinux.sh > +++ b/scripts/link-vmlinux.sh > @@ -44,7 +44,7 @@ modpost_link() >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 10:10:51 AM CEST Stephen Rothwell wrote: > Hi Arnd, > > On Wed, 03 Aug 2016 20:52:48 +0200 Arnd Bergmann wrote: > > > > Most of the difference appears to be in branch trampolines (634 added, > > 559 removed, 14837 unchanged) as you suspect, but I also

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Hi Arnd, On Wed, 03 Aug 2016 20:52:48 +0200 Arnd Bergmann wrote: > > Most of the difference appears to be in branch trampolines (634 added, > 559 removed, 14837 unchanged) as you suspect, but I also see a couple > of symbols show up in vmlinux that were not there before: > > -A

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wednesday, August 3, 2016 2:44:29 PM CEST Segher Boessenkool wrote: > Hi Arnd, > > On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote: > > From my first look, it seems that all of lib/*.o is now getting linked > > into vmlinux, while we traditionally leave out everything from lib/ >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Hi Arnd, On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote: > From my first look, it seems that all of lib/*.o is now getting linked > into vmlinux, while we traditionally leave out everything from lib/ > that is not referenced. > > I also see a noticeable overhead in link time, the

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Thursday, August 4, 2016 1:37:29 AM CEST Nicholas Piggin wrote: > > I've attached what I'm using, which builds and runs for me without > any work. Your arch obviously has to select the option to use it. > > text data bss dec hex filename > 11196784 1185024

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wed, 03 Aug 2016 14:29:13 +0200 Arnd Bergmann wrote: > On Wednesday, August 3, 2016 10:19:11 PM CEST Stephen Rothwell wrote: > > Hi Arnd, > > > > On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote: > > > > > > Using a different way to link the kernel

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wednesday, August 3, 2016 10:19:11 PM CEST Stephen Rothwell wrote: > Hi Arnd, > > On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote: > > > > Using a different way to link the kernel would also help us with > > the remaining allyesconfig problem on ARM, as the problem is

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Hi Arnd, On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote: > > Using a different way to link the kernel would also help us with > the remaining allyesconfig problem on ARM, as the problem is only in > 'ld -r' not producing trampolines for symbols that later cannot get > them

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wednesday, August 3, 2016 10:23:24 AM CEST Stephen Rothwell wrote: > Hi Luis, > > On Wed, 3 Aug 2016 00:02:43 +0200 "Luis R. Rodriguez" > wrote: > > > > Thanks for the confirmation. For how long is it known this is broken? > > Does anyone care and fix these ? Or is this

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

"Luis R. Rodriguez" writes: > Are linux-next builds being tested for powerpc with allyesconfig and > allmodconfig ? Yes, every single version: http://kisskb.ellerman.id.au/kisskb/target/2659/ > I have some changes I'm making and while debugging my > build issues I decided

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Hi Luis, On Wed, 3 Aug 2016 00:02:43 +0200 "Luis R. Rodriguez" wrote: > > Thanks for the confirmation. For how long is it known this is broken? > Does anyone care and fix these ? Or is this best effort? This has been broken for many years :-( I have a couple of times almost

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Wednesday, August 3, 2016 12:02:43 AM CEST Luis R. Rodriguez wrote: > On Tue, Aug 02, 2016 at 02:58:39PM -0700, Guenter Roeck wrote: > > On Tue, Aug 02, 2016 at 01:07:09PM -0700, Luis R. Rodriguez wrote: > > > Are linux-next builds being tested for powerpc with allyesconfig and > > >

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Tue, Aug 02, 2016 at 02:58:39PM -0700, Guenter Roeck wrote: > On Tue, Aug 02, 2016 at 01:07:09PM -0700, Luis R. Rodriguez wrote: > > Are linux-next builds being tested for powerpc with allyesconfig and > > allmodconfig ? I have some changes I'm making and while debugging my > > build issues I

Re: powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

On Tue, Aug 02, 2016 at 01:07:09PM -0700, Luis R. Rodriguez wrote: > Are linux-next builds being tested for powerpc with allyesconfig and > allmodconfig ? I have some changes I'm making and while debugging my > build issues I decided to give a clean build a shot and see linux-next > next-20160729

powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Are linux-next builds being tested for powerpc with allyesconfig and allmodconfig ? I have some changes I'm making and while debugging my build issues I decided to give a clean build a shot and see linux-next next-20160729 up to next-20160729 all have build failures without my changes. I get: