From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: Jan Kara <jack@suse.cz>,
Richard Palethorpe <rpalethorpe@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/3] fanotify10: Add support for multiple event files
Date: Mon, 21 Nov 2022 10:39:46 +0100 [thread overview]
Message-ID: <Y3tHYo/iQ6t6D7SR@rei> (raw)
In-Reply-To: <Y3tF2XF1xVlOE3fA@pevik>
Hi!
> > > > +#define foreach_path(tc, buf, pname) \
> > > > + for (int piter = 0; format_path_check((buf), (tc)->pname##_fmt, \
> > > Unfortunately we still support C99 due old compiler on CentOS 7,
> > > therefore int piter needs to be defined outside of for loop.
>
> > Hum, but variable declaration in the for loop is part of C99 standard (as
> > the error message also says). So did you want to say you are compiling
> > against C89 standard? And CentOS 7 ships with GCC 4.8.5 AFAICS which should
> > be fully C99 compliant BTW. So what's the situation here?
> I'm sorry, I didn't express clearly myself. Yes, 4.8.5 supports C99,
> but the default is C90 [1].
>
> > That being said I can workaround the problem in the macro, it will just be
> > somewhat uglier. So before doing that I'd like to understand whether
> > following C89 is really required...
>
> I'm don't remember why we have just not specified -std=... already, Cyril had
> some objections, thus Cc him.
I think that at the time there stil was even older compiler we had to
support. I guess that we can add -std=c99 now.
So I would propose adding -std=c99 into CFLAGS and see if anyone would
complain.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-21 9:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:47 [LTP] [PATCH 0/3] Make fanotify10 test yet more reliable Jan Kara
2022-11-15 12:47 ` [LTP] [PATCH 1/3] fanotify10: Use named initializers Jan Kara
2022-11-15 12:47 ` [LTP] [PATCH 2/3] fanotify10: Add support for multiple event files Jan Kara
2022-11-17 15:58 ` Petr Vorel
2022-11-21 9:14 ` Jan Kara
2022-11-21 9:33 ` Petr Vorel
2022-11-21 9:39 ` Cyril Hrubis [this message]
2022-11-22 8:19 ` Petr Vorel
2022-11-22 10:10 ` Petr Vorel
2022-11-21 9:53 ` Jan Kara
2022-11-21 14:24 ` Richard Palethorpe
2022-11-22 8:17 ` Petr Vorel
2022-11-22 8:57 ` Richard Palethorpe
2022-11-21 15:04 ` Cyril Hrubis
2022-11-22 12:10 ` Richard Palethorpe
2022-11-22 12:56 ` Cyril Hrubis
2022-11-15 12:47 ` [LTP] [PATCH 3/3] fanotify10: Make evictable marks tests more reliable Jan Kara
2022-11-16 2:17 ` Pengfei Xu
2022-11-16 10:58 ` Jan Kara
2022-11-16 16:32 ` Amir Goldstein
2022-11-17 15:50 ` Petr Vorel
2022-11-21 15:09 ` Cyril Hrubis
2022-11-22 10:30 ` Petr Vorel
2022-11-22 12:42 ` Cyril Hrubis
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=Y3tHYo/iQ6t6D7SR@rei \
--to=chrubis@suse.cz \
--cc=jack@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rpalethorpe@suse.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox