https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117600
--- Comment #7 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Richard Earnshaw from comment #6) > libgcc is always built with the target compiler. --disable-werror is > intended to allow compliers other than the one being built to work when they > generate warnings based on different algorithms. No, -Werror can be problematic even for the same compiler. If someone commits a change that only shows a warning on a single target, I'll report it, but I don't want it to block my build. I'll note that again that libgcc for arm here is the odd one out. > It would be inappropriate to cross-link the two issues under the same > configure flag. I don't see how. Are you suggesting PR121397 merits a --disable-target-werror?
