Date: Mon, 08 Jan 2018 14:37:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224669] [exp-run] Against projects/clang600-import branch Message-ID: <bug-224669-13-I2whhBTTay@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224669-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224669-13@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=3D224669 --- Comment #24 from Ed Maste <emaste@freebsd.org> --- (In reply to Jan Beich from comment #23) > When do you plan to merge the branch? Maybe rc1 (circa January 17) is a g= ood > time. Not to rush but C++11 bustage is going to haunt us for months, anyw= ay. I think it's reasonable to do this soon. There is work in progress to intro= duce separate user/kernel page tables for Intel "meltdown" mitigation and I don't want to do anything that might conflict or hold that up, but I do not belie= ve there are any kernel-related issues in the branch. On the other hand, for other mitigations there are fixes in lld for functionality we're going to use, as well as the retpoline work ongoing for Clang/LLVM. Having 6.0 in HEAD might help in both testing and deploying this work. > Cons: > - may spoil other base exp-runs (like bug 214864) until more ports are fi= xed I'd be happy to move the lld-is-ld exp-run to using lld 6.0; lld in FreeBSD-HEAD is very close to usable and I think krion@ has addressed about= as much in the ports tree as we're able to. That is, I think 214864 has just a= bout served its purpose already, and getting coverage on lld 6 gives us useful n= ew information. --=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-224669-13-I2whhBTTay>