Home
last modified time | relevance | path

Searched refs:writing (Results 1 – 25 of 122) sorted by relevance

12345

/toolchain/binutils/binutils-2.25/elfcpp/
DREADME1 elfcpp is a C++ library for reading and writing ELF information. This
/toolchain/binutils/binutils-2.25/bfd/
DTODO5 *writing* object files is still pulled into all the applications
DChangeLog-94953620 caller is writing to a valid section.
3990 writing the symbol strings, use the unsorted symbol table.
4178 total_subspaces when writing the unloadable subspaces.
4309 the reloc's offset when writing .o's. Instead add the section's
4310 vma to the reloc's offset when writing an executable or shared
4775 Use a hash table when writing out ELF symbol names.
5562 * som.c (som_prep_headers): If writing some form of an executable,
6722 (NAME(bfd_elf,write_object_contents)): Permit writing DYNAMIC
8139 built by mips_relax_section when writing out addresses.
8336 subspaces too when writing executables. Never request a negative
[all …]
DChangeLog-91931270 absolute sections when writing out relocs.
1598 separating reading and writing stuff to not refer to a
1734 * archive.c (_bfd_write_archive_contents): At end of file writing,
1740 writing the armap in a BSD file.
1875 (nlm_write_object_contents): Don't bother writing out exported
2685 * elfcode.h: Reimplement segment writing.
2864 file writing to handle unpredictable state of section relocation
2867 data structure with only data that is used only when writing out
3812 rather than caching the whole file and writing it at close time.
7452 routine, if writing, before calling target-dependent
/toolchain/binutils/binutils-2.25/libiberty/
Dpexecute.txh183 the first program in the pipeline; @var{fp} is opened for writing.
188 finished writing data to the pipeline.
216 you fill the input pipe by writing more data to @var{fp}, then there
DREADME46 writing, the special cases are newlib and VxWorks. If a
Dfunctions.texi808 reading and writing.
907 the first program in the pipeline; @var{fp} is opened for writing.
912 finished writing data to the pipeline.
940 you fill the input pipe by writing more data to @var{fp}, then there
1922 if an error occurred while writing to FILE.
/toolchain/binutils/binutils-2.25/ld/scripttempl/
Dmmo.sc104 writing out sections, so this works fine. */
/toolchain/binutils/binutils-2.25/gas/testsuite/gas/arm/
Dmsr-reg.d4 # warning: writing to APSR without specifying a bitmask is deprecated
Dmsr-reg-thumb.d5 # warning: writing to APSR without specifying a bitmask is deprecated
Dmsr-reg-bad.l2 [^:]*:8: writing to APSR without specifying a bitmask is deprecated
/toolchain/binutils/binutils-2.25/gas/doc/
Dc-arm.texi610 be used in Neon instructions instead of writing types after the mnemonic
620 This is equivalent to writing the following:
1054 If you are writing functions in assembly code, and those functions
1145 function you are writing, then your code must save the value before it
1183 The pseudo ops described above are sufficient for writing assembly
Dc-d10v.texi76 either @samp{.s} (short) or @samp{.l} (long) to it. For example, if you are writing
Dc-i386.texi1015 it also supports writing code to run in real mode or in 16-bit protected
1018 be run in 16-bit mode. You can switch @code{@value{AS}} to writing
1038 Note that writing 16-bit code instructions by explicitly specifying a
1123 explicitly request the two byte opcode by writing @samp{sarl %eax}.
Dc-d30v.texi74 either @samp{.s} (short) or @samp{.l} (long) to it. For example, if you are writing
Dinternals.texi109 will be used in writing the object file.
758 Porting GAS to a new CPU requires writing the @file{tc-@var{CPU}} files.
759 Porting GAS to a new object file format requires writing the
861 @code{md_assemble} will do this by calling @code{frag_more} and writing out
/toolchain/binutils/binutils-2.25/gas/
DREADME129 BFD data structures internally, and use BFD for writing object files.
/toolchain/binutils/binutils-2.25/bfd/doc/
Dbfdint.texi158 when writing files.
453 target vector function on a file opened for writing.
457 by @samp{bfd_close} function for a BFD opened for writing. This really
508 mentioned earlier is only called for a BFD opened for writing). Most
768 for a COFF target. This is called when writing out COFF line numbers.
830 with writing out a BFD.
1392 be given to writing ELF specific but ELF target generic code to handle
1543 When writing a @file{elf@var{nn}-@var{cpu}.c} file, you must do the
1566 in the @samp{e_machine} field of the ELF header. As of this writing,
1606 by overriding the relocation reading and writing routines.
/toolchain/binutils/binutils-2.25/ld/
DNEWS166 archive by writing "archive:file".
412 * Added -O option to optimize linker output (as of this writing, this only
591 * There is now support for writing ECOFF files, so ld and the
/toolchain/binutils/binutils-2.25/ld/emultempl/
Dsh64elf.em554 Sorting before writing is done by sh64_elf_final_write_processing. */
/toolchain/binutils/binutils-2.25/bfd/po/
Dzh_CN.po56 msgid "Warning: writing archive was slow: rewriting timestamp\n"
875 msgid "%s: uses _-prefixed symbols, but writing file with non-prefixed symbols"
880 msgid "%s: uses non-prefixed symbols, but writing file with _-prefixed symbols"
Drw.po68 msgid "Warning: writing archive was slow: rewriting timestamp\n"
874 msgid "%s: uses _-prefixed symbols, but writing file with non-prefixed symbols"
879 msgid "%s: uses non-prefixed symbols, but writing file with _-prefixed symbols"
/toolchain/binutils/binutils-2.25/binutils/doc/
Dbinutils.texi482 @cindex writing archive index
489 @cindex not writing archive index
670 Extract each named @var{module} from the current archive, writing them
1357 and writing the archive index, use zero for UIDs, GIDs, timestamps,
1370 and writing the archive index, use their actual UID, GID, timestamp,
2829 rather than writing modified copies under different names.
2911 and writing the archive index, use zero for UIDs, GIDs, timestamps,
2924 and writing the archive index, use their actual UID, GID, timestamp,
3388 on writing the NLM command file language used in header files, see the
3424 writing the NLM command file language used in header files, see@ see the
/toolchain/binutils/binutils-2.25/binutils/
DNEWS481 * There is now support for writing ECOFF files, so ld and the other utilities
/toolchain/binutils/binutils-2.25/gold/
Dpowerpc.cc5029 bool writing = false; in savres_define() local
5041 writing = writing || refd; in savres_define()
5042 if (writing) in savres_define()

12345