Christian Banse

> Currently, the cpg handles macro resolution in the following way:  > > Code and file location are pointing to the un-resolved macro, but the node type and its...

ffserver.c: 87021 ms. `ControlFlowSensitiveDFGPass` takes 84965 ms mpegvideo.c: Parses in 614 ms overall on my M1, although I get a LOT of problem declaration nodes there so not sure now...

> Thanks for checking, could you give me your translation configuration? Seems like this is then a problem on my side I was doing it as part of a unit...

> Wow interesting. h264.c takes 22s for me on my MacBook Pro 2019 when using _your_ configuration. It takes 3min and 10s when Im using my Configuration: > > ```...

Maybe this helps. I have implemented a way to read consolidated benchmark information. I will push the branch in a minute (Update: its here https://github.com/Fraunhofer-AISEC/cpg/pull/680) # Benchmark run 177c0350-88a8-48a0-bd40-18d5dbc52cac |...

Ah, you either need to have Go installed (in case you want to analyse programs in Go), otherwise you can exclude the Go frontend from being compiled if you run...

> I just noticed, that tree-sitter is also not resolving everything correctly: [tree-sitter/tree-sitter-c#99](https://github.com/tree-sitter/tree-sitter-c/issues/99) > > Did you also come along similar problems? I'm still not sure, if this is a...

I am beginning to think that hooking into LLVM / libclang is becoming a more and more viable option. It seems that there is a class called https://clang.llvm.org/doxygen/classclang_1_1ExternalSemaSource.html which can...

There are more problems with member call expressions. It is not really clear what `base` is in this context, it is not even a field of member call expression, but...

> The `base` apparently was a relic from the prototype or from the type solver, I looked at the code and it seems like the case can be extracted to...