summary refs log tree commit diff
path: root/arch/arc/boot
diff options
context:
space:
mode:
authorYuriy Kolerov <yuriy.kolerov@synopsys.com>2015-08-12 17:23:32 +0300
committerVineet Gupta <vgupta@synopsys.com>2015-08-20 18:53:15 +0530
commit6de6066c0d24a66df465cf87a4041ef7ef35ba6f (patch)
treef04687c44c4d3e537fcd83e287c9132d8737ef1e /arch/arc/boot
parenteb2cd8b72b08fe56998600aee8a5dff93f7be5a2 (diff)
downloadlinux-6de6066c0d24a66df465cf87a4041ef7ef35ba6f.tar.gz
ARC: change some branchs to jumps to resolve linkage errors
When kernel's binary becomes large enough (32M and more) errors
may occur during the final linkage stage. It happens because
the build system uses short relocations for ARC  by default.
This problem may be easily resolved by passing -mlong-calls
option to GCC to use long absolute jumps (j) instead of short
relative branchs (b).

But there are fragments of pure assembler code exist which use
branchs in inappropriate places and cause a linkage error because
of relocations overflow.

First of these fragments is .fixup insertion in futex.h and
unaligned.c. It inserts a code in the separate section (.fixup)
with branch instruction. It leads to the linkage error when
kernel becomes large.

Second of these fragments is calling scheduler's functions
(common kernel code) from entry.S of ARC's code. When kernel's
binary becomes large it may lead to the linkage error because
scheduler may occur far enough from ARC's code in the final
binary.

Signed-off-by: Yuriy Kolerov <yuriy.kolerov@synopsys.com>
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'arch/arc/boot')
0 files changed, 0 insertions, 0 deletions