https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88011
--- Comment #4 from boger at gcc dot gnu.org --- Created attachment 45005 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45005&action=edit Hack workaround to show bad loop Through my debugging I found that if I add the print statement as shown in this patch in math/big/int.go function lehmerGCD then the bugs in the tests for the math/big and crypto packages go away. I realize this is not a valid workaround but should show what loop contains the bad code.
