From: Kai Tietz <Kai.Tietz@onevision.com>
To: gcc@gcc.gnu.org
Subject: Question about how to implement abi specific va_list (and builtins)
Date: Fri, 13 Jun 2008 09:12:00 -0000 [thread overview]
Message-ID: <OF2199F8A3.040CF624-ONC1257467.0031C911-C1257467.003288BA@onevision.de> (raw)
Hi,
The issue is, that for x86_64 the call for a w64 abi function should be
supported. The problem is, that va_list has always the type of the target
and there is no abi specific switching supported. My first idea was to
make the define for va_list_type_node in tree.h overridable for targets,
or replace the use of this type in code by an new target specific macro
(e.g. TARGET_VA_LIST).
Additionally of course new builtin types have to be added for such
targets, as for x86_64<->w64 like __builtin_ms_va_list and
__builting_sysv_va_list.
I am not sure if this approach would be ok. May somebody could give me a
hint about how to implement it?
Thanks in advance,
Kai
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
reply other threads:[~2008-06-13 9:12 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=OF2199F8A3.040CF624-ONC1257467.0031C911-C1257467.003288BA@onevision.de \
--to=kai.tietz@onevision.com \
--cc=gcc@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).