On 15 December 2017 at 15:13, Matthias Klumpp <m...@debian.org> wrote: > 2017-12-15 15:05 GMT+01:00 Matthias Klose <d...@debian.org>: >> Control: reopen -1 >> Control: reassign -1 ldc >> >> On 15.12.2017 13:53, Matthias Klumpp wrote: >>> 2017-12-15 9:46 GMT+01:00 Matthias Klose <d...@debian.org>: >>>> [...] >> >> ok, but then the issue is in ldc, so you should change the default over >> there, >> like it's done by every other compiler in the distro. > > That's fair enough - the default wasn't changed because upstream > didn't want user-compiled code to run slower on their machine, and > Markos, the LDC maintainer, also didn't like this at all. > Therefore, we change this for Debian packaging only now, as some kind > of compromise. > > In any case, that's indeed something to be addressed by the LDC > package, so it makes sense to have the issue report there. >
I checked this with LDC devs. They claimed that the neon baseline was coming from LLVM, and that it's that package which should be fixed to not default to it. The baseline CPU could always be set in ldc2.conf if you really want it fixed in LDC. That is at least what I understood from the conversation. Regards Iain.
