On 05/11/2015 04:19, Martin Buchholz wrote:
Alright, it's a much better situation if we're not giving up on fixing
the underlying problem.
I don't like temporary fixes. They tend to become permanent.
I agree and view this dialing down of the optimization level as
temporary until the issue is understood. Maybe it's a gcc bug or maybe
it is exposing a bug in Bits.c or somewhere else. We need to do get a
handle on it and if a gcc bug then we need to understand it in case
there is other code impacted. I've been busy with other things and
haven't had time to look at it myself.
BTW: I think you asked about the purpose of the methods, you need to
look into Direct-X-Buffer.java.template to see that they are only used
when the buffer is not in native order. A while back we eliminated most
of the JNI code, it's only the cases where we need to swap that still
have native code.
-Alan
