------- Comment #4 from paolo dot carlini at oracle dot com 2008-07-09 11:18 ------- (In reply to comment #3) > a) The problem does not exist on gcc 4.2 (Intel), but I do not have a > 4.2 PPC x-compiler - only 4.0. So I cannot confirm a x-compile issue in 4.2.
Ok. > b) It would be very helpful if you would tell me GCC's support policy. > i.e. How far back from the latest release will bug reports be > considered? In this case, I've reported a bug only three minor releases > back of the latest [4.2 at the time] and you seem to be saying "too old". Well, it's easy, we just closed 4_1-branch, 4_0-branch has been closed a lot of time ago. That means, you can certainly find somehow a volunteer working on the release branch you care about, but since the branch is closed, the fix will not appear in any further official release from the branch. > c) I identified the problem as "C++", but more correctly it is an STL > problem. Wrongly. There is no "STL" mention in the C++ Standard in force (C++98 + TC1), "STL" is a legacy acronym dating back to the HP / SGI times. The problem would be, in case, libstdc++, that this our (GNU) implementation of the C++ Standard Library. > d) If and when I can reproduce the problem in a current release, I'll > let you know. Ok. For now, I'm going to close this one, for lack, to date, of compelling evidence. Thanks again. -- paolo dot carlini at oracle dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36567