[fpc-devel] Merging identical procedure proposals
J. Gareth Moreton
gareth at moreton-family.com
Wed Oct 13 19:33:54 CEST 2021
So one optimisation that has cropped up a couple of times is finding
ways to merge subroutines that, while containing different source code,
compile into the exact same assembly language. For example,
TStream.WriteData has implementations for numerous input types, and the
compilation of "function TStream.WriteData(const Buffer: WideChar):
NativeInt;", "function TStream.WriteData(const Buffer: Int16):
NativeInt;", "function TStream.WriteData(const Buffer: UInt16):
NativeInt;" all produce the following:
As you can imagine, having the compiler only keep one copy of the code
and redirect all relevant calls to it will reduce code size
significantly for no speed penalty.
One thought I had was to keep a "code hash" for each subroutine that's
computed via digesting the assembly language, although I'm not quite
sure how it should handle labels. If two hashes are identical, the
procedures are checked more closely to determine if they are actually
identical and it wasn't just a collision.
I figure this would be a whole-program optimization though due to
inter-unit calls and comparisons and the like.
Gareth aka. Kit
This email has been checked for viruses by Avast antivirus software.
More information about the fpc-devel