JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Linkers and Libraries Guide     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


Part I Using the Link-Editor and Runtime Linker

1.  Introduction to the Oracle Solaris Link Editors

2.  Link-Editor

3.  Runtime Linker

4.  Shared Objects

Part II Quick Reference

5.  Link-Editor Quick Reference

Part III Advanced Topics

6.  Direct Bindings

7.  Building Objects to Optimize System Performance

8.  Mapfiles

9.  Interfaces and Versioning

10.  Establishing Dependencies with Dynamic String Tokens

Capability Specific Shared Objects

Reducing Filtee Searches

Instruction Set Specific Shared Objects

Reducing Filtee Searches

System Specific Shared Objects

Locating Associated Dependencies

Dependencies Between Unbundled Products


11.  Extensibility Mechanisms

Part IV ELF Application Binary Interface

12.  Object File Format

13.  Program Loading and Dynamic Linking

14.  Thread-Local Storage

Part V Appendices

A.  Linker and Libraries Updates and New Features

B.  System V Release 4 (Version 1) Mapfiles


Instruction Set Specific Shared Objects

The dynamic token $ISALIST is expanded at runtime to reflect the native instruction sets executable on this platform, as displayed by the utility isalist(1). This token is available for filters, runpath definitions, and dependencies. As this token can expand to multiple objects, its use with dependencies is controlled. Dependencies obtained with dlopen(3C), can use this token with the mode RTLD_FIRST. Explicit dependencies that use this token will load the first appropriate dependency found.

Note - This token is obsolete, and might be removed in a future release of Oracle Solaris. See Capability Specific Shared Objects for the recommended technique for handling instruction set extensions.

Any string name that incorporates the $ISALIST token is effectively duplicated into multiple strings. Each string is assigned one of the available instruction sets.

The following example shows how the auxiliary filter can be designed to access an instruction set specific filtee

$ LD_OPTIONS='-f /opt/ISV/lib/$ISALIST/' \
cc -o -G -K pic -h -R. foo.c
$ elfdump -d | egrep 'SONAME|AUXILIARY'
       [2]  SONAME            0x1       
       [3]  AUXILIARY         0x96                /opt/ISV/lib/$ISALIST/

Or alternatively the runpath can be used.

$ LD_OPTIONS='-f' \
cc -o -G -K pic -h -R'/opt/ISV/lib/$ISALIST' foo.c
$ elfdump -d | egrep 'RUNPATH|AUXILIARY'
       [3]  AUXILIARY         0x96      
       [4]  RUNPATH           0xa2                /opt/ISV/lib/$ISALIST

In either case the runtime linker uses the platform available instruction list to construct multiple search paths. For example, the following application is dependent on and executed on a SUNW,Ultra-2.

$ ldd -ls prog
  find; required by ./
    search path=/opt/ISV/lib/$ISALIST  (RPATH from file ./
      trying path=/opt/ISV/lib/sparcv9+vis/
      trying path=/opt/ISV/lib/sparcv9/
      trying path=/opt/ISV/lib/sparcv8plus+vis/
      trying path=/opt/ISV/lib/sparcv8plus/
      trying path=/opt/ISV/lib/sparcv8/
      trying path=/opt/ISV/lib/sparcv8-fsmuld/
      trying path=/opt/ISV/lib/sparcv7/
      trying path=/opt/ISV/lib/sparc/

Or an application with similar dependencies is executed on an MMX configured Pentium Pro.

$ ldd -ls prog
  find; required by ./
    search path=/opt/ISV/lib/$ISALIST  (RPATH from file ./
      trying path=/opt/ISV/lib/pentium_pro+mmx/
      trying path=/opt/ISV/lib/pentium_pro/
      trying path=/opt/ISV/lib/pentium+mmx/
      trying path=/opt/ISV/lib/pentium/
      trying path=/opt/ISV/lib/i486/
      trying path=/opt/ISV/lib/i386/
      trying path=/opt/ISV/lib/i86/

Reducing Filtee Searches

The use of $ISALIST within a filter enables one or more filtees to provide implementations of interfaces defined within the filter.

Any interface defined in a filter can result in an exhaustive search of all potential filtees in an attempt to locate the required interface. If filtees are being employed to provide performance critical functions, this exhaustive filtee searching can be counterproductive.

A filtee can be built with the link-editor's -z endfiltee option to indicate that it is the last of the available filtees. This option terminates any further filtee searching for that filter. From the previous SPARC example, if the SPARCV9 filtee existed, and was tagged with -z endfiltee, the filtee searches would be as follows.

$ ldd -ls prog
  find; required by ./
    search path=/opt/ISV/lib/$ISALIST  (RPATH from file ./
      trying path=/opt/ISV/lib/sparcv9+vis/
      trying path=/opt/ISV/lib/sparcv9/