|
Patch 2899 : o32 code generator fixes for MIPSpro 7.1 & 7.2 rollup : [IRIX 6.4 6.3 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0002899 Release Note
This release note describes patch SG0002899 to the o32 code
generator for MIPSpro 7.1 & 7.2. This patch replaces
SG0002500. The patch replaces
Problems with patch SG0002500 will not allow you to return
to the base software if you were to remove patchSG0002899.
You must re-install compiler_dev.sw.base from the MIPSpro
7.2 Developer's Foundation to return to the base 7.2
version.
1.1 Supported Hardware Platforms
This patch contains bug fixes for all platforms. The
software cannot be installed on other configurations.
1.2 Supported Software Platforms
This patch contains bug fixes to the MIPSpro 7.1 and 7.2 o32
code generators on a system running IRIX 6.2, 6.3 and 6.4.
The software cannot be installed on other configurations.
1.3 Bugs Fixed by Patch SG0002899
This patch contains fixes for the following bugs in the 7.1
and 7.2 o32 code generators. Bug numbers from Silicon
Graphics bug tracking system are included for reference.
o o32 -O2 code breaks in alloca. (Bug #532558)
1.4 Subsystems Included in Patch SG0002899
This patch release includes these subsystems:
o patchSG0002899.compiler_dev_sw.base
1.5 Installation Instructions
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
inst. The inst program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your Software
Installation Administrator's Guide to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
install patchSGxxxxxxx
where xxxxxxx is the patch number.
2. Initiate the installation sequence. Type
Inst> go
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
Inst> keep patchSGxxxxxxx
where xxxxxxx is the patch number.
4. After completing the installation process, exit the
inst program by typing
Inst> quit
1.6 Patch Removal Instructions
To remove a patch, use the versions remove command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
versions remove patchSGxxxxxxx
where xxxxxxx is the patch number.
To keep a patch but increase your disk space, use the
versions removehist command to remove the patch history.
versions removehist patchSGxxxxxxx
where xxxxxxx is the patch number.
1.7 Known Problems INST SUBSYSTEM REQUIREMENTS No Requirements Information Available. INST SUBSYSTEM CHECKSUMS These checksums help to provide a 'signature' for the patch inst image which can be used to authenticate other inst images. You can obtain this kind of output by running sum -r on the image (from the command line): 30904 2 patchSG0002899 38715 547 patchSG0002899.compiler_dev_sw 55126 1 patchSG0002899.idb INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117071436-IRIXPatch-1203
|
||||||||||||||||||||||||||||||||||||