Patch-ID# 101205-02 Keywords: C, C++, FORTRAN, x86, assembler, Teamware Synopsis: ProCompilers 2.0.1: Jumbo x86 patch for C, C++, FORTRAN Date: Mar/04/94 SunOS release: 5.1_x86 Unbundled Product: ProCompilers (C, C++, Fortran) Unbundled Release: 2.0.1 Topic: This patch fixes several bugs which have been discovered in ProCompilers C and FORTRAN. BugId's fixed with this patch: 1146759 1143448 1142637 1138945 1145656 1129998 1145518 1144083 1145077 1147492 1141894 1147801 1144138 1145699 1141047 1143420 1145276 1142916 1140882 1137382 1147505 1138750 1136155 1129998 1136076 1138159 1132143 1136254 3002510 3002521 1133160 1133163 1133162 1137892 1135079 1134812 1129279 1130949 1132527 1132803 1133016 1129802 1129805 1131649 1133150 1135847 1136321 1136398 1135125 1137487 Changes incorporated in this version: Relevant Architectures ('arch -k' values if kernel specific): i86pc Other patches which conflict with this patch: This patch obsoleted by: Files included with this patch: /opt/SUNWspro/SC2.0.1/acomp /opt/SUNWspro/SC2.0.1/cc /opt/SUNWspro/SC2.0.1/cg386 /opt/SUNWspro/SC2.0.1/cg386_f /opt/SUNWspro/SC2.0.1/codegen /opt/SUNWspro/SC2.0.1/crt1.o /opt/SUNWspro/SC2.0.1/f77 /opt/SUNWspro/SC2.0.1/f80387/libp/libm.a /opt/SUNWspro/SC2.0.1/f80387/libm.il /opt/SUNWspro/SC2.0.1/f80387/__fstd.o /opt/SUNWspro/SC2.0.1/f80387/__fnonstd.o /opt/SUNWspro/SC2.0.1/f80387/libm.a /opt/SUNWspro/SC2.0.1/fbe /opt/SUNWspro/SC2.0.1/include/CC/task.h /opt/SUNWspro/SC2.0.1/llib-lm.ln /opt/SUNWspro/SC2.0.1/mcrt1.o /opt/SUNWspro/SC2.0.1/pcrt1.o /opt/SUNWspro/SPROflmrg/bin/filemerge The following files from patch 101205-01 are included in this patch: /opt/SUNWspro/SC2.0.1/CC /opt/SUNWspro/SC2.0.1/README/c++_software /opt/SUNWspro/SC2.0.1/cfront /opt/SUNWspro/SC2.0.1/libp/libtask.a /opt/SUNWspro/SC2.0.1/libtask.a /opt/SUNWspro/SC2.0.1/f77pass1 /opt/SUNWspro/SC2.0.1/libF77.a /opt/SUNWspro/SC2.0.1/libF77.so.2 /opt/SUNWspro/SC2.0.1/libM77.a /opt/SUNWspro/SC2.0.1/libM77.so.2 /opt/SUNWspro/SC2.0.1/libV77.a /opt/SUNWspro/SC2.0.1/libV77.so.2 /opt/SUNWspro/SC2.0.1/libp/libF77.a /opt/SUNWspro/SC2.0.1/libp/libM77.a /opt/SUNWspro/SC2.0.1/libp/libV77.a /opt/SUNWspro/SC2.0.1/sbxref Problem Description: The following bugs have been fixed in this patch. C compiler ========== 1146759 Null in string followed by a digit interpreted incorrectly 1143448 Compiler generates incorrect jump when asm() follows if statement 1142637 The -xpentium flag is not accepted 1138945 at dbx breakpoint line from include file is displayed instead of local function 1145656 code generator sometimes reversed order of operands of a f.p. subtract or divide 1129998 Incorrect stabs when included file contains executable code 1145518 Expressions using the -= and /= operators somtimes computed incorrectly 1144083 asm statement doesn't work for strings containing a colon 1145077 Incorrect optimization of if statement 1147492 Reference to a field of a structured function causes compiler to abort 1141894 ABI violation: compiler generates references to __xtol, __xtoll, and __xtoull C++ compiler ============ 1147801 task.h is missing from /opt/SUNWspro/SC2.0.1/include/CC fortran compiler ================ 1144138 incorrect length used for character argument 1145699 incorrect optimization of loops assembler ========= 1141047 assembler sometimes generates huge object files 1143420 assembler fails with message "cannot alloc data for section" 1145276 Incorrect branches generated when assembling program compiled with -xF option math library ============ 1142916 invalid opcode in inline expansion of fabs() in libm.il 1140882 call to signaling_nan raises exception 1137382 program using ieee_handler fails with segmentation violation filemerge ========= 1147505 Filemerge requires a Teamware license token even if Proworks is installed. The following bugs were fixed in patch 101205-01 which is included in this patch. C compiler ========== 1138750 The "weak" pragma not fully implemented. 1136155 -xF flag is not supported. 1129998 Incorrect stabs when included file contains executable code 1136076 NaN comparisons incorrect 1138159 Incorrect code may be generated for calls with -Kpic 1132143 bad code generated for sign transfer macro 1136254 bad code generation for float variables with -g 3002510 Assembler aborts when certain sources are compiled with -g -c -Wa,-s 3002521 Return value mishandled when one function call away from proc exit, using -K PIC c++ compiler ============ 1133160 C++ compile dies with "SYSTEM ERROR 1" 1133163 C++ compiler dies with "SYSTEM ERROR 1" and "SYSTEM ERROR 2" 1133162 C++ compiler segmentation fault in codegen 1137892 c++ long double is wrong internally 1135079 x86 c++ compiler produces code which core dumps when using -O fortran compiler ================ 1134812 sbxref binary missing 1129279 -sbfast option produces a .s file 1130949 calls to complex functions leave stack pointer incorrect 1132527 int local variables not always 4-byte aligned 1132803 incorrect evaluation of x**n 1133016 Formatted write sometimes leaves stuff on the x87 stack 1129802 Compiler aborts with "cannot find an initialization" message with -pic 1129805 undefined symbol for unreference variable in namelist 1131649 x86 acos is much too inaccurate 1133150 incorrect trig argument reduction 1135847 fpu stack overflow 1136321 compiler aborts with register mapping error 1136398 compiler aborts with message "Can't allocate register" with -O4 option assembler ========= 1135125 Incorrect instruction generated for branches when more than 15 sections math library ============ 1137487 undefined symbol Infl at ld-time Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions added in this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- The installpatch script saves the old version of the patched components under /var/sadm/patch. The total size of the replaced components is approximately 10 Mb. If you don't have enough space, you may invoke installpatch with the -d option, however this will prevent the backoutpatch script from removing the patch. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev