From: Andrew Haley <aph@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"libffi-discuss@sourceware.org"
<libffi-discuss@sourceware.org>
Subject: Re: [PATCH] Implement libffi for AARCH64:ILP32
Date: Mon, 09 Feb 2015 08:51:00 -0000 [thread overview]
Message-ID: <54D874F8.9040004@redhat.com> (raw)
In-Reply-To: <CA+=Sn1m6s93Gvuv7OvCGciYfbLWdmQYkqm8m7ruQn7DL2pXZ3w@mail.gmail.com>
On 09/02/15 08:40, Andrew Pinski wrote:
> For ILP32, we need to use long long types for ffi_arg and ffi_sarg.
> And then we need to fix up the closure code to load cif, fn, and
> user_data by 32bit instead of 64bits as they are stored as pointers in
> C code.
Would it make more sense to use int64_t rather than long long?
Andrew.
next prev parent reply other threads:[~2015-02-09 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 8:40 Andrew Pinski
2015-02-09 8:51 ` Andrew Haley [this message]
2015-02-10 18:40 ` Richard Henderson
2015-02-10 18:35 ` Richard Henderson
2015-02-10 19:02 ` Andrew Pinski
2015-02-10 21:20 ` Richard Henderson
2015-02-10 22:46 ` Andrew Pinski
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=54D874F8.9040004@redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.org \
--cc=pinskia@gmail.com \
/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).