From: Suneeth D <Suneeth.D@amd.com>
To: <linux-rt-users@vger.kernel.org>
Cc: <williams@redhat.com>, <jkacur@redhat.com>,
<bigeasy@linutronix.de>, Suneeth D <Suneeth.D@amd.com>
Subject: [PATCH v2] cyclictest: Fix BUILD failure for GCC_VER < 14
Date: Fri, 11 Sep 2026 05:29:29 +0000 [thread overview]
Message-ID: <20260911052929.2565-1-Suneeth.D@amd.com> (raw)
timerthread() uses bool, true, and false. Those are keywords in C23,
which became GCC's default in GCC 15 (-std=gnu23), so the file compiles
there without stdbool.h. With the earlier versions of GCC the default is gnu17,
where they are provided by <stdbool.h>, and the build fails without it.
Fixes: 98fcd661ac59 (cyclictest: Acquire a lock before invoking pthread_cond_signal())
Closes: https://lore.kernel.org/linux-rt-users/4ce24139-5f7e-4180-a290-bcc15fb4f559@amd.com/
Signed-off-by: Suneeth D <Suneeth.D@amd.com>
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
Changes since v1 ---> v2:
* Modify commit message to include Tomas Glozar's note on default
changes happened since GCC 15.
based on: fd45df830803dd7f26d2ca8bdcf05fd7e0d62ae8 (rt-tests/main)
src/cyclictest/cyclictest.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
index 99194378f946..58b56bcede0f 100644
--- a/src/cyclictest/cyclictest.c
+++ b/src/cyclictest/cyclictest.c
@@ -15,6 +15,7 @@
#include <stdlib.h>
#include <stdint.h>
#include <stdarg.h>
+#include <stdbool.h>
#include <unistd.h>
#include <fcntl.h>
#include <getopt.h>
--
2.43.0
next reply other threads:[~2026-09-11 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 5:29 Suneeth D [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-02 9:58 [PATCH v2] cyclictest: Fix BUILD failure for GCC_VER < 14 Suneeth D
2026-09-03 18:39 ` John Kacur
2026-09-10 18:06 ` John Kacur
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=20260911052929.2565-1-Suneeth.D@amd.com \
--to=suneeth.d@amd.com \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.