www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ldc - LDC-LTS and debuginfo

reply Johan Engelen <j j.nl> writes:
debuginfo is broken in LTS and it breaks the build with LLVM 5.0. 
I am backporting some fixes but... should I spend time on this?
Why don't we just kill debuginfo, or at least remove it from the 
LTS runtime build?
That way we'd get slightly faster bootstrapping, and we will no 
longer have to maintain debuginfo (that file with all the #ifdef 
in it ... ).

- Johan
Sep 18
parent reply "David Nadlinger" <code klickverbot.at> writes:
On 18 Sep 2017, at 21:11, Johan Engelen via digitalmars-d-ldc wrote:
 debuginfo is broken in LTS and it breaks the build with LLVM 5.0. I am 
 backporting some fixes but... should I spend time on this?
 Why don't we just kill debuginfo, or at least remove it from the LTS 
 runtime build?
Hmm… It is still useful for bringing up new platforms when starting from C++ (e.g. if cross-compiling is messy), so I don't have a strong opinion either way. Just be sure to actually kill it (make -g a no-op apart from printing a warning) to avoid confusion if you decide against keeping it. — David
Sep 18
parent Johan Engelen <j j.nl> writes:
On Monday, 18 September 2017 at 20:19:03 UTC, David Nadlinger 
wrote:
 On 18 Sep 2017, at 21:11, Johan Engelen via digitalmars-d-ldc 
 wrote:
 debuginfo is broken in LTS and it breaks the build with LLVM 
 5.0. I am backporting some fixes but... should I spend time on 
 this?
 Why don't we just kill debuginfo, or at least remove it from 
 the LTS runtime build?
Hmm… It is still useful for bringing up new platforms when starting from C++ (e.g. if cross-compiling is messy), so I don't have a strong opinion either way.
https://github.com/ldc-developers/ldc/pull/2334 Hope that works. It works on my Mac. -Johan
Sep 18