https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89530
--- Comment #2 from dcci <dccitaliano at gmail dot com> --- Thanks Jakub. We're trying to report more of these but it's hard to filter out duplicates. A possible way we thought was that of stopping at some point in the pipeline (so running a subset of the optimizations), to identify where this broke. (something like https://llvm.org/docs/OptBisect.html). Is there any easy way of doing this in GCC? I skimmed through the docs and haven't found any.
