Need to verify that check generation adds loads if indirect limits are fetched and that global struct limits are fetched directly from struct allocation start and end addresses.
Currently at least LocalLimit checks does not seem to work (at least for global scope struct) and would be quite possible that the same thing fails for ConstantAddresSpace limits as well.
Global and private address space limits seems to be always fine, since global scope limits are always red from PA struct and private limits are got without any loads from geps taken from program allocations argument.
Or maybe only loading limits from safe args is done correctly...
Need to verify that check generation adds loads if indirect limits are fetched and that global struct limits are fetched directly from struct allocation start and end addresses.
Currently at least LocalLimit checks does not seem to work (at least for global scope struct) and would be quite possible that the same thing fails for ConstantAddresSpace limits as well.
Global and private address space limits seems to be always fine, since global scope limits are always red from PA struct and private limits are got without any loads from geps taken from program allocations argument.
Or maybe only loading limits from safe args is done correctly...