P4
When debugging, I often add multiple IR dumps throughout the code to capture different states. To do that, I'm just re-using various PHASE_XYZ CompilerPhaseType enum values:
Compile::current()->print_method(PHASE_END, 3);
But this becomes confusing when using multiple such enum values and trying to remember what they actually mean. To overcome that, I suggest to introduce a new dump_igv(custom_name) method where custom_name can be an arbitrary string.
Compile::current()->print_method(PHASE_END, 3);
But this becomes confusing when using multiple such enum values and trying to remember what they actually mean. To overcome that, I suggest to introduce a new dump_igv(custom_name) method where custom_name can be an arbitrary string.
