I just tried changing to this fasm164 release, and although the executable size itself is identical between the two versions, a binary comparison shows that 17,877 bytes in the resulting executable are different.
Two seperate compiles using the identical version of FASM show a difference of 4 bytes with one another (I assume a timestamp gets put in there somewhere?)
- Are there other differences in the generated code that one should be aware of?
- Will the next update of BlitzMax use the latest version of FASM? (and if not, why not?)
Two seperate compiles using the identical version of FASM show a difference of 4 bytes with one another (I assume a timestamp gets put in there somewhere?)
- Are there other differences in the generated code that one should be aware of?
- Will the next update of BlitzMax use the latest version of FASM? (and if not, why not?)