crt0_ia(3)						     Library Functions Manual							crt0_ia(3)

NAME

       crt0_ia: crt0.o - execution startup routines for Integrity systems

SYNOPSIS

   Remarks
       This manpage describes for Integrity systems.  For on PA-RISC systems, see crt0_pa(3).

DESCRIPTION

       The  C,	aC++, and FORTRAN compilers link in the object file for statically-bound programs to provide startup capabilities and environments
       for program execution.  It contains startup code that must be linked using to every statically-bound  program.	In  a  dynamically  linked
       program	(the  default  method),  the  object file is not used, and all actions normally associated with it are instead done by the dynamic
       loader dld.so(5).

       processes initializers and terminators.	Initializers are routines that are called before the program entry point and terminators are  rou-
       tines  that  are  called  when  the program terminates via the routine.	Initializers are invoked in reverse order of the link line so that
       dependent libraries are initialized before the libraries that depend on them.  Terminators, on the other hand, are invoked in  the  forward
       order.

       does not define any variables.  It, however, sets the following global variables:

	      A variable of type  long containing the number of arguments.

	      An array of character pointers to the arguments themselves.

	      An array of character pointers to the environment in which the
				  program will run.  This array is terminated by a null pointer.

	      A variable of type  long containing the system id value for an executable program.

	      A variable of type  long	containing  the requested thread local storage size.  This variable is initialized with data from the ker-
				  nel.

	      A variable of type  void * containing load information passed from the kernel.

	      A variable of type  void * whose value equals to the global pointer.

				  A symbol named is also declared in as an enumeration constant, and is incompatible with the  declaration  in	In
				  order  to  include  both  header files, it is necessary to define the macro before including This will force the
				  header file to omit the conflicting definition of The enumeration constant is equivalent to in that context, and
				  may be used instead.	See ttrace(2).

AUTHOR

       The features described in this entry originated from AT&T UNIX System III.

FILES

SEE ALSO

   System Tools
       aCC(1)		 invoke the HP-UX aC++ compiler
       cc(1)		 invoke the HP-UX C compiler
       dld.so(5)	 the dynamic loader
       exec(2)		 execute a file
       f90(1)		 invoke the HP-UX FORTRAN compiler
       ld(1)		 invoke the link editor
   Miscellaneous
       end(3C)		 symbol of the last locations in program

Integrity Systems Only															crt0_ia(3)