From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH luajit 0/2] Fix dangling CType references
Date: Fri, 22 Aug 2025 09:36:16 +0300 [thread overview]
Message-ID: <cover.1755844191.git.skaplun@tarantool.org> (raw)
These two patches fix the dangling ctype references for the vararg FFI
call and its recording.
Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-1360-dangling-ctype-ref-on-ccall
Issues:
* https://github.com/tarantool/tarantool/issues/11691
* https://github.com/LuaJIT/LuaJIT/issues/1360
Mike Pall (2):
FFI: Fix dangling CType references.
FFI: Fix dangling CType references (again).
src/lj_ccall.c | 19 +++--
src/lj_crecord.c | 32 +++++---
...0-dangling-ctype-ref-on-ccall-jit.test.lua | 82 +++++++++++++++++++
...-1360-dangling-ctype-ref-on-ccall.test.lua | 70 ++++++++++++++++
4 files changed, 183 insertions(+), 20 deletions(-)
create mode 100644 test/tarantool-tests/lj-1360-dangling-ctype-ref-on-ccall-jit.test.lua
create mode 100644 test/tarantool-tests/lj-1360-dangling-ctype-ref-on-ccall.test.lua
--
2.50.1
next reply other threads:[~2025-08-22 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 6:36 Sergey Kaplun via Tarantool-patches [this message]
2025-08-22 6:36 ` [Tarantool-patches] [PATCH luajit 1/2] FFI: " Sergey Kaplun via Tarantool-patches
2025-09-08 12:00 ` Sergey Bronnikov via Tarantool-patches
2025-08-22 6:36 ` [Tarantool-patches] [PATCH luajit 2/2] FFI: Fix dangling CType references (again) Sergey Kaplun via Tarantool-patches
2025-09-08 12:01 ` Sergey Bronnikov via Tarantool-patches
2025-09-08 12:02 ` [Tarantool-patches] [PATCH luajit 0/2] Fix dangling CType references Sergey Bronnikov via Tarantool-patches
2025-12-13 16:12 ` Sergey Kaplun via Tarantool-patches
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=cover.1755844191.git.skaplun@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/2] Fix dangling CType references' \
/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