On Thu, 22 Jun 2017 10:29:23 -0400 (EDT) David Miller <davem@xxxxxxxxxxxxx> wrote: > From: David Miller <davem@xxxxxxxxxxxxx> > Date: Thu, 22 Jun 2017 10:13:06 -0400 (EDT) > > > From: Nicholas Piggin <npiggin@xxxxxxxxx> > > 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 because it just serves to move the > >> input location, but not really any more of a hack than the current code > >> that also only works because of input locations... > > > > I could adjust those branches in the sparc code into indirect calls > > but it's going to perform a bit poorly on older cpus. > > > > Something like this: > > I just wanted to mention something in passing. > > On sparc64 we patch the first two instructions of memcpy, memset, > bzero, etc. in order to vector them to cpu optimized routines. > > And we use the same kind of branch there. > > Now because the branches are to routines in the same directory it > should never exceed the relocation limits. > > However, if the relocation limits were exceeded in this case, the > build would still succeed and the kernel would be simply broken and > not bootup properly. Powerpc has similar problems with linking, particularly in patch code. What it does is to actually link the patch code into the kernel as well in another section, so the branch target is resolved by the linker. When moving the patch code at runtime, the branch offset is adjusted. So it does get a link error if things don't work there. I guess the other thing you could do is a build-time check over your patch code with a custom script or tool. If you're in the same directory it should be okay, unless it is split between obj-y/built-in.o and lib-y/lib.a then you might have a problem. Thanks, Nick -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
