Files
binutils-gdb/bfd
Alan Modra e416bd75c3 warn unused result for bfd IO functions
This patch fixes all the warnings I found in bfd, binutils and ld,
plus some bitrotted COFF_GO32 code that tried to allocate -168ul
bytes.  When the malloc fail was reported these testsuite fails
resulted:

i386-go32  +FAIL: go32 stub
i386-go32  +ERROR: tcl error sourcing /home/alan/src/binutils-gdb/ld/testsuite/ld-i386/i386.exp.
i386-go32  +ERROR: couldn't open "tmpdir/go32stub": no such file or directory
i386-go32  +FAIL: ld-scripts/sane1
i386-go32  +FAIL: ld-scripts/assign-loc
i386-go32  +FAIL: ld-scripts/pr18963

This does result in some warnings in gdb which are fixed in a followup
patch.

bfd/
	* bfdio.c (bfd_read, bfd_write): Add ATTRIBUTE_WARN_UNUSED_RESULT.
	(bfd_tell, bfd_stat, bfd_seek, bfd_mmap): Likewise.
	* bfd-in2.h: Regenerate.
	* coff-rs6000.c (xcoff_write_armap_big) Don't ignore bfd_write
	return value.
	(xcoff_generate_rtinit): Likewise.  Also free data_buffer and
	string_table before returning.
	* coff64-rs6000.c (xcoff64_generate_rtinit): Likewise.
	* coff-stgo32.c (go32exe_check_format): Don't ignore bfd_seek
	return value.
	* coffcode.h (coff_apply_checksum): Don't ignore bfd_write return.
	(coff_write_object_contents <COFF_GO32>): Likewise, and bfd_malloc.
	Fix bitrotted code to look for first section with non-zero filepos.
	* elf64-ia64-vms.c (elf64_vms_write_shdrs_and_ehdr): Don't ignore
	bfd_seek or bfd_write return values.
	* pef.c (bfd_pef_scan_section): Likewise.
	(bfd_pef_read_header, bfd_pef_xlib_read_header): Likewise.
	* vms-misc.c (_bfd_vms_output_end): Likewise.  Return status.
	* vms.h (_bfd_vms_output_end): Update prototype.
	* vms-alpha.c: Pass _bfd_vms_output_end status up call chains.
	* wasm-module.c (wasm_compute_custom_section_file_position): Don't
	ignore bfd_seek or bfd_write return values.
	(wasm_compute_section_file_positions): Likewise.
	* xsym.c (bfd_sym_scan): Don't ignore bfd_seek return value.
	(bfd_sym_read_name_table): Likewise.
binutils/
	* ar.c (print_contents, extract_file): Don't ignore bfd_seek
	return value.
ld/
	* pdb.c (create_section_contrib_substream): Don't ignore bfd_seek
	return value.
	(create_section_header_stream): Likewise.
	* pe-dll.c (pe_get16, pe_get32): Add fail param to return results
	from bfd_seek and bfd_read.
	(pe_implied_import_dll): Handle these fails, and other bfd_seek
	and bfd_read return values.
2023-08-11 16:36:11 +09:30
..
2023-08-09 08:48:09 +09:30
2023-01-02 14:03:22 +10:30
2023-08-02 12:06:23 +01:00
2023-01-10 23:05:31 +10:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-05-03 15:00:05 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-03 07:39:15 -06:00
2023-08-09 08:48:09 +09:30
2023-01-06 21:06:15 +10:30
2023-02-09 20:07:55 +10:30
2023-01-06 21:06:15 +10:30
2023-08-09 08:48:09 +09:30
2023-08-03 07:39:15 -06:00
2023-01-10 09:15:51 +10:30
2023-05-20 10:49:19 +09:30
2023-08-03 07:39:15 -06:00
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-05-03 15:00:05 +09:30
2023-08-02 12:06:23 +01:00
2023-01-20 14:58:04 +01:00
2023-08-02 12:06:23 +01:00
2023-01-20 14:58:04 +01:00
2023-06-01 09:51:59 +09:30
2023-08-02 12:06:23 +01:00
2023-03-24 21:01:43 +10:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-05-17 11:21:43 +09:30
2023-06-14 14:24:50 +09:30
2023-08-09 08:48:09 +09:30
2023-05-17 11:21:43 +09:30
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-04 17:59:01 +09:30
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-06-08 10:31:45 +09:30
2023-06-14 14:24:50 +09:30
2023-08-09 08:48:09 +09:30
2023-06-07 14:16:06 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-01-10 09:15:51 +10:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-06-07 14:16:06 +09:30
2023-06-07 14:16:06 +09:30
2023-08-03 07:39:15 -06:00
2023-05-03 15:00:05 +09:30
2023-08-09 08:48:09 +09:30
2023-06-07 14:16:06 +09:30
2023-08-09 08:48:09 +09:30
2023-06-07 14:16:06 +09:30
2023-05-03 15:00:05 +09:30
2023-05-03 15:00:05 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-03 07:39:15 -06:00
2023-08-03 07:39:15 -06:00
2023-08-11 16:36:11 +09:30
2023-08-03 07:39:15 -06:00
2023-08-03 07:39:15 -06:00
2023-08-03 07:39:15 -06:00
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-05-03 15:00:05 +09:30
2023-05-03 15:00:05 +09:30
2023-05-20 21:06:03 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-09 08:48:09 +09:30
2023-08-11 00:00:24 +00:00
2023-08-02 12:06:23 +01:00
2023-08-09 08:48:09 +09:30
2023-08-11 16:36:11 +09:30
2023-08-09 08:48:09 +09:30
2023-08-11 16:36:11 +09:30

BFD is an object file library.  It permits applications to use the
same routines to process object files regardless of their format.

BFD is used by the GNU debugger, assembler, linker, and the binary
utilities.

The documentation on using BFD is scanty and may be occasionally
incorrect.  Pointers to documentation problems, or an entirely
rewritten manual, would be appreciated.

There is some BFD internals documentation in doc/bfdint.texi which may
help programmers who want to modify BFD.

BFD is normally built as part of another package.  See the build
instructions for that package, probably in a README file in the
appropriate directory.

BFD supports the following configure options:

  --target=TARGET
	The default target for which to build the library.  TARGET is
	a configuration target triplet, such as sparc-sun-solaris.
  --enable-targets=TARGET,TARGET,TARGET...
	Additional targets the library should support.  To include
	support for all known targets, use --enable-targets=all.
  --enable-64-bit-bfd
	Include support for 64 bit targets.  This is automatically
	turned on if you explicitly request a 64 bit target, but not
	for --enable-targets=all.  This requires a compiler with a 64
	bit integer type, such as gcc.
  --enable-shared
	Build BFD as a shared library.
  --with-mmap
	Use mmap when accessing files.  This is faster on some hosts,
	but slower on others.  It may not work on all hosts.

Report bugs in BFD to https://sourceware.org/bugzilla/

Patches are encouraged.  When sending patches, always send the output
of diff -u or diff -c from the original file to the new file.  Do not
send default diff output.  Do not make the diff from the new file to
the original file.  Remember that any patch must not break other
systems.  Remember that BFD must support cross compilation from any
host to any target, so patches which use ``#ifdef HOST'' are not
acceptable.  Please also read the ``Reporting Bugs'' section of the
gcc manual.

Bug reports without patches will be remembered, but they may never get
fixed until somebody volunteers to fix them.

Copyright (C) 2012-2023 Free Software Foundation, Inc.

Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.