mirror of
https://github.com/isledecomp/isle.git
synced 2024-11-29 11:06:05 -05:00
f247e10b7e
* Rather than using <OFFSET> as a replacement for all offsets in a function, label the offsets as <OFFSET1>, <OFFSET2>, etc. Doing this will avoid false-positive 100% matches resulting from the same function being called in two times where a different on should have been called or vice versa. And the same for globals. I already encountered one case of this in the wild. * When a 100% match initially fails, try to make the functions match by swapping register allocations. This makes it possible to get a 100% match where the generated machine code differs only in register allocation. * Only apply the above when it is possible to reach a 100% match in that way. Otherwise show the developer the unadultrated diff to avoid complicating decompilation. * In the result listing, show the functions which are "effective matches" in this way as "100%*" instead of "100%". |
||
|---|---|---|
| .. | ||
| cvdump.exe | ||
| isle.png | ||
| lego1.png | ||
| reccmp.py | ||
| requirements.txt | ||
| template.html | ||
| template.svg | ||
