Date: Fri, 20 Oct 2023 12:35:08 -0400 From: Ed Maste <emaste@freebsd.org> To: Mark Johnston <markj@freebsd.org> Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: b6c653c97463 - main - kmsan: Set -fno-sanitize-memory-param-retval for now Message-ID: <CAPyFy2Dnx9sCHyytPOhFmZSbg0Ld5tQvQ0m69tdRnj6r_n3dYw@mail.gmail.com> In-Reply-To: <202310171337.39HDb4Xp095686@gitrepo.freebsd.org> References: <202310171337.39HDb4Xp095686@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Oct 2023 at 09:37, Mark Johnston <markj@freebsd.org> wrote: > > commit b6c653c9746342b373af01979319b3cb123b2872 > Author: Mark Johnston <markj@FreeBSD.org> > AuthorDate: 2023-10-16 19:45:42 +0000 > Commit: Mark Johnston <markj@FreeBSD.org> > CommitDate: 2023-10-17 13:05:45 +0000 > > kmsan: Set -fno-sanitize-memory-param-retval for now > > As of LLVM 16, -fsanitize-memory-param-retval is the default. It yields > significantly smaller code, but the KMSAN runtime interceptors need to > be updated to stop checking shadow state of parameters. Apply a minimal > workaround for now. What could we do to be more proactive in finding this kind of issue? Is it just a consequence of our (current lack of) LLVM FreeBSD CI/testing infrastructure?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2Dnx9sCHyytPOhFmZSbg0Ld5tQvQ0m69tdRnj6r_n3dYw>