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
Some sv-benchmarks are preprocessed using glibc. Symbiotic doesn't seem to understand glibc's expansion of assert macro.
It looks like this: __assert("", "sources/sys/sv_comp.h", 5, "0")); where __assert is an ordinary function (not a macro). This works like __assert_fail, so we could technically just replace it.
The text was updated successfully, but these errors were encountered:
In general, we would like to handle these other assertions (probably as you proposed: just replace these with __assert_fail) but in the context of SV-COMP, these are wrong benchmarks and they should be fixed.
EDIT: Of course, if these assertions in the benchmark are those whose validity is being verified (they can be used just for aborting undesirable paths).
Some sv-benchmarks are preprocessed using glibc. Symbiotic doesn't seem to understand glibc's expansion of
assert
macro.It looks like this:
__assert("", "sources/sys/sv_comp.h", 5, "0"));
where__assert
is an ordinary function (not a macro). This works like__assert_fail
, so we could technically just replace it.The text was updated successfully, but these errors were encountered: