Hi, > That means I believe GCCINTRINx86-32.lib, CLANGINTRINx86-32.lib and > XCODEINTRINx86-32.lib could be simply created > using these files her: > https://opensource.apple.com/source/clang/clang-600.0.57/src/projects/compiler-rt/lib/i386/ > or > https://github.com/llvm/llvm-project/tree/main/compiler-rt/lib/builtins/i386 > Than we have the space saving assembler implementation for all GCC derivates.
Yes, using the source and compiling our own probably works better because we don't run into abi problems that way. > BTW: Microsoft source is leaked here: > https://github.com/microsoft/Ironclad/blob/main/ironclad-apps/src/Checked/BootLoader/SingLdrPc/x86/blcrtasm.asm I doubt using leaked sources is a good idea from a legal/licensing point of view ... > There is also a library INT64.LIB in the current Windows 10 SDK, and also in > the old WinDDK 7600. > C:\WinDDK\7600.16385.1\lib\wxp\i386\int64.lib ... but if there is a library with only the 64bit math intrinsics and nothing else it is maybe easy enough to use the library as-is when building with the microsoft compiler. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#86275): https://edk2.groups.io/g/devel/message/86275 Mute This Topic: https://groups.io/mt/87479913/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
