From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 1/2] Prevent recording of loops with -0 step or NaN values.
Date: Mon, 16 Mar 2026 11:22:50 +0300 [thread overview]
Message-ID: <c4e37397-b3f7-45a7-8421-12c1bcf2bbef@tarantool.org> (raw)
In-Reply-To: <abezQoMXhVwBK6Tc@root>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Hi, Sergey,
thanks for update. LGTM then.
Sergey
On 3/16/26 10:37, Sergey Kaplun wrote:
> Sergey,
>
> Updated the comment as we discussed offline.
> Branch is force-pushed.
>
> On 13.03.26, Sergey Kaplun via Tarantool-patches wrote:
>>
<snipped>
> Made the comment more verbose:
Thanks, I suppose it is more clear now for readers.
>
> ===================================================================
> diff --git a/test/tarantool-tests/lj-1432-minus-zero-step.test.lua b/test/tarantool-tests/lj-1432-minus-zero-step.test.lua
> index 112153dc..e3b97dde 100644
> --- a/test/tarantool-tests/lj-1432-minus-zero-step.test.lua
> +++ b/test/tarantool-tests/lj-1432-minus-zero-step.test.lua
> @@ -42,7 +42,7 @@ end
>
> local function test_trace_recorded(test_payload)
> jit.flush()
> - -- Reset hotcounters.
> + -- XXX: Reset hotcounters to avoid false-positive collisions.
> jit.opt.start('hotloop=1', 'hotexit=1')
> test_payload()
> return traceinfo(1)
> diff --git a/test/tarantool-tests/lj-1433-nan-for-loop-control-var.test.lua b/test/tarantool-tests/lj-1433-nan-for-loop-control-var.test.lua
> index b9e5ad92..f7566d6a 100644
> --- a/test/tarantool-tests/lj-1433-nan-for-loop-control-var.test.lua
> +++ b/test/tarantool-tests/lj-1433-nan-for-loop-control-var.test.lua
> @@ -62,7 +62,7 @@ end
>
> local function test_trace_recorded(test_payload)
> jit.flush()
> - -- Reset hotcounters.
> + -- XXX: Reset hotcounters to avoid false-positive collisions.
> jit.opt.start('hotloop=1', 'hotexit=1')
> test_payload()
> return traceinfo(1)
> ===================================================================
>
>>> <snipped>
>> --
>> Best regards,
>> Sergey Kaplun
[-- Attachment #2: Type: text/html, Size: 2852 bytes --]
next prev parent reply other threads:[~2026-03-16 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:55 [Tarantool-patches] [PATCH luajit 0/2] Fix corner cases of for loop recording Sergey Kaplun via Tarantool-patches
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-13 8:52 ` Sergey Bronnikov via Tarantool-patches
2026-03-13 10:07 ` Sergey Kaplun via Tarantool-patches
2026-03-13 14:32 ` Sergey Bronnikov via Tarantool-patches
2026-03-13 14:41 ` Sergey Kaplun via Tarantool-patches
2026-03-16 7:37 ` Sergey Kaplun via Tarantool-patches
2026-03-16 8:22 ` Sergey Bronnikov via Tarantool-patches [this message]
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
2026-03-13 10:11 ` Sergey Bronnikov 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=c4e37397-b3f7-45a7-8421-12c1bcf2bbef@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=sergeyb@tarantool.org \
--cc=skaplun@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 1/2] Prevent recording of loops with -0 step or NaN values.' \
/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