Patch-ID# 101503-03 Keywords: antilog,jzext,izext,backspace,performance,speed,compile time Synopsis: SPARCompiler Fortran 3.0: Jumbo patch Date: Aug/08/94 Solaris Release: 2.x SunOS release: 5.x Unbundled Product: SPARCompiler Fortran Unbundled Release: 3.0 Topic: Fixes for 10.0D0**X and 2.0D0**X; also JZEXT and IZEXT with constant arguments. Fixes for backspace problems and structure assignment problems and loc problems. This patch fixes the "compile speed" aspect of bug #1162290. BugId's fixed with this patch: 1162290 1164639 1165584 1169129 1169908 1171015 1172259 Changes incorporated in this version: 1164639 1165584 1169129 1169908 1171015 1172259 Relevant Architectures ('arch -k' values if kernel specific): sparc Other patches which conflict with this patch: This patch obsoleted by: Files included with this patch: f77pass1, libF77.a, libF77.so.2, libF77_mt.a libF77_mt.so.2, libF77_mt_p.a, libF77_p.a, libM77.a, libM77.so.2, libM77_p.a, cg,iropt Problem Description: (101503-01) f77pass1 compiles too slowly, especially in the presence of -C. (bug id 1162290) (101503-02) Backspace, when executed between a write and a read, can truncate the file, causing an error on read. Structure assignment, when done between sufficiently complicated objects (arrays of structures inside of structures) assigns the wrong object. loc() does not always work as expected (101503-03) 10.0D0**X and 2.0D0**X call special code rather than the generic exponentiation routines; the type of the special code was incorrectly specified, resulting in wrong answers. JZEXT and IZEXT couldn't handle some constant arguments. Other patches included with this patch: Patch id binaries Synopsis ======== ======== ======== 101503-02 f77 libs fixes for backspace, structure assignment and loc() 101503-01 f77pass1 F77 compiles too slowly 101505-02 cg, iropt iropt core dumps sometimes when -parallel is used 101505-01 cg, iropt compilation problems with huge programs 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: ----------------------------- Recent changes to the patch scripts have brought some problems in our patch structure to the fore. You may notice that the installpatch log file warns you about mismatched versions. The patch *is* being installed properly; you can check with f77 -V (it should show that f77pass1 is "Sun Fortran 77 3.0 patch 101503-03" in this case). If you need to back out a patch, you should use pkgrm(1) rather than the "backoutpatch" script. 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