Here are the macros that control how the compiler handles initialization and termination functions:
INIT_SECTION_ASM_OP
HAS_INIT_SECTION
main
will not call __main
as described above. This macro should be defined for systems that control the contents of the init section on a symbol-by-symbol basis, such as OSF/1, and should not be defined explicitly for systems that support INIT_SECTION_ASM_OP
.
LD_INIT_SWITCH
LD_FINI_SWITCH
INVOKE__main
main
will call __main
despite the presence of INIT_SECTION_ASM_OP
. This macro should be defined for systems where the init section is not actually run automatically, but is still useful for collecting the lists of constructors and destructors.
ASM_OUTPUT_CONSTRUCTOR (stream, name)
Assume that name is the name of a C function generated automatically by the compiler. This function takes no arguments. Use the function assemble_name
to output the name name; this performs any system-specific syntactic transformations such as adding an underscore.
If you don't define this macro, nothing special is output to arrange to call the function. This is correct when the function will be called in some other manner---for example, by means of the collect2
program, which looks through the symbol table to find these functions by their names.
ASM_OUTPUT_DESTRUCTOR (stream, name)
ASM_OUTPUT_CONSTRUCTOR
but used for termination functions rather than initialization functions.
If your system uses collect2
as the means of processing constructors, then that program normally uses nm
to scan an object file for constructor functions to be called. On certain kinds of systems, you can define these macros to make collect2
work faster (and, in some cases, make it work at all):
OBJECT_FORMAT_COFF
collect2
can assume this format and scan object files directly for dynamic constructor/destructor functions.
OBJECT_FORMAT_ROSE
collect2
can assume this format and scan object files directly for dynamic constructor/destructor functions.
These macros are effective only in a native compiler; collect2
as part of a cross compiler always uses nm
for the target machine.
REAL_NM_FILE_NAME
nm
. The default is to search the path normally for nm
. If your system supports shared libraries and has a program to list the dynamic dependencies of a given library or executable, you can define these macros to enable support for running initialization and termination functions in shared libraries:
LDD_SUFFIX
"ldd"
under SunOS 4.
PARSE_LDD_OUTPUT (PTR)
LDD_SUFFIX
. PTR is a variable of type char *
that points to the beginning of a line of output from LDD_SUFFIX
. If the line lists a dynamic dependency, the code must advance PTR to the beginning of the filename on that line. Otherwise, it must set PTR to NULL
.