mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-25 13:27:26 +08:00
b301b24869
* elf.c (IS_LOADED): Define. (assign_file_positions_for_segments): Don't round up file offset of PT_LOAD segments containing no SEC_LOAD sections, instead round down. Delete code handling link script adjustment of lma. Do the adjust in later code handling similar ajustments. Remove dead code error check. Warn if section lma would require a negative offset adjustment. Tweak lma adjustment to use p_filesz rather than p_memsz. Use p_vaddr + p_memsz inside section loop in place of voff. Don't update voff in section loop. Change voff in segment loop to be an adjustment on top of "off". Set sec->filepos and update "off" later. Test for loadable sections consistently using IS_LOADED. Similarly, test for alloc-only sections other than .tbss consistently. Don't bother checking SEC_ALLOC in PT_LOAD segments. Remove FIXME. Tidy PT_NOTE handling. Use %B and %A in error messages. (assign_file_positions_except_relocs): Use %B in error message. ld/testsuite/ * ld-scripts/overlay-size.d: Don't check .mbss lma. * ld-sh/sh64/mix1.xd: Update for changed .bss file offset. * ld-sh/sh64/shdl32.xd: Likewise. * ld-sh/sh64/shdl64.xd: Likewise.
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.