Update all plugins to BAP 2.0

[codyroux]

Not sure what's required for this one, hopefully no too much except the BitVector module.

It also sounds like they're moving away from having, for every module M, a sub-module M.Set and M.Map, which I use extensively in WP, so maybe some re-factoring there as well.

[ivg]

Nothing is required, the Bap.Std interface is backward compatible. It would be good to eventually update cbat_tools to use the more general Bap 2.0 interfaces (i.e., Bap_core_theory and Bap_knowledge) and make VSA available in the knowledge base. But this is not immediately required. Again, old analysis will continue to work for the observed future, it just won't be able to benefit from all the new features.

It also sounds like they're moving away from having, for every module M, a sub-module M.Set and M.Map, which I use extensively in WP, so maybe some re-factoring there as well.

Well, our new modules are not exposing those interfaces (old are still having the same interface), but Base/Core_kernel is making the obsolete, so expect them to disappear from Base/Core_kernel sooner or later. The change is easy, instead of M.Map one should use just Map :)

[ivg]

I've recalled one semantic change that might affect you. When we reify program semantics into BIR we no longer create the ret terms. Now BAP 2.x you won't have any return dst terms, instead it will be reified to a more general call dst with noreturn, where dst is some expression denoting the set of possible return destinations.

Do you think it will affect you?

[codyroux]

It might affect us, but I think we can handle it! Thanks again.

…

On Tue, Aug 20, 2019 at 10:17 AM Ivan Gotovchits ***@***.***> wrote: I've recalled one semantic change that might affect you. When we reify program semantics into BIR we no longer create the ret terms. Now BAP 2.x you won't have any return dst terms, instead it will be reified to a more general call dst with noreturn, where dst is some expression denoting the set of possible return destinations. Do you think it will affect you? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#58?email_source=notifications&email_token=AA772UCWHM652APYZRCU2U3QFP4I7A5CNFSM4ING4J4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4WOL5Q#issuecomment-523036150>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA772UGESBT4WXPER3DWCKLQFP4I7ANCNFSM4ING4J4A> .

[fortunac]

Handled in #65