https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90310
--- Comment #7 from Zdenek Sojka <zsojka at seznam dot cz> --- (In reply to Eric Botcazou from comment #6) > > Sure; how do I detect if it is a duplicate? > > Look at the different PRs, both the code, the options and the target. Isn't > there an obviously redundant trend? What is obvious to you, is not obvious to me. Most of the bug reports I create look quite similar (both testcases and compiler flags; eg. -fno-forward-propagate, -fno-dce, -fno-tree-dce and some other flags are very common in the bugreports). I already filter out about 1/2 of wrong-code testcases because they look too similiar to me. If I am unsure, I link the other bug report as in #c0 "Might be related to PR89795." Sometimes it is a dup, sometimes not. I have stopped testing this target, until PR89795 is fixed. I can also generally stop testing this target (as I did for sparc) if you think the bugreports are meaningless, as they generally contain several -fno-* compiler switches.
