From: Iain Buclaw <ibuclaw@gdcproject.org>
To: gcc-patches@gcc.gnu.org
Cc: Iain Buclaw <ibuclaw@gdcproject.org>
Subject: [committed] d: Document that TypeInfo-based va_arg is not implemented [PR108763]
Date: Fri, 3 Mar 2023 20:43:33 +0100 [thread overview]
Message-ID: <20230303194333.559903-1-ibuclaw@gdcproject.org> (raw)
Hi,
GDC's run-time library doesn't implement the RTTI-based overload of
va_arg, document it on the missing features page.
Bootstrapped and regression tested, committed to mainline.
Regards,
Iain.
---
PR d/108763
gcc/d/ChangeLog:
* implement-d.texi (Missing Features): Document that TypeInfo-based
va_arg is not implemented.
---
gcc/d/implement-d.texi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/gcc/d/implement-d.texi b/gcc/d/implement-d.texi
index 89a17916a83..039e5fbd24e 100644
--- a/gcc/d/implement-d.texi
+++ b/gcc/d/implement-d.texi
@@ -2511,4 +2511,10 @@ version (GNU)
@}
@end smallexample
+@item TypeInfo-based va_arg
+The Digital Mars D compiler implements a version of @code{core.vararg.va_arg}
+that accepts a run-time @code{TypeInfo} argument for use when the static type
+is not known. This function is not implemented by GNU D. It is more portable
+to use variadic template functions instead.
+
@end table
--
2.37.2
reply other threads:[~2023-03-03 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230303194333.559903-1-ibuclaw@gdcproject.org \
--to=ibuclaw@gdcproject.org \
--cc=gcc-patches@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).