incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Liviu Nicoara <nico...@roguewave.com>
Subject Re: Any ideas on these StdLib build errors?
Date Wed, 08 Feb 2006 22:32:11 GMT
What's the compile line?

Nicole Willson wrote:
> NO! It's MY test case. :)  I actually streamlined it a little more. Ok, here
> it is:
> 
> //Test case for ICE on SuSE 9sp2 with xlC 8.0
> #include <string.h>
> 
> template <class _InternT> class codecvt_byname
> {
> public:
>     explicit codecvt_byname (){}
> };
> 
> template<> class codecvt_byname<wchar_t>
> {
> public:
>     explicit codecvt_byname ();
> };
> 
> codecvt_byname<wchar_t>::codecvt_byname ()
> {
> static struct {int flag;} mods = {1};
> int flags = 0;
> flags = mods.flag;
> }
> 
> //End Test case for ICE on SuSE 9sp2 with xlC 8.0
> 
> The error shows up while trying to build stdlib - specifically wcodecvt.cpp.
> 
> Nicole Willson
> Consulting Engineer
> Rogue Wave Software, Inc.
> A Division of Quovadx
> 303-545-3210
> 
> 
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com] 
> Sent: Wednesday, February 08, 2006 3:14 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: Any ideas on these StdLib build errors?
> 
> Nicole Willson wrote:
> 
>>Ok, I have a test case for this ICE.  It's a very specific combination of
>>#include <string.h>, a specialized template class, and an array of static
>>struct.  So, I can see how the bug got past them.  However, I'm not sure
> 
> how
> 
>>to workaround this bug.  I need all of these components together.  I'll
> 
> see
> 
>>if I can somehow not use string.h
> 
> 
> I'm sure we can come up with a way if you could just show us the test
> case... ;-)
> 
> Martin
> 


Mime
View raw message