Date: Thu, 21 Feb 2019 22:54:20 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 215798] clang: please Include thread sanitizer (and all other available sanitizers) Message-ID: <bug-215798-29464-OC7wk7gGGz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215798-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-215798-29464@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=3D215798 --- Comment #6 from Sean McBride <sean@rogue-research.com> --- And just today on the clang mailing list: http://lists.llvm.org/pipermail/cfe-dev/2019-February/061374.html "I think the release is looking pretty good, but there is one blocker that's worrying me: https://llvm.org/PR40761 >From what I understand, ASan et al. used to work on FreeBSD but don't anymore, and there's nobody working on it. Is there someone who has access to a FreeBSD machine that could help investigate this? Just getting it bisected would be super helpful." --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215798-29464-OC7wk7gGGz>