5 ms·

This is the wrong end of the issue. ELF for executables and dynamic libs is obsolete on modern hardware (same for microsoft PE+). I am now using for most of my

by sylware 18d ago

This is the wrong end of the issue. ELF for executables and dynamic libs is obsolete on modern hardware (same for microsoft PE+). I am now using for most of my projects a exe/dynamic lib format of my own. This file format is so miminal a simple RFC will suffice. BUT, I will need to build dynamic libs which are system interfaces (for instance userland drivers like mesa) with this file format: problem, c++ and its runtime (and probably other similar languages with their runtimes)... as usual... Well, I am still removing stuff from my file format, because I think this is not yet "minimal and enough" on modern hardware architecture (I think I have still too much complexity in the tracker of loaded dynamic libs).

Retr0id 18d ago
> ELF for executables and dynamic libs is obsolete on modern hardware (same for microsoft PE+) This is... extremely not true?
- sylware 9d ago
  Then you are of extremely bad faith? come on...
BruceEel 17d ago
> I am now using for most of my projects a exe/dynamic lib format of my own. This file format is so miminal a simple RFC will suffice. That's great! Have you published it? If not, please consider doing so.
- sylware 15d ago
  Well, everything is open source, I have a partial and very limited (but currently enough for my needs) linker for x86_64 and RISC-V 64bits (but written in plain and simple C which compiles with tinycc and cproc/qbe!). I even have an ELF capsule for executables (for x86_64, written in assembly). So it is out there, but not "tidy" (aka a wip messy tarball), as I said, I am not sorta sure about how to handle the in-process loader, which is beyond simple, but I still believe I can make it even simpler (yeah, not more gigantic external "interpreter"/"loader). Once I am satisfied, I'll ship that to a nicely tidied GIT repo (but with support of noscript/basic HTML browsers, unlike ... you know which ones...).

by sylware 18d ago

Retr0id 18d ago

> ELF for executables and dynamic libs is obsolete on modern hardware (same for microsoft PE+) This is... extremely not true?

sylware 9d ago
Then you are of extremely bad faith? come on...

BruceEel 17d ago

> I am now using for most of my projects a exe/dynamic lib format of my own. This file format is so miminal a simple RFC will suffice. That's great! Have you published it? If not, please consider doing so.

sylware 15d ago
Well, everything is open source, I have a partial and very limited (but currently enough for my needs) linker for x86_64 and RISC-V 64bits (but written in plain and simple C which compiles with tinycc and cproc/qbe!). I even have an ELF capsule for executables (for x86_64, written in assembly). So it is out there, but not "tidy" (aka a wip messy tarball), as I said, I am not sorta sure about how to handle the in-process loader, which is beyond simple, but I still believe I can make it even simpler (yeah, not more gigantic external "interpreter"/"loader). Once I am satisfied, I'll ship that to a nicely tidied GIT repo (but with support of noscript/basic HTML browsers, unlike ... you know which ones...).