mirror of
https://github.com/bminor/binutils-gdb.git
synced 2026-02-07 08:42:31 +00:00
548332a43f
This patch applies on top of the upstream branch users/ibhagat/sframe-v3-jan14-v4. I attempted to see what the terminology change would look like. This patch is my first shabby attempt. Whats not attempted, but needs to be covered: - (#1) The spec defines "fre_offset_count" and "fre_offset_size" - (#2) There are other constants: SFRAME_FRE_OFFSET_1B, SFRAME_FRE_OFFSET_2B, SFRAME_FRE_OFFSET_4B. Changing these constants is a search-replace patch touching gas/ and ld/ and libsframe/, not attempted either. - (#3) Control/Register Word, Displacement Word does not seem to fit very well: The "Control/Register Word" contains the register data, so I kept the name as such, and not "Control Word" What do you think ? I do not prefer to do this last minute change anymore; there could be more renames needed in code once we start from (#2) above. (#1) could be addressed by renaming those to "fre_dataitem_count", and "fre_dataitem_size", but I find the latter even more awkward. More misfit like feeling arises with (#3). That said, I will reconsider if your judgement is different. Please let me know what you think.
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, and so on. 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.