On 11/10/2014 10:59 AM, Joseph Myers wrote: > On Mon, 10 Nov 2014, Joel Sherrill wrote: > >> On 11/10/2014 10:32 AM, Joseph Myers wrote: >>> On Sat, 8 Nov 2014, Paolo Carlini wrote: >>> >>>> Good. Sorry, if I missed some relatively recent development: is now GCC >>>> installing its own stdint.h on *all* the supported targets, thus we can >>>> safely >>> No; I sent a list of targets missing the information in >>> <https://gcc.gnu.org/ml/gcc-patches/2013-06/msg00248.html> (possibly out >>> of date now, but the goal there of unifying uint32_type_node and >>> c_uint32_type_node etc. still applies). >>> >> I just submitted a patch using stdint.h and uintptr_t to gcc-patches. >> I think this fixes the code in a standard way. I don't know what to >> do about the list of targets you cited which don't support that. > Well, some of them may in fact have their own stdint.h provided by the OS, > or not use libstdc++, but if they use libstdc++ and don't have stdint.h, > the correct fix is for the OS maintainer to add the necessary GCC support > for providing stdint.h. > I will leave it for you all to decide to push my patch or switch to something like Paolo's trick.
-- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985