Closed
Description
I noticed that the location numbers in the goto binaries produced by goto-cc are only unique per function (but not globally unique). Also when reading a goto binary (via, e.g., get_goto_program() in goto-instrument), the resulting goto functions do not contain globally unique location numbers even when the binary one read from had unique location numbers.
Is this all expected behavior? As it currently works we'd need to call goto_functions.update() immediately after reading a goto binary to make sure it has unique location numbers.
Metadata
Metadata
Assignees
Labels
No labels