------- Comment #20 from davek at gcc dot gnu dot org 2010-01-27 12:48 ------- (In reply to comment #18) > (In reply to comment #17) > > So, as a matter of fact, char16_t and char32_t normally work on cygwin too. > > Ah, hang on. I may have got some of my revision numbers mixed up there. (I > have a number of objdirs lying around built at various times from the same > sandbox.) > > Here are two fairly recent ones:
Those versions are: gcc version 4.5.0 20100121 (experimental) (GCC) gcc version 4.5.0 20100125 (experimental) (GCC) So I can confirm the specialisation error that you've also seen on x86_64-linux has also appeared on cygwin, but I can't yet confirm any bug about the char types. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42880