https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #86 from The Written Word <bugzilla-gcc at thewrittenword dot com> --- (In reply to C. Heide from comment #79) > (In reply to The Written Word from comment #75) > > > > I think a local patch might be doing this. Rebuild without it. > > I did have some other patches applied from other PRs, from previous > desperate attempts to get anything working, including PR90714, PR85412, > PR87338, and tips from PR64919. > > I'm doing some more testing with combinations of them, and so far I've found > that if I start from a fresh 8.3 and apply only the essential ones, the fix > here, the operand64 removal, the nftw workaround, and -O1 to work around the > stage 2 ICE, I don't get the duplicate symbols but the compiler segfaults in > libgcc configure tests in stage 2. > > If I add the '#undef MAKE_DECL_ONE_ONLY' fix from PR64919 (is it even still > relevant? It does seem to be for the stage 2 libgcc segfault symptom I > see.), I start getting the duplicate symbols in stage 1 libstdc++. Yeah, we had PR64919 applied and backed out only the "#undef MAKE_DECL_ONE_ONLY" to work around the duplicate symbols error. We also have fixes for PR60465, PR64919, PR66319, PR85412, PR87338, PR90714, r214747, and Debian's ia64-disable-selective-scheduling.patch applied, in addition to some local -O2=>-O0 workarounds.
