Am 04.11.25 um 10:33 schrieb Eric Rullens:
Yes, I have seen this as well. After compiling I always calculate a
CRC over the entire binary, and this is not identical over compile
cycles.
It has been some time since I investigated this, but Windows 10 (and
11) contain some memory protection features that are not present in
Windows 7:
https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/
windows-10/security/threat-protection/overview-of-threat-mitigations-
in-windows-10#table-2
These should not influence "correct" programs, but I suspect SDCC
somewhere uses uninitialized memory and/or pointers.
At the time I did not dig further in the problem, but if it helps I
can check my notes again and recreate a test case.
Eric
If you can reproduce this in SDCC 4.5.0 or later: SDCC works mostly
function by function, so most SDCC issues can be reproduced within a
single function (basically take the affected progra, find the affected
function, and the check if compiling just that function (preceded by
any necessary declarations, macros and inline function definitions)
reproduces the
issue - most times it does).
If you can find a not too big code sample to reproduce it, please open a
bug ticket.
Philipp
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
