On Tue, 2024-03-12 at 17:19 +0100, Jakub Jelinek wrote:
> On Thu, Feb 15, 2024 at 10:53:08PM +0000, Sam James wrote:
> > With _FORTIFY_SOURCE >= 2 (enabled by -fhardened), vfprintf-chk-1.c's
> > __vfprintf_chk ends up calling __vprintf_chk rather than vprintf.
Do we really want to support adding random CFLAGS running the test
suite? AFAIK adding random CFLAGS will just cause test failures here or
there. We are adjusting the test suite for -fPIE -pie and -fstack-
protector-strong but it's because they can be implicitly enabled with --
enable-default-* options, and we don't have --enable-default-hardened as
at now.
If we need to bootstrap a hardened GCC and test it, pass -fhardened as
how "info gccinstall" suggests:
make BOOT_CFLAGS="-O2 -g -fhardened"
instead of
env C{,XX}FLAGS="-O2 -g -fhardened" /path/to/gcc/configure ...
which will taint the test suite with -fhardened.
--
Xi Ruoyao <xry...@xry111.site>
School of Aerospace Science and Technology, Xidian University
