[PATCH v3 17/18] PR ld/24600: BFD: Add general linker support for fake archives
Jan Beulich
jbeulich@suse.com
Tue Dec 9 15:34:33 GMT 2025
More information about the Binutils mailing list
Tue Dec 9 15:34:33 GMT 2025
- Previous message (by thread): [PATCH v3 16/18] BFD: Add BFD pointer member to archive member references
- Next message (by thread): [PATCH v10 08/28] bfd: write Object Attributes v2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 20.11.2025 11:57, Maciej W. Rozycki wrote:
> --- binutils-gdb.orig/bfd/opncls.c
> +++ binutils-gdb/bfd/opncls.c
> @@ -496,6 +496,47 @@ bfd_openstreamr (const char *filename, c
>
> /*
> FUNCTION
> + bfd_openr_fake_archive
> +
> +SYNOPSIS
> + bfd *bfd_openr_fake_archive (bfd *fbfd);
> +
> +DESCRIPTION
> + Open a list of BFDs starting from @var{filename} as an artificial
Elsewhere in this file @var{...} refers to function parameters; there is ...
> + archive. Subsequent members of the archive are indicated by each
> + BFD's proxy_handle.abfd member, with the final one holding a NULL
> + pointer there. The newly opened archive will necessarily also be
> + a thin archive as there will be member files only to refer to and
> + no containing archive file.
> +*/
> +
> +bfd *
> +bfd_openr_fake_archive (bfd *fbfd)
... no such function parameter here, though.
Overall I feel like the underlying idea of "file collections" (plus why /
where / when it's useful) isn't explained sufficiently in the description.
Maybe that would become more clear by reading the next patch, but I think
the patch here would best be self-contained.
Jan
- Previous message (by thread): [PATCH v3 16/18] BFD: Add BFD pointer member to archive member references
- Next message (by thread): [PATCH v10 08/28] bfd: write Object Attributes v2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list