https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119521
--- Comment #8 from Simon Sobisch <simonsobisch at gnu dot org> --- Hm, sounds like an internal stack check or similar would be good here to circumvent this issue from another side... If it doesn't work then it would definitely better for gcc to abort compiling this code for now instead of producing something that is known to internally produce a loop. Maybe you want to mark this bug as fixed and create another one about this specific issue and/or DECLARATIVES in general?
