From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tarantool-patches@dev.tarantool.org, skaplun@tarantool.org,
sergeyb@tarantool.org
Subject: [Tarantool-patches] [PATCH luajit 0/4] Fix error-throwing on an incorrect coroutine
Date: Thu, 28 Sep 2023 20:08:45 +0300 [thread overview]
Message-ID: <cover.1695920642.git.m.kokryashkin@tarantool.org> (raw)
This patch set reverts three patches, that introduced cur_L update
on error throw, because this behavior is a violation of the Lua C
API. Then, a proper fix from the vanilla LuaJIT is applied.
This proper fix now lets us perform that Lua C API violation
though, so the old test for the issue left intact and no new
tests were added.
Branch: https://github.com/tarantool/luajit/tree/fckxorg/gh-6323-fix-curL
PR: https://github.com/tarantool/tarantool/pull/9168
Maxim Kokryashkin (3):
Revert "Fix cur_L tracking on exceptional path"
Revert "Update cur_L on exceptional path"
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_x64.dasc | 8 +++-----
src/vm_x86.dasc | 8 +++-----
4 files changed, 10 insertions(+), 13 deletions(-)
--
2.42.0
next reply other threads:[~2023-09-28 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 17:08 Maxim Kokryashkin via Tarantool-patches [this message]
2023-09-28 17:08 ` [Tarantool-patches] [PATCH luajit 1/4] Revert "Fix cur_L tracking on exceptional path" Maxim Kokryashkin via Tarantool-patches
2023-09-28 17:08 ` [Tarantool-patches] [PATCH luajit 2/4] Revert "Update cur_L " Maxim Kokryashkin via Tarantool-patches
2023-09-28 17:08 ` [Tarantool-patches] [PATCH luajit 3/4] Revert "Update cur_L on exceptional path (arm)" Maxim Kokryashkin via Tarantool-patches
2023-09-28 17:08 ` [Tarantool-patches] [PATCH luajit 4/4] Restore cur_L for specific Lua/C API use case Maxim Kokryashkin 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.1695920642.git.m.kokryashkin@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=max.kokryashkin@gmail.com \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 0/4] 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