Binutils with MCST patches
Go to file
Yao Qi 88af8ea80b Don't pass -m32 to libcc1 on arm-linux
When I run gdb.compile/ tests on arm-linux, I get the following fails,

(gdb) compile code -- ;^M
arm-none-linux-gnueabihf-gcc: error: unrecognized command line option '-m32'; did you mean '-mbe32'?^M
Compilation failed.^M
(gdb) compile code (void) param^M
arm-none-linux-gnueabihf-gcc: error: unrecognized command line option '-m32'; did you mean '-mbe32'?^M
Compilation failed.^M
(gdb) FAIL: gdb.compile/compile-ops.exp: compile code (void) param

This patch fixes it by implementing gcc_target_options gdbarch method
for arm-linux to override option "-m32".

gdb:

2018-01-19  Yao Qi  <yao.qi@linaro.org>

	* arm-linux-tdep.c (arm_linux_gcc_target_options): New function.
	(arm_linux_init_abi): Install it.
2018-01-19 09:16:45 +00:00
bfd Automatic date update in version.in 2018-01-19 00:00:31 +00:00
binutils Update Bulgarian translation of the binutils sub-directory 2018-01-18 09:38:59 +00:00
config Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
cpu Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
elfcpp Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
etc
gas RISC-V: Fix bug in prior addi/c.nop patch. 2018-01-17 14:04:16 -08:00
gdb Don't pass -m32 to libcc1 on arm-linux 2018-01-19 09:16:45 +00:00
gold PowerPC PLT stub alignment fixes 2018-01-18 22:25:21 +10:30
gprof Update pot files 2018-01-13 13:56:48 +00:00
include Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
intl
ld Also xfail ld-elf/group1.d for Solaris 2018-01-18 17:21:24 -08:00
libdecnumber
libiberty Update the libiberty sources with the latest patches found in the master sources. 2018-01-10 13:57:48 +00:00
opcodes RISC-V: Fix bug in prior addi/c.nop patch. 2018-01-17 14:04:16 -08:00
readline
sim
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Update notes on how to make a release 2018-01-13 14:29:27 +00:00
compile
config-ml.in Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
config.guess Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
config.rpath
config.sub Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
configure Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
configure.ac Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00: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.sh Update notes on how to make a release 2018-01-13 14:29:27 +00:00
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.