Date: Tue, 03 Sep 2019 14:07:23 -0000 From: John Baldwin <jhb@FreeBSD.org> To: Enji Cooper <ngie@FreeBSD.org>, src-committers@freebsd.org, svn-src-projects@freebsd.org Subject: Re: svn commit: r346492 - projects/runtime-coverage-v2/lib/libclang_rt Message-ID: <e1229f59-ab16-b995-b645-afd1b89bf925@FreeBSD.org> In-Reply-To: <201904211926.x3LJQeg2024873@repo.freebsd.org> References: <201904211926.x3LJQeg2024873@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/21/19 12:26 PM, Enji Cooper wrote: > Author: ngie > Date: Sun Apr 21 19:26:40 2019 > New Revision: 346492 > URL: https://svnweb.freebsd.org/changeset/base/346492 > > Log: > Build libclang_rt/profile on all clang-supported architectures > > There's no reason why a special case needs to be added specifically for amd64, > arm, and i386, as the code is written in machine architecture agnostic C/C++. > > There might be compilation/link time issues, but we'll find out soon. For a sanitizer to be useful, you need to make sure clang's FreeBSD driver will actually use it. clang has builtin knowledge about which sanitizers work on which architectures. Just building the library alone doesn't enable it unless you also check the driver in clang. I haven't looked to see what conditions clang places on the profile case, but I am familiar with this from working on ASAN support for mips. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1229f59-ab16-b995-b645-afd1b89bf925>