A compiler generates object code files (machine language) from source code. A linker combines these object code files into an executable. Many IDEs invoke them in succession, so you never actually see the linker at work. Some languages/compilers do not have a distinct linker and linking is done by the compiler as part of its work.
I need to write a linker, and am stuck. The object format is a custom one, designed around the byte code interpreter, so I cant really use any existing linkers. My biggest hurdle is how to organize the object code to output the linked binary. Dynamic linking is not necessary, at this time. I need to get static linking working first.
To combine all .text section of each translation unit the linker script provides some specific commands for the same. This is the same for the .data section as well. After combining all the object files the final executable is ready to use. Now coming to the some paradox... The entry point in case of the Cortex-M series is just the ResetISR.
To understand linkers, it helps to first understand what happens "under the hood" when you convert a source file (such as a C or C++ file) into an executable file (an executable file is a file that can be executed on your machine or someone else's machine running the same machine architecture). Under the hood, when a program is compiled, the compiler converts the source file into object byte ...
I wanted to know in depth meaning and working of compiler, linker and loader. With reference to any language preferably c++.