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>,
	Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 luajit 0/5] Handle all errors during stitching
Date: Tue, 18 Jun 2024 11:40:24 +0300	[thread overview]
Message-ID: <3d9dc802-c916-449b-a953-8c91296f5127@tarantool.org> (raw)
In-Reply-To: <cover.1718528874.git.skaplun@tarantool.org>

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

Hi, Sergey!

On 16.06.2024 13:01, Sergey Kaplun wrote:
> This patchset handles all possible error types that may be observed
> during stitching. The first 2 patches add an option to enable table bump
> optimization for CMake options and add it to the CI exotic build
> correspondingly. The third patch enhances the <jit/parse.lua> testing
> utility to return IRs of aborted trace as well. Also, the reason for the
> abort of a trace may be examined. The last 2 patches handle all possible
> errors during stitching and ensure that the output of `jit.dump()` is
> alid for all cases.

Patch series LGTM.


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

  parent reply	other threads:[~2024-06-18  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 10:01 Sergey Kaplun via Tarantool-patches
2024-06-16 10:00 ` [Tarantool-patches] [PATCH v2 luajit 1/5] build: introduce option LUAJIT_ENABLE_TABLE_BUMP Sergey Kaplun via Tarantool-patches
2024-06-16 10:00 ` [Tarantool-patches] [PATCH v2 luajit 2/5] ci: add tablebump flavor for exotic builds Sergey Kaplun via Tarantool-patches
2024-06-16 10:00 ` [Tarantool-patches] [PATCH v2 luajit 3/5] test: allow `jit.parse` to return aborted traces Sergey Kaplun via Tarantool-patches
2024-06-16 10:00 ` [Tarantool-patches] [PATCH v2 luajit 4/5] Handle all types of errors during trace stitching Sergey Kaplun via Tarantool-patches
2024-06-16 10:00 ` [Tarantool-patches] [PATCH v2 luajit 5/5] Use generic trace error for OOM " Sergey Kaplun via Tarantool-patches
2024-06-18  8:40 ` Sergey Bronnikov via Tarantool-patches [this message]
2024-07-09  8:04 ` [Tarantool-patches] [PATCH v2 luajit 0/5] Handle all errors during stitching Sergey Kaplun via Tarantool-patches
  -- strict thread matches above, loose matches on Subject: below --
2024-06-16 10:00 Sergey Kaplun via Tarantool-patches
2024-06-16 10:03 ` 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=3d9dc802-c916-449b-a953-8c91296f5127@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=m.kokryashkin@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2 luajit 0/5] Handle all errors during stitching' \
    /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