From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C8FA3385DC04; Sat, 18 Apr 2020 17:23:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C8FA3385DC04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587230630; bh=FQ5fH7oRkRs6VZ7BymmmLTXyfqzHQkN/eQjaR5OBU8s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=qKZ8gECjhEXAfa3E9bHClJN4OgUKW5Cp1iwDBJTBvMHMXC+EUzeQcwcdUblDSrZzV jCb3W/S5RRuwxwum1+NkvjmgjxmO0vmn3X2fsyN/djERevzbJGE4M072H6fK2IYVgv Q/jyhIsfuH+k/KLqiQocEiUIGnvZ8ecUIM+9UodA= From: "fw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/80878] -mcx16 (enable 128 bit CAS) on x86_64 seems not to work on 7.1.0 Date: Sat, 18 Apr 2020 17:23:50 +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: 7.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fw at gcc dot gnu.org X-Bugzilla-Status: NEW 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: In-Reply-To: References: 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: Sat, 18 Apr 2020 17:23:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D80878 --- Comment #21 from Florian Weimer --- (In reply to Avi Kivity from comment #20) > Note that clang generates cmpxchg16b when the conditions are ripe: >=20 > https://godbolt.org/z/j9Whgh I believe this is a different, C++-specific issue. The C front end already emits cmpxchgq in this situation.=