Binutils with MCST patches
Go to file
Tom Tromey 3c473fad8f Add constructor to stap_static_probe_ops
PR build/24937 concerns an error given by the clang provided by a
particular version of macOS.  In particular, it reports

    error: default initialization of an object of const type 'const
    stap_static_probe_ops' without a user-provided default constructor

Although (at least according to sources I found online) this was
resolved as a bug in the standard, it seemed simple enough to work
around this.

Given that this is a trivial build fix, I think it should go on the
gdb 9 branch as well.

2020-01-07  Tom Tromey  <tromey@adacore.com>

	PR build/24937:
	* stap-probe.c (class stap_static_probe_ops): Add constructor.

Change-Id: I18f180c17850f420e9b66afc67f9cb3d8dceb0b3
2020-01-07 09:46:26 -07:00
bfd Automatic date update in version.in 2020-01-07 00:00:51 +00:00
binutils Make bfd_get_8 return a bfd_vma like other bfd_get_* functions 2019-12-11 21:14:19 +10:30
config
contrib
cpu Remove more shifts for sign/zero extension 2019-12-11 21:14:19 +10:30
elfcpp
etc
gas [gas][arm] Add -mwarn-restrict-it 2019-12-11 15:53:26 +00:00
gdb Add constructor to stap_static_probe_ops 2020-01-07 09:46:26 -07:00
gnulib Copyright year range updates after running gdb/copyright.py 2020-01-05 09:44:10 +04:00
gold Introduce new .text.sorted.* sections. 2019-11-26 17:20:10 +01:00
gprof Revert previous delta. 2019-11-15 11:52:50 +00:00
include Copyright year range updates after running gdb/copyright.py 2020-01-05 09:44:10 +04:00
intl
ld Optional matching for run_dump_test 2019-12-08 22:03:53 +10:30
libctf libctf: Add configure check for asprintf (for MinGW) 2020-01-05 09:54:55 +04:00
libdecnumber
libiberty
opcodes Remove more shifts for sign/zero extension 2019-12-11 21:14:19 +10:30
readline Fix compilation of Readline on mingw.org's MinGW 2019-12-23 16:30:35 +02:00
sim Copyright year range updates after running gdb/copyright.py 2020-01-05 09:44:10 +04: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
ar-lib
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
multilib.am
setup.com
src-release.sh
symlink-tree
test-driver
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.