Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDCC creates .ROM files with different checksums on different PCs #94

Open
mr-GreyWolf opened this issue Oct 22, 2021 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@mr-GreyWolf
Copy link

This happens with the file source/kernel/bank5/fdisk.c

Probably the problem in file source/kernel/Makefile in line:

sdcc -o bank5/ --code-loc 0x4120 --data-loc 0x8020 -mz80 --disable-warning 196 --disable-warning 84 --disable-warning 85 \
     --max-allocs-per-node 1000 --allow-unsafe-read --opt-code-size --no-std-crt0 bank5/fdisk_crt0.rel $(patsubst %.dat,%.c,$@)
$(call hex2bin_full,$(patsubst %.dat,%.ihx,$@),$@)

@Konamiman
Copy link
Owner

Indeed, since that particular line is compiling FDISK using optimizations, the result might not always be the same (I don't know the internals of SDCC and how much these optimizations are "random") but I assume that the resulting code works in all cases, right?

Therefore I'll label it as an enhancement request and leave it open in case someone can figure out a wait to get consistent compilation results.

@Konamiman Konamiman added the enhancement New feature or request label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants