From ed38fadfbe79486cfcf556851bd3b2018b179ac3 Mon Sep 17 00:00:00 2001
From: Joel Sherrill <joel@rtems.org>
Date: Fri, 17 Oct 2025 15:05:37 -0500
Subject: [PATCH] spec/build/cpukit/optwarn.yml: Warning flags to match current
 state

All but ~50 warnings have been fixed if you account for unmerged
MRs. These settings should give a warning free build given the
current state.

       Warnings by Type
=================================
   2 -Wshift-negative-value
   3 -Wenum-conversion
   7 -Wcast-function-type
   7 -Wmissing-field-initializers
   8 -Wclobbered
  32 -Wtype-limits
---
 spec/build/cpukit/optwarn.yml | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/spec/build/cpukit/optwarn.yml b/spec/build/cpukit/optwarn.yml
index ad4296ae84..4aa34e768f 100644
--- a/spec/build/cpukit/optwarn.yml
+++ b/spec/build/cpukit/optwarn.yml
@@ -12,7 +12,20 @@ default:
 - enabled-by: true
   value:
   - -Wall
-  - -Wempty-body
+  - -Wextra
+# We currently have not addressed all of the cases for these warnings.
+# Use -Wno- for the ones remaining. There are ~50 left to resolve
+# Afor -Wextra
+#     -Wclobbered is issue #5364
+#     -Wmissing-field-initializers is resolved by MR801
+  - -Wno-cast-function-type
+  - -Wno-clobbered
+  - -Wno-enum-conversion
+  - -Wno-ignored-qualifiers
+  - -Wno-missing-field-initializers
+  - -Wno-shift-negative-value
+  - -Wno-sign-compare
+  - -Wno-type-limits
   - -Werror
 description: |
   Warning flags passed to the C and C++ compiler