On 03/31/20 16:36, Kinney, Michael D wrote: > ARM and AARCH64 have a compiler intrinsic lib that is linked against all > modules. > > [LibraryClasses.ARM, LibraryClasses.AARCH64] > # > # It is not possible to prevent ARM compiler calls to generic intrinsic > functions. > # This library provides the instrinsic functions generated by a given > compiler. > # [LibraryClasses.ARM] and NULL mean link this library into all ARM images. > # > NULL|ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib.inf > > Can we use this same technique for IA32/X64
It's not a problem for in-tree platforms (I do hope the edk2 patch series will include the patch for OvmfPkg), but it will require all out-of-tree platforms to be updated. > VS builds? Yes; I think the library instance should consist of one totally empty C file, and an |MSFT specific C file providing the external definition of _fltused. When building for GCC, the lib instance should compile to an empty object (archive) file. In my opinion, of course. Thanks Laszlo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#56785): https://edk2.groups.io/g/devel/message/56785 Mute This Topic: https://groups.io/mt/72648022/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
