snip...
>
> At a very high level, you should be aware of a general belief that GCJ's
> life is limited. There's been various calls to deprecate it. So
> spending a lot of time optimizing GCJ's output may not be the best use
> of your skills :-)
>
Unless things have changed since it was last d
On 02/22/2016 11:10 AM, ro...@nextmovesoftware.com wrote:
It has been a while since my last contribution. The following patch allows
GCC's optimizers
to more aggressively eliminate and optimize java array bounds checks. The
results are
quite impressive, for example producing a 26% performanc
On 02/22/2016 11:10 AM, ro...@nextmovesoftware.com wrote:
It has been a while since my last contribution.
It has been. I ran into some of your eyesopen.com colleagues a couple
years back at SC12 or SC13. It'd obviously be great to have you
contributing regularly again.
Note that we're ra
It has been a while since my last contribution. The following patch allows
GCC's optimizers
to more aggressively eliminate and optimize java array bounds checks. The
results are
quite impressive, for example producing a 26% performance improvement on the
sieve.java
benchmark given at http://k
