Arch Linux

The compiler on Arch Linux always builds with -fstack-protector, even when -ffreestanding is passed.  However, when -fnostdlib is passed at link time (which is normally the case when building with -ffreestanding), it is not linked with the stack-protector library.  This leads to a link time error:
/usr/bin/ld: x86/realmode.o: in function `print_serial_u32':
.../x86/realmode.c:104: undefined reference to `__stack_chk_fail'

What was observed in a working build on Ubuntu was that there were the same link time (link_ssp) SSP conditions in the spec.  However for compiler spec options, the following additional item was present. 
*ssp_default:
%{!fno-stack-protector:%{!fstack-protector-all:%{!ffreestanding:%{!nostdlib:%{!fstack-protector:-fstack-protector-strong}}}}} %{!Wformat:%{!Wformat=2:%{!Wformat=0:%{!Wall:-Wform
at} %{!Wno-format-security:-Wformat-security}}}}

We believe that a GCC build when "--enable-default-ssp" adds the "ssp_default" to the spec. Does Arch use that option or a custom patch to set the stack protector flags?

Additional info:
* package version(s)
gcc 9.2.0

Steps to reproduce:
1) git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
2) cd kvm-unit-tests ; make

That example compiles an application with the -ffreestanding compile flag and links it with -nostdlib set.  This should normally bypass the stack protector default (RHEL / Ubuntu / Debian)