Original sentence: It should be noted that there are often subtle differences in how various compilers implement these conventions, so it is often difficult to interface code which is compiled by different compilers.Note that many compilers can optimize these standard sequences away when not needed, for instance when a function does not use local temporaries (often called "no stackframe generation").Note that when compiling for the x64 architecture using Microsoft tools, there is only one calling convention — the one described here, so that stdcall, thiscall, cdecl, fastcall, etc.Note that while functions tend to have only one entry point, they may have multiple exit points, and thus may well have more than one standard exit sequence, or a jump to the standard exit sequence in the function body
Edited sentence: Many compilers can optimize these standard sequences away when not needed, for instance when a function does not use local temporaries (often called "no stackframe generation").There are often subtle differences in how various compilers implement these conventions, so it is often difficult to interface code which is compiled by different compilers.When compiling for the x64 architecture using Microsoft tools, there is only one calling convention — the one described here, so that stdcall, thiscall, cdecl, fastcall, etc.While functions tend to have only one entry point, they may have multiple exit points, and thus may well have more than one standard exit sequence, or a jump to the standard exit sequence in the function body