[Bug libitm/66453] In a deadlock libitm allocates all available RAM until oom is called

[torvald at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66453

torvald at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |torvald at gcc dot gnu.org

--- Comment #1 from torvald at gcc dot gnu.org ---
Created attachment 36848
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36848&action=edit
test case of original bug report

I can't reproduce this with the attached test case with current trunl.  The
only difference to your test case is that the non-synchronization while loop is
technically undefined behavior, and to try to prevent this, I added the hack
that prevents the loop from being optimized out.  Please test again, and reopen
the bug if you still see the OOM situation, ideally with more data on your test
environment.