search

DeadCodeProductions / dead

Other
50 stars 5 forks source link

some doubts #47

Closed codyhu closed 1 year ago

codyhu commented 1 year ago

Hello, after reading the paper, I think it is a very interesting and meaningful work.

In the meantime, I have some specific questions and would like your answers.

  1. I have no doubts about the current way of inserting the DCEMarker and think it is a very effective. The question is, how exactly do I construct my own test set? Or, how do I add the corresponding DCEMarker to my local test case？

  2. On the basis of the first question, if I can insert the corresponding DCEMarker into some benchmarks, such as spec, can it also help the compiler to optimize its performance?

Hope to get your reply ASAP.

Thx again.

Quarub commented 1 year ago

Hi @codyhu

you can add markers to your programs by invoking instrument_program from the dead_instrumenter package on your code. An example use can be found here.

The markers hinder optimizations. This, for example, has been pointed out in issue #30 . If you want to reuse the information gained from the markers on the benchmark, you'll mostly be out of luck as there's not much dead code in more realistic code (compared to csmith code). Thus, you have few opportunities to optimize in the first place.

codyhu commented 1 year ago

Got it, Thx.

Quarub commented 1 year ago

Closing because it seems to be resolved