Creating builtin platform specific typedefs

[Steve Ellcey]

> Trying to avoid running fixincludes is risky.  If gcc and HPUX ever get 
> out of step, then gcc starts failing, possibly in subtle ways.  It would 
> be a shame if HP releases a new version of HPUX, and then we find that 
> the last gcc release doesn't work on it because we aren't running 
> fixincludes.
> 
> Jim

Well, things don't work all that well now with fixincludes.  You build
GCC on HP-UX version X and it creates copies of HP-UX header files.  If
you then install that GCC (without rebuilding) on HP-UX version X+1, it
won't work because one of the system headers that GCC made a copy of
changed and the private GCC header file is out of sync with the public
OS version of the header file.  If you don't run fixincludes and don't
have any private hacked header files then you are more likely to have a
single GCC that will work on multiple releases of the OS without being
built specially for each one.

Steve Ellcey
sje@cup.hp.com