Variable Tracking Optimisation

Variable Tracking is enabled with -fvar-tracking and -fvar-tracking-assignments and imposes a significant hit in GCC's runtime. By default it's on when optimisation is turned on (not -O0). Its functionality as described in the man page:

Run variable tracking pass. It computes where variables are stored at each position in code. Better debugging information is then generated (if the debugging information format supports this information).
Annotate assignments to user variables early in the compilation and attempt to carry the annotations over throughout the compilation all the way to the end, in an attempt to improve debug information while optimizing. Use of -gdwarf-4 is recommended along with it.

Call Graph


(times called)

[instruction count]




  * vt_find_locations



    * compute_bb_dataflow.isra.47



      * hashtab.c:htab_traverse



      * dataflow_set_clear_at_call



      * val_resolve



      * val_store.isra.45



    * dataflow_set_merge



      * hashtab.c:htab_find_slot_with_hash



      * canonicalize_values_star



      * dataflow_set_merge

(time in itself)


  * vt_emit_notes



    * emit_notes_for_changes



    * hashtab.c:htab_traverse



    * dataflow_set_clear



    * dataflow_set_clear_at_call



  * vt_initialize



    * cselib.c:cselib_process_insn



      * cselib_record_sets

None: Optimise variable_tracking (last edited 2011-08-05 22:03:19 by 139)