https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Thanks Mark. What architecture are you on? When I do those steps, there's a long wait and then in terminates with no analyzer output. If I add -Wanalyzer-too-complex I see lots of warnings about "terminating analysis for this program point". What do you see if you add -Wanalyzer-too-complex? If you do, my guess as to what's happening is that there's a "random" factor in how the worklist is being explored, and that on my machine it's hitting the complexity limits before finding the issue, and on your machine it's finding the issue first. Perhaps it relates to pointer addresses; PR 96608 notes some places where hash values could vary between runs, and that could be enough to throw out the worklist traversal order.
