------- Comment #10 from davek at gcc dot gnu dot org  2010-01-27 12:29 -------
(In reply to comment #8)
> Also note: something is going on with char16_t / char32_t which I do not
> understand at all, at the moment: in that tr1_impl code I did not setup the
> specializations for char16_t / char32_t conditionally to some configure check
> or header included or actual target, because I was assuming that in C++, in
> C++0x mode, those are **always** available. Is that not true? And we didn't
> realize for all this time?!?

  I don't understand.  There's no equivalent in g++ of the builtin stdint types
that Joseph added for C, so if you don't include the header that defines them,
no definitions should be available, yes?

> Note, actually the error means the submitter is passing -std=c++0x on the
> command line.

That didn't make any difference to the undefined types errors, but it did fix a
lot of the knock-on errors I was seeing.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42880

Reply via email to