On Tue, 12 Jun 2012, rbmj wrote: > On 06/12/2012 11:47 AM, Joseph S. Myers wrote: > > On Wed, 6 Jun 2012, rbmj wrote: > > > > > The stdint.h doesn't have all the typedefs needed for standards > > > compliance, so add a hack that adds all of the needed typedefs > > > to be fully compliant to the standard. Fixes broken libstdc++. > > If you're touching VxWorks stdint.h perhaps you could also define the > > relevant target macros for GCC to have built-in knowledge of the types? > > This is needed for the Fortran C bindings to work correctly, at least, and > > ensures char16_t and char32_t (C11/C++11) are correct as well. (You could > > then set use_gcc_stdint to "wrap" in config.gcc if you want to use GCC's > > stdint.h for freestanding compilations.) > I would be happy to, but I'm not aware of what macros those are. If you could > point me to some documentation or explain to me what macros I need to define > I'll update the patch.
<http://gcc.gnu.org/ml/gcc/2009-04/msg00000.html> was my original announcement for target OS maintainers. You should define the same set of macros as in gcc/config/glibc-stdint.h (but, obviously, to values appropriate to VxWorks), plus INTMAX_TYPE and UINTMAX_TYPE if the default values of those macros are wrong for VxWorks, and make sure all the c99-stdint-*.c tests pass. -- Joseph S. Myers jos...@codesourcery.com
