On 6/27/20 5:33 AM, Shuai Wang via Gcc wrote:
virtual unsigned int execute(function *fun) override
which has no idea about the .C file information. In LLVM all .C files are
roughly maintained in separate "modules" but I just don't know how to
access such information in GIMPLE.
Hey.
Please tak
Any idea on that? I just cannot find a way of using GIMPLE to analyze
multiple .C files. All my analysis is still start from the following
function:
virtual unsigned int execute(function *fun) override
which has no idea about the .C file information. In LLVM all .C files are
roughly maintained in
Hello,
I am working on a basic block coverage counter which
mimics -fsanitize-coverage=trace-pc but has more features. My problem is
that when instrumenting multiple C files (e.g., test1.c test2.c test3.c), I
want to generate correspondingly three coverage logs (test1.log, test2.log,
test3.log), s
