Ehem, ARM

[Joakim]

On Friday, 15 November 2013 at 18:44:20 UTC, Iain Buclaw wrote:
> On 15 November 2013 18:40, Joakim <joakim at airpost.net> wrote:
>> Yes, I thought that would be easier, to split the effort into 
>> two parts.
>>  First, get D working on Android/x86, then, linux/ARM.  Some 
>> fine day, we
>> combine the two into Android/ARM. :)
>>
> GNU/Linux on ARM will come first... it's now only a matter of 
> time. ;)

Everything is "only a matter of time." ;) The order is not 
important; it'd be great if linux/ARM is done first, though I 
hope gdc isn't the only one that does it.

On Friday, 15 November 2013 at 19:09:24 UTC, Johannes Pfau wrote:
> There are 3 main points which need to be addressed for a solid 
> Android
> port:
>
> * Druntime must be ported to bionic. Not difficult, but 
> annoying as
>   bionic is a mixture between bsd and posix code, so you'll 
> have to
>   edit many version statements. All compilers will benefit from 
> that.
Yep, this is the part I'm taking a stab at.

> * You need to implement TLS support. Last time I checked there 
> bionic
>   didn't support native TLS and gcc's emulated TLS   doesn't 
> work with
>   the D GC.
I think there's TLS support in bionic now, but not with the 
__thread keyword.  I'll look into it more as I go.

> * The main program in Android should always be java code, 
> native code
>   loaded as shared libraries. This is implemented in DMD now, 
> but not
>   in GDC. (And IIRC not in LDC either?)
I just want to get it working as a pure native compilation option 
for now.  Perhaps someone else will tie D into JNI and get it 
working with Dalvik, I'm not interested in that.

Thanks for the info.