remove stats:ppr parser workaround; update documentation

com.oracle.truffle.r.ffi.impl/src/com/oracle/truffle/r/ffi/impl/llvm/TruffleLLVM_DLL.java

@@ -26,8 +26,6 @@ import java.io.BufferedInputStream;
 import java.io.FileInputStream;
 import java.io.IOException;
 import java.nio.file.FileSystems;
-import java.nio.file.Path;
-import java.nio.file.Paths;
 import java.util.ArrayList;
 import java.util.zip.ZipEntry;
 import java.util.zip.ZipInputStream;
@@ -230,7 +228,7 @@ public class TruffleLLVM_DLL implements DLLRFFI {
      */
     private LLVM_IR[] libRModules;
 
-    private static final String[] PARSE_ERRORS = new String[]{"stats", "ppr"};
+    private static final String[] PARSE_ERRORS = new String[0];
 
     private static boolean parseFails(String libName, LLVM_IR ir) {
         for (int i = 0; i < PARSE_ERRORS.length / 2; i++) {

documentation/dev/truffle_llvm_ffi.md

@@ -30,6 +30,8 @@ The `sulong` repository must be cloned to a sibling directory of `fastr` and bui
 
 The `mx su-pulldragonegg` step is required to be able to compile Fortran code to LLVM, which is required by FastR.. As well as downloading DragonEgg this will also download and clang 3.2, which is needed to build DragonEgg. On Linux, it is necessary to use clang 3.2 in preference to any installed clang, e.g., 3.8, as some of the LLVM code generated by DragonEgg is syntax-incompatible with 3.8. The downloaded version is saved in `cache/tools/llvm/bin`.
 
+Once `dragonegg` is built, unset the `SULONG_GCC` and `SULONG_GPP` environment variables.
+
 Sulong must be built with a more recent version of `clang` than 3.2, which means that `sulong` and `fastr` cannot be built in one step.
 First make sure that you have a supported version of `clang` and related tools installed, e.g., 3.8 and that they are on your `PATH`. Also if you are on MacOS and are using MacPorts, you must make symbolic links to the explicitly versioned tool names, i.e. `clang` -> `clang-mp-3.8`. This also applies to the `opt` and `llvm-link` tools. You can set these links directly in `/opt/local/bin` using `sudo` or create a local `bin` directory and place the links there, making sure that this directory is on your `PATH`.