Enso Language Support for Ideal Graph Visualizer & NetBeans

Enso language runtime engine is built on top of GraalVM and its Truffle framework. Enso, as a good citizen of the GraalVM ecosystem, benefits from polyglot capabilities of GraalVM as well as its rich tooling offering. One of such tools is IGV - the Ideal Graph Visualizer - an excellent tool to get insights into behavior of Graal compiler.

This document shows how to use IGV with the Enso language. The command line instructions format is Unix oriented. Use instructions appropriate for your operating system to perform the same on different OS. IGV itself as well as the Enso language support are platform neutral with launch scripts for all major operating systems.

Installation

Visit GraalVM's IGV page to read and download IGV. Or follow this link to get ZIP with the most up to date version of Ideal Graph Visualizer (as of June 2024). Then:

$ unzip idealgraphvisualizer-*.zip
$ ./idealgraphvisualizer/bin/idealgraphvisualizer --userdir /tmp/emptyuserdir

launches the IGV application. One doesn't have to use the --userdir option, but doing so ensures the newly running IGV process is isolated from any settings left around by previous usage of IGV.

IGV understands Enso when Enso Language Support module is installed. Login to GitHub, follow the GitHub actions link and select a build. Unless you have some special needs choose the latest one. The build summary page provides various information as well as list of artifacts at the bottom. Download the Enso IGV Plugin ZIP file (make sure you are logged into GitHub - artifacts are only available to those logged in). Unzip it and get enso*.nbm file. This file can be installed into IGV (or any other NetBeans based application). Go to Tools/Plugins/Downloaded/Add Plugins and select the NBM file.

Proceed by clicking Install. You may be asked to download TextMate Lexer - a necessary dependency of the Enso support module. Continue through the wizard to finish the installation.

Using the IGV

Build an instance of the Enso runtime engine (see Running Enso) using and then launch it the following system properties:

enso$ env JAVA_OPTS='-Dgraal.Dump=Truffle:2 -Dgraal.PrintGraph=File' ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run yourprogram.enso

See Graal system props docs for the description of the graal system properties.

When executed on GraalVM 22.3.1 these options instruct the Graal/Truffle compiler to dump files into graal_dumps/_sometimestamp_ directory. Generating these files takes a while - make sure yourprogram.enso runs long enough for the system to warmup, compile the code and run at full speed.

Sieve of Eratosthenes Example

As an example you can download sieve.enso which computes hundred thousand of prime numbers repeatedly and measures time of each round. Download the file and launch Enso with:

enso$ env JAVA_OPTS='-Dgraal.Dump=Truffle:2 -Dgraal.PrintGraph=File' ./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --run yourprogram.enso

Bunch of files in graal_dumps/* subdirectory is going to be generated:

enso$ ls graal_dumps/*/Truffle* | tail -n5
graal_dumps/2022.06.20.06.18.21.733/TruffleHotSpotCompilation-9889[argument<2>].bgv
graal_dumps/2022.06.20.06.18.21.733/TruffleHotSpotCompilation-9896[IfThenElseMethodGen@3af870b9_<split-62b6b4f3>]_1.bgv
graal_dumps/2022.06.20.06.18.21.733/TruffleHotSpotCompilation-9896[IfThenElseMethodGen@3af870b9_<split-62b6b4f3>].bgv
graal_dumps/2022.06.20.06.18.21.733/TruffleHotSpotCompilation-9935[Primes.next_<split-717d5bdf>]_1.bgv
graal_dumps/2022.06.20.06.18.21.733/TruffleHotSpotCompilation-9935[Primes.next_<split-717d5bdf>].bgv

Let's launch IGV with Enso integration. Locate the engine/runtime directory and open it as "project" in IGV:

The project directories (not only runtime, but also other like runtime-language-epb, etc.) are recognized only if you have built the Enso engine sources with sbt buildEngineDistribution. Once the IGV opens the runtime & co. projects, it allows smooth navigation among the sources

With such setup let's open graph for one of the top-most functions: TruffleHotSpotCompilation*Primes*next*.bgv. Choose compilation phase "Before lowering":

Now you can inspect the compiler graphs the regular IGV way. Let's locate for example LoadField#FunctionSchema.isFullyApplied node and let's check how it got inlined(you can use search box in the top-right corner)

The stack trace shows what methods of the Enso interpreter and Truffle runtime are "inlined on stack" when this node is being compiled. However thanks to integration with engine/runtime sources one can directly jump to the sources of the interpreter that represent certain graph nodes:

Not only that, but one we can also switch to Enso view:

By choosing the Enso language icon in front of the stack trace combo, the source code of our .enso program is opened and we can analyze what compiler nodes refer to what lines in the our Enso program. Click Navigate to Source icon in the Stack View to get from graph node to source. Select a drop down widget in the editor toolbar to show you what compiler nodes as associated with currently selected line.

Building

The plugin can be rebuilt using Apache Maven. The build is platform independent. The following instructions are for Unix like environment. Switch to this directory and invoke:

enso/tools/enso4igv$ mvn clean install
enso/tools/enso4igv$ ls target/*.nbm
target/enso4igv-*-SNAPSHOT.nbm

an NBM file is generated which can be installed into IGV, NetBeans or any other NetBeans based application.

VSCode Extension

There is also a VSCode extension for Enso. Read more about the extension here.

7.6 KiB Raw Blame History