You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent change in CBMC made it an invariant of pointer_typet that pointers have a width field. On my development branch, I've added assert(!type.get(ID_width).empty()); to to_pointer_type so that I find all malformedpointer_typets.
This is fine, and I've found several places where pointer_typets are constructed incorrectly. The problem is that when the cross-compiled object files in the arch_flags regression tests are loaded, they contain malformed pointers, which cause the new assertions to fail.
The instructions in the test.desc files are not especially clear: it's not obvious how to set up an ARM cross-compiler.
More detailed instructions should be added to the test.desc files, and new object files should be submitted, generated with a more recent version of goto-cc.
This was needed after an update to goto-cc, which caused
previously-compiled binaries used in the test suite to trigger an
assertion failure. Also updated instructions on how to generate these
binaries.
This commit fixesdiffblue#1376.
A recent change in CBMC made it an invariant of
pointer_typet
that pointers have a width field. On my development branch, I've addedassert(!type.get(ID_width).empty());
toto_pointer_type
so that I find all malformedpointer_typet
s.This is fine, and I've found several places where
pointer_typet
s are constructed incorrectly. The problem is that when the cross-compiled object files in thearch_flags
regression tests are loaded, they contain malformed pointers, which cause the new assertions to fail.The instructions in the test.desc files are not especially clear: it's not obvious how to set up an ARM cross-compiler.
More detailed instructions should be added to the test.desc files, and new object files should be submitted, generated with a more recent version of
goto-cc
.Pinging @karkhaz and @tautschnig as they may be familiar with this process.
The text was updated successfully, but these errors were encountered: