text:  3887 [details]
  Activity showing working vs. not working float collection examples
  I am seeing corrupted floating point values using the 4.7.4 Alpha for Xamarin.Android. I used the default API-level 10 emulator to observe this error as well as a brand new (but extremely cheap Android 2.3 phone). If I use a System.Collections.Generic.Queue to store values, then Dequeue corrupts the values. However, it works with a non-generic queue as well as a generic queue of doubles.
  Test app code is here:
  This error does not occur on the previous stable release series (4.6.4).
  Thanks for the report!
  The test fails on armeabi hardware, e.g. the Android 2.3.3 emulator, not armeabi-v7a.
  I'm guessing it's a JIT bug.
  This was caused by Mono revision 8f7a7a74 which made invalid assumptions about the target FPU. The code the commit touched was relevant for Android too, where the assumption is invalid.
  Commit 89c3c44d fixed it.
  *** Bug 12519 has been marked as a duplicate of this bug. ***
  We have checked this issue with XS 4.0.9 build 12 and MFA 4.7.11.2 :
  As this bug is duplicate of bug 12519.
  And by using following code from Bug 12519:
  namespace TestApp {
  [Activity (Label = "TestApp", MainLauncher = true)]
  public class Activity1 : Activity {
  protected override void OnCreate (Bundle bundle)
  {
  base.OnCreate (bundle);
  var testClass = new TestClass ();
  float prop1 = testClass.Prop1;
  Console.WriteLine ("Get Prop1: {0}", prop1);
  }
  }
  public class TestClass {
  public float Prop1 { get { return 0.5f; } }
  }
  }
  and on running application we get 'Get Prop1: 0.5' in console output.
  **********************************
  And when we tried it with application code:
  Application run successfully and we get following in console output:
  [monodroid-gc] GREF GC Threshold: 1800
  result = 1, as hex = 0000803F
  We are not clear about expected result.
  Let us know, is it expected result or not.
  0.5 is correct. 0.0 was the errant result it was returning before.