From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Ostanevich <sergos@tarantool.org>, Maxim Kokryashkin <m.kokryashkin@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH luajit 0/3] Dualnumber mode fixes Date: Wed, 18 Jan 2023 23:19:07 +0300 [thread overview] Message-ID: <cover.1674068996.git.skaplun@tarantool.org> (raw) Something strange happened with the previous cover-letter, so resend it. The first 2 patches: * sysprof: fix interval parsing in dual-number mode * ci: introduce workflow for exotic builds are needed to introduce workflow for dualnumber mode build, to test the 3rd commit: * x86/x64: Fix loop realignment. The first and second commits are separated as far as only the first one is needed to backport to tarantool-1.10 branch. PR: https://github.com/tarantool/tarantool/pull/8180 Issues: * https://github.com/LuaJIT/LuaJIT/issues/556 * https://github.com/tarantool/tarantool/issues/8069 Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-556-fix-loop-realignment-full-ci Mike Pall (1): x86/x64: Fix loop realignment. Sergey Kaplun (2): sysprof: fix interval parsing in dual-number mode ci: introduce workflow for exotic builds .github/workflows/exotic-builds-testing.yml | 71 +++++++++++++++++++ src/lib_misc.c | 2 +- src/lj_asm_x86.h | 5 +- .../lj-556-fix-loop-realignment.test.lua | 18 +++++ 4 files changed, 93 insertions(+), 3 deletions(-) create mode 100644 .github/workflows/exotic-builds-testing.yml create mode 100644 test/tarantool-tests/lj-556-fix-loop-realignment.test.lua -- 2.34.1
next reply other threads:[~2023-01-18 20:22 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 20:19 Sergey Kaplun via Tarantool-patches [this message] 2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 1/3] sysprof: fix interval parsing in dual-number mode Sergey Kaplun via Tarantool-patches 2023-01-24 14:16 ` Maxim Kokryashkin via Tarantool-patches 2023-01-26 15:55 ` sergos via Tarantool-patches 2023-01-30 9:39 ` Sergey Kaplun via Tarantool-patches 2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 2/3] ci: introduce workflow for exotic builds Sergey Kaplun via Tarantool-patches 2023-01-24 14:20 ` Maxim Kokryashkin via Tarantool-patches 2023-01-26 21:12 ` sergos via Tarantool-patches 2023-01-30 9:51 ` Sergey Kaplun via Tarantool-patches 2023-02-01 8:27 ` Igor Munkin via Tarantool-patches 2023-02-01 8:52 ` Sergey Kaplun via Tarantool-patches 2023-02-02 8:54 ` sergos via Tarantool-patches 2023-01-18 20:16 ` [Tarantool-patches] [PATCH luajit 3/3] x86/x64: Fix loop realignment Sergey Kaplun via Tarantool-patches 2023-01-19 10:17 ` Sergey Kaplun via Tarantool-patches 2023-01-24 15:13 ` Maxim Kokryashkin via Tarantool-patches 2023-01-26 7:06 ` Sergey Kaplun via Tarantool-patches 2023-01-26 14:45 ` Maxim Kokryashkin via Tarantool-patches 2023-01-26 21:22 ` sergos via Tarantool-patches 2023-02-20 9:56 ` [Tarantool-patches] [PATCH luajit 0/3] Dualnumber mode fixes Igor Munkin via Tarantool-patches -- strict thread matches above, loose matches on Subject: below -- 2023-01-18 20:16 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.1674068996.git.skaplun@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --cc=sergos@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 0/3] Dualnumber mode fixes' \ /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