Re: Exception at "need_ssa_update_p" during GIMPLE instrumentation

2020-06-21 Thread Richard Biener via Gcc
On June 21, 2020 11:38:49 AM GMT+02:00, Shuai Wang via Gcc wrote: >OK, I think I know how to solve it. Just return TODO_update_ssa >. If you dump with -vops you'll likely see that virtual operands got out of sync. You can either manually copy

gcc-11-20200621 is now available

2020-06-21 Thread GCC Administrator via Gcc
Snapshot gcc-11-20200621 is now available on https://gcc.gnu.org/pub/gcc/snapshots/11-20200621/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 11 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: Exception at "need_ssa_update_p" during GIMPLE instrumentation

2020-06-21 Thread Shuai Wang via Gcc
OK, I think I know how to solve it. Just return TODO_update_ssa . On Sun, Jun 21, 2020 at 5:34 PM Shuai Wang wrote: > Hello, > > I am doing instrumentation of GIMPLE code by adding extra coverage > counters at each basic block. Basically it's

Exception at "need_ssa_update_p" during GIMPLE instrumentation

2020-06-21 Thread Shuai Wang via Gcc
Hello, I am doing instrumentation of GIMPLE code by adding extra coverage counters at each basic block. Basically it's mimicking -fsanitize-coverage=trace-pc, where the only difference is that __sanitizer_cov_trace_pc (the default hander of fsanitize-coverage=trace-pc) has no input parameters, bu