http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58996
--- Comment #17 from Jeffrey A. Law <law at redhat dot com> --- If there's an interest, I could probably create a kickstart for a RHL8 VM suitable for building GCC 4.9. But it's a 10+ year old platform of marginal value at best. I'd be much more concerned about using cpu_set_t instead of the dynamically sizing variants. As Jakub noted cpu_set_t doesn't work with > 1024 processors and it's been the source of some cross-distro problems as well. If at all possible we need to be moving away from using cpu_set_t to the newer APIs. My recommendation would be to address the RHL8 problem (no cpu_set_t at all) as efficiently as possible without burning huge amount of time on it. Then a separate BZ to track issues around moving away from cpu_set_t to the more modern interfaces.
