This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[DOCPATCH] Remove troubles with HP-UX 9 and SunOS 4.


Hey,

 HP-UX 9 and SunOS 4 support has been dropped in the mainline tree.  This
patch removes specific troubles associated with said operating systems.
Other minor changes to trouble.texi are included in this patch as well.

Jim

2003-12-02  James A. Morrison  <ja2morri@uwaterloo.ca>

        * doc/trouble.texi (Interoperation): Remove HP-UX 9 and SunOS 4
        specific documentation.
        Use PA-RISC instead of the HP PA machine.
        (External Bugs): Remove Decstation Ultrix specific documentation.
        (Fixed Headers): Remove SunOS 4 specific documentation.
        Use LynxOS instead of Lynxos.
        (Standard Libraries): Remove SunOS 4 specific documentation.
        Use GNU/Hurd instead of HURD-based GNU systems.


Index: doc/trouble.texi
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/doc/trouble.texi,v
retrieving revision 1.16
diff -u -r1.16 trouble.texi
--- doc/trouble.texi	22 Jul 2003 17:50:13 -0000	1.16
+++ doc/trouble.texi	2 Dec 2003 05:14:04 -0000
@@ -211,51 +211,25 @@
 this problem.
 
 @item
-Sun forgot to include a static version of @file{libdl.a} with some
-versions of SunOS (mainly 4.1).  This results in undefined symbols when
-linking static binaries (that is, if you use @option{-static}).  If you
-see undefined symbols @code{_dlclose}, @code{_dlsym} or @code{_dlopen}
-when linking, compile and link against the file
-@file{mit/util/misc/dlsym.c} from the MIT version of X windows.
-
-@item
-The 128-bit long double format that the SPARC port supports currently
-works by using the architecturally defined quad-word floating point
-instructions.  Since there is no hardware that supports these
-instructions they must be emulated by the operating system.  Long
-doubles do not work in Sun OS versions 4.0.3 and earlier, because the
-kernel emulator uses an obsolete and incompatible format.  Long doubles
-do not work in Sun OS version 4.1.1 due to a problem in a Sun library.
-Long doubles do work on Sun OS versions 4.1.2 and higher, but GCC
-does not enable them by default.  Long doubles appear to work in Sun OS
-5.x (Solaris 2.x).
-
-@item
-On HP-UX version 9.01 on the HP PA, the HP compiler @code{cc} does not
-compile GCC correctly.  We do not yet know why.  However, GCC
-compiled on earlier HP-UX versions works properly on HP-UX 9.01 and can
-compile itself properly on 9.01.
-
-@item
-On the HP PA machine, ADB sometimes fails to work on functions compiled
+On PA-RISC, ADB sometimes fails to work on functions compiled
 with GCC@.  Specifically, it fails to work on functions that use
 @code{alloca} or variable-size arrays.  This is because GCC doesn't
 generate HP-UX unwind descriptors for such functions.  It may even be
 impossible to generate them.
 
 @item
-Debugging (@option{-g}) is not supported on the HP PA machine, unless you use
-the preliminary GNU tools.
+Debugging (@option{-g}) is not supported on PA-RISC, unless you use
+the GNU toolchain.
 
 @item
 Taking the address of a label may generate errors from the HP-UX
-PA assembler.  GAS for the PA does not have this problem.
+PA assembler.  GAS for PA-RISC does not have this problem.
 
 @item
 Using floating point parameters for indirect calls to static functions
 will not work when using the HP assembler.  There simply is no way for GCC
 to specify what registers hold arguments for static functions when using
-the HP assembler.  GAS for the PA does not have this problem.
+the HP assembler.  GAS for PA-RISC does not have this problem.
 
 @item
 In extremely rare cases involving some very large functions you may
@@ -347,7 +321,7 @@
 with BSD Unix: registers 2 through 5 may be clobbered by function calls.
 
 GCC uses the same convention as the Ultrix C compiler.  You can use
-these options to produce code compatible with the Fortran compiler:
+the following options to produce code compatible with the Fortran compiler:
 
 @smallexample
 -fcall-saved-r2 -fcall-saved-r3 -fcall-saved-r4 -fcall-saved-r5
@@ -368,19 +342,6 @@
 
 @itemize @bullet
 @item
-Parse errors may occur compiling X11 on a Decstation running Ultrix 4.2
-because of problems in DEC's versions of the X11 header files
-@file{X11/Xlib.h} and @file{X11/Xutil.h}.  People recommend adding
-@option{-I/usr/include/mit} to use the MIT versions of the header files,
-or fixing the header files by adding this:
-
-@example
-#ifdef __STDC__
-#define NeedFunctionPrototypes 0
-#endif
-@end example
-
-@item
 On various 386 Unix systems derived from System V, including SCO, ISC,
 and ESIX, you may get error messages about running out of virtual memory
 while compiling certain programs.
@@ -680,25 +641,7 @@
 shortcut.)
 
 @item
-On some systems, in particular SunOS 4, header file directories contain
-machine-specific symbolic links in certain places.  This makes it
-possible to share most of the header files among hosts running the
-same version of SunOS 4 on different machine models.
-
-The programs that fix the header files do not understand this special
-way of using symbolic links; therefore, the directory of fixed header
-files is good only for the machine model used to build it.
-
-In SunOS 4, only programs that look inside the kernel will notice the
-difference between machine models.  Therefore, for most purposes, you
-need not be concerned about this.
-
-It is possible to make separate sets of fixed header files for the
-different machine models, and arrange a structure of symbolic links so
-as to use the proper set, but you'll have to do this by hand.
-
-@item
-On Lynxos, GCC by default does not fix the header files.  This is
+On LynxOS, GCC by default does not fix the header files.  This is
 because bugs in the shell cause the @code{fixincludes} script to fail.
 
 This means you will encounter problems due to bugs in the system header
@@ -718,16 +661,10 @@
 standards, then your programs might get warnings (especially when using
 @option{-Wall}) that you don't expect.
 
-For example, the @code{sprintf} function on SunOS 4.1.3 returns
-@code{char *} while the C standard says that @code{sprintf} returns an
-@code{int}.  The @code{fixincludes} program could make the prototype for
-this function match the Standard, but that would be wrong, since the
-function will still return @code{char *}.
-
 If you need a Standard compliant library, then you need to find one, as
 GCC does not provide one.  The GNU C library (called @code{glibc})
 provides ISO C, POSIX, BSD, SystemV and X/Open compatibility for
-GNU/Linux and HURD-based GNU systems; no recent version of it supports
+GNU/Linux and GNU/Hurd systems; no recent version of it supports
 other systems, though some very old versions did.  Version 2.2 of the
 GNU C library includes nearly complete C99 support.  You could also ask
 your operating system vendor if newer libraries are available.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]