From: Jan Beulich <jbeulich@suse.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: Ian Lance Taylor <ian@airs.com>, Iain Buclaw <ibuclaw@gdcproject.org>
Subject: libiberty D tuple demangling
Date: Mon, 25 Jul 2022 08:45:57 +0200 [thread overview]
Message-ID: <168911bd-ba44-e197-ffd7-c687a6d7eb06@suse.com> (raw)
In-Reply-To: <f35a2359-e102-7682-65b4-e56e602f9adf@aol.com>
Hello,
while commit 3f30a274913b ("libiberty: Update D symbol demangling
for latest ABI spec") mentions in its description that tuple encoding
has changed, there's no real adjustment to dlang_parse_tuple() there,
nor are there any new (or replaced) test cases for that. Was this
simply overlooked?
Furthermore the current ABI specifies "B Parameters Z". As I don't
know what the old ABI said, I can only wonder whether the present
code decoding (in a loop) merely a Type (and not a Parameter) was
actually correct.
Thanks for any insight, Jan
next parent reply other threads:[~2022-07-25 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f35a2359-e102-7682-65b4-e56e602f9adf@aol.com>
2022-07-25 6:45 ` Jan Beulich [this message]
2022-07-25 12:05 ` ibuclaw
2022-07-25 12:13 ` Jan Beulich
2022-07-25 15:45 ` ibuclaw
2022-07-25 15:57 ` Jan Beulich
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=168911bd-ba44-e197-ffd7-c687a6d7eb06@suse.com \
--to=jbeulich@suse.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=ibuclaw@gdcproject.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).