3 ms·
it's too bad the JVM inlining budget isn't configurable or hintable, that seems like a poor design decision to have to work around. Then again, the JVM probably
by pmarreck 10y ago
it's too bad the JVM inlining budget isn't configurable or hintable, that seems like a poor design decision to have to work around. Then again, the JVM probably wasn't originally intended to be the foundation for a dozen other languages
- ianopolous 10y agoIt is with -XX:MaxInlineSize=35 (that's the default number of bytecodes to consider inlining)
- jgalt212 10y agoOK, so can you develop with better error messages, and then ship to production a jar a faster version with the spartan error messages?
- puredanger 10y agoWe have been working on this off an on for a while and that's definitely an option.
- pmarreck 10y agoSo why couldn't they simply include the extra debug code and use that config for Clojure compiles?
- twoodfin 10y agoHotSpot is a JIT, so that's a runtime option. You'd be asking anyone deploying a .jar containing some Clojure to add fiddly configuration. Not impossible, but one of the heavily advertised virtues of Clojure is that it can be deployed alongside Java code without anyone having to be the wiser.
- puredanger 10y agoWe general try to assume that the user has applied no special JVM options. Planning with that as a baseline is much better than requiring people supply a big soup of options.
- jdc 10y agoCan these options not be set with an ini file? If not, why not use a shell script?