You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently ET_DYN is used both for
static and shared linking. But for
static linking we could probably use
ET_EXEC instead. It may even be
non-pie, relocated to 0x400000,
where we have a reserve for win32
executables.
Since we use static linking for poor
man's OSes anyway (currently freebsd),
why not to limit things even more.
Statically linked non-pie ET_EXEC
can even be supported under DOS!
(well, not a 64bit one, of course)
The text was updated successfully, but these errors were encountered:
relocated to 0x400000,
where we have a reserve for win32
executables.
Crap, its a 64bit elf, so it goes
above any DOS or win32 space.
Anyway, too much to desire.
And in an absence of #17 such
elfs won't be available "in a wild"
anyway, only inside the dj64's .exe
container file.
Currently ET_DYN is used both for
static and shared linking. But for
static linking we could probably use
ET_EXEC instead. It may even be
non-pie, relocated to 0x400000,
where we have a reserve for win32
executables.
Since we use static linking for poor
man's OSes anyway (currently freebsd),
why not to limit things even more.
Statically linked non-pie ET_EXEC
can even be supported under DOS!
(well, not a 64bit one, of course)
The text was updated successfully, but these errors were encountered: