From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <max.kokryashkin@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit v2 0/5] Fix error-throwing on an incorrect coroutine
Date: Tue, 7 Nov 2023 13:31:19 +0000 [thread overview]
Message-ID: <ZUo8J1pFGI0of1Iv@tarantool.org> (raw)
In-Reply-To: <cover.1695968227.git.m.kokryashkin@tarantool.org>
Max,
I've checked the patchset into all long-term branches in
tarantool/luajit and bumped a new version in master, release/2.11 and
release/2.10.
On 29.09.23, Maxim Kokryashkin via Tarantool-patches wrote:
> Changes in v2:
> - Fixed comments as per offline talk with Igor:
> * Reverted one more patch for ARM
> ('arm64: fix cur_L restoration on error throw').
> * Added test from the original issue LuaJIT/LuaJIT#1066
>
> Branch: https://github.com/tarantool/luajit/tree/fckxorg/gh-6323-fix-curL
> PR: https://github.com/tarantool/tarantool/pull/9168
>
> Maxim Kokryashkin (4):
> Revert "Fix cur_L tracking on exceptional path"
> Revert "Update cur_L on exceptional path"
> Revert "arm64: fix cur_L restoration on error throw"
> Revert "Update cur_L on exceptional path (arm)"
>
> Mike Pall (1):
> Restore cur_L for specific Lua/C API use case.
>
> src/lj_err.c | 5 ++-
> src/vm_arm.dasc | 2 --
> src/vm_arm64.dasc | 2 --
> src/vm_x64.dasc | 8 ++---
> src/vm_x86.dasc | 8 ++---
> test/tarantool-tests/CMakeLists.txt | 1 +
> ...-fix-cur_L-after-coroutine-resume.test.lua | 32 +++++++++++++++++++
> .../CMakeLists.txt | 1 +
> .../libcur_L_coroutine.c | 22 +++++++++++++
> 9 files changed, 66 insertions(+), 15 deletions(-)
> create mode 100644 test/tarantool-tests/lj-1066-fix-cur_L-after-coroutine-resume.test.lua
> create mode 100644 test/tarantool-tests/lj-1066-fix-cur_L-after-coroutine-resume/CMakeLists.txt
> create mode 100644 test/tarantool-tests/lj-1066-fix-cur_L-after-coroutine-resume/libcur_L_coroutine.c
>
> --
> 2.42.0
>
--
Best regards,
IM
prev parent reply other threads:[~2023-11-07 13:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 6:20 Maxim Kokryashkin via Tarantool-patches
2023-09-29 6:20 ` [Tarantool-patches] [PATCH luajit v2 1/5] Revert "Fix cur_L tracking on exceptional path" Maxim Kokryashkin via Tarantool-patches
2023-10-03 18:54 ` Sergey Bronnikov via Tarantool-patches
2023-10-04 11:27 ` Maxim Kokryashkin via Tarantool-patches
2023-10-06 8:28 ` Sergey Bronnikov via Tarantool-patches
2023-10-10 8:19 ` Sergey Kaplun via Tarantool-patches
2023-09-29 6:20 ` [Tarantool-patches] [PATCH luajit v2 2/5] Revert "Update cur_L " Maxim Kokryashkin via Tarantool-patches
2023-10-03 18:55 ` Sergey Bronnikov via Tarantool-patches
2023-10-04 11:27 ` Maxim Kokryashkin via Tarantool-patches
2023-10-06 8:28 ` Sergey Bronnikov via Tarantool-patches
2023-10-10 8:20 ` Sergey Kaplun via Tarantool-patches
2023-09-29 6:20 ` [Tarantool-patches] [PATCH luajit v2 3/5] Revert "arm64: fix cur_L restoration on error throw" Maxim Kokryashkin via Tarantool-patches
2023-10-06 8:29 ` Sergey Bronnikov via Tarantool-patches
2023-10-10 8:21 ` Sergey Kaplun via Tarantool-patches
2023-09-29 6:20 ` [Tarantool-patches] [PATCH luajit v2 4/5] Revert "Update cur_L on exceptional path (arm)" Maxim Kokryashkin via Tarantool-patches
2023-10-06 8:29 ` Sergey Bronnikov via Tarantool-patches
2023-10-10 8:21 ` Sergey Kaplun via Tarantool-patches
2023-09-29 6:20 ` [Tarantool-patches] [PATCH luajit v2 5/5] Restore cur_L for specific Lua/C API use case Maxim Kokryashkin via Tarantool-patches
2023-10-03 19:16 ` Sergey Bronnikov via Tarantool-patches
2023-10-04 11:26 ` Maxim Kokryashkin via Tarantool-patches
2023-10-06 8:30 ` Sergey Bronnikov via Tarantool-patches
2023-10-10 8:57 ` Sergey Kaplun via Tarantool-patches
2023-10-13 11:50 ` Maxim Kokryashkin via Tarantool-patches
2023-10-22 1:58 ` Sergey Kaplun via Tarantool-patches
2023-11-07 13:31 ` 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=ZUo8J1pFGI0of1Iv@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=max.kokryashkin@gmail.com \
--subject='Re: [Tarantool-patches] [PATCH luajit v2 0/5] Fix error-throwing on an incorrect coroutine' \
/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