From:
Date: Fri, 23 Jun 2017 06:46:53 +
> I will insert this before Nicholas' series.
Thank you.
t; linux-kernel@vger.kernel.org; Yamada, Masahiro/山田 真弘
> > ; amo...@gmail.com
> > Subject: Re: linux-next: build failure after merge of most trees
> >
> > Hi all,
> >
> > On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller
> > wrote:
> > >
.@gmail.com
> Subject: Re: linux-next: build failure after merge of most trees
>
> Hi all,
>
> On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller
> wrote:
> >
> > Feel free to merge it into your series:
> >
> >
[snip]
>
> I a
Hi all,
On Thu, 22 Jun 2017 10:56:48 -0400 (EDT) David Miller
wrote:
>
> Feel free to merge it into your series:
>
>
> sparc64: Use indirect calls in hamming weight stubs.
>
> Otherwise, depending upon link order, the branch relocation
> limits could be exceeded.
>
> Sign
On Thu, 22 Jun 2017 10:29:23 -0400 (EDT)
David Miller wrote:
> From: David Miller
> Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT)
>
> > From: Nicholas Piggin
> > Date: Thu, 22 Jun 2017 18:41:16 +1000
> >
> >> Is there any way for the linker to place the inputs to avoid unresolvable
> >> reloc
On Thu, 22 Jun 2017 10:56:48 -0400 (EDT)
David Miller wrote:
> From: Nicholas Piggin
> Date: Fri, 23 Jun 2017 00:33:39 +1000
>
> > On Thu, 22 Jun 2017 10:13:06 -0400 (EDT)
> > David Miller wrote:
> >
> >> From: Nicholas Piggin
> >> Date: Thu, 22 Jun 2017 18:41:16 +1000
> >>
> >> > Is th
From: Nicholas Piggin
Date: Fri, 23 Jun 2017 00:33:39 +1000
> On Thu, 22 Jun 2017 10:13:06 -0400 (EDT)
> David Miller wrote:
>
>> From: Nicholas Piggin
>> Date: Thu, 22 Jun 2017 18:41:16 +1000
>>
>> > Is there any way for the linker to place the inputs to avoid unresolvable
>> > relocations w
On Thu, 22 Jun 2017 23:43:10 +0930
Alan Modra wrote:
> On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote:
> > Is there any way for the linker to place the inputs to avoid unresolvable
> > relocations where possible?
>
> Not without quite a lot of work writing support for that fea
On Thu, 22 Jun 2017 10:13:06 -0400 (EDT)
David Miller wrote:
> From: Nicholas Piggin
> Date: Thu, 22 Jun 2017 18:41:16 +1000
>
> > Is there any way for the linker to place the inputs to avoid unresolvable
> > relocations where possible?
>
> I don't think so.
>
> > A way to work around this
From: David Miller
Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT)
> From: Nicholas Piggin
> Date: Thu, 22 Jun 2017 18:41:16 +1000
>
>> Is there any way for the linker to place the inputs to avoid unresolvable
>> relocations where possible?
>
> I don't think so.
>
>> A way to work around this is
On Thu, Jun 22, 2017 at 06:41:16PM +1000, Nicholas Piggin wrote:
> Is there any way for the linker to place the inputs to avoid unresolvable
> relocations where possible?
Not without quite a lot of work writing support for that feature.
--
Alan Modra
Australia Development Lab, IBM
From: Nicholas Piggin
Date: Thu, 22 Jun 2017 18:41:16 +1000
> Is there any way for the linker to place the inputs to avoid unresolvable
> relocations where possible?
I don't think so.
> A way to work around this is to make arch/sparc/lib/hweight.o an obj-y
> rather than lib-y. That's a hack bec
CC'ing Alan
On Thu, 22 Jun 2017 15:24:41 +1000
Stephen Rothwell wrote:
> Hi Dave,
>
> After merging almost all the trees, today's linux-next build (sparc64
> defconfig) failed like this:
>
> arch/sparc/lib/hweight.o: In function `__arch_hweight8':
> (.text+0x0): relocation truncated to fit: R_
Hi Nick,
On Thu, 22 Jun 2017 16:20:11 +1000 Stephen Rothwell
wrote:
>
> On Thu, 22 Jun 2017 15:49:52 +1000 Nicholas Piggin wrote:
> >
> > It could be this
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=thin-ar&id=ec2c9c20f0efab37ae31de44fe0617aa612
Hi Nicholas,
On Thu, 22 Jun 2017 15:49:52 +1000 Nicholas Piggin wrote:
>
> It could be this
>
> https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=thin-ar&id=ec2c9c20f0efab37ae31de44fe0617aa61283905
>
> kbuild: handle libs-y archives separately from built-i
On Thu, 22 Jun 2017 15:24:41 +1000
Stephen Rothwell wrote:
> Hi Dave,
>
> After merging almost all the trees, today's linux-next build (sparc64
> defconfig) failed like this:
>
> arch/sparc/lib/hweight.o: In function `__arch_hweight8':
> (.text+0x0): relocation truncated to fit: R_SPARC_WDISP19
Hi Dave,
After merging almost all the trees, today's linux-next build (sparc64
defconfig) failed like this:
arch/sparc/lib/hweight.o: In function `__arch_hweight8':
(.text+0x0): relocation truncated to fit: R_SPARC_WDISP19 against symbol
`__sw_hweight8' defined in .text section in lib/hweight.o
17 matches
Mail list logo