"
The indirect call resolution still seems quite unreliable. It fails for the following cases.
examples:
functionpointer/functionpointer - throws exception due to a region having bitvector as its contents
functionpointer/functionpointer_clang - throws exception due to a region having bitvector as its contents
jumptable/jumptable_clang - throws exception due to a region having bitvector as its contents
jumptable2/jumptable2_clang - fails to resolve statements 000004fc (a call to sub_seven) and 000004e6 (a call to add_six)
tests:
functionpointer/gcc and functionpointer/clang are the same as the examples and throw an exception
indirect_call/clang - throws exception due to a region having bitvector as its contents
indirect_call/gcc - throws exception due to a region having bitvector as its contents
jumptable/clang - throws exception due to a region having bitvector as its contents
jumptable2/jumptable2_clang - throws exception due to a region having bitvector as its contents
"
Liam wrote:
" The indirect call resolution still seems quite unreliable. It fails for the following cases.
examples:
functionpointer/functionpointer - throws exception due to a region having bitvector as its contents functionpointer/functionpointer_clang - throws exception due to a region having bitvector as its contents jumptable/jumptable_clang - throws exception due to a region having bitvector as its contents jumptable2/jumptable2_clang - fails to resolve statements 000004fc (a call to sub_seven) and 000004e6 (a call to add_six) tests:
functionpointer/gcc and functionpointer/clang are the same as the examples and throw an exception indirect_call/clang - throws exception due to a region having bitvector as its contents indirect_call/gcc - throws exception due to a region having bitvector as its contents jumptable/clang - throws exception due to a region having bitvector as its contents jumptable2/jumptable2_clang - throws exception due to a region having bitvector as its contents "