08.11.2019 16:28, J. Gareth Moreton:
[...]
No gain? Wow, is whole-program optimisation that underperforming? Given
the bloated size of FPC's binaries compared to, say, what a mainstream
C++ compiler than do, I would have thought that there could be a lot

Keep in mind that pretty much any tiny MSVC application would these days push a (few-megabytes-sized) vcredist package in front of it. Similarly, gcc would typically dynamically link against some-megabytes-sized libc and other system libraries. On the other hand, FPC typically produces self-contained binaries with all required RTL code built-in. Whether it is good or not depends on your usage context, but application binary size comparison should at least take this into account to be of some use.

--
Regards,
Nikolai

that could be stripped out in regards to unused functions and the like.
Or am I missing something?  The large binary sizes feel like an elephant
in the room that no-one talks about.  What causes them?

Gareth aka. Kit

_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply via email to