Go to file
Tsukasa OI d9fa9b7c33 include: Add macro to ignore -Wunused-but-set-variable
"-Wunused-but-set-variable" warning option can be helpful to track variables
that are written but not read thereafter.  But it can be harmful if some of
the code is auto-generated and we have no ways to deal with it.

The particular example is Bison-generated code.

The new DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE macro can be helpful on
such cases. A typical use of this macro is to place this macro before the
end of user prologues on Bison (.y) files.

include/ChangeLog:

    * diagnostics.h (DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE): New.
2022-09-22 10:53:24 +00:00
bfd Automatic date update in version.in 2022-09-22 00:00:10 +00:00
binutils RISC-V: Implement Ztso extension 2022-09-21 11:43:35 +08:00
config
contrib
cpu
elfcpp
etc
gas RISC-V: Add macro-only operands to validate_riscv_insn 2022-09-22 06:28:19 +00:00
gdb gdb/python: restrict the names accepted by gdb.register_window_type 2022-09-22 10:34:15 +01:00
gdbserver gdbsupport: move include/gdb/fileio.h contents to fileio.h 2022-09-21 14:11:03 -04:00
gdbsupport gdbsupport: move fileio_errno_to_host to fileio.{h,cc} and rename 2022-09-21 14:11:03 -04:00
gnulib
gold New Serbian translations for various binutils sub-directories. 2022-09-20 11:33:16 +01:00
gprof bfd: Stop using -Wstack-usage=262144 when built with Clang 2022-09-14 05:42:17 +00:00
gprofng gprofng: fix -Wduplicated-cond warning 2022-09-21 19:00:00 -07:00
include include: Add macro to ignore -Wunused-but-set-variable 2022-09-22 10:53:24 +00:00
intl
ld ld/testsuite: allow to force another directory for gcc linker 2022-09-22 09:23:18 +02:00
libbacktrace
libctf
libdecnumber
libiberty
opcodes RISC-V: Remove "b" operand type from disassembler 2022-09-22 06:28:19 +00:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure configure: Pass CPPFLAGS_FOR_BUILD to subdirs 2022-09-21 06:14:16 +00:00
configure.ac configure: Pass CPPFLAGS_FOR_BUILD to subdirs 2022-09-21 06:14:16 +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
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
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.