https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91254
Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- [apinski@xeond2 upstream-cross-aarch64]$ time ./a.out 100 Numero de casas: 100 3.14159265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706 real 0m0.732s user 0m0.730s sys 0m0.001s [apinski@xeond2 upstream-cross-aarch64]$ time ./a.out 200 Numero de casas: 200 3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819 real 0m5.842s user 0m5.833s sys 0m0.001s [apinski@xeond2 upstream-cross-aarch64]$ time ./a.out 300 Numero de casas: 300 3.14159265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316527120190914564856692346034861045432664821339360726024914127 real 0m19.778s user 0m19.753s sys 0m0.001s so 300 for me takes 19 seconds while 200 takes 5/6 seconds. This means 1000 will take over an hour. This is on a fast machine too. So there is no issue with GCC here.