New CE/EE version string

(cherry picked from commit af808ba)

Author: chrisseaton

CHANGELOG.md

@@ -25,6 +25,8 @@ New features:
 
 Changes:
 
+* The version string now mentions `GraalVM CE` or `EE`.
+
 * The inline JavaScript functionality `-Xinline_js` has been removed.
 
 * Line numbers `< 0`, in the various eval methods, are now warned about, because

README.md

@@ -47,28 +47,31 @@ is that you can't use Java tools like VisualVM, you can't use Java
 interoperability, and *peak performance may be lower than on the JVM*. The
 native configuration is used by default, but you can also request it using
 `--native`. To use polyglot programming with the *native* configuration, you
-need to use the `--polyglot` flag.
+need to use the `--polyglot` flag. To check you are using the *native*
+configuration, `ruby --version` should mention `Native`.
 
 TruffleRuby can also be used in the *JVM* configuration, where it runs as a
 normal Java application on the JVM, as any other Java application would. The
 advantage of the JVM configuration is that you can use Java interoperability,
 and *peak performance may be higher than the native configuration*. The
 disadvantage of the JVM configuration is that it takes much longer to start and
 to get fast, and may use more memory. The JVM configuration is requested using
-`--jvm`.
+`--jvm`. To check you are using the *JVM* configuration, `ruby --version` should
+not mention `Native`.
 
 If you are running a short-running program you probably want the default,
 *native*, configuration. If you are running a long-running program and want the
 highest possible performance you probably want the *JVM* configuration, by using
 `--jvm`.
 
 At runtime you can tell if you are using the native configuration using
-`TruffleRuby.native?`.
+`TruffleRuby.native?`
 
 You won't encounter it when using TruffleRuby from the GraalVM, but there is
 also another configuration which is TruffleRuby running on the JVM but with the
 Graal compiler not available. This configuration will have much lower
-performance and should normally only be used for development.
+performance and should normally only be used for development. `ruby --version`
+will mention `Interpreter` for this configuration.
 
 ## System Compatibility
 

doc/user/faq.md

@@ -85,9 +85,25 @@ chris.seaton@oracle.com.
 
 ### How do I know if I’m using a VM that has Graal?
 
+`ruby --version` will report `GraalVM CE` or `EE`.
+
 `TruffleRuby.graal?` will tell you if you are also running with the Graal
 dynamic compiler.
 
+### How do I know that I'm using the Community Edition of GraalVM?
+
+`ruby --version` will report `GraalVM CE`.
+
+### How do I know that I'm using the Enterprise Edition of GraalVM?
+
+`ruby --version` will report `GraalVM EE`.
+
+### How do I know that I'm using the native version of TruffleRuby?
+
+`ruby --version` will report `Native`.
+
+`TruffleRuby.native?` will return `true`.
+
 ### How can I see that Truffle and Graal are working?
 
 Put this program into `test.rb`:

doc/user/installing.md

@@ -64,7 +64,8 @@ rebuild the Ruby executable images using the runtime from the Enterprise
 Edition. The version of the Ruby executable images you install by default uses
 the Community Edition runtime until you rebuild.
 
-To get the best performance you want to rebuild the images.
+To get the best performance you want to rebuild the images. Check with `ruby
+--version` that it says you are running `EE` rather than `CE`.
 
 Rebuilding the executable images can take a few minutes and you should have
 about 8 GB of RAM available.