I would write at
https://groups.google.com/forum/#!forum/adt-dev
in addition to the bug report
On 08/07/2013 07:02 PM, Digipom wrote:
I figured it out -- I seem to have run into some sort of an obscure
floating-point optimization bug that occurs on certain devices. I
opened
I agree with you. And that also may be of concern for Eric Lafortune, the
ProGuard developer. It could be that there is a glitch in his code
obfuscation routines.
On Friday, August 9, 2013 2:49:42 AM UTC-5, Daniele Segato wrote:
I would write at
Interesting, I wasn't aware of the strictfp modifier. It seems that
changing one of the floats to a double may have fixed it... I sent out
several more specific tests and waiting for the remote debugger to confirm.
:)
On Wed, Aug 7, 2013 at 5:12 PM, Nobu Games dev.nobu.ga...@gmail.com wrote:
If
So after some further follow-up I can confirm there are two fixes:
1) Just print out the value of the variable in a Log.d. Believe it or not,
that fixes the code.
2) Change float into double.
Based on customer reports I received, the bug only affected users running
API 15 or 16, and only some
I figured it out -- I seem to have run into some sort of an obscure
floating-point optimization bug that occurs on certain devices. I
opened https://code.google.com/p/android/issues/detail?id=58698 to track
the issue. I haven't found a workaround yet aside from exporting from
Eclipse for now,
Thank you for posting the response here ;-)
On Wed, Aug 7, 2013 at 7:02 PM, Digipom digi...@gmail.com wrote:
I figured it out -- I seem to have run into some sort of an obscure
floating-point optimization bug that occurs on certain devices. I opened
If it is floating point related you could try adding the strictfp
modifier to your methods or classes that rely on platform-independent
floating point arithmetics.
On Wednesday, August 7, 2013 12:02:04 PM UTC-5, Digipom wrote:
I figured it out -- I seem to have run into some sort of an
7 matches
Mail list logo
