Date: Mon, 20 May 2024 17:45:04 +0000 From: Paul Floyd <paulf2718@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Initial implementation of _FORTIFY_SOURCE Message-ID: <f7acf705-b042-4ddf-ae5c-fd3ae2463a73@gmail.com> In-Reply-To: <f8000e6b-226b-45f3-a751-aca790f4f8c8@FreeBSD.org> References: <f8000e6b-226b-45f3-a751-aca790f4f8c8@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13-05-24 17:47, Kyle Evans wrote: > Hi, > Please test _FORTIFY_SOURCE out now by setting FORTIFY_SOURCE=2 in the > buildworld env -- I intend to flip the default to 2 when WITH_SSP is set > in the next month if nobody complains about serious breakage. I've > personally been rolling with FORTIFY_SOURCE=2 for the last three years > that this has been sitting in a local branch, so I don't really > anticipate any super-fundamental breakage. Hi Kyle I just tried c7581d76a1e46a925bba59d3e18394908f65c907 No issues on arm64 other than the usual -CURRENT noise which has nothing to do with FORTIFY_SOURCE. A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f7acf705-b042-4ddf-ae5c-fd3ae2463a73>