The Solaris semaphore routines, sema_*(3T), are contained Linking With -lposix4 for POSIX Semaphores Rather than -lthread, to compile and link your application.Įnsures proper library linking order. (this is incorrect)įor C++ programs that use threads, use the -mt option, With an ld command line that includes the following incorrect fragment. The behavior of the C library is undefined if a program is constructed Or libpthread when the application links both libc and the thread library. True procedures are interposed by libthread The runtime library libc has many predefined libthread and libpthread stubs that are null In mixed usage, you need to include both thread.hĪre no-ops if the application does not link -lthread or -lpthread. Waste system resources, and produce misleading results when you debug yourįigure 7-1 summarizes the compile options. These slow down a single-threaded application, Doing so establishes multithreading mechanisms at link Make fork() behave the same way as the Solaris fork1() call, and change the behavior of alarm(2).īefore -lc on the ld command line, or lastĭo not link a nonthreaded program with -lthread or -lpthread. Preserve the Solaris distinction between fork() and fork1(). Some POSIX programmers might want to link with -lthread to Linking With libthread or libpthreadįor POSIX threads behavior, load the libpthread library.įor Solaris threads behavior, load the libthread library. Get the POSIX semantics for these routines, but can still use the SolarisĪpplications that define both -D_POSIX_C_SOURCE and -D_REENTRANT get the POSIX semantics.
Solaris applications that define -D_POSIX_PTHREAD_SEMANTICS Only -D_REENTRANT get the Solaris semantics for these routines. To summarize, POSIX applications that define -D_POSIX_C_SOURCE get the POSIX 1003.1c semantics for the routines listed in Table 7-1. Performance degradation incurred when macros, such as putc(3s),Īre converted into reentrant function calls. Thread libraries ( libthread.so.1 or libpthread.so.1), without the -D_REENTRANT flag. When these flags are not present, all the old definitions for errno, stdio, and so on, remain in effect.Ĭompile single-threaded applications, not linked with either of the
The -D_REENTRANT nor the -D_POSIX_C_SOURCEįlag. To compile a single-threaded application, define neither This applies to every module of an application.įor mixed applications (for example, Solaris threads with POSIX semantics),Ĭompile with the -D_REENTRANT and -D_POSIX_PTHREAD_SEMANTICS flags. For Solaris behavior,Ĭompile multithreaded programs with the -D_REENTRANT flag. Defining _REENTRANT or _POSIX_C_SOURCEįor POSIX behavior, compile applications with the -D_POSIX_C_SOURCE flag set >= 199506L. POSIX semantics prevail when compiling with -D_POSIX_C_SOURCEĪnd linking with -lpthread. In mixed use, Solaris semantics prevail when compiling with -D_REENTRANT and linking with -lthread, whereas You can mix Solaris threads and POSIX threads in the same application,īy including both and, and linking with either the -lthread or -lpthread library. POSIX compliance, the define flag _POSIX_C_SOURCE shouldīe set to a ( long) value >= 199506: cc file. The multithreading interfaces defined by the POSIX 1003.1c standard.
#LINKING PTHREAD C CODE#
lpthread library, compiles code that is conformant with To call thr_setconcurrency(3T) with POSIX threads, your Interfaces-those with Solaris semantics and those with POSIX semantics. Releases of the Solaris Operating Environment. The include file, used with the -lthread library, compiles code that is upward compatible with earlier To the thread's LWP, while a POSIX alarm goes to the whole process (see "Per-Thread Alarms"). The handling of an alarm(2) is also different: a Solaris alarm goes The Solaris fork(2) function duplicates all threads ( fork-all behavior), while the POSIX fork(2) function duplicates only theĬalling thread ( fork-one behavior), as does the Solaris fork1() function.
Table 7-1 Functions With POSIX/Solaris Semantic Differences Routines for a description of the differences in expected parameters and return Have different semantics in the POSIX 1003.1c standard than in the SolarisĢ.4 Operating Environment release, which was based on an earlier POSIX draft.įunction definitions are chosen at compile time. MT-safe libraries ( libc, libm, libw, libintl, libnsl, libsocket, libmalloc,Ĭertain functions, including the ones listed in Table 7-1, POSIX realtime library ( librt) for semaphores The POSIX threads library ( libpthread), and possibly the The Solaris threads library ( libthread), Except for the C compiler, all should come with your Solaris operating The following items are required to compile and link a multithreaded Many options are available for header files, define flags, and linking.
0 kommentar(er)
