https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119832
--- Comment #4 from Li Pan <pan2.li at intel dot com> --- (In reply to Kito Cheng from comment #1) > Created attachment 61135 [details] > 0001-RISC-V-Implement-TARGET_MODE_CONFLUENCE.patch > > My working patch for this bug I think TARGET_MODE_CONFLUENCE should be a better place for this issue, which is somehow designed for non-exclusive modes, quote from doc. "some entities might have overlapping, non-exclusive modes, so that it is sometimes possible to represent “mode mode1 or mode mode2” with something more specifi c than “mode not known”." CC Richard S in case my understanding is incorrect. To double confirm, is it a mis-optimized issue instead of correctness?