Hairy Pixels via fpc-pascal <fpc-pascal@lists.freepascal.org> schrieb am Fr., 24. Jan. 2025, 02:17:
> Is the compiler actually able to inline functions which are used from a > unit? When a unit is used it’s compiled to a .o file and linked so the > compiler doesn’t have access to the source code anymore and thus can’t > inline I would think. > > I write this because I’ve recently learned of link-time optimizations > (LTO) from LLVM where modules are compiled to bitcode which can be linked > together and inlined. It’s probably much slower than using precompiled .o > files but good for release builds. Without that I don’t see how the > compiler can inline any code called from units, which includes the whole > RTL! > When a function has inlining enabled (either explicit with the inline directive or implicit through AutoInline optimization) then in addition to generating its code to the object file (for direct calls) the node tree is stored in the PPU. And this node tree is then used for inlining the function. So the compiler correctly handles inlining of precompiled code. We're not stupid after all... Regards, Sven >
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
