From: Jonathan Wakely <jwakely@redhat.com>
Date: Thu, 18 Jan 2024 12:40:52 +0000 (+0000)
Subject: libstdc++: Avoid -Wmaybe-uninitialized warnings in text_encoding.cc
X-Git-Tag: basepoints/gcc-15~1914
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ac913d5d518604c5baf7274bed76e3ff8f3e4c08;p=thirdparty%2Fgcc.git

libstdc++: Avoid -Wmaybe-uninitialized warnings in text_encoding.cc

These variables are only read from if we haven't reached the end of
either range, in which case they're guaranteed to be initialized to the
next alphanumeric character. But we can just initialize them to make the
compiler happy.

libstdc++-v3/ChangeLog:

	* include/bits/unicode.h (__charset_alias_match): Initialize
	__var_a and __var_b.
---

diff --git a/libstdc++-v3/include/bits/unicode.h b/libstdc++-v3/include/bits/unicode.h
index d025d21f3dd9..51bf02e927fc 100644
--- a/libstdc++-v3/include/bits/unicode.h
+++ b/libstdc++-v3/include/bits/unicode.h
@@ -1084,7 +1084,7 @@ inline namespace __v15_1_0
     while (true)
       {
 	// Find the value of the next alphanumeric character in each string.
-	unsigned char __val_a, __val_b;
+	unsigned char __val_a{}, __val_b{};
 	while (__ptr_a != __end_a
 		 && (__val_a = __map(*__ptr_a, __num_a)) == 127)
 	  ++__ptr_a;