With a decision or 2 inside it?
Single point of exit either requires numerous flag variables that have nothing to do with the program logic - they are there as an artifact of the language itself. Additional tests at each loop level to determine whether you broke out of the loop via a decision in the loop or a loop fall out.
Or, shudder - goto - that bounces you to the bottom.
Or, my favorite solution, named loops and a "last NAME;" statement, which allows a clean breaking out of nested loops.
Whether or not you have a problem with this is not the issue. I've seen a far better way and now know better. Far less code, much cleaner and easier to code and maintain.