Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <m.kokryashkin@tarantool.org>,
	Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH luajit 0/4] Fixes for ctypes with attributes
Date: Mon,  3 Jun 2024 17:33:58 +0300	[thread overview]
Message-ID: <cover.1717424008.git.skaplun@tarantool.org> (raw)

The first two patches fix the parsing and calculation for size and align
for C++ references. The last two patches fix the `ffi.metatype()`
behaviour for C types with attributes.

Branch: https://github.com/tarantool/luajit/tree/skaplun/lj-861-1005-ffi-fixes

Be aware that CI is red due to infrastructure problems with aarch64
hosts and being unable to download manifests for ecosystem integrational
CI.

Related issues:
* https://github.com/tarantool/tarantool/issues/9924
* https://github.com/LuaJIT/LuaJIT/issues/861
* https://github.com/LuaJIT/LuaJIT/issues/1005

Mike Pall (4):
  FFI: Fix ffi.alignof() for reference types.
  FFI: Fix sizeof expression in C parser for reference types.
  FFI: Allow ffi.metatype() for typedefs with attributes.
  FFI: Fix ffi.metatype() for non-raw types.

 src/lib_ffi.c                                 |  6 +--
 src/lj_cparse.c                               |  2 +-
 src/lj_ctype.c                                |  8 +++
 src/lj_ctype.h                                |  1 +
 .../lj-861-ctype-attributes.test.lua          | 53 +++++++++++++++++++
 5 files changed, 66 insertions(+), 4 deletions(-)
 create mode 100644 test/tarantool-tests/lj-861-ctype-attributes.test.lua

-- 
2.45.1


             reply	other threads:[~2024-06-03 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 14:33 Sergey Kaplun via Tarantool-patches [this message]
2024-06-03 14:33 ` [Tarantool-patches] [PATCH luajit 1/4] FFI: Fix ffi.alignof() for reference types Sergey Kaplun via Tarantool-patches
2024-06-11 15:40   ` Sergey Bronnikov via Tarantool-patches
2024-06-14 12:19   ` Maxim Kokryashkin via Tarantool-patches
2024-06-03 14:34 ` [Tarantool-patches] [PATCH luajit 2/4] FFI: Fix sizeof expression in C parser " Sergey Kaplun via Tarantool-patches
2024-06-11 15:42   ` Sergey Bronnikov via Tarantool-patches
2024-06-14 12:21   ` Maxim Kokryashkin via Tarantool-patches
2024-06-03 14:34 ` [Tarantool-patches] [PATCH luajit 3/4] FFI: Allow ffi.metatype() for typedefs with attributes Sergey Kaplun via Tarantool-patches
2024-06-11 15:48   ` Sergey Bronnikov via Tarantool-patches
2024-06-13  7:34     ` Sergey Kaplun via Tarantool-patches
2024-06-13 15:14       ` Sergey Bronnikov via Tarantool-patches
2024-06-14 12:39   ` Maxim Kokryashkin via Tarantool-patches
2024-06-03 14:34 ` [Tarantool-patches] [PATCH luajit 4/4] FFI: Fix ffi.metatype() for non-raw types Sergey Kaplun via Tarantool-patches
2024-06-11 15:50   ` Sergey Bronnikov via Tarantool-patches
2024-06-14 12:40   ` Maxim Kokryashkin via Tarantool-patches
2024-07-09  8:03 ` [Tarantool-patches] [PATCH luajit 0/4] Fixes for ctypes with attributes 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.1717424008.git.skaplun@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 luajit 0/4] Fixes for ctypes with attributes' \
    /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