bbrehm
bbrehm
The CfgCreator has a complexity class problem. The general algorithm is very map-reduce style, on top of immutable persistent (copy-on-write) datastructures. Nice, everything is side-effect free! However The `cfgA ++...
Minor improvements in output readability and parsability. Unlikely to meet standards for code-beauty; will possibly be cleared up later. This pull-request is mainly to make you aware of the fork.
This brings in an isormorphism invariant hashcode for cfgNodes, especially METHOD. quote docstring: >"An isomorphism-invariant hash-code that describes a CfgNode and its position inside the method body. The ISOHASH of...
The corresponding classes extend from Noderef. This means that they create a second Noderef referencing the same underlying Node. However, overflowdb cannot deal with that: The entire logic (e.g. https://github.com/ShiftLeftSecurity/overflowdb/blob/5bf234034dc7b58edf0983753adb253ce340578a/core/src/main/java/overflowdb/NodeRef.java#L91)...
Some cpgs were found that have nonunique label/fullname combinations (specifically: multiple NamespaceBlock nodes with same fullName). This sucks for the AstLinker, so let's warn. cc @ltcmelo, related https://github.com/ShiftLeftSecurity/codescience/pull/6466 https://github.com/ShiftLeftSecurity/py2cpg/issues/574
## Reproduction steps Consider the following jmh benchmark (on scala 2.13.8 and hotspot openjdk-19, but I believe this applies to all versions except that graal is possibly better than C2...
This adds some fixme notes on fundamental architecture/API/performance issues I spotted. I also started to write down some of the general pitfalls. How do we want these general pitfalls documented...
This is obviously not mergeable. But it allows us to explore how IO for flat storage could look like, and what it's performance characteristics are. Apart from uglyness (e.g. use...