From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DF0CF38582BD; Thu, 4 May 2023 06:21:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DF0CF38582BD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683181263; bh=o4v8B1HPU/kRbjwsyRsU4JmccEziLJqmRwAFG9rxHyY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Lkhg4VnkZB35sJQ1cTCamEt47gV0QVQqTsyQQhz1WdECi1hqaWy9OsI/PPmPQw85V DQIplpeQikv1kWvGqskBLF/TrWkKmynTh79sRiUc0AkqUZieyDzZ63yiMeg7dnXLRK eHDlBBzXS3U2L8xwpBa3iB85BysbaEx1xl7mA8So= From: "jbeulich at suse dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/53929] [meta-bug] -masm=intel with global symbol Date: Thu, 04 May 2023 06:21:03 +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: 4.6.3 X-Bugzilla-Keywords: assemble-failure, wrong-code X-Bugzilla-Severity: minor X-Bugzilla-Who: jbeulich at suse dot com 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D53929 --- Comment #14 from jbeulich at suse dot com --- (In reply to LIU Hao from comment #13) > MSVC outputs: > ``` > get_value PROC ; COMDAT > mov ecx, DWORD PTR eax > mov rax, QWORD PTR rip > mov eax, DWORD PTR [rax+rcx*4] > ret 0 > get_value ENDP > ``` Which as least MASM up to 12.x won't assemble. For one it complains about "= rip" being undeclared. And then the load of "ecx" is _not_ a memory access (i.e.= the "DWORD PTR" is ignored there). Which is in line with it also objecting to something like "extrn eax:dword". I say this because I'd be happy to help this on the gas side, but only with= out breaking MASM compatibility. My present plan for gas is (as already outline= d in #11) to make quoted identifiers unambiguously mean symbols, not registers. = But of course that would still require a gcc side change as well. Unfortunately there continue to be inconsistencies in gas with quoted identifiers in gene= ral, and it's not entirely clear yet whether those may need addressing first.=