config.gcc has cases for a number of configurations that do not build at all. I've constructed a list of 215 targets to get reasonable coverage of the cases in config.gcc, and found that one of these would not configure, and a further 36 would not build.
I know Jeff Law does config-list.mk builds sometimes and Joseph Myers tests a wide range of configurations with his build-many-glibcs.py script; cc-ing them to see if they've noticed any additional broken configurations.
Actually, it's not config-list.ml, though I did use that to help generate the list of targets I am testing. None of them ones I'm testing would fall into the category as a "broken configuration".
(In reply to Jeffrey A. Law from comment #2) > Actually, it's not config-list.ml, though I did use that to help generate > the list of targets I am testing. None of them ones I'm testing would fall > into the category as a "broken configuration". Do you test with --enable-werror-always at all? Asking because bug 44756 is the last bug open blocking this meta-bug.
No, I do not use -enable-werror-always. I try to do as little as possible to change the standard configuration.