<div dir="ltr"><div>(I admit that I remain intimidated by the build system.)</div><div><div> </div><div>I'm renabling some ticky counter bumps from within the RTS. The most direct path I see to this involves adding -ticky to makefile variables such as WAY_debug_HC_OPTS. (See the APPENDIX for why I need that.)</div>
</div><div> </div><div>It seems that the debug way is only used in the build system for building the RTS. Is that right?</div><div> </div><div>If so, will a flag added to the debug HC_OPTS vars in <a href="http://ways.mk">ways.mk</a> only be used when compiling from .cmm sources? If so, my -ticky flag won't be putting ticky counters into any .o file where I'm not expecting them, right?</div>
<div> </div><div>So:</div><div> </div><div>1) Is it a bad idea to add -ticky to the non-threaded and non-profiling WAY_debug*_HC_OPTS variables in <a href="http://ways.mk">ways.mk</a>?</div><div> </div><div>2) Alternative designs? A few come to mind, but they're more invasive/fragile.</div>
<div> </div><div>Thank you for your time.</div><div> </div><div> </div><div> </div><div>APPENDIX</div><div> </div><div>For example:</div><div> </div><div> * The (generated) definition of stg_ap_*_info uses BUILD_PAP</div>
<div> </div><div> * The definition of BUILD_PAP uses TICK_ALLOC_PAP</div><div> </div><div> * TICK_ALLOC_PAP is elaborated by CmmParse.y using StgCmmTicky.tickyAllocPAP</div><div> </div><div> * tickyAllocPAP emits no code unless Opt_Ticky is present.</div>
<div> </div><div> * -ticky is not currently in the relevant command lines</div></div>