Bug 15844 - AOT Compilation exited with code 134
Summary: AOT Compilation exited with code 134
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 1.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2013-10-31 07:41 UTC by Jacco Rademaker
Modified: 2013-10-31 11:11 UTC (History)
3 users (show)

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


Attachments
A sample solution, the build output and my version information (31.11 KB, application/x-zip-compressed)
2013-10-31 07:41 UTC, Jacco Rademaker
Details


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:
Status:
RESOLVED FIXED

Description Jacco Rademaker 2013-10-31 07:41:16 UTC
Created attachment 5290 [details]
A sample solution, the build output and my version information

The AOT compilation fails when using "Link all assemblies".
In the attachment you can find a sample solution containing:
 - an iOS project
 - a Portable Class Library

The zip also contains my Version Information and the Build Output.
Comment 1 Sebastien Pouliot 2013-10-31 10:33:36 UTC
Thank you for providing a test case along with the build/versions details. It makes things a lot simpler and remove any doubts :-)

It turned out to be a known issue with type forwarders (used extensively in PCL assemblies) and is already fixed (confirmed with your test case). The fix will be released as part of the 7.0.4 release.
Comment 2 Jacco Rademaker 2013-10-31 10:43:56 UTC
Thank you Sebastien for your quick response.
Any estimate of when this will be available (alpha or beta)?

(Not AOT compiling our app seems to cause a large performance penalty, so we are really looking forward to the fix.)
Comment 3 Sebastien Pouliot 2013-10-31 11:06:01 UTC
> Any estimate of when this will be available (alpha or beta)?

I expect 7.0.4 to be released next month - but it's too soon to know when an alpha will be released.

> Not AOT compiling our app

Not sure I understand correctly. All device builds are AOT'ed - that's required for iOS devices (where the JIT can't be used). So you should not be able to compare performance with a non-AOT'ed build.

Maybe you mean not enabling "Link all" ? In that case you _might_ be able to workaround this by using some `--linkskip=ASSEMBLY_NAME_WITHOUT_EXTENSION` in the "Additional mtouch arguments" of your project's options.
Comment 4 Jacco Rademaker 2013-10-31 11:11:11 UTC
Yes, my bad, I meant "Link all".
I'll try linkskip and see if I can make it build and improve it's performance.

Thanks again.