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>,
	Evgeniy Temirgaleev <e.temirgaleev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] test: fix libfficcall compilation for old GCC
Date: Tue, 9 Jun 2026 16:55:38 +0300	[thread overview]
Message-ID: <4b4838ea-4ada-4bf5-8e20-8083133139df@tarantool.org> (raw)
In-Reply-To: <20260608102318.4068317-1-skaplun@tarantool.org>

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

Hello, Sergey,

Thanks for the patch! LGTM with a minor comment.

Sergey

On 6/8/26 13:23, Sergey Kaplun wrote:
> On CentOS 7 GCC has no std=c99 by default. This leads to compilation
> warnings and errors for ‘for’ loop initial declarations. This patch
> fixes that by declaring the variable out of the loop body.
> ---
>
> Branch:https://github.com/tarantool/luajit/tree/skaplun/gh-noticket-fix-tests-old-gcc
> CI failure:https://github.com/tarantool/luajit/actions/runs/27124968515/job/80063067169#step:6:10593
>
>   test/tarantool-tests/ffi-ccall/libfficcall.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/test/tarantool-tests/ffi-ccall/libfficcall.c b/test/tarantool-tests/ffi-ccall/libfficcall.c
> index 2145b556..129bc75d 100644
> --- a/test/tarantool-tests/ffi-ccall/libfficcall.c
> +++ b/test/tarantool-tests/ffi-ccall/libfficcall.c
> @@ -307,7 +307,8 @@ int test_2_large_agg_a16(int x, large_agg_a16 s1, large_agg_a16 s2)
>   	const int *v1 = s1.v;
>   	const int *v2 = s2.v;
>   	int sum = x;
> -	for (int i = 0; i < lengthof(s1.v); i++) {
> +	int i = 0;
> +	for (; i < lengthof(s1.v); i++) {

isn't better declaring outside the loop and define in a loop?

int i;
for (i = 0; i < lengthof(s1.v); i++) {

It looks more familiar this way. Feel free to ignore.

>   		sum += v1[i] + v2[i];
>   	}
>   	return sum;

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

      reply	other threads:[~2026-06-09 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 10:23 Sergey Kaplun via Tarantool-patches
2026-06-09 13:55 ` Sergey Bronnikov via Tarantool-patches [this message]

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=4b4838ea-4ada-4bf5-8e20-8083133139df@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=e.temirgaleev@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] test: fix libfficcall compilation for old GCC' \
    /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