Binutils with MCST patches
Go to file
John Baldwin 906b4aac4c Use the correct value for the offset of 'kve_protection'.
I had forgotten to convert the decimal output of 'ptype /o' to hex
(but still used a 0x prefix) for the KVE_PROTECTION constant defining
the offset of the 'kve_protection' field in the 'kinfo_vmentry'
structure.  This resulted in garbage permissions for entries in 'info
proc mappings' for FreeBSD core dumps.

gdb/ChangeLog:

	* fbsd-tdep.c (KVE_PROTECTION): Correct value.
2018-01-12 12:05:50 -08:00
bfd Optimize the performance of the group_setup function. 2018-01-12 13:16:17 +00:00
binutils Add notes on how to make a branch and a pre-release snapshot. 2018-01-12 17:52:38 +00:00
config Update top level configure files by synchronizing them with gcc. 2018-01-10 15:29:21 +00:00
cpu
elfcpp
etc
gas Fix compile time warning building aout targeted architectures. 2018-01-12 13:12:17 +00:00
gdb Use the correct value for the offset of 'kve_protection'. 2018-01-12 12:05:50 -08:00
gold Apply: 2018-01-12 11:05:58 -08:00
gprof
include ld: Add "-z separate-code" option to ELF linker 2018-01-11 19:01:52 -08:00
intl
ld pr22374 function pointer initialization 2018-01-12 21:13:11 +10:30
libdecnumber
libiberty Update the libiberty sources with the latest patches found in the master sources. 2018-01-10 13:57:48 +00:00
opcodes Remove VL variants for 4FMAPS and 4VNNIW insns. 2018-01-11 03:09:47 +03:00
readline
sim
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog oops - updates to ChangeLog omitted by accident from previous delta. 2018-01-10 15:35:34 +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
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.