From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6089E385840A; Mon, 24 Oct 2022 18:37:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6089E385840A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666636667; bh=Bcq8lFy5UC52nEDl+1jzLtsarXIWDW0Y8fKGmNuCAGs=; h=From:To:Subject:Date:From; b=k2wcohskEN5zeUnlCroumGm0/qWpiZz1d0htyCoUHY0WUJjAuw2deqRk5S12UrK0+ 27doX4u+PXeKTU1UL9udz0UNZTbuwfbfuT3mdh29kGKJrF+zUpRlqJQYROLbkajZOo KhxKPJvKV2pSdUKyEkIHpcNkGbKOqC9gg0RELtRo= From: "ndesaulniers at google dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107385] New: [asm goto] "=r" vs "+r" for outputs along indirect edges Date: Mon, 24 Oct 2022 18:37:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ndesaulniers at google 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 target_milestone 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107385 Bug ID: 107385 Summary: [asm goto] "=3Dr" vs "+r" for outputs along indirect edges Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: ndesaulniers at google dot com CC: isanbard at gmail dot com Target Milestone: --- I was playing around with adding support for outputs along indirect edges of asm goto in clang. When I was comparing codegen between various cases, I noticed a case that looked like a bug to me: int foo (void) { int x; asm goto ("": "=3Dr"(x) ::: bar); x =3D 6; bar: return x; } in gcc 12.2 with `-O2` produces: foo: ret The write to x from the inline asm should be dead along the fallthough or default path out of the asm goto. We should have one edge that assigns 6 to the output. Changing the output constraint modifier from =3Dr to +r seems to produce the expected code. https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended-Asm mentions > Be careful when you set output operands inside asm goto only on some poss= ible control flow paths. If you don=E2=80=99t set up the output on given pa= th and never use it on this path, it is okay. Otherwise, you should use =E2= =80=98+=E2=80=99 constraint modifier meaning that the operand is input and = output one. With this modifier you will have the correct values on all poss= ible paths from the asm goto. I'm not sure if that comment is alluding to this behavior, but it might be = nice to not have to pass in any prior value for output only variables?=