✧✦✶✷Catherine✷✶✦✧
yeah i love fat shared libraries (libraries with both PE and ELF headers that refer to the exact same executable code. for compatibility.)
(the PE header starts at 0x80, and conveniently, the ELF file header ends at 0x40. basically everything else lives at offsets specified in the file headers, so you can have both)
all you need to add is compiler-generated thunks adjusting the calling convention
✧✦✶✷Catherine✷✶✦✧
i'm not sure if structs have a different layout. i think aligntment rules may be slight different? in any case, i can envision a kind of preprocessor smoothing over the differences
the really funny bit would be to add portable exception handling supporg
pinskia
@whitequark For x86_64, most structs between windows and elf ABIs are similar alignment if not the same. Also if done correctly the ABI for library would not expose any structs which will allow things even more.
As far as EH is concern, I suspect the library where this would be used the best for are ones which don't do any external calls just do stuff like encryption or some other kind of encoding/decoding like audio or picture or movies.
✧✦✶✷Catherine✷✶✦✧
@pinskia um, i'm pretty sure structs being a part of the ABI is a rather normal thing
pinskia
@whitequark I meant if done correct the API would not expose any structs. A small typo where I had meant API rather than ABI. :)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.