Lines Matching +refs:dwarf +refs:file
17 @c defaults, config file may override:
100 This file documents the GNU Assembler "@value{AS}".
168 This file is a user guide to the @sc{gnu} assembler @command{@value{AS}}
174 This version of the file describes @command{@value{AS}} configured to generate
221 gcc(1), ld(1), and the Info entries for @file{binutils} and @file{ld}.
229 @value{AS} [@b{-a}[@b{cdghlns}][=@var{file}]] [@b{--alternate}] [@b{-D}]
542 [@b{-merrors-to-file} @var{<filename>}|@b{-me} @var{<filename>}]
596 @include at-file.texi
626 @item =file
627 set the name of the listing file
631 listing without forms processing. The @samp{=file} option, if used, must be
642 ELF ABI. The resulting object file may not be compatible with older
643 linkers and object file utilities. Note if compression would make a
675 When assembling files in directory @file{@var{old}}, record debugging
676 information describing them as in @file{@var{new}} instead.
679 Define the symbol @var{sym} to be @var{value} before assembling the input file.
682 value. The value of the symbol can be overridden inside a source file via the
715 will have its dwarf line number information placed into a section called
783 Name the object-file output from @command{@value{AS}} @var{objfile}.
839 Generate an object file even after errors.
861 @c ended inside the included file
880 @c ended inside the included file
944 @c ended inside the included file
1001 @c ended inside the included file
1020 @c ended inside the included file
1039 @c ended inside the included file
1164 @c ended inside the included file
1304 @item -merrors-to-file @var{FILENAME}
1305 Redirect error output to a file, for broken systems which don't support such
1411 @code{.set mips16} at the start of the assembly file. @samp{-no-mips16}
1417 @code{.set micromips} at the start of the assembly file. @samp{-mno-micromips}
1419 at the start of the assembly file.
1424 equivalent to putting @code{.set smartmips} at the start of the assembly file.
1488 the start of the assembly file. @samp{-mno-insn32} turns off this
1490 start of the assembly file. By default @samp{-mno-insn32} is
1590 @c ended inside the included file
1606 @c ended inside the included file
1616 @c ended inside the included file
1634 @c ended inside the included file
1684 @c ended inside the included file
1703 @c ended inside the included file
1722 @c ended inside the included file
1741 @c ended inside the included file
1872 including object file formats, most assembler directives (often called
1895 program in one pass of the source file. This has a subtle impact on the
1901 @cindex object file format
1903 object file formats. For the most part, this does not affect how you
1905 are typically different in different file formats. @xref{Symbol
1929 options and file names. Options may appear in any order, and may be
1930 before, after, or between file names. The order of file names is
1933 @cindex standard input, as input file
1935 @file{--} (two hyphens) by itself names the standard input file
1945 Some options expect exactly one file name to follow them. The file
1951 @value{AS} -o my-object-file.o mumble.s
1952 @value{AS} -omy-object-file.o mumble.s
1974 (The standard input is also a file.)
1976 You give @command{@value{AS}} a command line that has zero or more input file
1977 names. The input files are read (from left file name to right). A
1979 is taken to be an input file name.
1981 If you give @command{@value{AS}} no file names it attempts to read one input file
1986 Use @samp{--} if you need to explicitly name the standard input file
1990 file.
1996 @cindex input file linenumbers
1998 There are two ways of locating a line in the input file (or files) and
2000 number in a physical file; the other refers to a line number in a
2001 ``logical'' file. @xref{Errors, ,Error and Warning Messages}.
2007 directives; they bear no relation to physical files. Logical file names help
2008 error messages reflect the original source file, when @command{@value{AS}} source
2011 @ref{File,,@code{.file}}.
2016 @cindex object file
2017 @cindex output file
2020 Every time you run @command{@value{AS}} it produces an output file, which is
2021 your assembly language program translated into numbers. This file
2022 is the object file. Its default name is
2033 object file names end with @file{.o}. The default name is used for historical
2040 The object file is meant for input to the linker @code{@value{LD}}. It contains
2042 the assembled program into a runnable file, and (optionally) symbolic
2045 @c link above to some info file(s) like the description of a.out.
2057 file (usually your terminal). This should not happen when a compiler
2072 @cindex file names and line numbers, in warnings/errors
2073 (where @b{NNN} is a line number). If both a logical file name
2074 (@pxref{File,,@code{.file}}) and a logical line number
2078 have been given then they will be used, otherwise the file name and line number
2079 in the current assembler source file will be used. The message text is
2082 Note the file name must be set via the logical version of the @code{.file}
2083 directive, not the DWARF2 version of the @code{.file} directive. For example:
2086 .file 2 "bar.c"
2088 .file "foo.c"
2108 The file name and line number are derived as for warning
2134 gcc -c -g -O -Wa,-alh,-L file.c
2168 * o:: -o to name the object file
2174 * Z:: -Z to make object file even after errors
2254 the input file(s) before assembling them. @xref{Preprocessing,
2314 in the object file. Usually if you do this you also tell the linker
2321 @samp{-a} (@pxref{a}). This feature combines the input source file(s) with a
2322 hex dump of the corresponding locations in the output object file, and displays
2323 them as a listing file. The format of this listing can be controlled by
2373 depend upon its object file format, and can not be supported using other object
2374 file formats. Supporting these would require enhancing each object file format
2381 Other object file formats do not support this. @command{@value{AS}} handles
2390 are not support by other object file formats.
2395 This is not supported by other object file formats. The start address may
2402 name to the output file. This is not supported by other object file formats.
2409 not supported by other object file formats. The address of a section may be
2496 @command{@value{AS}} can generate a dependency file for the file it creates. This
2497 file consists of a single rule suitable for @code{make} describing the
2498 dependencies of the main source file.
2500 The rule is written to the file named in its argument.
2517 @cindex naming object file
2518 @cindex object file name
2519 There is always one object file output when you run @command{@value{AS}}. By
2523 @file{a.out} (or @file{b.out}, for Intel 960 targets only).
2526 @file{a.out}.
2531 @file{b.out}.
2534 @file{a.out}.
2538 object file a different name.
2540 Whatever the object file is called, @command{@value{AS}} overwrites any
2541 existing file of the same name.
2551 @option{-R} tells @command{@value{AS}} to write the object file as if all
2555 your object file is zero bytes long because all its bytes are
2614 made. All such warnings are directed to the standard error file.
2622 how @command{@value{AS}} assembles your file. Errors, which stop the assembly,
2638 @cindex object file, after errors
2641 some reason you are interested in object file output even after
2644 writes an object file after a final warning message of the form @samp{@var{n}
2645 errors, @var{m} warnings, generating bad object file.}
2653 source file. @command{@value{AS}} syntax is similar to what many other
2693 It does not do macro processing, include file handling, or
2695 do include file processing with the @code{.include} directive
2697 to get other ``CPP'' style preprocessing by giving the input file a
2709 If the first line of an input file is @code{#NO_APP} or if you use the
2710 @samp{-f} option, whitespace and comments are not removed from the input file.
2711 Within an input file, you can ask for whitespace and comment removal in
2768 new logical file name. The rest of the line, if any, should be whitespace.
2775 # 42-6 "new_file_name" # New logical file name
2807 beginning of a file (since the source program must end with a newline, the end
2808 of a file is not a possible symbol delimiter). @xref{Symbols}.
2831 @cindex newline, required at file end
2833 It is an error to end any statement with end-of-file: the last
2834 character of any input file should be a newline.@refill
3266 emits an object file, the partial program is assumed to start at address 0.
3277 the task of adjusting mentions of object-file addresses so they refer to
3286 An object file written by @command{@value{AS}} has at least three sections, any
3318 Within the object file, the text section starts at address @code{0}, the
3329 object file details of the relocation needed. To perform relocation
3331 file is mentioned:
3334 Where in the object file is the beginning of this reference to
3427 bytes in the object file. The bss section was invented to eliminate
3441 @c FIXME: ref to some other doc on obj-file formats could go here.
3551 that you want to end up near to each other in the object file, even though they
3555 same subsection go into the object file together with other objects in the same
3586 Subsections appear in your object file in numeric order, lowest numbered
3588 The object file contains no representation of subsections; @code{@value{LD}} and
3677 @emph{Warning:} @command{@value{AS}} does not place symbols in the object file in
3820 are optionally emitted to the object file. The names are constructed using
3830 object file. If you also instruct @code{@value{LD}} to retain these symbols,
3858 by contrast, remain in scope for the entire file, or until they are redefined
3896 The detailed definitions are in @file{a.out.h}.
3942 0 then the symbol is not defined in this assembler source file, and
4350 * File:: @code{.file}
4363 * Incbin:: @code{.incbin "@var{file}"[,@var{skip}[,@var{count}]]}
4364 * Include:: @code{.include "@var{file}"}
4909 will be encoded in the output file according to @var{encoding}; see the
4924 common symbol in one object file may be merged with a defined or common symbol
4925 of the same name in another object file. If @code{@value{LD}} does not see a
4944 is not the same as the executable image file alignment controlled by @code{@value{LD}}'s
4945 @samp{--section-alignment} option; image file sections in PE are aligned to
5066 @code{.end} marks the end of the assembly file. @command{@value{AS}} does not
5067 process anything in the file past the @code{.end} directive.
5149 object file. This can be used to signal an error in conditionally compiled code.
5157 message, it defaults to @code{".error directive invoked in source file"}.
5187 @section @code{.file}
5188 @cindex @code{file} directive
5190 @ifclear no-file-dir
5191 There are two different versions of the @code{.file} directive. Targets
5193 @code{.file}. Other targets use the default version.
5197 @cindex logical file name
5198 @cindex file name, logical
5199 This version of the @code{.file} directive tells @command{@value{AS}} that we
5200 are about to start a new logical file. The syntax is:
5203 .file @var{string}
5206 @var{string} is the new file name. In general, the filename is
5208 to specify an empty file name, you must give the quotes--@code{""}. This
5215 When emitting DWARF2 line number information, @code{.file} assigns filenames
5216 to the @code{.debug_line} file name table. The syntax is:
5219 .file @var{fileno} @var{filename}
5277 is ignored unless the file is assembled with debugging enabled.
5294 from another file linked into the same program.
5308 Record a @sc{gnu} object attribute for this file. @xref{Object Attributes}.
5355 a.out object file format, @command{@value{AS}} simply accepts the directive for
5356 source-file compatibility with existing assemblers, but does not emit anything
5451 @section @code{.incbin "@var{file}"[,@var{skip}[,@var{count}]]}
5455 The @code{incbin} directive includes @var{file} verbatim at the current
5458 around @var{file}.
5461 @var{file}. The @var{count} argument indicates the maximum number of bytes to
5467 @section @code{.include "@var{file}"}
5473 points in your source program. The code from @var{file} is assembled as
5475 included file is reached, assembly of the original file continues. You
5478 around @var{file}.
5639 but ensure that the linker will only include it once in the final output file.
5644 This directive is only supported by a few object file formats; as of this
5645 writing, the only object file format which supports it is the Portable
5653 Not all types may be supported on all object file formats.
5980 of the file. @xref{M, MRI mode, MRI mode}.
6609 file is the last value stored into it.
6753 cannot be referenced elsewhere in the source file.
6782 you get a half-formed symbol in your object file. This is
6814 @cindex string, copying to object file
6815 @cindex string8, copying to object file
6816 @cindex string16, copying to object file
6817 @cindex string32, copying to object file
6818 @cindex string64, copying to object file
6825 Copy the characters in @var{str} to the object file. You may specify more than
6887 within a source file. This is only supported on ELF platforms, and is
6897 If the symbol @var{name} is defined within the file
6905 file, and so that the compiler can unambiguously know which version of a
6912 If the symbol @var{name} is not defined within the file being assembled, all
6922 the file being assembled. It is similar to @var{name2@@nodename}. The
6931 file being assembled, it is treated as @var{name2@@nodename}. When
6932 @var{name} is defined within the file being assembled, the symbol
6970 source file name and pagenumber) when generating assembly listings.
7169 assembly source file, renaming the alias to the symbol in it, declaring the
7171 resulting from the assembly of the new source file and the old source file that
7275 point arguments might be passed in floating point registers if the object file
7277 passed in integer registers if the object file supports processors with no
7284 time, tools like @command{gdb} can use it to process the linked file
7295 The file format is documented in @cite{ELF for the ARM Architecture}.
7321 the flag value is 0, the file is compatible with other toolchains. If it is 1,
7322 then the file is only compatible with the named toolchain. If it is greater
7323 than 1, the file can only be processed by other toolchains under some private
7331 The floating-point ABI used by this object file. The value will be:
7365 The floating-point ABI used by this object file. The value will be:
7379 The vector ABI used by this object file. The value will be:
7397 The vector ABI used by this object file. The value will be:
7420 The header for your architecture @file{include/elf}, to define the tag.
7422 The @file{bfd} support file for your architecture, to merge the attribute
7425 Test cases in @file{ld/testsuite} for merging and link warnings.
7427 @file{binutils/readelf.c} to display your attribute.
7920 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
7981 A complete input file that will reproduce the bug. If the bug is observed when
7986 file with an extension of @file{.s}, and also show you exactly how
8010 option. Always send diffs from the old file to the new file. If you even
8025 which changes to the input file will make the bug go away and which
8079 extensive changes in @file{messages.c}, @file{input-file.c}, @file{write.c}.
8083 up to handle multiple object file format back ends (including heavy rewrite,
8085 including heavy testing and verification of cross assemblers and file splits
8089 file rewrite, DECstation, rs6000, and hp300hpux host ports, updated ``know''
8106 (@file{tc-mips.c}, @file{tc-mips.h}), and contributed Rose format support
8111 tc-h8300), and IEEE 695 object file format (obj-ieee), was written by