On Mon, Mar 30, 2015 at 02:38:35PM +0200, Michal Marek wrote: > Is this a limitation of a particular ARM ABI or a limitation of a state > of the art ARM linker or something else? It's a limitation of the ARM ISA. Normal PC-relative branches, which are emitted by the C compiler, can branch +/- 32MB for ARM, or +/- 16MB of Thumb. Beyond that, the address offset is not representable in the instruction. To get around that "modern" linkers are able to insert stubs as necessary inbetween the object .text sections to extend the range of these branches (by emitting a chunk of code possibly with some data to extend the range of the branch.) Obviously, gcc can't know before hand that the sum total of all the small object files is going to cause problems, so the compiler can't do this on an "as necessary basis". For most practical kernels, this is not a problem; they normally fit within the PC-relative range. However, the exception is allyesconfig. The question is: how far do we go with allyesconfig... do we want it to work, or is reaching the final link sufficient? If we do tweak stuff to allow the link to work, are we going to try running it? -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
