https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120935
--- Comment #12 from pietro <pietro at sociotechnical dot xyz> --- (In reply to Hans-Peter Nilsson from comment #11) > (In reply to pietro from comment #10) > > Since there's a workaround in place for 15.2 should we change the Target > > Milestone to 16.1? > > Then why not 16.0? (Honest question: I don't understand the nuances of that > field, in particular when the bug doesn't actually manifest anymore.) I > changed it tentatively. AIUI the first release of GCC version X is X.1, there was no 15.0 release: https://gcc.gnu.org/releases.html#timeline Since there's a workaround for 15.2 I thought setting the target to 16.1 makes it clear the patch is only targeting the main branch. > Come to think of it, if you're certain that mips64-elf exhibits this > problem, perhaps the target field and description should change? You have a better grasp on the actual issue than I do. Feel free to change the description and mark PR120144 as a duplicate of this one. > But then for mips64-elf there's no workaround in place.
