From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] pthread_barrier_init: remove the restrict limit
Date: Tue, 18 Oct 2022 14:45:05 +0200 [thread overview]
Message-ID: <Y06f0WK4CeabqTIi@pevik> (raw)
In-Reply-To: <87bkq9mryj.fsf@suse.de>
Hi,
Acked-by: Petr Vorel <pvorel@suse.cz>
> Hello,
> Li Wang <liwang@redhat.com> writes:
> > The restrict keyword tells the compiler that a given pointer
> > does not alias any other pointer in the same context. But this
> > is only supported by C99.
> > To make older platforms compilinng LTP successful, we have to cancel
> > that limitation in function definition.
> > Fix error: https://github.com/linux-test-project/ltp/actions/runs/3263823142/jobs/5363481739
Fixes: f55cb14ca ("syscalls/nice05: Add testcase for nice() syscall")
...
> > Notes:
> > I also considering adding "-std=gun99" for compiling the whole library,
> > but not sure if this could bring a bigger potential impact on
> > LTP.
> It would be nice to at least use C99, but I guess we can wait a bit
> longer until centos7 is EOL.
Exactly.
Also LTP is used by others on embedded, which might still have old toolchain
(although C99 as the default is since gcc 5.x [1], I'm not sure if anybody
really uses gcc 4.9.x [2], we could ask on automated-testing ML after 2024-06 -
CentOS 7 EOL).
Kind regards,
Petr
[1] https://gcc.gnu.org/onlinedocs/gcc-5.5.0/gcc/Standards.html
[2] https://gcc.gnu.org/onlinedocs/gcc-4.9.4/gcc/Standards.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-10-18 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 3:22 [LTP] [PATCH] pthread_barrier_init: remove the restrict limit Li Wang
2022-10-18 8:48 ` Richard Palethorpe
2022-10-18 12:45 ` Petr Vorel [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=Y06f0WK4CeabqTIi@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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