From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
Evgeniy Temirgaleev <e.temirgaleev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 5/5] FFI/MacOS: Fix calling convention for enums.
Date: Mon, 1 Jun 2026 16:07:03 +0300 [thread overview]
Message-ID: <d29bcb46-2c49-4f77-918c-9e4e391ca9eb@tarantool.org> (raw)
In-Reply-To: <20260530160409.4043089-6-skaplun@tarantool.org>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
Hi, Sergey,
thanks for the patch! LGTM
Sergey
On 5/30/26 19:04, Sergey Kaplun wrote:
> From: Mike Pall <mike>
>
> Thanks to Sergey Kaplun.
>
> (cherry picked from commit b925b3e3fc6771171602323b45fbe9fb8fc90369)
>
> This patch fixes the regression in the arm64 OSX FFI behaviour when the
> fundamental C types are passed via the stack. The given arguments should
> occupy the "packed" size on the stack if they are fundamental C
> types [1]. Structures require the pointer-size alignment like it was done
> in the previous commit. This patch fixes that (not only for enums but for
> other data types too). This fixes the tests that were failing after the
> previous commit.
>
> [1]:https://developer.apple.com/documentation/xcode/writing-arm64-code-for-apple-platforms#Pass-arguments-to-functions-correctly
>
> Sergey Kaplun:
> * added the description for the problem
>
> Part of tarantool/tarantool#12480
> ---
> src/lj_ccall.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/lj_ccall.c b/src/lj_ccall.c
> index 1beccc10..7c3ec1e5 100644
> --- a/src/lj_ccall.c
> +++ b/src/lj_ccall.c
> @@ -1082,7 +1082,7 @@ static int ccall_set_args(lua_State *L, CTState *cts, CType *ct,
> if (CCALL_ALIGN_STACKARG) { /* Align argument on stack. */
> MSize align = (1u << ctype_align(ccall_struct_align(cts, d))) - 1;
> #if LJ_TARGET_ARM64 && LJ_TARGET_OSX
> - isva = 1;
> + isva = ctype_isstruct(d->info);
> #endif
> if (rp || (CCALL_PACK_STACKARG && isva && align < CTSIZE_PTR-1))
> align = CTSIZE_PTR-1;
[-- Attachment #2: Type: text/html, Size: 2169 bytes --]
prev parent reply other threads:[~2026-06-01 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 16:04 [Tarantool-patches] [PATCH luajit 0/5] Various FFI ABI calling conventions fixes Sergey Kaplun via Tarantool-patches
2026-05-30 16:04 ` [Tarantool-patches] [PATCH luajit 1/5] FFI: Unify stack setup for C calls in interpreter Sergey Kaplun via Tarantool-patches
2026-05-30 16:04 ` [Tarantool-patches] [PATCH luajit 2/5] FFI/ARM64/OSX: Handle non-standard OSX C calling conventions Sergey Kaplun via Tarantool-patches
2026-06-01 11:40 ` Sergey Bronnikov via Tarantool-patches
2026-05-30 16:04 ` [Tarantool-patches] [PATCH luajit 3/5] ARM64: Fix pass-by-value struct " Sergey Kaplun via Tarantool-patches
2026-06-01 12:27 ` Sergey Bronnikov via Tarantool-patches
2026-05-30 16:04 ` [Tarantool-patches] [PATCH luajit 4/5] FFI: Various ABI and calling convention fixes Sergey Kaplun via Tarantool-patches
2026-06-01 13:02 ` Sergey Bronnikov via Tarantool-patches
2026-05-30 16:04 ` [Tarantool-patches] [PATCH luajit 5/5] FFI/MacOS: Fix calling convention for enums Sergey Kaplun via Tarantool-patches
2026-06-01 13:07 ` Sergey Bronnikov via Tarantool-patches [this message]
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=d29bcb46-2c49-4f77-918c-9e4e391ca9eb@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=e.temirgaleev@tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 5/5] FFI/MacOS: Fix calling convention for enums.' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox