https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125182
--- Comment #8 from Mark Millard <markmigm at gmail dot com> --- A note on the FreeBSD explorations on the issue that are visible in the FreeBSD port's 294062 bugzilla-entry. : Not knowing what gcc16+ would do for the overall issue, reverting to what is basically the historical technique for lang/gcc15 and before is what has been explored relative to checking build-ability. That included reverting the relevant aarch64 cpuinfo.c code structure to the old style. With that I was able to build --and so know that no other issues prevented building. But it does not necessarily make for the way gcc would want to handle the issues associated with aarch64's cpuinfo.c for gcc16 or later long term. It is just a workaround for now as far as I'm concerned. (But I do not maintain any lang/gcc* ports or devel/freebsd-gcc* ports.)
