Test results for D on Android/ARM
Joakim via digitalmars-d-ldc
digitalmars-d-ldc at puremagic.com
Mon Jan 18 06:09:00 PST 2016
On Monday, 18 January 2016 at 09:32:06 UTC, David Nadlinger wrote:
> Hi Joakim,
> On 17 Jan 2016, at 12:24, Joakim via digitalmars-d-ldc wrote:
>> I've released updated test runners on github:
> I don't have much to contribute right now but thank you for
> keeping us updated on the progress. We should probably figure
> out how to go forward with integrating this into mainline LDC
> soon (how do the upstream LLVM TLS support additions affect
> this, by the way?).
Yes, I wanted to polish off some of these remaining rough edges
before submitting PRs. I will do that next, as there's only a
couple failing tests left and they don't bother me.
As for "the upstream LLVM TLS support additions," I assume you're
talking about the recent support for emulated TLS added to llvm
3.8, that mimics the way gcc does it. I tried it out a while
back, works fine, except I'll need to figure out how to register
that TLS data with the GC, as Johannes had to do for gcc. I
haven't looked into that last GC portion yet.
> 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.
Long answer short: I don't expect the 2.069 merge to affect the
Android port much, but I'll try to get some PRs in before then
More information about the digitalmars-d-ldc