From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8F9783858D35; Wed, 3 Nov 2021 17:35:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F9783858D35 From: "hjl.tools at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103066] New: __sync_val_compare_and_swap/__sync_bool_compare_and_swap aren't optimized Date: Wed, 03 Nov 2021 17:35:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc blocked target_milestone cf_gcctarget Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2021 17:35:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103066 Bug ID: 103066 Summary: __sync_val_compare_and_swap/__sync_bool_compare_and_sw ap aren't optimized Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com CC: crazylht at gmail dot com, wwwhhhyyy333 at gmail dot com Blocks: 103065 Target Milestone: --- Target: i386,x86-64 >>From the CPU's point of view, getting a cache line for writing is more expensive than reading. See Appendix A.2 Spinlock in: https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/x= eon-lock-scaling-analysis-paper.pdf The full compare and swap will grab the cache line exclusive and causes excessive cache line bouncing. [hjl@gnu-cfl-1 tmp]$ cat x.c extern int m; int test(int oldv, int newv) { return __sync_val_compare_and_swap (&m, oldv, newv); } [hjl@gnu-cfl-1 tmp]$ gcc -S -O2 x.c [hjl@gnu-cfl-1 tmp]$ cat x.s .file "x.c" .text .p2align 4 .globl test .type test, @function test: .LFB0: .cfi_startproc movl %edi, %eax lock cmpxchgl %esi, m(%rip) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ GCC should first emit a normal load, check and return immediately if cmpxch= gl may fail. ret .cfi_endproc .LFE0: .size test, .-test .ident "GCC: (GNU) 11.2.1 20211019 (Red Hat 11.2.1-6)" .section .note.GNU-stack,"",@progbits [hjl@gnu-cfl-1 tmp]$ Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103065 [Bug 103065] [meta] atomic operations aren't optimized=