Tarantool development patches archive
 help / color / mirror / Atom feed
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] Correct allocation limit without JIT
Date: Mon,  2 Mar 2026 11:05:30 +0300	[thread overview]
Message-ID: <cover.1772438261.git.skaplun@tarantool.org> (raw)

This patch-set fixes the allocation limit for the build with disabled
JIT. The first commit helps to catch the error early in tests by the
correct check of the address returned by the allocator.

Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-1430-alloc-limit
Related issues:
* https://github.com/LuaJIT/LuaJIT/issues/1430
* https://github.com/tarantool/tarantool/issues/12134
Related ML thread: https://www.freelists.org/post/luajit/Provide-error-outputdetails-upon-luaL-newstate-failures

Mike Pall (2):
  Fix pointer check for non-GC64 mode.
  x64/!LJ_GC64: The allocation limit is required for a no-JIT build,
    too.

 src/lj_alloc.c                                |  4 +-
 src/lj_def.h                                  |  3 +-
 .../lj-1430-internal-alloc-limit.test.lua     | 39 +++++++++++++++++++
 3 files changed, 43 insertions(+), 3 deletions(-)
 create mode 100644 test/tarantool-tests/lj-1430-internal-alloc-limit.test.lua

-- 
2.53.0


             reply	other threads:[~2026-03-02  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  8:05 Sergey Kaplun via Tarantool-patches [this message]
2026-03-02  8:05 ` [Tarantool-patches] [PATCH luajit 1/2] Fix pointer check for non-GC64 mode Sergey Kaplun via Tarantool-patches
2026-03-02  8:05 ` [Tarantool-patches] [PATCH luajit 2/2] x64/!LJ_GC64: The allocation limit is required for a no-JIT build, too 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.1772438261.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] Correct allocation limit without JIT' \
    /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