https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #8 from AlphaOmegaProgrammer ---
> So what about this untested patch?
I've spent about an hour trying to find flaws in the idea, and I can't think of
any. I applied the patch and it fixed the deadlock for me in my test code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #5 from AlphaOmegaProgrammer ---
> Please see https://gcc.gnu.org/contribute.html for how to contribute, which
> includes sending a real patch
My apologies, this is my first time trying to contribute. I'll do this.
> This can only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #2 from AlphaOmegaProgrammer ---
Created attachment 61109
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61109&action=edit
Proposed Patch
This is my proposed patch. I've tested it and my test case no longer deadlocks,
and none
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
--- Comment #1 from AlphaOmegaProgrammer ---
Created attachment 61108
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61108&action=edit
Current implementation of locking algorithm
This file can be found at /libatomic/config/posix/lock.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119796
Bug ID: 119796
Summary: Atomic Operations Can Deadlock Without Hardware
Support
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116900
--- Comment #2 from alpha.and.omega.programmer ---
Created attachment 59232
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59232&action=edit
gcc -v -save-temps .i file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116900
--- Comment #1 from alpha.and.omega.programmer ---
Created attachment 59231
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59231&action=edit
gcc -v
Output of gcc -v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116900
Bug ID: 116900
Summary: False Positive Use After Free Warning
Product: gcc
Version: 14.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
