[pushed, wwwdocs] gcc-15/porting_to: prefer to for non-std:: types

[David Malcolm]

My tests showed the removal of internal uses of <cstdint> from
stdlibc++ usually manifests in complaints about unqualified types like
"uint8_t", rather than "std::uint8_t" (and unfortunately the fix-it
hint gets this wrong; see PR c++/110930).

I've taken the liberty of pushing this patch to the website to
recommend <stdint.h> rather than <cstdint>

Hope this wording is an improvement.
Dave

---
 htdocs/gcc-15/porting_to.html | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/htdocs/gcc-15/porting_to.html b/htdocs/gcc-15/porting_to.html
index 7344afa5..39598b93 100644
--- a/htdocs/gcc-15/porting_to.html
+++ b/htdocs/gcc-15/porting_to.html
@@ -82,11 +82,13 @@ As such, C++ programs that used standard library components 
without
 including the right headers will no longer compile.
 </p>
 <p>
-In particular, the following header is used less widely within libstdc++ and
+In particular, the following headers are used less widely within libstdc++ and
 may need to be included explicitly when compiling with GCC 15:
 </p>
 <ul>
-<li> <code>&lt;cstdint&gt;</code>
+<li> <code>&lt;stdint.h&gt;</code>
+  (for <code>int8_t</code>, <code>int32_t</code> etc.)
+  and <code>&lt;cstdint&gt;</code>
   (for <code>std::int8_t</code>, <code>std::int32_t</code> etc.)
 </li>
 </ul>
-- 
2.46.0