Test results for D on Android/ARM

[Dan Olson via digitalmars-d-ldc]

Joakim <dlang at joakim.fea.st> writes:
>
>> I'm bringing this up now because the upcoming 2.069 merge (with the
>> move to the D frontend) has the potential to be quite disruptive to
>> long-term projects like yours, and I want to be sure things do no
>> grind to a halt because of that.
>
> Why do you say that: do you expect it to take a while to get the 2.069
> release of ldc done?  Since I'm providing ldc as a cross-compiler, I
> don't see how it would affect the linux/x86 or linux/x64 host
> compiler.  It might affect the native Android/ARM host compiler, but
> I'm optimistic that that won't take much.
>
> If you simply mean that merging might take a while after switching the
> ldc frontend to D, as my patches are against the current C++ version
> of ldc, my patches to the ldc compiler itself are fairly minimal. The
> vast majority is Kai's longdouble2 branch, which is only necessary
> when cross-compiling, and I suspect we could translate it fairly
> quickly if needed.

I think David did mean that your Android changes might get messed up by
the update to D frontend 2.069.  I agree that Kai's longdouble2 branch
could be the most work, but it is pretty straight forward and might be
easier to just reimplement as LDC starts using 2.069 D frontend.
-- 
Dan