From: Andreas Schwab <schwab@linux-m68k.org>
To: Richard Henderson <rth@twiddle.net>
Cc: libffi-discuss@sourceware.org, Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH 08/16] aarch64: Tidy up abi manipulation
Date: Sun, 17 Sep 2017 14:24:00 -0000 [thread overview]
Message-ID: <87efr5fln8.fsf@linux-m68k.org> (raw)
In-Reply-To: <1414522393-19169-9-git-send-email-rth@twiddle.net> (Richard Henderson's message of "Tue, 28 Oct 2014 11:53:05 -0700")
On Okt 28 2014, Richard Henderson <rth@twiddle.net> wrote:
> + case FFI_TYPE_STRUCT:
> + {
> + void *dest;
> + int elems;
> +
> + h = is_hfa (ty);
> + if (h)
> + {
> + do_hfa:
> + elems = h >> 8;
> + if (state.nsrn + elems <= N_V_ARG_REG)
> + {
> + dest = &context->v[state.nsrn];
> + state.nsrn += elems;
> + extend_hfa_type (dest, a, h);
> + break;
> + }
> + state.nsrn = N_V_ARG_REG;
> + dest = allocate_to_stack (&state, stack, ty->alignment, s);
> + }
> + else if (s > 16)
> + {
> + /* If the argument is a composite type that is larger than 16
> + bytes, then the argument has been copied to memory, and
> + the argument is replaced by a pointer to the copy. */
> + a = &avalue[i];
> + t = FFI_TYPE_POINTER;
> + goto do_pointer;
I don't see where the argument has been copied to memory. Doesn't that
need to call allocate_to_stack here?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-09-17 14:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 18:53 [PATCH 00/16] Go closures for aarch64 Richard Henderson
2014-10-28 18:53 ` [PATCH 01/16] aarch64: Fix non-apple compilation Richard Henderson
2014-10-28 18:53 ` [PATCH 03/16] aarch64: Always distinguish LONGDOUBLE Richard Henderson
2014-10-28 18:54 ` [PATCH 11/16] aarch64: Move return value handling into ffi_closure_SYSV Richard Henderson
2014-10-28 18:54 ` [PATCH 12/16] aarch64: Unify scalar fp and hfa handling Richard Henderson
2014-10-28 18:54 ` [PATCH 10/16] aarch64: Move return value handling into ffi_call_SYSV Richard Henderson
2014-10-28 18:54 ` [PATCH 15/16] aarch64: Move x8 out of call_context Richard Henderson
2014-10-28 18:54 ` [PATCH 07/16] aarch64: Treat void return as not passed in registers Richard Henderson
2014-10-28 18:54 ` [PATCH 04/16] aarch64: Simplify AARCH64_STACK_ALIGN Richard Henderson
2014-10-28 18:54 ` [PATCH 08/16] aarch64: Tidy up abi manipulation Richard Henderson
2017-09-17 14:24 ` Andreas Schwab [this message]
2014-10-28 18:54 ` [PATCH 14/16] aarch64: Add support for complex types Richard Henderson
2014-10-28 18:54 ` [PATCH 09/16] aarch64: Merge prep_args with ffi_call Richard Henderson
2014-10-28 18:54 ` [PATCH 16/16] aarch64: Add support for Go closures Richard Henderson
2014-10-28 18:54 ` [PATCH 02/16] aarch64: Improve is_hfa Richard Henderson
2014-10-28 18:54 ` [PATCH 13/16] aarch64: Remove aarch64_flags Richard Henderson
2014-10-28 18:54 ` [PATCH 05/16] aarch64: Reduce the size of register_context Richard Henderson
2014-10-28 18:54 ` [PATCH 06/16] aarch64: Use correct return registers Richard Henderson
2014-11-10 10:12 ` [PATCH 00/16] Go closures for aarch64 James Greenhalgh
2014-11-10 13:22 ` Richard Henderson
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=87efr5fln8.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=libffi-discuss@sourceware.org \
--cc=rth@redhat.com \
--cc=rth@twiddle.net \
/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).