<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_1_1438184102968_10477">Hi all,</div><div id="yui_3_16_0_1_1438184102968_10415"><br></div><div id="yui_3_16_0_1_1438184102968_10426">I'm working on the CoreCLR project, coordinating a community effort to produce an Android port of Microsoft's open-source version of the CLR. A major part of that is getting everything to run on the ARM32 architecture, which is by far the most common CPU for Android devices.</div><div id="yui_3_16_0_1_1438184102968_10476"><br></div><div id="yui_3_16_0_1_1438184102968_10482" dir="ltr">A couple weeks ago, Ben Pye, a developer working on the ARM32 stuff, found and reported a bug related to incorrect generation of stack unwinding info. ( https://llvm.org/bugs/show_bug.cgi?id=24146 ) Apparently it only occurs under a highly specific set of circumstances, which might look like a minor corner case, except that that just happens to be exactly the configuration needed to build CoreCLR for ARM32. This is a blocking problem for us, and I was just wondering how things are coming on it? Has anyone been looking into this, who might be able to provide some sort of estimate as to what's going on and when we might expect to see a fix?</div><div id="yui_3_16_0_1_1438184102968_10573" dir="ltr"><br></div><div id="yui_3_16_0_1_1438184102968_10572" dir="ltr">I totally understand that sometimes working on a project gets to be more important than talking about it, but it would be nice to at least get *some* feedback. :)<br></div><div id="yui_3_16_0_1_1438184102968_10379"><br></div><div id="yui_3_16_0_1_1438184102968_10603">Thanks,</div><div id="yui_3_16_0_1_1438184102968_10604"><br></div><div id="yui_3_16_0_1_1438184102968_10605">Mason Wheeler<br></div></div></body></html>