Displaying 3 results from an estimated 3 matches for "e9ad2370".
2011 Aug 10
2
[LLVMdev] incorrect DSCallGraph for simple indirect call with vtable nearby
...: red() or blue(), but not Base::virt() const or Derived::virt() const.
-- Ben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.cpp
Type: text/x-c++src
Size: 387 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110810/e9ad2370/attachment.cpp>
2011 Aug 10
0
[LLVMdev] incorrect DSCallGraph for simple indirect call with vtable nearby
Dear Ben,
Just a few comments on DSA:
1) I'll try out your example C++ code below and see if I can get the
same results that you do. However, I'm at a conference right now
(Usenix Security), so I don't know exactly when I'll get to it.
2) DSA can get pessimistic results when dealing with external code (as
Andrew described). It is designed for whole program analysis, meaning
2011 Aug 10
4
[LLVMdev] incorrect DSCallGraph for simple indirect call with vtable nearby
In an earlier message
(http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-August/042298.html),
Andrew Lenharth suggested that EQTDDataStructures (from the poolalloc
project) may only try to resolve indirect function calls. However, I am
now finding that the generated DSCallGraph over-approximates the callees
in a very simple indirect call. Some over-approximation is unavoidable,
but this case