Home
last modified time | relevance | path

Searched refs:BFD (Results 1 – 25 of 94) sorted by relevance

1234

/mirbsd/src/gnu/usr.bin/binutils/bfd/doc/
Dbfd.texinfo32 This file documents the BFD library.
55 @settitle LIB BFD, the Binary File Descriptor Library
60 @subtitle First Edition---BFD version < 3.0 % Since no product is stable berfore version 3.0 :-)
72 \hfill {\it BFD}, \manvers\par
97 * Overview:: Overview of BFD
98 * BFD front end:: BFD front end
99 * BFD back ends:: BFD back ends
104 @node Overview, BFD front end, Top, Top
106 @cindex BFD
108 BFD is a package which allows applications to use the
[all …]
Dbfdint.texi7 @settitle BFD Internals
10 @title{BFD Internals}
17 @top BFD Internals
21 This document describes some BFD internal information which may be
22 helpful when working on BFD. It is very incomplete.
30 * BFD overview:: BFD overview
31 * BFD guidelines:: BFD programming guidelines
32 * BFD target vector:: BFD target vector
33 * BFD generated files:: BFD generated files
34 * BFD multiple compilations:: Files compiled multiple times in BFD
[all …]
Dbfdt.texi2 A BFD has type @code{bfd}; objects of this type are the
3 cornerstone of any application using BFD. Using BFD
4 consists of making references though the BFD and to data in the BFD.
15 /* A unique identifier of the BFD */
18 /* The filename the application opened the BFD with. */
25 to the file backing the BFD. */
34 BFD was opened. This is used to select which matching algorithm
42 /* When a file is closed by the caching routines, BFD retains
59 /* The format which belongs to the BFD. (object, core, etc.) */
62 /* The direction with which the BFD was opened. */
[all …]
Dbfdsumm.texi1 @c This summary of BFD is shared by the BFD and LD docs.
2 When an object file is opened, BFD subroutines automatically determine
8 BFD reads from different sections of the file and processes them.
10 tables. Each BFD back end provides a routine for converting
14 relevant BFD back end which reads and converts the table into a canonical
17 another BFD back end routine is called to take the newly
21 * BFD information loss:: Information Loss
22 * Canonical format:: The BFD canonical object-file format
25 @node BFD information loss
29 supported by BFD do not provide identical facilities, and
[all …]
Dopncls.texi13 Return a pointer to the created BFD. If @var{fd} is not -1,
21 The new BFD is marked as cacheable iff @var{fd} is -1.
35 @var{target}. Return a pointer to the created BFD.
52 @code{fopen}. It opens a BFD on a file already described by the
57 cached by BFD (opened as needed, closed as needed to free
60 call bfd_set_cacheable(bfd, 1) on the returned BFD. The default
62 until @code{bfd_close}, and will not be affected by BFD operations
75 Open a BFD for read access on an existing stdio stream. When
76 the BFD is passed to @code{bfd_close}, the stream will be closed.
95 Create and return a BFD backed by a read-only @var{stream}.
[all …]
Dformat.texi2 A format is a BFD concept of high level file contents type. The
3 formats supported by BFD are:
10 The BFD may contain data, symbols, relocations and debug info.
17 The BFD contains other BFDs and an optional index.
24 The BFD contains the result of an executable core dump.
33 Verify if the file attached to the BFD @var{abfd} is compatible
37 If the BFD has been set to a specific target before the
94 This function sets the file format of the BFD @var{abfd} to the
95 format @var{format}. If the target set in the BFD does not
96 support the format requested, the format is invalid, or the BFD
Dtargets.texi5 Each port of BFD to a different machine requires the creation
7 part of BFD is a structure containing pointers to functions
8 which perform certain low level operations on files. BFD
13 target are unknown. BFD uses various mechanisms to determine
19 Create a BFD by calling the internal routine
21 target string supplied to @code{bfd_openr} and the new BFD pointer.
31 as the target type, and set @code{target_defaulted} in the BFD to
46 @code{bfd_open_file}, and returns the BFD.
48 Once the BFD has been opened and the target selected, the file
50 @code{bfd_check_format} on the BFD with a suggested format.
[all …]
Darchive.texi5 An archive (or library) is just another BFD. It has a symbol
8 The big difference between an archive BFD and an ordinary BFD
22 @code{next} pointer in a BFD. The first one is findable through
24 @code{bfd_set_archive_head} (q.v.). A given BFD may be in only one
27 As expected, the BFD archive code is more general than the
28 archive code of any given environment. BFD archives may
51 Archives are supported in BFD in @code{archive.c}.
90 Provided a BFD, @var{archive}, containing an archive and NULL, open
91 an input BFD on the first contained element and returns that.
94 BFD to the next contained element. NULL is returned when there
Dsyms.texi2 BFD tries to maintain as much symbol information as it can when
3 it moves information from file to file. BFD passes information
5 application requests the symbol table, BFD reads the table in
12 a BFD is read in. On output, the coff back end can reconstruct
14 information unique to coff which BFD doesn't know or
17 would be lost. The symbol table of a BFD
19 made. Then the BFD back end fills in a table provided by the
21 output symbols, the application provides BFD with a table of
35 There are two stages to reading a symbol table from a BFD:
66 connected to the BFD; it is freed when the BFD is closed.
[all …]
Dcache.texi2 The file caching mechanism is embedded within BFD and allows
9 the required BFD is open. If not, then it chooses a file to
29 Zero, or a pointer to the topmost BFD on the chain. This is
36 Check to see if the required BFD is the same as the last one
37 looked up. If so, then it can use the stream in the BFD with
54 Add a newly opened BFD to the cache.
63 Remove the BFD @var{abfd} from the cache. If the attached file is open,
93 BFD so that future accesses know the file is open. If the @code{FILE *}
Darchures.texi2 BFD keeps one atom in a BFD describing the
3 architecture of the data attached to the BFD: a pointer to a
6 Pointers to structures can be requested independently of a BFD
8 without access to an open BFD.
16 When BFD starts up, all the architectures are called with an
22 BFD's idea of an architecture is implemented in @file{archures.c}.
339 within BFD.
384 Figure out if BFD supports any cpu which could be described with
396 of all the valid BFD architectures. Do not modify the names.
417 generic state. A BFD starts life by pointing to this
[all …]
Dinit.texi2 These are the functions that handle initializing a BFD.
11 This routine must be called before any other BFD function to
Dsection.texi2 The raw data contained within a BFD is maintained through the
3 section abstraction. A single BFD may have any number of
7 Sections are supported in BFD in @code{section.c}.
18 When a BFD is opened for reading, the section structures are
19 created and attached to the BFD.
28 Sometimes a BFD will contain more than the ``natural'' number of
32 BFD. For example, the linker creates an extra section
33 @code{COMMON} for each input file's BFD to hold information about
48 To write a new object style BFD, the various sections to be
49 written have to be created. They are attached to the BFD in
[all …]
Daoutx.texi5 BFD supports a number of different flavours of a.out format,
24 other methods which BFD requires. It is included by
84 your host system, will produce a BFD target that will access
168 Initialize BFD @var{abfd} for use with a.out files.
198 Set the architecture and the machine of the BFD @var{abfd} to the
211 Called by the BFD in response to a @code{bfd_make_section}
Delf.texi4 BFD support for ELF formats is being worked on.
20 Since BFD hides string tables from callers, GDB needs to use an
Dcoffcode.texi2 BFD supports a number of different flavours of coff format.
36 You can verify that your new BFD backend works quite simply by
80 Each flavour of coff supported in BFD has its own header file
96 moment. To port BFD, that person will have to add more @code{#defines}.
100 table on its own, but uses BFD to fix things up. More of the
107 saving the internal BFD overhead, but uses BFD to swap things
109 allows BFD (and thus the linker) to use the same header files
113 The simple canonical form for symbols used by BFD is not rich
142 the canonical table used by the BFD application. Each symbol
154 structure remembers the BFD from which the symbol was taken, and on
[all …]
Dlinker.texi3 The linker uses three special entry points in the BFD target
5 these entry points when creating a new BFD back end, since
17 sections as directed by the linker script and lets BFD handle
83 object file, BFD must add any relevant symbol information to
84 the hash table. For an archive, BFD must determine which
160 BFD. However, the information should only be saved if the
226 the @code{_bfd_final_link} entry point of the output BFD. This
237 point when the BFD is closed. The two entry points must work
267 created by the BFD backend, but do not correspond to any input
282 to a BFD of the same format as the output BFD must be handled
[all …]
Dbfdio.texi5 Each @code{BFD} has an instance of this class and all file I/O is
50 associated with BFD @var{abfd}.
53 so we can get the exact size of the object the BFD applies to, since
/mirbsd/src/gnu/usr.bin/binutils/bfd/
Daout-ns32k.c134 #define CTOR_TABLE_RELOC_HOWTO(BFD) (MY (howto_table) + 14) argument
163 #define MY_reloc_howto(BFD, REL, IN, EX, PC) \ argument
164 MY (reloc_howto) (BFD, REL, &IN, &EX, &PC)
193 #define MY_put_reloc(BFD, EXT, IDX, VAL, HOWTO, RELOC) \ argument
194 MY (put_reloc) (BFD, EXT, IDX, VAL, HOWTO, RELOC)
Daout-tic30.c45 #define MY_reloc_howto(BFD, REL, IN, EX, PC) tic30_aout_reloc_howto (BFD, REL, & IN, & EX, & PC) argument
305 #define bfd_getb_24(BFD,ADDR) \ argument
306 (bfd_get_8 (BFD, ADDR ) << 16) | \
307 (bfd_get_8 (BFD, ADDR + 1) << 8) | \
308 (bfd_get_8 (BFD, ADDR + 2) )
310 #define bfd_putb_24(BFD,DATA,ADDR) \ argument
311 bfd_put_8 (BFD, (bfd_byte) ((DATA >> 16) & 0xFF), ADDR ); \
312 bfd_put_8 (BFD, (bfd_byte) ((DATA >> 8) & 0xFF), ADDR + 1); \
313 bfd_put_8 (BFD, (bfd_byte) ( DATA & 0xFF), ADDR + 2)
Daout-arm.c136 #define MY_reloc_howto(BFD, REL, IN, EX, PC) \ argument
137 MY (reloc_howto) (BFD, REL, &IN, &EX, &PC)
186 #define MY_put_reloc(BFD, EXT, IDX, VAL, HOWTO, RELOC) \ argument
187 MY (put_reloc) (BFD, EXT, IDX, VAL, HOWTO, RELOC)
218 #define MY_relocatable_reloc(HOW, BFD, REL, AMOUNT, ADDR) \ argument
219 MY (relocatable_reloc) (HOW, BFD, REL, &(AMOUNT), ADDR)
Daout-cris.c99 #define SET_ARCH_MACH(BFD, EXEC) \ argument
100 MY_set_arch_mach (BFD, DEFAULT_ARCH, N_MACHTYPE (EXEC))
/mirbsd/src/gnu/usr.bin/binutils/ld/emultempl/
Dm68kelf.em53 input file with a nonzero .data section. The BFD backend will fill in
60 /* As first-order business, make sure that each input BFD is either
61 COFF or ELF. We need to call a special BFD backend function to
75 read in the relocs into BFD canonical form, which would waste
133 /* If we are generating embedded relocs, call a special BFD backend
Dm68kcoff.em54 .data section. The BFD backend will fill in these sections with
71 /* As first-order business, make sure that each input BFD is COFF. It
83 read in the relocs into BFD canonical form, which would waste
123 BFD backend routine to do the work. */
/mirbsd/src/gnu/usr.bin/binutils/gas/config/
Dobj-ieee.h22 #define BFD 1 macro

1234