sxkan

> re 1: I'm not too familiar with how the SVFIR is constructed, but I believe calls to functions that have an extapi counterpart should be handled specially. When encountering...

In pull request #1188, "attribute((annotate("STATIC")))" has been removed, and instead, returns malloc() within the function body. When functions with the "STATIC" annotation in previous extapi.c are called multiple times, only...

Hi, @251, thank you for your suggestions, I have some questions before I submit new pr, > 1. there is still no setter for the path In the next pr,...

Hi, @251 Because you're not using SVF's default installation method (`source ./build.sh`), but instead opting for your own installation method, > I install SVF roughly similar to: ... SVF encounters...

PR #1212 provides two ways to specify extapi.bc path: 1. Set it via the command line using -extapi=/path_to_extapi; 2. Use the API setExtBcPath(). Please note that setExtBcPath() should be used...

@251 `void (*fn_ptrs[])() = {foo, boo, hoo}; ` is supposed to use LLVM's memcpy: `call void @llvm.memcpy.p0i8.p0i8.i64(...)` Can you provide your clang command?

@251 Do you mean manually change the call to `llvm.memcpy.p0i8.p0i8.i64` to your custom `memcpy`? If you want to replace `llvm.memcpy` with `memcpy`, you can replace the `__attribute__((annotate("MEMCPY")))` of `llvm_memcpy_p0i8_p0i8_i64` in...

@251 Could you upload the bc file?

I use clang to complie the example, and IR uses LLVM intrinsic. I'm not clear how it links to your `memcpy`? ``` 10: ; preds = %2 %11 = bitcast...

Yes. Are you going to use `memcpy` to replace the LLVM intrinsic, and implement the same functionality as the LLVM intrinsic?