musl/arch/sh/reloc.h

#if __BYTE_ORDER == __BIG_ENDIAN
#define ENDIAN_SUFFIX "eb"
#else
#define ENDIAN_SUFFIX ""
#endif

#define LDSO_ARCH "sh" ENDIAN_SUFFIX

#define TPOFF_K 8

#define REL_SYMBOLIC    R_SH_DIR32
#define REL_OFFSET      R_SH_REL32
#define REL_GOT         R_SH_GLOB_DAT
#define REL_PLT         R_SH_JMP_SLOT
#define REL_RELATIVE    R_SH_RELATIVE
#define REL_COPY        R_SH_COPY
#define REL_DTPMOD      R_SH_TLS_DTPMOD32
#define REL_DTPOFF      R_SH_TLS_DTPOFF32
#define REL_TPOFF       R_SH_TLS_TPOFF32

#define CRTJMP(pc,sp) __asm__ __volatile__( \
	"jmp @%0 ; mov %1,r15" : : "r"(pc), "r"(sp) : "memory" )
fix endian subarchs for sh arch default endianness for sh on linux is little, and while conventions vary, "eb" seems to be the most widely used suffix for big endian. 2014-02-27 22:20:44 -05:00			`#if __BYTE_ORDER == __BIG_ENDIAN`
			`#define ENDIAN_SUFFIX "eb"`
superh port 2013-10-05 05:13:18 -05:00			`#else`
			`#define ENDIAN_SUFFIX ""`
			`#endif`

			`#define LDSO_ARCH "sh" ENDIAN_SUFFIX`

refactor to remove arch-specific relocation code from dynamic linker this was one of the main instances of ugly code duplication: all archs use basically the same types of relocations, but roughly equivalent logic was duplicated for each arch to account for the different naming and numbering of relocation types and variation in whether REL or RELA records are used. as an added bonus, both REL and RELA are now supported on all archs, regardless of which is used by the standard toolchain. 2014-06-18 02:44:02 -04:00			`#define TPOFF_K 8`
superh port 2013-10-05 05:13:18 -05:00
dynamic linker bootstrap overhaul this overhaul further reduces the amount of arch-specific code needed by the dynamic linker and removes a number of assumptions, including: - that symbolic function references inside libc are bound at link time via the linker option -Bsymbolic-functions. - that libc functions used by the dynamic linker do not require access to data symbols. - that static/internal function calls and data accesses can be made without performing any relocations, or that arch-specific startup code handled any such relocations needed. removing these assumptions paves the way for allowing libc.so itself to be built with stack protector (among other things), and is achieved by a three-stage bootstrap process: 1. relative relocations are processed with a flat function. 2. symbolic relocations are processed with no external calls/data. 3. main program and dependency libs are processed with a fully-functional libc/ldso. reduction in arch-specific code is achived through the following: - crt_arch.h, used for generating crt1.o, now provides the entry point for the dynamic linker too. - asm is no longer responsible for skipping the beginning of argv[] when ldso is invoked as a command. - the functionality previously provided by __reloc_self for heavily GOT-dependent RISC archs is now the arch-agnostic stage-1. - arch-specific relocation type codes are mapped directly as macros rather than via an inline translation function/switch statement. 2015-04-13 02:56:26 -04:00			`#define REL_SYMBOLIC R_SH_DIR32`
			`#define REL_OFFSET R_SH_REL32`
			`#define REL_GOT R_SH_GLOB_DAT`
			`#define REL_PLT R_SH_JMP_SLOT`
			`#define REL_RELATIVE R_SH_RELATIVE`
			`#define REL_COPY R_SH_COPY`
			`#define REL_DTPMOD R_SH_TLS_DTPMOD32`
			`#define REL_DTPOFF R_SH_TLS_DTPOFF32`
			`#define REL_TPOFF R_SH_TLS_TPOFF32`

			`#define CRTJMP(pc,sp) __asm__ __volatile__( \`
			`"jmp @%0 ; mov %1,r15" : : "r"(pc), "r"(sp) : "memory" )`