Skip to content

Commit 709ff79

Browse files
committed
Full slicing always requires consistent location numbers
We need to ensure consistency both with single properties as well as when slicing for all properties.
1 parent 5d85d38 commit 709ff79

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/goto-instrument/goto_instrument_parse_options.cpp

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1764,6 +1764,8 @@ void goto_instrument_parse_optionst::instrument_goto_program()
17641764
do_indirect_call_and_rtti_removal();
17651765
do_remove_returns();
17661766
rewrite_rw_ok(goto_model);
1767+
// full_slicer requires that the model has unique location numbers:
1768+
goto_model.goto_functions.update();
17671769

17681770
log.warning() << "**** WARNING: Experimental option --full-slice, "
17691771
<< "analysis results may be unsound. See "
@@ -1775,8 +1777,6 @@ void goto_instrument_parse_optionst::instrument_goto_program()
17751777
goto_model, cmdline.get_values("property"), ui_message_handler);
17761778
else
17771779
{
1778-
// full_slicer requires that the model has unique location numbers:
1779-
goto_model.goto_functions.update();
17801780
full_slicer(goto_model, ui_message_handler);
17811781
}
17821782
}

0 commit comments

Comments
 (0)