diff options
| author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2022-03-04 09:18:39 +0100 |
|---|---|---|
| committer | Rasmus Villemoes <rv@rasmusvillemoes.dk> | 2022-03-07 08:44:46 +0100 |
| commit | 0f0b42896196315acfc636b1e535cda4ee283646 (patch) | |
| tree | 171a86289d0d99ed8b5d256cbda4b23e0adfc4ae /gcc | |
| parent | aad3d9351890f6190a4ea61260b6d93ad1f372c4 (diff) | |
| download | gcc-0f0b42896196315acfc636b1e535cda4ee283646.zip gcc-0f0b42896196315acfc636b1e535cda4ee283646.tar.gz gcc-0f0b42896196315acfc636b1e535cda4ee283646.tar.bz2 | |
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.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions