https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117970
--- Comment #4 from Edwin Lu <ewlu at rivosinc dot com> --- (In reply to Lewis Hyatt from comment #2) > Thanks, I will see what I can find. Did you, by any chance, run the tests > before/after r15-6016 in the same build directory? I think this error would > make sense to me, if a module created with the old gcc is being read by the > new one, and some logic is missing to be sure not to read the old one, but > that's just a quick guess. We built and ran the tests in a clean build environment with r15-6016-gd9cdc500c1e as the current gcc hash. After stage1 is built, it compiles newlib and stage2. I'm not sure if that answers your question?
