Changes between Version 9 and Version 10 of Doc/compiler/problems
- Timestamp:
- May 22, 2007, 5:39:38 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/compiler/problems
v9 v10 26 26 The java-implementation of the pan language compiler is completely multi-threaded. Internally, it controls several thread pools to handle compilation, execution, and serialization in parallel. At the end of a compilation, the compiler will normally destroy the thread pools that were created. The java security model requires that a program have the "modifyThread" permission to destroy threads. In some environments (notably eclipse), this permission may not be given to the compiler. If this is the case, then the message "WARNING: missing modifyThread permission" is printed on the standard error. Lacking this permission causes a "thread leak", but the effects are minor unless an extremely large number of templates are being compiled. If this is the case, then you should either change the configuration to grant this permission to the compiler, or work in an environment that grants it by default (e.g. using ant from the command line). 27 27 28 A possible fix can be using Java6. 29 * To configure eclipse with multiple JREs: go to "Window -> Preferences -> Java -> Installed JREs". If you don't see the JRE you want (and you have it installed), use the "Search" button to have eclipse configure the new JRE for you. Make sure you select it after it is found. 28 This problem is fixed if using Java6. To configure eclipse with multiple JREs: go to "Window -> Preferences -> Java -> Installed JREs". If you don't see the JRE you want (and you have it installed), use the "Search" button to have eclipse configure the new JRE for you. Make sure you select it after it is found. 30 29 30 31 == Miscellaneous == 32 33 === Unnecessary rebuild of clusters === 34 35 It can happen that a cluster is always rebuilt when you run `ant`, even if there was no change in the dependencies. In this case, you may suspect a Java issue with optimizations enabled by default (JIT). The only workaround is to disable these optimizations by adding the option `-Xint` to Java VM when running ant. It is achieved differently depending how you started ant : 36 * From command line : define environment variable `ANT_OPTS`. 37 * From Eclipse : right click on `build.xml` in ant pane, choose `Run As...-> External Tools...` and then click on `JRE` tab. Be sure to use a separate JRE (if possible Java 6 or later) and add option in the options area. 38 39 This problem has been seen on Windows only, with Java 5 and Java 6.
