Building frustration

[Doug Simon]

> On 27 Dec 2015, at 12:38, Raffaello Giulietti <raffaello.giulietti at supsi.ch> wrote:
> 
> Hi Stefan,
> 
> 
> On 2015-12-27 04:54, Stefan Marr wrote:
>>> thanks for your supporting words (fyi, Raffaella with the final "a" in
>>> your reply is the female variant of my first name).
>> 
>> Sorry. I’d like to blame OS X autocorrect for the typo, it just tried to do it again. Sorry.
>> 
> 
> No problems.
> 
> 
> 
>>> I dislike Ubuntu for other reasons not related to Truffle/Graal.
>>> However, I have to admit that, at least for the purpose of building
>>> Truffle/Graal and for working on it, it was much smoother an experience
>>> than with CentOS, Fedora and Oracle Linux, all of them I tried before.
>>> Hence, I think I’ll stick with it.
>> 
>> Strange, I would not expect much differences with those distributions either.
>> Not sure what the counter part of build-essentials is, but it shouldn’t be much more than a C/C++ tool chain, and some development headers (see http://packages.ubuntu.com/trusty/build-essential).
>> 
>> I was under the impression that some of us use Oracle Linux to work on Graal. Perhaps we could extend the instructions for those distributions. Do you remember any of the specific issues you ran into?
>> 
> 
> Since I don't remember the details, I would have to retry the
> installation. I run my Linux systems as VirtualBox images, so that
> should be possible with little investment in time starting from scratch,
> i.e., by first installing the OS (for what it costs, VirtualBox is
> really a great product). No promises, however...
> 
> 
> 
>>> I still have two questions:
>>> 
>>> * The very last command on
>>> https://wiki.openjdk.java.net/display/Graal/Instructions does not work
>>> for me, although the IGV starts without problems. The message reads:
>>> 
>>> Unrecognized option: -jvmci
>>> 
>>> (I've configured the "server" HotSpot VM during the build.) For the time
>>> being I can live without the internals of Graal's IR, but one day I'd
>>> like to have a look at it, just as user, not as developer.
>> 
>> Yes, that’s expected behavior, I think.
>> 
>> ’server’ means that the C2 compiler, i.e., the standard Hotspot top-tier compiler is used for the Java code.
>> ‘jvmci’ means, the JVMCI compiler, which in our case is Graal, is going to be used as top-tier compiler for all Java code. So, if you built the ‘server’ VM, this specific example is not going to work. To dump the compiler graphs with the -G:Dump= option and then inspect them with IGV, the code needs to be compiled with Graal. So, an JVMCI build is necessary to inspect Java code compilation.
>> 
>> However, if you run a Truffle-based language on top of a ’server’ build, you can still use the ‘-G:Dump=‘ option and IGV to see what get’s compiled, inlined, etc.
>> 
>> 
> 
> I see Doug just changed the instructions about IGV on the page. Doug is
> unbelievable: he seems to be working 24 x 7!

Gotta keep the customers happy ;-)

> Thanks Doug, it works now.

Great.

-Doug