public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r12-7508] libstdc++: vxworks: remove stray <iostream> include
@ 2022-03-07 7:45 Rasmus Villemoes
0 siblings, 0 replies; only message in thread
From: Rasmus Villemoes @ 2022-03-07 7:45 UTC (permalink / raw)
To: gcc-cvs, libstdc++-cvs
https://gcc.gnu.org/g:0f0b42896196315acfc636b1e535cda4ee283646
commit r12-7508-g0f0b42896196315acfc636b1e535cda4ee283646
Author: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Date: Fri Mar 4 09:18:39 2022 +0100
libstdc++: vxworks: remove stray <iostream> include
There doesn't seem to be any reason for this TU to include
<iostream>, and it causes errors when the resulting libstdc++ is used
on our VxWorks 5.5 target - presumably because now libstdc++ itself
contains an instance of std::ios_base::Init. Which should be mostly
harmless, but apparently isn't, and from a QoI viewpoint should
probably be avoided anyway.
libstdc++-v3/ChangeLog:
* config/locale/vxworks/ctype_members.cc: Remove <iostream>
include.
Diff:
---
libstdc++-v3/config/locale/vxworks/ctype_members.cc | 1 -
1 file changed, 1 deletion(-)
diff --git a/libstdc++-v3/config/locale/vxworks/ctype_members.cc b/libstdc++-v3/config/locale/vxworks/ctype_members.cc
index 82569d075c6..d8ca551078d 100644
--- a/libstdc++-v3/config/locale/vxworks/ctype_members.cc
+++ b/libstdc++-v3/config/locale/vxworks/ctype_members.cc
@@ -33,7 +33,6 @@
#include <cstdlib>
#include <cstring>
#include <cstdio>
-#include <iostream>
namespace std _GLIBCXX_VISIBILITY(default)
{
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-03-07 7:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-07 7:45 [gcc r12-7508] libstdc++: vxworks: remove stray <iostream> include Rasmus Villemoes
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).