search for: qus2

...gt;> BB. >> > Can you add some debug dumping to your pass and give some real-world >> examples of counters that it merges? >> >> I still have the pruned IR from the example I brought up at the start >> of the thread: >> >> https://ghostbin.com/paste/qus2s >> >> Look for the __llvm_prf_alias section. >> > > Could you maybe digest that a bit for us to give source-level examples of > what those counters are that end up aliased? > > Also, in the linked IR there is still a tremendous amount of counter > redundancy bei...

...function bar() is the only caller of foo() and calls it in only one BB. > Can you add some debug dumping to your pass and give some real-world examples of counters that it merges? I still have the pruned IR from the example I brought up at the start of the thread: https://ghostbin.com/paste/qus2s Look for the __llvm_prf_alias section. > The fused counter approach (or the one I suggested which is just a generalization of that (see below)) seems like it can reduce the number of counter updates much more. > > > 4. > > >> The complexity of this pass is O(N*M), wh...

There have been a lot of responses. I'll try to summarize the thread and respond to some of the questions/feedback. Summary ======= 1. We should teach GlobalDCE to strip out instrumented functions which the inliner cannot delete. 2. Sean suggests adding metadata to loads/stores of counters to convey that they do not alias normal program data. I'm not familiar with AA, but