public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/arm/morello/main] scripts: Use bool in tunables initializer Date: Thu, 27 Oct 2022 13:48:36 +0000 (GMT) [thread overview] Message-ID: <20221027134837.3783B3851523@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ed4d5c56b87413be83ac085b3eae52b592fca5cb commit ed4d5c56b87413be83ac085b3eae52b592fca5cb Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Tue Jun 8 14:03:38 2021 +0100 scripts: Use bool in tunables initializer The initializer for a tunable_t set the bool initialized flag to NULL. This causes a build failure when pointer to bool conversion warns. Diff: --- scripts/gen-tunables.awk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/gen-tunables.awk b/scripts/gen-tunables.awk index fa63e86d1a..d6de100df0 100644 --- a/scripts/gen-tunables.awk +++ b/scripts/gen-tunables.awk @@ -177,7 +177,7 @@ END { n = indices[2]; m = indices[3]; printf (" {TUNABLE_NAME_S(%s, %s, %s)", t, n, m) - printf (", {TUNABLE_TYPE_%s, %s, %s}, {%s}, NULL, TUNABLE_SECLEVEL_%s, %s},\n", + printf (", {TUNABLE_TYPE_%s, %s, %s}, {%s}, false, TUNABLE_SECLEVEL_%s, %s},\n", types[t,n,m], minvals[t,n,m], maxvals[t,n,m], default_val[t,n,m], security_level[t,n,m], env_alias[t,n,m]); }
next reply other threads:[~2022-10-27 13:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 13:48 Szabolcs Nagy [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-11-23 14:38 Szabolcs Nagy 2022-10-26 15:10 Szabolcs Nagy 2022-08-05 19:29 Szabolcs Nagy
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=20221027134837.3783B3851523@sourceware.org \ --to=nsz@sourceware.org \ --cc=glibc-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).