Bug 37280 - [regression] 32-bit iPad has issues when perform 32 bit floats as 64 bit is NOT checked
Summary: [regression] 32-bit iPad has issues when perform 32 bit floats as 64 bit is N...
Status: RESOLVED DUPLICATE of bug 37045
Alias: None
Product: iOS
Classification: Xamarin
Component: Mono runtime / AOT compiler ()
Version: XI 9.4 (iOS 9.2)
Hardware: Macintosh Mac OS
: Highest blocker
Target Milestone: C6SR1
Assignee: Zoltan Varga
Depends on:
Reported: 2015-12-24 17:43 UTC by Neal
Modified: 2016-01-04 19:47 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Neal 2015-12-24 17:43:43 UTC

My beta testers are reporting lockups in my iOS app and text rendering issues (blurry fonts) and I tested against an iPad 4 (32 bit device) and my UIButtons don't even render (GlassButton from Miguel) in an iPad modal popup for login UI.  I turned off (cleared tick) of the perform 32 bit floats as 64 bit due to the noted performance and trying to get max perf out of my app.  Turning this back ON resolves this issue.  I used debug / iPhone to test on my iPad 4 to repro and resolve the issue with this setting.

=== Xamarin Studio ===

Version 5.10.2 (build 49)
Installation UUID: 73513e37-5013-428d-8378-0897497f2380
	Mono 4.2.2 (explicit/7b87787)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402020010

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.Mac ===

Version: (Business Edition)

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 78c6cd3
Branch: master
Build date: 2015-12-17 18:29:42-0500

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/Neal/Applications/android-sdk-macosx
	Supported Android versions:
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
		6.0   (API level 23)

SDK Tools Version: 24.4.0
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)

=== Xamarin Android Player ===

Not Installed

=== Build Information ===

Release ID: 510020049
Git revision: deed4cd240ff3611c8742bbc62296e207f46173d
Build date: 2015-12-17 11:13:36-05
Xamarin addins: 8bd975e7b465f6fe812b64d736f3b7e8c1a79a3e
Build lane: monodevelop-lion-cycle6-c6sr1

=== Operating System ===

Mac OS X 10.11.2
Darwin iMACRH.local 15.2.0 Darwin Kernel Version 15.2.0
    Fri Nov 13 19:56:56 PST 2015
    root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2015-12-24 19:21:28 UTC
## Note to the Xamarin team for initial cross-referencing

I think this might be the same underlying problem as non-public Bug 37045? (And in that case the problem should in principle be resolved in the next preview release of Cycle 6 – Service Release 1.)
Comment 2 Sebastien Pouliot 2015-12-24 19:43:58 UTC
Agreed, it's likely the same, already fixed, issue.
Comment 3 GouriKumari 2016-01-04 19:47:02 UTC
Based on verification results, I am marking this bug as duplicate of bug 37405. Fix for this issue will be available with next cycle6-SR1 alpha release.

*** This bug has been marked as a duplicate of bug 37045 ***