Binutils with MCST patches
Go to file
Simon Marchi 3015c06465 Update comment in remote_can_async_p
I find this comment counter intuitive, and it probably predates the
always-target-async change.  AFAIK, remote will always be async, unless
the user explicitly prevents it with "maint set target-async off".

gdb/ChangeLog:

	* remote.c (remote_can_async_p): Update comment.
2017-01-12 11:15:02 -05:00
bfd Automatic date update in version.in 2017-01-12 00:00:25 +00:00
binutils Fix compile time warning about pointer comparison. 2017-01-10 11:45:12 +00:00
config picflag.m4 high bit set in comment 2017-01-05 00:02:57 +10:30
cpu
elfcpp
etc update-copyright.py for binutils 2017-01-05 00:03:07 +10:30
gas Prevent internal assembler errors if a stabs creation function builds an badly formatted input string. 2017-01-12 14:56:13 +00:00
gdb Update comment in remote_can_async_p 2017-01-12 11:15:02 -05:00
gold Fix more compile errors with GCC 4.2. 2017-01-11 13:42:24 -08:00
gprof
include [DWARF] Sync GCC dwarf.def change on AArch64 2017-01-04 14:27:52 +00:00
intl
ld x86-64: Correct unwind info for the BND PLT 2017-01-11 09:17:05 -08:00
libdecnumber
libiberty Sync libiberty from gcc 2017-01-05 00:03:07 +10:30
opcodes Return -1 on memory error in print_insn_msp430 2017-01-12 09:40:41 +00:00
readline
sim Fix problems with the implementation of the uzp1 and uzp2 instructions. 2017-01-09 15:44:57 -08:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
src-release.sh
symlink-tree
ylwrap

README

		   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.