NaplesPU LLD Linker - Revision history

Francesco at 15:21, 21 June 2019

2019-06-21T15:21:17Z

Francesco: Francesco moved page Nu+ LLD Linker to NaplesPU LLD Linker

2019-06-21T15:20:46Z

Francesco moved page Nu+ LLD Linker to NaplesPU LLD Linker

Francesco at 09:31, 31 March 2019

2019-03-31T09:31:11Z

Francesco: /* Linkerscript */

2019-03-31T09:30:29Z

‎Linkerscript

Francesco at 09:22, 31 March 2019

2019-03-31T09:22:48Z

Francesco at 09:21, 31 March 2019

2019-03-31T09:21:36Z

Francesco at 09:13, 31 March 2019

2019-03-31T09:13:16Z

Francesco: Francesco moved page The nu+ LLD Linker to Nu+ LLD Linker

2019-03-31T08:46:08Z

Francesco moved page The nu+ LLD Linker to Nu+ LLD Linker

Francesco: Francesco moved page Tools to The nu+ LLD Linker

2019-03-31T08:45:39Z

Francesco moved page Tools to The nu+ LLD Linker

Edo at 16:42, 28 May 2018

2018-05-28T16:42:56Z

@@ Line 2: / Line 2: @@
 LLD is built as a set of libraries to join the main idea of the software modular design.
-The nu+ implementation of LLD is made on an ELF-based approach, by adding a new Target class inside lld/ELF/Arch folder. [[NuPlus.cpp]] contains the ''relocation'' logic and other information needed to support nu+. Each nu+ application must be linked together with two additional object files:
+The NaplesPU implementation of LLD is made on an ELF-based approach, by adding a new Target class inside lld/ELF/Arch folder. [[NaplesPU.cpp]] contains the ''relocation'' logic and other information needed to support NaplesPU. Each NaplesPU application must be linked together with two additional object files:
 * ''crt0.o'', is the object file resulting of the compilation of the start routine for the custom platform, composed of operations needed to set-up the platform.
@@ Line 8: / Line 8: @@
 == Relocations ==
-This section explains how the relocations are implemented in nu+.
+This section explains how the relocations are implemented in NaplesPU.
 All relocations are specified in the ''relocateOne'' method implementation. By looking at the target ISA, LLD must check for each instruction type in which an immediate value is specified to verify if it can fit the machine instruction field.
 <syntaxhighlight>
