| 1 | \input texinfo |
| 2 | @c Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, |
| 3 | @c 2001, 2002, 2003 |
| 4 | @c Free Software Foundation, Inc. |
| 5 | @setfilename internals.info |
| 6 | @node Top |
| 7 | @top Assembler Internals |
| 8 | @raisesections |
| 9 | @cindex internals |
| 10 | |
| 11 | This chapter describes the internals of the assembler. It is incomplete, but |
| 12 | it may help a bit. |
| 13 | |
| 14 | This chapter is not updated regularly, and it may be out of date. |
| 15 | |
| 16 | @menu |
| 17 | * GAS versions:: GAS versions |
| 18 | * Data types:: Data types |
| 19 | * GAS processing:: What GAS does when it runs |
| 20 | * Porting GAS:: Porting GAS |
| 21 | * Relaxation:: Relaxation |
| 22 | * Broken words:: Broken words |
| 23 | * Internal functions:: Internal functions |
| 24 | * Test suite:: Test suite |
| 25 | @end menu |
| 26 | |
| 27 | @node GAS versions |
| 28 | @section GAS versions |
| 29 | |
| 30 | GAS has acquired layers of code over time. The original GAS only supported the |
| 31 | a.out object file format, with three sections. Support for multiple sections |
| 32 | has been added in two different ways. |
| 33 | |
| 34 | The preferred approach is to use the version of GAS created when the symbol |
| 35 | @code{BFD_ASSEMBLER} is defined. The other versions of GAS are documented for |
| 36 | historical purposes, and to help anybody who has to debug code written for |
| 37 | them. |
| 38 | |
| 39 | The type @code{segT} is used to represent a section in code which must work |
| 40 | with all versions of GAS. |
| 41 | |
| 42 | @menu |
| 43 | * Original GAS:: Original GAS version |
| 44 | * MANY_SEGMENTS:: MANY_SEGMENTS gas version |
| 45 | * BFD_ASSEMBLER:: BFD_ASSEMBLER gas version |
| 46 | @end menu |
| 47 | |
| 48 | @node Original GAS |
| 49 | @subsection Original GAS |
| 50 | |
| 51 | The original GAS only supported the a.out object file format with three |
| 52 | sections: @samp{.text}, @samp{.data}, and @samp{.bss}. This is the version of |
| 53 | GAS that is compiled if neither @code{BFD_ASSEMBLER} nor @code{MANY_SEGMENTS} |
| 54 | is defined. This version of GAS is still used for the m68k-aout target, and |
| 55 | perhaps others. |
| 56 | |
| 57 | This version of GAS should not be used for any new development. |
| 58 | |
| 59 | There is still code that is specific to this version of GAS, notably in |
| 60 | @file{write.c}. There is no way for this code to loop through all the |
| 61 | sections; it simply looks at global variables like @code{text_frag_root} and |
| 62 | @code{data_frag_root}. |
| 63 | |
| 64 | The type @code{segT} is an enum. |
| 65 | |
| 66 | @node MANY_SEGMENTS |
| 67 | @subsection MANY_SEGMENTS gas version |
| 68 | @cindex MANY_SEGMENTS |
| 69 | |
| 70 | The @code{MANY_SEGMENTS} version of gas is only used for COFF. It uses the BFD |
| 71 | library, but it writes out all the data itself using @code{bfd_write}. This |
| 72 | version of gas supports up to 40 normal sections. The section names are stored |
| 73 | in the @code{seg_name} array. Other information is stored in the |
| 74 | @code{segment_info} array. |
| 75 | |
| 76 | The type @code{segT} is an enum. Code that wants to examine all the sections |
| 77 | can use a @code{segT} variable as loop index from @code{SEG_E0} up to but not |
| 78 | including @code{SEG_UNKNOWN}. |
| 79 | |
| 80 | Most of the code specific to this version of GAS is in the file |
| 81 | @file{config/obj-coff.c}, in the portion of that file that is compiled when |
| 82 | @code{BFD_ASSEMBLER} is not defined. |
| 83 | |
| 84 | This version of GAS is still used for several COFF targets. |
| 85 | |
| 86 | @node BFD_ASSEMBLER |
| 87 | @subsection BFD_ASSEMBLER gas version |
| 88 | @cindex BFD_ASSEMBLER |
| 89 | |
| 90 | The preferred version of GAS is the @code{BFD_ASSEMBLER} version. In this |
| 91 | version of GAS, the output file is a normal BFD, and the BFD routines are used |
| 92 | to generate the output. |
| 93 | |
| 94 | @code{BFD_ASSEMBLER} will automatically be used for certain targets, including |
| 95 | those that use the ELF, ECOFF, and SOM object file formats, and also all Alpha, |
| 96 | MIPS, PowerPC, and SPARC targets. You can force the use of |
| 97 | @code{BFD_ASSEMBLER} for other targets with the configure option |
| 98 | @samp{--enable-bfd-assembler}; however, it has not been tested for many |
| 99 | targets, and can not be assumed to work. |
| 100 | |
| 101 | @node Data types |
| 102 | @section Data types |
| 103 | @cindex internals, data types |
| 104 | |
| 105 | This section describes some fundamental GAS data types. |
| 106 | |
| 107 | @menu |
| 108 | * Symbols:: The symbolS structure |
| 109 | * Expressions:: The expressionS structure |
| 110 | * Fixups:: The fixS structure |
| 111 | * Frags:: The fragS structure |
| 112 | @end menu |
| 113 | |
| 114 | @node Symbols |
| 115 | @subsection Symbols |
| 116 | @cindex internals, symbols |
| 117 | @cindex symbols, internal |
| 118 | @cindex symbolS structure |
| 119 | |
| 120 | The definition for the symbol structure, @code{symbolS}, is located in |
| 121 | @file{struc-symbol.h}. |
| 122 | |
| 123 | In general, the fields of this structure may not be referred to directly. |
| 124 | Instead, you must use one of the accessor functions defined in @file{symbol.h}. |
| 125 | These accessor functions should work for any GAS version. |
| 126 | |
| 127 | Symbol structures contain the following fields: |
| 128 | |
| 129 | @table @code |
| 130 | @item sy_value |
| 131 | This is an @code{expressionS} that describes the value of the symbol. It might |
| 132 | refer to one or more other symbols; if so, its true value may not be known |
| 133 | until @code{resolve_symbol_value} is called with @var{finalize_syms} non-zero |
| 134 | in @code{write_object_file}. |
| 135 | |
| 136 | The expression is often simply a constant. Before @code{resolve_symbol_value} |
| 137 | is called with @var{finalize_syms} set, the value is the offset from the frag |
| 138 | (@pxref{Frags}). Afterward, the frag address has been added in. |
| 139 | |
| 140 | @item sy_resolved |
| 141 | This field is non-zero if the symbol's value has been completely resolved. It |
| 142 | is used during the final pass over the symbol table. |
| 143 | |
| 144 | @item sy_resolving |
| 145 | This field is used to detect loops while resolving the symbol's value. |
| 146 | |
| 147 | @item sy_used_in_reloc |
| 148 | This field is non-zero if the symbol is used by a relocation entry. If a local |
| 149 | symbol is used in a relocation entry, it must be possible to redirect those |
| 150 | relocations to other symbols, or this symbol cannot be removed from the final |
| 151 | symbol list. |
| 152 | |
| 153 | @item sy_next |
| 154 | @itemx sy_previous |
| 155 | These pointers to other @code{symbolS} structures describe a singly or doubly |
| 156 | linked list. (If @code{SYMBOLS_NEED_BACKPOINTERS} is not defined, the |
| 157 | @code{sy_previous} field will be omitted; @code{SYMBOLS_NEED_BACKPOINTERS} is |
| 158 | always defined if @code{BFD_ASSEMBLER}.) These fields should be accessed with |
| 159 | the @code{symbol_next} and @code{symbol_previous} macros. |
| 160 | |
| 161 | @item sy_frag |
| 162 | This points to the frag (@pxref{Frags}) that this symbol is attached to. |
| 163 | |
| 164 | @item sy_used |
| 165 | Whether the symbol is used as an operand or in an expression. Note: Not all of |
| 166 | the backends keep this information accurate; backends which use this bit are |
| 167 | responsible for setting it when a symbol is used in backend routines. |
| 168 | |
| 169 | @item sy_mri_common |
| 170 | Whether the symbol is an MRI common symbol created by the @code{COMMON} |
| 171 | pseudo-op when assembling in MRI mode. |
| 172 | |
| 173 | @item bsym |
| 174 | If @code{BFD_ASSEMBLER} is defined, this points to the BFD @code{asymbol} that |
| 175 | will be used in writing the object file. |
| 176 | |
| 177 | @item sy_name_offset |
| 178 | (Only used if @code{BFD_ASSEMBLER} is not defined.) This is the position of |
| 179 | the symbol's name in the string table of the object file. On some formats, |
| 180 | this will start at position 4, with position 0 reserved for unnamed symbols. |
| 181 | This field is not used until @code{write_object_file} is called. |
| 182 | |
| 183 | @item sy_symbol |
| 184 | (Only used if @code{BFD_ASSEMBLER} is not defined.) This is the |
| 185 | format-specific symbol structure, as it would be written into the object file. |
| 186 | |
| 187 | @item sy_number |
| 188 | (Only used if @code{BFD_ASSEMBLER} is not defined.) This is a 24-bit symbol |
| 189 | number, for use in constructing relocation table entries. |
| 190 | |
| 191 | @item sy_obj |
| 192 | This format-specific data is of type @code{OBJ_SYMFIELD_TYPE}. If no macro by |
| 193 | that name is defined in @file{obj-format.h}, this field is not defined. |
| 194 | |
| 195 | @item sy_tc |
| 196 | This processor-specific data is of type @code{TC_SYMFIELD_TYPE}. If no macro |
| 197 | by that name is defined in @file{targ-cpu.h}, this field is not defined. |
| 198 | |
| 199 | @end table |
| 200 | |
| 201 | Here is a description of the accessor functions. These should be used rather |
| 202 | than referring to the fields of @code{symbolS} directly. |
| 203 | |
| 204 | @table @code |
| 205 | @item S_SET_VALUE |
| 206 | @cindex S_SET_VALUE |
| 207 | Set the symbol's value. |
| 208 | |
| 209 | @item S_GET_VALUE |
| 210 | @cindex S_GET_VALUE |
| 211 | Get the symbol's value. This will cause @code{resolve_symbol_value} to be |
| 212 | called if necessary. |
| 213 | |
| 214 | @item S_SET_SEGMENT |
| 215 | @cindex S_SET_SEGMENT |
| 216 | Set the section of the symbol. |
| 217 | |
| 218 | @item S_GET_SEGMENT |
| 219 | @cindex S_GET_SEGMENT |
| 220 | Get the symbol's section. |
| 221 | |
| 222 | @item S_GET_NAME |
| 223 | @cindex S_GET_NAME |
| 224 | Get the name of the symbol. |
| 225 | |
| 226 | @item S_SET_NAME |
| 227 | @cindex S_SET_NAME |
| 228 | Set the name of the symbol. |
| 229 | |
| 230 | @item S_IS_EXTERNAL |
| 231 | @cindex S_IS_EXTERNAL |
| 232 | Return non-zero if the symbol is externally visible. |
| 233 | |
| 234 | @item S_IS_EXTERN |
| 235 | @cindex S_IS_EXTERN |
| 236 | A synonym for @code{S_IS_EXTERNAL}. Don't use it. |
| 237 | |
| 238 | @item S_IS_WEAK |
| 239 | @cindex S_IS_WEAK |
| 240 | Return non-zero if the symbol is weak. |
| 241 | |
| 242 | @item S_IS_COMMON |
| 243 | @cindex S_IS_COMMON |
| 244 | Return non-zero if this is a common symbol. Common symbols are sometimes |
| 245 | represented as undefined symbols with a value, in which case this function will |
| 246 | not be reliable. |
| 247 | |
| 248 | @item S_IS_DEFINED |
| 249 | @cindex S_IS_DEFINED |
| 250 | Return non-zero if this symbol is defined. This function is not reliable when |
| 251 | called on a common symbol. |
| 252 | |
| 253 | @item S_IS_DEBUG |
| 254 | @cindex S_IS_DEBUG |
| 255 | Return non-zero if this is a debugging symbol. |
| 256 | |
| 257 | @item S_IS_LOCAL |
| 258 | @cindex S_IS_LOCAL |
| 259 | Return non-zero if this is a local assembler symbol which should not be |
| 260 | included in the final symbol table. Note that this is not the opposite of |
| 261 | @code{S_IS_EXTERNAL}. The @samp{-L} assembler option affects the return value |
| 262 | of this function. |
| 263 | |
| 264 | @item S_SET_EXTERNAL |
| 265 | @cindex S_SET_EXTERNAL |
| 266 | Mark the symbol as externally visible. |
| 267 | |
| 268 | @item S_CLEAR_EXTERNAL |
| 269 | @cindex S_CLEAR_EXTERNAL |
| 270 | Mark the symbol as not externally visible. |
| 271 | |
| 272 | @item S_SET_WEAK |
| 273 | @cindex S_SET_WEAK |
| 274 | Mark the symbol as weak. |
| 275 | |
| 276 | @item S_GET_TYPE |
| 277 | @item S_GET_DESC |
| 278 | @item S_GET_OTHER |
| 279 | @cindex S_GET_TYPE |
| 280 | @cindex S_GET_DESC |
| 281 | @cindex S_GET_OTHER |
| 282 | Get the @code{type}, @code{desc}, and @code{other} fields of the symbol. These |
| 283 | are only defined for object file formats for which they make sense (primarily |
| 284 | a.out). |
| 285 | |
| 286 | @item S_SET_TYPE |
| 287 | @item S_SET_DESC |
| 288 | @item S_SET_OTHER |
| 289 | @cindex S_SET_TYPE |
| 290 | @cindex S_SET_DESC |
| 291 | @cindex S_SET_OTHER |
| 292 | Set the @code{type}, @code{desc}, and @code{other} fields of the symbol. These |
| 293 | are only defined for object file formats for which they make sense (primarily |
| 294 | a.out). |
| 295 | |
| 296 | @item S_GET_SIZE |
| 297 | @cindex S_GET_SIZE |
| 298 | Get the size of a symbol. This is only defined for object file formats for |
| 299 | which it makes sense (primarily ELF). |
| 300 | |
| 301 | @item S_SET_SIZE |
| 302 | @cindex S_SET_SIZE |
| 303 | Set the size of a symbol. This is only defined for object file formats for |
| 304 | which it makes sense (primarily ELF). |
| 305 | |
| 306 | @item symbol_get_value_expression |
| 307 | @cindex symbol_get_value_expression |
| 308 | Get a pointer to an @code{expressionS} structure which represents the value of |
| 309 | the symbol as an expression. |
| 310 | |
| 311 | @item symbol_set_value_expression |
| 312 | @cindex symbol_set_value_expression |
| 313 | Set the value of a symbol to an expression. |
| 314 | |
| 315 | @item symbol_set_frag |
| 316 | @cindex symbol_set_frag |
| 317 | Set the frag where a symbol is defined. |
| 318 | |
| 319 | @item symbol_get_frag |
| 320 | @cindex symbol_get_frag |
| 321 | Get the frag where a symbol is defined. |
| 322 | |
| 323 | @item symbol_mark_used |
| 324 | @cindex symbol_mark_used |
| 325 | Mark a symbol as having been used in an expression. |
| 326 | |
| 327 | @item symbol_clear_used |
| 328 | @cindex symbol_clear_used |
| 329 | Clear the mark indicating that a symbol was used in an expression. |
| 330 | |
| 331 | @item symbol_used_p |
| 332 | @cindex symbol_used_p |
| 333 | Return whether a symbol was used in an expression. |
| 334 | |
| 335 | @item symbol_mark_used_in_reloc |
| 336 | @cindex symbol_mark_used_in_reloc |
| 337 | Mark a symbol as having been used by a relocation. |
| 338 | |
| 339 | @item symbol_clear_used_in_reloc |
| 340 | @cindex symbol_clear_used_in_reloc |
| 341 | Clear the mark indicating that a symbol was used in a relocation. |
| 342 | |
| 343 | @item symbol_used_in_reloc_p |
| 344 | @cindex symbol_used_in_reloc_p |
| 345 | Return whether a symbol was used in a relocation. |
| 346 | |
| 347 | @item symbol_mark_mri_common |
| 348 | @cindex symbol_mark_mri_common |
| 349 | Mark a symbol as an MRI common symbol. |
| 350 | |
| 351 | @item symbol_clear_mri_common |
| 352 | @cindex symbol_clear_mri_common |
| 353 | Clear the mark indicating that a symbol is an MRI common symbol. |
| 354 | |
| 355 | @item symbol_mri_common_p |
| 356 | @cindex symbol_mri_common_p |
| 357 | Return whether a symbol is an MRI common symbol. |
| 358 | |
| 359 | @item symbol_mark_written |
| 360 | @cindex symbol_mark_written |
| 361 | Mark a symbol as having been written. |
| 362 | |
| 363 | @item symbol_clear_written |
| 364 | @cindex symbol_clear_written |
| 365 | Clear the mark indicating that a symbol was written. |
| 366 | |
| 367 | @item symbol_written_p |
| 368 | @cindex symbol_written_p |
| 369 | Return whether a symbol was written. |
| 370 | |
| 371 | @item symbol_mark_resolved |
| 372 | @cindex symbol_mark_resolved |
| 373 | Mark a symbol as having been resolved. |
| 374 | |
| 375 | @item symbol_resolved_p |
| 376 | @cindex symbol_resolved_p |
| 377 | Return whether a symbol has been resolved. |
| 378 | |
| 379 | @item symbol_section_p |
| 380 | @cindex symbol_section_p |
| 381 | Return whether a symbol is a section symbol. |
| 382 | |
| 383 | @item symbol_equated_p |
| 384 | @cindex symbol_equated_p |
| 385 | Return whether a symbol is equated to another symbol. |
| 386 | |
| 387 | @item symbol_constant_p |
| 388 | @cindex symbol_constant_p |
| 389 | Return whether a symbol has a constant value, including being an offset within |
| 390 | some frag. |
| 391 | |
| 392 | @item symbol_get_bfdsym |
| 393 | @cindex symbol_get_bfdsym |
| 394 | Return the BFD symbol associated with a symbol. |
| 395 | |
| 396 | @item symbol_set_bfdsym |
| 397 | @cindex symbol_set_bfdsym |
| 398 | Set the BFD symbol associated with a symbol. |
| 399 | |
| 400 | @item symbol_get_obj |
| 401 | @cindex symbol_get_obj |
| 402 | Return a pointer to the @code{OBJ_SYMFIELD_TYPE} field of a symbol. |
| 403 | |
| 404 | @item symbol_set_obj |
| 405 | @cindex symbol_set_obj |
| 406 | Set the @code{OBJ_SYMFIELD_TYPE} field of a symbol. |
| 407 | |
| 408 | @item symbol_get_tc |
| 409 | @cindex symbol_get_tc |
| 410 | Return a pointer to the @code{TC_SYMFIELD_TYPE} field of a symbol. |
| 411 | |
| 412 | @item symbol_set_tc |
| 413 | @cindex symbol_set_tc |
| 414 | Set the @code{TC_SYMFIELD_TYPE} field of a symbol. |
| 415 | |
| 416 | @end table |
| 417 | |
| 418 | When @code{BFD_ASSEMBLER} is defined, GAS attempts to store local |
| 419 | symbols--symbols which will not be written to the output file--using a |
| 420 | different structure, @code{struct local_symbol}. This structure can only |
| 421 | represent symbols whose value is an offset within a frag. |
| 422 | |
| 423 | Code outside of the symbol handler will always deal with @code{symbolS} |
| 424 | structures and use the accessor functions. The accessor functions correctly |
| 425 | deal with local symbols. @code{struct local_symbol} is much smaller than |
| 426 | @code{symbolS} (which also automatically creates a bfd @code{asymbol} |
| 427 | structure), so this saves space when assembling large files. |
| 428 | |
| 429 | The first field of @code{symbolS} is @code{bsym}, the pointer to the BFD |
| 430 | symbol. The first field of @code{struct local_symbol} is a pointer which is |
| 431 | always set to NULL. This is how the symbol accessor functions can distinguish |
| 432 | local symbols from ordinary symbols. The symbol accessor functions |
| 433 | automatically convert a local symbol into an ordinary symbol when necessary. |
| 434 | |
| 435 | @node Expressions |
| 436 | @subsection Expressions |
| 437 | @cindex internals, expressions |
| 438 | @cindex expressions, internal |
| 439 | @cindex expressionS structure |
| 440 | |
| 441 | Expressions are stored in an @code{expressionS} structure. The structure is |
| 442 | defined in @file{expr.h}. |
| 443 | |
| 444 | @cindex expression |
| 445 | The macro @code{expression} will create an @code{expressionS} structure based |
| 446 | on the text found at the global variable @code{input_line_pointer}. |
| 447 | |
| 448 | @cindex make_expr_symbol |
| 449 | @cindex expr_symbol_where |
| 450 | A single @code{expressionS} structure can represent a single operation. |
| 451 | Complex expressions are formed by creating @dfn{expression symbols} and |
| 452 | combining them in @code{expressionS} structures. An expression symbol is |
| 453 | created by calling @code{make_expr_symbol}. An expression symbol should |
| 454 | naturally never appear in a symbol table, and the implementation of |
| 455 | @code{S_IS_LOCAL} (@pxref{Symbols}) reflects that. The function |
| 456 | @code{expr_symbol_where} returns non-zero if a symbol is an expression symbol, |
| 457 | and also returns the file and line for the expression which caused it to be |
| 458 | created. |
| 459 | |
| 460 | The @code{expressionS} structure has two symbol fields, a number field, an |
| 461 | operator field, and a field indicating whether the number is unsigned. |
| 462 | |
| 463 | The operator field is of type @code{operatorT}, and describes how to interpret |
| 464 | the other fields; see the definition in @file{expr.h} for the possibilities. |
| 465 | |
| 466 | An @code{operatorT} value of @code{O_big} indicates either a floating point |
| 467 | number, stored in the global variable @code{generic_floating_point_number}, or |
| 468 | an integer too large to store in an @code{offsetT} type, stored in the global |
| 469 | array @code{generic_bignum}. This rather inflexible approach makes it |
| 470 | impossible to use floating point numbers or large expressions in complex |
| 471 | expressions. |
| 472 | |
| 473 | @node Fixups |
| 474 | @subsection Fixups |
| 475 | @cindex internals, fixups |
| 476 | @cindex fixups |
| 477 | @cindex fixS structure |
| 478 | |
| 479 | A @dfn{fixup} is basically anything which can not be resolved in the first |
| 480 | pass. Sometimes a fixup can be resolved by the end of the assembly; if not, |
| 481 | the fixup becomes a relocation entry in the object file. |
| 482 | |
| 483 | @cindex fix_new |
| 484 | @cindex fix_new_exp |
| 485 | A fixup is created by a call to @code{fix_new} or @code{fix_new_exp}. Both |
| 486 | take a frag (@pxref{Frags}), a position within the frag, a size, an indication |
| 487 | of whether the fixup is PC relative, and a type. In a @code{BFD_ASSEMBLER} |
| 488 | GAS, the type is nominally a @code{bfd_reloc_code_real_type}, but several |
| 489 | targets use other type codes to represent fixups that can not be described as |
| 490 | relocations. |
| 491 | |
| 492 | The @code{fixS} structure has a number of fields, several of which are obsolete |
| 493 | or are only used by a particular target. The important fields are: |
| 494 | |
| 495 | @table @code |
| 496 | @item fx_frag |
| 497 | The frag (@pxref{Frags}) this fixup is in. |
| 498 | |
| 499 | @item fx_where |
| 500 | The location within the frag where the fixup occurs. |
| 501 | |
| 502 | @item fx_addsy |
| 503 | The symbol this fixup is against. Typically, the value of this symbol is added |
| 504 | into the object contents. This may be NULL. |
| 505 | |
| 506 | @item fx_subsy |
| 507 | The value of this symbol is subtracted from the object contents. This is |
| 508 | normally NULL. |
| 509 | |
| 510 | @item fx_offset |
| 511 | A number which is added into the fixup. |
| 512 | |
| 513 | @item fx_addnumber |
| 514 | Some CPU backends use this field to convey information between |
| 515 | @code{md_apply_fix3} and @code{tc_gen_reloc}. The machine independent code does |
| 516 | not use it. |
| 517 | |
| 518 | @item fx_next |
| 519 | The next fixup in the section. |
| 520 | |
| 521 | @item fx_r_type |
| 522 | The type of the fixup. This field is only defined if @code{BFD_ASSEMBLER}, or |
| 523 | if the target defines @code{NEED_FX_R_TYPE}. |
| 524 | |
| 525 | @item fx_size |
| 526 | The size of the fixup. This is mostly used for error checking. |
| 527 | |
| 528 | @item fx_pcrel |
| 529 | Whether the fixup is PC relative. |
| 530 | |
| 531 | @item fx_done |
| 532 | Non-zero if the fixup has been applied, and no relocation entry needs to be |
| 533 | generated. |
| 534 | |
| 535 | @item fx_file |
| 536 | @itemx fx_line |
| 537 | The file and line where the fixup was created. |
| 538 | |
| 539 | @item tc_fix_data |
| 540 | This has the type @code{TC_FIX_TYPE}, and is only defined if the target defines |
| 541 | that macro. |
| 542 | @end table |
| 543 | |
| 544 | @node Frags |
| 545 | @subsection Frags |
| 546 | @cindex internals, frags |
| 547 | @cindex frags |
| 548 | @cindex fragS structure. |
| 549 | |
| 550 | The @code{fragS} structure is defined in @file{as.h}. Each frag represents a |
| 551 | portion of the final object file. As GAS reads the source file, it creates |
| 552 | frags to hold the data that it reads. At the end of the assembly the frags and |
| 553 | fixups are processed to produce the final contents. |
| 554 | |
| 555 | @table @code |
| 556 | @item fr_address |
| 557 | The address of the frag. This is not set until the assembler rescans the list |
| 558 | of all frags after the entire input file is parsed. The function |
| 559 | @code{relax_segment} fills in this field. |
| 560 | |
| 561 | @item fr_next |
| 562 | Pointer to the next frag in this (sub)section. |
| 563 | |
| 564 | @item fr_fix |
| 565 | Fixed number of characters we know we're going to emit to the output file. May |
| 566 | be zero. |
| 567 | |
| 568 | @item fr_var |
| 569 | Variable number of characters we may output, after the initial @code{fr_fix} |
| 570 | characters. May be zero. |
| 571 | |
| 572 | @item fr_offset |
| 573 | The interpretation of this field is controlled by @code{fr_type}. Generally, |
| 574 | if @code{fr_var} is non-zero, this is a repeat count: the @code{fr_var} |
| 575 | characters are output @code{fr_offset} times. |
| 576 | |
| 577 | @item line |
| 578 | Holds line number info when an assembler listing was requested. |
| 579 | |
| 580 | @item fr_type |
| 581 | Relaxation state. This field indicates the interpretation of @code{fr_offset}, |
| 582 | @code{fr_symbol} and the variable-length tail of the frag, as well as the |
| 583 | treatment it gets in various phases of processing. It does not affect the |
| 584 | initial @code{fr_fix} characters; they are always supposed to be output |
| 585 | verbatim (fixups aside). See below for specific values this field can have. |
| 586 | |
| 587 | @item fr_subtype |
| 588 | Relaxation substate. If the macro @code{md_relax_frag} isn't defined, this is |
| 589 | assumed to be an index into @code{TC_GENERIC_RELAX_TABLE} for the generic |
| 590 | relaxation code to process (@pxref{Relaxation}). If @code{md_relax_frag} is |
| 591 | defined, this field is available for any use by the CPU-specific code. |
| 592 | |
| 593 | @item fr_symbol |
| 594 | This normally indicates the symbol to use when relaxing the frag according to |
| 595 | @code{fr_type}. |
| 596 | |
| 597 | @item fr_opcode |
| 598 | Points to the lowest-addressed byte of the opcode, for use in relaxation. |
| 599 | |
| 600 | @item tc_frag_data |
| 601 | Target specific fragment data of type TC_FRAG_TYPE. |
| 602 | Only present if @code{TC_FRAG_TYPE} is defined. |
| 603 | |
| 604 | @item fr_file |
| 605 | @itemx fr_line |
| 606 | The file and line where this frag was last modified. |
| 607 | |
| 608 | @item fr_literal |
| 609 | Declared as a one-character array, this last field grows arbitrarily large to |
| 610 | hold the actual contents of the frag. |
| 611 | @end table |
| 612 | |
| 613 | These are the possible relaxation states, provided in the enumeration type |
| 614 | @code{relax_stateT}, and the interpretations they represent for the other |
| 615 | fields: |
| 616 | |
| 617 | @table @code |
| 618 | @item rs_align |
| 619 | @itemx rs_align_code |
| 620 | The start of the following frag should be aligned on some boundary. In this |
| 621 | frag, @code{fr_offset} is the logarithm (base 2) of the alignment in bytes. |
| 622 | (For example, if alignment on an 8-byte boundary were desired, @code{fr_offset} |
| 623 | would have a value of 3.) The variable characters indicate the fill pattern to |
| 624 | be used. The @code{fr_subtype} field holds the maximum number of bytes to skip |
| 625 | when doing this alignment. If more bytes are needed, the alignment is not |
| 626 | done. An @code{fr_subtype} value of 0 means no maximum, which is the normal |
| 627 | case. Target backends can use @code{rs_align_code} to handle certain types of |
| 628 | alignment differently. |
| 629 | |
| 630 | @item rs_broken_word |
| 631 | This indicates that ``broken word'' processing should be done (@pxref{Broken |
| 632 | words}). If broken word processing is not necessary on the target machine, |
| 633 | this enumerator value will not be defined. |
| 634 | |
| 635 | @item rs_cfa |
| 636 | This state is used to implement exception frame optimizations. The |
| 637 | @code{fr_symbol} is an expression symbol for the subtraction which may be |
| 638 | relaxed. The @code{fr_opcode} field holds the frag for the preceding command |
| 639 | byte. The @code{fr_offset} field holds the offset within that frag. The |
| 640 | @code{fr_subtype} field is used during relaxation to hold the current size of |
| 641 | the frag. |
| 642 | |
| 643 | @item rs_fill |
| 644 | The variable characters are to be repeated @code{fr_offset} times. If |
| 645 | @code{fr_offset} is 0, this frag has a length of @code{fr_fix}. Most frags |
| 646 | have this type. |
| 647 | |
| 648 | @item rs_leb128 |
| 649 | This state is used to implement the DWARF ``little endian base 128'' |
| 650 | variable length number format. The @code{fr_symbol} is always an expression |
| 651 | symbol, as constant expressions are emitted directly. The @code{fr_offset} |
| 652 | field is used during relaxation to hold the previous size of the number so |
| 653 | that we can determine if the fragment changed size. |
| 654 | |
| 655 | @item rs_machine_dependent |
| 656 | Displacement relaxation is to be done on this frag. The target is indicated by |
| 657 | @code{fr_symbol} and @code{fr_offset}, and @code{fr_subtype} indicates the |
| 658 | particular machine-specific addressing mode desired. @xref{Relaxation}. |
| 659 | |
| 660 | @item rs_org |
| 661 | The start of the following frag should be pushed back to some specific offset |
| 662 | within the section. (Some assemblers use the value as an absolute address; GAS |
| 663 | does not handle final absolute addresses, but rather requires that the linker |
| 664 | set them.) The offset is given by @code{fr_symbol} and @code{fr_offset}; one |
| 665 | character from the variable-length tail is used as the fill character. |
| 666 | @end table |
| 667 | |
| 668 | @cindex frchainS structure |
| 669 | A chain of frags is built up for each subsection. The data structure |
| 670 | describing a chain is called a @code{frchainS}, and contains the following |
| 671 | fields: |
| 672 | |
| 673 | @table @code |
| 674 | @item frch_root |
| 675 | Points to the first frag in the chain. May be NULL if there are no frags in |
| 676 | this chain. |
| 677 | @item frch_last |
| 678 | Points to the last frag in the chain, or NULL if there are none. |
| 679 | @item frch_next |
| 680 | Next in the list of @code{frchainS} structures. |
| 681 | @item frch_seg |
| 682 | Indicates the section this frag chain belongs to. |
| 683 | @item frch_subseg |
| 684 | Subsection (subsegment) number of this frag chain. |
| 685 | @item fix_root, fix_tail |
| 686 | (Defined only if @code{BFD_ASSEMBLER} is defined). Point to first and last |
| 687 | @code{fixS} structures associated with this subsection. |
| 688 | @item frch_obstack |
| 689 | Not currently used. Intended to be used for frag allocation for this |
| 690 | subsection. This should reduce frag generation caused by switching sections. |
| 691 | @item frch_frag_now |
| 692 | The current frag for this subsegment. |
| 693 | @end table |
| 694 | |
| 695 | A @code{frchainS} corresponds to a subsection; each section has a list of |
| 696 | @code{frchainS} records associated with it. In most cases, only one subsection |
| 697 | of each section is used, so the list will only be one element long, but any |
| 698 | processing of frag chains should be prepared to deal with multiple chains per |
| 699 | section. |
| 700 | |
| 701 | After the input files have been completely processed, and no more frags are to |
| 702 | be generated, the frag chains are joined into one per section for further |
| 703 | processing. After this point, it is safe to operate on one chain per section. |
| 704 | |
| 705 | The assembler always has a current frag, named @code{frag_now}. More space is |
| 706 | allocated for the current frag using the @code{frag_more} function; this |
| 707 | returns a pointer to the amount of requested space. Relaxing is done using |
| 708 | variant frags allocated by @code{frag_var} or @code{frag_variant} |
| 709 | (@pxref{Relaxation}). |
| 710 | |
| 711 | @node GAS processing |
| 712 | @section What GAS does when it runs |
| 713 | @cindex internals, overview |
| 714 | |
| 715 | This is a quick look at what an assembler run looks like. |
| 716 | |
| 717 | @itemize @bullet |
| 718 | @item |
| 719 | The assembler initializes itself by calling various init routines. |
| 720 | |
| 721 | @item |
| 722 | For each source file, the @code{read_a_source_file} function reads in the file |
| 723 | and parses it. The global variable @code{input_line_pointer} points to the |
| 724 | current text; it is guaranteed to be correct up to the end of the line, but not |
| 725 | farther. |
| 726 | |
| 727 | @item |
| 728 | For each line, the assembler passes labels to the @code{colon} function, and |
| 729 | isolates the first word. If it looks like a pseudo-op, the word is looked up |
| 730 | in the pseudo-op hash table @code{po_hash} and dispatched to a pseudo-op |
| 731 | routine. Otherwise, the target dependent @code{md_assemble} routine is called |
| 732 | to parse the instruction. |
| 733 | |
| 734 | @item |
| 735 | When pseudo-ops or instructions output data, they add it to a frag, calling |
| 736 | @code{frag_more} to get space to store it in. |
| 737 | |
| 738 | @item |
| 739 | Pseudo-ops and instructions can also output fixups created by @code{fix_new} or |
| 740 | @code{fix_new_exp}. |
| 741 | |
| 742 | @item |
| 743 | For certain targets, instructions can create variant frags which are used to |
| 744 | store relaxation information (@pxref{Relaxation}). |
| 745 | |
| 746 | @item |
| 747 | When the input file is finished, the @code{write_object_file} routine is |
| 748 | called. It assigns addresses to all the frags (@code{relax_segment}), resolves |
| 749 | all the fixups (@code{fixup_segment}), resolves all the symbol values (using |
| 750 | @code{resolve_symbol_value}), and finally writes out the file (in the |
| 751 | @code{BFD_ASSEMBLER} case, this is done by simply calling @code{bfd_close}). |
| 752 | @end itemize |
| 753 | |
| 754 | @node Porting GAS |
| 755 | @section Porting GAS |
| 756 | @cindex porting |
| 757 | |
| 758 | Each GAS target specifies two main things: the CPU file and the object format |
| 759 | file. Two main switches in the @file{configure.in} file handle this. The |
| 760 | first switches on CPU type to set the shell variable @code{cpu_type}. The |
| 761 | second switches on the entire target to set the shell variable @code{fmt}. |
| 762 | |
| 763 | The configure script uses the value of @code{cpu_type} to select two files in |
| 764 | the @file{config} directory: @file{tc-@var{CPU}.c} and @file{tc-@var{CPU}.h}. |
| 765 | The configuration process will create a file named @file{targ-cpu.h} in the |
| 766 | build directory which includes @file{tc-@var{CPU}.h}. |
| 767 | |
| 768 | The configure script also uses the value of @code{fmt} to select two files: |
| 769 | @file{obj-@var{fmt}.c} and @file{obj-@var{fmt}.h}. The configuration process |
| 770 | will create a file named @file{obj-format.h} in the build directory which |
| 771 | includes @file{obj-@var{fmt}.h}. |
| 772 | |
| 773 | You can also set the emulation in the configure script by setting the @code{em} |
| 774 | variable. Normally the default value of @samp{generic} is fine. The |
| 775 | configuration process will create a file named @file{targ-env.h} in the build |
| 776 | directory which includes @file{te-@var{em}.h}. |
| 777 | |
| 778 | There is a special case for COFF. For historical reason, the GNU COFF |
| 779 | assembler doesn't follow the documented behavior on certain debug symbols for |
| 780 | the compatibility with other COFF assemblers. A port can define |
| 781 | @code{STRICTCOFF} in the configure script to make the GNU COFF assembler |
| 782 | to follow the documented behavior. |
| 783 | |
| 784 | Porting GAS to a new CPU requires writing the @file{tc-@var{CPU}} files. |
| 785 | Porting GAS to a new object file format requires writing the |
| 786 | @file{obj-@var{fmt}} files. There is sometimes some interaction between these |
| 787 | two files, but it is normally minimal. |
| 788 | |
| 789 | The best approach is, of course, to copy existing files. The documentation |
| 790 | below assumes that you are looking at existing files to see usage details. |
| 791 | |
| 792 | These interfaces have grown over time, and have never been carefully thought |
| 793 | out or designed. Nothing about the interfaces described here is cast in stone. |
| 794 | It is possible that they will change from one version of the assembler to the |
| 795 | next. Also, new macros are added all the time as they are needed. |
| 796 | |
| 797 | @menu |
| 798 | * CPU backend:: Writing a CPU backend |
| 799 | * Object format backend:: Writing an object format backend |
| 800 | * Emulations:: Writing emulation files |
| 801 | @end menu |
| 802 | |
| 803 | @node CPU backend |
| 804 | @subsection Writing a CPU backend |
| 805 | @cindex CPU backend |
| 806 | @cindex @file{tc-@var{CPU}} |
| 807 | |
| 808 | The CPU backend files are the heart of the assembler. They are the only parts |
| 809 | of the assembler which actually know anything about the instruction set of the |
| 810 | processor. |
| 811 | |
| 812 | You must define a reasonably small list of macros and functions in the CPU |
| 813 | backend files. You may define a large number of additional macros in the CPU |
| 814 | backend files, not all of which are documented here. You must, of course, |
| 815 | define macros in the @file{.h} file, which is included by every assembler |
| 816 | source file. You may define the functions as macros in the @file{.h} file, or |
| 817 | as functions in the @file{.c} file. |
| 818 | |
| 819 | @table @code |
| 820 | @item TC_@var{CPU} |
| 821 | @cindex TC_@var{CPU} |
| 822 | By convention, you should define this macro in the @file{.h} file. For |
| 823 | example, @file{tc-m68k.h} defines @code{TC_M68K}. You might have to use this |
| 824 | if it is necessary to add CPU specific code to the object format file. |
| 825 | |
| 826 | @item TARGET_FORMAT |
| 827 | This macro is the BFD target name to use when creating the output file. This |
| 828 | will normally depend upon the @code{OBJ_@var{FMT}} macro. |
| 829 | |
| 830 | @item TARGET_ARCH |
| 831 | This macro is the BFD architecture to pass to @code{bfd_set_arch_mach}. |
| 832 | |
| 833 | @item TARGET_MACH |
| 834 | This macro is the BFD machine number to pass to @code{bfd_set_arch_mach}. If |
| 835 | it is not defined, GAS will use 0. |
| 836 | |
| 837 | @item TARGET_BYTES_BIG_ENDIAN |
| 838 | You should define this macro to be non-zero if the target is big endian, and |
| 839 | zero if the target is little endian. |
| 840 | |
| 841 | @item md_shortopts |
| 842 | @itemx md_longopts |
| 843 | @itemx md_longopts_size |
| 844 | @itemx md_parse_option |
| 845 | @itemx md_show_usage |
| 846 | @itemx md_after_parse_args |
| 847 | @cindex md_shortopts |
| 848 | @cindex md_longopts |
| 849 | @cindex md_longopts_size |
| 850 | @cindex md_parse_option |
| 851 | @cindex md_show_usage |
| 852 | @cindex md_after_parse_args |
| 853 | GAS uses these variables and functions during option processing. |
| 854 | @code{md_shortopts} is a @code{const char *} which GAS adds to the machine |
| 855 | independent string passed to @code{getopt}. @code{md_longopts} is a |
| 856 | @code{struct option []} which GAS adds to the machine independent long options |
| 857 | passed to @code{getopt}; you may use @code{OPTION_MD_BASE}, defined in |
| 858 | @file{as.h}, as the start of a set of long option indices, if necessary. |
| 859 | @code{md_longopts_size} is a @code{size_t} holding the size @code{md_longopts}. |
| 860 | GAS will call @code{md_parse_option} whenever @code{getopt} returns an |
| 861 | unrecognized code, presumably indicating a special code value which appears in |
| 862 | @code{md_longopts}. GAS will call @code{md_show_usage} when a usage message is |
| 863 | printed; it should print a description of the machine specific options. |
| 864 | @code{md_after_pase_args}, if defined, is called after all options are |
| 865 | processed, to let the backend override settings done by the generic option |
| 866 | parsing. |
| 867 | |
| 868 | @item md_begin |
| 869 | @cindex md_begin |
| 870 | GAS will call this function at the start of the assembly, after the command |
| 871 | line arguments have been parsed and all the machine independent initializations |
| 872 | have been completed. |
| 873 | |
| 874 | @item md_cleanup |
| 875 | @cindex md_cleanup |
| 876 | If you define this macro, GAS will call it at the end of each input file. |
| 877 | |
| 878 | @item md_assemble |
| 879 | @cindex md_assemble |
| 880 | GAS will call this function for each input line which does not contain a |
| 881 | pseudo-op. The argument is a null terminated string. The function should |
| 882 | assemble the string as an instruction with operands. Normally |
| 883 | @code{md_assemble} will do this by calling @code{frag_more} and writing out |
| 884 | some bytes (@pxref{Frags}). @code{md_assemble} will call @code{fix_new} to |
| 885 | create fixups as needed (@pxref{Fixups}). Targets which need to do special |
| 886 | purpose relaxation will call @code{frag_var}. |
| 887 | |
| 888 | @item md_pseudo_table |
| 889 | @cindex md_pseudo_table |
| 890 | This is a const array of type @code{pseudo_typeS}. It is a mapping from |
| 891 | pseudo-op names to functions. You should use this table to implement |
| 892 | pseudo-ops which are specific to the CPU. |
| 893 | |
| 894 | @item tc_conditional_pseudoop |
| 895 | @cindex tc_conditional_pseudoop |
| 896 | If this macro is defined, GAS will call it with a @code{pseudo_typeS} argument. |
| 897 | It should return non-zero if the pseudo-op is a conditional which controls |
| 898 | whether code is assembled, such as @samp{.if}. GAS knows about the normal |
| 899 | conditional pseudo-ops, and you should normally not have to define this macro. |
| 900 | |
| 901 | @item comment_chars |
| 902 | @cindex comment_chars |
| 903 | This is a null terminated @code{const char} array of characters which start a |
| 904 | comment. |
| 905 | |
| 906 | @item tc_comment_chars |
| 907 | @cindex tc_comment_chars |
| 908 | If this macro is defined, GAS will use it instead of @code{comment_chars}. |
| 909 | |
| 910 | @item tc_symbol_chars |
| 911 | @cindex tc_symbol_chars |
| 912 | If this macro is defined, it is a pointer to a null terminated list of |
| 913 | characters which may appear in an operand. GAS already assumes that all |
| 914 | alphanumberic characters, and @samp{$}, @samp{.}, and @samp{_} may appear in an |
| 915 | operand (see @samp{symbol_chars} in @file{app.c}). This macro may be defined |
| 916 | to treat additional characters as appearing in an operand. This affects the |
| 917 | way in which GAS removes whitespace before passing the string to |
| 918 | @samp{md_assemble}. |
| 919 | |
| 920 | @item line_comment_chars |
| 921 | @cindex line_comment_chars |
| 922 | This is a null terminated @code{const char} array of characters which start a |
| 923 | comment when they appear at the start of a line. |
| 924 | |
| 925 | @item line_separator_chars |
| 926 | @cindex line_separator_chars |
| 927 | This is a null terminated @code{const char} array of characters which separate |
| 928 | lines (null and newline are such characters by default, and need not be |
| 929 | listed in this array). Note that line_separator_chars do not separate lines |
| 930 | if found in a comment, such as after a character in line_comment_chars or |
| 931 | comment_chars. |
| 932 | |
| 933 | @item EXP_CHARS |
| 934 | @cindex EXP_CHARS |
| 935 | This is a null terminated @code{const char} array of characters which may be |
| 936 | used as the exponent character in a floating point number. This is normally |
| 937 | @code{"eE"}. |
| 938 | |
| 939 | @item FLT_CHARS |
| 940 | @cindex FLT_CHARS |
| 941 | This is a null terminated @code{const char} array of characters which may be |
| 942 | used to indicate a floating point constant. A zero followed by one of these |
| 943 | characters is assumed to be followed by a floating point number; thus they |
| 944 | operate the way that @code{0x} is used to indicate a hexadecimal constant. |
| 945 | Usually this includes @samp{r} and @samp{f}. |
| 946 | |
| 947 | @item LEX_AT |
| 948 | @cindex LEX_AT |
| 949 | You may define this macro to the lexical type of the @kbd{@@} character. The |
| 950 | default is zero. |
| 951 | |
| 952 | Lexical types are a combination of @code{LEX_NAME} and @code{LEX_BEGIN_NAME}, |
| 953 | both defined in @file{read.h}. @code{LEX_NAME} indicates that the character |
| 954 | may appear in a name. @code{LEX_BEGIN_NAME} indicates that the character may |
| 955 | appear at the beginning of a name. |
| 956 | |
| 957 | @item LEX_BR |
| 958 | @cindex LEX_BR |
| 959 | You may define this macro to the lexical type of the brace characters @kbd{@{}, |
| 960 | @kbd{@}}, @kbd{[}, and @kbd{]}. The default value is zero. |
| 961 | |
| 962 | @item LEX_PCT |
| 963 | @cindex LEX_PCT |
| 964 | You may define this macro to the lexical type of the @kbd{%} character. The |
| 965 | default value is zero. |
| 966 | |
| 967 | @item LEX_QM |
| 968 | @cindex LEX_QM |
| 969 | You may define this macro to the lexical type of the @kbd{?} character. The |
| 970 | default value it zero. |
| 971 | |
| 972 | @item LEX_DOLLAR |
| 973 | @cindex LEX_DOLLAR |
| 974 | You may define this macro to the lexical type of the @kbd{$} character. The |
| 975 | default value is @code{LEX_NAME | LEX_BEGIN_NAME}. |
| 976 | |
| 977 | @item NUMBERS_WITH_SUFFIX |
| 978 | @cindex NUMBERS_WITH_SUFFIX |
| 979 | When this macro is defined to be non-zero, the parser allows the radix of a |
| 980 | constant to be indicated with a suffix. Valid suffixes are binary (B), |
| 981 | octal (Q), and hexadecimal (H). Case is not significant. |
| 982 | |
| 983 | @item SINGLE_QUOTE_STRINGS |
| 984 | @cindex SINGLE_QUOTE_STRINGS |
| 985 | If you define this macro, GAS will treat single quotes as string delimiters. |
| 986 | Normally only double quotes are accepted as string delimiters. |
| 987 | |
| 988 | @item NO_STRING_ESCAPES |
| 989 | @cindex NO_STRING_ESCAPES |
| 990 | If you define this macro, GAS will not permit escape sequences in a string. |
| 991 | |
| 992 | @item ONLY_STANDARD_ESCAPES |
| 993 | @cindex ONLY_STANDARD_ESCAPES |
| 994 | If you define this macro, GAS will warn about the use of nonstandard escape |
| 995 | sequences in a string. |
| 996 | |
| 997 | @item md_start_line_hook |
| 998 | @cindex md_start_line_hook |
| 999 | If you define this macro, GAS will call it at the start of each line. |
| 1000 | |
| 1001 | @item LABELS_WITHOUT_COLONS |
| 1002 | @cindex LABELS_WITHOUT_COLONS |
| 1003 | If you define this macro, GAS will assume that any text at the start of a line |
| 1004 | is a label, even if it does not have a colon. |
| 1005 | |
| 1006 | @item TC_START_LABEL |
| 1007 | @itemx TC_START_LABEL_WITHOUT_COLON |
| 1008 | @cindex TC_START_LABEL |
| 1009 | You may define this macro to control what GAS considers to be a label. The |
| 1010 | default definition is to accept any name followed by a colon character. |
| 1011 | |
| 1012 | @item TC_START_LABEL_WITHOUT_COLON |
| 1013 | @cindex TC_START_LABEL_WITHOUT_COLON |
| 1014 | Same as TC_START_LABEL, but should be used instead of TC_START_LABEL when |
| 1015 | LABELS_WITHOUT_COLONS is defined. |
| 1016 | |
| 1017 | @item NO_PSEUDO_DOT |
| 1018 | @cindex NO_PSEUDO_DOT |
| 1019 | If you define this macro, GAS will not require pseudo-ops to start with a |
| 1020 | @kbd{.} character. |
| 1021 | |
| 1022 | @item TC_EQUAL_IN_INSN |
| 1023 | @cindex TC_EQUAL_IN_INSN |
| 1024 | If you define this macro, it should return nonzero if the instruction is |
| 1025 | permitted to contain an @kbd{=} character. GAS will call it with two |
| 1026 | arguments, the character before the @kbd{=} character, and the value of |
| 1027 | @code{input_line_pointer} at that point. GAS uses this macro to decide if a |
| 1028 | @kbd{=} is an assignment or an instruction. |
| 1029 | |
| 1030 | @item TC_EOL_IN_INSN |
| 1031 | @cindex TC_EOL_IN_INSN |
| 1032 | If you define this macro, it should return nonzero if the current input line |
| 1033 | pointer should be treated as the end of a line. |
| 1034 | |
| 1035 | @item md_parse_name |
| 1036 | @cindex md_parse_name |
| 1037 | If this macro is defined, GAS will call it for any symbol found in an |
| 1038 | expression. You can define this to handle special symbols in a special way. |
| 1039 | If a symbol always has a certain value, you should normally enter it in the |
| 1040 | symbol table, perhaps using @code{reg_section}. |
| 1041 | |
| 1042 | @item md_undefined_symbol |
| 1043 | @cindex md_undefined_symbol |
| 1044 | GAS will call this function when a symbol table lookup fails, before it |
| 1045 | creates a new symbol. Typically this would be used to supply symbols whose |
| 1046 | name or value changes dynamically, possibly in a context sensitive way. |
| 1047 | Predefined symbols with fixed values, such as register names or condition |
| 1048 | codes, are typically entered directly into the symbol table when @code{md_begin} |
| 1049 | is called. One argument is passed, a @code{char *} for the symbol. |
| 1050 | |
| 1051 | @item md_operand |
| 1052 | @cindex md_operand |
| 1053 | GAS will call this function with one argument, an @code{expressionS} |
| 1054 | pointer, for any expression that can not be recognized. When the function |
| 1055 | is called, @code{input_line_pointer} will point to the start of the |
| 1056 | expression. |
| 1057 | |
| 1058 | @item tc_unrecognized_line |
| 1059 | @cindex tc_unrecognized_line |
| 1060 | If you define this macro, GAS will call it when it finds a line that it can not |
| 1061 | parse. |
| 1062 | |
| 1063 | @item md_do_align |
| 1064 | @cindex md_do_align |
| 1065 | You may define this macro to handle an alignment directive. GAS will call it |
| 1066 | when the directive is seen in the input file. For example, the i386 backend |
| 1067 | uses this to generate efficient nop instructions of varying lengths, depending |
| 1068 | upon the number of bytes that the alignment will skip. |
| 1069 | |
| 1070 | @item HANDLE_ALIGN |
| 1071 | @cindex HANDLE_ALIGN |
| 1072 | You may define this macro to do special handling for an alignment directive. |
| 1073 | GAS will call it at the end of the assembly. |
| 1074 | |
| 1075 | @item TC_IMPLICIT_LCOMM_ALIGNMENT (@var{size}, @var{p2var}) |
| 1076 | @cindex TC_IMPLICIT_LCOMM_ALIGNMENT |
| 1077 | An @code{.lcomm} directive with no explicit alignment parameter will use this |
| 1078 | macro to set @var{p2var} to the alignment that a request for @var{size} bytes |
| 1079 | will have. The alignment is expressed as a power of two. If no alignment |
| 1080 | should take place, the macro definition should do nothing. Some targets define |
| 1081 | a @code{.bss} directive that is also affected by this macro. The default |
| 1082 | definition will set @var{p2var} to the truncated power of two of sizes up to |
| 1083 | eight bytes. |
| 1084 | |
| 1085 | @item md_flush_pending_output |
| 1086 | @cindex md_flush_pending_output |
| 1087 | If you define this macro, GAS will call it each time it skips any space because of a |
| 1088 | space filling or alignment or data allocation pseudo-op. |
| 1089 | |
| 1090 | @item TC_PARSE_CONS_EXPRESSION |
| 1091 | @cindex TC_PARSE_CONS_EXPRESSION |
| 1092 | You may define this macro to parse an expression used in a data allocation |
| 1093 | pseudo-op such as @code{.word}. You can use this to recognize relocation |
| 1094 | directives that may appear in such directives. |
| 1095 | |
| 1096 | @item BITFIELD_CONS_EXPRESSION |
| 1097 | @cindex BITFIELD_CONS_EXPRESSION |
| 1098 | If you define this macro, GAS will recognize bitfield instructions in data |
| 1099 | allocation pseudo-ops, as used on the i960. |
| 1100 | |
| 1101 | @item REPEAT_CONS_EXPRESSION |
| 1102 | @cindex REPEAT_CONS_EXPRESSION |
| 1103 | If you define this macro, GAS will recognize repeat counts in data allocation |
| 1104 | pseudo-ops, as used on the MIPS. |
| 1105 | |
| 1106 | @item md_cons_align |
| 1107 | @cindex md_cons_align |
| 1108 | You may define this macro to do any special alignment before a data allocation |
| 1109 | pseudo-op. |
| 1110 | |
| 1111 | @item TC_CONS_FIX_NEW |
| 1112 | @cindex TC_CONS_FIX_NEW |
| 1113 | You may define this macro to generate a fixup for a data allocation pseudo-op. |
| 1114 | |
| 1115 | @item TC_INIT_FIX_DATA (@var{fixp}) |
| 1116 | @cindex TC_INIT_FIX_DATA |
| 1117 | A C statement to initialize the target specific fields of fixup @var{fixp}. |
| 1118 | These fields are defined with the @code{TC_FIX_TYPE} macro. |
| 1119 | |
| 1120 | @item TC_FIX_DATA_PRINT (@var{stream}, @var{fixp}) |
| 1121 | @cindex TC_FIX_DATA_PRINT |
| 1122 | A C statement to output target specific debugging information for |
| 1123 | fixup @var{fixp} to @var{stream}. This macro is called by @code{print_fixup}. |
| 1124 | |
| 1125 | @item TC_FRAG_INIT (@var{fragp}) |
| 1126 | @cindex TC_FRAG_INIT |
| 1127 | A C statement to initialize the target specific fields of frag @var{fragp}. |
| 1128 | These fields are defined with the @code{TC_FRAG_TYPE} macro. |
| 1129 | |
| 1130 | @item md_number_to_chars |
| 1131 | @cindex md_number_to_chars |
| 1132 | This should just call either @code{number_to_chars_bigendian} or |
| 1133 | @code{number_to_chars_littleendian}, whichever is appropriate. On targets like |
| 1134 | the MIPS which support options to change the endianness, which function to call |
| 1135 | is a runtime decision. On other targets, @code{md_number_to_chars} can be a |
| 1136 | simple macro. |
| 1137 | |
| 1138 | @item md_atof (@var{type},@var{litP},@var{sizeP}) |
| 1139 | @cindex md_atof |
| 1140 | This function is called to convert an ASCII string into a floating point value |
| 1141 | in format used by the CPU. It takes three arguments. The first is @var{type} |
| 1142 | which is a byte describing the type of floating point number to be created. |
| 1143 | Possible values are @var{'f'} or @var{'s'} for single precision, @var{'d'} or |
| 1144 | @var{'r'} for double precision and @var{'x'} or @var{'p'} for extended |
| 1145 | precision. Either lower or upper case versions of these letters can be used. |
| 1146 | |
| 1147 | The second parameter is @var{litP} which is a pointer to a byte array where the |
| 1148 | converted value should be stored. The third argument is @var{sizeP}, which is |
| 1149 | a pointer to a integer that should be filled in with the number of |
| 1150 | @var{LITTLENUM}s emitted into the byte array. (@var{LITTLENUM} is defined in |
| 1151 | gas/bignum.h). The function should return NULL upon success or an error string |
| 1152 | upon failure. |
| 1153 | |
| 1154 | @item TC_LARGEST_EXPONENT_IS_NORMAL |
| 1155 | @cindex TC_LARGEST_EXPONENT_IS_NORMAL (@var{precision}) |
| 1156 | This macro is used only by @file{atof-ieee.c}. It should evaluate to true |
| 1157 | if floats of the given precision use the largest exponent for normal numbers |
| 1158 | instead of NaNs and infinities. @var{precision} is @samp{F_PRECISION} for |
| 1159 | single precision, @samp{D_PRECISION} for double precision, or |
| 1160 | @samp{X_PRECISION} for extended double precision. |
| 1161 | |
| 1162 | The macro has a default definition which returns 0 for all cases. |
| 1163 | |
| 1164 | @item md_reloc_size |
| 1165 | @cindex md_reloc_size |
| 1166 | This variable is only used in the original version of gas (not |
| 1167 | @code{BFD_ASSEMBLER} and not @code{MANY_SEGMENTS}). It holds the size of a |
| 1168 | relocation entry. |
| 1169 | |
| 1170 | @item WORKING_DOT_WORD |
| 1171 | @itemx md_short_jump_size |
| 1172 | @itemx md_long_jump_size |
| 1173 | @itemx md_create_short_jump |
| 1174 | @itemx md_create_long_jump |
| 1175 | @itemx TC_CHECK_ADJUSTED_BROKEN_DOT_WORD |
| 1176 | @cindex WORKING_DOT_WORD |
| 1177 | @cindex md_short_jump_size |
| 1178 | @cindex md_long_jump_size |
| 1179 | @cindex md_create_short_jump |
| 1180 | @cindex md_create_long_jump |
| 1181 | @cindex TC_CHECK_ADJUSTED_BROKEN_DOT_WORD |
| 1182 | If @code{WORKING_DOT_WORD} is defined, GAS will not do broken word processing |
| 1183 | (@pxref{Broken words}). Otherwise, you should set @code{md_short_jump_size} to |
| 1184 | the size of a short jump (a jump that is just long enough to jump around a |
| 1185 | number of long jumps) and @code{md_long_jump_size} to the size of a long jump |
| 1186 | (a jump that can go anywhere in the function). You should define |
| 1187 | @code{md_create_short_jump} to create a short jump around a number of long |
| 1188 | jumps, and define @code{md_create_long_jump} to create a long jump. |
| 1189 | If defined, the macro TC_CHECK_ADJUSTED_BROKEN_DOT_WORD will be called for each |
| 1190 | adjusted word just before the word is output. The macro takes two arguments, |
| 1191 | an @code{addressT} with the adjusted word and a pointer to the current |
| 1192 | @code{struct broken_word}. |
| 1193 | |
| 1194 | @item md_estimate_size_before_relax |
| 1195 | @cindex md_estimate_size_before_relax |
| 1196 | This function returns an estimate of the size of a @code{rs_machine_dependent} |
| 1197 | frag before any relaxing is done. It may also create any necessary |
| 1198 | relocations. |
| 1199 | |
| 1200 | @item md_relax_frag |
| 1201 | @cindex md_relax_frag |
| 1202 | This macro may be defined to relax a frag. GAS will call this with the |
| 1203 | segment, the frag, and the change in size of all previous frags; |
| 1204 | @code{md_relax_frag} should return the change in size of the frag. |
| 1205 | @xref{Relaxation}. |
| 1206 | |
| 1207 | @item TC_GENERIC_RELAX_TABLE |
| 1208 | @cindex TC_GENERIC_RELAX_TABLE |
| 1209 | If you do not define @code{md_relax_frag}, you may define |
| 1210 | @code{TC_GENERIC_RELAX_TABLE} as a table of @code{relax_typeS} structures. The |
| 1211 | machine independent code knows how to use such a table to relax PC relative |
| 1212 | references. See @file{tc-m68k.c} for an example. @xref{Relaxation}. |
| 1213 | |
| 1214 | @item md_prepare_relax_scan |
| 1215 | @cindex md_prepare_relax_scan |
| 1216 | If defined, it is a C statement that is invoked prior to scanning |
| 1217 | the relax table. |
| 1218 | |
| 1219 | @item LINKER_RELAXING_SHRINKS_ONLY |
| 1220 | @cindex LINKER_RELAXING_SHRINKS_ONLY |
| 1221 | If you define this macro, and the global variable @samp{linkrelax} is set |
| 1222 | (because of a command line option, or unconditionally in @code{md_begin}), a |
| 1223 | @samp{.align} directive will cause extra space to be allocated. The linker can |
| 1224 | then discard this space when relaxing the section. |
| 1225 | |
| 1226 | @item TC_LINKRELAX_FIXUP (@var{segT}) |
| 1227 | @cindex TC_LINKRELAX_FIXUP |
| 1228 | If defined, this macro allows control over whether fixups for a |
| 1229 | given section will be processed when the @var{linkrelax} variable is |
| 1230 | set. The macro is given the N_TYPE bits for the section in its |
| 1231 | @var{segT} argument. If the macro evaluates to a non-zero value |
| 1232 | then the fixups will be converted into relocs, otherwise they will |
| 1233 | be passed to @var{md_apply_fix3} as normal. |
| 1234 | |
| 1235 | @item md_convert_frag |
| 1236 | @cindex md_convert_frag |
| 1237 | GAS will call this for each rs_machine_dependent fragment. |
| 1238 | The instruction is completed using the data from the relaxation pass. |
| 1239 | It may also create any necessary relocations. |
| 1240 | @xref{Relaxation}. |
| 1241 | |
| 1242 | @item TC_FINALIZE_SYMS_BEFORE_SIZE_SEG |
| 1243 | @cindex TC_FINALIZE_SYMS_BEFORE_SIZE_SEG |
| 1244 | Specifies the value to be assigned to @code{finalize_syms} before the function |
| 1245 | @code{size_segs} is called. Since @code{size_segs} calls @code{cvt_frag_to_fill} |
| 1246 | which can call @code{md_convert_frag}, this constant governs whether the symbols |
| 1247 | accessed in @code{md_convert_frag} will be fully resolved. In particular it |
| 1248 | governs whether local symbols will have been resolved, and had their frag |
| 1249 | information removed. Depending upon the processing performed by |
| 1250 | @code{md_convert_frag} the frag information may or may not be necessary, as may |
| 1251 | the resolved values of the symbols. The default value is 1. |
| 1252 | |
| 1253 | @item TC_VALIDATE_FIX (@var{fixP}, @var{seg}, @var{skip}) |
| 1254 | @cindex TC_VALIDATE_FIX |
| 1255 | This macro is evaluated for each fixup (when @var{linkrelax} is not set). |
| 1256 | It may be used to change the fixup in @code{struct fix *@var{fixP}} before |
| 1257 | the generic code sees it, or to fully process the fixup. In the latter case, |
| 1258 | a @code{goto @var{skip}} will bypass the generic code. |
| 1259 | |
| 1260 | @item md_apply_fix3 (@var{fixP}, @var{valP}, @var{seg}) |
| 1261 | @cindex md_apply_fix3 |
| 1262 | GAS will call this for each fixup that passes the @code{TC_VALIDATE_FIX} test |
| 1263 | when @var{linkrelax} is not set. It should store the correct value in the |
| 1264 | object file. @code{struct fix *@var{fixP}} is the fixup @code{md_apply_fix3} |
| 1265 | is operating on. @code{valueT *@var{valP}} is the value to store into the |
| 1266 | object files, or at least is the generic code's best guess. Specifically, |
| 1267 | *@var{valP} is the value of the fixup symbol, perhaps modified by |
| 1268 | @code{MD_APPLY_SYM_VALUE}, plus @code{@var{fixP}->fx_offset} (symbol addend), |
| 1269 | less @code{MD_PCREL_FROM_SECTION} for pc-relative fixups. |
| 1270 | @code{segT @var{seg}} is the section the fix is in. |
| 1271 | @code{fixup_segment} performs a generic overflow check on *@var{valP} after |
| 1272 | @code{md_apply_fix3} returns. If the overflow check is relevant for the target |
| 1273 | machine, then @code{md_apply_fix3} should modify *@var{valP}, typically to the |
| 1274 | value stored in the object file. |
| 1275 | |
| 1276 | @item TC_FORCE_RELOCATION (@var{fix}) |
| 1277 | @cindex TC_FORCE_RELOCATION |
| 1278 | If this macro returns non-zero, it guarantees that a relocation will be emitted |
| 1279 | even when the value can be resolved locally, as @code{fixup_segment} tries to |
| 1280 | reduce the number of relocations emitted. For example, a fixup expression |
| 1281 | against an absolute symbol will normally not require a reloc. If undefined, |
| 1282 | a default of @w{@code{(S_FORCE_RELOC ((@var{fix})->fx_addsy))}} is used. |
| 1283 | |
| 1284 | @item TC_FORCE_RELOCATION_ABS (@var{fix}) |
| 1285 | @cindex TC_FORCE_RELOCATION_ABS |
| 1286 | Like @code{TC_FORCE_RELOCATION}, but used only for fixup expressions against an |
| 1287 | absolute symbol. If undefined, @code{TC_FORCE_RELOCATION} will be used. |
| 1288 | |
| 1289 | @item TC_FORCE_RELOCATION_LOCAL (@var{fix}) |
| 1290 | @cindex TC_FORCE_RELOCATION_LOCAL |
| 1291 | Like @code{TC_FORCE_RELOCATION}, but used only for fixup expressions against a |
| 1292 | symbol in the current section. If undefined, fixups that are not |
| 1293 | @code{fx_pcrel} or @code{fx_plt} or for which @code{TC_FORCE_RELOCATION} |
| 1294 | returns non-zero, will emit relocs. |
| 1295 | |
| 1296 | @item TC_FORCE_RELOCATION_SUB_SAME (@var{fix}, @var{seg}) |
| 1297 | @cindex TC_FORCE_RELOCATION_SUB_SAME |
| 1298 | This macro controls resolution of fixup expressions involving the |
| 1299 | difference of two symbols in the same section. If this macro returns zero, |
| 1300 | the subtrahend will be resolved and @code{fx_subsy} set to @code{NULL} for |
| 1301 | @code{md_apply_fix3}. If undefined, the default of |
| 1302 | @w{@code{! SEG_NORMAL (@var{seg}) || TC_FORCE_RELOCATION (@var{fix})}} will |
| 1303 | be used. |
| 1304 | |
| 1305 | @item TC_FORCE_RELOCATION_SUB_ABS (@var{fix}) |
| 1306 | @cindex TC_FORCE_RELOCATION_SUB_ABS |
| 1307 | Like @code{TC_FORCE_RELOCATION_SUB_SAME}, but used when the subtrahend is an |
| 1308 | absolute symbol. If the macro is undefined a default of @code{0} is used. |
| 1309 | |
| 1310 | @item TC_FORCE_RELOCATION_SUB_LOCAL (@var{fix}) |
| 1311 | @cindex TC_FORCE_RELOCATION_SUB_LOCAL |
| 1312 | Like @code{TC_FORCE_RELOCATION_SUB_ABS}, but the subtrahend is a symbol in the |
| 1313 | same section as the fixup. |
| 1314 | |
| 1315 | @item TC_VALIDATE_FIX_SUB (@var{fix}) |
| 1316 | @cindex TC_VALIDATE_FIX_SUB |
| 1317 | This macro is evaluated for any fixup with a @code{fx_subsy} that |
| 1318 | @code{fixup_segment} cannot reduce to a number. If the macro returns |
| 1319 | @code{false} an error will be reported. |
| 1320 | |
| 1321 | @item MD_APPLY_SYM_VALUE (@var{fix}) |
| 1322 | @cindex MD_APPLY_SYM_VALUE |
| 1323 | This macro controls whether the symbol value becomes part of the value passed |
| 1324 | to @code{md_apply_fix3}. If the macro is undefined, or returns non-zero, the |
| 1325 | symbol value will be included. For ELF, a suitable definition might simply be |
| 1326 | @code{0}, because ELF relocations don't include the symbol value in the addend. |
| 1327 | |
| 1328 | @item S_FORCE_RELOC (@var{sym}, @var{strict}) |
| 1329 | @cindex S_FORCE_RELOC |
| 1330 | This macro (or function, for @code{BFD_ASSEMBLER} gas) returns true for symbols |
| 1331 | that should not be reduced to section symbols or eliminated from expressions, |
| 1332 | because they may be overridden by the linker. ie. for symbols that are |
| 1333 | undefined or common, and when @var{strict} is set, weak, or global (for ELF |
| 1334 | assemblers that support ELF shared library linking semantics). |
| 1335 | |
| 1336 | @item EXTERN_FORCE_RELOC |
| 1337 | @cindex EXTERN_FORCE_RELOC |
| 1338 | This macro controls whether @code{S_FORCE_RELOC} returns true for global |
| 1339 | symbols. If undefined, the default is @code{true} for ELF assemblers, and |
| 1340 | @code{false} for non-ELF. |
| 1341 | |
| 1342 | @item tc_gen_reloc |
| 1343 | @cindex tc_gen_reloc |
| 1344 | A @code{BFD_ASSEMBLER} GAS will call this to generate a reloc. GAS will pass |
| 1345 | the resulting reloc to @code{bfd_install_relocation}. This currently works |
| 1346 | poorly, as @code{bfd_install_relocation} often does the wrong thing, and |
| 1347 | instances of @code{tc_gen_reloc} have been written to work around the problems, |
| 1348 | which in turns makes it difficult to fix @code{bfd_install_relocation}. |
| 1349 | |
| 1350 | @item RELOC_EXPANSION_POSSIBLE |
| 1351 | @cindex RELOC_EXPANSION_POSSIBLE |
| 1352 | If you define this macro, it means that @code{tc_gen_reloc} may return multiple |
| 1353 | relocation entries for a single fixup. In this case, the return value of |
| 1354 | @code{tc_gen_reloc} is a pointer to a null terminated array. |
| 1355 | |
| 1356 | @item MAX_RELOC_EXPANSION |
| 1357 | @cindex MAX_RELOC_EXPANSION |
| 1358 | You must define this if @code{RELOC_EXPANSION_POSSIBLE} is defined; it |
| 1359 | indicates the largest number of relocs which @code{tc_gen_reloc} may return for |
| 1360 | a single fixup. |
| 1361 | |
| 1362 | @item tc_fix_adjustable |
| 1363 | @cindex tc_fix_adjustable |
| 1364 | You may define this macro to indicate whether a fixup against a locally defined |
| 1365 | symbol should be adjusted to be against the section symbol. It should return a |
| 1366 | non-zero value if the adjustment is acceptable. |
| 1367 | |
| 1368 | @item MD_PCREL_FROM_SECTION (@var{fixp}, @var{section}) |
| 1369 | @cindex MD_PCREL_FROM_SECTION |
| 1370 | If you define this macro, it should return the position from which the PC |
| 1371 | relative adjustment for a PC relative fixup should be made. On many |
| 1372 | processors, the base of a PC relative instruction is the next instruction, |
| 1373 | so this macro would return the length of an instruction, plus the address of |
| 1374 | the PC relative fixup. The latter can be calculated as |
| 1375 | @var{fixp}->fx_where + @var{fixp}->fx_frag->fr_address . |
| 1376 | |
| 1377 | @item md_pcrel_from |
| 1378 | @cindex md_pcrel_from |
| 1379 | This is the default value of @code{MD_PCREL_FROM_SECTION}. The difference is |
| 1380 | that @code{md_pcrel_from} does not take a section argument. |
| 1381 | |
| 1382 | @item tc_frob_label |
| 1383 | @cindex tc_frob_label |
| 1384 | If you define this macro, GAS will call it each time a label is defined. |
| 1385 | |
| 1386 | @item md_section_align |
| 1387 | @cindex md_section_align |
| 1388 | GAS will call this function for each section at the end of the assembly, to |
| 1389 | permit the CPU backend to adjust the alignment of a section. The function |
| 1390 | must take two arguments, a @code{segT} for the section and a @code{valueT} |
| 1391 | for the size of the section, and return a @code{valueT} for the rounded |
| 1392 | size. |
| 1393 | |
| 1394 | @item md_macro_start |
| 1395 | @cindex md_macro_start |
| 1396 | If defined, GAS will call this macro when it starts to include a macro |
| 1397 | expansion. @code{macro_nest} indicates the current macro nesting level, which |
| 1398 | includes the one being expanded. |
| 1399 | |
| 1400 | @item md_macro_info |
| 1401 | @cindex md_macro_info |
| 1402 | If defined, GAS will call this macro after the macro expansion has been |
| 1403 | included in the input and after parsing the macro arguments. The single |
| 1404 | argument is a pointer to the macro processing's internal representation of the |
| 1405 | macro (macro_entry *), which includes expansion of the formal arguments. |
| 1406 | |
| 1407 | @item md_macro_end |
| 1408 | @cindex md_macro_end |
| 1409 | Complement to md_macro_start. If defined, it is called when finished |
| 1410 | processing an inserted macro expansion, just before decrementing macro_nest. |
| 1411 | |
| 1412 | @item DOUBLEBAR_PARALLEL |
| 1413 | @cindex DOUBLEBAR_PARALLEL |
| 1414 | Affects the preprocessor so that lines containing '||' don't have their |
| 1415 | whitespace stripped following the double bar. This is useful for targets that |
| 1416 | implement parallel instructions. |
| 1417 | |
| 1418 | @item KEEP_WHITE_AROUND_COLON |
| 1419 | @cindex KEEP_WHITE_AROUND_COLON |
| 1420 | Normally, whitespace is compressed and removed when, in the presence of the |
| 1421 | colon, the adjoining tokens can be distinguished. This option affects the |
| 1422 | preprocessor so that whitespace around colons is preserved. This is useful |
| 1423 | when colons might be removed from the input after preprocessing but before |
| 1424 | assembling, so that adjoining tokens can still be distinguished if there is |
| 1425 | whitespace, or concatenated if there is not. |
| 1426 | |
| 1427 | @item tc_frob_section |
| 1428 | @cindex tc_frob_section |
| 1429 | If you define this macro, a @code{BFD_ASSEMBLER} GAS will call it for each |
| 1430 | section at the end of the assembly. |
| 1431 | |
| 1432 | @item tc_frob_file_before_adjust |
| 1433 | @cindex tc_frob_file_before_adjust |
| 1434 | If you define this macro, GAS will call it after the symbol values are |
| 1435 | resolved, but before the fixups have been changed from local symbols to section |
| 1436 | symbols. |
| 1437 | |
| 1438 | @item tc_frob_symbol |
| 1439 | @cindex tc_frob_symbol |
| 1440 | If you define this macro, GAS will call it for each symbol. You can indicate |
| 1441 | that the symbol should not be included in the object file by defining this |
| 1442 | macro to set its second argument to a non-zero value. |
| 1443 | |
| 1444 | @item tc_frob_file |
| 1445 | @cindex tc_frob_file |
| 1446 | If you define this macro, GAS will call it after the symbol table has been |
| 1447 | completed, but before the relocations have been generated. |
| 1448 | |
| 1449 | @item tc_frob_file_after_relocs |
| 1450 | If you define this macro, GAS will call it after the relocs have been |
| 1451 | generated. |
| 1452 | |
| 1453 | @item md_post_relax_hook |
| 1454 | If you define this macro, GAS will call it after relaxing and sizing the |
| 1455 | segments. |
| 1456 | |
| 1457 | @item LISTING_HEADER |
| 1458 | A string to use on the header line of a listing. The default value is simply |
| 1459 | @code{"GAS LISTING"}. |
| 1460 | |
| 1461 | @item LISTING_WORD_SIZE |
| 1462 | The number of bytes to put into a word in a listing. This affects the way the |
| 1463 | bytes are clumped together in the listing. For example, a value of 2 might |
| 1464 | print @samp{1234 5678} where a value of 1 would print @samp{12 34 56 78}. The |
| 1465 | default value is 4. |
| 1466 | |
| 1467 | @item LISTING_LHS_WIDTH |
| 1468 | The number of words of data to print on the first line of a listing for a |
| 1469 | particular source line, where each word is @code{LISTING_WORD_SIZE} bytes. The |
| 1470 | default value is 1. |
| 1471 | |
| 1472 | @item LISTING_LHS_WIDTH_SECOND |
| 1473 | Like @code{LISTING_LHS_WIDTH}, but applying to the second and subsequent line |
| 1474 | of the data printed for a particular source line. The default value is 1. |
| 1475 | |
| 1476 | @item LISTING_LHS_CONT_LINES |
| 1477 | The maximum number of continuation lines to print in a listing for a particular |
| 1478 | source line. The default value is 4. |
| 1479 | |
| 1480 | @item LISTING_RHS_WIDTH |
| 1481 | The maximum number of characters to print from one line of the input file. The |
| 1482 | default value is 100. |
| 1483 | |
| 1484 | @item TC_COFF_SECTION_DEFAULT_ATTRIBUTES |
| 1485 | @cindex TC_COFF_SECTION_DEFAULT_ATTRIBUTES |
| 1486 | The COFF @code{.section} directive will use the value of this macro to set |
| 1487 | a new section's attributes when a directive has no valid flags or when the |
| 1488 | flag is @code{w}. The default value of the macro is @code{SEC_LOAD | SEC_DATA}. |
| 1489 | |
| 1490 | @item DWARF2_FORMAT () |
| 1491 | @cindex DWARF2_FORMAT |
| 1492 | If you define this, it should return one of @code{dwarf2_format_32bit}, |
| 1493 | @code{dwarf2_format_64bit}, or @code{dwarf2_format_64bit_irix} to indicate |
| 1494 | the size of internal DWARF section offsets and the format of the DWARF initial |
| 1495 | length fields. When @code{dwarf2_format_32bit} is returned, the initial |
| 1496 | length field will be 4 bytes long and section offsets are 32 bits in size. |
| 1497 | For @code{dwarf2_format_64bit} and @code{dwarf2_format_64bit_irix}, section |
| 1498 | offsets are 64 bits in size, but the initial length field differs. An 8 byte |
| 1499 | initial length is indicated by @code{dwarf2_format_64bit_irix} and |
| 1500 | @code{dwarf2_format_64bit} indicates a 12 byte initial length field in |
| 1501 | which the first four bytes are 0xffffffff and the next 8 bytes are |
| 1502 | the section's length. |
| 1503 | |
| 1504 | If you don't define this, @code{dwarf2_format_32bit} will be used as |
| 1505 | the default. |
| 1506 | |
| 1507 | This define only affects @code{.debug_info} and @code{.debug_line} |
| 1508 | sections generated by the assembler. DWARF 2 sections generated by |
| 1509 | other tools will be unaffected by this setting. |
| 1510 | |
| 1511 | @item DWARF2_ADDR_SIZE (@var{bfd}) |
| 1512 | @cindex DWARF2_ADDR_SIZE |
| 1513 | It should return the size of an address, as it should be represented in |
| 1514 | debugging info. If you don't define this macro, the default definition uses |
| 1515 | the number of bits per address, as defined in @var{bfd}, divided by 8. |
| 1516 | |
| 1517 | @end table |
| 1518 | |
| 1519 | @node Object format backend |
| 1520 | @subsection Writing an object format backend |
| 1521 | @cindex object format backend |
| 1522 | @cindex @file{obj-@var{fmt}} |
| 1523 | |
| 1524 | As with the CPU backend, the object format backend must define a few things, |
| 1525 | and may define some other things. The interface to the object format backend |
| 1526 | is generally simpler; most of the support for an object file format consists of |
| 1527 | defining a number of pseudo-ops. |
| 1528 | |
| 1529 | The object format @file{.h} file must include @file{targ-cpu.h}. |
| 1530 | |
| 1531 | This section will only define the @code{BFD_ASSEMBLER} version of GAS. It is |
| 1532 | impossible to support a new object file format using any other version anyhow, |
| 1533 | as the original GAS version only supports a.out, and the @code{MANY_SEGMENTS} |
| 1534 | GAS version only supports COFF. |
| 1535 | |
| 1536 | @table @code |
| 1537 | @item OBJ_@var{format} |
| 1538 | @cindex OBJ_@var{format} |
| 1539 | By convention, you should define this macro in the @file{.h} file. For |
| 1540 | example, @file{obj-elf.h} defines @code{OBJ_ELF}. You might have to use this |
| 1541 | if it is necessary to add object file format specific code to the CPU file. |
| 1542 | |
| 1543 | @item obj_begin |
| 1544 | If you define this macro, GAS will call it at the start of the assembly, after |
| 1545 | the command line arguments have been parsed and all the machine independent |
| 1546 | initializations have been completed. |
| 1547 | |
| 1548 | @item obj_app_file |
| 1549 | @cindex obj_app_file |
| 1550 | If you define this macro, GAS will invoke it when it sees a @code{.file} |
| 1551 | pseudo-op or a @samp{#} line as used by the C preprocessor. |
| 1552 | |
| 1553 | @item OBJ_COPY_SYMBOL_ATTRIBUTES |
| 1554 | @cindex OBJ_COPY_SYMBOL_ATTRIBUTES |
| 1555 | You should define this macro to copy object format specific information from |
| 1556 | one symbol to another. GAS will call it when one symbol is equated to |
| 1557 | another. |
| 1558 | |
| 1559 | @item obj_sec_sym_ok_for_reloc |
| 1560 | @cindex obj_sec_sym_ok_for_reloc |
| 1561 | You may define this macro to indicate that it is OK to use a section symbol in |
| 1562 | a relocation entry. If it is not, GAS will define a new symbol at the start |
| 1563 | of a section. |
| 1564 | |
| 1565 | @item EMIT_SECTION_SYMBOLS |
| 1566 | @cindex EMIT_SECTION_SYMBOLS |
| 1567 | You should define this macro with a zero value if you do not want to include |
| 1568 | section symbols in the output symbol table. The default value for this macro |
| 1569 | is one. |
| 1570 | |
| 1571 | @item obj_adjust_symtab |
| 1572 | @cindex obj_adjust_symtab |
| 1573 | If you define this macro, GAS will invoke it just before setting the symbol |
| 1574 | table of the output BFD. For example, the COFF support uses this macro to |
| 1575 | generate a @code{.file} symbol if none was generated previously. |
| 1576 | |
| 1577 | @item SEPARATE_STAB_SECTIONS |
| 1578 | @cindex SEPARATE_STAB_SECTIONS |
| 1579 | You may define this macro to a nonzero value to indicate that stabs should be |
| 1580 | placed in separate sections, as in ELF. |
| 1581 | |
| 1582 | @item INIT_STAB_SECTION |
| 1583 | @cindex INIT_STAB_SECTION |
| 1584 | You may define this macro to initialize the stabs section in the output file. |
| 1585 | |
| 1586 | @item OBJ_PROCESS_STAB |
| 1587 | @cindex OBJ_PROCESS_STAB |
| 1588 | You may define this macro to do specific processing on a stabs entry. |
| 1589 | |
| 1590 | @item obj_frob_section |
| 1591 | @cindex obj_frob_section |
| 1592 | If you define this macro, GAS will call it for each section at the end of the |
| 1593 | assembly. |
| 1594 | |
| 1595 | @item obj_frob_file_before_adjust |
| 1596 | @cindex obj_frob_file_before_adjust |
| 1597 | If you define this macro, GAS will call it after the symbol values are |
| 1598 | resolved, but before the fixups have been changed from local symbols to section |
| 1599 | symbols. |
| 1600 | |
| 1601 | @item obj_frob_symbol |
| 1602 | @cindex obj_frob_symbol |
| 1603 | If you define this macro, GAS will call it for each symbol. You can indicate |
| 1604 | that the symbol should not be included in the object file by defining this |
| 1605 | macro to set its second argument to a non-zero value. |
| 1606 | |
| 1607 | @item obj_frob_file |
| 1608 | @cindex obj_frob_file |
| 1609 | If you define this macro, GAS will call it after the symbol table has been |
| 1610 | completed, but before the relocations have been generated. |
| 1611 | |
| 1612 | @item obj_frob_file_after_relocs |
| 1613 | If you define this macro, GAS will call it after the relocs have been |
| 1614 | generated. |
| 1615 | |
| 1616 | @item SET_SECTION_RELOCS (@var{sec}, @var{relocs}, @var{n}) |
| 1617 | @cindex SET_SECTION_RELOCS |
| 1618 | If you define this, it will be called after the relocations have been set for |
| 1619 | the section @var{sec}. The list of relocations is in @var{relocs}, and the |
| 1620 | number of relocations is in @var{n}. This is only used with |
| 1621 | @code{BFD_ASSEMBLER}. |
| 1622 | @end table |
| 1623 | |
| 1624 | @node Emulations |
| 1625 | @subsection Writing emulation files |
| 1626 | |
| 1627 | Normally you do not have to write an emulation file. You can just use |
| 1628 | @file{te-generic.h}. |
| 1629 | |
| 1630 | If you do write your own emulation file, it must include @file{obj-format.h}. |
| 1631 | |
| 1632 | An emulation file will often define @code{TE_@var{EM}}; this may then be used |
| 1633 | in other files to change the output. |
| 1634 | |
| 1635 | @node Relaxation |
| 1636 | @section Relaxation |
| 1637 | @cindex relaxation |
| 1638 | |
| 1639 | @dfn{Relaxation} is a generic term used when the size of some instruction or |
| 1640 | data depends upon the value of some symbol or other data. |
| 1641 | |
| 1642 | GAS knows to relax a particular type of PC relative relocation using a table. |
| 1643 | You can also define arbitrarily complex forms of relaxation yourself. |
| 1644 | |
| 1645 | @menu |
| 1646 | * Relaxing with a table:: Relaxing with a table |
| 1647 | * General relaxing:: General relaxing |
| 1648 | @end menu |
| 1649 | |
| 1650 | @node Relaxing with a table |
| 1651 | @subsection Relaxing with a table |
| 1652 | |
| 1653 | If you do not define @code{md_relax_frag}, and you do define |
| 1654 | @code{TC_GENERIC_RELAX_TABLE}, GAS will relax @code{rs_machine_dependent} frags |
| 1655 | based on the frag subtype and the displacement to some specified target |
| 1656 | address. The basic idea is that several machines have different addressing |
| 1657 | modes for instructions that can specify different ranges of values, with |
| 1658 | successive modes able to access wider ranges, including the entirety of the |
| 1659 | previous range. Smaller ranges are assumed to be more desirable (perhaps the |
| 1660 | instruction requires one word instead of two or three); if this is not the |
| 1661 | case, don't describe the smaller-range, inferior mode. |
| 1662 | |
| 1663 | The @code{fr_subtype} field of a frag is an index into a CPU-specific |
| 1664 | relaxation table. That table entry indicates the range of values that can be |
| 1665 | stored, the number of bytes that will have to be added to the frag to |
| 1666 | accommodate the addressing mode, and the index of the next entry to examine if |
| 1667 | the value to be stored is outside the range accessible by the current |
| 1668 | addressing mode. The @code{fr_symbol} field of the frag indicates what symbol |
| 1669 | is to be accessed; the @code{fr_offset} field is added in. |
| 1670 | |
| 1671 | If the @code{TC_PCREL_ADJUST} macro is defined, which currently should only happen |
| 1672 | for the NS32k family, the @code{TC_PCREL_ADJUST} macro is called on the frag to |
| 1673 | compute an adjustment to be made to the displacement. |
| 1674 | |
| 1675 | The value fitted by the relaxation code is always assumed to be a displacement |
| 1676 | from the current frag. (More specifically, from @code{fr_fix} bytes into the |
| 1677 | frag.) |
| 1678 | @ignore |
| 1679 | This seems kinda silly. What about fitting small absolute values? I suppose |
| 1680 | @code{md_assemble} is supposed to take care of that, but if the operand is a |
| 1681 | difference between symbols, it might not be able to, if the difference was not |
| 1682 | computable yet. |
| 1683 | @end ignore |
| 1684 | |
| 1685 | The end of the relaxation sequence is indicated by a ``next'' value of 0. This |
| 1686 | means that the first entry in the table can't be used. |
| 1687 | |
| 1688 | For some configurations, the linker can do relaxing within a section of an |
| 1689 | object file. If call instructions of various sizes exist, the linker can |
| 1690 | determine which should be used in each instance, when a symbol's value is |
| 1691 | resolved. In order for the linker to avoid wasting space and having to insert |
| 1692 | no-op instructions, it must be able to expand or shrink the section contents |
| 1693 | while still preserving intra-section references and meeting alignment |
| 1694 | requirements. |
| 1695 | |
| 1696 | For the i960 using b.out format, no expansion is done; instead, each |
| 1697 | @samp{.align} directive causes extra space to be allocated, enough that when |
| 1698 | the linker is relaxing a section and removing unneeded space, it can discard |
| 1699 | some or all of this extra padding and cause the following data to be correctly |
| 1700 | aligned. |
| 1701 | |
| 1702 | For the H8/300, I think the linker expands calls that can't reach, and doesn't |
| 1703 | worry about alignment issues; the cpu probably never needs any significant |
| 1704 | alignment beyond the instruction size. |
| 1705 | |
| 1706 | The relaxation table type contains these fields: |
| 1707 | |
| 1708 | @table @code |
| 1709 | @item long rlx_forward |
| 1710 | Forward reach, must be non-negative. |
| 1711 | @item long rlx_backward |
| 1712 | Backward reach, must be zero or negative. |
| 1713 | @item rlx_length |
| 1714 | Length in bytes of this addressing mode. |
| 1715 | @item rlx_more |
| 1716 | Index of the next-longer relax state, or zero if there is no next relax state. |
| 1717 | @end table |
| 1718 | |
| 1719 | The relaxation is done in @code{relax_segment} in @file{write.c}. The |
| 1720 | difference in the length fields between the original mode and the one finally |
| 1721 | chosen by the relaxing code is taken as the size by which the current frag will |
| 1722 | be increased in size. For example, if the initial relaxing mode has a length |
| 1723 | of 2 bytes, and because of the size of the displacement, it gets upgraded to a |
| 1724 | mode with a size of 6 bytes, it is assumed that the frag will grow by 4 bytes. |
| 1725 | (The initial two bytes should have been part of the fixed portion of the frag, |
| 1726 | since it is already known that they will be output.) This growth must be |
| 1727 | effected by @code{md_convert_frag}; it should increase the @code{fr_fix} field |
| 1728 | by the appropriate size, and fill in the appropriate bytes of the frag. |
| 1729 | (Enough space for the maximum growth should have been allocated in the call to |
| 1730 | frag_var as the second argument.) |
| 1731 | |
| 1732 | If relocation records are needed, they should be emitted by |
| 1733 | @code{md_estimate_size_before_relax}. This function should examine the target |
| 1734 | symbol of the supplied frag and correct the @code{fr_subtype} of the frag if |
| 1735 | needed. When this function is called, if the symbol has not yet been defined, |
| 1736 | it will not become defined later; however, its value may still change if the |
| 1737 | section it is in gets relaxed. |
| 1738 | |
| 1739 | Usually, if the symbol is in the same section as the frag (given by the |
| 1740 | @var{sec} argument), the narrowest likely relaxation mode is stored in |
| 1741 | @code{fr_subtype}, and that's that. |
| 1742 | |
| 1743 | If the symbol is undefined, or in a different section (and therefore movable |
| 1744 | to an arbitrarily large distance), the largest available relaxation mode is |
| 1745 | specified, @code{fix_new} is called to produce the relocation record, |
| 1746 | @code{fr_fix} is increased to include the relocated field (remember, this |
| 1747 | storage was allocated when @code{frag_var} was called), and @code{frag_wane} is |
| 1748 | called to convert the frag to an @code{rs_fill} frag with no variant part. |
| 1749 | Sometimes changing addressing modes may also require rewriting the instruction. |
| 1750 | It can be accessed via @code{fr_opcode} or @code{fr_fix}. |
| 1751 | |
| 1752 | If you generate frags separately for the basic insn opcode and any relaxable |
| 1753 | operands, do not call @code{fix_new} thinking you can emit fixups for the |
| 1754 | opcode field from the relaxable frag. It is not guaranteed to be the same frag. |
| 1755 | If you need to emit fixups for the opcode field from inspection of the |
| 1756 | relaxable frag, then you need to generate a common frag for both the basic |
| 1757 | opcode and relaxable fields, or you need to provide the frag for the opcode to |
| 1758 | pass to @code{fix_new}. The latter can be done for example by defining |
| 1759 | @code{TC_FRAG_TYPE} to include a pointer to it and defining @code{TC_FRAG_INIT} |
| 1760 | to set the pointer. |
| 1761 | |
| 1762 | Sometimes @code{fr_var} is increased instead, and @code{frag_wane} is not |
| 1763 | called. I'm not sure, but I think this is to keep @code{fr_fix} referring to |
| 1764 | an earlier byte, and @code{fr_subtype} set to @code{rs_machine_dependent} so |
| 1765 | that @code{md_convert_frag} will get called. |
| 1766 | |
| 1767 | @node General relaxing |
| 1768 | @subsection General relaxing |
| 1769 | |
| 1770 | If using a simple table is not suitable, you may implement arbitrarily complex |
| 1771 | relaxation semantics yourself. For example, the MIPS backend uses this to emit |
| 1772 | different instruction sequences depending upon the size of the symbol being |
| 1773 | accessed. |
| 1774 | |
| 1775 | When you assemble an instruction that may need relaxation, you should allocate |
| 1776 | a frag using @code{frag_var} or @code{frag_variant} with a type of |
| 1777 | @code{rs_machine_dependent}. You should store some sort of information in the |
| 1778 | @code{fr_subtype} field so that you can figure out what to do with the frag |
| 1779 | later. |
| 1780 | |
| 1781 | When GAS reaches the end of the input file, it will look through the frags and |
| 1782 | work out their final sizes. |
| 1783 | |
| 1784 | GAS will first call @code{md_estimate_size_before_relax} on each |
| 1785 | @code{rs_machine_dependent} frag. This function must return an estimated size |
| 1786 | for the frag. |
| 1787 | |
| 1788 | GAS will then loop over the frags, calling @code{md_relax_frag} on each |
| 1789 | @code{rs_machine_dependent} frag. This function should return the change in |
| 1790 | size of the frag. GAS will keep looping over the frags until none of the frags |
| 1791 | changes size. |
| 1792 | |
| 1793 | @node Broken words |
| 1794 | @section Broken words |
| 1795 | @cindex internals, broken words |
| 1796 | @cindex broken words |
| 1797 | |
| 1798 | Some compilers, including GCC, will sometimes emit switch tables specifying |
| 1799 | 16-bit @code{.word} displacements to branch targets, and branch instructions |
| 1800 | that load entries from that table to compute the target address. If this is |
| 1801 | done on a 32-bit machine, there is a chance (at least with really large |
| 1802 | functions) that the displacement will not fit in 16 bits. The assembler |
| 1803 | handles this using a concept called @dfn{broken words}. This idea is well |
| 1804 | named, since there is an implied promise that the 16-bit field will in fact |
| 1805 | hold the specified displacement. |
| 1806 | |
| 1807 | If broken word processing is enabled, and a situation like this is encountered, |
| 1808 | the assembler will insert a jump instruction into the instruction stream, close |
| 1809 | enough to be reached with the 16-bit displacement. This jump instruction will |
| 1810 | transfer to the real desired target address. Thus, as long as the @code{.word} |
| 1811 | value really is used as a displacement to compute an address to jump to, the |
| 1812 | net effect will be correct (minus a very small efficiency cost). If |
| 1813 | @code{.word} directives with label differences for values are used for other |
| 1814 | purposes, however, things may not work properly. For targets which use broken |
| 1815 | words, the @samp{-K} option will warn when a broken word is discovered. |
| 1816 | |
| 1817 | The broken word code is turned off by the @code{WORKING_DOT_WORD} macro. It |
| 1818 | isn't needed if @code{.word} emits a value large enough to contain an address |
| 1819 | (or, more correctly, any possible difference between two addresses). |
| 1820 | |
| 1821 | @node Internal functions |
| 1822 | @section Internal functions |
| 1823 | |
| 1824 | This section describes basic internal functions used by GAS. |
| 1825 | |
| 1826 | @menu |
| 1827 | * Warning and error messages:: Warning and error messages |
| 1828 | * Hash tables:: Hash tables |
| 1829 | @end menu |
| 1830 | |
| 1831 | @node Warning and error messages |
| 1832 | @subsection Warning and error messages |
| 1833 | |
| 1834 | @deftypefun @{@} int had_warnings (void) |
| 1835 | @deftypefunx @{@} int had_errors (void) |
| 1836 | Returns non-zero if any warnings or errors, respectively, have been printed |
| 1837 | during this invocation. |
| 1838 | @end deftypefun |
| 1839 | |
| 1840 | @deftypefun @{@} void as_perror (const char *@var{gripe}, const char *@var{filename}) |
| 1841 | Displays a BFD or system error, then clears the error status. |
| 1842 | @end deftypefun |
| 1843 | |
| 1844 | @deftypefun @{@} void as_tsktsk (const char *@var{format}, ...) |
| 1845 | @deftypefunx @{@} void as_warn (const char *@var{format}, ...) |
| 1846 | @deftypefunx @{@} void as_bad (const char *@var{format}, ...) |
| 1847 | @deftypefunx @{@} void as_fatal (const char *@var{format}, ...) |
| 1848 | These functions display messages about something amiss with the input file, or |
| 1849 | internal problems in the assembler itself. The current file name and line |
| 1850 | number are printed, followed by the supplied message, formatted using |
| 1851 | @code{vfprintf}, and a final newline. |
| 1852 | |
| 1853 | An error indicated by @code{as_bad} will result in a non-zero exit status when |
| 1854 | the assembler has finished. Calling @code{as_fatal} will result in immediate |
| 1855 | termination of the assembler process. |
| 1856 | @end deftypefun |
| 1857 | |
| 1858 | @deftypefun @{@} void as_warn_where (char *@var{file}, unsigned int @var{line}, const char *@var{format}, ...) |
| 1859 | @deftypefunx @{@} void as_bad_where (char *@var{file}, unsigned int @var{line}, const char *@var{format}, ...) |
| 1860 | These variants permit specification of the file name and line number, and are |
| 1861 | used when problems are detected when reprocessing information saved away when |
| 1862 | processing some earlier part of the file. For example, fixups are processed |
| 1863 | after all input has been read, but messages about fixups should refer to the |
| 1864 | original filename and line number that they are applicable to. |
| 1865 | @end deftypefun |
| 1866 | |
| 1867 | @deftypefun @{@} void fprint_value (FILE *@var{file}, valueT @var{val}) |
| 1868 | @deftypefunx @{@} void sprint_value (char *@var{buf}, valueT @var{val}) |
| 1869 | These functions are helpful for converting a @code{valueT} value into printable |
| 1870 | format, in case it's wider than modes that @code{*printf} can handle. If the |
| 1871 | type is narrow enough, a decimal number will be produced; otherwise, it will be |
| 1872 | in hexadecimal. The value itself is not examined to make this determination. |
| 1873 | @end deftypefun |
| 1874 | |
| 1875 | @node Hash tables |
| 1876 | @subsection Hash tables |
| 1877 | @cindex hash tables |
| 1878 | |
| 1879 | @deftypefun @{@} @{struct hash_control *@} hash_new (void) |
| 1880 | Creates the hash table control structure. |
| 1881 | @end deftypefun |
| 1882 | |
| 1883 | @deftypefun @{@} void hash_die (struct hash_control *) |
| 1884 | Destroy a hash table. |
| 1885 | @end deftypefun |
| 1886 | |
| 1887 | @deftypefun @{@} PTR hash_delete (struct hash_control *, const char *) |
| 1888 | Deletes entry from the hash table, returns the value it had. |
| 1889 | @end deftypefun |
| 1890 | |
| 1891 | @deftypefun @{@} PTR hash_replace (struct hash_control *, const char *, PTR) |
| 1892 | Updates the value for an entry already in the table, returning the old value. |
| 1893 | If no entry was found, just returns NULL. |
| 1894 | @end deftypefun |
| 1895 | |
| 1896 | @deftypefun @{@} @{const char *@} hash_insert (struct hash_control *, const char *, PTR) |
| 1897 | Inserting a value already in the table is an error. |
| 1898 | Returns an error message or NULL. |
| 1899 | @end deftypefun |
| 1900 | |
| 1901 | @deftypefun @{@} @{const char *@} hash_jam (struct hash_control *, const char *, PTR) |
| 1902 | Inserts if the value isn't already present, updates it if it is. |
| 1903 | @end deftypefun |
| 1904 | |
| 1905 | @node Test suite |
| 1906 | @section Test suite |
| 1907 | @cindex test suite |
| 1908 | |
| 1909 | The test suite is kind of lame for most processors. Often it only checks to |
| 1910 | see if a couple of files can be assembled without the assembler reporting any |
| 1911 | errors. For more complete testing, write a test which either examines the |
| 1912 | assembler listing, or runs @code{objdump} and examines its output. For the |
| 1913 | latter, the TCL procedure @code{run_dump_test} may come in handy. It takes the |
| 1914 | base name of a file, and looks for @file{@var{file}.d}. This file should |
| 1915 | contain as its initial lines a set of variable settings in @samp{#} comments, |
| 1916 | in the form: |
| 1917 | |
| 1918 | @example |
| 1919 | #@var{varname}: @var{value} |
| 1920 | @end example |
| 1921 | |
| 1922 | The @var{varname} may be @code{objdump}, @code{nm}, or @code{as}, in which case |
| 1923 | it specifies the options to be passed to the specified programs. Exactly one |
| 1924 | of @code{objdump} or @code{nm} must be specified, as that also specifies which |
| 1925 | program to run after the assembler has finished. If @var{varname} is |
| 1926 | @code{source}, it specifies the name of the source file; otherwise, |
| 1927 | @file{@var{file}.s} is used. If @var{varname} is @code{name}, it specifies the |
| 1928 | name of the test to be used in the @code{pass} or @code{fail} messages. |
| 1929 | |
| 1930 | The non-commented parts of the file are interpreted as regular expressions, one |
| 1931 | per line. Blank lines in the @code{objdump} or @code{nm} output are skipped, |
| 1932 | as are blank lines in the @code{.d} file; the other lines are tested to see if |
| 1933 | the regular expression matches the program output. If it does not, the test |
| 1934 | fails. |
| 1935 | |
| 1936 | Note that this means the tests must be modified if the @code{objdump} output |
| 1937 | style is changed. |
| 1938 | |
| 1939 | @bye |
| 1940 | @c Local Variables: |
| 1941 | @c fill-column: 79 |
| 1942 | @c End: |