From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 77AD9385BF92; Wed, 1 Apr 2020 18:08:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77AD9385BF92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585764529; bh=8Vr/g/JskddI0LCY1AYOTXrIc+xVSaN3rmda//38uu4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dWkb02PJE+aVuDF0TySh5D9LLKZMxkP2sMQbsiJ7WvWtgNOgXW0hfvfFyLLXiszAl FkRFbqpoj9a0oK1VuDkOyqA7nj0OKXVECz9o/5jlM+nfEE+zwNSsuaaTqg/+gpQoZl brirSJh6Whh/iNXNLf+VEZ2YTA5vLMw9OWnO5W2Y= From: "ibuclaw at gdcproject dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug d/94321] gdc.dg/pr92216.d FAILs on 32-bit targets Date: Wed, 01 Apr 2020 18:08:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: d X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ibuclaw at gdcproject dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org X-Bugzilla-Target-Milestone: 10.0 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: Wed, 01 Apr 2020 18:08:49 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94321 --- Comment #2 from Iain Buclaw --- (In reply to Rainer Orth from comment #0) > As originally reported in >=20 > https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542177.html >=20 > [which didn't get Cc'ed to you due to the abominable header rewriting]: >=20 > The new gdc.dg/pr92216.d testcase FAILs on 32-bit Solaris/SPARC and x86 (= and, > I suppose, on every non-64-bit target): >=20 > +FAIL: gdc.dg/pr92216.d -O0 scan-assembler > _DT16_D7imports7pr922161B8__mixin24getSMFZPv[: \\t\\n] > +FAIL: gdc.dg/pr92216.d -O0 -frelease scan-assembler > _DT16_D7imports7pr922161B8__mixin24getSMFZPv[: \\t\\n] > +FAIL: gdc.dg/pr92216.d -O0 -frelease -g scan-assembler > _DT16_D7imports7pr922161B8__mixin24getSMFZPv[: \\t\\n] > +FAIL: gdc.dg/pr92216.d -O0 -g scan-assembler > _DT16_D7imports7pr922161B8__mixin24getSMFZPv[: \\t\\n] >=20 > Same at -O[1-3s]. While the 64-bit version contains the expected >=20 > _DT16_D7imports7pr922161B8__mixin24getSMFZPv >=20 > the 32-bit one has >=20 > _DT8_D7imports7pr922161B8__mixin24getSMFZPv >=20 > I can't tell for certain if it's enough to allow for those two variants > or if more is needed. > That discrepancy is the encoded this pointer offset. I didn't consider that this information was present when I added the test. > Btw., I noticed that binutils 2.34 c++filt -s dlang cannot demangle those > symbols. Is this expected? Yes, these thunk symbols are a non-standard extension.=