PROBLEM: (QAR 42274) (Patch ID: OSF375-360049) ******** Link times increases exponentially when using ld's -hidden option. PROBLEM: (QAR 43546) (Patch ID: OSF375-360049) ******** The linker is extremely slow when linking against a large number of .so (shared library) files. PROBLEM: (QAR 47588) (Patch ID: OSF375-360073) ******** Linker executes an error exit with chmod() permission problems and certain data-segment alignments for OMAGIC files. PROBLEM: (QAR 48365) (Patch ID: OSF375-360073) ******** Linker hangs (fails to complete execution). PROBLEM: (49301) (Patch ID: OSF375-350337) ******** This patch fixes a problem where use of "ld -r ..." will change symbol preemption behavior. Without this patch, some global relocations can be converted to locals as an optimization. These locals cannot be preempted. An undocumented linker option has been added in the patched linker to prevent this conversion. This new switch is "ld -no_local_conversion ..." PROBLEM: (QAR 53151) (Patch ID: OSF375-350443) ******** At link-time the linker issues an ASSERT statement from within the module relocate.c. This will only be observed for very large applications that build a final image based on previously linked 'ld -r' object files. assertion failed: EX at ../../../../../../src/usr/ccs/bin/ld/relocate.c line 2471 PROBLEM: (QAR 55440) (Patch ID: OSF375-350443) ******** Hidden/Export Symbol wildcard problem: A regression was introduced into the linker when -hidden symbol processing was scaled up to use a hash table. The wildcard capability with the "exported_symbol" option was completely lost. This fix makes wildcards functional for hidden/export symbols. An example of wildcard usage that was no longer functional is: ld -o libf.so -shared -all -hidden -exported_symbol 'X500*' file.o -lc Any symbol beginning with X500 should be "GLOBAL" not "LOCAL". To check if a symbol is global use the following odump command on the library that is produced by the linker: odump -Dt libf.so Shows the symbol being GLOBAL or LOCAL PROBLEM: (QAR 54224) (Patch ID: OSF375-350443) ******** The linker was improperly rounding -T values to 64K increments even when linking OMAGIC files, which do not have the same rounding requirements. It turns out that the check being made in the ld.c was already being done in layout, so all we really need to do is to remove the bogus check in ld.c PROBLEM: (QAR 55693) (Patch ID: OSF375-350443) ******** The linker fails to link a c++ program issuing an "ld_munmap error" message.