From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, Sergey Kaplun <skaplun@tarantool.org>, max.kokryashkin@gmail.com Subject: [Tarantool-patches] [PATCH luajit 1/3][v2] Add 'cc' file type for saving bytecode. Date: Thu, 9 Nov 2023 16:08:11 +0300 [thread overview] Message-ID: <350137386d2ce8f959cfe452e1355998fded73dd.1699534835.git.sergeyb@tarantool.org> (raw) In-Reply-To: <cover.1699534835.git.sergeyb@tarantool.org> From: Mike Pall <mike> Contributed by Sergey Bronnikov. #1105 (cherry picked from commit e826d0c101d750fac8334d71e221c50d8dbe236c) The patch adds a file type `cc` that allows exporting byte code directly to a file with extension `.cc`. Sergey Bronnikov: * added the description Part of tarantool/tarantool#9145 --- doc/running.html | 3 ++- src/jit/bcsave.lua | 4 ++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/running.html b/doc/running.html index 666b0abc..7868efab 100644 --- a/doc/running.html +++ b/doc/running.html @@ -124,7 +124,8 @@ file name: </p> <ul> <li><tt>c</tt> — C source file, exported bytecode data.</li> -<li><tt>h</tt> — C header file, static bytecode data.</li> +<li><tt>cc</tt> — C++ source file, exported bytecode data.</li> +<li><tt>h</tt> — C/C++ header file, static bytecode data.</li> <li><tt>obj</tt> or <tt>o</tt> — Object file, exported bytecode data (OS- and architecture-specific).</li> <li><tt>raw</tt> or any other extension — Raw bytecode file (portable). diff --git a/src/jit/bcsave.lua b/src/jit/bcsave.lua index 41081184..48b2329c 100644 --- a/src/jit/bcsave.lua +++ b/src/jit/bcsave.lua @@ -37,7 +37,7 @@ Save LuaJIT bytecode: luajit -b[options] input output -- Stop handling options. - Use stdin as input and/or stdout as output. -File types: c h obj o raw (default) +File types: c cc h obj o raw (default) ]] os.exit(1) end @@ -63,7 +63,7 @@ end ------------------------------------------------------------------------------ local map_type = { - raw = "raw", c = "c", h = "h", o = "obj", obj = "obj", + raw = "raw", c = "c", cc = "c", h = "h", o = "obj", obj = "obj", } local map_arch = { -- 2.34.1
next prev parent reply other threads:[~2023-11-09 13:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-09 13:06 [Tarantool-patches] [PATCH luajit 0/3][v2] Fix C file generation in jit.bcsave Sergey Bronnikov via Tarantool-patches 2023-11-09 13:08 ` Sergey Bronnikov via Tarantool-patches [this message] 2023-11-13 7:04 ` [Tarantool-patches] [PATCH luajit 1/3][v2] Add 'cc' file type for saving bytecode Sergey Kaplun via Tarantool-patches 2023-11-15 9:39 ` Sergey Bronnikov via Tarantool-patches 2023-11-09 13:08 ` [Tarantool-patches] [PATCH luajit 2/3][v2] test: set dependencies to tarantool-tests explicitly Sergey Bronnikov via Tarantool-patches 2023-11-13 7:10 ` Sergey Kaplun via Tarantool-patches 2023-11-15 11:34 ` Sergey Bronnikov via Tarantool-patches 2023-11-09 13:08 ` [Tarantool-patches] [PATCH luajit 3/3][v2] Fix C file generation in jit.bcsave Sergey Bronnikov via Tarantool-patches 2023-11-13 7:10 ` Sergey Kaplun via Tarantool-patches 2024-02-29 7:40 ` [Tarantool-patches] [PATCH luajit 0/3][v2] " Igor Munkin 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=350137386d2ce8f959cfe452e1355998fded73dd.1699534835.git.sergeyb@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=max.kokryashkin@gmail.com \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 1/3][v2] Add '\''cc'\'' file type for saving bytecode.' \ /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