From: Alan Lehotsky <alehotsky@codegentllc.com>
To: libffi-discuss@sourceware.org
Subject: libffi support for z/OS and xlc compiler?
Date: Tue, 02 Jul 2019 14:45:00 -0000 [thread overview]
Message-ID: <3451DF60-F5DA-4FAA-8D97-37D7FB189E2C@codegentllc.com> (raw)
I implemented a minimal ability to dynamically call DLLs on z/OS using xlc, but it’s far from able to handle the full C ABI for passing returning things like structs by value or mixing floats and doubles. It would seem that libffi would be a more capable environment, but there doesn’t seem to be a supported z/OS port - just the OS390 UNIX ports.
Anybody know if the OS390 ABI is compatible with the z/OS ABI? I tried a google search to see if there was any comparison documentation, but didn’t get any obvious hits.
And has anybody tried using libffi on z/OS?
— Al
next reply other threads:[~2019-07-02 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 14:45 Alan Lehotsky [this message]
2019-07-02 15:00 ` Anthony Green
2019-07-03 22:08 Devin Nakamura
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=3451DF60-F5DA-4FAA-8D97-37D7FB189E2C@codegentllc.com \
--to=alehotsky@codegentllc.com \
--cc=apl@alum.mit.edu \
--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).