------- Comment #33 from davek at gcc dot gnu dot org 2010-01-27 16:07 ------- (In reply to comment #32) > Dave, the issue with char16_t / cha32_t is cygwin specific, and, to be really > honest, personally I'm not interested in cygwin much. My suggestion is just > making sure the C++ front-end is fine for cygwin vs char16_t / char32_t, ans > simply running the C++ testsuite should be more than enough. If eventually you > come to the conclusion that some special workrounds in the C++ runtime is > needed to support cygwin, let's discuss that separately.
I'll run the testsuite on today's build and see if it differs from my most recent run, which was pretty clean. More later when that finishes. (I thought the problem was that the preprocessed testcase was prepared using -std=c++0x and therefore embeds all the #ifdef decisions made using that standard, and so the preprocessed testcase must be compiled using the same -std= which was used to prepare it.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42880
