On Fri, Jan 28, 2022 at 04:00:26PM +0000, Pedro Falcato wrote: > Also, quick note: I've seen linking blowing up because the ABIs being used > in the bare metal code and in libgcc were different; this was in riscv64. I > know x86 doesn't do such checks but a few others do, including RISCV (they > tag object files with the ABI). This makes libgcc unusable in such > architectures.
Same on arm, object files seem to be tagged with the floating point abi used (even in case the object files doesn't actually use floating point instructions) and the linker throws errors in case there is a mismatch. > If we want to provide intrinsics, then possibly shipping our own > compiler-rt would be the only solid option. Yes, I suspect that'll work better than trying to use the compiler-shipped intrinsics. But in any case we should have a single intrinsic library for everybody to use. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#86274): https://edk2.groups.io/g/devel/message/86274 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] -=-=-=-=-=-=-=-=-=-=-=-
