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 corner cases of for loop recording
Date: Thu, 12 Mar 2026 18:55:55 +0300 [thread overview]
Message-ID: <cover.1773330679.git.skaplun@tarantool.org> (raw)
The first patch prevents recording of useless traces with always-fail
guards for NaN control vars or -0 step values. The second patch is the
follow-up to fix DUALNUM mode.
Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-1432-1433-bad-for-loops
Related issues:
* https://github.com/LuaJIT/LuaJIT/issues/1432
* https://github.com/LuaJIT/LuaJIT/issues/1433
* https://github.com/LuaJIT/LuaJIT/issues/1438
* https://github.com/tarantool/tarantool/issues/12134
Mike Pall (2):
Prevent recording of loops with -0 step or NaN values.
DUALNUM: Fix recording of loops broken by previous change.
src/lj_record.c | 6 ++
.../lj-1432-minus-zero-step.test.lua | 57 +++++++++++++
.../lj-1433-nan-for-control-var.test.lua | 79 +++++++++++++++++++
.../lj-1438-jit-for-canary.test.lua | 22 ++++++
4 files changed, 164 insertions(+)
create mode 100644 test/tarantool-tests/lj-1432-minus-zero-step.test.lua
create mode 100644 test/tarantool-tests/lj-1433-nan-for-control-var.test.lua
create mode 100644 test/tarantool-tests/lj-1438-jit-for-canary.test.lua
--
2.53.0
next reply other threads:[~2026-03-12 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:55 Sergey Kaplun via Tarantool-patches [this message]
2026-03-12 15:55 ` [Tarantool-patches] [PATCH luajit 1/2] Prevent recording of loops with -0 step or NaN values Sergey Kaplun via Tarantool-patches
2026-03-12 15:55 ` [Tarantool-patches] [PATCH luajit 2/2] DUALNUM: Fix recording of loops broken by previous change 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.1773330679.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 corner cases of for loop recording' \
/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