https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #4 from Vittorio Zecca ---
(In reply to Jerry DeLisle from comment #3)
> Initially it is creating the very large string in the frontend passes and
> then via resolution and translation phases, and finally into the middle-end
> and bac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #3 from Jerry DeLisle ---
Initially it is creating the very large string in the frontend passes and then
via resolution and translation phases, and finally into the middle-end and back
end phases where it I am guessing the optimizers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #2 from Vittorio Zecca ---
I am sorry I should have taken more time analyzing this issue.
Actually it is not and infinite loop, I clocked the compilation first
with the -S option,
then with the -c option.
The compiler takes 4'52" of r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
