diff options
Diffstat (limited to 'gas/doc/as.texi')
| -rw-r--r-- | gas/doc/as.texi | 54 |
1 files changed, 38 insertions, 16 deletions
diff --git a/gas/doc/as.texi b/gas/doc/as.texi index 33169a5..0b4109e 100644 --- a/gas/doc/as.texi +++ b/gas/doc/as.texi @@ -260,7 +260,8 @@ gcc(1), ld(1), and the Info entries for @file{binutils} and @file{ld}. [@b{--size-check=[error|warning]}] [@b{--statistics}] [@b{-v}] [@b{-version}] [@b{--version}] - [@b{-W}] [@b{--warn}] [@b{--fatal-warnings}] [@b{-w}] [@b{-x}] + [@b{-W}] [@b{--no-warn}] [@b{--warn}] [@b{--fatal-warnings}] + [@b{-w}] [@b{-x}] [@b{-Z}] [@b{@@@var{FILE}}] [@var{target-options}] [@b{--}|@var{files} @dots{}] @@ -983,12 +984,12 @@ Print the @command{as} version and exit. @itemx --no-warn Suppress warning messages. -@item --fatal-warnings -Treat warnings as errors. - @item --warn Don't suppress warning messages or treat them as errors. +@item --fatal-warnings +Treat warnings as errors. + @item -w Ignored. @@ -2863,7 +2864,7 @@ option @samp{-v} (which you can also spell as @samp{-version}) on the command line. @node W -@section Control Warnings: @option{-W}, @option{--warn}, @option{--no-warn}, @option{--fatal-warnings} +@section Control Warnings: @option{-W}, @option{--no-warn}, @option{--warn}, @option{--fatal-warnings} @command{@value{AS}} should never give a warning or error message when assembling compiler output. But programs written by people often @@ -2874,22 +2875,24 @@ made. All such warnings are directed to the standard error file. @kindex --no-warn @cindex suppressing warnings @cindex warnings, suppressing -If you use the @option{-W} and @option{--no-warn} options, no warnings are issued. +If you use the @option{-W} or @option{--no-warn} option, no warnings are issued. This only affects the warning messages: it does not change any particular of how @command{@value{AS}} assembles your file. Errors, which stop the assembly, are still reported. +@kindex --warn +@cindex outputing warnings +@cindex warnings, switching on +Warnings are switched on by default. They can be switched off with @option{-W} or +@option{--no-warn}. Specifying the @option{--warn} again later on the command line +will switch on warnings again, and cause them to be output as usual. + @kindex --fatal-warnings @cindex errors, caused by warnings @cindex warnings, causing error If you use the @option{--fatal-warnings} option, @command{@value{AS}} considers files that generate warnings to be in error. -@kindex --warn -@cindex warnings, switching on -You can switch these options off again by specifying @option{--warn}, which -causes warnings to be output as usual. - @node Z @section Generate Object File in Spite of Errors: @option{-Z} @cindex object file, after errors @@ -2987,11 +2990,11 @@ as exactly one space. @section Comments @cindex comments -There are two ways of rendering comments to @command{@value{AS}}. In both -cases the comment is equivalent to one space. +There are two ways of rendering comments to @command{@value{AS}}. Anything from @samp{/*} through the next @samp{*/} is a comment. -This means you may not nest these comments. +This means you may not nest these comments. Such a comment is equivalent to +one space, plus bumping the line counter accordingly. @smallexample /* @@ -4497,6 +4500,7 @@ Some machine configurations provide additional directives. * Asciz:: @code{.asciz "@var{string}"}@dots{} * Attach_to_group:: @code{.attach_to_group @var{name}} * Balign:: @code{.balign [@var{abs-expr}[, @var{abs-expr}]]} +* Base64:: @code{.base64 "@var{string}"[, @dots{}]} @ifset ELF * Bss:: @code{.bss @var{subsection}} @end ifset @@ -4784,7 +4788,7 @@ and use the result as a string. @item No passing arguments to macros based upon keyword assignment. In altmacro mode arguments cannot be passed to macros by keyword assignment. -See @xref{altmacro-keyword-arguments} for more details +See @xref{altmacro-keyword-arguments}. @end ftable @node Ascii @@ -4851,6 +4855,24 @@ filled in with the value 0x368d (the exact placement of the bytes depends upon the endianness of the processor). If it skips 1 or 3 bytes, the fill value is undefined. +@node Base64 +@section @code{.base64 "@var{string}"[, @dots{}]} +Allows binary data to be entered into a section encoded as a base64 string. +There is no maximum length to the strings, but they must be a multiple of four +bytes long. If necessary the ends of the strings can be padded with @code{=} +characters. Line breaks, control characters and escaped characters are not +allowed in the strings. The strings must be enclosed between double quote +characters. Multiple strings are allowed, but they must be separated by +commas. + +As an example of how to create a base64 encoded string, see the +@command{base64} program (with its @option{-w0} option to disable line breaks). + +Note: for targets where the size of a byte is larger than the size of an octet +the @code{.base64} directive will, if necessary, pad the end of the @emph{last} +string so that the total number of octets generated are a multiple the number +of octets in a byte. + @ifset ELF @node Bss @section @code{.bss @var{subsection}} @@ -7785,7 +7807,7 @@ section, using the endian model of the target. If an expression will not fit in two bytes, a warning message is displayed and the least significant two bytes of the expression's value are used. If an expression cannot be evaluated at assembly time then relocations will be generated in order to compute the -value at link time. +value at link time. This directive does not apply any alignment before or after inserting the values. As a result of this, if relocations are generated, they may be |