tree 3dd5a60a3fa84b5f2adb43a7c351f9d539f07b92
parent 0e44bfa9aa692bd7521c8e9d5245d650e546ce74
author Robert Norton-Wright <robert.norton@scisemi.com> 1737031435 +0000
committer Robert Norton <1412774+rmn30@users.noreply.github.com> 1737121251 +0000

Fix revoker scan regions.

Neither software or hardware revoker were scanning enough of memory,
as revealed by the tests in the previous commit. To fix this we move
all the mutable data (which needs to be swept) into a single contigous
range bounded by __revoker_scan_start and __export_mem_heap_end.

The software revoker is currently set up to scan multiple disjoint
regions (stack, heap etc) but we now only need to use one, which is
not the same as the hardware revoker. This revealed a problem in the
loader where it was not using imprecise set bounds as intended.