public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.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	[thread overview]
Message-ID: <bug-94321-4-OLqccKFo7g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94321-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94321

--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Rainer Orth from comment #0)
> As originally reported in
> 
> https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542177.html
> 
> [which didn't get Cc'ed to you due to the abominable header rewriting]:
> 
> The new gdc.dg/pr92216.d testcase FAILs on 32-bit Solaris/SPARC and x86 (and,
> I suppose, on every non-64-bit target):
> 
> +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]
> 
> Same at -O[1-3s].  While the 64-bit version contains the expected
> 
> _DT16_D7imports7pr922161B8__mixin24getSMFZPv
> 
> the 32-bit one has
> 
> _DT8_D7imports7pr922161B8__mixin24getSMFZPv
> 
> 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.

  parent reply	other threads:[~2020-04-01 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 11:58 [Bug d/94321] New: " ro at gcc dot gnu.org
2020-03-25 11:58 ` [Bug d/94321] " ro at gcc dot gnu.org
2020-03-25 20:24 ` danglin at gcc dot gnu.org
2020-04-01 18:08 ` ibuclaw at gdcproject dot org [this message]
2020-04-01 20:56 ` ibuclaw at gdcproject dot org
2020-04-01 21:10 ` cvs-commit at gcc dot gnu.org
2020-04-01 21:21 ` ibuclaw at gdcproject dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94321-4-OLqccKFo7g@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).