From: Devin Nakamura <devin122@gmail.com>
To: libffi-discuss@sourceware.org
Cc: alehotsky@codegentllc.com, green@redhat.com
Subject: Re: libffi support for z/OS and xlc compiler?
Date: Wed, 03 Jul 2019 22:08:00 -0000 [thread overview]
Message-ID: <CAJ1AwB546Y0_-QH4ji3u3KAMudy-emXsSnWkBJDJ=WFnpqdq-Q@mail.gmail.com> (raw)
libffi-discuss-owner@sourceware.org wrote on 2019-07-02 11:00:43 AM:
> From: Anthony Green <green@redhat.com>
> To: Alan Lehotsky <alehotsky@codegentllc.com>
> Cc: libffi-discuss@sourceware.org, apl@alum.mit.edu
> Date: 2019-07-02 11:01 AM
> Subject: [EXTERNAL] Re: libffi support for z/OS and xlc compiler?
> Sent by: libffi-discuss-owner@sourceware.org
>
>
> Hi Alan - it's been a long time!
>
> Alan Lehotsky <alehotsky@codegentllc.com> writes:
>
> > 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?
Not sure what you mean. AFAIK OS390 == z/OS. If you mean linux 390,
then no, they are not abi compatible
>
> A quick google search tells me that an intern at IBM ported libffi to
> z/OS in 2015
I can do you one better. I am ended up rewriting the z/os port and am
currently the one maintaining it. There a quite a few limitations (I
only bothered implementing as much as we needed)
What exactly did you need it for? I'd be happy to help. (I've been
meaning to upstream the changes, but there have always been more
urgent matters on my plate)
Standard disclaimer: my opinions are my own, and in no way do I
represent IBM, etc. etc.
next reply other threads:[~2019-07-03 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 22:08 Devin Nakamura [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-02 14:45 Alan Lehotsky
2019-07-02 15:00 ` Anthony Green
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='CAJ1AwB546Y0_-QH4ji3u3KAMudy-emXsSnWkBJDJ=WFnpqdq-Q@mail.gmail.com' \
--to=devin122@gmail.com \
--cc=alehotsky@codegentllc.com \
--cc=green@redhat.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).