RFR: 8348645: IGV: visualize live ranges [v3]

[Damon Fenacci]

On Tue, 18 Feb 2025 10:31:26 GMT, Roberto Castañeda Lozano <rcastanedalo at openjdk.org> wrote:

>> This changeset extends IGV with live range visualization. It introduces live ranges as first-class IGV entities and displays them along with the control-flow graph in the CFG view. Visualizing liveness information should hopefully make C2's register allocator easier to understand, diagnose, debug, and enhance.
>> 
>> Live ranges are visible in C2 phases where liveness information is available, that is, phases `Initial liveness` to `Fix up spills` at IGV print level 4 or greater. For example, running a debug build of the JVM as follows:
>> 
>> 
>> java -Xbatch -XX:CompileCommand=IGVPrintLevel,java.util.HashMap::newNode,4
>> 
>> 
>> produces the following visualization for the `Initial spilling` phase:
>> 
>> ![initial-spilling](https://github.com/user-attachments/assets/1ecf74f5-92a8-4866-b1ec-2323bb0c428e)
>> 
>> Live ranges are first-class IGV entities, meaning that the user can:
>> 
>> - search, select, and extract them;
>> 
>> ![search-extract](https://github.com/user-attachments/assets/8e0dfa59-457f-49cb-b2b5-1d202301c79d)
>> 
>> - examine their properties in the `Properties` window or via tooltips;
>> 
>> ![properties](https://github.com/user-attachments/assets/68d2d23b-b986-4d2e-835c-b661bce0de23)
>> 
>> - navigate to related IGV entities via a pop-up menu; and
>> 
>> ![popup](https://github.com/user-attachments/assets/21de2fef-d36a-42d5-b828-2696d87a18ea)
>> 
>> - program filters that act om them according to their properties.
>> 
>> ![filters](https://github.com/user-attachments/assets/e993b067-d0b8-452c-a885-c4e601e31e1c)
>> 
>> Live ranges are connected to nodes by a use-def relation: a node can define zero or one live ranges, and use multiple live ranges; a live range can be defined and used by multiple nodes. Consequently, a live range in IGV is visible if and only if all its related nodes are visible (fully or semi-transparently). Generally, the start and end of a live range are vertically aligned with the nodes that first define and last use the live range. To reflect accurately the semantics of Phi nodes w.r.t. liveness, the visualization treats live ranges related by Phi nodes specially: live ranges used by a Phi node end at the bottom of the corresponding predecessor basic blocks, whereas live ranges defined by a Phi node start at the top of the node's basic block. The following screenshot shows an example of a Phi node (`48 Phi`) joining live ranges `L8` and `L13` into `L15`:
>> 
>> ![phi](https://github.com/user-attachments/assets/0ef8aa1d-523d-4391-982e-6b74c2016a3c...
>
> Roberto Castañeda Lozano has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Remove unnecessary whitespace

Thanks for the fix Roberto.

I noticed that the live ranges are not saved when saving the graph into an xml file (`LIVE_RANGES_ELEMENT` and related tags don't seem to be exported in `Printer.java`). Is this perhaps something you did intentionally (maybe to be added in the future)?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/23558#issuecomment-2668185963