From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9C71A3858D28; Wed, 25 Jan 2023 13:33:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C71A3858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674653600; bh=cBc4vVr68DXqCgGgx42Ktcr7/bRKr8oqIb7g9C12V3c=; h=From:To:Subject:Date:From; b=KIzL/mTyXzbq6rSK0/dL8PWrzHphUPYxJFYAYVBZM6o8tSjO9KHOEKxySR8X4/VhN EV7zn8nCJgALLX72sIVFibB40Wc2jwdmkfeJNBksO8ZvI88ckYGyf6dFq6NRLUt3Zo Lm+p5ja5PFUi3iMSTdMTi4fdosNGqbpHsscVZuFM= From: "arheik at dnainternet dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108539] New: Wrong register usage for -m16 -masm=intel -march=i386 on asm volatile Date: Wed, 25 Jan 2023 13:33:20 +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.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: arheik at dnainternet dot net 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 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=3D108539 Bug ID: 108539 Summary: Wrong register usage for -m16 -masm=3Dintel -march=3Di3= 86 on asm volatile Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: arheik at dnainternet dot net Target Milestone: --- Consider the following code (test.cpp): void test(unsigned char& a, unsigned char& b) { unsigned char _a, _b; asm volatile( "mov dx, 0\n" "mov bx, 0\n" : "=3Ddl" (_a), "=3Ddh" (_b) : : "bx" ); a =3D _a; b =3D _b; } void main(void) { unsigned char a, b; test(a, b); } Compiled with: g++ -m16 -masm=3Dintel -march=3Di386 -ffreestanding -fno-inline -mregparm= =3D3 -fno-dwarf2-cfi-asm -fno-asynchronous-unwind-tables -fno-ident -O2 test.cpp= -o - -S This generates for test(): _Z4testRhS_: .LFB0: push esi .LCFI0: push ebx .LCFI1: mov ecx, edx #APP # 4 "test.cpp" 1 mov dx, 0 mov bx, 0 # 0 "" 2 #NO_APP mov ebx, esi mov BYTE PTR [eax], bl mov BYTE PTR [ecx], dl pop ebx .LCFI2: pop esi .LCFI3: ret In which bl usage is clearly wrong (dh is missing) and ebx/eax/esi usage lo= oks suspect. Compling with -mregparm=3D0 produces for test(): _Z4testRhS_: .LFB0: push ebx .LCFI0: #APP # 4 "test.cpp" 1 mov dx, 0 mov bx, 0 # 0 "" 2 #NO_APP mov eax, DWORD PTR 8[esp] mov BYTE PTR [eax], cl mov eax, DWORD PTR 12[esp] mov BYTE PTR [eax], dl pop ebx .LCFI1: ret Which should use dh instead of cl.=