Displaying 3 results from an estimated 3 matches for "klee_div_zero_check".
[LLVMdev] Help with LLVM Bitcode function inlining and duplicating debug information on instructions
2013 Aug 30
1
[LLVMdev] Help with LLVM Bitcode function inlining and duplicating debug information on instructions
Hi,
I'm working on a tool (KLEE) that interprets LLVM bitcode.
One of the things it does is it instruments the LLVM bitcode with
checks for division by zero. It does this by injecting calls to a
function "klee_div_zero_check(long long divisor)" just before every
division instruction (e.g. SDiv). These checks are injected by a pass
that has been implemented in KLEE.
This klee_div_zero_check() function is implemented in C and is
compiled to LLVM Bitcode which is then linked into the module that
KLEE is interpreting...
2013 Aug 30
1
[LLVMdev] Are instr_iterators invalidated when function inlining is performed?
Hi,
I'm trying to write a small piece of code that inlines all calls to a
particular function. The codes is as follows
Function* klee_check_divF = module->getFunction("klee_div_zero_check");
assert(klee_check_divF != 0 && "Failed to find klee_div_zero_check function");
// Hack inline checks
for (Module::iterator f = module->begin(), fe = module->end(); f != fe; ++f) {
for (inst_iterator i=inst_begin(f), ie = inst_end(f); i != ie; ++i) {
i...
2013 Sep 15
0
[LLVMdev] Are instr_iterators invalidated when function inlining is performed?
...53 AM, Daniel Liew <daniel.liew at imperial.ac.uk> wrote:
>> Hi,
>>
>> I'm trying to write a small piece of code that inlines all calls to a
>> particular function. The codes is as follows
>>
>> Function* klee_check_divF = module->getFunction("klee_div_zero_check");
>> assert(klee_check_divF != 0 && "Failed to find klee_div_zero_check function");
>> // Hack inline checks
>> for (Module::iterator f = module->begin(), fe = module->end(); f != fe; ++f) {
>> for (inst_iterator i=inst_begin(f), ie =...