Go to file
Torbjörn SVENSSON 998a4f589d libctf: Sanitize error types for PR 30836
Made sure there is no implicit conversion between signed and unsigned
return value for functions setting the ctf_errno value.
An example of the problem is that in ctf_member_next, the "offset" value
is either 0L or (ctf_id_t)-1L, but it should have been 0L or -1L.
The issue was discovered while building a 64 bit ld binary to be
executed on the Windows platform.
Example object file that demonstrates the issue is attached in the PR.

libctf/
	Affected functions adjusted.

Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
Co-Authored-By: Yvan ROUX <yvan.roux@foss.st.com>
2023-10-17 17:31:20 +02:00
bfd LoongArch: readelf -d RELASZ excludes .rela.plt size 2023-10-17 14:57:04 +08:00
binutils objcopy: Fix name of the field modified by pe_stack_reserve. 2023-10-16 10:37:23 +02:00
config
contrib
cpu
elfcpp
etc
gas RISC-V: Add "lp64e" ABI support 2023-10-16 04:11:07 +00:00
gdb [gdb/cli] Keep track of styling failures in source_cache 2023-10-17 11:38:06 +02:00
gdbserver Move -lsocket check to common.m4 2023-10-12 18:23:13 -06:00
gdbsupport Move -lsocket check to common.m4 2023-10-12 18:23:13 -06:00
gnulib
gold
gprof
gprofng gprofng: Use the correct application name in error messages 2023-10-10 20:53:22 -07:00
include RISC-V: Fix typo 2023-10-17 02:09:44 +00:00
intl
ld Update the documentation of the LINKER_VERSIOn script command to actually mention the name of the command. 2023-10-17 10:42:44 +01:00
libbacktrace
libctf libctf: Sanitize error types for PR 30836 2023-10-17 17:31:20 +02:00
libdecnumber
libiberty
libsframe
opcodes opcodes: microblaze: Add new bit-field instructions 2023-10-15 09:28:10 -07:00
readline
sim sim: mips: fix printf string 2023-10-15 16:25:13 +05:45
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
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 sim: add distclean dep for gnulib 2023-10-15 23:00:33 +05:45
Makefile.in sim: add distclean dep for gnulib 2023-10-15 23:00:33 +05:45
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
SECURITY.txt
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.