https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125947
--- Comment #3 from Drea Pinski <pinskia at gcc dot gnu.org> --- (In reply to Dhruv Chawla from comment #2) > Very interesting, thanks a lot for the explanation! 2 is quite the arbitrary > constant to have for something like this :-) It dates even before my time working on GCC. I suspect it was there so reload would not go into an infinite loop. That is the same class to its same class would not cause reload to check the constraints and then reload and then reload again and again if the constraints are broken on the move.
