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
Software libraries may use bitfields and bitmasks to track configuration options. Options can be included, combined or excluded. In the end, there will be a bitfield with each bit representing whether an option is set or not.
Currently, MARK does not support a simple way to track bitfields and bitmasks. In particular, it must be possible:
to track expressions (i.e. &, |, ...) that combine options,
to track multiple calls to function manipulationing options (e.g. set_*(), unset_*(), ...)
to track calls that reset options (e.g. clear_*())
In the end, it should become possible to get a computed value for the bitfield before it's being used.
The text was updated successfully, but these errors were encountered:
Software libraries may use bitfields and bitmasks to track configuration options. Options can be included, combined or excluded. In the end, there will be a bitfield with each bit representing whether an option is set or not.
Currently, MARK does not support a simple way to track bitfields and bitmasks. In particular, it must be possible:
&
,|
, ...) that combine options,set_*()
,unset_*()
, ...)clear_*()
)In the end, it should become possible to get a computed value for the bitfield before it's being used.
The text was updated successfully, but these errors were encountered: