Patch 2773 : libmp rollup : [IRIX 6.4 6.3 6.2]
INDEX
RELATIONS
RELEASE NOTES
1. Patch SG0002773 Release Note This release note describes patch SG0002773 to IRIX 6.2 (and above).1.1 Supported Hardware Platforms This patch contains bug fixes for all platforms running 6.2 (and above). The software cannot be installed on other configurations.1.2 Supported Software Platforms This patch contains bug fixes for the Fortran, C, and C++ compiler development and execution environment (version 1233356910) on a system running IRIX 6.2 (and above). While installing the patch you may notice a conflict between patchSG0002773.compiler_dev_sw.lib and patchSG0002773.compiler_dev_sw32.lib. These conflicts are to be expected, so rather than overriding the conflicts, do not install the conflicting subsystem.1.3 Bugs Fixed by Patch SG0002773 This patch contains fixes for the following bugs. Bug numbers from Silicon Graphics bug tracking system are included for reference. o SGI bug number 232474: The routine mp_set_slave_stacksize should return old value of stacksize. With this patch the routine now returns the previous value of stacksize. o SGI bug number 378358: The MP library had a bug in -n32 compilation where the return address was improperly aligned in memory. This caused a problem with stack- unwind by tools such as dbx and gprof. o SGI bug number 404228: The MP library now provides support for data distribution, useful in the context of distributed shared memory machines such as the Origins. o SGI bug number 441658: A user-specified signal handler to trap control-c did not work. This patch fixes this bug, so that user-defined handlers to catch SIGINT now work. o SGI bug number 451258: CC Sync counter can occasionally encounter a hardware deadlock on IP25. With this patch the use of the CC-sync counter is disabled by default. o SGI bug number 455437: Bug in using hardware fetch- and-op on IP27 through the _DSM_FOP environment variable (programs run with 1 thread get deadlocked). With this patch _DSM_FOP now works correctly with varying number of threads, including 1. o SGI bug number 455511: On IP27 the environment variable _DSM_MUSTRUN could sometimes cause multiple threads to be assigned to the same node, leading to poor performance. With this patch the MP library requests a small amount of memory per node, avoiding corner cases that resulted in the above problem. o SGI bug number 460617: The symbol pm_filldefault referenced by the MP library is undefined on systems before IRIX 6.4. To allow execution on earlier systems (e.g. IRIX 6.2) this symbol needs to be declared as weak within the library. o SGI bug number 468925: On Origin-2000 systems although page migration is disabled by default, once enabled the migration level requested was extremely aggressive. With this patch the migration level (if enabled) is lower with the value 10 on a scale of 1-100. In addition, the user can control the migration level explicitly through the environment variable _DSM_MIGRATION_LEVEL (which can take values between 1 and 100). o SGI bug number 474179: This patch cleans up two environment variables. The first concerns data placement on Origin-2000 systems: _DSM_PLACEMENT is now the recommended way to obtain either FIRST_TOUCH data placement (default) or ROUND_ROBIN placement (optional). The second environment variable controls the underlying barrier implementation in the MP runtime: _DSM_BARRIER can now be set to FOP, enabling the hardware uncached/fetchop barrier implementation (disabled by default). o SGI bug number 520385: This patch fixes a bug in the handling a zero-trip parallel loop with either dynamic or gss scheduling. Before this fix, such a parallel loop could spin indefinitely. o SGI bug number 538673: This patch fixes a bug in program termination when the user program has installed a SIGCLD handler. Before this fix, such a program could result in error messages of the form "Error doing waitpid for slave termination". o SGI bug number 549413: breakup patch 2416 runtime into smaller patches o SGI bug number 561897: This patch fixes a race condition in handling the ONTO clause. o SGI bug number 562965: This patch fixes a bug in handling overlapping portions of a distributed array. o SGI bug number 574971: This patch fixes a bug in handling affinity for a non-distributed dimension of an array, and in computing the loop bounds for a block- distribution. o SGI bug number 576927: If the program exits due to an error condition, some threads might be killed while they are holding a lock. This fix ensures that the program does not deadlock in that situation.1.4 Subsystems Included in Patch SG0002773 This patch replaces patches: 1382 1390 1481 1609 1737 1816 1896 and 2422 This patch release includes these subsystems: o patchSG0002773.compiler_dev_sw.lib o patchSG0002773.compiler_dev_sw32.lib o patchSG0002773.compiler_dev_sw64.lib o patchSG0002773.compiler_eoe_sw.lib o patchSG0002773.compiler_eoe_sw64.lib1.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> quit1.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): 20769 11 patchSG0002773 46672 902 patchSG0002773.compiler_dev_sw 46672 902 patchSG0002773.compiler_dev_sw32 39963 916 patchSG0002773.compiler_dev_sw64 09088 661 patchSG0002773.compiler_eoe_sw 03061 657 patchSG0002773.compiler_eoe_sw64 20707 6 patchSG0002773.idb INST SUBSYSTEM FILE LISTINGS The following lists the files which get installed from each subsystem in the patch:
DOWNLOAD PATCH
|
||||||||||||||||||||||||||||||||||||
Document Id: 20021117071154-IRIXPatch-1175
|