Binutils with MCST patches
Go to file
Antoine Tremblay ff71884063 Set emacs default mode for the GDB directory to C++
Since GDB has switched to C++ but the file names are still .c emacs does
not load the proper mode when opening files in the gdb directory.

This patch fixes that by enabling c++ mode.

This patch also fixes indentation tweaks as discussed in this thread:
https://sourceware.org/ml/gdb-patches/2016-12/msg00074.html

Indent with gdb-code-style.el included and the .dir-locals.el is as such:

namespace TestNameSpace {

class test
{
public:
  test test() {}

  int m_a;
};

struct teststruct
{
  int a;
}
}

gdb/ChangeLog:

	* .dir-locals.el: Set c++ mode for the directory and set indent
	properly.
	* gdb-code-style.el: Set c-set-offset 'innamespace as a safe value
	to be used in .dir-locals.el.
2016-12-20 08:42:10 -05:00
bfd Re-work RISC-V gas flags: now we just support -mabi and -march 2016-12-20 12:26:34 +10:30
binutils MIPS16/opcodes: Respect ISA and ASE in disassembly 2016-12-20 12:05:48 +00:00
config sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
cpu
elfcpp
etc
gas MIPS16/opcodes: Respect ISA and ASE in disassembly 2016-12-20 12:05:48 +00:00
gdb Set emacs default mode for the GDB directory to C++ 2016-12-20 08:42:10 -05:00
gold Update testsuite Makefile with missing dependencies. 2016-12-20 01:03:55 -08:00
gprof Fix spelling in comments in C source files (gprof) 2016-11-27 15:04:01 +10:30
include MIPS16: Switch to 32-bit opcode table interpretation 2016-12-20 11:56:32 +00:00
intl
ld Implement and document --gc-keep-exported 2016-12-16 13:49:03 +10:30
libdecnumber
libiberty Port c++/78252 from GCC 2016-12-12 12:52:37 -05:00
opcodes MIPS16/opcodes: Respect ISA and ASE in disassembly 2016-12-20 12:05:48 +00:00
readline
sim MAINTAINERS: Add myself as a MIPS maintainer 2016-12-14 22:19:08 +00:00
texinfo
zlib sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
.cvsignore
.gitattributes
.gitignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure sync binutils config/ with gcc 2016-12-08 21:35:11 +10:30
configure.ac Add support for Fushia OS. 2016-12-02 10:44:29 +00:00
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.