Hi all!

Currently LDC can be compiled with LLVM 3.1-3.6 with support for LLVM trunk constantly added.

Because the LLVM API is not stable this broad support becomes more and more a burden. It is also likely that this set of LLVM libraries will not be supported by the new Travis container (which I like to use because of more RAM and CPU cores).

Versions 3.1, 3.2 and 3.3 have serious bugs which forces us to disable optimizations for some tests. Especially 3.3 is unusable with OS X!

Therefore I like to know which LLVM version do you use with LDC.

If no one objects then the plan would be that the next major release is the last one which can be compiled with LLVM 3.1-3.4.

Please give feedback!

Regards,
Kai

3.5.1

On Friday, 10 April 2015 at 05:56:36 UTC, Kai Nacke wrote:
> Hi all!
>
> Currently LDC can be compiled with LLVM 3.1-3.6 with support for LLVM trunk constantly added.
>
> Because the LLVM API is not stable this broad support becomes more and more a burden. It is also likely that this set of LLVM libraries will not be supported by the new Travis container (which I like to use because of more RAM and CPU cores).
>
> Versions 3.1, 3.2 and 3.3 have serious bugs which forces us to disable optimizations for some tests. Especially 3.3 is unusable with OS X!
>
> Therefore I like to know which LLVM version do you use with LDC.
>
> If no one objects then the plan would be that the next major release is the last one which can be compiled with LLVM 3.1-3.4.
>
> Please give feedback!
>
> Regards,
> Kai

Yes, please do! Personally I only use 3.6+ but 3.5 is a reasonable level, I have been meaning to suggest the same.

Considering llvm project is very refactoring happy, any new code I tried to write for ldc quickly degraded into ifdef hell, actually to the point where I lost motivation to contribute at all, my respects that you have managed this long.

If we jump to 3.5 I might give it another whirl. :)

openSUSE 13.1 (the previous release) comes with LLVM 3.4, but 13.2 (the current one) has LLVM 3.5.

I'm providing packages [1] for 13.1, but they were only accepted into the semi-official devel:languages:D two months ago; I guess not many people are using it. So it's fine with me.

https://build.opensuse.org/package/show?project=devel%3Alanguages%3AD&package=ldc

On Friday, 10 April 2015 at 05:56:36 UTC, Kai Nacke wrote:
> Hi all!
>
> Currently LDC can be compiled with LLVM 3.1-3.6 with support for LLVM trunk constantly added.
>
> Because the LLVM API is not stable this broad support becomes more and more a burden. It is also likely that this set of LLVM libraries will not be supported by the new Travis container (which I like to use because of more RAM and CPU cores).
>
> Versions 3.1, 3.2 and 3.3 have serious bugs which forces us to disable optimizations for some tests. Especially 3.3 is unusable with OS X!
>
> Therefore I like to know which LLVM version do you use with LDC.
>
> If no one objects then the plan would be that the next major release is the last one which can be compiled with LLVM 3.1-3.4.
>
> Please give feedback!
>
> Regards,
> Kai

OK by me. It's not like building LLVM is particularly tricky anyway.

Why drop 3.4?

Actually last stable release doesn't compile with 3.6, only with 3.5 (caught me by surprise when I was rebuilding Arch packages last time as they have already moved to 3.6 as default)

I am using LLVM 3.6 and trunk (I build LLVM myself).
The only reason I have builds for 3.4 and 3.5 is to fix backwards compatibility issues...

On Friday, 10 April 2015 at 05:56:36 UTC, Kai Nacke wrote:
>
> Because the LLVM API is not stable this broad support becomes more and more a burden. It is also likely that this set of LLVM libraries will not be supported by the new Travis container (which I like to use because of more RAM and CPU cores).

Is anyone actively working on having green Travis build for LLVM 3.6+ ?

On 04/10/2015 07:56 AM, Kai Nacke via digitalmars-d-ldc wrote:
> If no one objects then the plan would be that the next major release is
> the last one which can be compiled with LLVM 3.1-3.4.

As the one who instigated this, I obviously agree.

One thing to keep in mind is that supporting old version requires quite a bit of effort on our side too, and arguably for no good reason. You can always build a local copy LLVM as part of the LDC build process which you don't even need to keep around after linking the LDC executable (if you use static linking).  In fact, this is exactly how the LDC release packages are built.

 — David

I use 3.5.0.

-- 
Marco

3.5.1 here.