From: "Devin A Nakamura" <devinn@ca.ibm.com>
To: libffi-discuss@sourceware.org
Subject: Win64 raw api
Date: Thu, 03 Mar 2016 18:25:00 -0000 [thread overview]
Message-ID: <201603031825.u23IP7kG002383@d01av02.pok.ibm.com> (raw)
Is there any particular logic for having the raw api disabled on win64
builds? From what I can tell of the source the raw api stub functions
should allow the api calls to work even when they are not natively
implemented. Also I noticed that in master the raw api is enabled. Is
there
any logic behind this (ie was some new functionality added to support
this)
or was it just fixing a logic error in the previous version of
x86/ffitarget.h?
reply other threads:[~2016-03-03 18:25 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=201603031825.u23IP7kG002383@d01av02.pok.ibm.com \
--to=devinn@ca.ibm.com \
--cc=libffi-discuss@sourceware.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).