Bug 17527 - FSharp.Core.dll AOT failure when using LLVM
Summary: FSharp.Core.dll AOT failure when using LLVM
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: master
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 7.2.1
Assignee: Bugzilla
Depends on:
Reported: 2014-01-30 22:12 UTC by Will Smith
Modified: 2014-03-21 02:43 UTC (History)
5 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 Will Smith 2014-01-30 22:12:55 UTC
When I tried build a release version of an app I'm working on in F# on Xamarin iOS, the FSharp.Core.dll failed to AOT. With some testing, I was able to get around the issue by turning off the LLVM optimizer; therefore, using the LLVM optimizer will cause an AOT of FSharp.Core.dll to fail.

The failure results in this message: "error MT3001: Could not AOT the assembly"

This is with the very latest FSharp.Core and FSharp Bindings from GitHub.

More info: https://github.com/fsharp/fsharp/issues/250
Comment 1 Zoltan Varga 2014-01-30 23:50:53 UTC
xamarin.ios includes the f# assemblies, those might work better than the original ones.
Comment 2 Zoltan Varga 2014-01-30 23:57:10 UTC
Could you add '-v -v -v -v' to the mtouch arguments in Project/Options/IOS Build, and attach the output ?
Comment 3 Zoltan Varga 2014-01-31 00:19:06 UTC
Fixed in mono 19362c66eec49d7a5da038e9796072a5cec82e8f/mt c7a89a527c378293ffb853a5482175a438c0162b.
Comment 4 Dave Thomas 2014-01-31 14:24:32 UTC
Is there a way of testing this easily without a custom build of monotouch?
Comment 5 Zoltan Varga 2014-01-31 17:06:21 UTC
You can try a recent snapshot from:
Comment 6 Zoltan Varga 2014-03-12 18:01:51 UTC
Comment 7 Sadik Ali 2014-03-21 02:43:40 UTC
I have verified this issue. I build F# application successfully in release version using LLVM optimizer on and off both.

Screen cast: http://www.screencast.com/t/hTgiDyew70Ww

Build Version:

=== Xamarin Studio ===
Version 4.2.4 (build 32)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
 Mono 3.2.7 ((no/40f92d5)
 GTK+ 2.24.23 (Raleigh theme)

=== Xamarin.Android ===
Version: 4.12.1 (Trial Edition)

=== Apple Developer Tools ===
Xcode 4.6.2 (2067.2)
Build 4H1003

=== Xamarin.Mac ===

=== Xamarin.iOS ===
Version: (Trial Edition)

=== Build Information ===
Release ID: 402040032
Git revision: a160c35dac9ab9fd32eeadaa171216316d5a5133
Xamarin addins: a779416ceabd54981ce812771a4061c942e8b872