From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 09205397248A; Fri, 19 Jun 2020 09:14:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 09205397248A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1592558042;
 bh=tR60+WONr73O7WNDQa+1y7+pquza5FJcWrWxBD89PkE=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=PbZgOBIo9eNncAd+5vuP5M6pdZWIOnUfwZ7eoXVB9JyyzhdniHYyUlKCAt0I9vmHu
 zGe+Hz9a6muL/bfE2B0rp6JHXatNVAQ039lfKVTLqFHDWOHRycacnxSnRZRSzpsGEV
 G92ypvCu29jvlJ6oDqZ/mjDxuXmYA1x5bU2FRl08=
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95750] [x86] Use dummy atomic insn instead of mfence in
 __atomic_thread_fence(seq_cst)
Date: Fri, 19 Jun 2020 09:14:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak 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: 
Message-ID: <bug-95750-4-ZdLyxtyGc7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95750-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2020 09:14:02 -0000

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

--- Comment #7 from Uro=C5=A1 Bizjak <ubizjak at gmail dot com> ---
Actually, x86_64 (at least my Fedora 32) does not like operations on stack:

Starting program: /sdd/uros/git/gcc/gcc/testsuite/gcc.dg/atomic/a.out=20

Program received signal SIGSEGV, Segmentation fault.
0x000000000040110a in main ()
(gdb) disass
Dump of assembler code for function main:
   0x0000000000401106 <+0>:     push   %rbp
   0x0000000000401107 <+1>:     mov    %rsp,%rbp
=3D> 0x000000000040110a <+4>:     lock orq $0x0,(%esp)
   0x0000000000401111 <+11>:    mov    $0x0,%eax
   0x0000000000401116 <+16>:    pop    %rbp
   0x0000000000401117 <+17>:    retq=20=20=20
End of assembler dump.

I didn't investigate further, but 32bit executable works OK.=