--- Comment #6 from paolo dot carlini at oracle dot com 2010-02-13 23:45
---
I gather that SUN fixed this problem more than 2 years ago, in Solaris 10
Update 4, see eg:
http://blogs.sun.com/mandalika/entry/solaris_workaround_to_stdio_s
Given that, I'm going to mark this as WONTFIX for
--- Comment #5 from paolo dot carlini at oracle dot com 2010-02-05 13:20
---
Eric, Rainer, do you have any comment on this? For sure it's very hard to
provide an implementation working around the reported Solaris limitation
without breaking the binary compatibility. Does the limitation
--- Comment #4 from pcarlini at suse dot de 2006-04-19 16:38 ---
(In reply to comment #3)
> 1.
> Agree, I wouldn't call it a bug. But I don't know where to put it other than
> here.
Maybe report it to Sun?
> 2.
> I don't think you have to use fopen for fstream defined by the C++
> sta
--- Comment #3 from zhong dot xie at yahoo dot ca 2006-04-19 16:08 ---
1.
Agree, I wouldn't call it a bug. But I don't know where to put it other than
here.
2.
I don't think you have to use fopen for fstream defined by the C++
standard.(see the details below)
3.
It is solaris itself l
--- Comment #2 from pcarlini at suse dot de 2006-04-19 08:59 ---
Indeed, not a libstdc++ bug. And, by the way, per the Standard (27.8.1.3/2) we
have to use fopen.
--
pcarlini at suse dot de changed:
What|Removed |Added
-
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-04-19 02:44 ---
Isn't this really a Solaris bug in that fopen is limited and not really a
libstdc++ bug? And that libstdc++ is just limited by the OS.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27198
