From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 0/3] Follow-up fixes for full 64-bit lightuserdata interning
Date: Thu, 30 Jun 2022 15:11:27 +0300 [thread overview]
Message-ID: <Yr2S7xTDn/HUu17U@tarantool.org> (raw)
In-Reply-To: <cover.1631170629.git.skaplun@tarantool.org>
Sergey,
I've checked the patches into all long-term branches in tarantool/luajit
and bumped a new version in master, 2.10 and 1.10 (only the first one).
On 09.09.21, Sergey Kaplun wrote:
> Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-727-lightuserdata-itern
> Tarantool branch: https://github.com/tarantool/tarantool/tree/skaplun/lj-727-lightuserdata-itern
> Issue: https://github.com/LuaJIT/LuaJIT/issues/727
>
> The first commit (test-related) is needed to fix test behaviour for
> is_deeply function for userdata object.
> The second commit (refactoring) is needed to simplify cherry-pick of the
> next one (and the last one) without conflicts.
>
> Mike Pall (2):
> Reorganize lightuserdata interning code.
> Avoid conflict between 64 bit lightuserdata and ITERN key.
>
> Sergey Kaplun (1):
> test: fix path storage for non-concatable objects
>
> src/lj_api.c | 30 +--------
> src/lj_udata.c | 28 +++++++++
> src/lj_udata.h | 3 +
> test/tarantool-tests/CMakeLists.txt | 1 +
> .../lj-727-lightuserdata-itern.test.lua | 48 ++++++++++++++
> .../lj-727-lightuserdata-itern/CMakeLists.txt | 1 +
> .../lightuserdata.c | 63 +++++++++++++++++++
> test/tarantool-tests/tap.lua | 4 +-
> 8 files changed, 148 insertions(+), 30 deletions(-)
> create mode 100644 test/tarantool-tests/lj-727-lightuserdata-itern.test.lua
> create mode 100644 test/tarantool-tests/lj-727-lightuserdata-itern/CMakeLists.txt
> create mode 100644 test/tarantool-tests/lj-727-lightuserdata-itern/lightuserdata.c
>
> --
> 2.31.0
>
--
Best regards,
IM
prev parent reply other threads:[~2022-06-30 12:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 7:03 Sergey Kaplun via Tarantool-patches
2021-09-09 7:03 ` [Tarantool-patches] [PATCH luajit 1/3] test: fix path storage for non-concatable objects Sergey Kaplun via Tarantool-patches
2021-09-15 15:30 ` sergos via Tarantool-patches
2021-09-20 8:28 ` Sergey Kaplun via Tarantool-patches
2021-09-20 9:37 ` sergos via Tarantool-patches
2022-06-28 15:41 ` Igor Munkin via Tarantool-patches
2021-09-09 7:03 ` [Tarantool-patches] [PATCH luajit 2/3] Reorganize lightuserdata interning code Sergey Kaplun via Tarantool-patches
2021-09-15 15:30 ` sergos via Tarantool-patches
2021-09-20 8:32 ` Sergey Kaplun via Tarantool-patches
2021-09-20 9:37 ` sergos via Tarantool-patches
2022-06-28 15:42 ` Igor Munkin via Tarantool-patches
2021-09-09 7:03 ` [Tarantool-patches] [PATCH luajit 3/3] Avoid conflict between 64 bit lightuserdata and ITERN key Sergey Kaplun via Tarantool-patches
2021-09-15 15:31 ` sergos via Tarantool-patches
2021-09-20 8:38 ` Sergey Kaplun via Tarantool-patches
2021-09-20 9:37 ` sergos via Tarantool-patches
2022-06-29 20:20 ` Igor Munkin via Tarantool-patches
2022-06-30 12:11 ` Igor Munkin 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=Yr2S7xTDn/HUu17U@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/3] Follow-up fixes for full 64-bit lightuserdata interning' \
/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