Hi guys,
turns out that in our real-life scenario there sadly aren't big
improvements yet. Might be due to the exception handling, but
we haven't profiled it yet. As said we have seen better improvements
in simpler benchmark code - but this benchmark here is what
really matters for us.
Please fin
Am 16.11.2018 um 20:22 schrieb Simon Kissel:
> Hi guys,
>
> turns out that in our real-life scenario there sadly aren't big
> improvements yet. Might be due to the exception handling, but
> we haven't profiled it yet. As said we have seen better improvements
> in simpler benchmark code - but this
On 16/11/18 22:44, Florian Klämpfl wrote:
With some compiler tuning and a few tricks (two changes to the code and
hand-simulated peephole optimizations, but I
think these tricks can also the compiler do):
You can improve performance further by devirtualising all method calls
using wpo. First
Am 16.11.2018 um 23:36 schrieb Jonas Maebe:
> On 16/11/18 22:44, Florian Klämpfl wrote:
>> With some compiler tuning and a few tricks (two changes to the code and
>> hand-simulated peephole optimizations, but I
>> think these tricks can also the compiler do):
>
> You can improve performance furth
Am 16.11.2018 um 23:41 schrieb Florian Klämpfl:
> Am 16.11.2018 um 23:36 schrieb Jonas Maebe:
>> On 16/11/18 22:44, Florian Klämpfl wrote:
>>> With some compiler tuning and a few tricks (two changes to the code and
>>> hand-simulated peephole optimizations, but I
>>> think these tricks can also th
At the moment, I'm experimenting with overhauling the x86_64 optimizer to
see if I can reduce the number of passes through a block of code - my hope
is to greatly increase the speed of the compiler without sacrificing the
optimisations performed under -O1 and -O2. At present, I've attempted to
no
