Messages in this thread | | | Date | Tue, 10 Nov 2009 11:04:50 +0100 | From | Enrico Weigelt <> | Subject | Re: FatELF patches... |
| |
* David Hagood <david.hagood@gmail.com> wrote:
Hi,
> I hope it's not too late for a request for consideration: if we start > having fat binaries, could one of the "binaries" be one of the "not > quite compiled code" formats like Architecture Neutral Distribution > Format (ANDF), such that, given a fat binary which does NOT support a > given CPU, you could at least in theory process the ANDF section to > create the needed target binary? Bonus points for being able to then > append the newly created section to the file.
If you really wanna have arch independent binaries, you need some sort of virtual processor. Java, LLVM, etc. The idea is far from being new, IMHO originally came from old Burroughs Mainframes, which ran some Algol-tailored bytecode, driven by an interpreter in microcode. (I'm currently desiging a new VP with similar concepts, just in case anybody's interested).
BTW: this does not need additional kernel support - binfmt_misc is your friend ;-P
> As an embedded systems guy who is looking to have to support multiple > CPU types, this is really very interesting to me.
Just for the protocol: you want to have FatELF on embedded system ?
cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------
| |