Fabian Schiebel

See https://github.com/secure-software-engineering/phasar/wiki/Coding-Conventions#branches

Is this still an issue? We added an entry to our [coding guidelines](https://github.com/secure-software-engineering/phasar/wiki/Coding-Conventions#type-aliases) were this is specified.

Hi @StamesJames, I could not reproduce your issue on my system. The analysis finishes very quickly, but does not find any vulnerabilities. I suppose, we are analyzing slightly different IR....

Hi @StamesJames, now I can reproduce your issue, thanks. I will debug it and see, what we can do

@small-cat, you are right. We are aware of the alias analysis problem (see #329, #610). We are also working on a different type-hierarchy solution #623; however, it will still take...

Hi @StamesJames, thank you for that example. That looks nice!. Creating documentation is always time consuming, so we really appreciate your contribution!

Haven't pushed the fixes yet, sry. Will push them on monday.

As agreed we won't merge this PR until we have a proper replacement for the CFLAndersAA

Hi @zamazan4ik, thank you for this suggestion. I aggree that we should make use of PGO at some time -- recently, we enabled LTO which already helps. To automate the...

Hi @yuffon, yes that sounds like a bug. Can you provide the analysis code, such that we can debug it?