From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BF0EA3858D33; Thu, 13 Apr 2023 11:51:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF0EA3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681386668; bh=rdiaXNlp/b3MjWm++HIO+0sjCXsQSMfW73AwO+Q3Kv0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SehMyXMXbGd4lRvbttavTQEkyvqPOGzANv85zUchL75xLA4f3vWxjE9wnlU15YNE0 rBxxYb9soJLAM9r9NafZveSqEgEBKBKz3faQYR4aLu32S21IcLw06gcntu5EKWJT5E U78AfWC9mm/H+SlCU48HAEc2q61Rc9ItjuwQRiZE= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109484] [Wrong Code][inline-asm] output operands overlap with output Date: Thu, 13 Apr 2023 11:51:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: cc 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109484 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #8 from Xi Ruoyao --- (In reply to Jakub Jelinek from comment #7) > Similar bug. The basic GCC expectations for inline-asm is that the whole > assembly template after substitutions (which is for GCC mostly intentiona= lly > a black box) works as a single instruction which reads all its inputs (and > that obviously doesn't mean just the input themselves, but also any other > register/memory used in the input) and then stores all its outputs. > Early clobbers are the way to tell the compiler that it is not the case a= nd > some output is written before all the inputs are used. Should we add this info into the doc?=