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
As stated in the title, std.elf.Header does not expose the type of the elf file. I think it would be generally useful to expose it in the struct as programs might not be able to use all the types elf provide.
For example, I'm making what I like to call "The Tempinator" (in true Dr. Doofenshmirtz fashion). It injects the use of the temporary registers on RiscV. Both GCC and LLVM does not emit machine code with the temp registers at all (GCC at least tries to but fails with optimizations turned on). The program runs on an object file and a given yaml file with all of the function definitions.
It would be generally useful to have the type of the elf file be exposed in std.elf.Header as it already has a small parsing routine and I wouldn't imagine it being too difficult to add even though some types are OS and ARCH specific.
The text was updated successfully, but these errors were encountered:
Peppy3
changed the title
Standard library not exposing the type of the elf in std.elf.Header
Standard library not exposing the type of elf in std.elf.Header
May 1, 2024
As stated in the title,
std.elf.Header
does not expose the type of the elf file. I think it would be generally useful to expose it in the struct as programs might not be able to use all the types elf provide.For example, I'm making what I like to call "The Tempinator" (in true Dr. Doofenshmirtz fashion). It injects the use of the temporary registers on RiscV. Both GCC and LLVM does not emit machine code with the temp registers at all (GCC at least tries to but fails with optimizations turned on). The program runs on an object file and a given yaml file with all of the function definitions.
It would be generally useful to have the type of the elf file be exposed in
std.elf.Header
as it already has a small parsing routine and I wouldn't imagine it being too difficult to add even though some types are OS and ARCH specific.The text was updated successfully, but these errors were encountered: