Skip to content

Fix typos in documentation #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PaulkaToast wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix typos in documentation #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9925b31
Fix typos in relocations doc
PaulkaToast Jan 30, 2020
fc55202
Fix typos in static pie doc
PaulkaToast Jan 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/relocations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,16 @@ ELF file of a statically linked non-PIE will have relocations to support
[_ifuncs_](https://github.com/sivachandra/elf-by-example/tree/master/examples/ifunc).
ELF file of a statically linked PIE will additional have one specific kind
of dynamic relocations. These relocations are required to adjust for the
load address (a [PIE](pie.md) is loaded at a different address everyone time it
load address (a [PIE](pie.md) is loaded at a different address every time it
runs). See this [example](https://github.com/sivachandra/elf-by-example/tree/master/examples/global_var_ptr)
for more elaborate illustration.
for a more elaborate illustration.

## What are linker generated relocations?

A coworker once asked, "Aren't relocations generated by the compiler/assembler?
What are linker generated relocations?" It is true that the compiler and/or
the assembler generate the relocations. The static linker makes use of these
relocations to performing the linking. Some values, like global variable
relocations to perform the linking. Some values, like global variable
addresses in a PIE, can only be known after the program starts. For such values,
the linker typically replaces the compiler generated relocations with its own
relocations which are most suitable for the linking mode used (for example,
Expand Down
2 changes: 1 addition & 1 deletion docs/static_pie.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ static-pie binary are explained in
A statically linked PIE binary differs from a dynamically linked PIE binary in
the following ways:

1. As there are no dynamic libraries to be loaded, they is no need of the
1. As there are no dynamic libraries to be loaded, there is no need for the
program interpreter. Consequently, there is no `PT_INTERP` segment in a
static-pie binary.
1. The dynamic section will not have `DT_NEEDED` entries as a static-pie binary
Expand Down