Sujet : Re: Baby X is bor nagain
De : already5chosen (at) *nospam* yahoo.com (Michael S)
Groupes : comp.lang.cDate : 28. Jun 2024, 09:11:51
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20240628111151.00002e50@yahoo.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
User-Agent : Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32)
On Fri, 28 Jun 2024 03:30:07 -0000 (UTC)
Kaz Kylheku <
643-408-1753@kylheku.com> wrote:
On 2024-06-27, bart <bc@freeuk.com> wrote:
For most, PIC isn't a necessity.
Only because they use a virtual memory operating system which allows
every executable to be mapped to the same fixed address in its own
address space.
It does not sound right.
For "simple" program that does not mess with copying pats of itself
and such, PIC just allows simpler exe format and more primitive loader.
If you already have advanced exe format and smart loader then all PIC
buys is faster load at cost of slower execution. Hopefully, just a
little slower, but that depends on architecture.
PID is more "interesting". Even on x86-64, where address displacement
field is ether 8 or 32 bits, completely free relocation of data
segments would need co-operation from code generator. More so on
architectures with significantly narrower displacement range.
If you designed your personal OS, which would be the case?
[ ] Programs must be PIC
[ ] Programs needn't be PIC