musl/arch/or1k/reloc.h

#define LDSO_ARCH "or1k"

#define TPOFF_K 0

#define REL_SYMBOLIC    R_OR1K_32
#define REL_GOT         R_OR1K_GLOB_DAT
#define REL_PLT         R_OR1K_JMP_SLOT
#define REL_RELATIVE    R_OR1K_RELATIVE
#define REL_COPY        R_OR1K_COPY
#define REL_DTPMOD      R_OR1K_TLS_DTPMOD
#define REL_DTPOFF      R_OR1K_TLS_DTPOFF
#define REL_TPOFF       R_OR1K_TLS_TPOFF

#define CRTJMP(pc,sp) __asm__ __volatile__( \
	"l.jr %0 ; l.ori r1,%1,0" : : "r"(pc), "r"(sp) : "memory" )
add or1k (OpenRISC 1000) architecture port With the exception of a fenv implementation, the port is fully featured. The port has been tested in or1ksim, the golden reference functional simulator for OpenRISC 1000. It passes all libc-test tests (except the math tests that requires a fenv implementation). The port assumes an or1k implementation that has support for atomic instructions (l.lwa/l.swa). Although it passes all the libc-test tests, the port is still in an experimental state, and has yet experienced very little 'real-world' use. 2014-07-17 22:09:10 +03:00			`#define LDSO_ARCH "or1k"`

			`#define TPOFF_K 0`

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_OR1K_32`
			`#define REL_GOT R_OR1K_GLOB_DAT`
			`#define REL_PLT R_OR1K_JMP_SLOT`
			`#define REL_RELATIVE R_OR1K_RELATIVE`
			`#define REL_COPY R_OR1K_COPY`
			`#define REL_DTPMOD R_OR1K_TLS_DTPMOD`
			`#define REL_DTPOFF R_OR1K_TLS_DTPOFF`
			`#define REL_TPOFF R_OR1K_TLS_TPOFF`

			`#define CRTJMP(pc,sp) __asm__ __volatile__( \`
			`"l.jr %0 ; l.ori r1,%1,0" : : "r"(pc), "r"(sp) : "memory" )`