Martin Mory

A brief update: as @pdschubert wrote in a related issue (https://github.com/secure-software-engineering/phasar/issues/200#issuecomment-714312700), llvm-link merges "identical" data types, e.g. those which have identical fields. When that happens, phasar fails to identify the...

@fabianbs96 what is the state of this? don't we already have sth. like this?

Maybe we need to provide some internal dummy header? This only refers to the test cases of the type state analysis for openssl, for which we don't need any actual...

The IFDS LCA is not implemented. Try the IDE one. Analyzing your code precisely requires field-sensitivity. Without field-sensitivity the initializers get overapproximated and you only have BOTTOM. IDE LCA is...

ide-lca would be the one to go. But again, your code that you intend to analyze cannot be analyzed by ide-lca precisely. ide-lca is field-insensitive, so the index accesses with...

You can see the overapproximation based on the value Bottom that is the resulting value in that case, it means "non-constant/don't know whether it's constant".

@blipper does the issue still exist?

We need to document the policy for this. The implicit policy is: only include when needed, don't if forward declarations suffice.

This depends on how you want to implement your analysis. In very simplified terms, only _linear_ constant propagation is distributive. Which means, you can only propagate constants with expressions CC...

I agree there is a lack of documentation here. I am not aware that we already have documentation for this, unfortunately.