<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Hi,</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Sorry for the delayed response. </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
Using -std=gnu++11 in our build scripts when building binutils does fix the issue for us, as mentioned in <a href="https://sourceware.org/bugzilla/show_bug.cgi?id=30867" id="LPlnk421038">https://sourceware.org/bugzilla/show_bug.cgi?id=30867</a> .</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
However, does this need fixing in configure.ac instead?</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Kind regards,</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Vasee</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Roland McGrath <mcgrathr@google.com><br>
<b>Sent:</b> 20 September 2023 01:41<br>
<b>To:</b> Vaseeharan Vinayagamoorthy <Vaseeharan.Vinayagamoorthy@arm.com><br>
<b>Cc:</b> Binutils <binutils@sourceware.org><br>
<b>Subject:</b> Re: [PATCH users/roland/gold-charnn] gold: Use char16_t, char32_t instead of uint16_t, uint32_t as character types</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">I didn't realize that building gold with compilers so old they don't<br>
support C++11 was supported. The GCC source history suggests that<br>
char16_t and char32_t support were introduced in GCC 4.4. I'm not<br>
sure when the default C++ mode was changed to be >= -std=c++11. It<br>
looks to me that the configure stuff should be making it pass<br>
`-std=c++11` if that's required, but I don't know how that test is<br>
coming out in your build. I wonder if using `CXX=g++ -std=c++11`<br>
makes a difference with your version.<br>
</div>
</span></font></div>
</body>
</html>