Binutils with MCST patches
Go to file
Simon Marchi b6d7a4bf29 Rename variable with confusing name
I saw this gem of not so legible code in solib-svr4.c (scan_dyntag):

	if (dyn_tag == dyntag)

and thought it deserved a small rename.

This just renames variables to be a bit more clear for those who read the
code. I also constified the parameter because, why not. The same was
done in scan_dyntag_auxv as well.

Tested only by rebuilding, since the change was done mechanically.

gdb/Changelog:

2014-08-01  Simon Marchi  <simon.marchi@ericsson.com>

	* solib-svr4.c (scan_dyntag): Rename dyntag and dyn_tag variables.
	(scan_dyntag_auxv): Same.
2014-08-06 15:32:57 -04:00
bfd daily update 2014-08-06 09:31:04 +09:30
binutils [MIPS] Implement O32 FPXX, FP64 and FP64A ABI extensions 2014-07-29 11:27:59 +01:00
config
cpu or1k: add missing l.msync, l.psync and l.psync instructions. 2014-07-20 20:26:09 +03:00
elfcpp [MIPS] Implement O32 FPXX, FP64 and FP64A ABI extensions 2014-07-29 11:27:59 +01:00
etc
gas Add -momit_lock_prefix=[no|yes] option 2014-08-06 08:32:01 -07:00
gdb Rename variable with confusing name 2014-08-06 15:32:57 -04:00
gold Modify new gold test to pass on powerpc64le 2014-08-06 22:15:48 +09:30
gprof Rename configure.in to configure.ac 2014-07-04 13:40:28 +09:30
include [MIPS] Rename COPROC related macros 2014-07-29 13:58:54 +01:00
intl
ld PR14918, lto always links in libgcc_s.so 2014-08-06 13:31:47 +09:30
libdecnumber
libiberty
opcodes [MIPS] Rename COPROC related macros 2014-07-29 13:58:54 +01:00
readline
sim
texinfo
.cvsignore
.gitattributes Add a .gitattributes file for use with git-merge-changelog 2014-07-25 18:07:23 -04:00
.gitignore
ChangeLog or1k: GDB not supported for or1k*-*-rtems* 2014-07-27 18:43:52 +02:00
compile
config-ml.in
config.guess
config.rpath
config.sub Import config.sub from upstream config repo 2014-07-29 07:04:52 -04:00
configure or1k: GDB not supported for or1k*-*-rtems* 2014-07-27 18:43:52 +02:00
configure.ac or1k: GDB not supported for or1k*-*-rtems* 2014-07-27 18:43:52 +02:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release
symlink-tree
ylwrap

		   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.