-void NuPlus::relocateOne(uint8_t *Loc, uint32_t Type, uint64_t Val) const {
+void NaplesPU::relocateOne(uint8_t *Loc, uint32_t Type, uint64_t Val) const {
    int64_t Offset;
    switch (Type) {
@@ Line 23: / Line 23: @@
       //Check Offset for J-Type Instructions
       checkInt(Loc, Val, 18, Type);
-      applyNuPlusReloc<18, 0>(Loc, Type, Val);
+      applyNaplesPUReloc<18, 0>(Loc, Type, Val);
       break;
     case R_NUPLUS_PCREL_MEM:
       //Check Offset for M-Type Instructions
       checkInt(Loc, Val, 9, Type);
-      applyNuPlusReloc<9, 3>(Loc, Type, Val);
+      applyNaplesPUReloc<9, 3>(Loc, Type, Val);
       break;
     case R_NUPLUS_PCREL_LEA:
       //Check Offset for I-Type Instructions
       checkInt(Loc, Val, 9, Type);
-      applyNuPlusReloc<9, 3>(Loc, Type, Val);
+      applyNaplesPUReloc<9, 3>(Loc, Type, Val);
       break;
     case R_NUPLUS_ABS_HIGH_LEA:
       //Check Offset for MOVEI-Type Instructions
       checkInt(Loc, (Val >> 16) & 0xFFFF , 16, Type);
-      applyNuPlusReloc<16, 2>(Loc, Type, (Val >> 16) & 0xFFFF);
+      applyNaplesPUReloc<16, 2>(Loc, Type, (Val >> 16) & 0xFFFF);
       break;
     case R_NUPLUS_ABS_LOW_LEA:
       //Check Offset for MOVEI-Type Instructions
       checkInt(Loc, (Val) & 0xFFFF , 16, Type);
-      applyNuPlusReloc<16, 2>(Loc, Type, (Val) & 0xFFFF);
+      applyNaplesPUReloc<16, 2>(Loc, Type, (Val) & 0xFFFF);
       break;
+   }
@@ Line 49: / Line 49: @@
 </syntaxhighlight>
-All of these implemented relocations relies on the method ''applyNuPlusRelocation'' that simply writes back the value into the instruction.
+All of these implemented relocations relies on the method ''applyNaplesPURelocation'' that simply writes back the value into the instruction.
 == Linkerscript ==
-All memory images generated for nu+ must be linked in a proper way. This way is specified by the linkerscript:
+All memory images generated for NaplesPU must be linked in a proper way. This way is specified by the linkerscript:
 <syntaxhighlight>

@@ Line 50: / Line 50: @@
 All of these implemented relocations relies on the method ''applyNuPlusRelocation'' that simply writes back the value into the instruction.
 == Linkerscript ==
@@ Line 106: / Line 87: @@
 As shown above, the linker script commonly defines where the sections must be placed into the memory. Also, it solves undefined symbols of the start routine, specifying the stack size per-thread, the number of threads and the starting address for the stack frame.

@@ Line 72: / Line 72: @@
 == Linkerscript ==
-All memory images generated for nu+ must be linked in a proper way.
+All memory images generated for nu+ must be linked in a proper way. This way is specified by the linkerscript:
 == llvm-readobj ==

@@ Line 69: / Line 69: @@
    ...
 </syntaxhighlight>
 == llvm-readobj ==

← Older revision		Revision as of 09:21, 31 March 2019
Line 7:		Line 7:
	* ''vectors.o'', is the Interrupt Vector Table.		* ''vectors.o'', is the Interrupt Vector Table.

		+	== Relocations ==
		+	This section explains how the relocations are implemented in nu+.
		+	All relocations are specified in the ''relocateOne'' method implementation. By looking at the target ISA, LLD must check for each instruction type in which an immediate value is specified to verify if it can fit the machine instruction field.
		+
		+	<syntaxhighlight>
		+	void NuPlus::relocateOne(uint8_t *Loc, uint32_t Type, uint64_t Val) const {
		+	int64_t Offset;
		+	switch (Type) {
		+	default:
		+	fatal("unrecognized reloc " + Twine(Type));
		+	case R_NUPLUS_ABS32:
		+	write32le(Loc, Val);
		+	break;
		+	case R_NUPLUS_BRANCH:
		+	//Check Offset for J-Type Instructions
		+	checkInt(Loc, Val, 18, Type);
		+	applyNuPlusReloc<18, 0>(Loc, Type, Val);
		+	break;
		+	case R_NUPLUS_PCREL_MEM:
		+	//Check Offset for M-Type Instructions
		+	checkInt(Loc, Val, 9, Type);
		+	applyNuPlusReloc<9, 3>(Loc, Type, Val);
		+	break;
		+	case R_NUPLUS_PCREL_LEA:
		+	//Check Offset for I-Type Instructions
		+	checkInt(Loc, Val, 9, Type);
		+	applyNuPlusReloc<9, 3>(Loc, Type, Val);
		+	break;
		+	case R_NUPLUS_ABS_HIGH_LEA:
		+	//Check Offset for MOVEI-Type Instructions
		+	checkInt(Loc, (Val >> 16) & 0xFFFF , 16, Type);
		+	applyNuPlusReloc<16, 2>(Loc, Type, (Val >> 16) & 0xFFFF);
		+	break;
		+	case R_NUPLUS_ABS_LOW_LEA:
		+	//Check Offset for MOVEI-Type Instructions
		+	checkInt(Loc, (Val) & 0xFFFF , 16, Type);
		+	applyNuPlusReloc<16, 2>(Loc, Type, (Val) & 0xFFFF);
		+	break;
		+	}
		+	}
		+	</syntaxhighlight>
		+
		+	All of these implemented relocations relies on the method ''applyNuPlusRelocation'' that simply writes back the value into the instruction.

	== llvm-objdump ==		== llvm-objdump ==

← Older revision	Revision as of 15:20, 21 June 2019
(No difference)

@@ Line 1: / Line 1: @@
-When adding a new target architecture to llvm, some changes are required to the tools located in the llvm/tools folder.
+LLD is the LLVM proprietary linker. It is based on the GNU linker, and it is compatible to it in terms of arguments accepted. It also fully supports the ''ELF'' generation but also, in a progressive lower percentage, ''PE/COFF'', ''Mach-O'', ''WebAssembly'' and custom linker-scripts.
 == llvm-objdump ==
 This is the llvm object file dumper. The full documentation for llvm-objdump is maintained as a Texinfo manual. If the info and llvm-objdump programs are properly installed, the command

← Older revision	Revision as of 08:46, 31 March 2019
(No difference)

← Older revision	Revision as of 08:45, 31 March 2019
(No difference)

← Older revision		Revision as of 16:42, 28 May 2018
Line 80:		Line 80:
	# ''*_mem.hex'': little-endian HEX file with 512-bit alignment. This file is used when simulating the architecture		# ''*_mem.hex'': little-endian HEX file with 512-bit alignment. This file is used when simulating the architecture
	# ''*_mem_mango_mem.hex'': big-endian HEX file with 512-bit alignment. This file is used when using nu+ inside the MANGO project		# ''*_mem_mango_mem.hex'': big-endian HEX file with 512-bit alignment. This file is used when using nu+ inside the MANGO project
−
−	~~== lldb ==~~
−	~~TBD~~