Bug 41950 - Bitcode stackoverflow with even-odd.exe test
Summary: Bitcode stackoverflow with even-odd.exe test
Status: CONFIRMED
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: 4.5.X
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Alexander Kyte
URL:
Depends on:
Blocks:
 
Reported: 2016-06-17 17:57 UTC by Alexander Kyte
Modified: 2016-09-14 01:28 UTC (History)
3 users (show)

Tags: bitcode_mobile_static
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 for Bug 41950 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Alexander Kyte 2016-06-17 17:57:48 UTC
This test is fairly simple, and yet results in a stackoverflow.
Comment 1 Alexander Kyte 2016-06-20 18:29:22 UTC
This is due to us not handling tailcall optimizations at all with llvm. 

When trying to use the naive "-tailcallopt" with llvm, llc segfaults. This is worth returning to. I'll probably implement OP_JMP on llvm and use that path of the tailcall infrastructure.
Comment 2 Rodrigo Kumpera 2016-09-14 01:28:33 UTC
Triaging it