Re: [Mingw-users] [BUG] - member is template<T>: ice in 4.2.1-sjlj (mingw32-2), bad compilation in 3

[Greg Chicares <gchicares@xxxxxxxxxxxxx>]

On 2007-12-20 15:21Z, John Brown wrote:
> 
> OK. My code was wrong, but it's still a gcc bug, right?
> 
> 1) gcc 3.4.5 compiled it when it should not have
> 2) gcc 4.1.2 gave an ICE instead of a normal error message

Certainly they're both anomalies, but not as serious as failing
to compile code that is not anomalous. ICE-on-invalid reports
aren't always viewed as urgent by the maintainers: they fulfill
the 1.4/2 requirement to "issue at least one diagnostic message"
even though not in an ideal way, so they aren't compliance
violations as defined in that section.

> Why does gcc have to use such ugly typenames?

http://groups.google.com/groups?as_q=type_info+name&as_ugroup=comp.lang.c%2B%2B.moderated

> I understand that the standard does not impose a format on the name, but it
> would have been better if it used the "real" name instead of the mangled
> name. I don't know gcc's name-mangling algorithm, so even if I were inclined,
> I cannot translate it myself.

Call __cxa_demangle(). My notes on that are in the 'detail'
namespace here:

http://cvs.savannah.gnu.org/viewvc/lmi/lmi/rtti_lmi.hpp?view=markup

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users