Master is now at frontend level 2.069.2

[Joakim via digitalmars-d-ldc]

On Thursday, 25 February 2016 at 19:19:53 UTC, David Nadlinger 
wrote:
> Hi Joakim,
>
> On 25 Feb 2016, at 20:06, Joakim via digitalmars-d-ldc wrote:
>> I've been trying out the new merge branches on Arch 
>> linux/x86_64 today.
>
> Thanks for testing!
>
>> The master branch and merge-2.069
>
> Just to make sure there are no misunderstandings, merge-2.069 
> does not exist in the upstream repo anymore, following the 
> merge.

OK, it still shows up in my local list of remote branches.  I 
guess git pull won't update the list and I have to prune such 
deleted remote branches myself occasionally, using a command like 
"git remote update origin --prune," which I just found through 
google.

>> I haven't seen linux/x64 results mentioned and I don't think 
>> it's tested on the auto-tester: anyone else getting the same 
>> results?
>
> All the builds on Travis are 64 bit, except for the one 
> multilib configuration. As such, it's quite weird that you are 
> seeing this failures. Which master commit in particular are you 
> testing, and which LLVM version are you building against?

Looks like I was wrong about using merge-2.069, even though that 
branch was available in my local list, I used release-1.0.0 
instead because I noticed it had much more recent commits.  Here 
are the ldc commits used, all are stock with no local changes:

master - 8bf013
release-1.0.0 - most likely 2d82da
merge-2.070 - 6b000f

I'm using dmd 2.070.0 to build the ddmd frontend and 
clang/clang++ to build the ldc glue layer.