Alan Modra
47fda0d3d9
* libieee.h (common_header_type): Add last_byte field.
* ieee.c: Add missing prototypes. Some format fixes. (struct output_buffer_struct): Move for availability to prototypes. (ieee_part_after): New function. (ieee_slurp_debug): Use it here. (ieee_seek): Pass in ieee_data_struct rather than bfd. Use ieee_part_after to set last_byte to one past end of current part. Update callers. (ieee_pos): Pass in ieee_data_struct rather than bfd. Update callers. (parse_expression): Don't go beyond the end of the current part. (ieee_slurp_external_symbols): Correct type passed to read_2bytes. (ieee_get_symtab_upper_bound, ieee_get_symtab, ieee_get_symbol_info, ieee_print_symbol, ieee_new_section_hook, ieee_get_reloc_upper_bound, ieee_canonicalize_reloc, block, ieee_set_section_contents, ieee_write_object_contents, ieee_make_empty_symbol): Make static. (ieee_archive_p): Correct comments regarding bfd_read. (ieee_object_p): Similarly. (ieee_mkobject): Move it. Clear output_ptr_start, output_ptr, output_ptr_end, input_ptr_start, input_ptr, input_ptr_end, input_bfd, output_bfd, output_buffer. (do_as_repeat): Write out ieee_set_current_pc_enum value as for do_with_relocs, ie. as a symbol for relocatable files. (ieee_vec): Add comments showing functions referenced by macros.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.
Description
Languages
C
52.1%
Makefile
22.5%
Assembly
12.2%
C++
6.2%
Roff
1.1%
Other
5.3%