Tarantool development patches archive
 help / color / mirror / Atom feed
From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: tarantool-patches@dev.tarantool.org, imun@tarantool.org,
	skaplun@tarantool.org
Subject: [Tarantool-patches] [PATCH luajit 0/4] jit: fix math.min/math.max inconsistencies
Date: Thu, 23 Sep 2021 16:55:24 +0300	[thread overview]
Message-ID: <cover.1632404890.git.m.kokryashkin@tarantool.org> (raw)
Message-ID: <20210923135524.ELuOgMwtCGwR-iDLny8UtLMqa4OHd0VnMojl3FsjI8I@z> (raw)

Once applied, this patch set will fix math.min/math.max inconsistencies
and add test case for them. This patch backports the fix[1] from the
vanilla LuaJIT, along with other[2][3] math module fixes.

[1]: https://github.com/LuaJIT/LuaJIT/commit/03208c81
[2]: https://github.com/LuaJIT/LuaJIT/commit/d75e2627
[3]: https://github.com/LuaJIT/LuaJIT/commit/5655be45

Maxim Kokryashkin (2):
  Cleanup math function compilation and fix inconsistencies.
  test: add test for gh-6163 min/max

Mike Pall (2):
  Fix math.min()/math.max() inconsistencies.
  Don't compile math.modf() anymore.

 src/lib_math.c                                | 24 +++---
 src/lj_asm.c                                  |  6 --
 src/lj_asm_arm.h                              |  7 +-
 src/lj_asm_arm64.h                            |  7 +-
 src/lj_asm_x86.h                              |  2 -
 src/lj_ffrecord.c                             | 35 +--------
 src/lj_ir.h                                   |  4 +-
 src/lj_ircall.h                               | 14 ++--
 src/lj_opt_fold.c                             | 78 ++++++++++---------
 src/lj_opt_split.c                            |  3 -
 src/lj_target_x86.h                           |  6 --
 src/lj_vmmath.c                               | 10 +--
 src/vm_arm.dasc                               |  4 +-
 src/vm_arm64.dasc                             |  4 +-
 src/vm_x64.dasc                               |  2 +-
 src/vm_x86.dasc                               |  2 +-
 .../gh-6163-jit-min-max.test.lua              | 18 +++++
 17 files changed, 99 insertions(+), 127 deletions(-)
 create mode 100644 test/tarantool-tests/gh-6163-jit-min-max.test.lua

---
Issue: https://github.com/tarantool/tarantool/issues/6163
GitHub branch: https://github.com/tarantool/luajit/tree/fckxorg/gh-6163-min-max
2.33.0


             reply	other threads:[~2021-09-23 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 13:54 Maxim Kokryashkin via Tarantool-patches [this message]
2021-09-23 13:55 ` Maxim Kokryashkin via Tarantool-patches
2021-09-23 13:55 ` [Tarantool-patches] [PATCH luajit 1/4] Fix math.min()/math.max() inconsistencies Maxim Kokryashkin via Tarantool-patches
2021-09-23 13:55 ` [Tarantool-patches] [PATCH luajit 2/4] Don't compile math.modf() anymore Maxim Kokryashkin via Tarantool-patches
2021-09-23 13:55 ` [Tarantool-patches] [PATCH luajit 3/4] Cleanup math function compilation and fix inconsistencies Maxim Kokryashkin via Tarantool-patches
2021-09-23 13:55 ` [Tarantool-patches] [PATCH luajit 4/4] test: add test for gh-6163 min/max 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.1632404890.git.m.kokryashkin@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=max.kokryashkin@gmail.com \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit 0/4] jit: fix math.min/math.max inconsistencies' \
    /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