Date: Sat, 26 Jan 2019 21:37:15 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 235215] Bump LLVM_DEFAULT to 80 Message-ID: <bug-235215-21738-T2LvwqscwW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235215-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-235215-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235215 --- Comment #5 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Yuri Victorovich from comment #2) > the latest LLVM release is 7.0.1, so this PR is premature. I'm trying to get everyone on board (or off board) by the time devel/llvm80= is updated to the actual release. Some maintainers may need time to evaluate t= he risk but being on LLVM_DEFAULT train assumes silence after timeout is an agreement. Otherwise, there's a risk of HEAD and 2019Q2 ending up with different LLVM_DEFAULT, complicating maintenance. (In reply to Yuri Victorovich from comment #3) > ikos says that they will fix compatibility once llvm-8 is released. Not quite. According to https://github.com/NASA-SW-VnV/ikos/issues/96#issuecomment-457843971 it doe= sn't look like ikos upstream plans to keep compatibility with llvm70 much like t= hey haven't with llvm60 or llvm50/llvm40. So, I don't understand why you insist= on using LLVM_DEFAULT in the port when it breaks if user specifies non-default value via DEFAULT_VERSIONS+=3Dllvm=3DNN. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235215-21738-T2LvwqscwW>