Hi Jochen; I also spent some time being concerned about the integer performance but then decided that this concern is probably premature based on the current state of indy. One big unknown to me is whether EA would ever recognize my holder for the prim int or if it would only recognize java Integer when it looks at boxing. There is also the possibility of fixnums support ( prims in pointers) that may or may not be useful in my design.
So I decided that all my ints will be boxed (references), added a cache and some special prim methods for now and then follow Charles approach of a good indy design to take advantage of the optimization efforts. Based on my large scale benchmarks this is ok so I am focusing on other places to optimize. This also supports my automatic conversion to/from BigInts. Log term I am guessing that I will follow your path of special paths with guards, Unless I can get the performance I want with more cores. regards mark
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
