Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov 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 1/2] Prevent recording of loops with -0 step or NaN values.
Date: Fri, 13 Mar 2026 17:32:46 +0300	[thread overview]
Message-ID: <256a4bfa-edea-4971-b5c3-3b94a102c6d9@tarantool.org> (raw)
In-Reply-To: <abPh4iY67H2yJubb@root>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hi, Sergey,

thanks for the fixes!

Sergey

On 3/13/26 13:07, Sergey Kaplun wrote:


<snipped>

>>> +local function test_trace_recorded(test_payload)
>>> +  jit.flush()
>>> +  -- Reset hotcounters.
>> nit: comment can be omitted
> I prefer not to. There may be the question: why we don't declare this
> parameters once? The reason is that the hotcounters may cause collisions
> and lead to the false-positive tests failures. Should I make the comment
> more verbose?

We reset hotcounters in tests about 470 times (grep -R -B 1 "hotloop=1" 
test | wc -l) and only

15 times we add a comment like "Reset hotcounters.". You add a comment 
here but missed it in the patch

"MIPS64: Avoid unaligned load in lj_vm_exit_interp.". Why we should 
leave comment here and

omit it the aforementioned patch? I'll not insist removing it, just 
interesting, it is not an issue for blocking merge.

>
<snipped>

[-- Attachment #2: Type: text/html, Size: 1877 bytes --]

  reply	other threads:[~2026-03-13 14:32 UTC|newest]

Thread overview: 8+ 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 [this message]
2026-03-13 14:41         ` 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
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=256a4bfa-edea-4971-b5c3-3b94a102c6d9@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