diff options
author | Steve Chamberlain <steve@cygnus> | 1991-08-17 00:07:43 +0000 |
---|---|---|
committer | Steve Chamberlain <steve@cygnus> | 1991-08-17 00:07:43 +0000 |
commit | bded7de2139c9b68665bbf85c721d456e25f63ea (patch) | |
tree | 2cd9ca2333be0fdaed9b163bf9d10574f2d77239 /include/bfd.h | |
parent | 0b5311ca6d788f0c8fe4c0fdc0773144af4e66b1 (diff) | |
download | gdb-bded7de2139c9b68665bbf85c721d456e25f63ea.zip gdb-bded7de2139c9b68665bbf85c721d456e25f63ea.tar.gz gdb-bded7de2139c9b68665bbf85c721d456e25f63ea.tar.bz2 |
Documentation changes
Diffstat (limited to 'include/bfd.h')
-rw-r--r-- | include/bfd.h | 1415 |
1 files changed, 942 insertions, 473 deletions
diff --git a/include/bfd.h b/include/bfd.h index a7cbc09..e205271 100644 --- a/include/bfd.h +++ b/include/bfd.h @@ -310,27 +310,43 @@ extern CONST short _bfd_host_big_endian; /*THE FOLLOWING IS EXTRACTED FROM THE SOURCE */ -/* Opens the file supplied (using fopen) with the target supplied, it +/* FROM opncls.c*/ +/* ------------------------------START FROM opncls.c + +*i bfd_openr +Opens the file supplied (using fopen) with the target supplied, it returns a pointer to the created bfd. If NULL is returned then an error has occured. Possible errors are no_memory, invalid_target or system_call error. */ -PROTO(bfd*, bfd_openr, (CONST char *filename,CONST char*target)); -/* bfd_fdopenr is to bfd_fopenr much like fdopen is to fopen. It opens a bfd on + PROTO(bfd*, bfd_openr, (CONST char *filename,CONST char*target)); + +/* + +*i bfd_fdopenr +bfd_fdopenr is to bfd_fopenr much like fdopen is to fopen. It opens a bfd on a file already described by the @var{fd} supplied. Possible errors are no_memory, invalid_target and system_call error. */ - PROTO(bfd *, bfd_fdopenr, + PROTO(bfd *, bfd_fdopenr, (CONST char *filename, CONST char *target, int fd)); -/* Creates a bfd, associated with file @var{filename}, using the file + +/* + + bfd_openw +Creates a bfd, associated with file @var{filename}, using the file format @var{target}, and returns a pointer to it. Possible errors are system_call_error, no_memory, invalid_target. */ -PROTO(bfd *, bfd_openw, (CONST char *filename, CONST char *target)); -/* This function closes a bfd. If the bfd was open for writing, then + PROTO(bfd *, bfd_openw, (CONST char *filename, CONST char *target)); + +/* + + bfd_close +This function closes a bfd. If the bfd was open for writing, then pending operations are completed and the file written out and closed. If the created file is executable, then @code{chmod} is called to mark it as such. @@ -339,26 +355,43 @@ All memory attatched to the bfd's obstacks is released. @code{true} is returned if all is ok, otherwise @code{false}. */ -PROTO(boolean, bfd_close,(bfd *)); -/* This routine creates a new bfd in the manner of bfd_openw, but without + PROTO(boolean, bfd_close,(bfd *)); + +/* + + bfd_create +This routine creates a new bfd in the manner of bfd_openw, but without opening a file. The new bfd takes the target from the target used by @var{template}. The format is always set to @code{bfd_object}. - */ -PROTO(bfd *, bfd_create, (CONST char *filename, bfd *template)); -/* Return the number of bytes in the obstacks connected to the supplied + + PROTO(bfd *, bfd_create, (CONST char *filename, bfd *template)); + +/* + + bfd_alloc_size +Return the number of bytes in the obstacks connected to the supplied bfd. */ -PROTO(bfd_size_type,bfd_alloc_size,(bfd *abfd)); -/* This enum gives the object file's CPU + PROTO(bfd_size_type,bfd_alloc_size,(bfd *abfd)); + +/* + + --------------------------------END FROM opncls.c*/ + + +/* FROM archures.c*/ +/* ------------------------------START FROM archures.c + bfd_architecture +This enum gives the object file's CPU architecture, in a global sense. E.g. what processor family does it belong to? There is another field, which indicates what processor within the family is in use. The machine gives a number which distingushes different versions of the architecture, containing for example 2 and 3 for Intel i960 KA and i960 KB, and 68020 and 68030 for Motorola 68020 and 68030. - */ + enum bfd_architecture { bfd_arch_unknown, /* File arch not known */ @@ -397,20 +430,29 @@ enum bfd_architecture bfd_arch_last }; -/* stuff -*/ +/* +stuff -/* Return a printable string representing the architecture and machine + bfd_prinable_arch_mach +Return a printable string representing the architecture and machine type. The result is only good until the next call to bfd_printable_arch_mach. */ -PROTO(CONST char *,bfd_printable_arch_mach, + PROTO(CONST char *,bfd_printable_arch_mach, (enum bfd_architecture arch, unsigned long machine)); -/* Scan a string and attempt to turn it into an archive and machine type combination. + +/* + +*i bfd_scan_arch_mach +Scan a string and attempt to turn it into an archive and machine type combination. */ -PROTO(boolean, bfd_scan_arch_mach, + PROTO(boolean, bfd_scan_arch_mach, (CONST char *, enum bfd_architecture *, unsigned long *)); -/* This routine is used to determine whether two BFDs' architectures and machine types are + +/* + +*i bfd_arch_compatible +This routine is used to determine whether two BFDs' architectures and machine types are compatible. It calculates the lowest common denominator between the two architectures and machine types implied by the bfds and sets the objects pointed at by @var{archp} and @var{machine} if non NULL. @@ -418,18 +460,32 @@ objects pointed at by @var{archp} and @var{machine} if non NULL. This routine returns @code{true} if the bfds are of compatible type, otherwise @code{false}. */ -PROTO(boolean, bfd_arch_compatible, + PROTO(boolean, bfd_arch_compatible, (bfd *abfd, bfd *bbfd, enum bfd_architecture *archp, unsigned long *machinep)); -/* Set atch mach + +/* + + bfd_set_arch_mach +Set atch mach */ #define bfd_set_arch_mach(abfd, arch, mach) \ BFD_SEND (abfd, _bfd_set_arch_mach,\ (abfd, arch, mach)) -/* These macros as used for reading and writing raw data in sections; +/* + --------------------------------END FROM archures.c*/ + + + +/* FROM libbfd.c*/ +/* ------------------------------START FROM libbfd.c + +*i bfd_put_size +*i bfd_get_size +These macros as used for reading and writing raw data in sections; each access (except for bytes) is vectored through the target format of the bfd and mangled accordingly. The mangling performs any necessary endian translations and removes alignment restrictions. @@ -450,8 +506,9 @@ necessary endian translations and removes alignment restrictions. BFD_SEND(abfd, bfd_putx64, (val, ptr)) #define bfd_get_64(abfd, ptr) \ BFD_SEND(abfd, bfd_getx64, (ptr)) - -/* These macros have the same function as their @code{bfd_get_x} +/* *i bfd_h_put_size +*i bfd_h_get_size +These macros have the same function as their @code{bfd_get_x} bretherin, except that they are used for removing information for the header records of object files. Believe it or not, some object files keep their header records in big endian order, and their data in little @@ -473,190 +530,286 @@ endan order. BFD_SEND(abfd, bfd_h_putx64,(val, ptr)) #define bfd_h_get_64(abfd, ptr) \ BFD_SEND(abfd, bfd_h_getx64,(ptr)) +/* --------------------------------END FROM libbfd.c*/ -/* The shape of a section struct: +/* FROM section.c*/ +/* ------------------------------START FROM section.c +The shape of a section struct: */ + typedef struct sec { - /* The name of the section, the name isn't a copy, the pointer is - the same as that passed to bfd_make_section. - */ +/* +The name of the section, the name isn't a copy, the pointer is +the same as that passed to bfd_make_section. +*/ + CONST char *name; - /* The next section in the list belonging to the bfd, or NULL. - */ +/* +The next section in the list belonging to the bfd, or NULL. +*/ + struct sec *next; - /* The field flags contains attributes of the section. Some of these - flags are read in from the object file, and some are synthesized from - other information. - */ +/* +The field flags contains attributes of the section. Some of these +flags are read in from the object file, and some are synthesized from +other information. +*/ + flagword flags; + +/* +*/ + #define SEC_NO_FLAGS 0x000 - /* Tells the OS to allocate space for this section when loaded. - This would clear for a section containing debug information only. - */ +/* +Tells the OS to allocate space for this section when loaded. +This would clear for a section containing debug information only. +*/ + #define SEC_ALLOC 0x001 - /* Tells the OS to load the section from the file when loading. - This would be clear for a .bss section - */ +/* +Tells the OS to load the section from the file when loading. +This would be clear for a .bss section +*/ + #define SEC_LOAD 0x002 - /* The section contains data still to be relocated, so there will be some - relocation information too. - */ +/* +The section contains data still to be relocated, so there will be some +relocation information too. +*/ + #define SEC_RELOC 0x004 - /* Obsolete ? - */ +/* +Obsolete ? +*/ + #define SEC_BALIGN 0x008 - /* A signal to the OS that the section contains read only data. - */ +/* +A signal to the OS that the section contains read only data. +*/ + #define SEC_READONLY 0x010 - /* The section contains code only. - */ +/* +The section contains code only. +*/ + #define SEC_CODE 0x020 - /* The section contains data only. - */ +/* +The section contains data only. +*/ + #define SEC_DATA 0x040 - /* The section will reside in ROM. - */ +/* +The section will reside in ROM. +*/ + #define SEC_ROM 0x080 - /* The section contains constructor information. This section type is - used by the linker to create lists of constructors and destructors - used by @code{g++}. When a back end sees a symbol which should be used - in a constructor list, it creates a new section for the type of name - (eg @code{__CTOR_LIST__}), attatches the symbol to it and builds a - relocation. To build the lists of constructors, all the linker has to - to is catenate all the sections called @code{__CTOR_LIST__} and - relocte the data contained within - exactly the operations it would - peform on standard data. - */ +/* +The section contains constructor information. This section type is +used by the linker to create lists of constructors and destructors +used by @code{g++}. When a back end sees a symbol which should be used +in a constructor list, it creates a new section for the type of name +(eg @code{__CTOR_LIST__}), attatches the symbol to it and builds a +relocation. To build the lists of constructors, all the linker has to +to is catenate all the sections called @code{__CTOR_LIST__} and +relocte the data contained within - exactly the operations it would +peform on standard data. +*/ + #define SEC_CONSTRUCTOR 0x100 - /* The section is a constuctor, and should be placed at the end of the .. - */ +/* +The section is a constuctor, and should be placed at the end of the .. +*/ + #define SEC_CONSTRUCTOR_TEXT 0x1100 + +/* +*/ #define SEC_CONSTRUCTOR_DATA 0x2100 + +/* +*/ #define SEC_CONSTRUCTOR_BSS 0x3100 - /* The section has contents - a bss section could be - @code{SEC_ALLOC} | @code{SEC_HAS_CONTENTS}, a debug section could be - @code{SEC_HAS_CONTENTS} - */ +/* + +The section has contents - a bss section could be +@code{SEC_ALLOC} | @code{SEC_HAS_CONTENTS}, a debug section could be +@code{SEC_HAS_CONTENTS} +*/ + #define SEC_HAS_CONTENTS 0x200 - /* An instruction to the linker not to output sections containing - this flag even if they have information which would normally be written. - */ +/* +An instruction to the linker not to output sections containing +this flag even if they have information which would normally be written. +*/ + #define SEC_NEVER_LOAD 0x400 - /* The base address of the section in the address space of the target. - */ +/* + +The base address of the section in the address space of the target. +*/ + bfd_vma vma; - /* The size of the section in bytes of the loaded section. This contains - a value even if the section has no contents (eg, the size of @code{.bss}). - */ +/* +The size of the section in bytes of the loaded section. This contains +a value even if the section has no contents (eg, the size of @code{.bss}). +*/ + bfd_size_type size; - /* If this section is going to be output, then this value is the - offset into the output section of the first byte in the input - section. Eg, if this was going to start at the 100th byte in the - output section, this value would be 100. - */ +/* +If this section is going to be output, then this value is the +offset into the output section of the first byte in the input +section. Eg, if this was going to start at the 100th byte in the +output section, this value would be 100. +*/ + bfd_vma output_offset; - /* The output section through which to map on output. - */ +/* +The output section through which to map on output. +*/ + struct sec *output_section; - /* The alignment requirement of the section, as an exponent - eg 3 - aligns to 2^3 (or 8) - */ +/* +The alignment requirement of the section, as an exponent - eg 3 +aligns to 2^3 (or 8) +*/ + unsigned int alignment_power; - /* If an input section, a pointer to a vector of relocation records for - the data in this section. - */ +/* +If an input section, a pointer to a vector of relocation records for +the data in this section. +*/ + struct reloc_cache_entry *relocation; - /* If an output section, a pointer to a vector of pointers to - relocation records for the data in this section. - */ +/* +If an output section, a pointer to a vector of pointers to +relocation records for the data in this section. +*/ + struct reloc_cache_entry **orelocation; - /* The number of relocation records in one of the above - */ +/* +The number of relocation records in one of the above +*/ + unsigned reloc_count; - /* Which section is it 0..nth - */ +/* +Which section is it 0..nth +*/ + int index; - /* Information below is back end specific - and not always used or - updated - - File position of section data - */ +/* +Information below is back end specific - and not always used or +updated + +File position of section data +*/ + file_ptr filepos; +/* File position of relocation info +*/ - /* File position of relocation info - */ file_ptr rel_filepos; - /* File position of line data - */ +/* +File position of line data +*/ + file_ptr line_filepos; - /* Pointer to data for applications - */ +/* +Pointer to data for applications +*/ + PTR userdata; + +/* +*/ struct lang_output_section *otheruserdata; - /* Attached line number information - */ +/* +Attached line number information +*/ + alent *lineno; +/* Number of line number records +*/ - /* Number of line number records - */ unsigned int lineno_count; - /* When a section is being output, this value changes as more - linenumbers are written out - */ +/* +When a section is being output, this value changes as more +linenumbers are written out +*/ + file_ptr moving_line_filepos; - /* what the section number is in the target world - */ +/* +what the section number is in the target world +*/ + unsigned int target_index; + +/* +*/ PTR used_by_bfd; - /* If this is a constructor section then here is a list of the - relocations created to relocate items within it. - */ +/* +If this is a constructor section then here is a list of the +relocations created to relocate items within it. +*/ + struct relent_chain *constructor_chain; - /* The bfd which owns the section. - */ +/* +The bfd which owns the section. +*/ + bfd *owner; + +/* +*/ } asection ; -/* Runs through the provided @var{abfd} and returns the @code{asection} -who's name matches that provided, otherwise NULL. @xref{Sections}, for more information. +/* + bfd_get_section_by_name +Runs through the provided @var{abfd} and returns the @code{asection} +who's name matches that provided, otherwise NULL. @xref{Sections}, for more information. */ -PROTO(asection *, bfd_get_section_by_name, + + PROTO(asection *, bfd_get_section_by_name, (bfd *abfd, CONST char *name)); -/* This function creates a new empty section called @var{name} and attatches it + +/* + + bfd_make_section +This function creates a new empty section called @var{name} and attatches it to the end of the chain of sections for @var{bfd}. An attempt to create a section with a name which is already in use, returns the old section by that name instead. @@ -668,10 +821,14 @@ If output has already started for this bfd. @item no_memory If obstack alloc fails. @end table - */ -PROTO(asection *, bfd_make_section, (bfd *, CONST char *name)); -/* Attempts to set the attributes of the section named in the bfd + + PROTO(asection *, bfd_make_section, (bfd *, CONST char *name)); + +/* + + bfd_set_section_flags +Attempts to set the attributes of the section named in the bfd supplied to the value. Returns true on success, false on error. Possible error returns are: @table @code @@ -680,32 +837,39 @@ The section cannot have one or more of the attributes requested. For example, a .bss section in @code{a.out} may not have the @code{SEC_HAS_CONTENTS} field set. @end table - */ -PROTO(boolean, bfd_set_section_flags, + + PROTO(boolean, bfd_set_section_flags, (bfd *, asection *, flagword)); -/* Calls the provided function @var{func} for each section attatched to + +/* + + bfd_map_over_sections +Calls the provided function @var{func} for each section attatched to the bfd @var{abfd}, passing @var{obj} as an argument. The function will be called as if by @example func(abfd, the_section, obj); @end example - - */ -PROTO(void, bfd_map_over_sections, + + PROTO(void, bfd_map_over_sections, (bfd *abfd, void (*func)(), PTR obj)); -/* This is the prefered method for iterating over sections, an + +/* + +This is the prefered method for iterating over sections, an alternative would be to use a loop: @example section *p; for (p = abfd->sections; p != NULL; p = p->next) func(abfd, p, ...) -@end example*/ +@end example -/* Sets @var{section} to the size @var{val}. If the operation is ok, then + bfd_set_section_size +Sets @var{section} to the size @var{val}. If the operation is ok, then @code{true} is returned, else @code{false}. Possible error returns: @@ -713,11 +877,15 @@ Possible error returns: @item invalid_operation Writing has started to the bfd, so setting the size is invalid @end table - */ -PROTO(boolean, bfd_set_section_size, + + PROTO(boolean, bfd_set_section_size, (bfd *, asection *, bfd_size_type val)); -/* Sets the contents of the section @var{section} in bfd @var{abfd} to + +/* + + bfd_set_section_contents +Sets the contents of the section @var{section} in bfd @var{abfd} to the data starting in memory at @var{data}. The data is written to the output section starting at offset @var{offset} for @var{count} bytes. @@ -730,15 +898,19 @@ attribute, so nothing can be written to it. @item and some more too @end table This routine is front end to the back end function @code{_bfd_set_section_contents}. - */ -PROTO(boolean, bfd_set_section_contents, + + PROTO(boolean, bfd_set_section_contents, (bfd *abfd, asection *section, PTR data, file_ptr offset, bfd_size_type count)); -/* This function reads data from @var{section} in bfd @var{abfd} into + +/* + + bfd_get_section_contents +This function reads data from @var{section} in bfd @var{abfd} into memory starting at @var{location}. The data is read at an offset of @var{offset} from the start of the input section, and is read for @var{count} bytes. @@ -752,134 +924,190 @@ Possible errors are: @table @code @item unknown yet @end table - */ -PROTO(boolean, bfd_get_section_contents, + + PROTO(boolean, bfd_get_section_contents, (bfd *abfd, asection *section, PTR location, file_ptr offset, bfd_size_type count)); -/* @subsection typedef asymbol -An @code{asymbol} has the form: +/* + + --------------------------------END FROM section.c*/ + +/* FROM syms.c*/ +/* ------------------------------START FROM syms.c + +@subsection typedef asymbol +An @code{asymbol} has the form: */ + typedef struct symbol_cache_entry { +/* A pointer to the bfd which owns the symbol. This information is +necessary so that a back end can work out what additional (invisible to +the application writer) information is carried with the symbol. +*/ - /* A pointer to the bfd which owns the symbol. This information is - necessary so that a back end can work out what additional (invisible to - the application writer) information is carried with the symbol. - */ struct _bfd *the_bfd; - /* The text of the symbol. The name is left alone, and not copied - the - application may not alter it. - */ +/* +The text of the symbol. The name is left alone, and not copied - the +application may not alter it. +*/ + CONST char *name; - /* The value of the symbol. - */ +/* +The value of the symbol. +*/ + symvalue value; - /* Attributes of a symbol: - */ +/* +Attributes of a symbol: +*/ + #define BSF_NO_FLAGS 0x00 - /* The symbol has local scope; @code{static} in @code{C}. The value is - the offset into the section of the data. - */ +/* +The symbol has local scope; @code{static} in @code{C}. The value is +the offset into the section of the data. +*/ + #define BSF_LOCAL 0x01 - /* The symbol has global scope; initialized data in @code{C}. The value - is the offset into the section of the data. - */ +/* +The symbol has global scope; initialized data in @code{C}. The value +is the offset into the section of the data. +*/ + #define BSF_GLOBAL 0x02 - /* Obsolete - */ +/* +Obsolete +*/ + #define BSF_IMPORT 0x04 - /* The symbol has global scope, and is exported. The value is the offset - into the section of the data. - */ +/* +The symbol has global scope, and is exported. The value is the offset +into the section of the data. +*/ + #define BSF_EXPORT 0x08 - /* The symbol is undefined. @code{extern} in @code{C}. The value has no meaning. - */ +/* +The symbol is undefined. @code{extern} in @code{C}. The value has no meaning. +*/ + #define BSF_UNDEFINED 0x10 - /* The symbol is common, initialized to zero; default in @code{C}. The - value is the size of the object in bytes. - */ +/* +The symbol is common, initialized to zero; default in @code{C}. The +value is the size of the object in bytes. +*/ + #define BSF_FORT_COMM 0x20 - /* A normal @code{C} symbol would be one of: - @code{BSF_LOCAL}, @code{BSF_FORT_COMM}, @code{BSF_UNDEFINED} or @code{BSF_EXPORT|BSD_GLOBAL} - - The symbol is a debugging record. The value has an arbitary meaning. - */ +/* +A normal @code{C} symbol would be one of: +@code{BSF_LOCAL}, @code{BSF_FORT_COMM}, @code{BSF_UNDEFINED} or @code{BSF_EXPORT|BSD_GLOBAL} + +The symbol is a debugging record. The value has an arbitary meaning. +*/ + #define BSF_DEBUGGING 0x40 - /* The symbol has no section attached, any value is the actual value and - is not a relative offset to a section. - */ +/* +The symbol has no section attached, any value is the actual value and +is not a relative offset to a section. +*/ + #define BSF_ABSOLUTE 0x80 - /* Used by the linker - */ +/* +Used by the linker +*/ + #define BSF_KEEP 0x10000 #define BSF_KEEP_G 0x80000 - /* Unused - */ +/* +Unused +*/ + #define BSF_WEAK 0x100000 #define BSF_CTOR 0x200000 #define BSF_FAKE 0x400000 - /* The symbol used to be a common symbol, but now it is allocated. - */ +/* +The symbol used to be a common symbol, but now it is allocated. +*/ + #define BSF_OLD_COMMON 0x800000 - /* The default value for common data. - */ +/* +The default value for common data. +*/ + #define BFD_FORT_COMM_DEFAULT_VALUE 0 - /* In some files the type of a symbol sometimes alters its location - in an output file - ie in coff a @code{ISFCN} symbol which is also @code{C_EXT} - symbol appears where it was declared and not at the end of a section. - This bit is set by the target bfd part to convey this information. - */ +/* +In some files the type of a symbol sometimes alters its location +in an output file - ie in coff a @code{ISFCN} symbol which is also @code{C_EXT} +symbol appears where it was declared and not at the end of a section. +This bit is set by the target bfd part to convey this information. +*/ + #define BSF_NOT_AT_END 0x40000 - /* Signal that the symbol is the label of constructor section. - */ +/* +Signal that the symbol is the label of constructor section. +*/ + #define BSF_CONSTRUCTOR 0x1000000 - /* Signal that the symbol is a warning symbol. If the symbol is a warning - symbol, then the value field (I know this is tacky) will point to the - asymbol which when referenced will cause the warning. - */ +/* +Signal that the symbol is a warning symbol. If the symbol is a warning +symbol, then the value field (I know this is tacky) will point to the +asymbol which when referenced will cause the warning. +*/ + #define BSF_WARNING 0x2000000 - /* Signal that the symbol is indirect. The value of the symbol is a - pointer to an undefined asymbol which contains the name to use - instead. - */ +/* +Signal that the symbol is indirect. The value of the symbol is a +pointer to an undefined asymbol which contains the name to use +instead. +*/ + #define BSF_INDIRECT 0x4000000 + +/* +*/ flagword flags; - /* Aointer to the section to which this symbol is relative, or 0 if the - symbol is absolute or undefined. Note that it is not sufficient to set - this location to 0 to mark a symbol as absolute - the flag - @code{BSF_ABSOLUTE} must be set also. - */ +/* +Aointer to the section to which this symbol is relative, or 0 if the +symbol is absolute or undefined. Note that it is not sufficient to set +this location to 0 to mark a symbol as absolute - the flag +@code{BSF_ABSOLUTE} must be set also. +*/ + struct sec *section; - /* Back end special data. This is being phased out in favour of making - this a union. - */ +/* +Back end special data. This is being phased out in favour of making +this a union. +*/ + PTR udata; } asymbol; -/* Returns the number of bytes required in a vector of pointers to +/* + + get_symtab_upper_bound +Returns the number of bytes required in a vector of pointers to @code{asymbols} for all the symbols in the supplied bfd, including a terminal NULL pointer. If there are no symbols in the bfd, then 0 is returned. @@ -887,27 +1115,39 @@ returned. #define get_symtab_upper_bound(abfd) \ BFD_SEND (abfd, _get_symtab_upper_bound, (abfd)) -/* Supplied a bfd and a pointer to an uninitialized vector of pointers. +/* + + bfd_canonicalize_symtab +Supplied a bfd and a pointer to an uninitialized vector of pointers. This reads in the symbols from the bfd, and fills in the table with pointers to the symbols, and a trailing NULL. The routine returns the actual number of symbol pointers not including the NULL. - */ + #define bfd_canonicalize_symtab(abfd, location) \ BFD_SEND (abfd, _bfd_canonicalize_symtab,\ (abfd, location)) - -/* Provided a table of pointers to to symbols and a count, writes to the +/* + bfd_set_symtab +Provided a table of pointers to to symbols and a count, writes to the output bfd the symbols when closed. - */ -PROTO(boolean, bfd_set_symtab, (bfd *, asymbol **, unsigned int )); -/* Prints the value and flags of the symbol supplied to the stream file. + PROTO(boolean, bfd_set_symtab, (bfd *, asymbol **, unsigned int )); + +/* + + bfd_print_symbol_vandf +Prints the value and flags of the symbol supplied to the stream file. */ -PROTO(void, bfd_print_symbol_vandf, (PTR file, asymbol *symbol)); -/* This function creates a new @code{asymbol} structure for the bfd, and + + PROTO(void, bfd_print_symbol_vandf, (PTR file, asymbol *symbol)); + +/* + + bfd_make_empty_symbol +This function creates a new @code{asymbol} structure for the bfd, and returns a pointer to it. This routine is necessary, since each back end has private information @@ -918,7 +1158,13 @@ problems later on. #define bfd_make_empty_symbol(abfd) \ BFD_SEND (abfd, _bfd_make_empty_symbol, (abfd)) -/* @section typedef bfd +/* + --------------------------------END FROM syms.c*/ + +/* FROM bfd.c*/ +/* ------------------------------START FROM bfd.c + +@section typedef bfd Pointers to bfd structs are the cornerstone of any application using libbfd. References though the bfd and to data in the bfd give the @@ -926,146 +1172,210 @@ entire bfd functionality. Finally! The BFD struct itself. This contains the major data about the file, and contains pointers to the rest of the data. - */ + struct _bfd { +/* The filename the application opened the bfd with. +*/ - /* The filename the application opened the bfd with. - */ CONST char *filename; - /* A pointer to the target jump table. - */ +/* +A pointer to the target jump table. +*/ + struct bfd_target *xvec; - /* To avoid dragging too many header files into every file that - includes bfd.h, IOSTREAM has been declared as a "char *", and MTIME - as a "long". Their correct types, to which they are cast when used, - are "FILE *" and "time_t". - - The iostream is the result of an fopen on the filename. - */ +/* + +To avoid dragging too many header files into every file that +includes bfd.h, IOSTREAM has been declared as a "char *", and MTIME +as a "long". Their correct types, to which they are cast when used, +are "FILE *" and "time_t". + +The iostream is the result of an fopen on the filename. +*/ + char *iostream; - /* Is the file being cached @xref{File Caching}. - */ +/* +Is the file being cached @xref{File Caching}. +*/ + boolean cacheable; - /* Marks whether there was a default target specified when the bfd was - opened. This is used to select what matching algorithm to use to chose - the back end. - */ +/* +Marks whether there was a default target specified when the bfd was +opened. This is used to select what matching algorithm to use to chose +the back end. +*/ + boolean target_defaulted; - /* The caching routines use these to maintain an LRU list of bfds. - */ +/* +The caching routines use these to maintain an LRU list of bfds. +*/ + struct _bfd *lru_prev, *lru_next; - /* When a file is closed by the caching routines, it retains the state - here: - */ +/* +When a file is closed by the caching routines, it retains the state +here: +*/ + file_ptr where; - /* and here: - */ +/* +and here: +*/ + boolean opened_once; + +/* +*/ boolean mtime_set; +/* File modified time +*/ - /* File modified time - */ long mtime; - /* For output files, channel we locked (is this used?). - */ +/* +For output files, channel we locked (is this used?). +*/ + int ifd; - /* The format which belongs to the bfd. - */ +/* +The format which belongs to the bfd. +*/ + bfd_format format; - /* The direction the bfd was opened with - */ +/* +The direction the bfd was opened with +*/ + enum bfd_direction {no_direction = 0, read_direction = 1, write_direction = 2, both_direction = 3} direction; - /* Format_specific flags - */ +/* +Format_specific flags +*/ + flagword flags; - /* Currently my_archive is tested before adding origin to anything. I - believe that this can become always an add of origin, with origin set - to 0 for non archive files. - */ +/* +Currently my_archive is tested before adding origin to anything. I +believe that this can become always an add of origin, with origin set +to 0 for non archive files. +*/ + file_ptr origin; - /* Remember when output has begun, to stop strange things happening. - */ +/* +Remember when output has begun, to stop strange things happening. +*/ + boolean output_has_begun; - /* Pointer to linked list of sections - */ +/* +Pointer to linked list of sections +*/ + struct sec *sections; - /* The number of sections - */ +/* +The number of sections +*/ + unsigned int section_count; - /* Stuff only usefull for object files: - The start address. - */ +/* +Stuff only usefull for object files: +The start address. +*/ + bfd_vma start_address; +/* Used for input and output +*/ - /* Used for input and output - */ unsigned int symcount; +/* Symtab for output bfd +*/ - /* Symtab for output bfd - */ struct symbol_cache_entry **outsymbols; - /* Architecture of object machine, eg m68k - */ +/* +Architecture of object machine, eg m68k +*/ + enum bfd_architecture obj_arch; - /* Particular machine within arch, e.g. 68010 - */ +/* +Particular machine within arch, e.g. 68010 +*/ + unsigned long obj_machine; - /* Stuff only usefull for archives: - */ +/* +Stuff only usefull for archives: +*/ + PTR arelt_data; struct _bfd *my_archive; struct _bfd *next; struct _bfd *archive_head; boolean has_armap; - /* Used by the back end to hold private data. - */ +/* +Used by the back end to hold private data. +*/ + PTR tdata; - /* Used by the application to hold private data - */ +/* +Used by the application to hold private data +*/ + PTR usrdata; - /* Where all the allocated stuff under this BFD goes - */ +/* +Where all the allocated stuff under this BFD goes +*/ + struct obstack memory; }; -/* Marks the entry point of an output bfd. Returns @code{true} on -success, @code{false} otherwise. +/* + bfd_set_start_address + +Marks the entry point of an output bfd. Returns @code{true} on +success, @code{false} otherwise. */ -PROTO(boolean, bfd_set_start_address,(bfd *, bfd_vma)); -/* Return cached file modification time (e.g. as read from archive header + + PROTO(boolean, bfd_set_start_address,(bfd *, bfd_vma)); + +/* + + bfd_get_mtime + +Return cached file modification time (e.g. as read from archive header for archive members, or from file system if we have been called before); else determine modify time, cache it, and return it. +*/ + + PROTO(long, bfd_get_mtime, (bfd *)); +/* + + stuff */ -PROTO(long, bfd_get_mtime, (bfd *)); + + #define bfd_sizeof_headers(abfd, reloc) \ BFD_SEND (abfd, _bfd_sizeof_headers, (abfd, reloc)) @@ -1093,195 +1403,274 @@ PROTO(long, bfd_get_mtime, (bfd *)); #define bfd_coff_swap_lineno_in(a,e,i) \ BFD_SEND ( a, _bfd_coff_swap_lineno_in, (a,e,i)) -/* What this does +/* + + --------------------------------END FROM bfd.c*/ + +/* FROM archive.c*/ +/* ------------------------------START FROM archive.c + bfd_get_next_mapent +What this does */ -PROTO(symindex, bfd_get_next_mapent, (bfd *, symindex, carsym **)); -/* Used whilst processing archives. Sets the head of the chain of bfds + PROTO(symindex, bfd_get_next_mapent, (bfd *, symindex, carsym **)); + +/* + + bfd_set_archive_head +Used whilst processing archives. Sets the head of the chain of bfds contained in an archive to @var{new_head}. (see chapter on archives) */ -PROTO(boolean, bfd_set_archive_head, (bfd *output, bfd *new_head));PROTO(bfd *, bfd_get_elt_at_index, (bfd *, int)); -/* Initially provided a bfd containing an archive and NULL, opens a bfd + PROTO(boolean, bfd_set_archive_head, (bfd *output, bfd *new_head)); + +/* + + bfd_get_elt_at_index +*/ + + PROTO(bfd *, bfd_get_elt_at_index, (bfd *, int)); + +/* + + bfd_openr_next_archived_file +Initially provided a bfd containing an archive and NULL, opens a bfd on the first contained element and returns that. Subsequent calls to bfd_openr_next_archived_file should pass the archive and the previous return value to return a created bfd to the next contained element. NULL is returned when there are no more. - */ -PROTO(bfd*, bfd_openr_next_archived_file, + + PROTO(bfd*, bfd_openr_next_archived_file, (bfd *archive, bfd *previous)); -/* Returns a read-only string explaining what program was running when -it failed and produced the core file being read -*/ -PROTO(CONST char *, bfd_core_file_failing_command, (bfd *)); -/* Returns the signal number which caused the core dump which generated -the file the bfd is attatched to. +/* -*/ -PROTO(int, bfd_core_file_failing_signal, (bfd *)); -/* Returns @code{true} if the core file attatched to @var{core_bfd} was -generated by a run of the executable file attatched to @var{exec_bfd}, -or else @code{false}. -*/ -PROTO(boolean, core_file_matches_executable_p, - (bfd *core_bfd, bfd *exec_bfd)); -/* The relocation routine returns as a status an enumerated type: + --------------------------------END FROM archive.c*/ +/* FROM core.c*/ + +/* FROM reloc.c*/ +/* ------------------------------START FROM reloc.c + bfd_perform_relocation +The relocation routine returns as a status an enumerated type: */ + typedef enum bfd_reloc_status { +/* No errors detected +*/ - /* No errors detected - */ bfd_reloc_ok, - /* The relocation was performed, but there was an overflow. - */ +/* +The relocation was performed, but there was an overflow. +*/ + bfd_reloc_overflow, - /* The address to relocate was not within the section supplied - */ +/* +The address to relocate was not within the section supplied +*/ + bfd_reloc_outofrange, - /* Used by special functions - */ +/* +Used by special functions +*/ + bfd_reloc_continue, - /* Unused - */ +/* +Unused +*/ + bfd_reloc_notsupported, - /* Unsupported relocation size requested. - */ +/* +Unsupported relocation size requested. +*/ + bfd_reloc_other, - /* The symbol to relocate against was undefined. - */ +/* +The symbol to relocate against was undefined. +*/ + bfd_reloc_undefined, - /* The relocaction was performed, but may not be ok - presently generated - only when linking i960 coff files with i960 b.out symbols. - */ +/* +The relocaction was performed, but may not be ok - presently generated +only when linking i960 coff files with i960 b.out symbols. +*/ + bfd_reloc_dangerous } bfd_reloc_status_enum_type; + +/* +*/ + typedef struct reloc_cache_entry { - /* A pointer into the canonical table of pointers - */ +/* +A pointer into the canonical table of pointers +*/ + struct symbol_cache_entry **sym_ptr_ptr; - /* offset in section - */ +/* +offset in section +*/ + rawdata_offset address; - /* addend for relocation value - */ +/* +addend for relocation value +*/ + bfd_vma addend; - /* if sym is null this is the section - */ +/* +if sym is null this is the section +*/ + struct sec *section; - /* Pointer to how to perform the required relocation - */ +/* +Pointer to how to perform the required relocation +*/ + CONST struct reloc_howto_struct *howto; } arelent; -/* The @code{reloc_howto_type} is a structure which contains all the -information that bfd needs to know to tie up a back end's data. +/* + reloc_howto_type +The @code{reloc_howto_type} is a structure which contains all the +information that bfd needs to know to tie up a back end's data. */ + typedef CONST struct reloc_howto_struct { +/* The type field has mainly a documetary use - the back end can to what +it wants with it, though the normally the back end's external idea of +what a reloc number would be would be stored in this field. For +example, the a PC relative word relocation in a coff environment would +have the type 023 - because that's what the outside world calls a +R_PCRWORD reloc. +*/ - /* The type field has mainly a documetary use - the back end can to what - it wants with it, though the normally the back end's external idea of - what a reloc number would be would be stored in this field. For - example, the a PC relative word relocation in a coff environment would - have the type 023 - because that's what the outside world calls a - R_PCRWORD reloc. - */ unsigned int type; - /* The value the final relocation is shifted right by. This drops - unwanted data from the relocation. - */ +/* +The value the final relocation is shifted right by. This drops +unwanted data from the relocation. +*/ + unsigned int rightshift; - /* The size of the item to be relocated - 0, is one byte, 1 is 2 bytes, 3 - is four bytes. - */ +/* +The size of the item to be relocated - 0, is one byte, 1 is 2 bytes, 3 +is four bytes. +*/ + unsigned int size; - /* Now obsolete - */ +/* +Now obsolete +*/ + unsigned int bitsize; - /* Notes that the relocation is relative to the location in the data - section of the addend. The relocation function will subtract from the - relocation value the address of the location being relocated. - */ +/* +Notes that the relocation is relative to the location in the data +section of the addend. The relocation function will subtract from the +relocation value the address of the location being relocated. +*/ + boolean pc_relative; - /* Now obsolete - */ +/* +Now obsolete +*/ + unsigned int bitpos; - /* Now obsolete - */ +/* +Now obsolete +*/ + boolean absolute; - /* Causes the relocation routine to return an error if overflow is - detected when relocating. - */ +/* +Causes the relocation routine to return an error if overflow is +detected when relocating. +*/ + boolean complain_on_overflow; - /* If this field is non null, then the supplied function is called rather - than the normal function. This allows really strange relocation - methods to be accomodated (eg, i960 callj instructions). - */ +/* +If this field is non null, then the supplied function is called rather +than the normal function. This allows really strange relocation +methods to be accomodated (eg, i960 callj instructions). +*/ + bfd_reloc_status_enum_type (*special_function)(); - /* The textual name of the relocation type. - */ +/* +The textual name of the relocation type. +*/ + char *name; - /* When performing a partial link, some formats must modify the - relocations rather than the data - this flag signals this. - */ +/* +When performing a partial link, some formats must modify the +relocations rather than the data - this flag signals this. +*/ + boolean partial_inplace; - /* The src_mask is used to select what parts of the read in data are to - be used in the relocation sum. Eg, if this was an 8 bit bit of data - which we read and relocated, this would be 0x000000ff. When we have - relocs which have an addend, such as sun4 extended relocs, the value - in the offset part of a relocating field is garbage so we never use - it. In this case the mask would be 0x00000000. - */ +/* +The src_mask is used to select what parts of the read in data are to +be used in the relocation sum. Eg, if this was an 8 bit bit of data +which we read and relocated, this would be 0x000000ff. When we have +relocs which have an addend, such as sun4 extended relocs, the value +in the offset part of a relocating field is garbage so we never use +it. In this case the mask would be 0x00000000. +*/ + bfd_word src_mask; +/* The dst_mask is what parts of the instruction are replaced into the +instruction. In most cases src_mask == dst_mask, except in the above +special case, where dst_mask would be 0x000000ff, and src_mask would +be 0x00000000. +*/ - /* The dst_mask is what parts of the instruction are replaced into the - instruction. In most cases src_mask == dst_mask, except in the above - special case, where dst_mask would be 0x000000ff, and src_mask would - be 0x00000000. - */ bfd_word dst_mask; - /* When some formats create PC relative instructions, they leave the - value of the pc of the place being relocated in the offset slot of the - instruction, so that a PC relative relocation can be made just by - adding in an ordinary offset (eg sun3 a.out). Some formats leave the - displacement part of an instruction empty (eg m88k bcs), this flag - signals the fact. - */ +/* +When some formats create PC relative instructions, they leave the +value of the pc of the place being relocated in the offset slot of the +instruction, so that a PC relative relocation can be made just by +adding in an ordinary offset (eg sun3 a.out). Some formats leave the +displacement part of an instruction empty (eg m88k bcs), this flag +signals the fact. +*/ + boolean pcrel_offset; } reloc_howto_type; -/* The HOWTO define is horrible and will go away. +/* + + HOWTO +The HOWTO define is horrible and will go away. */ #define HOWTO(C, R,S,B, P, BI, ABS, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC) \ {(unsigned)C,R,S,B, P, BI, ABS,O,SF,NAME,INPLACE,MASKSRC,MASKDST,PC} + +/* + + reloc_chain +*/ typedef unsigned char bfd_byte; typedef struct relent_chain { @@ -1289,8 +1678,9 @@ typedef struct relent_chain { struct relent_chain *next; } arelent_chain; +/* -/* If an output_bfd is supplied to this function the generated image +If an output_bfd is supplied to this function the generated image will be relocatable, the relocations are copied to the output file after they have been changed to reflect the new state of the world. There are two ways of reflecting the results of partial linkage in an @@ -1302,14 +1692,22 @@ these formats the output data slot will always be big enough for the addend. Complex reloc types with addends were invented to solve just this problem. */ -PROTO(bfd_reloc_status_enum_type, + PROTO(bfd_reloc_status_enum_type, bfd_perform_relocation, (bfd * abfd, arelent *reloc_entry, PTR data, asection *input_section, bfd *output_bfd)); -/* @node bfd_target + +/* + + --------------------------------END FROM reloc.c*/ + +/* FROM targets.c*/ +/* ------------------------------START FROM targets.c + bfd_target +@node bfd_target @subsection bfd_target This structure contains everything that BFD knows about a target. It includes things like its byte order, name, what routines to call @@ -1317,30 +1715,35 @@ to do various operations, etc. Every BFD points to a target structure with its "xvec" member. - Shortcut for declaring fields which are prototyped function pointers, while avoiding anguish on compilers that don't support protos. */ + #define SDEF(ret, name, arglist) \ PROTO(ret,(*name),arglist) #define SDEF_FMT(ret, name, arglist) \ PROTO(ret,(*name[bfd_type_end]),arglist) -/* These macros are used to dispatch to functions through the bfd_target +/* +These macros are used to dispatch to functions through the bfd_target vector. They are used in a number of macros further down in bfd.h, and are also used when calling various routines by hand inside the bfd implementation. The "arglist" argument must be parenthesized; it contains all the arguments to the called function. */ + #define BFD_SEND(bfd, message, arglist) \ ((*((bfd)->xvec->message)) arglist) -/* For operations which index on the bfd format +/* +For operations which index on the bfd format */ + #define BFD_SEND_FMT(bfd, message, arglist) \ (((bfd)->xvec->message[(int)((bfd)->format)]) arglist) -/* This is the struct which defines the type of BFD this is. The +/* +This is the struct which defines the type of BFD this is. The "xvec" member of the struct bfd itself points here. Each module that implements access to a different target under BFD, defines one of these. @@ -1348,18 +1751,22 @@ one of these. FIXME, these names should be rationalised with the names of the entry points which call them. Too bad we can't have one macro to define them both! - */ + typedef struct bfd_target { - /* identifies the kind of target, eg SunOS4, Ultrix, etc - */ +/* +identifies the kind of target, eg SunOS4, Ultrix, etc +*/ + char *name; - /* The "flavour" of a back end is a general indication about the contents - of a file. - */ +/* +The "flavour" of a back end is a general indication about the contents +of a file. +*/ + enum target_flavour_enum { bfd_target_aout_flavour_enum, bfd_target_coff_flavour_enum, @@ -1367,40 +1774,56 @@ typedef struct bfd_target bfd_target_oasys_flavour_enum, bfd_target_srec_flavour_enum} flavour; - /* The order of bytes within the data area of a file. - */ +/* +The order of bytes within the data area of a file. +*/ + boolean byteorder_big_p; - /* The order of bytes within the header parts of a file. - */ +/* +The order of bytes within the header parts of a file. +*/ + boolean header_byteorder_big_p; - /* This is a mask of all the flags which an executable may have set - - from the set @code{NO_FLAGS}, @code{HAS_RELOC}, ...@code{D_PAGED}. - */ +/* +This is a mask of all the flags which an executable may have set - +from the set @code{NO_FLAGS}, @code{HAS_RELOC}, ...@code{D_PAGED}. +*/ + flagword object_flags; - /* This is a mask of all the flags which a section may have set - from - the set @code{SEC_NO_FLAGS}, @code{SEC_ALLOC}, ...@code{SET_NEVER_LOAD}. - */ +/* +This is a mask of all the flags which a section may have set - from +the set @code{SEC_NO_FLAGS}, @code{SEC_ALLOC}, ...@code{SET_NEVER_LOAD}. +*/ + flagword section_flags; - /* The pad character for filenames within an archive header. - */ +/* +The pad character for filenames within an archive header. +*/ + char ar_pad_char; - /* The maximum number of characters in an archive header. - */ +/* +The maximum number of characters in an archive header. +*/ + unsigned short ar_max_namelen; - /* The minimum alignment restriction for any section. - */ +/* +The minimum alignment restriction for any section. +*/ + unsigned int align_power_min; - /* Entries for byte swapping for data. These are different to the other - entry points, since they don't take bfd as first arg. Certain other handlers - could do the same. - */ +/* +Entries for byte swapping for data. These are different to the other +entry points, since they don't take bfd as first arg. Certain other handlers +could do the same. +*/ + SDEF (bfd_vma, bfd_getx64, (bfd_byte *)); SDEF (void, bfd_putx64, (bfd_vma, bfd_byte *)); SDEF (bfd_vma, bfd_getx32, (bfd_byte *)); @@ -1408,8 +1831,10 @@ typedef struct bfd_target SDEF (bfd_vma, bfd_getx16, (bfd_byte *)); SDEF (void, bfd_putx16, (bfd_vma, bfd_byte *)); - /* Byte swapping for the headers - */ +/* +Byte swapping for the headers +*/ + SDEF (bfd_vma, bfd_h_getx64, (bfd_byte *)); SDEF (void, bfd_h_putx64, (bfd_vma, bfd_byte *)); SDEF (bfd_vma, bfd_h_getx32, (bfd_byte *)); @@ -1417,34 +1842,44 @@ typedef struct bfd_target SDEF (bfd_vma, bfd_h_getx16, (bfd_byte *)); SDEF (void, bfd_h_putx16, (bfd_vma, bfd_byte *)); - /* Format dependent routines, these turn into vectors of entry points - within the target vector structure; one for each format to check. - - Check the format of a file being read. Return bfd_target * or zero. - */ +/* +Format dependent routines, these turn into vectors of entry points +within the target vector structure; one for each format to check. + +Check the format of a file being read. Return bfd_target * or zero. +*/ + SDEF_FMT (struct bfd_target *, _bfd_check_format, (bfd *)); - /* Set the format of a file being written. - */ +/* +Set the format of a file being written. +*/ + SDEF_FMT (boolean, _bfd_set_format, (bfd *)); - /* Write cached information into a file being written, at bfd_close. - */ +/* +Write cached information into a file being written, at bfd_close. +*/ + SDEF_FMT (boolean, _bfd_write_contents, (bfd *)); - /* The following functions are defined in @code{JUMP_TABLE}. The idea is - that the back end writer of @code{foo} names all the routines - @code{foo_}@var{entry_point}, @code{JUMP_TABLE} will built the entries - in this structure in the right order. - - Core file entry points - */ +/* +The following functions are defined in @code{JUMP_TABLE}. The idea is +that the back end writer of @code{foo} names all the routines +@code{foo_}@var{entry_point}, @code{JUMP_TABLE} will built the entries +in this structure in the right order. + +Core file entry points +*/ + SDEF (char *, _core_file_failing_command, (bfd *)); SDEF (int, _core_file_failing_signal, (bfd *)); SDEF (boolean, _core_file_matches_executable_p, (bfd *, bfd *)); - /* Archive entry points - */ +/* +Archive entry points +*/ + SDEF (boolean, _bfd_slurp_armap, (bfd *)); SDEF (boolean, _bfd_slurp_extended_name_table, (bfd *)); SDEF (void, _bfd_truncate_arname, (bfd *, CONST char *, char *)); @@ -1454,8 +1889,10 @@ typedef struct bfd_target int orl_count, int stridx)); - /* Standard stuff. - */ +/* +Standard stuff. +*/ + SDEF (boolean, _close_and_cleanup, (bfd *)); SDEF (boolean, _bfd_set_section_contents, (bfd *, sec_ptr, PTR, file_ptr, bfd_size_type)); @@ -1463,8 +1900,10 @@ typedef struct bfd_target file_ptr, bfd_size_type)); SDEF (boolean, _new_section_hook, (bfd *, sec_ptr)); - /* Symbols and reloctions - */ +/* +Symbols and reloctions +*/ + SDEF (unsigned int, _get_symtab_upper_bound, (bfd *)); SDEF (unsigned int, _bfd_canonicalize_symtab, (bfd *, struct symbol_cache_entry **)); @@ -1493,8 +1932,10 @@ typedef struct bfd_target SDEF (void, _bfd_debug_info_end, (bfd *)); SDEF (void, _bfd_debug_info_accumulate, (bfd *, struct sec *)); - /* Special entry points for gdb to swap in coff symbol table parts - */ +/* +Special entry points for gdb to swap in coff symbol table parts +*/ + SDEF(void, _bfd_coff_swap_aux_in,( bfd *abfd , PTR ext, @@ -1514,7 +1955,10 @@ typedef struct bfd_target } bfd_target; -/* Returns a pointer to the transfer vector for the object target +/* + +*i bfd_find_target +Returns a pointer to the transfer vector for the object target named target_name. If target_name is NULL, chooses the one in the environment variable GNUTARGET; if that is null or not defined then the first entry in the target list is chosen. Passing in the @@ -1524,12 +1968,25 @@ and "target_defaulted" will be set in the bfd. This causes bfd_check_format to loop over all the targets to find the one that matches the file being read. */ -PROTO(bfd_target *, bfd_find_target,(CONST char *, bfd *)); -/* This function returns a freshly malloced NULL-terminated vector of the + PROTO(bfd_target *, bfd_find_target,(CONST char *, bfd *)); + +/* + +*i bfd_target_list +This function returns a freshly malloced NULL-terminated vector of the names of all the valid bfd targets. Do not modify the names */ -PROTO(CONST char **,bfd_target_list,()); -/* This routine is supplied a bfd and a format. It attempts to verify if + PROTO(CONST char **,bfd_target_list,()); + +/* + + --------------------------------END FROM targets.c*/ + +/* FROM format.c*/ +/* ------------------------------START FROM format.c + +*i bfd_check_format +This routine is supplied a bfd and a format. It attempts to verify if the file attatched to the bfd is indeed compatible with the format specified (ie, one of @code{bfd_object}, @code{bfd_archive} or @code{bfd_core}). @@ -1555,17 +2012,29 @@ none of the backends recognised the file format more than one backend recognised the file format. @end table */ -PROTO(boolean, bfd_check_format, (bfd *abfd, bfd_format format)); -/* This function sets the file format of the supplied bfd to the format + PROTO(boolean, bfd_check_format, (bfd *abfd, bfd_format format)); + +/* + +*i bfd_set_format +This function sets the file format of the supplied bfd to the format requested. If the target set in the bfd does not support the format requested, the format is illegal or the bfd is not open for writing than an error occurs. */ -PROTO(boolean,bfd_set_format,(bfd *, bfd_format)); -/* This function takes one argument, and enumerated type (bfd_format) and + PROTO(boolean,bfd_set_format,(bfd *, bfd_format)); + +/* + +*i bfd_format_string +This function takes one argument, and enumerated type (bfd_format) and returns a pointer to a const string "invalid", "object", "archive", "core" or "unknown" depending upon the value of the enumeration. */ -PROTO(CONST char *, bfd_format_string, (bfd_format)); -#endif + PROTO(CONST char *, bfd_format_string, (bfd_format)); +/* + + --------------------------------END FROM format.c*/ + +#endif |