@jpf91 
> Nope, dmd needs work on ARM. Everything which was portable between compilers has been published to the standard druntime repo. But as long as DMD doesn't have an inline assembler for ARM there's stuff that you simply can't implement. That's not an issue with druntime, it's just a result of the standard druntime being tied to dmd.

All that can be versioned out and used by ldc also.  As long as it isn't in the official druntime, my point is that I wasn't sure what ARM port he was referring to.

@ibuclaw 
> And I'm advising you the real fixes.

Telling me not to take it out is not the real fix.  Where we discussed the underlying issues and what the real fix might be, that's the point of slapping the pull up early.

> But really, you should only raise a PR when you feel it's ready for actual review.

Sometimes it's useful to slap up an unfinished pull to get input on how to proceed, especially if it's clearly stated to be unfinished.  Given the wide variety of the 13 modules that didn't fully pass the tests, I wanted any input I could get on this early iteration of an Android/x86 pull, plus it's as good a place as any to slap the patch up for others to use if they want to pitch in on fixing them.