From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org>, Maxim Kokryashkin <m.kokryashkin@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH luajit v2 0/5] Adjust tests to be run when JIT is disabled Date: Tue, 28 Feb 2023 19:00:43 +0000 [thread overview] Message-ID: <cover.1677607479.git.imun@tarantool.org> (raw) This series make LuaJIT tests work when JIT is either disabled or turned off. It looks large a bit, but it's not complex at all. The first patch is a backport of a tiny change fixing header dependencies for the build with -DLUAJIT_DISABLE_JIT=ON and whitespace inconsistency (that is a bit irrelevant, but IMHO still OK). The second patch is quite similar to the first one, but relates to the changes made in our fork (sysprof, memprof, etc). The third patch disables all JIT-related tests in tarantool-tests suite via skipcond introduced in the separate series[1]. The fourth patch fixes <compiled_with_jit> condition according to its usage in lua-Harness suite. The last patch introduces a new flavor to exotic builds matrix to test builds with JIT disabled. Changes in v2: - Moved test enhancements to a separate series[1] Issue: https://github.com/tarantool/tarantool/issues/8252 Branch: https://github.com/tarantool/luajit/commits/imun/jit-off-ci Tarantool PR: https://github.com/tarantool/tarantool/pull/8288 CI: https://github.com/tarantool/luajit/commit/6aa9059 [1]: https://lists.tarantool.org/tarantool-patches/cover.1677236706.git.imun@tarantool.org/T/#t Igor Munkin (4): build: fix build with JIT disabled test: add skipcond for all JIT-related tests test: fix lua-Harness JIT-related tests ci: add nojit flavor for exotic builds Mike Pall (1): Minor fixes. .github/workflows/exotic-builds-testing.yml | 4 +++- src/lib_base.c | 2 +- src/lj_gc.c | 1 + src/lj_memprof.c | 9 ++++----- src/lj_symtab.c | 13 +++---------- src/lj_symtab.h | 2 ++ test/lua-Harness-tests/403-jit.t | 2 +- test/lua-Harness-tests/411-luajit.t | 2 +- test/tarantool-tests/bc-jit-unpatching.test.lua | 6 ++++-- .../fix-fold-simplify-conv-sext.test.lua | 7 ++++--- .../fix-slot-check-for-mm-record.test.lua | 4 +++- test/tarantool-tests/gh-4199-gc64-fuse.test.lua | 1 + test/tarantool-tests/gh-4427-ffi-sandwich.test.lua | 1 + .../gh-4476-fix-string-find-recording.test.lua | 4 +++- .../gh-5813-resolving-of-c-symbols.test.lua | 4 +++- .../gh-6065-jit-library-smoke-tests.test.lua | 4 +++- ...gh-6098-fix-side-exit-patching-on-arm64.test.lua | 5 ++++- test/tarantool-tests/gh-6189-cur_L.test.lua | 7 +++++-- ...6227-bytecode-allocator-for-comparisons.test.lua | 5 ++++- .../gh-6371-string-char-no-arg.test.lua | 5 +++-- .../gh-6782-stitching-in-vmevent-handler.test.lua | 6 ++++-- .../gh-6976-narrowing-of-unary-minus.test.lua | 5 ++++- ...gh-7264-add-proto-trace-sysprof-default.test.lua | 1 + .../tarantool-tests/lj-350-sload-typecheck.test.lua | 8 +++++--- .../lj-356-ir-khash-non-string-obj.test.lua | 11 +++++++---- test/tarantool-tests/lj-357-arm64-hrefk.test.lua | 6 ++++-- .../lj-375-ir-bufput-signed-char.test.lua | 4 +++- .../lj-408-tonumber-cdata-record.test.lua | 11 ++++++----- test/tarantool-tests/lj-416-xor-before-jcc.test.lua | 6 ++++-- test/tarantool-tests/lj-430-maxirconst.test.lua | 1 + .../lj-505-fold-no-strref-for-ptrdiff.test.lua | 4 +++- .../lj-524-fold-conv-respect-src-irt.test.lua | 6 ++++-- .../lj-556-fix-loop-realignment.test.lua | 4 +++- .../lj-584-bad-renames-for-sunk-values.test.lua | 4 +++- .../lj-603-err-snap-restore.test.lua | 1 + .../lj-672-cdata-allocation-recording.test.lua | 1 + .../lj-864-varg-rec-base-offset.test.lua | 6 ++++-- test/tarantool-tests/lj-flush-on-trace.test.lua | 1 + .../misclib-getmetrics-capi.test.lua | 1 + .../misclib-getmetrics-lapi.test.lua | 1 + test/tarantool-tests/misclib-memprof-lapi.test.lua | 2 +- test/tarantool-tests/misclib-sysprof-capi.test.lua | 5 +++-- test/tarantool-tests/misclib-sysprof-lapi.test.lua | 5 +++-- 43 files changed, 122 insertions(+), 66 deletions(-) -- 2.30.2
next reply other threads:[~2023-02-28 19:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 19:00 Igor Munkin via Tarantool-patches [this message] 2023-02-28 19:00 ` [Tarantool-patches] [PATCH luajit v2 1/5] Minor fixes Igor Munkin via Tarantool-patches 2023-03-01 19:25 ` Maxim Kokryashkin via Tarantool-patches 2023-02-28 19:00 ` [Tarantool-patches] [PATCH luajit v2 2/5] build: fix build with JIT disabled Igor Munkin via Tarantool-patches 2023-03-01 19:27 ` Maxim Kokryashkin via Tarantool-patches 2023-03-02 15:52 ` Igor Munkin via Tarantool-patches 2023-02-28 19:00 ` [Tarantool-patches] [PATCH luajit v2 3/5] test: add skipcond for all JIT-related tests Igor Munkin via Tarantool-patches 2023-03-01 10:04 ` Sergey Kaplun via Tarantool-patches 2023-03-02 16:42 ` Igor Munkin via Tarantool-patches 2023-03-01 19:28 ` Maxim Kokryashkin via Tarantool-patches 2023-02-28 19:00 ` [Tarantool-patches] [PATCH luajit v2 4/5] test: fix lua-Harness " Igor Munkin via Tarantool-patches 2023-03-01 10:08 ` Sergey Kaplun via Tarantool-patches 2023-03-01 19:30 ` Maxim Kokryashkin via Tarantool-patches 2023-02-28 19:00 ` [Tarantool-patches] [PATCH luajit v2 5/5] ci: add nojit flavor for exotic builds Igor Munkin via Tarantool-patches 2023-03-01 19:30 ` 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.1677607479.git.imun@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v2 0/5] Adjust tests to be run when JIT is disabled' \ /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