Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread John David Anglin
> > I have to define __STDC_EXT__ under all circumstances to get consistency > > of the long long types in the 32-bit runtime. Previously, gcc for hpux > > tried to mirror the behavior of the HP C compiler wrt long long types. > > Rather then define __STDC_EXT__ all the time I was looking at defi

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread Steve Ellcey
On Tue, 2009-04-14 at 12:18 -0400, John David Anglin wrote: > I have a patch to provide stdint.h on HP-UX that I have been testing. > I have resolved the consistency issues with inttypes.h although there > are some slightly wierd aspects. For example, I found "signed char" and > "char" are inconsi

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread John David Anglin
Attached is my change as it currently stands. Dave -- J. David Anglin dave.ang...@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602) Index: config.gcc === -

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread Andrew Pinski
On Tue, Apr 14, 2009 at 9:18 AM, John David Anglin wrote: > I have a patch to provide stdint.h on HP-UX that I have been testing. > I have resolved the consistency issues with inttypes.h although there > are some slightly wierd aspects.  For example, I found "signed char" and > "char" are inconsis

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread John David Anglin
I have a patch to provide stdint.h on HP-UX that I have been testing. I have resolved the consistency issues with inttypes.h although there are some slightly wierd aspects. For example, I found "signed char" and "char" are inconsistent, yet characters are signed. The specification of some types d

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread Steve Ellcey
On Tue, 2009-04-14 at 15:50 +, Joseph S. Myers wrote: > > Is there a standard way of having GCC provide a new header file > > for a given platform? > > You'd create an alternative setting to "provide", "wrap" and "none", say > "hpux", and add code to handle it. But you shouldn't need to do

Re: Question about creating stdint.h on systems that don't have it

2009-04-14 Thread Joseph S. Myers
On Tue, 14 Apr 2009, Steve Ellcey wrote: > On HP-UX 11.11 there is no stdint.h but I think we want to provide one. > I tried setting use_gcc_stdint to "provide" but that doesn't work > because HP-UX 11.11 already has typedefs in other header files for some > of the things the GCC provided stdint.