diff -ruN binutils-2.28/bfd/ChangeLog binutils-2.28.1/bfd/ChangeLog --- binutils-2.28/bfd/ChangeLog 2017-03-02 09:55:49.000000000 +0100 +++ binutils-2.28.1/bfd/ChangeLog 2017-07-25 16:27:34.000000000 +0200 @@ -1,3 +1,153 @@ +2017-07-25 Tristan Gingold + + * version.m4: Bump version to 2.28.1 + * configure: Regenerate. + +2017-07-25 Tristan Gingold + + * development.sh: Set development to false. + +2017-06-22 Eric Christopher + + Backport from mainline + 2017-06-22 Eric Christopher + + * elf32-arm.c (elf32_arm_final_link_relocate): Use labs rather than + abs to fix a truncation warning. + +2017-06-20 Thomas Preud'homme + + Backport from mainline + 2017-05-08 Thomas Preud'homme + + * elflink.c (elf_output_implib): Remove executable flag from import + library bfd. + * elf32-arm.c (elf32_arm_filter_implib_symbols): Assert that the import + library is a relocatable object file. + +2017-06-13 Nick Clifton + + Import this fix from the mainline sources: + + 2017-06-06 James Clarke + + PR ld/19579 + * elfnn-aarch64.c (elfNN_aarch64_finish_dynamic_symbol): Check + ELF_COMMON_DEF_P for common symbols. + +2017-06-07 Nick Clifton + + Import this fix from upstream: + + 2017-05-30 Casey Smith + + PR ld/21523 + * elf32-arm.c (elf32_arm_final_link_relocate): Install an absolute + value when processing the R_ARM_THM_ALU_PREL_11_0 reloc. + +2017-06-05 Alan Modra + + PR 21529 + * linker.c (_bfd_generic_link_output_symbols): Handle BSF_GNU_UNIQUE. + +2017-05-01 Senthil Kumar Selvaraj + + PR ld/21404 + * elf32-avr.c (avr_should_move_sym): New function. + (avr_should_reduce_sym_size): Likewise. + (avr_should_increase_sym_size): Likewise. + (elf32_avr_relax_delete_bytes): Adjust symbol values + and sizes by calling new functions. + +2017-05-01 Palmer Dabbelt + + * config.bfd (riscv32-*): Enable rv64. + +2017-04-03 Palmer Dabbelt + + * elfnn-riscv.c (GP_NAME): Delete. + (riscv_global_pointer_value): Change GP_NAME to RISCV_GP_SYMBOL. + (_bfd_riscv_relax_lui): Likewise. + +2017-01-17 Kuan-Lin Chen + + * elfnn-riscv.c (riscv_elf_object_p): New function. + +2017-04-26 Maciej W. Rozycki + + PR ld/21334 + * elf-bfd.h (elf_backend_data): Add `always_renumber_dynsyms' + member. + * elfxx-target.h [!elf_backend_always_renumber_dynsyms] + (elf_backend_always_renumber_dynsyms): Define. + (elfNN_bed): Initialize `always_renumber_dynsyms' member. + * elfxx-mips.h (elf_backend_always_renumber_dynsyms): Define. + * elflink.c (bfd_elf_size_dynsym_hash_dynstr): Also call + `_bfd_elf_link_renumber_dynsyms' if the backend has requested + it. + (elf_gc_sweep): Likewise. + +2017-04-26 Maciej W. Rozycki + + * elflink.c (elf_gc_sweep): Only call + `_bfd_elf_link_renumber_dynsyms' if dynamic sections have been + created. + +2017-04-24 H.J. Lu + + PR ld/21425 + * elf32-i386.c (ELF_MAXPAGESIZE): Set to 0x1000 for VxWorks. + +2017-03-28 Hans-Peter Nilsson + + PR ld/16044 + * elf32-cris.c (elf_cris_adjust_gotplt_to_got): Adjust BFD_ASSERT + to handle a local symbol with a hash-symbol-entry; without PLT. + Add BFD_ASSERT for an incidental case with GOT entry present. + (cris_elf_check_relocs): Increment PLT refcount only if the symbol + isn't forced-or-set local. + +2017-04-13 Alan Modra + + * elf32-arm.c (arm_type_of_stub): Supply missing args to "long + branch veneers" error. Fix double space and format message. + * elf32-avr.c (avr_add_stub): Do not pass NULL as %B arg. + * elf64-ppc.c (tocsave_find): Supply missing %B arg. + +2017-04-10 H.J. Lu + + PR ld/19579 + PR ld/21306 + * elf32-s390.c (elf_s390_finish_dynamic_symbol): Check + ELF_COMMON_DEF_P for common symbols. + * elf64-s390.c (elf_s390_finish_dynamic_symbol): Likewise. + * elf64-x86-64.c (elf_x86_64_relocate_section): Likewise. + * elflink.c (_bfd_elf_merge_symbol): Revert commits + 202ac193bbbecc96a4978d1ac3d17148253f9b01 and + 07492f668d2173da7a2bda3707ff0985e0f460b6. + +2017-03-07 Alan Modra + + PR 21224 + PR 20519 + * elf64-ppc.c (ppc64_elf_relocate_section): Add missing + dyn_relocs check. + +2017-03-07 Alan Modra + + Apply from master + 2017-03-02 Alan Modra + * elf32-ppc.c (ppc_elf_vle_split16): Correct insn mask typo. + +2017-03-02 Tristan Gingold + + * version.m4: Bump version to 2.28.0 + * configure: Regenerate. + +2017-03-02 Tristan Gingold + + * development.sh: Set development to true. + 2017-03-02 Tristan Gingold * version.m4: Bump version to 2.28 diff -ruN binutils-2.28/bfd/config.bfd binutils-2.28.1/bfd/config.bfd --- binutils-2.28/bfd/config.bfd 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/config.bfd 2017-07-25 16:25:50.000000000 +0200 @@ -1439,10 +1439,9 @@ #ifdef BFD64 riscv32-*-*) targ_defvec=riscv_elf32_vec - targ_selvecs="riscv_elf32_vec" + targ_selvecs="riscv_elf32_vec riscv_elf64_vec" want64=true ;; - riscv64-*-*) targ_defvec=riscv_elf64_vec targ_selvecs="riscv_elf32_vec riscv_elf64_vec" diff -ruN binutils-2.28/bfd/configure binutils-2.28.1/bfd/configure --- binutils-2.28/bfd/configure 2017-03-02 09:55:49.000000000 +0100 +++ binutils-2.28.1/bfd/configure 2017-07-25 16:27:34.000000000 +0200 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.64 for bfd 2.28. +# Generated by GNU Autoconf 2.64 for bfd 2.28.1. # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, # 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software @@ -556,8 +556,8 @@ # Identity of this package. PACKAGE_NAME='bfd' PACKAGE_TARNAME='bfd' -PACKAGE_VERSION='2.28' -PACKAGE_STRING='bfd 2.28' +PACKAGE_VERSION='2.28.1' +PACKAGE_STRING='bfd 2.28.1' PACKAGE_BUGREPORT='' PACKAGE_URL='' @@ -1354,7 +1354,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures bfd 2.28 to adapt to many kinds of systems. +\`configure' configures bfd 2.28.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1425,7 +1425,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of bfd 2.28:";; + short | recursive ) echo "Configuration of bfd 2.28.1:";; esac cat <<\_ACEOF @@ -1546,7 +1546,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -bfd configure 2.28 +bfd configure 2.28.1 generated by GNU Autoconf 2.64 Copyright (C) 2009 Free Software Foundation, Inc. @@ -2188,7 +2188,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by bfd $as_me 2.28, which was +It was created by bfd $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was $ $0 $@ @@ -3997,7 +3997,7 @@ # Define the identity of the package. PACKAGE='bfd' - VERSION='2.28' + VERSION='2.28.1' cat >>confdefs.h <<_ACEOF @@ -16613,7 +16613,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by bfd $as_me 2.28, which was +This file was extended by bfd $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -16677,7 +16677,7 @@ _ACEOF cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_version="\\ -bfd config.status 2.28 +bfd config.status 2.28.1 configured by $0, generated by GNU Autoconf 2.64, with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" diff -ruN binutils-2.28/bfd/elf32-arm.c binutils-2.28.1/bfd/elf32-arm.c --- binutils-2.28/bfd/elf32-arm.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-arm.c 2017-07-25 16:25:50.000000000 +0200 @@ -4024,10 +4024,12 @@ if (!thumb_only) { if (input_sec->flags & SEC_ELF_PURECODE) - _bfd_error_handler (_("\ -%B(%A): warning: long branch veneers used in section with SHF_ARM_PURECODE section \ -attribute is only supported for M-profile targets that implement the movw instruction."), - input_sec); + _bfd_error_handler + (_("%B(%A): warning: long branch veneers used in" + " section with SHF_ARM_PURECODE section" + " attribute is only supported for M-profile" + " targets that implement the movw instruction."), + input_bfd, input_sec); stub_type = (bfd_link_pic (info) | globals->pic_veneer) /* PIC stubs. */ @@ -4056,10 +4058,12 @@ else { if (input_sec->flags & SEC_ELF_PURECODE) - _bfd_error_handler (_("\ -%B(%A): warning: long branch veneers used in section with SHF_ARM_PURECODE section \ -attribute is only supported for M-profile targets that implement the movw instruction."), - input_sec); + _bfd_error_handler + (_("%B(%A): warning: long branch veneers used in" + " section with SHF_ARM_PURECODE section" + " attribute is only supported for M-profile" + " targets that implement the movw instruction."), + input_bfd, input_sec); stub_type = (bfd_link_pic (info) | globals->pic_veneer) /* PIC stub. */ @@ -4073,13 +4077,12 @@ else { if (input_sec->flags & SEC_ELF_PURECODE) - _bfd_error_handler (_("%B(%s): warning: long branch " - " veneers used in section with " - "SHF_ARM_PURECODE section " - "attribute is only supported" - " for M-profile targets that " - "implement the movw " - "instruction.")); + _bfd_error_handler + (_("%B(%A): warning: long branch veneers used in" + " section with SHF_ARM_PURECODE section" + " attribute is only supported" " for M-profile" + " targets that implement the movw instruction."), + input_bfd, input_sec); /* Thumb to arm. */ if (sym_sec != NULL @@ -4126,13 +4129,12 @@ || r_type == R_ARM_TLS_CALL) { if (input_sec->flags & SEC_ELF_PURECODE) - _bfd_error_handler (_("%B(%s): warning: long branch " - " veneers used in section with " - "SHF_ARM_PURECODE section " - "attribute is only supported" - " for M-profile targets that " - "implement the movw " - "instruction.")); + _bfd_error_handler + (_("%B(%A): warning: long branch veneers used in" + " section with SHF_ARM_PURECODE section" + " attribute is only supported for M-profile" + " targets that implement the movw instruction."), + input_bfd, input_sec); if (branch_type == ST_BRANCH_TO_THUMB) { /* Arm to thumb. */ @@ -10503,7 +10505,9 @@ + input_section->output_offset + rel->r_offset); - value = relocation; + /* PR 21523: Use an absolute value. The user of this reloc will + have already selected an ADD or SUB insn appropriately. */ + value = labs (relocation); if (value >= 0x1000) return bfd_reloc_overflow; @@ -17496,6 +17500,10 @@ { struct elf32_arm_link_hash_table *globals = elf32_arm_hash_table (info); + /* Requirement 8 of "ARM v8-M Security Extensions: Requirements on + Development Tools" (ARM-ECM-0359818) mandates Secure Gateway import + library to be a relocatable object file. */ + BFD_ASSERT (!(bfd_get_file_flags (info->out_implib_bfd) & EXEC_P)); if (globals->cmse_implib) return elf32_arm_filter_cmse_symbols (abfd, info, syms, symcount); else diff -ruN binutils-2.28/bfd/elf32-avr.c binutils-2.28.1/bfd/elf32-avr.c --- binutils-2.28/bfd/elf32-avr.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-avr.c 2017-07-25 16:25:50.000000000 +0200 @@ -1854,6 +1854,40 @@ } } +static bfd_boolean +avr_should_move_sym (symvalue symval, + bfd_vma start, + bfd_vma end, + bfd_boolean did_pad) +{ + bfd_boolean sym_within_boundary = + did_pad ? symval < end : symval <= end; + return (symval > start && sym_within_boundary); +} + +static bfd_boolean +avr_should_reduce_sym_size (symvalue symval, + symvalue symend, + bfd_vma start, + bfd_vma end, + bfd_boolean did_pad) +{ + bfd_boolean sym_end_within_boundary = + did_pad ? symend < end : symend <= end; + return (symval <= start && symend > start && sym_end_within_boundary); +} + +static bfd_boolean +avr_should_increase_sym_size (symvalue symval, + symvalue symend, + bfd_vma start, + bfd_vma end, + bfd_boolean did_pad) +{ + return avr_should_move_sym (symval, start, end, did_pad) + && symend >= end && did_pad; +} + /* Delete some bytes from a section while changing the size of an instruction. The parameter "addr" denotes the section-relative offset pointing just behind the shrinked instruction. "addr+count" point at the first @@ -1875,13 +1909,14 @@ Elf_Internal_Rela *irel, *irelend; Elf_Internal_Sym *isym; Elf_Internal_Sym *isymbuf = NULL; - bfd_vma toaddr, reloc_toaddr; + bfd_vma toaddr; struct elf_link_hash_entry **sym_hashes; struct elf_link_hash_entry **end_hashes; unsigned int symcount; struct avr_relax_info *relax_info; struct avr_property_record *prop_record = NULL; bfd_boolean did_shrink = FALSE; + bfd_boolean did_pad = FALSE; symtab_hdr = &elf_tdata (abfd)->symtab_hdr; sec_shndx = _bfd_elf_section_from_bfd_section (abfd, sec); @@ -1912,17 +1947,6 @@ } } - /* We need to look at all relocs with offsets less than toaddr. prop - records handling adjusts toaddr downwards to avoid moving syms at the - address of the property record, but all relocs with offsets between addr - and the current value of toaddr need to have their offsets adjusted. - Assume addr = 0, toaddr = 4 and count = 2. After prop records handling, - toaddr becomes 2, but relocs with offsets 2 and 3 still need to be - adjusted (to 0 and 1 respectively), as the first 2 bytes are now gone. - So record the current value of toaddr here, and use it when adjusting - reloc offsets. */ - reloc_toaddr = toaddr; - irel = elf_section_data (sec)->relocs; irelend = irel + sec->reloc_count; @@ -1962,10 +1986,7 @@ to remember we didn't delete anything i.e. don't set did_shrink, so that we don't corrupt reloc offsets or symbol values.*/ memset (contents + toaddr - count, fill, count); - - /* Adjust the TOADDR to avoid moving symbols located at the address - of the property record, which has not moved. */ - toaddr -= count; + did_pad = TRUE; } if (!did_shrink) @@ -1981,7 +2002,7 @@ /* Get the new reloc address. */ if ((irel->r_offset > addr - && irel->r_offset < reloc_toaddr)) + && irel->r_offset < toaddr)) { if (debug_relax) printf ("Relocation at address 0x%x needs to be moved.\n" @@ -2059,7 +2080,7 @@ { /* If there is an alignment boundary, we only need to adjust addends that end up below the boundary. */ - bfd_vma shrink_boundary = (reloc_toaddr + bfd_vma shrink_boundary = (toaddr + sec->output_section->vma + sec->output_offset); @@ -2102,12 +2123,10 @@ { if (isym->st_shndx == sec_shndx) { - if (isym->st_value > addr - && isym->st_value <= toaddr) - isym->st_value -= count; - - if (isym->st_value <= addr - && isym->st_value + isym->st_size > addr) + symvalue symval = isym->st_value; + symvalue symend = symval + isym->st_size; + if (avr_should_reduce_sym_size (symval, symend, + addr, toaddr, did_pad)) { /* If this assert fires then we have a symbol that ends part way through an instruction. Does that make @@ -2115,6 +2134,12 @@ BFD_ASSERT (isym->st_value + isym->st_size >= addr + count); isym->st_size -= count; } + else if (avr_should_increase_sym_size (symval, symend, + addr, toaddr, did_pad)) + isym->st_size += count; + + if (avr_should_move_sym (symval, addr, toaddr, did_pad)) + isym->st_value -= count; } } } @@ -2131,20 +2156,24 @@ || sym_hash->root.type == bfd_link_hash_defweak) && sym_hash->root.u.def.section == sec) { - if (sym_hash->root.u.def.value > addr - && sym_hash->root.u.def.value <= toaddr) - sym_hash->root.u.def.value -= count; + symvalue symval = sym_hash->root.u.def.value; + symvalue symend = symval + sym_hash->size; - if (sym_hash->root.u.def.value <= addr - && (sym_hash->root.u.def.value + sym_hash->size > addr)) + if (avr_should_reduce_sym_size (symval, symend, + addr, toaddr, did_pad)) { /* If this assert fires then we have a symbol that ends part way through an instruction. Does that make sense? */ - BFD_ASSERT (sym_hash->root.u.def.value + sym_hash->size - >= addr + count); + BFD_ASSERT (symend >= addr + count); sym_hash->size -= count; } + else if (avr_should_increase_sym_size (symval, symend, + addr, toaddr, did_pad)) + sym_hash->size += count; + + if (avr_should_move_sym (symval, addr, toaddr, did_pad)) + sym_hash->root.u.def.value -= count; } } @@ -3284,8 +3313,7 @@ if (hsh == NULL) { /* xgettext:c-format */ - _bfd_error_handler (_("%B: cannot create stub entry %s"), - NULL, stub_name); + _bfd_error_handler (_("cannot create stub entry %s"), stub_name); return NULL; } diff -ruN binutils-2.28/bfd/elf32-cris.c binutils-2.28.1/bfd/elf32-cris.c --- binutils-2.28/bfd/elf32-cris.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-cris.c 2017-07-25 16:25:50.000000000 +0200 @@ -2714,8 +2714,9 @@ struct bfd_link_info *info = (struct bfd_link_info *) p; /* A GOTPLT reloc, when activated, is supposed to be included into - the PLT refcount. */ + the PLT refcount, when the symbol isn't set-or-forced local. */ BFD_ASSERT (h->gotplt_refcount == 0 + || h->root.plt.refcount == -1 || h->gotplt_refcount <= h->root.plt.refcount); /* If nobody wanted a GOTPLT with this symbol, we're done. */ @@ -2741,6 +2742,7 @@ srelgot = elf_hash_table (info)->srelgot; /* Put accurate refcounts there. */ + BFD_ASSERT (h->root.got.refcount >= 0); h->root.got.refcount += h->gotplt_refcount; h->reg_got_refcount = h->gotplt_refcount; @@ -3476,7 +3478,10 @@ continue; h->needs_plt = 1; - h->plt.refcount++; + + /* If the symbol is forced local, the refcount is unavailable. */ + if (h->plt.refcount != -1) + h->plt.refcount++; break; case R_CRIS_8: diff -ruN binutils-2.28/bfd/elf32-i386.c binutils-2.28.1/bfd/elf32-i386.c --- binutils-2.28/bfd/elf32-i386.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-i386.c 2017-07-25 16:25:50.000000000 +0200 @@ -6576,6 +6576,8 @@ #undef TARGET_LITTLE_NAME #define TARGET_LITTLE_NAME "elf32-i386-vxworks" #undef ELF_OSABI +#undef ELF_MAXPAGESIZE +#define ELF_MAXPAGESIZE 0x1000 #undef elf_backend_plt_alignment #define elf_backend_plt_alignment 4 diff -ruN binutils-2.28/bfd/elf32-ppc.c binutils-2.28.1/bfd/elf32-ppc.c --- binutils-2.28/bfd/elf32-ppc.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-ppc.c 2017-07-25 16:25:50.000000000 +0200 @@ -4921,7 +4921,7 @@ unsigned int insn, opcode, top5; insn = bfd_get_32 (input_bfd, loc); - opcode = insn & 0xf300f800; + opcode = insn & 0xfc00f800; if (opcode == E_OR2I_INSN || opcode == E_AND2I_DOT_INSN || opcode == E_OR2IS_INSN diff -ruN binutils-2.28/bfd/elf32-s390.c binutils-2.28.1/bfd/elf32-s390.c --- binutils-2.28/bfd/elf32-s390.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf32-s390.c 2017-07-25 16:25:50.000000000 +0200 @@ -3785,7 +3785,7 @@ RELATIVE reloc. The entry in the global offset table will already have been initialized in the relocate_section function. */ - if (!h->def_regular) + if (!(h->def_regular || ELF_COMMON_DEF_P (h))) return FALSE; BFD_ASSERT((h->got.offset & 1) != 0); rela.r_info = ELF32_R_INFO (0, R_390_RELATIVE); diff -ruN binutils-2.28/bfd/elf64-ppc.c binutils-2.28.1/bfd/elf64-ppc.c --- binutils-2.28/bfd/elf64-ppc.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf64-ppc.c 2017-07-25 16:25:50.000000000 +0200 @@ -7627,7 +7627,7 @@ if (ent.sec == NULL || ent.sec->output_section == NULL) { _bfd_error_handler - (_("%B: undefined symbol on R_PPC64_TOCSAVE relocation")); + (_("%B: undefined symbol on R_PPC64_TOCSAVE relocation"), ibfd); return NULL; } @@ -14798,8 +14798,10 @@ break; if (bfd_link_pic (info) - ? ((h != NULL && pc_dynrelocs (h)) - || must_be_dyn_reloc (info, r_type)) + ? ((h == NULL + || h->dyn_relocs != NULL) + && ((h != NULL && pc_dynrelocs (h)) + || must_be_dyn_reloc (info, r_type))) : (h != NULL ? h->dyn_relocs != NULL : ELF_ST_TYPE (sym->st_info) == STT_GNU_IFUNC)) diff -ruN binutils-2.28/bfd/elf64-s390.c binutils-2.28.1/bfd/elf64-s390.c --- binutils-2.28/bfd/elf64-s390.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf64-s390.c 2017-07-25 16:25:50.000000000 +0200 @@ -3582,7 +3582,7 @@ RELATIVE reloc. The entry in the global offset table will already have been initialized in the relocate_section function. */ - if (!h->def_regular) + if (!(h->def_regular || ELF_COMMON_DEF_P (h))) return FALSE; BFD_ASSERT((h->got.offset & 1) != 0); rela.r_info = ELF64_R_INFO (0, R_390_RELATIVE); diff -ruN binutils-2.28/bfd/elf64-x86-64.c binutils-2.28.1/bfd/elf64-x86-64.c --- binutils-2.28/bfd/elf64-x86-64.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf64-x86-64.c 2017-07-25 16:25:50.000000000 +0200 @@ -4926,7 +4926,8 @@ { /* Symbol is referenced locally. Make sure it is defined locally or for a branch. */ - fail = !h->def_regular && !branch; + fail = (!(h->def_regular || ELF_COMMON_DEF_P (h)) + && !branch); } else if (!(bfd_link_pie (info) && (h->needs_copy || eh->needs_copy))) diff -ruN binutils-2.28/bfd/elf-bfd.h binutils-2.28.1/bfd/elf-bfd.h --- binutils-2.28/bfd/elf-bfd.h 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elf-bfd.h 2017-07-25 16:25:50.000000000 +0200 @@ -1478,6 +1478,10 @@ /* Address of protected data defined in the shared library may be external, i.e., due to copy relocation. */ unsigned extern_protected_data : 1; + + /* True if `_bfd_elf_link_renumber_dynsyms' must be called even for + static binaries. */ + unsigned always_renumber_dynsyms : 1; }; /* Information about reloc sections associated with a bfd_elf_section_data diff -ruN binutils-2.28/bfd/elflink.c binutils-2.28.1/bfd/elflink.c --- binutils-2.28/bfd/elflink.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elflink.c 2017-07-25 16:25:50.000000000 +0200 @@ -1543,16 +1543,13 @@ represent variables; this can cause confusion in principle, but any such confusion would seem to indicate an erroneous program or shared library. We also permit a common symbol in a regular - object to override a weak symbol in a shared object. A common - symbol in executable also overrides a symbol in a shared object. */ + object to override a weak symbol in a shared object. */ if (newdyn && newdef && (olddef || (h->root.type == bfd_link_hash_common - && (newweak - || newfunc - || (!olddyn && bfd_link_executable (info)))))) + && (newweak || newfunc)))) { *override = TRUE; newdef = FALSE; @@ -6710,6 +6707,8 @@ bfd_elf_size_dynsym_hash_dynstr (bfd *output_bfd, struct bfd_link_info *info) { const struct elf_backend_data *bed; + unsigned long section_sym_count; + bfd_size_type dynsymcount; if (!is_elf_hash_table (info->hash)) return TRUE; @@ -6717,24 +6716,30 @@ bed = get_elf_backend_data (output_bfd); (*bed->elf_backend_init_index_section) (output_bfd, info); + /* Assign dynsym indices. In a shared library we generate a section + symbol for each output section, which come first. Next come all + of the back-end allocated local dynamic syms, followed by the rest + of the global symbols. + + This is usually not needed for static binaries, however backends + can request to always do it, e.g. the MIPS backend uses dynamic + symbol counts to lay out GOT, which will be produced in the + presence of GOT relocations even in static binaries (holding fixed + data in that case, to satisfy those relocations). */ + + if (elf_hash_table (info)->dynamic_sections_created + || bed->always_renumber_dynsyms) + dynsymcount = _bfd_elf_link_renumber_dynsyms (output_bfd, info, + §ion_sym_count); + if (elf_hash_table (info)->dynamic_sections_created) { bfd *dynobj; asection *s; - bfd_size_type dynsymcount; - unsigned long section_sym_count; unsigned int dtagcount; dynobj = elf_hash_table (info)->dynobj; - /* Assign dynsym indicies. In a shared library we generate a - section symbol for each output section, which come first. - Next come all of the back-end allocated local dynamic syms, - followed by the rest of the global symbols. */ - - dynsymcount = _bfd_elf_link_renumber_dynsyms (output_bfd, info, - §ion_sym_count); - /* Work out the size of the symbol version section. */ s = bfd_get_linker_section (dynobj, ".gnu.version"); BFD_ASSERT (s != NULL); @@ -11141,10 +11146,11 @@ if (!bfd_set_format (implib_bfd, bfd_object)) return FALSE; + /* Use flag from executable but make it a relocatable object. */ flags = bfd_get_file_flags (abfd); flags &= ~HAS_RELOC; if (!bfd_set_start_address (implib_bfd, 0) - || !bfd_set_file_flags (implib_bfd, flags)) + || !bfd_set_file_flags (implib_bfd, flags & ~EXEC_P)) return FALSE; /* Copy architecture of output file to import library file. */ @@ -12986,7 +12992,12 @@ elf_link_hash_traverse (elf_hash_table (info), elf_gc_sweep_symbol, &sweep_info); - _bfd_elf_link_renumber_dynsyms (abfd, info, §ion_sym_count); + /* We need to reassign dynsym indices now that symbols may have + been removed. See the call in `bfd_elf_size_dynsym_hash_dynstr' + for the details of the conditions used here. */ + if (elf_hash_table (info)->dynamic_sections_created + || bed->always_renumber_dynsyms) + _bfd_elf_link_renumber_dynsyms (abfd, info, §ion_sym_count); return TRUE; } diff -ruN binutils-2.28/bfd/elfnn-aarch64.c binutils-2.28.1/bfd/elfnn-aarch64.c --- binutils-2.28/bfd/elfnn-aarch64.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elfnn-aarch64.c 2017-07-25 16:25:50.000000000 +0200 @@ -8903,7 +8903,7 @@ } else if (bfd_link_pic (info) && SYMBOL_REFERENCES_LOCAL (info, h)) { - if (!h->def_regular) + if (!(h->def_regular || ELF_COMMON_DEF_P (h))) return FALSE; BFD_ASSERT ((h->got.offset & 1) != 0); diff -ruN binutils-2.28/bfd/elfnn-riscv.c binutils-2.28.1/bfd/elfnn-riscv.c --- binutils-2.28/bfd/elfnn-riscv.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elfnn-riscv.c 2017-07-25 16:25:50.000000000 +0200 @@ -52,10 +52,6 @@ #define ELF_MAXPAGESIZE 0x1000 #define ELF_COMMONPAGESIZE 0x1000 -/* The global pointer's symbol name. */ - -#define GP_NAME "__global_pointer$" - /* The RISC-V linker needs to keep track of the number of relocs that it decides to copy as dynamic relocs in check_relocs for each symbol. This is so that it can later discard them if they are found to be @@ -1467,7 +1463,7 @@ { struct bfd_link_hash_entry *h; - h = bfd_link_hash_lookup (info->hash, GP_NAME, FALSE, FALSE, TRUE); + h = bfd_link_hash_lookup (info->hash, RISCV_GP_SYMBOL, FALSE, FALSE, TRUE); if (h == NULL || h->type != bfd_link_hash_defined) return 0; @@ -2818,7 +2814,8 @@ /* If gp and the symbol are in the same output section, then consider only that section's alignment. */ struct bfd_link_hash_entry *h = - bfd_link_hash_lookup (link_info->hash, GP_NAME, FALSE, FALSE, TRUE); + bfd_link_hash_lookup (link_info->hash, RISCV_GP_SYMBOL, FALSE, FALSE, + TRUE); if (h->u.def.section->output_section == sym_sec->output_section) max_alignment = (bfd_vma) 1 << sym_sec->output_section->alignment_power; } @@ -3205,6 +3202,19 @@ return TRUE; } +/* Set the right mach type. */ +static bfd_boolean +riscv_elf_object_p (bfd *abfd) +{ + /* There are only two mach types in RISCV currently. */ + if (strcmp (abfd->xvec->name, "elf32-littleriscv") == 0) + bfd_default_set_arch_mach (abfd, bfd_arch_riscv, bfd_mach_riscv32); + else + bfd_default_set_arch_mach (abfd, bfd_arch_riscv, bfd_mach_riscv64); + + return TRUE; +} + #define TARGET_LITTLE_SYM riscv_elfNN_vec #define TARGET_LITTLE_NAME "elfNN-littleriscv" @@ -3230,6 +3240,7 @@ #define elf_backend_plt_sym_val riscv_elf_plt_sym_val #define elf_backend_grok_prstatus riscv_elf_grok_prstatus #define elf_backend_grok_psinfo riscv_elf_grok_psinfo +#define elf_backend_object_p riscv_elf_object_p #define elf_info_to_howto_rel NULL #define elf_info_to_howto riscv_info_to_howto_rela #define bfd_elfNN_bfd_relax_section _bfd_riscv_relax_section diff -ruN binutils-2.28/bfd/elfxx-mips.h binutils-2.28.1/bfd/elfxx-mips.h --- binutils-2.28/bfd/elfxx-mips.h 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elfxx-mips.h 2017-07-25 16:25:50.000000000 +0200 @@ -196,3 +196,4 @@ #define elf_backend_post_process_headers _bfd_mips_post_process_headers #define elf_backend_compact_eh_encoding _bfd_mips_elf_compact_eh_encoding #define elf_backend_cant_unwind_opcode _bfd_mips_elf_cant_unwind_opcode +#define elf_backend_always_renumber_dynsyms TRUE diff -ruN binutils-2.28/bfd/elfxx-target.h binutils-2.28.1/bfd/elfxx-target.h --- binutils-2.28/bfd/elfxx-target.h 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/elfxx-target.h 2017-07-25 16:25:50.000000000 +0200 @@ -126,6 +126,9 @@ #ifndef elf_backend_extern_protected_data #define elf_backend_extern_protected_data 0 #endif +#ifndef elf_backend_always_renumber_dynsyms +#define elf_backend_always_renumber_dynsyms FALSE +#endif #ifndef elf_backend_stack_align #define elf_backend_stack_align 16 #endif @@ -866,7 +869,8 @@ elf_backend_no_page_alias, elf_backend_default_execstack, elf_backend_caches_rawsize, - elf_backend_extern_protected_data + elf_backend_extern_protected_data, + elf_backend_always_renumber_dynsyms }; /* Forward declaration for use when initialising alternative_target field. */ diff -ruN binutils-2.28/bfd/linker.c binutils-2.28.1/bfd/linker.c --- binutils-2.28/bfd/linker.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/linker.c 2017-07-25 16:25:50.000000000 +0200 @@ -2091,7 +2091,7 @@ && bfd_hash_lookup (info->keep_hash, bfd_asymbol_name (sym), FALSE, FALSE) == NULL)) output = FALSE; - else if ((sym->flags & (BSF_GLOBAL | BSF_WEAK)) != 0) + else if ((sym->flags & (BSF_GLOBAL | BSF_WEAK | BSF_GNU_UNIQUE)) != 0) { /* If this symbol is marked as occurring now, rather than at the end, output it now. This is used for diff -ruN binutils-2.28/bfd/version.h binutils-2.28.1/bfd/version.h --- binutils-2.28/bfd/version.h 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/bfd/version.h 2017-07-25 16:25:50.000000000 +0200 @@ -1,4 +1,4 @@ -#define BFD_VERSION_DATE 20170302 +#define BFD_VERSION_DATE 20170706 #define BFD_VERSION @bfd_version@ #define BFD_VERSION_STRING @bfd_version_package@ @bfd_version_string@ #define REPORT_BUGS_TO @report_bugs_to@ diff -ruN binutils-2.28/bfd/version.m4 binutils-2.28.1/bfd/version.m4 --- binutils-2.28/bfd/version.m4 2017-03-02 09:55:47.000000000 +0100 +++ binutils-2.28.1/bfd/version.m4 2017-07-25 16:27:33.000000000 +0200 @@ -1 +1 @@ -m4_define([BFD_VERSION], [2.28]) +m4_define([BFD_VERSION], [2.28.1]) diff -ruN binutils-2.28/binutils/ChangeLog binutils-2.28.1/binutils/ChangeLog --- binutils-2.28/binutils/ChangeLog 2017-03-02 09:55:51.000000000 +0100 +++ binutils-2.28.1/binutils/ChangeLog 2017-07-25 16:27:35.000000000 +0200 @@ -1,3 +1,19 @@ +2017-07-25 Tristan Gingold + + * configure: Regenerate. + +2017-05-18 Alan Modra + + Apply from master + 2017-01-10 Nick Clifton + PR 21034 + * stabs.c (parse_stab_members): Fix thinko checking for g++ + version 1 stabs information. + +2017-03-02 Tristan Gingold + + * configure: Regenerate. + 2017-03-02 Tristan Gingold * configure: Regenerate. diff -ruN binutils-2.28/binutils/configure binutils-2.28.1/binutils/configure --- binutils-2.28/binutils/configure 2017-03-02 09:55:51.000000000 +0100 +++ binutils-2.28.1/binutils/configure 2017-07-25 16:27:35.000000000 +0200 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.64 for binutils 2.28. +# Generated by GNU Autoconf 2.64 for binutils 2.28.1. # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, # 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software @@ -556,8 +556,8 @@ # Identity of this package. PACKAGE_NAME='binutils' PACKAGE_TARNAME='binutils' -PACKAGE_VERSION='2.28' -PACKAGE_STRING='binutils 2.28' +PACKAGE_VERSION='2.28.1' +PACKAGE_STRING='binutils 2.28.1' PACKAGE_BUGREPORT='' PACKAGE_URL='' @@ -1338,7 +1338,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures binutils 2.28 to adapt to many kinds of systems. +\`configure' configures binutils 2.28.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1409,7 +1409,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of binutils 2.28:";; + short | recursive ) echo "Configuration of binutils 2.28.1:";; esac cat <<\_ACEOF @@ -1530,7 +1530,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -binutils configure 2.28 +binutils configure 2.28.1 generated by GNU Autoconf 2.64 Copyright (C) 2009 Free Software Foundation, Inc. @@ -2172,7 +2172,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by binutils $as_me 2.28, which was +It was created by binutils $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was $ $0 $@ @@ -3981,7 +3981,7 @@ # Define the identity of the package. PACKAGE='binutils' - VERSION='2.28' + VERSION='2.28.1' cat >>confdefs.h <<_ACEOF @@ -15223,7 +15223,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by binutils $as_me 2.28, which was +This file was extended by binutils $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -15287,7 +15287,7 @@ _ACEOF cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_version="\\ -binutils config.status 2.28 +binutils config.status 2.28.1 configured by $0, generated by GNU Autoconf 2.64, with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" diff -ruN binutils-2.28/binutils/doc/addr2line.1 binutils-2.28.1/binutils/doc/addr2line.1 --- binutils-2.28/binutils/doc/addr2line.1 2017-03-02 09:59:34.000000000 +0100 +++ binutils-2.28.1/binutils/doc/addr2line.1 2017-07-25 16:29:31.000000000 +0200 @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) +.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29) .\" .\" Standard preamble: .\" ======================================================================== @@ -133,7 +133,7 @@ .\" ======================================================================== .\" .IX Title "ADDR2LINE 1" -.TH ADDR2LINE 1 "2017-03-02" "binutils-2.28" "GNU Development Tools" +.TH ADDR2LINE 1 "2017-07-25" "binutils-2.28.1" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -ruN binutils-2.28/binutils/doc/ar.1 binutils-2.28.1/binutils/doc/ar.1 --- binutils-2.28/binutils/doc/ar.1 2017-03-02 09:59:34.000000000 +0100 +++ binutils-2.28.1/binutils/doc/ar.1 2017-07-25 16:29:32.000000000 +0200 @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) +.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29) .\" .\" Standard preamble: .\" ======================================================================== @@ -133,7 +133,7 @@ .\" ======================================================================== .\" .IX Title "AR 1" -.TH AR 1 "2017-03-02" "binutils-2.28" "GNU Development Tools" +.TH AR 1 "2017-07-25" "binutils-2.28.1" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l diff -ruN binutils-2.28/binutils/stabs.c binutils-2.28.1/binutils/stabs.c --- binutils-2.28/binutils/stabs.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/binutils/stabs.c 2017-07-25 16:25:50.000000000 +0200 @@ -2702,7 +2702,7 @@ ++*pp; voffset &= 0x7fffffff; - if (**pp == ';' || *pp == '\0') + if (**pp == ';' || **pp == '\0') { /* Must be g++ version 1. */ context = DEBUG_TYPE_NULL; diff -ruN binutils-2.28/binutils/sysinfo.c binutils-2.28.1/binutils/sysinfo.c --- binutils-2.28/binutils/sysinfo.c 2017-03-02 09:59:33.000000000 +0100 +++ binutils-2.28.1/binutils/sysinfo.c 2017-07-25 16:29:31.000000000 +0200 @@ -1,8 +1,8 @@ -/* A Bison parser, made by GNU Bison 3.0. */ +/* A Bison parser, made by GNU Bison 3.0.4. */ /* Bison implementation for Yacc-like parsers in C - Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc. + Copyright (C) 1984, 1989-1990, 2000-2015 Free Software Foundation, Inc. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -44,7 +44,7 @@ #define YYBISON 1 /* Bison version. */ -#define YYBISON_VERSION "3.0" +#define YYBISON_VERSION "3.0.4" /* Skeleton name. */ #define YYSKELETON_NAME "yacc.c" @@ -82,11 +82,11 @@ #line 84 "sysinfo.c" /* yacc.c:339 */ -# ifndef YY_NULL +# ifndef YY_NULLPTR # if defined __cplusplus && 201103L <= __cplusplus -# define YY_NULL nullptr +# define YY_NULLPTR nullptr # else -# define YY_NULL 0 +# define YY_NULLPTR 0 # endif # endif @@ -133,7 +133,7 @@ /* Value type. */ #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED -typedef union YYSTYPE YYSTYPE; + union YYSTYPE { #line 40 "sysinfo.y" /* yacc.c:355 */ @@ -143,6 +143,8 @@ #line 145 "sysinfo.c" /* yacc.c:355 */ }; + +typedef union YYSTYPE YYSTYPE; # define YYSTYPE_IS_TRIVIAL 1 # define YYSTYPE_IS_DECLARED 1 #endif @@ -156,7 +158,7 @@ /* Copy the second part of user declarations. */ -#line 160 "sysinfo.c" /* yacc.c:358 */ +#line 162 "sysinfo.c" /* yacc.c:358 */ #ifdef short # undef short @@ -213,11 +215,30 @@ # endif #endif -#ifndef __attribute__ -/* This feature is available in gcc versions 2.5 and later. */ -# if (! defined __GNUC__ || __GNUC__ < 2 \ - || (__GNUC__ == 2 && __GNUC_MINOR__ < 5)) -# define __attribute__(Spec) /* empty */ +#ifndef YY_ATTRIBUTE +# if (defined __GNUC__ \ + && (2 < __GNUC__ || (__GNUC__ == 2 && 96 <= __GNUC_MINOR__))) \ + || defined __SUNPRO_C && 0x5110 <= __SUNPRO_C +# define YY_ATTRIBUTE(Spec) __attribute__(Spec) +# else +# define YY_ATTRIBUTE(Spec) /* empty */ +# endif +#endif + +#ifndef YY_ATTRIBUTE_PURE +# define YY_ATTRIBUTE_PURE YY_ATTRIBUTE ((__pure__)) +#endif + +#ifndef YY_ATTRIBUTE_UNUSED +# define YY_ATTRIBUTE_UNUSED YY_ATTRIBUTE ((__unused__)) +#endif + +#if !defined _Noreturn \ + && (!defined __STDC_VERSION__ || __STDC_VERSION__ < 201112) +# if defined _MSC_VER && 1200 <= _MSC_VER +# define _Noreturn __declspec (noreturn) +# else +# define _Noreturn YY_ATTRIBUTE ((__noreturn__)) # endif #endif @@ -450,7 +471,7 @@ "NAME", "NUMBER", "UNIT", "$accept", "top", "$@1", "it_list", "it", "$@2", "it_field_list", "repeat_it_field", "$@3", "cond_it_field", "$@4", "it_field", "$@5", "attr_type", "attr_desc", "attr_size", "attr_id", - "enums", "enum_list", YY_NULL + "enums", "enum_list", YY_NULLPTR }; #endif @@ -841,11 +862,11 @@ yysyntax_error (YYSIZE_T *yymsg_alloc, char **yymsg, yytype_int16 *yyssp, int yytoken) { - YYSIZE_T yysize0 = yytnamerr (YY_NULL, yytname[yytoken]); + YYSIZE_T yysize0 = yytnamerr (YY_NULLPTR, yytname[yytoken]); YYSIZE_T yysize = yysize0; enum { YYERROR_VERBOSE_ARGS_MAXIMUM = 5 }; /* Internationalized format string. */ - const char *yyformat = YY_NULL; + const char *yyformat = YY_NULLPTR; /* Arguments of yyformat. */ char const *yyarg[YYERROR_VERBOSE_ARGS_MAXIMUM]; /* Number of reported tokens (one for the "unexpected", one per @@ -902,7 +923,7 @@ } yyarg[yycount++] = yytname[yyx]; { - YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULL, yytname[yyx]); + YYSIZE_T yysize1 = yysize + yytnamerr (YY_NULLPTR, yytname[yyx]); if (! (yysize <= yysize1 && yysize1 <= YYSTACK_ALLOC_MAXIMUM)) return 2; @@ -1234,7 +1255,7 @@ switch (yyn) { case 2: -#line 54 "sysinfo.y" /* yacc.c:1661 */ +#line 54 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { @@ -1257,11 +1278,11 @@ break; } } -#line 1261 "sysinfo.c" /* yacc.c:1661 */ +#line 1282 "sysinfo.c" /* yacc.c:1646 */ break; case 3: -#line 76 "sysinfo.y" /* yacc.c:1661 */ +#line 76 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { case 'i': @@ -1274,11 +1295,11 @@ break; } } -#line 1278 "sysinfo.c" /* yacc.c:1661 */ +#line 1299 "sysinfo.c" /* yacc.c:1646 */ break; case 6: -#line 98 "sysinfo.y" /* yacc.c:1661 */ +#line 98 "sysinfo.y" /* yacc.c:1646 */ { it = (yyvsp[-1].s); code = (yyvsp[0].i); switch (writecode) @@ -1328,11 +1349,11 @@ } } -#line 1332 "sysinfo.c" /* yacc.c:1661 */ +#line 1353 "sysinfo.c" /* yacc.c:1646 */ break; case 7: -#line 149 "sysinfo.y" /* yacc.c:1661 */ +#line 149 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { case 'd': @@ -1347,11 +1368,11 @@ printf("}\n"); } } -#line 1351 "sysinfo.c" /* yacc.c:1661 */ +#line 1372 "sysinfo.c" /* yacc.c:1646 */ break; case 12: -#line 175 "sysinfo.y" /* yacc.c:1661 */ +#line 175 "sysinfo.y" /* yacc.c:1646 */ { rdepth++; switch (writecode) @@ -1380,11 +1401,11 @@ oldrepeat = repeat; repeat = (yyvsp[0].s); } -#line 1384 "sysinfo.c" /* yacc.c:1661 */ +#line 1405 "sysinfo.c" /* yacc.c:1646 */ break; case 13: -#line 206 "sysinfo.y" /* yacc.c:1661 */ +#line 206 "sysinfo.y" /* yacc.c:1646 */ { repeat = oldrepeat; oldrepeat =0; @@ -1398,11 +1419,11 @@ printf("\t}}\n"); } } -#line 1402 "sysinfo.c" /* yacc.c:1661 */ +#line 1423 "sysinfo.c" /* yacc.c:1646 */ break; case 14: -#line 223 "sysinfo.y" /* yacc.c:1661 */ +#line 223 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { @@ -1414,11 +1435,11 @@ break; } } -#line 1418 "sysinfo.c" /* yacc.c:1661 */ +#line 1439 "sysinfo.c" /* yacc.c:1646 */ break; case 15: -#line 236 "sysinfo.y" /* yacc.c:1661 */ +#line 236 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { @@ -1429,17 +1450,17 @@ printf("\t}\n"); } } -#line 1433 "sysinfo.c" /* yacc.c:1661 */ +#line 1454 "sysinfo.c" /* yacc.c:1646 */ break; case 16: -#line 250 "sysinfo.y" /* yacc.c:1661 */ +#line 250 "sysinfo.y" /* yacc.c:1646 */ {name = (yyvsp[0].s); } -#line 1439 "sysinfo.c" /* yacc.c:1661 */ +#line 1460 "sysinfo.c" /* yacc.c:1646 */ break; case 17: -#line 252 "sysinfo.y" /* yacc.c:1661 */ +#line 252 "sysinfo.y" /* yacc.c:1646 */ { char *desc = (yyvsp[-8].s); char *type = (yyvsp[-6].s); @@ -1540,47 +1561,47 @@ break; } } -#line 1544 "sysinfo.c" /* yacc.c:1661 */ +#line 1565 "sysinfo.c" /* yacc.c:1646 */ break; case 18: -#line 357 "sysinfo.y" /* yacc.c:1661 */ +#line 357 "sysinfo.y" /* yacc.c:1646 */ { (yyval.s) = (yyvsp[0].s); } -#line 1550 "sysinfo.c" /* yacc.c:1661 */ +#line 1571 "sysinfo.c" /* yacc.c:1646 */ break; case 19: -#line 358 "sysinfo.y" /* yacc.c:1661 */ +#line 358 "sysinfo.y" /* yacc.c:1646 */ { (yyval.s) = "INT";} -#line 1556 "sysinfo.c" /* yacc.c:1661 */ +#line 1577 "sysinfo.c" /* yacc.c:1646 */ break; case 20: -#line 363 "sysinfo.y" /* yacc.c:1661 */ +#line 363 "sysinfo.y" /* yacc.c:1646 */ { (yyval.s) = (yyvsp[-1].s); } -#line 1562 "sysinfo.c" /* yacc.c:1661 */ +#line 1583 "sysinfo.c" /* yacc.c:1646 */ break; case 21: -#line 368 "sysinfo.y" /* yacc.c:1661 */ +#line 368 "sysinfo.y" /* yacc.c:1646 */ { (yyval.i) = (yyvsp[-1].i) * (yyvsp[0].i); } -#line 1568 "sysinfo.c" /* yacc.c:1661 */ +#line 1589 "sysinfo.c" /* yacc.c:1646 */ break; case 22: -#line 373 "sysinfo.y" /* yacc.c:1661 */ +#line 373 "sysinfo.y" /* yacc.c:1646 */ { (yyval.s) = (yyvsp[-1].s); } -#line 1574 "sysinfo.c" /* yacc.c:1661 */ +#line 1595 "sysinfo.c" /* yacc.c:1646 */ break; case 23: -#line 374 "sysinfo.y" /* yacc.c:1661 */ +#line 374 "sysinfo.y" /* yacc.c:1646 */ { (yyval.s) = "dummy";} -#line 1580 "sysinfo.c" /* yacc.c:1661 */ +#line 1601 "sysinfo.c" /* yacc.c:1646 */ break; case 27: -#line 382 "sysinfo.y" /* yacc.c:1661 */ +#line 382 "sysinfo.y" /* yacc.c:1646 */ { switch (writecode) { @@ -1591,11 +1612,11 @@ printf("if (ptr->%s%s == %s) { tabout(); printf(\"%s\\n\");}\n", name, names[rdepth],(yyvsp[-1].s),(yyvsp[-2].s)); } } -#line 1595 "sysinfo.c" /* yacc.c:1661 */ +#line 1616 "sysinfo.c" /* yacc.c:1646 */ break; -#line 1599 "sysinfo.c" /* yacc.c:1661 */ +#line 1620 "sysinfo.c" /* yacc.c:1646 */ default: break; } /* User semantic actions sometimes alter yychar, and that requires diff -ruN binutils-2.28/binutils/sysinfo.h binutils-2.28.1/binutils/sysinfo.h --- binutils-2.28/binutils/sysinfo.h 2017-03-02 09:59:33.000000000 +0100 +++ binutils-2.28.1/binutils/sysinfo.h 2017-07-25 16:29:31.000000000 +0200 @@ -1,8 +1,8 @@ -/* A Bison parser, made by GNU Bison 3.0. */ +/* A Bison parser, made by GNU Bison 3.0.4. */ /* Bison interface for Yacc-like parsers in C - Copyright (C) 1984, 1989-1990, 2000-2013 Free Software Foundation, Inc. + Copyright (C) 1984, 1989-1990, 2000-2015 Free Software Foundation, Inc. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by @@ -63,16 +63,18 @@ /* Value type. */ #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED -typedef union YYSTYPE YYSTYPE; + union YYSTYPE { -#line 40 "sysinfo.y" /* yacc.c:1915 */ +#line 40 "sysinfo.y" /* yacc.c:1909 */ int i; char *s; -#line 75 "sysinfo.h" /* yacc.c:1915 */ +#line 75 "sysinfo.h" /* yacc.c:1909 */ }; + +typedef union YYSTYPE YYSTYPE; # define YYSTYPE_IS_TRIVIAL 1 # define YYSTYPE_IS_DECLARED 1 #endif diff -ruN binutils-2.28/gas/ChangeLog binutils-2.28.1/gas/ChangeLog --- binutils-2.28/gas/ChangeLog 2017-03-02 09:55:50.000000000 +0100 +++ binutils-2.28.1/gas/ChangeLog 2017-07-25 16:27:34.000000000 +0200 @@ -1,3 +1,131 @@ +2017-07-25 Tristan Gingold + + * configure: Regenerate. + +2017-07-23 Jiong Wang + + Backport from mainline + 2017-06-06 Jiong Wang + * config/tc-arm.c (reject_bad_reg): Allow REG_SP on ARMv8-A. + (parse_operands): Allow REG_SP for OP_oRRnpcsp and OP_RRnpcsp on + ARMv8-A. + (do_co_reg): Allow REG_SP for Rd on ARMv8-A. + (do_t_add_sub): Likewise. + (do_t_mov_cmp): Likewise. + (do_t_tb): Likewise. + * testsuite/gas/arm/ld-sp-warn.l: Delete the warning on REG_SP as Rt for + ldrsb. + * testsuite/gas/arm/sp-pc-validations-bad-t-v8a.d: New test. + * testsuite/gas/arm/sp-pc-validations-bad-t-v8a.l: New test. + * testsuite/gas/arm/sp-pc-validations-bad-t.d: Specifies -march=armv7-a. + * testsuite/gas/arm/sp-pc-validations-bad-t.s: Remove ".arch armv7-a". + * testsuite/gas/arm/sp-usage-thumb2-relax-on-v7.d: New test. + * testsuite/gas/arm/sp-usage-thumb2-relax-on-v7.l: New test. + * testsuite/gas/arm/sp-usage-thumb2-relax-on-v8.d: New test. + * testsuite/gas/arm/sp-usage-thumb2-relax.s: New test. + * testsuite/gas/arm/strex-bad-t.d: Specifies -march=armv7-a. + +2017-04-05 Ramana Radhakrishnan + + Backport from mainline + 2017-04-04 Ramana Radhakrishnan + * config/tc-arm.c (arm_regs): Add MVFR2. + (do_vmrs): Constraint for MVFR2 and armv8. + (do_vmsr): Likewise. + * testsuite/gas/arm/armv8-a+fp.d: Update. + * testsuite/gas/arm/armv8-a+fp.s: Likewise. + * testsuite/gas/arm/vfp-bad.s: Likewise. + * testsuite/gas/arm/vfp-bad.l: Likewise. + +2017-06-20 Thomas Preud'homme + + Backport from mainline + 2017-04-24 Thomas Preud'homme + + * config/tc-arm.c (move_or_literal_pool): Remove code generating MOVS. + Forbid MOV.W and MOVW if destination is SP or PC. + * testsuite/gas/arm/thumb2_ldr_immediate_highregs_armv6t2.s: Explain + expectation of LDR not generating a MOVS for low registers and small + constants. Add tests of MOVW generation. + * testsuite/gas/arm/thumb2_ldr_immediate_highregs_armv6t2.d: Update + expected disassembly. + +2017-06-05 Alan Modra + + Apply from master + 2017-03-15 Nick Clifton + * config/tc-riscv.c (riscv_pre_output_hook): Fix compile time + warning about discarding a const qualifier. + +2017-04-03 Palmer Dabbelt + + * config/tc-riscv.c (riscv_clear_subsets): Cast argument to free to + avoid const warnings. + +2017-03-30 Palmer Dabbelt + + * config/tc-riscv.c (riscv_clear_subsets): New function. + (riscv_add_subset): Call riscv_clear_subsets and riscv_set_rvc to + clear RVC when it's been previously set. + +2017-03-21 Palmer Dabbbelt + + * config/tc-riscv.c (md_show_usage): Remove defuct -m32, -m64, + -msoft-float, -mhard-float, -mno-rvc, and -mrvc options; and don't + print an invalid default ISA string. + * doc/c-riscv.texi (OPTIONS): Add -fpic and -fno-pic options. + +2017-03-14 Kito Cheng + + * config/tc-riscv.c (validate_riscv_insn): Add 'o' RVC immediate + encoding format, which can accept 0-valued immediates. + (riscv_ip): Likewise. + +2017-03-02 Kuan-Lin Chen + + * config/tc-riscv.h (HWARD2_USE_FIXED_ADVANCE_PC): New define. + +2017-03-02 Kuan-Lin Chen + + * config/tc-riscv.c (md_apply_fix): Set fx_frag and + fx_next->fx_frag for CFA_advance_loc relocations. + +2017-03-02 Kuan-Lin Chen + + * config/tc-riscv.c (md_apply_fix): Compute the correct offsets + for CFA relocations. + +2017-03-27 Alan Modra + + PR 21303 + * testsuite/gas/ppc/pr21303.d, + * testsuite/gas/ppc/pr21303.s: New test + * testsuite/gas/ppc/ppc.exp: Run it. + +2017-03-21 Andreas Krebbel + + Backport from mainline + 2017-03-21 Andreas Krebbel + + * config/tc-s390.c (s390_parse_cpu): Remove S390_INSTR_FLAG_VX2 + from cpu_table. Remove vx2, and novx2 from cpu_flags. + +2017-03-08 Peter Bergner + + * testsuite/gas/ppc/altivec2.d (as): Use the -mpower8 option. + (objdump): Use the -Mpower8 option. + +2017-03-08 Peter Bergner + + Apply from master. + 2017-03-08 Peter Bergner + * testsuite/gas/ppc/power9.d New test. + * testsuite/gas/ppc/power9.s: Likewise. + +2017-03-02 Tristan Gingold + + * configure: Regenerate. + 2017-03-02 Tristan Gingold * configure: Regenerate. diff -ruN binutils-2.28/gas/config/tc-arm.c binutils-2.28.1/gas/config/tc-arm.c --- binutils-2.28/gas/config/tc-arm.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/gas/config/tc-arm.c 2017-07-25 16:26:26.000000000 +0200 @@ -7185,8 +7185,14 @@ { if (inst.operands[i].reg == REG_PC) inst.error = BAD_PC; - else if (inst.operands[i].reg == REG_SP) - inst.error = BAD_SP; + else if (inst.operands[i].reg == REG_SP + /* The restriction on Rd/Rt/Rt2 on Thumb mode has been + relaxed since ARMv8-A. */ + && !ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) + { + gas_assert (thumb); + inst.error = BAD_SP; + } } break; @@ -7284,14 +7290,23 @@ /* Reject "bad registers" for Thumb-2 instructions. Many Thumb-2 instructions are unpredictable if these registers are used. This - is the BadReg predicate in ARM's Thumb-2 documentation. */ -#define reject_bad_reg(reg) \ - do \ - if (reg == REG_SP || reg == REG_PC) \ - { \ - inst.error = (reg == REG_SP) ? BAD_SP : BAD_PC; \ - return; \ - } \ + is the BadReg predicate in ARM's Thumb-2 documentation. + + Before ARMv8-A, REG_PC and REG_SP were not allowed in quite a few + places, while the restriction on REG_SP was relaxed since ARMv8-A. */ +#define reject_bad_reg(reg) \ + do \ + if (reg == REG_PC) \ + { \ + inst.error = BAD_PC; \ + return; \ + } \ + else if (reg == REG_SP \ + && !ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) \ + { \ + inst.error = BAD_SP; \ + return; \ + } \ while (0) /* If REG is R13 (the stack pointer), warn that its use is @@ -7955,17 +7970,13 @@ { if (thumb_p) { - /* This can be encoded only for a low register. */ - if ((v & ~0xFF) == 0 && (inst.operands[i].reg < 8)) - { - /* This can be done with a mov(1) instruction. */ - inst.instruction = T_OPCODE_MOV_I8 | (inst.operands[i].reg << 8); - inst.instruction |= v; - return TRUE; - } + /* LDR should not use lead in a flag-setting instruction being + chosen so we do not check whether movs can be used. */ - if (ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v6t2) + if ((ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v6t2) || ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v6t2_v8m)) + && inst.operands[i].reg != 13 + && inst.operands[i].reg != 15) { /* Check if on thumb2 it can be done with a mov.w, mvn or movw instruction. */ @@ -8647,7 +8658,7 @@ || inst.instruction == 0xfe000010) /* MCR, MCR2 */ reject_bad_reg (Rd); - else + else if (!ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) /* MRC, MRC2 */ constraint (Rd == REG_SP, BAD_SP); } @@ -9112,6 +9123,11 @@ return; } + /* MVFR2 is only valid at ARMv8-A. */ + if (inst.operands[1].reg == 5) + constraint (!ARM_CPU_HAS_FEATURE (cpu_variant, fpu_vfp_ext_armv8), + _(BAD_FPU)); + /* APSR_ sets isvec. All other refs to PC are illegal. */ if (!inst.operands[0].isvec && Rt == REG_PC) { @@ -9138,6 +9154,11 @@ return; } + /* MVFR2 is only valid for ARMv8-A. */ + if (inst.operands[0].reg == 5) + constraint (!ARM_CPU_HAS_FEATURE (cpu_variant, fpu_vfp_ext_armv8), + _(BAD_FPU)); + /* If we get through parsing the register name, we just insert the number generated into the instruction without further validation. */ inst.instruction |= (inst.operands[0].reg << 16); @@ -10517,7 +10538,8 @@ { int add; - constraint (Rd == REG_SP && Rs != REG_SP, BAD_SP); + if (!ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) + constraint (Rd == REG_SP && Rs != REG_SP, BAD_SP); add = (inst.instruction == T_MNEM_add || inst.instruction == T_MNEM_adds); @@ -10641,7 +10663,8 @@ } constraint (Rd == REG_PC, BAD_PC); - constraint (Rd == REG_SP && Rs != REG_SP, BAD_SP); + if (!ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) + constraint (Rd == REG_SP && Rs != REG_SP, BAD_SP); constraint (Rs == REG_PC, BAD_PC); reject_bad_reg (Rn); @@ -11889,7 +11912,8 @@ /* This is mov.w. */ constraint (Rn == REG_PC, BAD_PC); constraint (Rm == REG_PC, BAD_PC); - constraint (Rn == REG_SP && Rm == REG_SP, BAD_SP); + if (!ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) + constraint (Rn == REG_SP && Rm == REG_SP, BAD_SP); } } else @@ -13110,7 +13134,8 @@ Rn = inst.operands[0].reg; Rm = inst.operands[0].imm; - constraint (Rn == REG_SP, BAD_SP); + if (!ARM_CPU_HAS_FEATURE (cpu_variant, arm_ext_v8)) + constraint (Rn == REG_SP, BAD_SP); reject_bad_reg (Rm); constraint (!half && inst.operands[0].shifted, @@ -18799,6 +18824,7 @@ REGDEF(FPINST,9,VFC), REGDEF(FPINST2,10,VFC), REGDEF(mvfr0,7,VFC), REGDEF(mvfr1,6,VFC), REGDEF(MVFR0,7,VFC), REGDEF(MVFR1,6,VFC), + REGDEF(mvfr2,5,VFC), REGDEF(MVFR2,5,VFC), /* Maverick DSP coprocessor registers. */ REGSET(mvf,MVF), REGSET(mvd,MVD), REGSET(mvfx,MVFX), REGSET(mvdx,MVDX), diff -ruN binutils-2.28/gas/config/tc-riscv.c binutils-2.28.1/gas/config/tc-riscv.c --- binutils-2.28/gas/config/tc-riscv.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/gas/config/tc-riscv.c 2017-07-25 16:25:50.000000000 +0200 @@ -121,6 +121,18 @@ } static void +riscv_clear_subsets (void) +{ + while (riscv_subsets != NULL) + { + struct riscv_subset *next = riscv_subsets->next; + free ((void *) riscv_subsets->name); + free (riscv_subsets); + riscv_subsets = next; + } +} + +static void riscv_add_subset (const char *subset) { struct riscv_subset *s = xmalloc (sizeof *s); @@ -139,6 +151,8 @@ const char *extension = NULL; const char *p = s; + riscv_clear_subsets(); + if (strncmp (p, "rv32", 4) == 0) { xlen = 32; @@ -500,6 +514,7 @@ case 'c': break; /* RS1, constrained to equal sp */ case 'i': used_bits |= ENCODE_RVC_SIMM3(-1U); break; case 'j': used_bits |= ENCODE_RVC_IMM (-1U); break; + case 'o': used_bits |= ENCODE_RVC_IMM (-1U); break; case 'k': used_bits |= ENCODE_RVC_LW_IMM (-1U); break; case 'l': used_bits |= ENCODE_RVC_LD_IMM (-1U); break; case 'm': used_bits |= ENCODE_RVC_LWSP_IMM (-1U); break; @@ -1321,6 +1336,13 @@ ip->insn_opcode |= ENCODE_RVC_LDSP_IMM (imm_expr->X_add_number); goto rvc_imm_done; + case 'o': + if (my_getSmallExpression (imm_expr, imm_reloc, s, p) + || imm_expr->X_op != O_constant + || !VALID_RVC_IMM (imm_expr->X_add_number)) + break; + ip->insn_opcode |= ENCODE_RVC_IMM (imm_expr->X_add_number); + goto rvc_imm_done; case 'K': if (my_getSmallExpression (imm_expr, imm_reloc, s, p) || imm_expr->X_op != O_constant @@ -1794,6 +1816,7 @@ riscv_set_arch (xlen == 64 ? "rv64g" : "rv32g"); /* Add the RVC extension, regardless of -march, to support .option rvc. */ + riscv_set_rvc (FALSE); if (riscv_subset_supports ("c")) riscv_set_rvc (TRUE); else @@ -1837,6 +1860,7 @@ unsigned int subtype; bfd_byte *buf = (bfd_byte *) (fixP->fx_frag->fr_literal + fixP->fx_where); bfd_boolean relaxable = FALSE; + offsetT loc; /* Remember value for tc_gen_reloc. */ fixP->fx_addnumber = *valP; @@ -1922,30 +1946,31 @@ case BFD_RELOC_RISCV_CFA: /* Load the byte to get the subtype. */ - subtype = bfd_get_8 (NULL, &fixP->fx_frag->fr_literal[fixP->fx_where]); + subtype = bfd_get_8 (NULL, &((fragS *) (fixP->fx_frag->fr_opcode))->fr_literal[fixP->fx_where]); + loc = fixP->fx_frag->fr_fix - (subtype & 7); switch (subtype) { case DW_CFA_advance_loc1: - fixP->fx_where++; - fixP->fx_next->fx_where++; + fixP->fx_where = loc + 1; + fixP->fx_next->fx_where = loc + 1; fixP->fx_r_type = BFD_RELOC_RISCV_SET8; fixP->fx_next->fx_r_type = BFD_RELOC_RISCV_SUB8; break; case DW_CFA_advance_loc2: fixP->fx_size = 2; - fixP->fx_where++; fixP->fx_next->fx_size = 2; - fixP->fx_next->fx_where++; + fixP->fx_where = loc + 1; + fixP->fx_next->fx_where = loc + 1; fixP->fx_r_type = BFD_RELOC_RISCV_SET16; fixP->fx_next->fx_r_type = BFD_RELOC_RISCV_SUB16; break; case DW_CFA_advance_loc4: fixP->fx_size = 4; - fixP->fx_where++; fixP->fx_next->fx_size = 4; - fixP->fx_next->fx_where++; + fixP->fx_where = loc; + fixP->fx_next->fx_where = loc; fixP->fx_r_type = BFD_RELOC_RISCV_SET32; fixP->fx_next->fx_r_type = BFD_RELOC_RISCV_SUB32; break; @@ -1954,6 +1979,8 @@ if (subtype < 0x80 && (subtype & 0x40)) { /* DW_CFA_advance_loc */ + fixP->fx_frag = (fragS *) fixP->fx_frag->fr_opcode; + fixP->fx_next->fx_frag = fixP->fx_frag; fixP->fx_r_type = BFD_RELOC_RISCV_SET6; fixP->fx_next->fx_r_type = BFD_RELOC_RISCV_SUB6; } @@ -2063,13 +2090,12 @@ for (s = stdoutput->sections; s; s = s->next) for (frch = seg_info (s)->frchainP; frch; frch = frch->frch_next) { - const fragS *frag; + fragS *frag; for (frag = frch->frch_root; frag; frag = frag->fr_next) { if (frag->fr_type == rs_cfa) { - fragS *loc4_frag; expressionS exp; symbolS *add_symbol = frag->fr_symbol->sy_value.X_add_symbol; @@ -2080,8 +2106,7 @@ exp.X_add_number = 0; exp.X_op_symbol = op_symbol; - loc4_frag = (fragS *) frag->fr_opcode; - fix_new_exp (loc4_frag, (int) frag->fr_offset, 1, &exp, 0, + fix_new_exp (frag, (int) frag->fr_offset, 1, &exp, 0, BFD_RELOC_RISCV_CFA); } } @@ -2455,15 +2480,10 @@ { fprintf (stream, _("\ RISC-V options:\n\ - -m32 assemble RV32 code\n\ - -m64 assemble RV64 code (default)\n\ -fpic generate position-independent code\n\ -fno-pic don't generate position-independent code (default)\n\ - -msoft-float don't use F registers for floating-point values\n\ - -mhard-float use F registers for floating-point values (default)\n\ - -mno-rvc disable the C extension for compressed instructions (default)\n\ - -mrvc enable the C extension for compressed instructions\n\ - -march=ISA set the RISC-V architecture, RV64IMAFD by default\n\ + -march=ISA set the RISC-V architecture\n\ + -mabi=ABI set the RISC-V ABI\n\ ")); } diff -ruN binutils-2.28/gas/config/tc-riscv.h binutils-2.28.1/gas/config/tc-riscv.h --- binutils-2.28/gas/config/tc-riscv.h 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/gas/config/tc-riscv.h 2017-07-25 16:25:50.000000000 +0200 @@ -112,4 +112,7 @@ #define elf_tc_final_processing riscv_elf_final_processing extern void riscv_elf_final_processing (void); +/* Adjust debug_line after relaxation. */ +#define DWARF2_USE_FIXED_ADVANCE_PC 1 + #endif /* TC_RISCV */ diff -ruN binutils-2.28/gas/config/tc-s390.c binutils-2.28.1/gas/config/tc-s390.c --- binutils-2.28/gas/config/tc-s390.c 2017-03-02 09:23:53.000000000 +0100 +++ binutils-2.28.1/gas/config/tc-s390.c 2017-07-25 16:25:50.000000000 +0200 @@ -291,7 +291,7 @@ { STRING_COMMA_LEN ("z13"), STRING_COMMA_LEN ("arch11"), S390_INSTR_FLAG_HTM | S390_INSTR_FLAG_VX }, { STRING_COMMA_LEN ("arch12"), STRING_COMMA_LEN (""), - S390_INSTR_FLAG_HTM | S390_INSTR_FLAG_VX | S390_INSTR_FLAG_VX2 } + S390_INSTR_FLAG_HTM | S390_INSTR_FLAG_VX } }; static struct { @@ -303,9 +303,7 @@ { "htm", S390_INSTR_FLAG_HTM, TRUE }, { "nohtm", S390_INSTR_FLAG_HTM, FALSE }, { "vx", S390_INSTR_FLAG_VX, TRUE }, - { "novx", S390_INSTR_FLAG_VX, FALSE }, - { "vx2", S390_INSTR_FLAG_VX2, TRUE }, - { "novx2", S390_INSTR_FLAG_VX2, FALSE } + { "novx", S390_INSTR_FLAG_VX, FALSE } }; unsigned int icpu; char *ilp_bak; diff -ruN binutils-2.28/gas/configure binutils-2.28.1/gas/configure --- binutils-2.28/gas/configure 2017-03-02 09:55:50.000000000 +0100 +++ binutils-2.28.1/gas/configure 2017-07-25 16:27:34.000000000 +0200 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.64 for gas 2.28. +# Generated by GNU Autoconf 2.64 for gas 2.28.1. # # Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, # 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software @@ -556,8 +556,8 @@ # Identity of this package. PACKAGE_NAME='gas' PACKAGE_TARNAME='gas' -PACKAGE_VERSION='2.28' -PACKAGE_STRING='gas 2.28' +PACKAGE_VERSION='2.28.1' +PACKAGE_STRING='gas 2.28.1' PACKAGE_BUGREPORT='' PACKAGE_URL='' @@ -1330,7 +1330,7 @@ # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures gas 2.28 to adapt to many kinds of systems. +\`configure' configures gas 2.28.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1401,7 +1401,7 @@ if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of gas 2.28:";; + short | recursive ) echo "Configuration of gas 2.28.1:";; esac cat <<\_ACEOF @@ -1523,7 +1523,7 @@ test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -gas configure 2.28 +gas configure 2.28.1 generated by GNU Autoconf 2.64 Copyright (C) 2009 Free Software Foundation, Inc. @@ -1933,7 +1933,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by gas $as_me 2.28, which was +It was created by gas $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was $ $0 $@ @@ -3742,7 +3742,7 @@ # Define the identity of the package. PACKAGE='gas' - VERSION='2.28' + VERSION='2.28.1' cat >>confdefs.h <<_ACEOF @@ -15212,7 +15212,7 @@ # report actual input values of CONFIG_FILES etc. instead of their # values after options handling. ac_log=" -This file was extended by gas $as_me 2.28, which was +This file was extended by gas $as_me 2.28.1, which was generated by GNU Autoconf 2.64. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -15276,7 +15276,7 @@ _ACEOF cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 ac_cs_version="\\ -gas config.status 2.28 +gas config.status 2.28.1 configured by $0, generated by GNU Autoconf 2.64, with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\" diff -ruN binutils-2.28/gas/doc/as.1 binutils-2.28.1/gas/doc/as.1 --- binutils-2.28/gas/doc/as.1 2017-03-02 09:59:31.000000000 +0100 +++ binutils-2.28.1/gas/doc/as.1 2017-07-25 16:29:30.000000000 +0200 @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28) +.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29) .\" .\" Standard preamble: .\" ======================================================================== @@ -133,7 +133,7 @@ .\" ======================================================================== .\" .IX Title "AS 1" -.TH AS 1 "2017-03-02" "binutils-2.28" "GNU Development Tools" +.TH AS 1 "2017-07-25" "binutils-2.28.1" "GNU Development Tools" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -1804,6 +1804,12 @@ .PP The following options are available when as is configured for a RISC-V processor. +.IP "\fB\-fpic\fR" 4 +.IX Item "-fpic" +Generate position-independent code +.IP "\fB\-fno\-pic\fR" 4 +.IX Item "-fno-pic" +Don't generate position-independent code (default) .IP "\fB\-march=ISA\fR" 4 .IX Item "-march=ISA" Select the base isa, as specified by \s-1ISA. \s0 For example \-march=rv32ima. diff -ruN binutils-2.28/gas/doc/as.info binutils-2.28.1/gas/doc/as.info --- binutils-2.28/gas/doc/as.info 2017-03-02 09:59:31.000000000 +0100 +++ binutils-2.28.1/gas/doc/as.info 2017-07-25 16:29:29.000000000 +0200 @@ -1,12 +1,6 @@ -This is as.info, produced by makeinfo version 4.8 from as.texinfo. +This is as.info, produced by makeinfo version 6.1 from as.texinfo. -INFO-DIR-SECTION Software development -START-INFO-DIR-ENTRY -* As: (as). The GNU assembler. -* Gas: (as). The GNU assembler. -END-INFO-DIR-ENTRY - - This file documents the GNU Assembler "as". +This file documents the GNU Assembler "as". Copyright (C) 1991-2017 Free Software Foundation, Inc. @@ -17,18 +11,24 @@ Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". +INFO-DIR-SECTION Software development +START-INFO-DIR-ENTRY +* As: (as). The GNU assembler. +* Gas: (as). The GNU assembler. +END-INFO-DIR-ENTRY +  File: as.info, Node: Top, Next: Overview, Up: (dir) Using as ******** -This file is a user guide to the GNU assembler `as' (GNU Binutils) +This file is a user guide to the GNU assembler 'as' (GNU Binutils) version 2.28. This document is distributed under the terms of the GNU Free -Documentation License. A copy of the license is included in the -section entitled "GNU Free Documentation License". +Documentation License. A copy of the license is included in the section +entitled "GNU Free Documentation License". * Menu: @@ -39,7 +39,6 @@ * Symbols:: Symbols * Expressions:: Expressions * Pseudo Ops:: Assembler Directives - * Object Attributes:: Object Attributes * Machine Dependencies:: Machine Dependent Features * Reporting Bugs:: Reporting Bugs @@ -53,7 +52,7 @@ 1 Overview ********** -Here is a brief summary of how to invoke `as'. For details, see *Note +Here is a brief summary of how to invoke 'as'. For details, see *note Command-Line Options: Invoking. as [-a[cdghlns][=FILE]] [-alternate] [-D] @@ -334,113 +333,113 @@ [ -forbid-undocumented-instructions] [-Fud] [ -forbid-unportable-instructions] [-Fup] -`@FILE' - Read command-line options from FILE. The options read are - inserted in place of the original @FILE option. If FILE does not - exist, or cannot be read, then the option will be treated - literally, and not removed. + + +'@FILE' + Read command-line options from FILE. The options read are inserted + in place of the original @FILE option. If FILE does not exist, or + cannot be read, then the option will be treated literally, and not + removed. Options in FILE are separated by whitespace. A whitespace character may be included in an option by surrounding the entire - option in either single or double quotes. Any character - (including a backslash) may be included by prefixing the character - to be included with a backslash. The FILE may itself contain - additional @FILE options; any such options will be processed - recursively. + option in either single or double quotes. Any character (including + a backslash) may be included by prefixing the character to be + included with a backslash. The FILE may itself contain additional + @FILE options; any such options will be processed recursively. -`-a[cdghlmns]' +'-a[cdghlmns]' Turn on listings, in any of a variety of ways: - `-ac' + '-ac' omit false conditionals - `-ad' + '-ad' omit debugging directives - `-ag' + '-ag' include general information, like as version and options passed - `-ah' + '-ah' include high-level source - `-al' + '-al' include assembly - `-am' + '-am' include macro expansions - `-an' + '-an' omit forms processing - `-as' + '-as' include symbols - `=file' + '=file' set the name of the listing file - You may combine these options; for example, use `-aln' for assembly - listing without forms processing. The `=file' option, if used, - must be the last one. By itself, `-a' defaults to `-ahls'. + You may combine these options; for example, use '-aln' for assembly + listing without forms processing. The '=file' option, if used, + must be the last one. By itself, '-a' defaults to '-ahls'. -`--alternate' - Begin in alternate macro mode. *Note `.altmacro': Altmacro. +'--alternate' + Begin in alternate macro mode. *Note '.altmacro': Altmacro. -`--compress-debug-sections' +'--compress-debug-sections' Compress DWARF debug sections using zlib with SHF_COMPRESSED from - the ELF ABI. The resulting object file may not be compatible with - older linkers and object file utilities. Note if compression - would make a given section _larger_ then it is not compressed. - -`--compress-debug-sections=none' -`--compress-debug-sections=zlib' -`--compress-debug-sections=zlib-gnu' -`--compress-debug-sections=zlib-gabi' + the ELF ABI. The resulting object file may not be compatible with + older linkers and object file utilities. Note if compression would + make a given section _larger_ then it is not compressed. + +'--compress-debug-sections=none' +'--compress-debug-sections=zlib' +'--compress-debug-sections=zlib-gnu' +'--compress-debug-sections=zlib-gabi' These options control how DWARF debug sections are compressed. - `--compress-debug-sections=none' is equivalent to - `--nocompress-debug-sections'. `--compress-debug-sections=zlib' - and `--compress-debug-sections=zlib-gabi' are equivalent to - `--compress-debug-sections'. `--compress-debug-sections=zlib-gnu' - compresses DWARF debug sections using zlib. The debug sections - are renamed to begin with `.zdebug'. Note if compression would - make a given section _larger_ then it is not compressed nor - renamed. + '--compress-debug-sections=none' is equivalent to + '--nocompress-debug-sections'. '--compress-debug-sections=zlib' + and '--compress-debug-sections=zlib-gabi' are equivalent to + '--compress-debug-sections'. '--compress-debug-sections=zlib-gnu' + compresses DWARF debug sections using zlib. The debug sections are + renamed to begin with '.zdebug'. Note if compression would make a + given section _larger_ then it is not compressed nor renamed. -`--nocompress-debug-sections' +'--nocompress-debug-sections' Do not compress DWARF debug sections. This is usually the default for all targets except the x86/x86_64, but a configure time option can be used to override this. -`-D' +'-D' Ignored. This option is accepted for script compatibility with calls to other assemblers. -`--debug-prefix-map OLD=NEW' - When assembling files in directory `OLD', record debugging - information describing them as in `NEW' instead. +'--debug-prefix-map OLD=NEW' + When assembling files in directory 'OLD', record debugging + information describing them as in 'NEW' instead. -`--defsym SYM=VALUE' +'--defsym SYM=VALUE' Define the symbol SYM to be VALUE before assembling the input file. - VALUE must be an integer constant. As in C, a leading `0x' - indicates a hexadecimal value, and a leading `0' indicates an octal + VALUE must be an integer constant. As in C, a leading '0x' + indicates a hexadecimal value, and a leading '0' indicates an octal value. The value of the symbol can be overridden inside a source - file via the use of a `.set' pseudo-op. + file via the use of a '.set' pseudo-op. -`-f' +'-f' "fast"--skip whitespace and comment preprocessing (assume source is compiler output). -`-g' -`--gen-debug' - Generate debugging information for each assembler source line - using whichever debug format is preferred by the target. This - currently means either STABS, ECOFF or DWARF2. +'-g' +'--gen-debug' + Generate debugging information for each assembler source line using + whichever debug format is preferred by the target. This currently + means either STABS, ECOFF or DWARF2. -`--gstabs' +'--gstabs' Generate stabs debugging information for each assembler line. This may help debugging assembler code, if the debugger can handle it. -`--gstabs+' +'--gstabs+' Generate stabs debugging information for each assembler line, with GNU extensions that probably only gdb can handle, and that could make other debuggers crash or refuse to read your program. This @@ -448,137 +447,136 @@ extension is the location of the current working directory at assembling time. -`--gdwarf-2' +'--gdwarf-2' Generate DWARF2 debugging information for each assembler line. This may help debugging assembler code, if the debugger can handle it. Note--this option is only supported by some targets, not all of them. -`--gdwarf-sections' +'--gdwarf-sections' Instead of creating a .debug_line section, create a series of - .debug_line.FOO sections where FOO is the name of the - corresponding code section. For example a code section called - .TEXT.FUNC will have its dwarf line number information placed into - a section called .DEBUG_LINE.TEXT.FUNC. If the code section is - just called .TEXT then debug line section will still be called - just .DEBUG_LINE without any suffix. + .debug_line.FOO sections where FOO is the name of the corresponding + code section. For example a code section called .TEXT.FUNC will + have its dwarf line number information placed into a section called + .DEBUG_LINE.TEXT.FUNC. If the code section is just called .TEXT + then debug line section will still be called just .DEBUG_LINE + without any suffix. -`--size-check=error' -`--size-check=warning' +'--size-check=error' +'--size-check=warning' Issue an error or warning for invalid ELF .size directive. -`--elf-stt-common=no' -`--elf-stt-common=yes' +'--elf-stt-common=no' +'--elf-stt-common=yes' These options control whether the ELF assembler should generate - common symbols with the `STT_COMMON' type. The default can be - controlled by a configure option `--enable-elf-stt-common'. + common symbols with the 'STT_COMMON' type. The default can be + controlled by a configure option '--enable-elf-stt-common'. -`--help' +'--help' Print a summary of the command line options and exit. -`--target-help' +'--target-help' Print a summary of all target specific options and exit. -`-I DIR' - Add directory DIR to the search list for `.include' directives. +'-I DIR' + Add directory DIR to the search list for '.include' directives. -`-J' +'-J' Don't warn about signed overflow. -`-K' +'-K' Issue warnings when difference tables altered for long displacements. -`-L' -`--keep-locals' +'-L' +'--keep-locals' Keep (in the symbol table) local symbols. These symbols start with - system-specific local label prefixes, typically `.L' for ELF - systems or `L' for traditional a.out systems. *Note Symbol + system-specific local label prefixes, typically '.L' for ELF + systems or 'L' for traditional a.out systems. *Note Symbol Names::. -`--listing-lhs-width=NUMBER' +'--listing-lhs-width=NUMBER' Set the maximum width, in words, of the output data column for an assembler listing to NUMBER. -`--listing-lhs-width2=NUMBER' +'--listing-lhs-width2=NUMBER' Set the maximum width, in words, of the output data column for continuation lines in an assembler listing to NUMBER. -`--listing-rhs-width=NUMBER' +'--listing-rhs-width=NUMBER' Set the maximum width of an input source line, as displayed in a listing, to NUMBER bytes. -`--listing-cont-lines=NUMBER' +'--listing-cont-lines=NUMBER' Set the maximum number of lines printed in a listing for a single line of input to NUMBER + 1. -`--no-pad-sections' +'--no-pad-sections' Stop the assembler for padding the ends of output sections to the - alignment of that section. The default is to pad the sections, - but this can waste space which might be needed on targets which - have tight memory constraints. + alignment of that section. The default is to pad the sections, but + this can waste space which might be needed on targets which have + tight memory constraints. -`-o OBJFILE' - Name the object-file output from `as' OBJFILE. +'-o OBJFILE' + Name the object-file output from 'as' OBJFILE. -`-R' +'-R' Fold the data section into the text section. -`--hash-size=NUMBER' +'--hash-size=NUMBER' Set the default size of GAS's hash tables to a prime number close to NUMBER. Increasing this value can reduce the length of time it takes the assembler to perform its tasks, at the expense of - increasing the assembler's memory requirements. Similarly - reducing this value can reduce the memory requirements at the - expense of speed. + increasing the assembler's memory requirements. Similarly reducing + this value can reduce the memory requirements at the expense of + speed. -`--reduce-memory-overheads' +'--reduce-memory-overheads' This option reduces GAS's memory requirements, at the expense of making the assembly processes slower. Currently this switch is a - synonym for `--hash-size=4051', but in the future it may have - other effects as well. + synonym for '--hash-size=4051', but in the future it may have other + effects as well. -`--sectname-subst' - Honor substitution sequences in section names. *Note `.section +'--sectname-subst' + Honor substitution sequences in section names. *Note '.section NAME': Section Name Substitutions. -`--statistics' - Print the maximum space (in bytes) and total time (in seconds) - used by assembly. +'--statistics' + Print the maximum space (in bytes) and total time (in seconds) used + by assembly. -`--strip-local-absolute' +'--strip-local-absolute' Remove local absolute symbols from the outgoing symbol table. -`-v' -`-version' - Print the `as' version. +'-v' +'-version' + Print the 'as' version. -`--version' - Print the `as' version and exit. +'--version' + Print the 'as' version and exit. -`-W' -`--no-warn' +'-W' +'--no-warn' Suppress warning messages. -`--fatal-warnings' +'--fatal-warnings' Treat warnings as errors. -`--warn' +'--warn' Don't suppress warning messages or treat them as errors. -`-w' +'-w' Ignored. -`-x' +'-x' Ignored. -`-Z' +'-Z' Generate an object file even after errors. -`-- | FILES ...' +'-- | FILES ...' Standard input, or source files to assemble. - *Note AArch64 Options::, for the options available when as is configured for the 64-bit mode of the ARM Architecture (AArch64). @@ -588,47 +586,36 @@ The following options are available when as is configured for an ARC processor. -`-mcpu=CPU' +'-mcpu=CPU' This option selects the core processor variant. - -`-EB | -EL' +'-EB | -EL' Select either big-endian (-EB) or little-endian (-EL) output. - -`-mcode-density' +'-mcode-density' Enable Code Density extenssion instructions. The following options are available when as is configured for the ARM processor family. -`-mcpu=PROCESSOR[+EXTENSION...]' +'-mcpu=PROCESSOR[+EXTENSION...]' Specify which ARM processor variant is the target. - -`-march=ARCHITECTURE[+EXTENSION...]' +'-march=ARCHITECTURE[+EXTENSION...]' Specify which ARM architecture variant is used by the target. - -`-mfpu=FLOATING-POINT-FORMAT' +'-mfpu=FLOATING-POINT-FORMAT' Select which Floating Point architecture is the target. - -`-mfloat-abi=ABI' +'-mfloat-abi=ABI' Select which floating point ABI is in use. - -`-mthumb' +'-mthumb' Enable Thumb only instruction decoding. - -`-mapcs-32 | -mapcs-26 | -mapcs-float | -mapcs-reentrant' +'-mapcs-32 | -mapcs-26 | -mapcs-float | -mapcs-reentrant' Select which procedure calling convention is in use. - -`-EB | -EL' +'-EB | -EL' Select either big-endian (-EB) or little-endian (-EL) output. - -`-mthumb-interwork' +'-mthumb-interwork' Specify that the code has been generated with interworking between Thumb and ARM code in mind. - -`-mccs' +'-mccs' Turns on CodeComposer Studio assembly syntax compatibility mode. - -`-k' +'-k' Specify that PIC code has been generated. *Note Blackfin Options::, for the options available when as is @@ -638,18 +625,18 @@ The following options are available when as is configured for a D10V processor. -`-O' +'-O' Optimize output by parallelizing instructions. The following options are available when as is configured for a D30V processor. -`-O' +'-O' Optimize output by parallelizing instructions. -`-n' +'-n' Warn when nops are generated. -`-N' +'-N' Warn when a nop after a 32-bit multiply instruction is generated. The following options are available when as is configured for the @@ -658,82 +645,78 @@ *Note Epiphany Options::, for the options available when as is configured for an Epiphany processor. - *Note i386-Options::, for the options available when as is -configured for an i386 processor. + *Note i386-Options::, for the options available when as is configured +for an i386 processor. The following options are available when as is configured for the Intel 80960 processor. -`-ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC' +'-ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC' Specify which variant of the 960 architecture is the target. -`-b' +'-b' Add code to collect statistics about branches taken. -`-no-relax' +'-no-relax' Do not alter compare-and-branch instructions for long displacements; error if necessary. - The following options are available when as is configured for the Ubicom IP2K series. -`-mip2022ext' +'-mip2022ext' Specifies that the extended IP2022 instructions are allowed. -`-mip2022' +'-mip2022' Restores the default behaviour, which restricts the permitted instructions to just the basic IP2022 ones. - The following options are available when as is configured for the Renesas M32C and M16C processors. -`-m32c' +'-m32c' Assemble M32C instructions. -`-m16c' +'-m16c' Assemble M16C instructions (the default). -`-relax' +'-relax' Enable support for link-time relaxations. -`-h-tick-hex' +'-h-tick-hex' Support H'00 style hex constants in addition to 0x00 style. - The following options are available when as is configured for the Renesas M32R (formerly Mitsubishi M32R) series. -`--m32rx' +'--m32rx' Specify which processor in the M32R family is the target. The default is normally the M32R, but this option changes it to the M32RX. -`--warn-explicit-parallel-conflicts or --Wp' +'--warn-explicit-parallel-conflicts or --Wp' Produce warning messages when questionable parallel constructs are encountered. -`--no-warn-explicit-parallel-conflicts or --Wnp' +'--no-warn-explicit-parallel-conflicts or --Wnp' Do not produce warning messages when questionable parallel constructs are encountered. - The following options are available when as is configured for the Motorola 68000 series. -`-l' +'-l' Shorten references to undefined symbols, to one word instead of two. -`-m68000 | -m68008 | -m68010 | -m68020 | -m68030' -`| -m68040 | -m68060 | -m68302 | -m68331 | -m68332' -`| -m68333 | -m68340 | -mcpu32 | -m5200' +'-m68000 | -m68008 | -m68010 | -m68020 | -m68030' +'| -m68040 | -m68060 | -m68302 | -m68331 | -m68332' +'| -m68333 | -m68340 | -mcpu32 | -m5200' Specify what processor in the 68000 family is the target. The default is normally the 68020, but this can be changed at configuration time. -`-m68881 | -m68882 | -mno-68881 | -mno-68882' +'-m68881 | -m68882 | -mno-68881 | -mno-68882' The target machine does (or does not) have a floating-point coprocessor. The default is to assume a coprocessor for 68020, 68030, and cpu32. Although the basic 68000 is not compatible with @@ -741,400 +724,393 @@ possible to do emulation of the coprocessor instructions with the main processor. -`-m68851 | -mno-68851' - The target machine does (or does not) have a memory-management - unit coprocessor. The default is to assume an MMU for 68020 and - up. - +'-m68851 | -mno-68851' + The target machine does (or does not) have a memory-management unit + coprocessor. The default is to assume an MMU for 68020 and up. *Note Nios II Options::, for the options available when as is configured for an Altera Nios II processor. For details about the PDP-11 machine dependent features options, see -*Note PDP-11-Options::. +*note PDP-11-Options::. -`-mpic | -mno-pic' +'-mpic | -mno-pic' Generate position-independent (or position-dependent) code. The - default is `-mpic'. + default is '-mpic'. -`-mall' -`-mall-extensions' +'-mall' +'-mall-extensions' Enable all instruction set extensions. This is the default. -`-mno-extensions' +'-mno-extensions' Disable all instruction set extensions. -`-mEXTENSION | -mno-EXTENSION' +'-mEXTENSION | -mno-EXTENSION' Enable (or disable) a particular instruction set extension. -`-mCPU' +'-mCPU' Enable the instruction set extensions supported by a particular CPU, and disable all other extensions. -`-mMACHINE' +'-mMACHINE' Enable the instruction set extensions supported by a particular machine model, and disable all other extensions. The following options are available when as is configured for a picoJava processor. -`-mb' +'-mb' Generate "big endian" format output. -`-ml' +'-ml' Generate "little endian" format output. - The following options are available when as is configured for the Motorola 68HC11 or 68HC12 series. -`-m68hc11 | -m68hc12 | -m68hcs12 | -mm9s12x | -mm9s12xg' +'-m68hc11 | -m68hc12 | -m68hcs12 | -mm9s12x | -mm9s12xg' Specify what processor is the target. The default is defined by the configuration option when building the assembler. -`--xgate-ramoffset' - Instruct the linker to offset RAM addresses from S12X address - space into XGATE address space. +'--xgate-ramoffset' + Instruct the linker to offset RAM addresses from S12X address space + into XGATE address space. -`-mshort' +'-mshort' Specify to use the 16-bit integer ABI. -`-mlong' +'-mlong' Specify to use the 32-bit integer ABI. -`-mshort-double' +'-mshort-double' Specify to use the 32-bit double ABI. -`-mlong-double' +'-mlong-double' Specify to use the 64-bit double ABI. -`--force-long-branches' - Relative branches are turned into absolute ones. This concerns +'--force-long-branches' + Relative branches are turned into absolute ones. This concerns conditional branches, unconditional branches and branches to a sub routine. -`-S | --short-branches' - Do not turn relative branches into absolute ones when the offset - is out of range. +'-S | --short-branches' + Do not turn relative branches into absolute ones when the offset is + out of range. -`--strict-direct-mode' +'--strict-direct-mode' Do not turn the direct addressing mode into extended addressing mode when the instruction does not support direct addressing mode. -`--print-insn-syntax' +'--print-insn-syntax' Print the syntax of instruction in case of error. -`--print-opcodes' +'--print-opcodes' Print the list of instructions with syntax and then exit. -`--generate-example' +'--generate-example' Print an example of instruction for each possible instruction and - then exit. This option is only useful for testing `as'. - + then exit. This option is only useful for testing 'as'. - The following options are available when `as' is configured for the + The following options are available when 'as' is configured for the SPARC architecture: -`-Av6 | -Av7 | -Av8 | -Asparclet | -Asparclite' -`-Av8plus | -Av8plusa | -Av9 | -Av9a' +'-Av6 | -Av7 | -Av8 | -Asparclet | -Asparclite' +'-Av8plus | -Av8plusa | -Av9 | -Av9a' Explicitly select a variant of the SPARC architecture. - `-Av8plus' and `-Av8plusa' select a 32 bit environment. `-Av9' - and `-Av9a' select a 64 bit environment. + '-Av8plus' and '-Av8plusa' select a 32 bit environment. '-Av9' and + '-Av9a' select a 64 bit environment. - `-Av8plusa' and `-Av9a' enable the SPARC V9 instruction set with + '-Av8plusa' and '-Av9a' enable the SPARC V9 instruction set with UltraSPARC extensions. -`-xarch=v8plus | -xarch=v8plusa' +'-xarch=v8plus | -xarch=v8plusa' For compatibility with the Solaris v9 assembler. These options are equivalent to -Av8plus and -Av8plusa, respectively. -`-bump' +'-bump' Warn when the assembler switches to another architecture. The following options are available when as is configured for the 'c54x architecture. -`-mfar-mode' +'-mfar-mode' Enable extended addressing mode. All addresses and relocations will assume extended addressing (usually 23 bits). - -`-mcpu=CPU_VERSION' +'-mcpu=CPU_VERSION' Sets the CPU version being compiled for. - -`-merrors-to-file FILENAME' +'-merrors-to-file FILENAME' Redirect error output to a file, for broken systems which don't support such behaviour in the shell. The following options are available when as is configured for a MIPS processor. -`-G NUM' +'-G NUM' This option sets the largest size of an object that can be - referenced implicitly with the `gp' register. It is only accepted + referenced implicitly with the 'gp' register. It is only accepted for targets that use ECOFF format, such as a DECstation running Ultrix. The default value is 8. -`-EB' +'-EB' Generate "big endian" format output. -`-EL' +'-EL' Generate "little endian" format output. -`-mips1' -`-mips2' -`-mips3' -`-mips4' -`-mips5' -`-mips32' -`-mips32r2' -`-mips32r3' -`-mips32r5' -`-mips32r6' -`-mips64' -`-mips64r2' -`-mips64r3' -`-mips64r5' -`-mips64r6' +'-mips1' +'-mips2' +'-mips3' +'-mips4' +'-mips5' +'-mips32' +'-mips32r2' +'-mips32r3' +'-mips32r5' +'-mips32r6' +'-mips64' +'-mips64r2' +'-mips64r3' +'-mips64r5' +'-mips64r6' Generate code for a particular MIPS Instruction Set Architecture - level. `-mips1' is an alias for `-march=r3000', `-mips2' is an - alias for `-march=r6000', `-mips3' is an alias for `-march=r4000' - and `-mips4' is an alias for `-march=r8000'. `-mips5', `-mips32', - `-mips32r2', `-mips32r3', `-mips32r5', `-mips32r6', `-mips64', - `-mips64r2', `-mips64r3', `-mips64r5', and `-mips64r6' correspond + level. '-mips1' is an alias for '-march=r3000', '-mips2' is an + alias for '-march=r6000', '-mips3' is an alias for '-march=r4000' + and '-mips4' is an alias for '-march=r8000'. '-mips5', '-mips32', + '-mips32r2', '-mips32r3', '-mips32r5', '-mips32r6', '-mips64', + '-mips64r2', '-mips64r3', '-mips64r5', and '-mips64r6' correspond to generic MIPS V, MIPS32, MIPS32 Release 2, MIPS32 Release 3, MIPS32 Release 5, MIPS32 Release 6, MIPS64, MIPS64 Release 2, MIPS64 Release 3, MIPS64 Release 5, and MIPS64 Release 6 ISA processors, respectively. -`-march=CPU' +'-march=CPU' Generate code for a particular MIPS CPU. -`-mtune=CPU' +'-mtune=CPU' Schedule and tune for a particular MIPS CPU. -`-mfix7000' -`-mno-fix7000' +'-mfix7000' +'-mno-fix7000' Cause nops to be inserted if the read of the destination register of an mfhi or mflo instruction occurs in the following two instructions. -`-mfix-rm7000' -`-mno-fix-rm7000' +'-mfix-rm7000' +'-mno-fix-rm7000' Cause nops to be inserted if a dmult or dmultu instruction is followed by a load instruction. -`-mdebug' -`-no-mdebug' +'-mdebug' +'-no-mdebug' Cause stabs-style debugging output to go into an ECOFF-style .mdebug section instead of the standard ELF .stabs sections. -`-mpdr' -`-mno-pdr' - Control generation of `.pdr' sections. +'-mpdr' +'-mno-pdr' + Control generation of '.pdr' sections. -`-mgp32' -`-mfp32' +'-mgp32' +'-mfp32' The register sizes are normally inferred from the ISA and ABI, but these flags force a certain group of registers to be treated as 32 - bits wide at all times. `-mgp32' controls the size of - general-purpose registers and `-mfp32' controls the size of + bits wide at all times. '-mgp32' controls the size of + general-purpose registers and '-mfp32' controls the size of floating-point registers. -`-mgp64' -`-mfp64' +'-mgp64' +'-mfp64' The register sizes are normally inferred from the ISA and ABI, but these flags force a certain group of registers to be treated as 64 - bits wide at all times. `-mgp64' controls the size of - general-purpose registers and `-mfp64' controls the size of + bits wide at all times. '-mgp64' controls the size of + general-purpose registers and '-mfp64' controls the size of floating-point registers. -`-mfpxx' +'-mfpxx' The register sizes are normally inferred from the ISA and ABI, but - using this flag in combination with `-mabi=32' enables an ABI + using this flag in combination with '-mabi=32' enables an ABI variant which will operate correctly with floating-point registers which are 32 or 64 bits wide. -`-modd-spreg' -`-mno-odd-spreg' +'-modd-spreg' +'-mno-odd-spreg' Enable use of floating-point operations on odd-numbered - single-precision registers when supported by the ISA. `-mfpxx' - implies `-mno-odd-spreg', otherwise the default is `-modd-spreg'. + single-precision registers when supported by the ISA. '-mfpxx' + implies '-mno-odd-spreg', otherwise the default is '-modd-spreg'. -`-mips16' -`-no-mips16' +'-mips16' +'-no-mips16' Generate code for the MIPS 16 processor. This is equivalent to - putting `.set mips16' at the start of the assembly file. - `-no-mips16' turns off this option. + putting '.set mips16' at the start of the assembly file. + '-no-mips16' turns off this option. -`-mmicromips' -`-mno-micromips' +'-mmicromips' +'-mno-micromips' Generate code for the microMIPS processor. This is equivalent to - putting `.set micromips' at the start of the assembly file. - `-mno-micromips' turns off this option. This is equivalent to - putting `.set nomicromips' at the start of the assembly file. + putting '.set micromips' at the start of the assembly file. + '-mno-micromips' turns off this option. This is equivalent to + putting '.set nomicromips' at the start of the assembly file. -`-msmartmips' -`-mno-smartmips' +'-msmartmips' +'-mno-smartmips' Enables the SmartMIPS extension to the MIPS32 instruction set. - This is equivalent to putting `.set smartmips' at the start of the - assembly file. `-mno-smartmips' turns off this option. + This is equivalent to putting '.set smartmips' at the start of the + assembly file. '-mno-smartmips' turns off this option. -`-mips3d' -`-no-mips3d' - Generate code for the MIPS-3D Application Specific Extension. - This tells the assembler to accept MIPS-3D instructions. - `-no-mips3d' turns off this option. +'-mips3d' +'-no-mips3d' + Generate code for the MIPS-3D Application Specific Extension. This + tells the assembler to accept MIPS-3D instructions. '-no-mips3d' + turns off this option. -`-mdmx' -`-no-mdmx' +'-mdmx' +'-no-mdmx' Generate code for the MDMX Application Specific Extension. This - tells the assembler to accept MDMX instructions. `-no-mdmx' turns + tells the assembler to accept MDMX instructions. '-no-mdmx' turns off this option. -`-mdsp' -`-mno-dsp' +'-mdsp' +'-mno-dsp' Generate code for the DSP Release 1 Application Specific Extension. This tells the assembler to accept DSP Release 1 instructions. - `-mno-dsp' turns off this option. + '-mno-dsp' turns off this option. -`-mdspr2' -`-mno-dspr2' +'-mdspr2' +'-mno-dspr2' Generate code for the DSP Release 2 Application Specific Extension. - This option implies `-mdsp'. This tells the assembler to accept - DSP Release 2 instructions. `-mno-dspr2' turns off this option. + This option implies '-mdsp'. This tells the assembler to accept + DSP Release 2 instructions. '-mno-dspr2' turns off this option. -`-mdspr3' -`-mno-dspr3' +'-mdspr3' +'-mno-dspr3' Generate code for the DSP Release 3 Application Specific Extension. - This option implies `-mdsp' and `-mdspr2'. This tells the - assembler to accept DSP Release 3 instructions. `-mno-dspr3' - turns off this option. - -`-mmsa' -`-mno-msa' - Generate code for the MIPS SIMD Architecture Extension. This - tells the assembler to accept MSA instructions. `-mno-msa' turns + This option implies '-mdsp' and '-mdspr2'. This tells the + assembler to accept DSP Release 3 instructions. '-mno-dspr3' turns off this option. -`-mxpa' -`-mno-xpa' +'-mmsa' +'-mno-msa' + Generate code for the MIPS SIMD Architecture Extension. This tells + the assembler to accept MSA instructions. '-mno-msa' turns off + this option. + +'-mxpa' +'-mno-xpa' Generate code for the MIPS eXtended Physical Address (XPA) Extension. This tells the assembler to accept XPA instructions. - `-mno-xpa' turns off this option. + '-mno-xpa' turns off this option. -`-mmt' -`-mno-mt' +'-mmt' +'-mno-mt' Generate code for the MT Application Specific Extension. This - tells the assembler to accept MT instructions. `-mno-mt' turns - off this option. + tells the assembler to accept MT instructions. '-mno-mt' turns off + this option. -`-mmcu' -`-mno-mcu' +'-mmcu' +'-mno-mcu' Generate code for the MCU Application Specific Extension. This - tells the assembler to accept MCU instructions. `-mno-mcu' turns + tells the assembler to accept MCU instructions. '-mno-mcu' turns off this option. -`-minsn32' -`-mno-insn32' +'-minsn32' +'-mno-insn32' Only use 32-bit instruction encodings when generating code for the microMIPS processor. This option inhibits the use of any 16-bit - instructions. This is equivalent to putting `.set insn32' at the - start of the assembly file. `-mno-insn32' turns off this option. - This is equivalent to putting `.set noinsn32' at the start of the - assembly file. By default `-mno-insn32' is selected, allowing all + instructions. This is equivalent to putting '.set insn32' at the + start of the assembly file. '-mno-insn32' turns off this option. + This is equivalent to putting '.set noinsn32' at the start of the + assembly file. By default '-mno-insn32' is selected, allowing all instructions to be used. -`--construct-floats' -`--no-construct-floats' - The `--no-construct-floats' option disables the construction of +'--construct-floats' +'--no-construct-floats' + The '--no-construct-floats' option disables the construction of double width floating point constants by loading the two halves of the value into the two single width floating point registers that - make up the double width register. By default - `--construct-floats' is selected, allowing construction of these - floating point constants. - -`--relax-branch' -`--no-relax-branch' - The `--relax-branch' option enables the relaxation of out-of-range - branches. By default `--no-relax-branch' is selected, causing any + make up the double width register. By default '--construct-floats' + is selected, allowing construction of these floating point + constants. + +'--relax-branch' +'--no-relax-branch' + The '--relax-branch' option enables the relaxation of out-of-range + branches. By default '--no-relax-branch' is selected, causing any out-of-range branches to produce an error. -`-mignore-branch-isa' -`-mno-ignore-branch-isa' +'-mignore-branch-isa' +'-mno-ignore-branch-isa' Ignore branch checks for invalid transitions between ISA modes. The semantics of branches does not provide for an ISA mode switch, so in most cases the ISA mode a branch has been encoded for has to be the same as the ISA mode of the branch's target label. - Therefore GAS has checks implemented that verify in branch - assembly that the two ISA modes match. `-mignore-branch-isa' - disables these checks. By default `-mno-ignore-branch-isa' is - selected, causing any invalid branch requiring a transition - between ISA modes to produce an error. - -`-mnan=ENCODING' - Select between the IEEE 754-2008 (`-mnan=2008') or the legacy - (`-mnan=legacy') NaN encoding format. The latter is the default. + Therefore GAS has checks implemented that verify in branch assembly + that the two ISA modes match. '-mignore-branch-isa' disables these + checks. By default '-mno-ignore-branch-isa' is selected, causing + any invalid branch requiring a transition between ISA modes to + produce an error. + +'-mnan=ENCODING' + Select between the IEEE 754-2008 ('-mnan=2008') or the legacy + ('-mnan=legacy') NaN encoding format. The latter is the default. -`--emulation=NAME' +'--emulation=NAME' This option was formerly used to switch between ELF and ECOFF output on targets like IRIX 5 that supported both. MIPS ECOFF support was removed in GAS 2.24, so the option now serves little purpose. It is retained for backwards compatibility. - The available configuration names are: `mipself', `mipslelf' and - `mipsbelf'. Choosing `mipself' now has no effect, since the output - is always ELF. `mipslelf' and `mipsbelf' select little- and - big-endian output respectively, but `-EL' and `-EB' are now the + The available configuration names are: 'mipself', 'mipslelf' and + 'mipsbelf'. Choosing 'mipself' now has no effect, since the output + is always ELF. 'mipslelf' and 'mipsbelf' select little- and + big-endian output respectively, but '-EL' and '-EB' are now the preferred options instead. -`-nocpp' - `as' ignores this option. It is accepted for compatibility with +'-nocpp' + 'as' ignores this option. It is accepted for compatibility with the native tools. -`--trap' -`--no-trap' -`--break' -`--no-break' +'--trap' +'--no-trap' +'--break' +'--no-break' Control how to deal with multiplication overflow and division by - zero. `--trap' or `--no-break' (which are synonyms) take a trap + zero. '--trap' or '--no-break' (which are synonyms) take a trap exception (and only work for Instruction Set Architecture level 2 - and higher); `--break' or `--no-trap' (also synonyms, and the + and higher); '--break' or '--no-trap' (also synonyms, and the default) take a break exception. -`-n' - When this option is used, `as' will issue a warning every time it +'-n' + When this option is used, 'as' will issue a warning every time it generates a nop instruction from a macro. The following options are available when as is configured for an MCore processor. -`-jsri2bsr' -`-nojsri2bsr' +'-jsri2bsr' +'-nojsri2bsr' Enable or disable the JSRI to BSR transformation. By default this - is enabled. The command line option `-nojsri2bsr' can be used to + is enabled. The command line option '-nojsri2bsr' can be used to disable it. -`-sifilter' -`-nosifilter' - Enable or disable the silicon filter behaviour. By default this - is disabled. The default can be overridden by the `-sifilter' - command line option. +'-sifilter' +'-nosifilter' + Enable or disable the silicon filter behaviour. By default this is + disabled. The default can be overridden by the '-sifilter' command + line option. -`-relax' +'-relax' Alter jump instructions for long displacements. -`-mcpu=[210|340]' +'-mcpu=[210|340]' Select the cpu type on the target hardware. This controls which instructions can be assembled. -`-EB' +'-EB' Assemble for a big endian target. -`-EL' +'-EL' Assemble for a little endian target. - *Note Meta Options::, for the options available when as is configured for a Meta processor. @@ -1154,27 +1130,22 @@ The following options are available when as is configured for the s390 processor family. -`-m31' -`-m64' +'-m31' +'-m64' Select the word size, either 31/32 bits or 64 bits. - -`-mesa' - -`-mzarch' +'-mesa' +'-mzarch' Select the architecture mode, either the Enterprise System Architecture (esa) or the z/Architecture mode (zarch). - -`-march=PROCESSOR' - Specify which s390 processor variant is the target, `g5' (or - `arch3'), `g6', `z900' (or `arch5'), `z990' (or `arch6'), - `z9-109', `z9-ec' (or `arch7'), `z10' (or `arch8'), `z196' (or - `arch9'), `zEC12' (or `arch10'), `z13' (or `arch11'), or `arch12'. - -`-mregnames' -`-mno-regnames' +'-march=PROCESSOR' + Specify which s390 processor variant is the target, 'g5' (or + 'arch3'), 'g6', 'z900' (or 'arch5'), 'z990' (or 'arch6'), 'z9-109', + 'z9-ec' (or 'arch7'), 'z10' (or 'arch8'), 'z196' (or 'arch9'), + 'zEC12' (or 'arch10'), 'z13' (or 'arch11'), or 'arch12'. +'-mregnames' +'-mno-regnames' Allow or disallow symbolic names for registers. - -`-mwarn-areg-zero' +'-mwarn-areg-zero' Warn whenever the operand for a base or index register has been specified but evaluates to zero. @@ -1192,37 +1163,30 @@ The following options are available when as is configured for a Z80 family processor. -`-z80' +'-z80' Assemble for Z80 processor. - -`-r800' +'-r800' Assemble for R800 processor. - -`-ignore-undocumented-instructions' -`-Wnud' +'-ignore-undocumented-instructions' +'-Wnud' Assemble undocumented Z80 instructions that also work on R800 without warning. - -`-ignore-unportable-instructions' -`-Wnup' +'-ignore-unportable-instructions' +'-Wnup' Assemble all undocumented Z80 instructions without warning. - -`-warn-undocumented-instructions' -`-Wud' - Issue a warning for undocumented Z80 instructions that also work - on R800. - -`-warn-unportable-instructions' -`-Wup' +'-warn-undocumented-instructions' +'-Wud' + Issue a warning for undocumented Z80 instructions that also work on + R800. +'-warn-unportable-instructions' +'-Wup' Issue a warning for undocumented Z80 instructions that do not work on R800. - -`-forbid-undocumented-instructions' -`-Fud' +'-forbid-undocumented-instructions' +'-Fud' Treat all undocumented instructions as errors. - -`-forbid-unportable-instructions' -`-Fup' +'-forbid-unportable-instructions' +'-Fup' Treat undocumented Z80 instructions that do not work on R800 as errors. @@ -1243,9 +1207,9 @@ ============================ This manual is intended to describe what you need to know to use GNU -`as'. We cover the syntax expected in source files, including notation -for symbols, constants, and expressions; the directives that `as' -understands; and of course how to invoke `as'. +'as'. We cover the syntax expected in source files, including notation +for symbols, constants, and expressions; the directives that 'as' +understands; and of course how to invoke 'as'. This manual also describes some of the machine-dependent features of various flavors of the assembler. @@ -1264,24 +1228,24 @@ 1.2 The GNU Assembler ===================== -GNU `as' is really a family of assemblers. If you use (or have used) +GNU 'as' is really a family of assemblers. If you use (or have used) the GNU assembler on one architecture, you should find a fairly similar environment when you use it on another architecture. Each version has much in common with the others, including object file formats, most assembler directives (often called "pseudo-ops") and assembler syntax. - `as' is primarily intended to assemble the output of the GNU C -compiler `gcc' for use by the linker `ld'. Nevertheless, we've tried -to make `as' assemble correctly everything that other assemblers for -the same machine would assemble. Any exceptions are documented -explicitly (*note Machine Dependencies::). This doesn't mean `as' -always uses the same syntax as another assembler for the same -architecture; for example, we know of several incompatible versions of -680x0 assembly language syntax. + 'as' is primarily intended to assemble the output of the GNU C +compiler 'gcc' for use by the linker 'ld'. Nevertheless, we've tried to +make 'as' assemble correctly everything that other assemblers for the +same machine would assemble. Any exceptions are documented explicitly +(*note Machine Dependencies::). This doesn't mean 'as' always uses the +same syntax as another assembler for the same architecture; for example, +we know of several incompatible versions of 680x0 assembly language +syntax. - Unlike older assemblers, `as' is designed to assemble a source + Unlike older assemblers, 'as' is designed to assemble a source program in one pass of the source file. This has a subtle impact on the -`.org' directive (*note `.org': Org.). +'.org' directive (*note '.org': Org.).  File: as.info, Node: Object Formats, Next: Command Line, Prev: GNU Assembler, Up: Overview @@ -1301,23 +1265,23 @@ 1.4 Command Line ================ -After the program name `as', the command line may contain options and +After the program name 'as', the command line may contain options and file names. Options may appear in any order, and may be before, after, or between file names. The order of file names is significant. - `--' (two hyphens) by itself names the standard input file -explicitly, as one of the files for `as' to assemble. + '--' (two hyphens) by itself names the standard input file +explicitly, as one of the files for 'as' to assemble. - Except for `--' any command line argument that begins with a hyphen -(`-') is an option. Each option changes the behavior of `as'. No -option changes the way another option works. An option is a `-' + Except for '--' any command line argument that begins with a hyphen +('-') is an option. Each option changes the behavior of 'as'. No +option changes the way another option works. An option is a '-' followed by one or more letters; the case of the letter is important. All options are optional. Some options expect exactly one file name to follow them. The file name may either immediately follow the option's letter (compatible with -older assemblers) or it may be the next command argument (GNU -standard). These two command lines are equivalent: +older assemblers) or it may be the next command argument (GNU standard). +These two command lines are equivalent: as -o my-object-file.o mumble.s as -omy-object-file.o mumble.s @@ -1329,30 +1293,30 @@ =============== We use the phrase "source program", abbreviated "source", to describe -the program input to one run of `as'. The program may be in one or -more files; how the source is partitioned into files doesn't change the +the program input to one run of 'as'. The program may be in one or more +files; how the source is partitioned into files doesn't change the meaning of the source. The source program is a concatenation of the text in all the files, in the order specified. - Each time you run `as' it assembles exactly one source program. The + Each time you run 'as' it assembles exactly one source program. The source program is made up of one or more files. (The standard input is also a file.) - You give `as' a command line that has zero or more input file names. -The input files are read (from left file name to right). A command -line argument (in any position) that has no special meaning is taken to -be an input file name. - - If you give `as' no file names it attempts to read one input file -from the `as' standard input, which is normally your terminal. You may -have to type to tell `as' there is no more program to assemble. + You give 'as' a command line that has zero or more input file names. +The input files are read (from left file name to right). A command line +argument (in any position) that has no special meaning is taken to be an +input file name. + + If you give 'as' no file names it attempts to read one input file +from the 'as' standard input, which is normally your terminal. You may +have to type to tell 'as' there is no more program to assemble. - Use `--' if you need to explicitly name the standard input file in + Use '--' if you need to explicitly name the standard input file in your command line. - If the source is empty, `as' produces a small, empty object file. + If the source is empty, 'as' produces a small, empty object file. Filenames and Line-numbers -------------------------- @@ -1363,14 +1327,14 @@ "logical" file. *Note Error and Warning Messages: Errors. "Physical files" are those files named in the command line given to -`as'. +'as'. "Logical files" are simply names declared explicitly by assembler -directives; they bear no relation to physical files. Logical file -names help error messages reflect the original source file, when `as' -source is itself synthesized from other files. `as' understands the -`#' directives emitted by the `gcc' preprocessor. See also *Note -`.file': File. +directives; they bear no relation to physical files. Logical file names +help error messages reflect the original source file, when 'as' source +is itself synthesized from other files. 'as' understands the '#' +directives emitted by the 'gcc' preprocessor. See also *note '.file': +File.  File: as.info, Node: Object, Next: Errors, Prev: Input Files, Up: Overview @@ -1378,19 +1342,19 @@ 1.6 Output (Object) File ======================== -Every time you run `as' it produces an output file, which is your +Every time you run 'as' it produces an output file, which is your assembly language program translated into numbers. This file is the -object file. Its default name is `a.out'. You can give it another -name by using the `-o' option. Conventionally, object file names end -with `.o'. The default name is used for historical reasons: older -assemblers were capable of assembling self-contained programs directly -into a runnable program. (For some formats, this isn't currently -possible, but it can be done for the `a.out' format.) - - The object file is meant for input to the linker `ld'. It contains -assembled program code, information to help `ld' integrate the -assembled program into a runnable file, and (optionally) symbolic -information for the debugger. +object file. Its default name is 'a.out'. You can give it another name +by using the '-o' option. Conventionally, object file names end with +'.o'. The default name is used for historical reasons: older assemblers +were capable of assembling self-contained programs directly into a +runnable program. (For some formats, this isn't currently possible, but +it can be done for the 'a.out' format.) + + The object file is meant for input to the linker 'ld'. It contains +assembled program code, information to help 'ld' integrate the assembled +program into a runnable file, and (optionally) symbolic information for +the debugger.  File: as.info, Node: Errors, Prev: Object, Up: Overview @@ -1398,9 +1362,9 @@ 1.7 Error and Warning Messages ============================== -`as' may write warnings and error messages to the standard error file -(usually your terminal). This should not happen when a compiler runs -`as' automatically. Warnings report an assumption made so that `as' +'as' may write warnings and error messages to the standard error file +(usually your terminal). This should not happen when a compiler runs +'as' automatically. Warnings report an assumption made so that 'as' could keep assembling a flawed program; errors report a grave problem that stops the assembly. @@ -1409,13 +1373,13 @@ file_name:NNN:Warning Message Text (where NNN is a line number). If both a logical file name (*note -`.file': File.) and a logical line number (*note `.line': Line.) have +'.file': File.) and a logical line number (*note '.line': Line.) have been given then they will be used, otherwise the file name and line number in the current assembler source file will be used. The message text is intended to be self explanatory (in the grand Unix tradition). - Note the file name must be set via the logical version of the `.file' -directive, not the DWARF2 version of the `.file' directive. For + Note the file name must be set via the logical version of the '.file' +directive, not the DWARF2 version of the '.file' directive. For example: .file 2 "bar.c" @@ -1445,230 +1409,228 @@ ********************** This chapter describes command-line options available in _all_ versions -of the GNU assembler; see *Note Machine Dependencies::, for options +of the GNU assembler; see *note Machine Dependencies::, for options specific to particular machine architectures. - If you are invoking `as' via the GNU C compiler, you can use the -`-Wa' option to pass arguments through to the assembler. The assembler -arguments must be separated from each other (and the `-Wa') by commas. + If you are invoking 'as' via the GNU C compiler, you can use the +'-Wa' option to pass arguments through to the assembler. The assembler +arguments must be separated from each other (and the '-Wa') by commas. For example: gcc -c -g -O -Wa,-alh,-L file.c -This passes two options to the assembler: `-alh' (emit a listing to -standard output with high-level and assembly source) and `-L' (retain +This passes two options to the assembler: '-alh' (emit a listing to +standard output with high-level and assembly source) and '-L' (retain local symbols in the symbol table). - Usually you do not need to use this `-Wa' mechanism, since many + Usually you do not need to use this '-Wa' mechanism, since many compiler command-line options are automatically passed to the assembler -by the compiler. (You can call the GNU compiler driver with the `-v' -option to see precisely what options it passes to each compilation -pass, including the assembler.) +by the compiler. (You can call the GNU compiler driver with the '-v' +option to see precisely what options it passes to each compilation pass, +including the assembler.) * Menu: * a:: -a[cdghlns] enable listings -* alternate:: --alternate enable alternate macro syntax +* alternate:: -alternate enable alternate macro syntax * D:: -D for compatibility * f:: -f to work faster * I:: -I for .include search path - * K:: -K for difference tables * L:: -L to retain local symbols -* listing:: --listing-XXX to configure listing output -* M:: -M or --mri to assemble in MRI compatibility mode -* MD:: --MD for dependency tracking -* no-pad-sections:: --no-pad-sections to stop section padding +* listing:: -listing-XXX to configure listing output +* M:: -M or -mri to assemble in MRI compatibility mode +* MD:: -MD for dependency tracking +* no-pad-sections:: -no-pad-sections to stop section padding * o:: -o to name the object file * R:: -R to join data and text sections -* statistics:: --statistics to see statistics about assembly -* traditional-format:: --traditional-format for compatible output +* statistics:: -statistics to see statistics about assembly +* traditional-format:: -traditional-format for compatible output * v:: -v to announce version -* W:: -W, --no-warn, --warn, --fatal-warnings to control warnings +* W:: -W, -no-warn, -warn, -fatal-warnings to control warnings * Z:: -Z to make object file even after errors  File: as.info, Node: a, Next: alternate, Up: Invoking -2.1 Enable Listings: `-a[cdghlns]' +2.1 Enable Listings: '-a[cdghlns]' ================================== -These options enable listing output from the assembler. By itself, -`-a' requests high-level, assembly, and symbols listing. You can use -other letters to select specific options for the list: `-ah' requests a -high-level language listing, `-al' requests an output-program assembly -listing, and `-as' requests a symbol table listing. High-level -listings require that a compiler debugging option like `-g' be used, -and that assembly listings (`-al') be requested also. +These options enable listing output from the assembler. By itself, '-a' +requests high-level, assembly, and symbols listing. You can use other +letters to select specific options for the list: '-ah' requests a +high-level language listing, '-al' requests an output-program assembly +listing, and '-as' requests a symbol table listing. High-level listings +require that a compiler debugging option like '-g' be used, and that +assembly listings ('-al') be requested also. - Use the `-ag' option to print a first section with general assembly + Use the '-ag' option to print a first section with general assembly information, like as version, switches passed, or time stamp. - Use the `-ac' option to omit false conditionals from a listing. Any -lines which are not assembled because of a false `.if' (or `.ifdef', or -any other conditional), or a true `.if' followed by an `.else', will be + Use the '-ac' option to omit false conditionals from a listing. Any +lines which are not assembled because of a false '.if' (or '.ifdef', or +any other conditional), or a true '.if' followed by an '.else', will be omitted from the listing. - Use the `-ad' option to omit debugging directives from the listing. + Use the '-ad' option to omit debugging directives from the listing. Once you have specified one of these options, you can further control -listing output and its appearance using the directives `.list', -`.nolist', `.psize', `.eject', `.title', and `.sbttl'. The `-an' -option turns off all forms processing. If you do not request listing -output with one of the `-a' options, the listing-control directives -have no effect. +listing output and its appearance using the directives '.list', +'.nolist', '.psize', '.eject', '.title', and '.sbttl'. The '-an' option +turns off all forms processing. If you do not request listing output +with one of the '-a' options, the listing-control directives have no +effect. - The letters after `-a' may be combined into one option, _e.g._, -`-aln'. + The letters after '-a' may be combined into one option, _e.g._, +'-aln'. Note if the assembler source is coming from the standard input (e.g., -because it is being created by `gcc' and the `-pipe' command line switch +because it is being created by 'gcc' and the '-pipe' command line switch is being used) then the listing will not contain any comments or -preprocessor directives. This is because the listing code buffers -input source lines from stdin only after they have been preprocessed by -the assembler. This reduces memory usage and makes the code more -efficient. +preprocessor directives. This is because the listing code buffers input +source lines from stdin only after they have been preprocessed by the +assembler. This reduces memory usage and makes the code more efficient.  File: as.info, Node: alternate, Next: D, Prev: a, Up: Invoking -2.2 `--alternate' +2.2 '--alternate' ================= -Begin in alternate macro mode, see *Note `.altmacro': Altmacro. +Begin in alternate macro mode, see *note '.altmacro': Altmacro.  File: as.info, Node: D, Next: f, Prev: alternate, Up: Invoking -2.3 `-D' +2.3 '-D' ======== This option has no effect whatsoever, but it is accepted to make it more -likely that scripts written for other assemblers also work with `as'. +likely that scripts written for other assemblers also work with 'as'.  File: as.info, Node: f, Next: I, Prev: D, Up: Invoking -2.4 Work Faster: `-f' +2.4 Work Faster: '-f' ===================== -`-f' should only be used when assembling programs written by a -(trusted) compiler. `-f' stops the assembler from doing whitespace and -comment preprocessing on the input file(s) before assembling them. -*Note Preprocessing: Preprocessing. - - _Warning:_ if you use `-f' when the files actually need to be - preprocessed (if they contain comments, for example), `as' does - not work correctly. +'-f' should only be used when assembling programs written by a (trusted) +compiler. '-f' stops the assembler from doing whitespace and comment +preprocessing on the input file(s) before assembling them. *Note +Preprocessing: Preprocessing. + + _Warning:_ if you use '-f' when the files actually need to be + preprocessed (if they contain comments, for example), 'as' does not + work correctly.  File: as.info, Node: I, Next: K, Prev: f, Up: Invoking -2.5 `.include' Search Path: `-I' PATH +2.5 '.include' Search Path: '-I' PATH ===================================== -Use this option to add a PATH to the list of directories `as' searches -for files specified in `.include' directives (*note `.include': -Include.). You may use `-I' as many times as necessary to include a +Use this option to add a PATH to the list of directories 'as' searches +for files specified in '.include' directives (*note '.include': +Include.). You may use '-I' as many times as necessary to include a variety of paths. The current working directory is always searched -first; after that, `as' searches any `-I' directories in the same order +first; after that, 'as' searches any '-I' directories in the same order as they were specified (left to right) on the command line.  File: as.info, Node: K, Next: L, Prev: I, Up: Invoking -2.6 Difference Tables: `-K' +2.6 Difference Tables: '-K' =========================== -`as' sometimes alters the code emitted for directives of the form -`.word SYM1-SYM2'. *Note `.word': Word. You can use the `-K' option -if you want a warning issued when this is done. +'as' sometimes alters the code emitted for directives of the form '.word +SYM1-SYM2'. *Note '.word': Word. You can use the '-K' option if you +want a warning issued when this is done.  File: as.info, Node: L, Next: listing, Prev: K, Up: Invoking -2.7 Include Local Symbols: `-L' +2.7 Include Local Symbols: '-L' =============================== Symbols beginning with system-specific local label prefixes, typically -`.L' for ELF systems or `L' for traditional a.out systems, are called +'.L' for ELF systems or 'L' for traditional a.out systems, are called "local symbols". *Note Symbol Names::. Normally you do not see such symbols when debugging, because they are intended for the use of programs (like compilers) that compose assembler programs, not for your -notice. Normally both `as' and `ld' discard such symbols, so you do -not normally debug with them. +notice. Normally both 'as' and 'ld' discard such symbols, so you do not +normally debug with them. - This option tells `as' to retain those local symbols in the object -file. Usually if you do this you also tell the linker `ld' to preserve + This option tells 'as' to retain those local symbols in the object +file. Usually if you do this you also tell the linker 'ld' to preserve those symbols.  File: as.info, Node: listing, Next: M, Prev: L, Up: Invoking -2.8 Configuring listing output: `--listing' +2.8 Configuring listing output: '--listing' =========================================== -The listing feature of the assembler can be enabled via the command -line switch `-a' (*note a::). This feature combines the input source -file(s) with a hex dump of the corresponding locations in the output -object file, and displays them as a listing file. The format of this -listing can be controlled by directives inside the assembler source -(i.e., `.list' (*note List::), `.title' (*note Title::), `.sbttl' -(*note Sbttl::), `.psize' (*note Psize::), and `.eject' (*note Eject::) -and also by the following switches: - -`--listing-lhs-width=`number'' - Sets the maximum width, in words, of the first line of the hex - byte dump. This dump appears on the left hand side of the listing +The listing feature of the assembler can be enabled via the command line +switch '-a' (*note a::). This feature combines the input source file(s) +with a hex dump of the corresponding locations in the output object +file, and displays them as a listing file. The format of this listing +can be controlled by directives inside the assembler source (i.e., +'.list' (*note List::), '.title' (*note Title::), '.sbttl' (*note +Sbttl::), '.psize' (*note Psize::), and '.eject' (*note Eject::) and +also by the following switches: + +'--listing-lhs-width='number'' + Sets the maximum width, in words, of the first line of the hex byte + dump. This dump appears on the left hand side of the listing output. -`--listing-lhs-width2=`number'' +'--listing-lhs-width2='number'' Sets the maximum width, in words, of any further lines of the hex byte dump for a given input source line. If this value is not - specified, it defaults to being the same as the value specified - for `--listing-lhs-width'. If neither switch is used the default - is to one. + specified, it defaults to being the same as the value specified for + '--listing-lhs-width'. If neither switch is used the default is to + one. -`--listing-rhs-width=`number'' +'--listing-rhs-width='number'' Sets the maximum width, in characters, of the source line that is displayed alongside the hex dump. The default value for this parameter is 100. The source line is displayed on the right hand side of the listing output. -`--listing-cont-lines=`number'' - Sets the maximum number of continuation lines of hex dump that - will be displayed for a given single line of source input. The - default value is 4. +'--listing-cont-lines='number'' + Sets the maximum number of continuation lines of hex dump that will + be displayed for a given single line of source input. The default + value is 4.  File: as.info, Node: M, Next: MD, Prev: listing, Up: Invoking -2.9 Assemble in MRI Compatibility Mode: `-M' +2.9 Assemble in MRI Compatibility Mode: '-M' ============================================ -The `-M' or `--mri' option selects MRI compatibility mode. This -changes the syntax and pseudo-op handling of `as' to make it compatible -with the `ASM68K' or the `ASM960' (depending upon the configured -target) assembler from Microtec Research. The exact nature of the MRI -syntax will not be documented here; see the MRI manuals for more -information. Note in particular that the handling of macros and macro -arguments is somewhat different. The purpose of this option is to -permit assembling existing MRI assembler code using `as'. - - The MRI compatibility is not complete. Certain operations of the -MRI assembler depend upon its object file format, and can not be -supported using other object file formats. Supporting these would -require enhancing each object file format individually. These are: +The '-M' or '--mri' option selects MRI compatibility mode. This changes +the syntax and pseudo-op handling of 'as' to make it compatible with the +'ASM68K' or the 'ASM960' (depending upon the configured target) +assembler from Microtec Research. The exact nature of the MRI syntax +will not be documented here; see the MRI manuals for more information. +Note in particular that the handling of macros and macro arguments is +somewhat different. The purpose of this option is to permit assembling +existing MRI assembler code using 'as'. + + The MRI compatibility is not complete. Certain operations of the MRI +assembler depend upon its object file format, and can not be supported +using other object file formats. Supporting these would require +enhancing each object file format individually. These are: * global symbols in common section - The m68k MRI assembler supports common sections which are merged - by the linker. Other object file formats do not support this. - `as' handles common sections by treating them as a single common - symbol. It permits local symbols to be defined within a common - section, but it can not support global symbols, since it has no - way to describe them. + The m68k MRI assembler supports common sections which are merged by + the linker. Other object file formats do not support this. 'as' + handles common sections by treating them as a single common symbol. + It permits local symbols to be defined within a common section, but + it can not support global symbols, since it has no way to describe + them. * complex relocations @@ -1677,31 +1639,31 @@ or more sections. These are not support by other object file formats. - * `END' pseudo-op specifying start address + * 'END' pseudo-op specifying start address - The MRI `END' pseudo-op permits the specification of a start + The MRI 'END' pseudo-op permits the specification of a start address. This is not supported by other object file formats. The - start address may instead be specified using the `-e' option to - the linker, or in a linker script. + start address may instead be specified using the '-e' option to the + linker, or in a linker script. - * `IDNT', `.ident' and `NAME' pseudo-ops + * 'IDNT', '.ident' and 'NAME' pseudo-ops - The MRI `IDNT', `.ident' and `NAME' pseudo-ops assign a module - name to the output file. This is not supported by other object - file formats. - - * `ORG' pseudo-op - - The m68k MRI `ORG' pseudo-op begins an absolute section at a given - address. This differs from the usual `as' `.org' pseudo-op, which - changes the location within the current section. Absolute - sections are not supported by other object file formats. The - address of a section may be assigned within a linker script. + The MRI 'IDNT', '.ident' and 'NAME' pseudo-ops assign a module name + to the output file. This is not supported by other object file + formats. + + * 'ORG' pseudo-op + + The m68k MRI 'ORG' pseudo-op begins an absolute section at a given + address. This differs from the usual 'as' '.org' pseudo-op, which + changes the location within the current section. Absolute sections + are not supported by other object file formats. The address of a + section may be assigned within a linker script. There are some other features of the MRI assembler which are not -supported by `as', typically either because they are difficult or -because they seem of little consequence. Some of these may be -supported in future releases. +supported by 'as', typically either because they are difficult or +because they seem of little consequence. Some of these may be supported +in future releases. * EBCDIC strings @@ -1710,76 +1672,75 @@ * packed binary coded decimal Packed binary coded decimal is not supported. This means that the - `DC.P' and `DCB.P' pseudo-ops are not supported. + 'DC.P' and 'DCB.P' pseudo-ops are not supported. - * `FEQU' pseudo-op + * 'FEQU' pseudo-op - The m68k `FEQU' pseudo-op is not supported. + The m68k 'FEQU' pseudo-op is not supported. - * `NOOBJ' pseudo-op + * 'NOOBJ' pseudo-op - The m68k `NOOBJ' pseudo-op is not supported. + The m68k 'NOOBJ' pseudo-op is not supported. - * `OPT' branch control options + * 'OPT' branch control options - The m68k `OPT' branch control options--`B', `BRS', `BRB', `BRL', - and `BRW'--are ignored. `as' automatically relaxes all branches, + The m68k 'OPT' branch control options--'B', 'BRS', 'BRB', 'BRL', + and 'BRW'--are ignored. 'as' automatically relaxes all branches, whether forward or backward, to an appropriate size, so these options serve no purpose. - * `OPT' list control options + * 'OPT' list control options - The following m68k `OPT' list control options are ignored: `C', - `CEX', `CL', `CRE', `E', `G', `I', `M', `MEX', `MC', `MD', `X'. + The following m68k 'OPT' list control options are ignored: 'C', + 'CEX', 'CL', 'CRE', 'E', 'G', 'I', 'M', 'MEX', 'MC', 'MD', 'X'. - * other `OPT' options + * other 'OPT' options - The following m68k `OPT' options are ignored: `NEST', `O', `OLD', - `OP', `P', `PCO', `PCR', `PCS', `R'. + The following m68k 'OPT' options are ignored: 'NEST', 'O', 'OLD', + 'OP', 'P', 'PCO', 'PCR', 'PCS', 'R'. - * `OPT' `D' option is default + * 'OPT' 'D' option is default - The m68k `OPT' `D' option is the default, unlike the MRI assembler. - `OPT NOD' may be used to turn it off. + The m68k 'OPT' 'D' option is the default, unlike the MRI assembler. + 'OPT NOD' may be used to turn it off. - * `XREF' pseudo-op. + * 'XREF' pseudo-op. - The m68k `XREF' pseudo-op is ignored. + The m68k 'XREF' pseudo-op is ignored. - * `.debug' pseudo-op + * '.debug' pseudo-op - The i960 `.debug' pseudo-op is not supported. + The i960 '.debug' pseudo-op is not supported. - * `.extended' pseudo-op + * '.extended' pseudo-op - The i960 `.extended' pseudo-op is not supported. + The i960 '.extended' pseudo-op is not supported. - * `.list' pseudo-op. + * '.list' pseudo-op. - The various options of the i960 `.list' pseudo-op are not + The various options of the i960 '.list' pseudo-op are not supported. - * `.optimize' pseudo-op - - The i960 `.optimize' pseudo-op is not supported. + * '.optimize' pseudo-op - * `.output' pseudo-op + The i960 '.optimize' pseudo-op is not supported. - The i960 `.output' pseudo-op is not supported. + * '.output' pseudo-op - * `.setreal' pseudo-op + The i960 '.output' pseudo-op is not supported. - The i960 `.setreal' pseudo-op is not supported. + * '.setreal' pseudo-op + The i960 '.setreal' pseudo-op is not supported.  File: as.info, Node: MD, Next: no-pad-sections, Prev: M, Up: Invoking -2.10 Dependency Tracking: `--MD' +2.10 Dependency Tracking: '--MD' ================================ -`as' can generate a dependency file for the file it creates. This file -consists of a single rule suitable for `make' describing the +'as' can generate a dependency file for the file it creates. This file +consists of a single rule suitable for 'make' describing the dependencies of the main source file. The rule is written to the file named in its argument. @@ -1794,114 +1755,114 @@ Normally the assembler will pad the end of each output section up to its alignment boundary. But this can waste space, which can be significant -on memory constrained targets. So the `--no-pad-sections' option will +on memory constrained targets. So the '--no-pad-sections' option will disable this behaviour.  File: as.info, Node: o, Next: R, Prev: no-pad-sections, Up: Invoking -2.12 Name the Object File: `-o' +2.12 Name the Object File: '-o' =============================== -There is always one object file output when you run `as'. By default -it has the name `a.out' (or `b.out', for Intel 960 targets only). You -use this option (which takes exactly one filename) to give the object -file a different name. +There is always one object file output when you run 'as'. By default it +has the name 'a.out' (or 'b.out', for Intel 960 targets only). You use +this option (which takes exactly one filename) to give the object file a +different name. - Whatever the object file is called, `as' overwrites any existing -file of the same name. + Whatever the object file is called, 'as' overwrites any existing file +of the same name.  File: as.info, Node: R, Next: statistics, Prev: o, Up: Invoking -2.13 Join Data and Text Sections: `-R' +2.13 Join Data and Text Sections: '-R' ====================================== -`-R' tells `as' to write the object file as if all data-section data +'-R' tells 'as' to write the object file as if all data-section data lives in the text section. This is only done at the very last moment: your binary data are the same, but data section parts are relocated differently. The data section part of your object file is zero bytes long because all its bytes are appended to the text section. (*Note Sections and Relocation: Sections.) - When you specify `-R' it would be possible to generate shorter + When you specify '-R' it would be possible to generate shorter address displacements (because we do not have to cross between text and data section). We refrain from doing this simply for compatibility with -older versions of `as'. In future, `-R' may work this way. +older versions of 'as'. In future, '-R' may work this way. - When `as' is configured for COFF or ELF output, this option is only -useful if you use sections named `.text' and `.data'. + When 'as' is configured for COFF or ELF output, this option is only +useful if you use sections named '.text' and '.data'. - `-R' is not supported for any of the HPPA targets. Using `-R' -generates a warning from `as'. + '-R' is not supported for any of the HPPA targets. Using '-R' +generates a warning from 'as'.  File: as.info, Node: statistics, Next: traditional-format, Prev: R, Up: Invoking -2.14 Display Assembly Statistics: `--statistics' +2.14 Display Assembly Statistics: '--statistics' ================================================ -Use `--statistics' to display two statistics about the resources used by -`as': the maximum amount of space allocated during the assembly (in +Use '--statistics' to display two statistics about the resources used by +'as': the maximum amount of space allocated during the assembly (in bytes), and the total execution time taken for the assembly (in CPU seconds).  File: as.info, Node: traditional-format, Next: v, Prev: statistics, Up: Invoking -2.15 Compatible Output: `--traditional-format' +2.15 Compatible Output: '--traditional-format' ============================================== -For some targets, the output of `as' is different in some ways from the -output of some existing assembler. This switch requests `as' to use -the traditional format instead. +For some targets, the output of 'as' is different in some ways from the +output of some existing assembler. This switch requests 'as' to use the +traditional format instead. - For example, it disables the exception frame optimizations which -`as' normally does by default on `gcc' output. + For example, it disables the exception frame optimizations which 'as' +normally does by default on 'gcc' output.  File: as.info, Node: v, Next: W, Prev: traditional-format, Up: Invoking -2.16 Announce Version: `-v' +2.16 Announce Version: '-v' =========================== You can find out what version of as is running by including the option -`-v' (which you can also spell as `-version') on the command line. +'-v' (which you can also spell as '-version') on the command line.  File: as.info, Node: W, Next: Z, Prev: v, Up: Invoking -2.17 Control Warnings: `-W', `--warn', `--no-warn', `--fatal-warnings' +2.17 Control Warnings: '-W', '--warn', '--no-warn', '--fatal-warnings' ====================================================================== -`as' should never give a warning or error message when assembling -compiler output. But programs written by people often cause `as' to -give a warning that a particular assumption was made. All such -warnings are directed to the standard error file. +'as' should never give a warning or error message when assembling +compiler output. But programs written by people often cause 'as' to +give a warning that a particular assumption was made. All such warnings +are directed to the standard error file. - If you use the `-W' and `--no-warn' options, no warnings are issued. + If you use the '-W' and '--no-warn' options, no warnings are issued. This only affects the warning messages: it does not change any -particular of how `as' assembles your file. Errors, which stop the +particular of how 'as' assembles your file. Errors, which stop the assembly, are still reported. - If you use the `--fatal-warnings' option, `as' considers files that + If you use the '--fatal-warnings' option, 'as' considers files that generate warnings to be in error. - You can switch these options off again by specifying `--warn', which + You can switch these options off again by specifying '--warn', which causes warnings to be output as usual.  File: as.info, Node: Z, Prev: W, Up: Invoking -2.18 Generate Object File in Spite of Errors: `-Z' +2.18 Generate Object File in Spite of Errors: '-Z' ================================================== -After an error message, `as' normally produces no output. If for some -reason you are interested in object file output even after `as' gives -an error message on your program, use the `-Z' option. If there are -any errors, `as' continues anyways, and writes an object file after a -final warning message of the form `N errors, M warnings, generating bad -object file.' +After an error message, 'as' normally produces no output. If for some +reason you are interested in object file output even after 'as' gives an +error message on your program, use the '-Z' option. If there are any +errors, 'as' continues anyways, and writes an object file after a final +warning message of the form 'N errors, M warnings, generating bad object +file.'  File: as.info, Node: Syntax, Next: Sections, Prev: Invoking, Up: Top @@ -1910,8 +1871,8 @@ ******** This chapter describes the machine-independent syntax allowed in a -source file. `as' syntax is similar to what many other assemblers use; -it is inspired by the BSD 4.2 assembler, except that `as' does not +source file. 'as' syntax is similar to what many other assemblers use; +it is inspired by the BSD 4.2 assembler, except that 'as' does not assemble Vax bit-fields. * Menu: @@ -1929,7 +1890,7 @@ 3.1 Preprocessing ================= -The `as' internal preprocessor: +The 'as' internal preprocessor: * adjusts and removes extra whitespace. It leaves one space or tab before the keywords on a line, and turns any other whitespace on the line into a single space. @@ -1941,23 +1902,22 @@ It does not do macro processing, include file handling, or anything else you may get from your C compiler's preprocessor. You can do -include file processing with the `.include' directive (*note -`.include': Include.). You can use the GNU C compiler driver to get -other "CPP" style preprocessing by giving the input file a `.S' suffix. -*Note Options Controlling the Kind of Output: (gcc info)Overall -Options. +include file processing with the '.include' directive (*note '.include': +Include.). You can use the GNU C compiler driver to get other "CPP" +style preprocessing by giving the input file a '.S' suffix. *Note +Options Controlling the Kind of Output: (gcc info)Overall Options. Excess whitespace, comments, and character constants cannot be used in the portions of the input text that are not preprocessed. - If the first line of an input file is `#NO_APP' or if you use the -`-f' option, whitespace and comments are not removed from the input + If the first line of an input file is '#NO_APP' or if you use the +'-f' option, whitespace and comments are not removed from the input file. Within an input file, you can ask for whitespace and comment -removal in specific portions of the by putting a line that says `#APP' +removal in specific portions of the by putting a line that says '#APP' before the text that may contain whitespace or comments, and putting a -line that says `#NO_APP' after this text. This feature is mainly -intend to support `asm' statements in compilers whose output is -otherwise free of comments and whitespace. +line that says '#NO_APP' after this text. This feature is mainly intend +to support 'asm' statements in compilers whose output is otherwise free +of comments and whitespace.  File: as.info, Node: Whitespace, Next: Comments, Prev: Preprocessing, Up: Syntax @@ -1965,8 +1925,8 @@ 3.2 Whitespace ============== -"Whitespace" is one or more blanks or tabs, in any order. Whitespace -is used to separate symbols, and to make programs neater for people to +"Whitespace" is one or more blanks or tabs, in any order. Whitespace is +used to separate symbols, and to make programs neater for people to read. Unless within character constants (*note Character Constants: Characters.), any whitespace means the same as exactly one space. @@ -1976,10 +1936,10 @@ 3.3 Comments ============ -There are two ways of rendering comments to `as'. In both cases the +There are two ways of rendering comments to 'as'. In both cases the comment is equivalent to one space. - Anything from `/*' through the next `*/' is a comment. This means + Anything from '/*' through the next '*/' is a comment. This means you may not nest these comments. /* @@ -1992,22 +1952,22 @@ Anything from a "line comment" character up to the next newline is considered a comment and is ignored. The line comment character is target specific, and some targets multiple comment characters. Some -targets also have line comment characters that only work if they are -the first character on a line. Some targets use a sequence of two +targets also have line comment characters that only work if they are the +first character on a line. Some targets use a sequence of two characters to introduce a line comment. Some targets can also change their line comment characters depending upon command line options that have been used. For more details see the _Syntax_ section in the documentation for individual targets. - If the line comment character is the hash sign (`#') then it still + If the line comment character is the hash sign ('#') then it still has the special ability to enable and disable preprocessing (*note Preprocessing::) and to specify logical line numbers: - To be compatible with past assemblers, lines that begin with `#' -have a special interpretation. Following the `#' should be an absolute + To be compatible with past assemblers, lines that begin with '#' have +a special interpretation. Following the '#' should be an absolute expression (*note Expressions::): the logical line number of the _next_ -line. Then a string (*note Strings: Strings.) is allowed: if present -it is a new logical file name. The rest of the line, if any, should be +line. Then a string (*note Strings: Strings.) is allowed: if present it +is a new logical file name. The rest of the line, if any, should be whitespace. If the first non-whitespace characters on the line are not numeric, @@ -2016,8 +1976,8 @@ # This is an ordinary comment. # 42-6 "new_file_name" # New logical file name # This is logical line # 36. - This feature is deprecated, and may disappear from future versions -of `as'. + This feature is deprecated, and may disappear from future versions of +'as'.  File: as.info, Node: Symbol Intro, Next: Statements, Prev: Comments, Up: Syntax @@ -2026,19 +1986,19 @@ =========== A "symbol" is one or more characters chosen from the set of all letters -(both upper and lower case), digits and the three characters `_.$'. On -most machines, you can also use `$' in symbol names; exceptions are -noted in *Note Machine Dependencies::. No symbol may begin with a +(both upper and lower case), digits and the three characters '_.$'. On +most machines, you can also use '$' in symbol names; exceptions are +noted in *note Machine Dependencies::. No symbol may begin with a digit. Case is significant. There is no length limit; all characters are significant. Multibyte characters are supported. Symbols are delimited by characters not in that set, or by the beginning of a file (since the source program must end with a newline, the end of a file is not a possible symbol delimiter). *Note Symbols::. -Symbol names may also be enclosed in double quote `"' characters. In -such cases any characters are allowed, except for the NUL character. -If a double quote character is to be included in the symbol name it -must be preceeded by a backslash `\' character. + Symbol names may also be enclosed in double quote '"' characters. In +such cases any characters are allowed, except for the NUL character. If +a double quote character is to be included in the symbol name it must be +preceeded by a backslash '\' character.  File: as.info, Node: Statements, Next: Constants, Prev: Symbol Intro, Up: Syntax @@ -2046,15 +2006,15 @@ 3.5 Statements ============== -A "statement" ends at a newline character (`\n') or a "line separator +A "statement" ends at a newline character ('\n') or a "line separator character". The line separator character is target specific and described in the _Syntax_ section of each target's documentation. Not all targets support a line separator character. The newline or line -separator character is considered to be part of the preceding -statement. Newlines and separators within character constants are an -exception: they do not end statements. +separator character is considered to be part of the preceding statement. +Newlines and separators within character constants are an exception: +they do not end statements. - It is an error to end any statement with end-of-file: the last + It is an error to end any statement with end-of-file: the last character of any input file should be a newline. An empty statement is allowed, and may include whitespace. It is @@ -2063,21 +2023,21 @@ A statement begins with zero or more labels, optionally followed by a key symbol which determines what kind of statement it is. The key symbol determines the syntax of the rest of the statement. If the -symbol begins with a dot `.' then the statement is an assembler +symbol begins with a dot '.' then the statement is an assembler directive: typically valid for any computer. If the symbol begins with a letter the statement is an assembly language "instruction": it assembles into a machine language instruction. Different versions of -`as' for different computers recognize different instructions. In -fact, the same symbol may represent a different instruction in a -different computer's assembly language. +'as' for different computers recognize different instructions. In fact, +the same symbol may represent a different instruction in a different +computer's assembly language. - A label is a symbol immediately followed by a colon (`:'). + A label is a symbol immediately followed by a colon (':'). Whitespace before a label or after a colon is permitted, but you may not -have whitespace between a label's symbol and its colon. *Note Labels::. +have whitespace between a label's symbol and its colon. *Note Labels::. - For HPPA targets, labels need not be immediately followed by a -colon, but the definition of a label must begin in column zero. This -also implies that only one label may be defined on each line. + For HPPA targets, labels need not be immediately followed by a colon, +but the definition of a label must begin in column zero. This also +implies that only one label may be defined on each line. label: .directive followed by something another_label: # This is an empty statement. @@ -2128,51 +2088,51 @@ A "string" is written between double-quotes. It may contain double-quotes or null characters. The way to get special characters into a string is to "escape" these characters: precede them with a -backslash `\' character. For example `\\' represents one backslash: -the first `\' is an escape which tells `as' to interpret the second -character literally as a backslash (which prevents `as' from -recognizing the second `\' as an escape character). The complete list -of escapes follows. +backslash '\' character. For example '\\' represents one backslash: the +first '\' is an escape which tells 'as' to interpret the second +character literally as a backslash (which prevents 'as' from recognizing +the second '\' as an escape character). The complete list of escapes +follows. -`\b' +'\b' Mnemonic for backspace; for ASCII this is octal code 010. -`backslash-f' +'backslash-f' Mnemonic for FormFeed; for ASCII this is octal code 014. -`\n' +'\n' Mnemonic for newline; for ASCII this is octal code 012. -`\r' +'\r' Mnemonic for carriage-Return; for ASCII this is octal code 015. -`\t' +'\t' Mnemonic for horizontal Tab; for ASCII this is octal code 011. -`\ DIGIT DIGIT DIGIT' +'\ DIGIT DIGIT DIGIT' An octal character code. The numeric code is 3 octal digits. For compatibility with other Unix systems, 8 and 9 are accepted as - digits: for example, `\008' has the value 010, and `\009' the - value 011. + digits: for example, '\008' has the value 010, and '\009' the value + 011. -`\`x' HEX-DIGITS...' +'\x HEX-DIGITS...' A hex character code. All trailing hex digits are combined. - Either upper or lower case `x' works. + Either upper or lower case 'x' works. -`\\' - Represents one `\' character. +'\\' + Represents one '\' character. -`\"' - Represents one `"' character. Needed in strings to represent this - character, because an unescaped `"' would end the string. - -`\ ANYTHING-ELSE' - Any other character when escaped by `\' gives a warning, but - assembles as if the `\' was not present. The idea is that if you +'\"' + Represents one '"' character. Needed in strings to represent this + character, because an unescaped '"' would end the string. + +'\ ANYTHING-ELSE' + Any other character when escaped by '\' gives a warning, but + assembles as if the '\' was not present. The idea is that if you used an escape sequence you clearly didn't want the literal - interpretation of the following character. However `as' has no - other interpretation, so `as' knows it is giving you the wrong - code and warns you of the fact. + interpretation of the following character. However 'as' has no + other interpretation, so 'as' knows it is giving you the wrong code + and warns you of the fact. Which characters are escapable, and what those escapes represent, varies widely among assemblers. The current set is what we think the @@ -2185,17 +2145,17 @@ 3.6.1.2 Characters .................. -A single character may be written as a single quote immediately -followed by that character. Some backslash escapes apply to -characters, `\b', `\f', `\n', `\r', `\t', and `\"' with the same meaning -as for strings, plus `\'' for a single quote. So if you want to write -the character backslash, you must write `'\\' where the first `\' -escapes the second `\'. As you can see, the quote is an acute accent, -not a grave accent. A newline immediately following an acute accent is -taken as a literal character and does not count as the end of a -statement. The value of a character constant in a numeric expression -is the machine's byte-wide code for that character. `as' assumes your -character code is ASCII: `'A' means 65, `'B' means 66, and so on. +A single character may be written as a single quote immediately followed +by that character. Some backslash escapes apply to characters, '\b', +'\f', '\n', '\r', '\t', and '\"' with the same meaning as for strings, +plus '\'' for a single quote. So if you want to write the character +backslash, you must write ''\\' where the first '\' escapes the second +'\'. As you can see, the quote is an acute accent, not a grave accent. +A newline immediately following an acute accent is taken as a literal +character and does not count as the end of a statement. The value of a +character constant in a numeric expression is the machine's byte-wide +code for that character. 'as' assumes your character code is ASCII: +''A' means 65, ''B' means 66, and so on.  File: as.info, Node: Numbers, Prev: Characters, Up: Constants @@ -2203,9 +2163,9 @@ 3.6.2 Number Constants ---------------------- -`as' distinguishes three kinds of numbers according to how they are +'as' distinguishes three kinds of numbers according to how they are stored in the target machine. _Integers_ are numbers that would fit -into an `int' in the C language. _Bignums_ are integers, but they are +into an 'int' in the C language. _Bignums_ are integers, but they are stored in more than 32 bits. _Flonums_ are floating point numbers, described below. @@ -2221,20 +2181,20 @@ 3.6.2.1 Integers ................ -A binary integer is `0b' or `0B' followed by zero or more of the binary -digits `01'. +A binary integer is '0b' or '0B' followed by zero or more of the binary +digits '01'. - An octal integer is `0' followed by zero or more of the octal digits -(`01234567'). + An octal integer is '0' followed by zero or more of the octal digits +('01234567'). A decimal integer starts with a non-zero digit followed by zero or -more digits (`0123456789'). +more digits ('0123456789'). - A hexadecimal integer is `0x' or `0X' followed by one or more -hexadecimal digits chosen from `0123456789abcdefABCDEF'. + A hexadecimal integer is '0x' or '0X' followed by one or more +hexadecimal digits chosen from '0123456789abcdefABCDEF'. Integers have the usual values. To denote a negative integer, use -the prefix operator `-' discussed under expressions (*note Prefix +the prefix operator '-' discussed under expressions (*note Prefix Operators: Prefix Ops.).  @@ -2256,51 +2216,48 @@ A "flonum" represents a floating point number. The translation is indirect: a decimal floating point number from the text is converted by -`as' to a generic binary floating point number of more than sufficient +'as' to a generic binary floating point number of more than sufficient precision. This generic floating point number is converted to a -particular computer's floating point format (or formats) by a portion -of `as' specialized to that computer. +particular computer's floating point format (or formats) by a portion of +'as' specialized to that computer. A flonum is written by writing (in order) - * The digit `0'. (`0' is optional on the HPPA.) + * The digit '0'. ('0' is optional on the HPPA.) - * A letter, to tell `as' the rest of the number is a flonum. `e' is + * A letter, to tell 'as' the rest of the number is a flonum. 'e' is recommended. Case is not important. On the H8/300, Renesas / SuperH SH, and AMD 29K architectures, the - letter must be one of the letters `DFPRSX' (in upper or lower + letter must be one of the letters 'DFPRSX' (in upper or lower case). - On the ARC, the letter must be one of the letters `DFRS' (in upper + On the ARC, the letter must be one of the letters 'DFRS' (in upper or lower case). On the Intel 960 architecture, the letter must be one of the - letters `DFT' (in upper or lower case). + letters 'DFT' (in upper or lower case). - On the HPPA architecture, the letter must be `E' (upper case only). + On the HPPA architecture, the letter must be 'E' (upper case only). - * An optional sign: either `+' or `-'. + * An optional sign: either '+' or '-'. * An optional "integer part": zero or more decimal digits. - * An optional "fractional part": `.' followed by zero or more - decimal digits. + * An optional "fractional part": '.' followed by zero or more decimal + digits. * An optional exponent, consisting of: - * An `E' or `e'. - - * Optional sign: either `+' or `-'. - + * An 'E' or 'e'. + * Optional sign: either '+' or '-'. * One or more decimal digits. - At least one of the integer part or the fractional part must be present. The floating point number has the usual base-10 value. - `as' does all processing using integers. Flonums are computed + 'as' does all processing using integers. Flonums are computed independently of any floating point hardware in the computer running -`as'. +'as'.  File: as.info, Node: Sections, Next: Symbols, Prev: Syntax, Up: Top @@ -2326,82 +2283,79 @@ those addresses is treated the same for some particular purpose. For example there may be a "read only" section. - The linker `ld' reads many object files (partial programs) and -combines their contents to form a runnable program. When `as' emits an -object file, the partial program is assumed to start at address 0. -`ld' assigns the final addresses for the partial program, so that -different partial programs do not overlap. This is actually an -oversimplification, but it suffices to explain how `as' uses sections. + The linker 'ld' reads many object files (partial programs) and +combines their contents to form a runnable program. When 'as' emits an +object file, the partial program is assumed to start at address 0. 'ld' +assigns the final addresses for the partial program, so that different +partial programs do not overlap. This is actually an +oversimplification, but it suffices to explain how 'as' uses sections. - `ld' moves blocks of bytes of your program to their run-time + 'ld' moves blocks of bytes of your program to their run-time addresses. These blocks slide to their run-time addresses as rigid units; their length does not change and neither does the order of bytes within them. Such a rigid unit is called a _section_. Assigning run-time addresses to sections is called "relocation". It includes the -task of adjusting mentions of object-file addresses so they refer to -the proper run-time addresses. For the H8/300, and for the Renesas / -SuperH SH, `as' pads sections if needed to ensure they end on a word -(sixteen bit) boundary. +task of adjusting mentions of object-file addresses so they refer to the +proper run-time addresses. For the H8/300, and for the Renesas / SuperH +SH, 'as' pads sections if needed to ensure they end on a word (sixteen +bit) boundary. - An object file written by `as' has at least three sections, any of + An object file written by 'as' has at least three sections, any of which may be empty. These are named "text", "data" and "bss" sections. - When it generates COFF or ELF output, `as' can also generate -whatever other named sections you specify using the `.section' -directive (*note `.section': Section.). If you do not use any -directives that place output in the `.text' or `.data' sections, these -sections still exist, but are empty. - - When `as' generates SOM or ELF output for the HPPA, `as' can also -generate whatever other named sections you specify using the `.space' -and `.subspace' directives. See `HP9000 Series 800 Assembly Language -Reference Manual' (HP 92432-90001) for details on the `.space' and -`.subspace' assembler directives. + When it generates COFF or ELF output, 'as' can also generate whatever +other named sections you specify using the '.section' directive (*note +'.section': Section.). If you do not use any directives that place +output in the '.text' or '.data' sections, these sections still exist, +but are empty. + + When 'as' generates SOM or ELF output for the HPPA, 'as' can also +generate whatever other named sections you specify using the '.space' +and '.subspace' directives. See 'HP9000 Series 800 Assembly Language +Reference Manual' (HP 92432-90001) for details on the '.space' and +'.subspace' assembler directives. - Additionally, `as' uses different names for the standard text, data, + Additionally, 'as' uses different names for the standard text, data, and bss sections when generating SOM output. Program text is placed -into the `$CODE$' section, data into `$DATA$', and BSS into `$BSS$'. +into the '$CODE$' section, data into '$DATA$', and BSS into '$BSS$'. - Within the object file, the text section starts at address `0', the + Within the object file, the text section starts at address '0', the data section follows, and the bss section follows the data section. When generating either SOM or ELF output files on the HPPA, the text -section starts at address `0', the data section at address `0x4000000', +section starts at address '0', the data section at address '0x4000000', and the bss section follows the data section. - To let `ld' know which data changes when the sections are relocated, -and how to change that data, `as' also writes to the object file -details of the relocation needed. To perform relocation `ld' must -know, each time an address in the object file is mentioned: + To let 'ld' know which data changes when the sections are relocated, +and how to change that data, 'as' also writes to the object file details +of the relocation needed. To perform relocation 'ld' must know, each +time an address in the object file is mentioned: * Where in the object file is the beginning of this reference to an address? - * How long (in bytes) is this reference? - - * Which section does the address refer to? What is the numeric - value of + * Which section does the address refer to? What is the numeric value + of (ADDRESS) - (START-ADDRESS OF SECTION)? - * Is the reference to an address "Program-Counter relative"? - In fact, every address `as' ever uses is expressed as + In fact, every address 'as' ever uses is expressed as (SECTION) + (OFFSET INTO SECTION) - Further, most expressions `as' computes have this section-relative +Further, most expressions 'as' computes have this section-relative nature. (For some object formats, such as SOM for the HPPA, some expressions are symbol-relative instead.) - In this manual we use the notation {SECNAME N} to mean "offset N -into section SECNAME." + In this manual we use the notation {SECNAME N} to mean "offset N into +section SECNAME." Apart from text, data and bss sections you need to know about the -"absolute" section. When `ld' mixes partial programs, addresses in the -absolute section remain unchanged. For example, address `{absolute 0}' -is "relocated" to run-time address 0 by `ld'. Although the linker -never arranges two partial programs' data sections with overlapping -addresses after linking, _by definition_ their absolute sections must -overlap. Address `{absolute 239}' in one part of a program is always -the same address when the program is running as address `{absolute -239}' in any other part of the program. +"absolute" section. When 'ld' mixes partial programs, addresses in the +absolute section remain unchanged. For example, address '{absolute 0}' +is "relocated" to run-time address 0 by 'ld'. Although the linker never +arranges two partial programs' data sections with overlapping addresses +after linking, _by definition_ their absolute sections must overlap. +Address '{absolute 239}' in one part of a program is always the same +address when the program is running as address '{absolute 239}' in any +other part of the program. The idea of sections is extended to the "undefined" section. Any address whose section is unknown at assembly time is by definition @@ -2412,14 +2366,13 @@ section _undefined_. By analogy the word _section_ is used to describe groups of sections -in the linked program. `ld' puts all partial programs' text sections -in contiguous addresses in the linked program. It is customary to -refer to the _text section_ of a program, meaning all the addresses of -all partial programs' text sections. Likewise for data and bss -sections. +in the linked program. 'ld' puts all partial programs' text sections in +contiguous addresses in the linked program. It is customary to refer to +the _text section_ of a program, meaning all the addresses of all +partial programs' text sections. Likewise for data and bss sections. - Some sections are manipulated by `ld'; others are invented for use -of `as' and have no meaning except during assembly. + Some sections are manipulated by 'ld'; others are invented for use of +'as' and have no meaning except during assembly.  File: as.info, Node: Ld Sections, Next: As Sections, Prev: Secs Background, Up: Sections @@ -2427,16 +2380,16 @@ 4.2 Linker Sections =================== -`ld' deals with just four kinds of sections, summarized below. +'ld' deals with just four kinds of sections, summarized below. *named sections* *text section* *data section* - These sections hold your program. `as' and `ld' treat them as + These sections hold your program. 'as' and 'ld' treat them as separate but equal sections. Anything you can say of one section is true of another. When the program is running, however, it is - customary for the text section to be unalterable. The text - section is often shared among processes: it contains instructions, + customary for the text section to be unalterable. The text section + is often shared among processes: it contains instructions, constants and the like. The data section of a running program is usually alterable: for example, C variables would be stored in the data section. @@ -2452,17 +2405,17 @@ *absolute section* Address 0 of this section is always "relocated" to runtime address - 0. This is useful if you want to refer to an address that `ld' + 0. This is useful if you want to refer to an address that 'ld' must not change when relocating. In this sense we speak of - absolute addresses being "unrelocatable": they do not change - during relocation. + absolute addresses being "unrelocatable": they do not change during + relocation. *undefined section* - This "section" is a catch-all for address references to objects - not in the preceding sections. + This "section" is a catch-all for address references to objects not + in the preceding sections. An idealized example of three relocatable sections follows. The -example uses the traditional section names `.text' and `.data'. Memory +example uses the traditional section names '.text' and '.data'. Memory addresses are on the horizontal axis. +-----+----+--+ @@ -2488,16 +2441,16 @@ 4.3 Assembler Internal Sections =============================== -These sections are meant only for the internal use of `as'. They have +These sections are meant only for the internal use of 'as'. They have no meaning at run-time. You do not really need to know about these -sections for most purposes; but they can be mentioned in `as' warning +sections for most purposes; but they can be mentioned in 'as' warning messages, so it might be helpful to have an idea of their meanings to -`as'. These sections are used to permit the value of every expression +'as'. These sections are used to permit the value of every expression in your assembly language program to be a section-relative address. ASSEMBLER-INTERNAL-LOGIC-ERROR! - An internal assembler logic error has been found. This means - there is a bug in the assembler. + An internal assembler logic error has been found. This means there + is a bug in the assembler. expr section The assembler stores complex expression internally as combinations @@ -2513,40 +2466,40 @@ Assembled bytes conventionally fall into two sections: text and data. You may have separate groups of data in named sections that you want to end up near to each other in the object file, even though they are not -contiguous in the assembler source. `as' allows you to use +contiguous in the assembler source. 'as' allows you to use "subsections" for this purpose. Within each section, there can be -numbered subsections with values from 0 to 8192. Objects assembled -into the same subsection go into the object file together with other -objects in the same subsection. For example, a compiler might want to -store constants in the text section, but might not want to have them +numbered subsections with values from 0 to 8192. Objects assembled into +the same subsection go into the object file together with other objects +in the same subsection. For example, a compiler might want to store +constants in the text section, but might not want to have them interspersed with the program being assembled. In this case, the -compiler could issue a `.text 0' before each section of code being -output, and a `.text 1' before each group of constants being output. +compiler could issue a '.text 0' before each section of code being +output, and a '.text 1' before each group of constants being output. -Subsections are optional. If you do not use subsections, everything + Subsections are optional. If you do not use subsections, everything goes in subsection number zero. Each subsection is zero-padded up to a multiple of four bytes. (Subsections may be padded a different amount on different flavors of -`as'.) +'as'.) Subsections appear in your object file in numeric order, lowest numbered to highest. (All this to be compatible with other people's -assemblers.) The object file contains no representation of -subsections; `ld' and other programs that manipulate object files see -no trace of them. They just see all your text subsections as a text -section, and all your data subsections as a data section. +assemblers.) The object file contains no representation of subsections; +'ld' and other programs that manipulate object files see no trace of +them. They just see all your text subsections as a text section, and +all your data subsections as a data section. To specify which subsection you want subsequent statements assembled -into, use a numeric argument to specify it, in a `.text EXPRESSION' or -a `.data EXPRESSION' statement. When generating COFF output, you can -also use an extra subsection argument with arbitrary named sections: -`.section NAME, EXPRESSION'. When generating ELF output, you can also -use the `.subsection' directive (*note SubSection::) to specify a -subsection: `.subsection EXPRESSION'. EXPRESSION should be an absolute -expression (*note Expressions::). If you just say `.text' then `.text -0' is assumed. Likewise `.data' means `.data 0'. Assembly begins in -`text 0'. For instance: +into, use a numeric argument to specify it, in a '.text EXPRESSION' or a +'.data EXPRESSION' statement. When generating COFF output, you can also +use an extra subsection argument with arbitrary named sections: +'.section NAME, EXPRESSION'. When generating ELF output, you can also +use the '.subsection' directive (*note SubSection::) to specify a +subsection: '.subsection EXPRESSION'. EXPRESSION should be an absolute +expression (*note Expressions::). If you just say '.text' then '.text +0' is assumed. Likewise '.data' means '.data 0'. Assembly begins in +'text 0'. For instance: .text 0 # The default subsection is text 0 anyway. .ascii "This lives in the first text subsection. *" .text 1 @@ -2560,12 +2513,12 @@ Each section has a "location counter" incremented by one for every byte assembled into that section. Because subsections are merely a -convenience restricted to `as' there is no concept of a subsection +convenience restricted to 'as' there is no concept of a subsection location counter. There is no way to directly manipulate a location -counter--but the `.align' directive changes it, and any label -definition captures its current value. The location counter of the -section where statements are being assembled is said to be the "active" -location counter. +counter--but the '.align' directive changes it, and any label definition +captures its current value. The location counter of the section where +statements are being assembled is said to be the "active" location +counter.  File: as.info, Node: bss, Prev: Sub-Sections, Up: Sections @@ -2578,17 +2531,17 @@ to load into it before your program executes. When your program starts running, all the contents of the bss section are zeroed bytes. - The `.lcomm' pseudo-op defines a symbol in the bss section; see -*Note `.lcomm': Lcomm. + The '.lcomm' pseudo-op defines a symbol in the bss section; see *note +'.lcomm': Lcomm. - The `.comm' pseudo-op may be used to declare a common symbol, which -is another form of uninitialized symbol; see *Note `.comm': Comm. + The '.comm' pseudo-op may be used to declare a common symbol, which +is another form of uninitialized symbol; see *note '.comm': Comm. When assembling for a target which supports multiple sections, such -as ELF or COFF, you may switch into the `.bss' section and define -symbols as usual; see *Note `.section': Section. You may only assemble +as ELF or COFF, you may switch into the '.bss' section and define +symbols as usual; see *note '.section': Section. You may only assemble zero values into the section. Typically the section will only contain -symbol definitions and `.skip' directives (*note `.skip': Skip.). +symbol definitions and '.skip' directives (*note '.skip': Skip.).  File: as.info, Node: Symbols, Next: Expressions, Prev: Sections, Up: Top @@ -2600,7 +2553,7 @@ things, the linker uses symbols to link, and the debugger uses symbols to debug. - _Warning:_ `as' does not place symbols in the object file in the + _Warning:_ 'as' does not place symbols in the object file in the same order they were declared. This may break some debuggers. * Menu: @@ -2617,7 +2570,7 @@ 5.1 Labels ========== -A "label" is written as a symbol immediately followed by a colon `:'. +A "label" is written as a symbol immediately followed by a colon ':'. The symbol then represents the current value of the active location counter, and is, for example, a suitable instruction operand. You are warned if you use the same symbol to represent two different locations: @@ -2626,7 +2579,7 @@ On the HPPA, the usual form for a label need not be immediately followed by a colon, but instead must start in column zero. Only one label may be defined on a single line. To work around this, the HPPA -version of `as' also provides a special directive `.label' for defining +version of 'as' also provides a special directive '.label' for defining labels more flexibly.  @@ -2636,12 +2589,12 @@ =============================== A symbol can be given an arbitrary value by writing a symbol, followed -by an equals sign `=', followed by an expression (*note Expressions::). -This is equivalent to using the `.set' directive. *Note `.set': Set. -In the same way, using a double equals sign `='`=' here represents an -equivalent of the `.eqv' directive. *Note `.eqv': Eqv. +by an equals sign '=', followed by an expression (*note Expressions::). +This is equivalent to using the '.set' directive. *Note '.set': Set. +In the same way, using a double equals sign '=''=' here represents an +equivalent of the '.eqv' directive. *Note '.eqv': Eqv. - Blackfin does not support symbol assignment with `='. + Blackfin does not support symbol assignment with '='.  File: as.info, Node: Symbol Names, Next: Dot, Prev: Setting Symbols, Up: Symbols @@ -2649,21 +2602,21 @@ 5.3 Symbol Names ================ -Symbol names begin with a letter or with one of `._'. On most -machines, you can also use `$' in symbol names; exceptions are noted in -*Note Machine Dependencies::. That character may be followed by any -string of digits, letters, dollar signs (unless otherwise noted for a -particular target machine), and underscores. +Symbol names begin with a letter or with one of '._'. On most machines, +you can also use '$' in symbol names; exceptions are noted in *note +Machine Dependencies::. That character may be followed by any string of +digits, letters, dollar signs (unless otherwise noted for a particular +target machine), and underscores. -Case of letters is significant: `foo' is a different symbol name than -`Foo'. + Case of letters is significant: 'foo' is a different symbol name than +'Foo'. - Symbol names do not start with a digit. An exception to this rule -is made for Local Labels. See below. + Symbol names do not start with a digit. An exception to this rule is +made for Local Labels. See below. Multibyte characters are supported. To generate a symbol name containing multibyte characters enclose it within double quotes and use -escape codes. cf *Note Strings::. Generating a multibyte symbol name +escape codes. cf *Note Strings::. Generating a multibyte symbol name from a label is not currently supported. Each symbol has exactly one name. Each name in an assembly language @@ -2674,14 +2627,14 @@ ------------------ A local symbol is any symbol beginning with certain local label -prefixes. By default, the local label prefix is `.L' for ELF systems or -`L' for traditional a.out systems, but each target may have its own set -of local label prefixes. On the HPPA local symbols begin with `L$'. +prefixes. By default, the local label prefix is '.L' for ELF systems or +'L' for traditional a.out systems, but each target may have its own set +of local label prefixes. On the HPPA local symbols begin with 'L$'. Local symbols are defined and used within the assembler, but they are normally not saved in object files. Thus, they are not visible when -debugging. You may use the `-L' option (*note Include Local Symbols: -L.) to retain the local symbols in the object files. +debugging. You may use the '-L' option (*note Include Local Symbols: +L.) to retain the local symbols in the object files. Local Labels ------------ @@ -2690,21 +2643,21 @@ compilers and programmers use names temporarily. They create symbols which are guaranteed to be unique over the entire scope of the input source code and which can be referred to by a simple notation. To -define a local label, write a label of the form `N:' (where N -represents any non-negative integer). To refer to the most recent -previous definition of that label write `Nb', using the same number as -when you defined the label. To refer to the next definition of a local -label, write `Nf'. The `b' stands for "backwards" and the `f' stands -for "forwards". +define a local label, write a label of the form 'N:' (where N represents +any non-negative integer). To refer to the most recent previous +definition of that label write 'Nb', using the same number as when you +defined the label. To refer to the next definition of a local label, +write 'Nf'. The 'b' stands for "backwards" and the 'f' stands for +"forwards". There is no restriction on how you can use these labels, and you can reuse them too. So that it is possible to repeatedly define the same -local label (using the same number `N'), although you can only refer to +local label (using the same number 'N'), although you can only refer to the most recently defined local label of that number (for a backwards reference) or the next definition of a specific local label for a forward reference. It is also worth noting that the first 10 local -labels (`0:'...`9:') are implemented in a slightly more efficient -manner than the others. +labels ('0:'...'9:') are implemented in a slightly more efficient manner +than the others. Here is an example: @@ -2726,52 +2679,51 @@ error messages, and are optionally emitted to the object file. The names are constructed using these parts: -`_local label prefix_' +'_local label prefix_' All local symbols begin with the system-specific local label - prefix. Normally both `as' and `ld' forget symbols that start - with the local label prefix. These labels are used for symbols - you are never intended to see. If you use the `-L' option then - `as' retains these symbols in the object file. If you also - instruct `ld' to retain these symbols, you may use them in - debugging. - -`NUMBER' - This is the number that was used in the local label definition. - So if the label is written `55:' then the number is `55'. + prefix. Normally both 'as' and 'ld' forget symbols that start with + the local label prefix. These labels are used for symbols you are + never intended to see. If you use the '-L' option then 'as' + retains these symbols in the object file. If you also instruct + 'ld' to retain these symbols, you may use them in debugging. + +'NUMBER' + This is the number that was used in the local label definition. So + if the label is written '55:' then the number is '55'. -`C-B' +'C-B' This unusual character is included so you do not accidentally - invent a symbol of the same name. The character has ASCII value - of `\002' (control-B). + invent a symbol of the same name. The character has ASCII value of + '\002' (control-B). -`_ordinal number_' +'_ordinal number_' This is a serial number to keep the labels distinct. The first - definition of `0:' gets the number `1'. The 15th definition of - `0:' gets the number `15', and so on. Likewise the first - definition of `1:' gets the number `1' and its 15th definition - gets `15' as well. + definition of '0:' gets the number '1'. The 15th definition of + '0:' gets the number '15', and so on. Likewise the first + definition of '1:' gets the number '1' and its 15th definition gets + '15' as well. - So for example, the first `1:' may be named `.L1C-B1', and the 44th -`3:' may be named `.L3C-B44'. + So for example, the first '1:' may be named '.L1C-B1', and the 44th +'3:' may be named '.L3C-B44'. Dollar Local Labels ------------------- -On some targets `as' also supports an even more local form of local +On some targets 'as' also supports an even more local form of local labels called dollar labels. These labels go out of scope (i.e., they become undefined) as soon as a non-local label is defined. Thus they remain valid for only a small region of the input source code. Normal -local labels, by contrast, remain in scope for the entire file, or -until they are redefined by another occurrence of the same local label. +local labels, by contrast, remain in scope for the entire file, or until +they are redefined by another occurrence of the same local label. Dollar labels are defined in exactly the same way as ordinary local labels, except that they have a dollar sign suffix to their numeric -value, e.g., `55$:'. +value, e.g., '55$:'. They can also be distinguished from ordinary local labels by their -transformed names which use ASCII character `\001' (control-A) as the +transformed names which use ASCII character '\001' (control-A) as the magic character to distinguish them from ordinary labels. For example, -the fifth definition of `6$' may be named `.L6C-A5'. +the fifth definition of '6$' may be named '.L6'C-A'5'.  File: as.info, Node: Dot, Next: Symbol Attributes, Prev: Symbol Names, Up: Symbols @@ -2779,11 +2731,11 @@ 5.4 The Special Dot Symbol ========================== -The special symbol `.' refers to the current address that `as' is -assembling into. Thus, the expression `melvin: .long .' defines -`melvin' to contain its own address. Assigning a value to `.' is -treated the same as a `.org' directive. Thus, the expression `.=.+4' -is the same as saying `.space 4'. +The special symbol '.' refers to the current address that 'as' is +assembling into. Thus, the expression 'melvin: .long .' defines +'melvin' to contain its own address. Assigning a value to '.' is +treated the same as a '.org' directive. Thus, the expression '.=.+4' is +the same as saying '.space 4'.  File: as.info, Node: Symbol Attributes, Prev: Dot, Up: Symbols @@ -2795,20 +2747,16 @@ "Type". Depending on output format, symbols can also have auxiliary attributes. - If you use a symbol without defining it, `as' assumes zero for all -these attributes, and probably won't warn you. This makes the symbol -an externally defined symbol, which is generally what you would want. + If you use a symbol without defining it, 'as' assumes zero for all +these attributes, and probably won't warn you. This makes the symbol an +externally defined symbol, which is generally what you would want. * Menu: * Symbol Value:: Value * Symbol Type:: Type - - -* a.out Symbols:: Symbol Attributes: `a.out' - +* a.out Symbols:: Symbol Attributes: 'a.out' * COFF Symbols:: Symbol Attributes for COFF - * SOM Symbols:: Symbol Attributes for SOM  @@ -2821,15 +2769,15 @@ location in the text, data, bss or absolute sections the value is the number of addresses from the start of that section to the label. Naturally for text, data and bss sections the value of a symbol changes -as `ld' changes section base addresses during linking. Absolute +as 'ld' changes section base addresses during linking. Absolute symbols' values do not change during linking: that is why they are called absolute. The value of an undefined symbol is treated in a special way. If it is 0 then the symbol is not defined in this assembler source file, and -`ld' tries to determine its value from other files linked into the same +'ld' tries to determine its value from other files linked into the same program. You make this kind of symbol simply by mentioning a symbol -name without defining it. A non-zero value represents a `.comm' common +name without defining it. A non-zero value represents a '.comm' common declaration. The value is how much common storage to reserve, in bytes (addresses). The symbol refers to the first address of the allocated storage. @@ -2848,7 +2796,7 @@  File: as.info, Node: a.out Symbols, Next: COFF Symbols, Prev: Symbol Type, Up: Symbol Attributes -5.5.3 Symbol Attributes: `a.out' +5.5.3 Symbol Attributes: 'a.out' -------------------------------- * Menu: @@ -2863,8 +2811,8 @@ .................. This is an arbitrary 16-bit value. You may establish a symbol's -descriptor value by using a `.desc' statement (*note `.desc': Desc.). -A descriptor value means nothing to `as'. +descriptor value by using a '.desc' statement (*note '.desc': Desc.). A +descriptor value means nothing to 'as'.  File: as.info, Node: Symbol Other, Prev: Symbol Desc, Up: a.out Symbols @@ -2872,7 +2820,7 @@ 5.5.3.2 Other ............. -This is an arbitrary 8-bit value. It means nothing to `as'. +This is an arbitrary 8-bit value. It means nothing to 'as'.  File: as.info, Node: COFF Symbols, Next: SOM Symbols, Prev: a.out Symbols, Up: Symbol Attributes @@ -2881,20 +2829,20 @@ -------------------------------- The COFF format supports a multitude of auxiliary symbol attributes; -like the primary symbol attributes, they are set between `.def' and -`.endef' directives. +like the primary symbol attributes, they are set between '.def' and +'.endef' directives. 5.5.4.1 Primary Attributes .......................... -The symbol name is set with `.def'; the value and type, respectively, -with `.val' and `.type'. +The symbol name is set with '.def'; the value and type, respectively, +with '.val' and '.type'. 5.5.4.2 Auxiliary Attributes ............................ -The `as' directives `.dim', `.line', `.scl', `.size', `.tag', and -`.weak' can generate auxiliary symbol table information for COFF. +The 'as' directives '.dim', '.line', '.scl', '.size', '.tag', and +'.weak' can generate auxiliary symbol table information for COFF.  File: as.info, Node: SOM Symbols, Prev: COFF Symbols, Up: Symbol Attributes @@ -2903,10 +2851,10 @@ ------------------------------- The SOM format for the HPPA supports a multitude of symbol attributes -set with the `.EXPORT' and `.IMPORT' directives. +set with the '.EXPORT' and '.IMPORT' directives. - The attributes are described in `HP9000 Series 800 Assembly Language -Reference Manual' (HP 92432-90001) under the `IMPORT' and `EXPORT' + The attributes are described in 'HP9000 Series 800 Assembly Language +Reference Manual' (HP 92432-90001) under the 'IMPORT' and 'EXPORT' assembler directive documentation.  @@ -2919,11 +2867,11 @@ precede and/or follow an expression. The result of an expression must be an absolute number, or else an -offset into a particular section. If an expression is not absolute, -and there is not enough information when `as' sees the expression to -know its section, a second pass over the source program might be -necessary to interpret the expression--but the second pass is currently -not implemented. `as' aborts with an error message in this situation. +offset into a particular section. If an expression is not absolute, and +there is not enough information when 'as' sees the expression to know +its section, a second pass over the source program might be necessary to +interpret the expression--but the second pass is currently not +implemented. 'as' aborts with an error message in this situation. * Menu: @@ -2938,7 +2886,7 @@ An empty expression has no value: it is just whitespace or null. Wherever an absolute expression is required, you may omit the -expression, and `as' assumes a value of (absolute) 0. This is +expression, and 'as' assumes a value of (absolute) 0. This is compatible with other assemblers.  @@ -2977,12 +2925,12 @@ Numbers are usually integers. A number can be a flonum or bignum. In this case, you are warned -that only the low order 32 bits are used, and `as' pretends these 32 +that only the low order 32 bits are used, and 'as' pretends these 32 bits are an integer. You may write integer-manipulating instructions that act on exotic constants, compatible with other assemblers. - Subexpressions are a left parenthesis `(' followed by an integer -expression, followed by a right parenthesis `)'; or a prefix operator + Subexpressions are a left parenthesis '(' followed by an integer +expression, followed by a right parenthesis ')'; or a prefix operator followed by an argument.  @@ -2991,10 +2939,9 @@ 6.2.2 Operators --------------- -"Operators" are arithmetic functions, like `+' or `%'. Prefix -operators are followed by an argument. Infix operators appear between -their arguments. Operators may be preceded and/or followed by -whitespace. +"Operators" are arithmetic functions, like '+' or '%'. Prefix operators +are followed by an argument. Infix operators appear between their +arguments. Operators may be preceded and/or followed by whitespace.  File: as.info, Node: Prefix Ops, Next: Infix Ops, Prev: Operators, Up: Integer Exprs @@ -3002,13 +2949,12 @@ 6.2.3 Prefix Operator --------------------- -`as' has the following "prefix operators". They each take one -argument, which must be absolute. +'as' has the following "prefix operators". They each take one argument, +which must be absolute. -`-' +'-' "Negation". Two's complement negation. - -`~' +'~' "Complementation". Bitwise not.  @@ -3019,83 +2965,78 @@ "Infix operators" take two arguments, one on either side. Operators have precedence, but operations with equal precedence are performed left -to right. Apart from `+' or `-', both arguments must be absolute, and +to right. Apart from '+' or '-', both arguments must be absolute, and the result is absolute. 1. Highest Precedence - `*' + '*' "Multiplication". - `/' - "Division". Truncation is the same as the C operator `/' + '/' + "Division". Truncation is the same as the C operator '/' - `%' + '%' "Remainder". - `<<' - "Shift Left". Same as the C operator `<<'. + '<<' + "Shift Left". Same as the C operator '<<'. - `>>' - "Shift Right". Same as the C operator `>>'. + '>>' + "Shift Right". Same as the C operator '>>'. 2. Intermediate precedence - `|' + '|' + "Bitwise Inclusive Or". - `&' + '&' "Bitwise And". - `^' + '^' "Bitwise Exclusive Or". - `!' + '!' "Bitwise Or Not". 3. Low Precedence - `+' + '+' "Addition". If either argument is absolute, the result has the section of the other argument. You may not add together arguments from different sections. - `-' + '-' "Subtraction". If the right argument is absolute, the result has the section of the left argument. If both arguments are in the same section, the result is absolute. You may not subtract arguments from different sections. - `==' + '==' "Is Equal To" - - `<>' - `!=' + '<>' + '!=' "Is Not Equal To" - - `<' + '<' "Is Less Than" - - `>' + '>' "Is Greater Than" - - `>=' + '>=' "Is Greater Than Or Equal To" - - `<=' + '<=' "Is Less Than Or Equal To" The comparison operators can be used as infix operators. A true results has a value of -1 whereas a false result has a - value of 0. Note, these operators perform signed - comparisons. + value of 0. Note, these operators perform signed comparisons. 4. Lowest Precedence - `&&' + '&&' "Logical And". - `||' + '||' "Logical Or". These two logical operations can be used to combine the @@ -3104,7 +3045,6 @@ results does still return 0. Also note that the logical or operator has a slightly lower precedence than logical and. - In short, it's only meaningful to add or subtract the _offsets_ in an address; you can only have a defined section in one of the two arguments. @@ -3115,8 +3055,8 @@ 7 Assembler Directives ********************** -All assembler directives have names that begin with a period (`.'). -The names are case insensitive for most targets, and usually written in +All assembler directives have names that begin with a period ('.'). The +names are case insensitive for most targets, and usually written in lower case. This chapter discusses directives that are available regardless of @@ -3126,180 +3066,156 @@ * Menu: -* Abort:: `.abort' - -* ABORT (COFF):: `.ABORT' - -* Align:: `.align ABS-EXPR , ABS-EXPR' -* Altmacro:: `.altmacro' -* Ascii:: `.ascii "STRING"'... -* Asciz:: `.asciz "STRING"'... -* Balign:: `.balign ABS-EXPR , ABS-EXPR' -* Bundle directives:: `.bundle_align_mode ABS-EXPR', etc -* Byte:: `.byte EXPRESSIONS' -* CFI directives:: `.cfi_startproc [simple]', `.cfi_endproc', etc. -* Comm:: `.comm SYMBOL , LENGTH ' -* Data:: `.data SUBSECTION' - -* Def:: `.def NAME' - -* Desc:: `.desc SYMBOL, ABS-EXPRESSION' - -* Dim:: `.dim' - -* Double:: `.double FLONUMS' -* Eject:: `.eject' -* Else:: `.else' -* Elseif:: `.elseif' -* End:: `.end' - -* Endef:: `.endef' - -* Endfunc:: `.endfunc' -* Endif:: `.endif' -* Equ:: `.equ SYMBOL, EXPRESSION' -* Equiv:: `.equiv SYMBOL, EXPRESSION' -* Eqv:: `.eqv SYMBOL, EXPRESSION' -* Err:: `.err' -* Error:: `.error STRING' -* Exitm:: `.exitm' -* Extern:: `.extern' -* Fail:: `.fail' -* File:: `.file' -* Fill:: `.fill REPEAT , SIZE , VALUE' -* Float:: `.float FLONUMS' -* Func:: `.func' -* Global:: `.global SYMBOL', `.globl SYMBOL' - -* Gnu_attribute:: `.gnu_attribute TAG,VALUE' -* Hidden:: `.hidden NAMES' - -* hword:: `.hword EXPRESSIONS' -* Ident:: `.ident' -* If:: `.if ABSOLUTE EXPRESSION' -* Incbin:: `.incbin "FILE"[,SKIP[,COUNT]]' -* Include:: `.include "FILE"' -* Int:: `.int EXPRESSIONS' - -* Internal:: `.internal NAMES' - -* Irp:: `.irp SYMBOL,VALUES'... -* Irpc:: `.irpc SYMBOL,VALUES'... -* Lcomm:: `.lcomm SYMBOL , LENGTH' -* Lflags:: `.lflags' +* Abort:: '.abort' +* ABORT (COFF):: '.ABORT' -* Line:: `.line LINE-NUMBER' - -* Linkonce:: `.linkonce [TYPE]' -* List:: `.list' -* Ln:: `.ln LINE-NUMBER' -* Loc:: `.loc FILENO LINENO' -* Loc_mark_labels:: `.loc_mark_labels ENABLE' - -* Local:: `.local NAMES' - -* Long:: `.long EXPRESSIONS' - -* Macro:: `.macro NAME ARGS'... -* MRI:: `.mri VAL' -* Noaltmacro:: `.noaltmacro' -* Nolist:: `.nolist' -* Octa:: `.octa BIGNUMS' -* Offset:: `.offset LOC' -* Org:: `.org NEW-LC, FILL' -* P2align:: `.p2align ABS-EXPR, ABS-EXPR, ABS-EXPR' - -* PopSection:: `.popsection' -* Previous:: `.previous' - -* Print:: `.print STRING' - -* Protected:: `.protected NAMES' - -* Psize:: `.psize LINES, COLUMNS' -* Purgem:: `.purgem NAME' - -* PushSection:: `.pushsection NAME' - -* Quad:: `.quad BIGNUMS' -* Reloc:: `.reloc OFFSET, RELOC_NAME[, EXPRESSION]' -* Rept:: `.rept COUNT' -* Sbttl:: `.sbttl "SUBHEADING"' - -* Scl:: `.scl CLASS' - -* Section:: `.section NAME[, FLAGS]' - -* Set:: `.set SYMBOL, EXPRESSION' -* Short:: `.short EXPRESSIONS' -* Single:: `.single FLONUMS' - -* Size:: `.size [NAME , EXPRESSION]' - -* Skip:: `.skip SIZE , FILL' - -* Sleb128:: `.sleb128 EXPRESSIONS' - -* Space:: `.space SIZE , FILL' - -* Stab:: `.stabd, .stabn, .stabs' - -* String:: `.string "STR"', `.string8 "STR"', `.string16 "STR"', `.string32 "STR"', `.string64 "STR"' -* Struct:: `.struct EXPRESSION' - -* SubSection:: `.subsection' -* Symver:: `.symver NAME,NAME2@NODENAME' - - -* Tag:: `.tag STRUCTNAME' - -* Text:: `.text SUBSECTION' -* Title:: `.title "HEADING"' - -* Type:: `.type ' - -* Uleb128:: `.uleb128 EXPRESSIONS' - -* Val:: `.val ADDR' - - -* Version:: `.version "STRING"' -* VTableEntry:: `.vtable_entry TABLE, OFFSET' -* VTableInherit:: `.vtable_inherit CHILD, PARENT' - -* Warning:: `.warning STRING' -* Weak:: `.weak NAMES' -* Weakref:: `.weakref ALIAS, SYMBOL' -* Word:: `.word EXPRESSIONS' - -* Zero:: `.zero SIZE' +* Align:: '.align ABS-EXPR , ABS-EXPR' +* Altmacro:: '.altmacro' +* Ascii:: '.ascii "STRING"'... +* Asciz:: '.asciz "STRING"'... +* Balign:: '.balign ABS-EXPR , ABS-EXPR' +* Bundle directives:: '.bundle_align_mode ABS-EXPR', etc +* Byte:: '.byte EXPRESSIONS' +* CFI directives:: '.cfi_startproc [simple]', '.cfi_endproc', etc. +* Comm:: '.comm SYMBOL , LENGTH ' +* Data:: '.data SUBSECTION' +* Def:: '.def NAME' +* Desc:: '.desc SYMBOL, ABS-EXPRESSION' +* Dim:: '.dim' + +* Double:: '.double FLONUMS' +* Eject:: '.eject' +* Else:: '.else' +* Elseif:: '.elseif' +* End:: '.end' +* Endef:: '.endef' + +* Endfunc:: '.endfunc' +* Endif:: '.endif' +* Equ:: '.equ SYMBOL, EXPRESSION' +* Equiv:: '.equiv SYMBOL, EXPRESSION' +* Eqv:: '.eqv SYMBOL, EXPRESSION' +* Err:: '.err' +* Error:: '.error STRING' +* Exitm:: '.exitm' +* Extern:: '.extern' +* Fail:: '.fail' +* File:: '.file' +* Fill:: '.fill REPEAT , SIZE , VALUE' +* Float:: '.float FLONUMS' +* Func:: '.func' +* Global:: '.global SYMBOL', '.globl SYMBOL' +* Gnu_attribute:: '.gnu_attribute TAG,VALUE' +* Hidden:: '.hidden NAMES' + +* hword:: '.hword EXPRESSIONS' +* Ident:: '.ident' +* If:: '.if ABSOLUTE EXPRESSION' +* Incbin:: '.incbin "FILE"[,SKIP[,COUNT]]' +* Include:: '.include "FILE"' +* Int:: '.int EXPRESSIONS' +* Internal:: '.internal NAMES' + +* Irp:: '.irp SYMBOL,VALUES'... +* Irpc:: '.irpc SYMBOL,VALUES'... +* Lcomm:: '.lcomm SYMBOL , LENGTH' +* Lflags:: '.lflags' +* Line:: '.line LINE-NUMBER' + +* Linkonce:: '.linkonce [TYPE]' +* List:: '.list' +* Ln:: '.ln LINE-NUMBER' +* Loc:: '.loc FILENO LINENO' +* Loc_mark_labels:: '.loc_mark_labels ENABLE' +* Local:: '.local NAMES' + +* Long:: '.long EXPRESSIONS' + +* Macro:: '.macro NAME ARGS'... +* MRI:: '.mri VAL' +* Noaltmacro:: '.noaltmacro' +* Nolist:: '.nolist' +* Octa:: '.octa BIGNUMS' +* Offset:: '.offset LOC' +* Org:: '.org NEW-LC, FILL' +* P2align:: '.p2align ABS-EXPR, ABS-EXPR, ABS-EXPR' +* PopSection:: '.popsection' +* Previous:: '.previous' + +* Print:: '.print STRING' +* Protected:: '.protected NAMES' + +* Psize:: '.psize LINES, COLUMNS' +* Purgem:: '.purgem NAME' +* PushSection:: '.pushsection NAME' + +* Quad:: '.quad BIGNUMS' +* Reloc:: '.reloc OFFSET, RELOC_NAME[, EXPRESSION]' +* Rept:: '.rept COUNT' +* Sbttl:: '.sbttl "SUBHEADING"' +* Scl:: '.scl CLASS' +* Section:: '.section NAME[, FLAGS]' + +* Set:: '.set SYMBOL, EXPRESSION' +* Short:: '.short EXPRESSIONS' +* Single:: '.single FLONUMS' +* Size:: '.size [NAME , EXPRESSION]' +* Skip:: '.skip SIZE , FILL' + +* Sleb128:: '.sleb128 EXPRESSIONS' +* Space:: '.space SIZE , FILL' +* Stab:: '.stabd, .stabn, .stabs' + +* String:: '.string "STR"', '.string8 "STR"', '.string16 "STR"', '.string32 "STR"', '.string64 "STR"' +* Struct:: '.struct EXPRESSION' +* SubSection:: '.subsection' +* Symver:: '.symver NAME,NAME2@NODENAME' + +* Tag:: '.tag STRUCTNAME' + +* Text:: '.text SUBSECTION' +* Title:: '.title "HEADING"' +* Type:: '.type ' + +* Uleb128:: '.uleb128 EXPRESSIONS' +* Val:: '.val ADDR' + +* Version:: '.version "STRING"' +* VTableEntry:: '.vtable_entry TABLE, OFFSET' +* VTableInherit:: '.vtable_inherit CHILD, PARENT' + +* Warning:: '.warning STRING' +* Weak:: '.weak NAMES' +* Weakref:: '.weakref ALIAS, SYMBOL' +* Word:: '.word EXPRESSIONS' +* Zero:: '.zero SIZE' * Deprecated:: Deprecated Directives  File: as.info, Node: Abort, Next: ABORT (COFF), Up: Pseudo Ops -7.1 `.abort' +7.1 '.abort' ============ This directive stops the assembly immediately. It is for compatibility -with other assemblers. The original idea was that the assembly -language source would be piped into the assembler. If the sender of -the source quit, it could use this directive tells `as' to quit also. -One day `.abort' will not be supported. +with other assemblers. The original idea was that the assembly language +source would be piped into the assembler. If the sender of the source +quit, it could use this directive tells 'as' to quit also. One day +'.abort' will not be supported.  File: as.info, Node: ABORT (COFF), Next: Align, Prev: Abort, Up: Pseudo Ops -7.2 `.ABORT' (COFF) +7.2 '.ABORT' (COFF) =================== -When producing COFF output, `as' accepts this directive as a synonym -for `.abort'. +When producing COFF output, 'as' accepts this directive as a synonym for +'.abort'.  File: as.info, Node: Align, Next: Altmacro, Prev: ABORT (COFF), Up: Pseudo Ops -7.3 `.align ABS-EXPR, ABS-EXPR, ABS-EXPR' +7.3 '.align ABS-EXPR, ABS-EXPR, ABS-EXPR' ========================================= Pad the location counter (in the current subsection) to a particular @@ -3314,99 +3230,99 @@ The third expression is also absolute, and is also optional. If it is present, it is the maximum number of bytes that should be skipped by -this alignment directive. If doing the alignment would require -skipping more bytes than the specified maximum, then the alignment is -not done at all. You can omit the fill value (the second argument) -entirely by simply using two commas after the required alignment; this -can be useful if you want the alignment to be filled with no-op -instructions when appropriate. +this alignment directive. If doing the alignment would require skipping +more bytes than the specified maximum, then the alignment is not done at +all. You can omit the fill value (the second argument) entirely by +simply using two commas after the required alignment; this can be useful +if you want the alignment to be filled with no-op instructions when +appropriate. The way the required alignment is specified varies from system to system. For the arc, hppa, i386 using ELF, i860, iq2000, m68k, or1k, s390, sparc, tic4x, tic80 and xtensa, the first expression is the -alignment request in bytes. For example `.align 8' advances the +alignment request in bytes. For example '.align 8' advances the location counter until it is a multiple of 8. If the location counter is already a multiple of 8, no change is needed. For the tic54x, the first expression is the alignment request in words. For other systems, including ppc, i386 using a.out format, arm and strongarm, it is the number of low-order zero bits the location counter -must have after advancement. For example `.align 3' advances the +must have after advancement. For example '.align 3' advances the location counter until it a multiple of 8. If the location counter is already a multiple of 8, no change is needed. This inconsistency is due to the different behaviors of the various native assemblers for these systems which GAS must emulate. GAS also -provides `.balign' and `.p2align' directives, described later, which -have a consistent behavior across all architectures (but are specific -to GAS). +provides '.balign' and '.p2align' directives, described later, which +have a consistent behavior across all architectures (but are specific to +GAS).  File: as.info, Node: Altmacro, Next: Ascii, Prev: Align, Up: Pseudo Ops -7.4 `.altmacro' +7.4 '.altmacro' =============== Enable alternate macro mode, enabling: -`LOCAL NAME [ , ... ]' - One additional directive, `LOCAL', is available. It is used to +'LOCAL NAME [ , ... ]' + One additional directive, 'LOCAL', is available. It is used to generate a string replacement for each of the NAME arguments, and replace any instances of NAME in each macro expansion. The replacement string is unique in the assembly, and different for - each separate macro expansion. `LOCAL' allows you to write macros + each separate macro expansion. 'LOCAL' allows you to write macros that define symbols, without fear of conflict between separate macro expansions. -`String delimiters' +'String delimiters' You can write strings delimited in these other ways besides - `"STRING"': + '"STRING"': - `'STRING'' + ''STRING'' You can delimit strings with single-quote characters. - `' + '' You can delimit strings with matching angle brackets. -`single-character string escape' +'single-character string escape' To include any single character literally in a string (even if the character would otherwise have some special meaning), you can - prefix the character with `!' (an exclamation mark). For example, - you can write `<4.3 !> 5.4!!>' to get the literal text `4.3 > + prefix the character with '!' (an exclamation mark). For example, + you can write '<4.3 !> 5.4!!>' to get the literal text '4.3 > 5.4!'. -`Expression results as strings' - You can write `%EXPR' to evaluate the expression EXPR and use the +'Expression results as strings' + You can write '%EXPR' to evaluate the expression EXPR and use the result as a string.  File: as.info, Node: Ascii, Next: Asciz, Prev: Altmacro, Up: Pseudo Ops -7.5 `.ascii "STRING"'... +7.5 '.ascii "STRING"'... ======================== -`.ascii' expects zero or more string literals (*note Strings::) +'.ascii' expects zero or more string literals (*note Strings::) separated by commas. It assembles each string (with no automatic trailing zero byte) into consecutive addresses.  File: as.info, Node: Asciz, Next: Balign, Prev: Ascii, Up: Pseudo Ops -7.6 `.asciz "STRING"'... +7.6 '.asciz "STRING"'... ======================== -`.asciz' is just like `.ascii', but each string is followed by a zero -byte. The "z" in `.asciz' stands for "zero". +'.asciz' is just like '.ascii', but each string is followed by a zero +byte. The "z" in '.asciz' stands for "zero".  File: as.info, Node: Balign, Next: Bundle directives, Prev: Asciz, Up: Pseudo Ops -7.7 `.balign[wl] ABS-EXPR, ABS-EXPR, ABS-EXPR' +7.7 '.balign[wl] ABS-EXPR, ABS-EXPR, ABS-EXPR' ============================================== Pad the location counter (in the current subsection) to a particular storage boundary. The first expression (which must be absolute) is the -alignment request in bytes. For example `.balign 8' advances the +alignment request in bytes. For example '.balign 8' advances the location counter until it is a multiple of 8. If the location counter is already a multiple of 8, no change is needed. @@ -3418,21 +3334,21 @@ The third expression is also absolute, and is also optional. If it is present, it is the maximum number of bytes that should be skipped by -this alignment directive. If doing the alignment would require -skipping more bytes than the specified maximum, then the alignment is -not done at all. You can omit the fill value (the second argument) -entirely by simply using two commas after the required alignment; this -can be useful if you want the alignment to be filled with no-op -instructions when appropriate. - - The `.balignw' and `.balignl' directives are variants of the -`.balign' directive. The `.balignw' directive treats the fill pattern -as a two byte word value. The `.balignl' directives treats the fill -pattern as a four byte longword value. For example, `.balignw -4,0x368d' will align to a multiple of 4. If it skips two bytes, they -will be filled in with the value 0x368d (the exact placement of the -bytes depends upon the endianness of the processor). If it skips 1 or -3 bytes, the fill value is undefined. +this alignment directive. If doing the alignment would require skipping +more bytes than the specified maximum, then the alignment is not done at +all. You can omit the fill value (the second argument) entirely by +simply using two commas after the required alignment; this can be useful +if you want the alignment to be filled with no-op instructions when +appropriate. + + The '.balignw' and '.balignl' directives are variants of the +'.balign' directive. The '.balignw' directive treats the fill pattern +as a two byte word value. The '.balignl' directives treats the fill +pattern as a four byte longword value. For example, '.balignw 4,0x368d' +will align to a multiple of 4. If it skips two bytes, they will be +filled in with the value 0x368d (the exact placement of the bytes +depends upon the endianness of the processor). If it skips 1 or 3 +bytes, the fill value is undefined.  File: as.info, Node: Bundle directives, Next: Byte, Prev: Balign, Up: Pseudo Ops @@ -3440,64 +3356,64 @@ 7.8 Bundle directives ===================== -7.8.1 `.bundle_align_mode ABS-EXPR' +7.8.1 '.bundle_align_mode ABS-EXPR' ----------------------------------- -`.bundle_align_mode' enables or disables "aligned instruction bundle" -mode. In this mode, sequences of adjacent instructions are grouped -into fixed-sized "bundles". If the argument is zero, this mode is -disabled (which is the default state). If the argument it not zero, it -gives the size of an instruction bundle as a power of two (as for the -`.p2align' directive, *note P2align::). +'.bundle_align_mode' enables or disables "aligned instruction bundle" +mode. In this mode, sequences of adjacent instructions are grouped into +fixed-sized "bundles". If the argument is zero, this mode is disabled +(which is the default state). If the argument it not zero, it gives the +size of an instruction bundle as a power of two (as for the '.p2align' +directive, *note P2align::). For some targets, it's an ABI requirement that no instruction may span a certain aligned boundary. A "bundle" is simply a sequence of instructions that starts on an aligned boundary. For example, if -ABS-EXPR is `5' then the bundle size is 32, so each aligned chunk of 32 +ABS-EXPR is '5' then the bundle size is 32, so each aligned chunk of 32 bytes is a bundle. When aligned instruction bundle mode is in effect, no single instruction may span a boundary between bundles. If an instruction would start too close to the end of a bundle for the length of that particular instruction to fit within the bundle, then the space at the end of that bundle is filled with no-op instructions so the -instruction starts in the next bundle. As a corollary, it's an error -if any single instruction's encoding is longer than the bundle size. +instruction starts in the next bundle. As a corollary, it's an error if +any single instruction's encoding is longer than the bundle size. -7.8.2 `.bundle_lock' and `.bundle_unlock' +7.8.2 '.bundle_lock' and '.bundle_unlock' ----------------------------------------- -The `.bundle_lock' and directive `.bundle_unlock' directives allow +The '.bundle_lock' and directive '.bundle_unlock' directives allow explicit control over instruction bundle padding. These directives are -only valid when `.bundle_align_mode' has been used to enable aligned +only valid when '.bundle_align_mode' has been used to enable aligned instruction bundle mode. It's an error if they appear when -`.bundle_align_mode' has not been used at all, or when the last -directive was `.bundle_align_mode 0'. +'.bundle_align_mode' has not been used at all, or when the last +directive was '.bundle_align_mode 0'. For some targets, it's an ABI requirement that certain instructions may appear only as part of specified permissible sequences of multiple -instructions, all within the same bundle. A pair of `.bundle_lock' and -`.bundle_unlock' directives define a "bundle-locked" instruction +instructions, all within the same bundle. A pair of '.bundle_lock' and +'.bundle_unlock' directives define a "bundle-locked" instruction sequence. For purposes of aligned instruction bundle mode, a sequence -starting with `.bundle_lock' and ending with `.bundle_unlock' is -treated as a single instruction. That is, the entire sequence must fit -into a single bundle and may not span a bundle boundary. If necessary, -no-op instructions will be inserted before the first instruction of the +starting with '.bundle_lock' and ending with '.bundle_unlock' is treated +as a single instruction. That is, the entire sequence must fit into a +single bundle and may not span a bundle boundary. If necessary, no-op +instructions will be inserted before the first instruction of the sequence so that the whole sequence starts on an aligned bundle boundary. It's an error if the sequence is longer than the bundle size. - For convenience when using `.bundle_lock' and `.bundle_unlock' -inside assembler macros (*note Macro::), bundle-locked sequences may be -nested. That is, a second `.bundle_lock' directive before the next -`.bundle_unlock' directive has no effect except that it must be matched -by another closing `.bundle_unlock' so that there is the same number of -`.bundle_lock' and `.bundle_unlock' directives. + For convenience when using '.bundle_lock' and '.bundle_unlock' inside +assembler macros (*note Macro::), bundle-locked sequences may be nested. +That is, a second '.bundle_lock' directive before the next +'.bundle_unlock' directive has no effect except that it must be matched +by another closing '.bundle_unlock' so that there is the same number of +'.bundle_lock' and '.bundle_unlock' directives.  File: as.info, Node: Byte, Next: CFI directives, Prev: Bundle directives, Up: Pseudo Ops -7.9 `.byte EXPRESSIONS' +7.9 '.byte EXPRESSIONS' ======================= -`.byte' expects zero or more expressions, separated by commas. Each +'.byte' expects zero or more expressions, separated by commas. Each expression is assembled into the next byte.  @@ -3506,175 +3422,175 @@ 7.10 CFI directives =================== -7.10.1 `.cfi_sections SECTION_LIST' +7.10.1 '.cfi_sections SECTION_LIST' ----------------------------------- -`.cfi_sections' may be used to specify whether CFI directives should -emit `.eh_frame' section and/or `.debug_frame' section. If -SECTION_LIST is `.eh_frame', `.eh_frame' is emitted, if SECTION_LIST is -`.debug_frame', `.debug_frame' is emitted. To emit both use -`.eh_frame, .debug_frame'. The default if this directive is not used -is `.cfi_sections .eh_frame'. +'.cfi_sections' may be used to specify whether CFI directives should +emit '.eh_frame' section and/or '.debug_frame' section. If SECTION_LIST +is '.eh_frame', '.eh_frame' is emitted, if SECTION_LIST is +'.debug_frame', '.debug_frame' is emitted. To emit both use '.eh_frame, +.debug_frame'. The default if this directive is not used is +'.cfi_sections .eh_frame'. On targets that support compact unwinding tables these can be -generated by specifying `.eh_frame_entry' instead of `.eh_frame'. +generated by specifying '.eh_frame_entry' instead of '.eh_frame'. - Some targets may support an additional name, such as `.c6xabi.exidx' -which is used by the target. + Some targets may support an additional name, such as '.c6xabi.exidx' +which is used by the target. - The `.cfi_sections' directive can be repeated, with the same or + The '.cfi_sections' directive can be repeated, with the same or different arguments, provided that CFI generation has not yet started. Once CFI generation has started however the section list is fixed and any attempts to redefine it will result in an error. -7.10.2 `.cfi_startproc [simple]' +7.10.2 '.cfi_startproc [simple]' -------------------------------- -`.cfi_startproc' is used at the beginning of each function that should -have an entry in `.eh_frame'. It initializes some internal data -structures. Don't forget to close the function by `.cfi_endproc'. +'.cfi_startproc' is used at the beginning of each function that should +have an entry in '.eh_frame'. It initializes some internal data +structures. Don't forget to close the function by '.cfi_endproc'. - Unless `.cfi_startproc' is used along with parameter `simple' it -also emits some architecture dependent initial CFI instructions. + Unless '.cfi_startproc' is used along with parameter 'simple' it also +emits some architecture dependent initial CFI instructions. -7.10.3 `.cfi_endproc' +7.10.3 '.cfi_endproc' --------------------- -`.cfi_endproc' is used at the end of a function where it closes its -unwind entry previously opened by `.cfi_startproc', and emits it to -`.eh_frame'. +'.cfi_endproc' is used at the end of a function where it closes its +unwind entry previously opened by '.cfi_startproc', and emits it to +'.eh_frame'. -7.10.4 `.cfi_personality ENCODING [, EXP]' +7.10.4 '.cfi_personality ENCODING [, EXP]' ------------------------------------------ -`.cfi_personality' defines personality routine and its encoding. +'.cfi_personality' defines personality routine and its encoding. ENCODING must be a constant determining how the personality should be -encoded. If it is 255 (`DW_EH_PE_omit'), second argument is not +encoded. If it is 255 ('DW_EH_PE_omit'), second argument is not present, otherwise second argument should be a constant or a symbol name. When using indirect encodings, the symbol provided should be the location where personality can be loaded from, not the personality -routine itself. The default after `.cfi_startproc' is -`.cfi_personality 0xff', no personality routine. +routine itself. The default after '.cfi_startproc' is '.cfi_personality +0xff', no personality routine. -7.10.5 `.cfi_personality_id ID' +7.10.5 '.cfi_personality_id ID' ------------------------------- -`cfi_personality_id' defines a personality routine by its index as +'cfi_personality_id' defines a personality routine by its index as defined in a compact unwinding format. Only valid when generating -compact EH frames (i.e. with `.cfi_sections eh_frame_entry'. +compact EH frames (i.e. with '.cfi_sections eh_frame_entry'. -7.10.6 `.cfi_fde_data [OPCODE1 [, ...]]' +7.10.6 '.cfi_fde_data [OPCODE1 [, ...]]' ---------------------------------------- -`cfi_fde_data' is used to describe the compact unwind opcodes to be -used for the current function. These are emitted inline in the -`.eh_frame_entry' section if small enough and there is no LSDA, or in -the `.gnu.extab' section otherwise. Only valid when generating compact -EH frames (i.e. with `.cfi_sections eh_frame_entry'. +'cfi_fde_data' is used to describe the compact unwind opcodes to be used +for the current function. These are emitted inline in the +'.eh_frame_entry' section if small enough and there is no LSDA, or in +the '.gnu.extab' section otherwise. Only valid when generating compact +EH frames (i.e. with '.cfi_sections eh_frame_entry'. -7.10.7 `.cfi_lsda ENCODING [, EXP]' +7.10.7 '.cfi_lsda ENCODING [, EXP]' ----------------------------------- -`.cfi_lsda' defines LSDA and its encoding. ENCODING must be a constant +'.cfi_lsda' defines LSDA and its encoding. ENCODING must be a constant determining how the LSDA should be encoded. If it is 255 -(`DW_EH_PE_omit'), the second argument is not present, otherwise the +('DW_EH_PE_omit'), the second argument is not present, otherwise the second argument should be a constant or a symbol name. The default -after `.cfi_startproc' is `.cfi_lsda 0xff', meaning that no LSDA is +after '.cfi_startproc' is '.cfi_lsda 0xff', meaning that no LSDA is present. -7.10.8 `.cfi_inline_lsda' [ALIGN] +7.10.8 '.cfi_inline_lsda' [ALIGN] --------------------------------- -`.cfi_inline_lsda' marks the start of a LSDA data section and switches -to the corresponding `.gnu.extab' section. Must be preceded by a CFI -block containing a `.cfi_lsda' directive. Only valid when generating -compact EH frames (i.e. with `.cfi_sections eh_frame_entry'. +'.cfi_inline_lsda' marks the start of a LSDA data section and switches +to the corresponding '.gnu.extab' section. Must be preceded by a CFI +block containing a '.cfi_lsda' directive. Only valid when generating +compact EH frames (i.e. with '.cfi_sections eh_frame_entry'. The table header and unwinding opcodes will be generated at this point, so that they are immediately followed by the LSDA data. The -symbol referenced by the `.cfi_lsda' directive should still be defined +symbol referenced by the '.cfi_lsda' directive should still be defined in case a fallback FDE based encoding is used. The LSDA data is terminated by a section directive. The optional ALIGN argument specifies the alignment required. The -alignment is specified as a power of two, as with the `.p2align' +alignment is specified as a power of two, as with the '.p2align' directive. -7.10.9 `.cfi_def_cfa REGISTER, OFFSET' +7.10.9 '.cfi_def_cfa REGISTER, OFFSET' -------------------------------------- -`.cfi_def_cfa' defines a rule for computing CFA as: take address from +'.cfi_def_cfa' defines a rule for computing CFA as: take address from REGISTER and add OFFSET to it. -7.10.10 `.cfi_def_cfa_register REGISTER' +7.10.10 '.cfi_def_cfa_register REGISTER' ---------------------------------------- -`.cfi_def_cfa_register' modifies a rule for computing CFA. From now on -REGISTER will be used instead of the old one. Offset remains the same. +'.cfi_def_cfa_register' modifies a rule for computing CFA. From now on +REGISTER will be used instead of the old one. Offset remains the same. -7.10.11 `.cfi_def_cfa_offset OFFSET' +7.10.11 '.cfi_def_cfa_offset OFFSET' ------------------------------------ -`.cfi_def_cfa_offset' modifies a rule for computing CFA. Register -remains the same, but OFFSET is new. Note that it is the absolute +'.cfi_def_cfa_offset' modifies a rule for computing CFA. Register +remains the same, but OFFSET is new. Note that it is the absolute offset that will be added to a defined register to compute CFA address. -7.10.12 `.cfi_adjust_cfa_offset OFFSET' +7.10.12 '.cfi_adjust_cfa_offset OFFSET' --------------------------------------- -Same as `.cfi_def_cfa_offset' but OFFSET is a relative value that is +Same as '.cfi_def_cfa_offset' but OFFSET is a relative value that is added/substracted from the previous offset. -7.10.13 `.cfi_offset REGISTER, OFFSET' +7.10.13 '.cfi_offset REGISTER, OFFSET' -------------------------------------- Previous value of REGISTER is saved at offset OFFSET from CFA. -7.10.14 `.cfi_val_offset REGISTER, OFFSET' +7.10.14 '.cfi_val_offset REGISTER, OFFSET' ------------------------------------------ Previous value of REGISTER is CFA + OFFSET. -7.10.15 `.cfi_rel_offset REGISTER, OFFSET' +7.10.15 '.cfi_rel_offset REGISTER, OFFSET' ------------------------------------------ Previous value of REGISTER is saved at offset OFFSET from the current -CFA register. This is transformed to `.cfi_offset' using the known -displacement of the CFA register from the CFA. This is often easier to +CFA register. This is transformed to '.cfi_offset' using the known +displacement of the CFA register from the CFA. This is often easier to use, because the number will match the code it's annotating. -7.10.16 `.cfi_register REGISTER1, REGISTER2' +7.10.16 '.cfi_register REGISTER1, REGISTER2' -------------------------------------------- Previous value of REGISTER1 is saved in register REGISTER2. -7.10.17 `.cfi_restore REGISTER' +7.10.17 '.cfi_restore REGISTER' ------------------------------- -`.cfi_restore' says that the rule for REGISTER is now the same as it -was at the beginning of the function, after all initial instruction -added by `.cfi_startproc' were executed. +'.cfi_restore' says that the rule for REGISTER is now the same as it was +at the beginning of the function, after all initial instruction added by +'.cfi_startproc' were executed. -7.10.18 `.cfi_undefined REGISTER' +7.10.18 '.cfi_undefined REGISTER' --------------------------------- From now on the previous value of REGISTER can't be restored anymore. -7.10.19 `.cfi_same_value REGISTER' +7.10.19 '.cfi_same_value REGISTER' ---------------------------------- Current value of REGISTER is the same like in the previous frame, i.e. no restoration needed. -7.10.20 `.cfi_remember_state' and `.cfi_restore_state' +7.10.20 '.cfi_remember_state' and '.cfi_restore_state' ------------------------------------------------------ -`.cfi_remember_state' pushes the set of rules for every register onto an -implicit stack, while `.cfi_restore_state' pops them off the stack and -places them in the current row. This is useful for situations where -you have multiple `.cfi_*' directives that need to be undone due to the +'.cfi_remember_state' pushes the set of rules for every register onto an +implicit stack, while '.cfi_restore_state' pops them off the stack and +places them in the current row. This is useful for situations where you +have multiple '.cfi_*' directives that need to be undone due to the control flow of the program. For example, we could have something like -this (assuming the CFA is the value of `rbp'): +this (assuming the CFA is the value of 'rbp'): je label popq %rbx @@ -3688,12 +3604,12 @@ label: /* Do something else */ - Here, we want the `.cfi' directives to affect only the rows -corresponding to the instructions before `label'. This means we'd have -to add multiple `.cfi' directives after `label' to recreate the -original save locations of the registers, as well as setting the CFA -back to the value of `rbp'. This would be clumsy, and result in a -larger binary size. Instead, we can write: + Here, we want the '.cfi' directives to affect only the rows +corresponding to the instructions before 'label'. This means we'd have +to add multiple '.cfi' directives after 'label' to recreate the original +save locations of the registers, as well as setting the CFA back to the +value of 'rbp'. This would be clumsy, and result in a larger binary +size. Instead, we can write: je label popq %rbx @@ -3709,39 +3625,39 @@ .cfi_restore_state /* Do something else */ - That way, the rules for the instructions after `label' will be the -same as before the first `.cfi_restore' without having to use multiple -`.cfi' directives. + That way, the rules for the instructions after 'label' will be the +same as before the first '.cfi_restore' without having to use multiple +'.cfi' directives. -7.10.21 `.cfi_return_column REGISTER' +7.10.21 '.cfi_return_column REGISTER' ------------------------------------- -Change return column REGISTER, i.e. the return address is either +Change return column REGISTER, i.e. the return address is either directly in REGISTER or can be accessed by rules for REGISTER. -7.10.22 `.cfi_signal_frame' +7.10.22 '.cfi_signal_frame' --------------------------- Mark current function as signal trampoline. -7.10.23 `.cfi_window_save' +7.10.23 '.cfi_window_save' -------------------------- SPARC register window has been saved. -7.10.24 `.cfi_escape' EXPRESSION[, ...] +7.10.24 '.cfi_escape' EXPRESSION[, ...] --------------------------------------- Allows the user to add arbitrary bytes to the unwind info. One might -use this to add OS-specific CFI opcodes, or generic CFI opcodes that -GAS does not yet support. +use this to add OS-specific CFI opcodes, or generic CFI opcodes that GAS +does not yet support. -7.10.25 `.cfi_val_encoded_addr REGISTER, ENCODING, LABEL' +7.10.25 '.cfi_val_encoded_addr REGISTER, ENCODING, LABEL' --------------------------------------------------------- The current value of REGISTER is LABEL. The value of LABEL will be -encoded in the output file according to ENCODING; see the description -of `.cfi_personality' for details on this encoding. +encoded in the output file according to ENCODING; see the description of +'.cfi_personality' for details on this encoding. The usefulness of equating a register to a fixed label is probably limited to the return address register. Here, it can be useful to mark @@ -3752,101 +3668,101 @@  File: as.info, Node: Comm, Next: Data, Prev: CFI directives, Up: Pseudo Ops -7.11 `.comm SYMBOL , LENGTH ' +7.11 '.comm SYMBOL , LENGTH ' ============================= -`.comm' declares a common symbol named SYMBOL. When linking, a common +'.comm' declares a common symbol named SYMBOL. When linking, a common symbol in one object file may be merged with a defined or common symbol -of the same name in another object file. If `ld' does not see a +of the same name in another object file. If 'ld' does not see a definition for the symbol-just one or more common symbols-then it will allocate LENGTH bytes of uninitialized memory. LENGTH must be an -absolute expression. If `ld' sees multiple common symbols with the -same name, and they do not all have the same size, it will allocate -space using the largest size. +absolute expression. If 'ld' sees multiple common symbols with the same +name, and they do not all have the same size, it will allocate space +using the largest size. - When using ELF or (as a GNU extension) PE, the `.comm' directive + When using ELF or (as a GNU extension) PE, the '.comm' directive takes an optional third argument. This is the desired alignment of the symbol, specified for ELF as a byte boundary (for example, an alignment of 16 means that the least significant 4 bits of the address should be zero), and for PE as a power of two (for example, an alignment of 5 -means aligned to a 32-byte boundary). The alignment must be an -absolute expression, and it must be a power of two. If `ld' allocates +means aligned to a 32-byte boundary). The alignment must be an absolute +expression, and it must be a power of two. If 'ld' allocates uninitialized memory for the common symbol, it will use the alignment -when placing the symbol. If no alignment is specified, `as' will set -the alignment to the largest power of two less than or equal to the -size of the symbol, up to a maximum of 16 on ELF, or the default -section alignment of 4 on PE(1). +when placing the symbol. If no alignment is specified, 'as' will set +the alignment to the largest power of two less than or equal to the size +of the symbol, up to a maximum of 16 on ELF, or the default section +alignment of 4 on PE(1). - The syntax for `.comm' differs slightly on the HPPA. The syntax is -`SYMBOL .comm, LENGTH'; SYMBOL is optional. + The syntax for '.comm' differs slightly on the HPPA. The syntax is +'SYMBOL .comm, LENGTH'; SYMBOL is optional. ---------- Footnotes ---------- (1) This is not the same as the executable image file alignment -controlled by `ld''s `--section-alignment' option; image file sections +controlled by 'ld''s '--section-alignment' option; image file sections in PE are aligned to multiples of 4096, which is far too large an alignment for ordinary variables. It is rather the default alignment -for (non-debug) sections within object (`*.o') files, which are less +for (non-debug) sections within object ('*.o') files, which are less strictly aligned.  File: as.info, Node: Data, Next: Def, Prev: Comm, Up: Pseudo Ops -7.12 `.data SUBSECTION' +7.12 '.data SUBSECTION' ======================= -`.data' tells `as' to assemble the following statements onto the end of +'.data' tells 'as' to assemble the following statements onto the end of the data subsection numbered SUBSECTION (which is an absolute expression). If SUBSECTION is omitted, it defaults to zero.  File: as.info, Node: Def, Next: Desc, Prev: Data, Up: Pseudo Ops -7.13 `.def NAME' +7.13 '.def NAME' ================ Begin defining debugging information for a symbol NAME; the definition -extends until the `.endef' directive is encountered. +extends until the '.endef' directive is encountered.  File: as.info, Node: Desc, Next: Dim, Prev: Def, Up: Pseudo Ops -7.14 `.desc SYMBOL, ABS-EXPRESSION' +7.14 '.desc SYMBOL, ABS-EXPRESSION' =================================== This directive sets the descriptor of the symbol (*note Symbol Attributes::) to the low 16 bits of an absolute expression. - The `.desc' directive is not available when `as' is configured for -COFF output; it is only for `a.out' or `b.out' object format. For the -sake of compatibility, `as' accepts it, but produces no output, when + The '.desc' directive is not available when 'as' is configured for +COFF output; it is only for 'a.out' or 'b.out' object format. For the +sake of compatibility, 'as' accepts it, but produces no output, when configured for COFF.  File: as.info, Node: Dim, Next: Double, Prev: Desc, Up: Pseudo Ops -7.15 `.dim' +7.15 '.dim' =========== This directive is generated by compilers to include auxiliary debugging information in the symbol table. It is only permitted inside -`.def'/`.endef' pairs. +'.def'/'.endef' pairs.  File: as.info, Node: Double, Next: Eject, Prev: Dim, Up: Pseudo Ops -7.16 `.double FLONUMS' +7.16 '.double FLONUMS' ====================== -`.double' expects zero or more flonums, separated by commas. It +'.double' expects zero or more flonums, separated by commas. It assembles floating point numbers. The exact kind of floating point -numbers emitted depends on how `as' is configured. *Note Machine +numbers emitted depends on how 'as' is configured. *Note Machine Dependencies::.  File: as.info, Node: Eject, Next: Else, Prev: Double, Up: Pseudo Ops -7.17 `.eject' +7.17 '.eject' ============= Force a page break at this point, when generating assembly listings. @@ -3854,80 +3770,80 @@  File: as.info, Node: Else, Next: Elseif, Prev: Eject, Up: Pseudo Ops -7.18 `.else' +7.18 '.else' ============ -`.else' is part of the `as' support for conditional assembly; see *Note -`.if': If. It marks the beginning of a section of code to be assembled -if the condition for the preceding `.if' was false. +'.else' is part of the 'as' support for conditional assembly; see *note +'.if': If. It marks the beginning of a section of code to be assembled +if the condition for the preceding '.if' was false.  File: as.info, Node: Elseif, Next: End, Prev: Else, Up: Pseudo Ops -7.19 `.elseif' +7.19 '.elseif' ============== -`.elseif' is part of the `as' support for conditional assembly; see -*Note `.if': If. It is shorthand for beginning a new `.if' block that -would otherwise fill the entire `.else' section. +'.elseif' is part of the 'as' support for conditional assembly; see +*note '.if': If. It is shorthand for beginning a new '.if' block that +would otherwise fill the entire '.else' section.  File: as.info, Node: End, Next: Endef, Prev: Elseif, Up: Pseudo Ops -7.20 `.end' +7.20 '.end' =========== -`.end' marks the end of the assembly file. `as' does not process -anything in the file past the `.end' directive. +'.end' marks the end of the assembly file. 'as' does not process +anything in the file past the '.end' directive.  File: as.info, Node: Endef, Next: Endfunc, Prev: End, Up: Pseudo Ops -7.21 `.endef' +7.21 '.endef' ============= -This directive flags the end of a symbol definition begun with `.def'. +This directive flags the end of a symbol definition begun with '.def'.  File: as.info, Node: Endfunc, Next: Endif, Prev: Endef, Up: Pseudo Ops -7.22 `.endfunc' +7.22 '.endfunc' =============== -`.endfunc' marks the end of a function specified with `.func'. +'.endfunc' marks the end of a function specified with '.func'.  File: as.info, Node: Endif, Next: Equ, Prev: Endfunc, Up: Pseudo Ops -7.23 `.endif' +7.23 '.endif' ============= -`.endif' is part of the `as' support for conditional assembly; it marks +'.endif' is part of the 'as' support for conditional assembly; it marks the end of a block of code that is only assembled conditionally. *Note -`.if': If. +'.if': If.  File: as.info, Node: Equ, Next: Equiv, Prev: Endif, Up: Pseudo Ops -7.24 `.equ SYMBOL, EXPRESSION' +7.24 '.equ SYMBOL, EXPRESSION' ============================== -This directive sets the value of SYMBOL to EXPRESSION. It is -synonymous with `.set'; see *Note `.set': Set. +This directive sets the value of SYMBOL to EXPRESSION. It is synonymous +with '.set'; see *note '.set': Set. - The syntax for `equ' on the HPPA is `SYMBOL .equ EXPRESSION'. + The syntax for 'equ' on the HPPA is 'SYMBOL .equ EXPRESSION'. - The syntax for `equ' on the Z80 is `SYMBOL equ EXPRESSION'. On the + The syntax for 'equ' on the Z80 is 'SYMBOL equ EXPRESSION'. On the Z80 it is an eror if SYMBOL is already defined, but the symbol is not -protected from later redefinition. Compare *Note Equiv::. +protected from later redefinition. Compare *note Equiv::.  File: as.info, Node: Equiv, Next: Eqv, Prev: Equ, Up: Pseudo Ops -7.25 `.equiv SYMBOL, EXPRESSION' +7.25 '.equiv SYMBOL, EXPRESSION' ================================ -The `.equiv' directive is like `.equ' and `.set', except that the +The '.equiv' directive is like '.equ' and '.set', except that the assembler will signal an error if SYMBOL is already defined. Note a symbol which has been referenced but not actually defined is considered to be undefined. @@ -3943,10 +3859,10 @@  File: as.info, Node: Eqv, Next: Err, Prev: Equiv, Up: Pseudo Ops -7.26 `.eqv SYMBOL, EXPRESSION' +7.26 '.eqv SYMBOL, EXPRESSION' ============================== -The `.eqv' directive is like `.equiv', but no attempt is made to +The '.eqv' directive is like '.equiv', but no attempt is made to evaluate the expression or any part of it immediately. Instead each time the resulting symbol is used in an expression, a snapshot of its current value is taken. @@ -3954,31 +3870,31 @@  File: as.info, Node: Err, Next: Error, Prev: Eqv, Up: Pseudo Ops -7.27 `.err' +7.27 '.err' =========== -If `as' assembles a `.err' directive, it will print an error message -and, unless the `-Z' option was used, it will not generate an object +If 'as' assembles a '.err' directive, it will print an error message +and, unless the '-Z' option was used, it will not generate an object file. This can be used to signal an error in conditionally compiled code.  File: as.info, Node: Error, Next: Exitm, Prev: Err, Up: Pseudo Ops -7.28 `.error "STRING"' +7.28 '.error "STRING"' ====================== -Similarly to `.err', this directive emits an error, but you can specify +Similarly to '.err', this directive emits an error, but you can specify a string that will be emitted as the error message. If you don't -specify the message, it defaults to `".error directive invoked in -source file"'. *Note Error and Warning Messages: Errors. +specify the message, it defaults to '".error directive invoked in source +file"'. *Note Error and Warning Messages: Errors. .error "This code has not been assembled and tested."  File: as.info, Node: Exitm, Next: Extern, Prev: Error, Up: Pseudo Ops -7.29 `.exitm' +7.29 '.exitm' ============= Exit early from the current macro definition. *Note Macro::. @@ -3986,54 +3902,54 @@  File: as.info, Node: Extern, Next: Fail, Prev: Exitm, Up: Pseudo Ops -7.30 `.extern' +7.30 '.extern' ============== -`.extern' is accepted in the source program--for compatibility with -other assemblers--but it is ignored. `as' treats all undefined symbols +'.extern' is accepted in the source program--for compatibility with +other assemblers--but it is ignored. 'as' treats all undefined symbols as external.  File: as.info, Node: Fail, Next: File, Prev: Extern, Up: Pseudo Ops -7.31 `.fail EXPRESSION' +7.31 '.fail EXPRESSION' ======================= Generates an error or a warning. If the value of the EXPRESSION is 500 -or more, `as' will print a warning message. If the value is less than -500, `as' will print an error message. The message will include the +or more, 'as' will print a warning message. If the value is less than +500, 'as' will print an error message. The message will include the value of EXPRESSION. This can occasionally be useful inside complex nested macros or conditional assembly.  File: as.info, Node: File, Next: Fill, Prev: Fail, Up: Pseudo Ops -7.32 `.file' +7.32 '.file' ============ -There are two different versions of the `.file' directive. Targets -that support DWARF2 line number information use the DWARF2 version of -`.file'. Other targets use the default version. +There are two different versions of the '.file' directive. Targets that +support DWARF2 line number information use the DWARF2 version of +'.file'. Other targets use the default version. Default Version --------------- -This version of the `.file' directive tells `as' that we are about to +This version of the '.file' directive tells 'as' that we are about to start a new logical file. The syntax is: .file STRING STRING is the new file name. In general, the filename is recognized -whether or not it is surrounded by quotes `"'; but if you wish to -specify an empty file name, you must give the quotes-`""'. This +whether or not it is surrounded by quotes '"'; but if you wish to +specify an empty file name, you must give the quotes-'""'. This statement may go away in future: it is only recognized to be compatible -with old `as' programs. +with old 'as' programs. DWARF2 Version -------------- -When emitting DWARF2 line number information, `.file' assigns filenames -to the `.debug_line' file name table. The syntax is: +When emitting DWARF2 line number information, '.file' assigns filenames +to the '.debug_line' file name table. The syntax is: .file FILENO FILENAME @@ -4042,14 +3958,14 @@ literal. The detail of filename indices is exposed to the user because the -filename table is shared with the `.debug_info' section of the DWARF2 +filename table is shared with the '.debug_info' section of the DWARF2 debugging information, and thus the user must know the exact indices that table entries will have.  File: as.info, Node: Fill, Next: Float, Prev: File, Up: Pseudo Ops -7.33 `.fill REPEAT , SIZE , VALUE' +7.33 '.fill REPEAT , SIZE , VALUE' ================================== REPEAT, SIZE and VALUE are absolute expressions. This emits REPEAT @@ -4058,8 +3974,8 @@ compatible with other people's assemblers. The contents of each REPEAT bytes is taken from an 8-byte number. The highest order 4 bytes are zero. The lowest order 4 bytes are VALUE rendered in the byte-order of -an integer on the computer `as' is assembling for. Each SIZE bytes in -a repetition is taken from the lowest order SIZE bytes of this number. +an integer on the computer 'as' is assembling for. Each SIZE bytes in a +repetition is taken from the lowest order SIZE bytes of this number. Again, this bizarre behavior is compatible with other people's assemblers. @@ -4070,51 +3986,51 @@  File: as.info, Node: Float, Next: Func, Prev: Fill, Up: Pseudo Ops -7.34 `.float FLONUMS' +7.34 '.float FLONUMS' ===================== This directive assembles zero or more flonums, separated by commas. It -has the same effect as `.single'. The exact kind of floating point -numbers emitted depends on how `as' is configured. *Note Machine +has the same effect as '.single'. The exact kind of floating point +numbers emitted depends on how 'as' is configured. *Note Machine Dependencies::.  File: as.info, Node: Func, Next: Global, Prev: Float, Up: Pseudo Ops -7.35 `.func NAME[,LABEL]' +7.35 '.func NAME[,LABEL]' ========================= -`.func' emits debugging information to denote function NAME, and is +'.func' emits debugging information to denote function NAME, and is ignored unless the file is assembled with debugging enabled. Only -`--gstabs[+]' is currently supported. LABEL is the entry point of the -function and if omitted NAME prepended with the `leading char' is used. -`leading char' is usually `_' or nothing, depending on the target. All -functions are currently defined to have `void' return type. The -function must be terminated with `.endfunc'. +'--gstabs[+]' is currently supported. LABEL is the entry point of the +function and if omitted NAME prepended with the 'leading char' is used. +'leading char' is usually '_' or nothing, depending on the target. All +functions are currently defined to have 'void' return type. The +function must be terminated with '.endfunc'.  File: as.info, Node: Global, Next: Gnu_attribute, Prev: Func, Up: Pseudo Ops -7.36 `.global SYMBOL', `.globl SYMBOL' +7.36 '.global SYMBOL', '.globl SYMBOL' ====================================== -`.global' makes the symbol visible to `ld'. If you define SYMBOL in +'.global' makes the symbol visible to 'ld'. If you define SYMBOL in your partial program, its value is made available to other partial programs that are linked with it. Otherwise, SYMBOL takes its attributes from a symbol of the same name from another file linked into the same program. - Both spellings (`.globl' and `.global') are accepted, for + Both spellings ('.globl' and '.global') are accepted, for compatibility with other assemblers. - On the HPPA, `.global' is not always enough to make it accessible to -other partial programs. You may need the HPPA-only `.EXPORT' directive + On the HPPA, '.global' is not always enough to make it accessible to +other partial programs. You may need the HPPA-only '.EXPORT' directive as well. *Note HPPA Assembler Directives: HPPA Directives.  File: as.info, Node: Gnu_attribute, Next: Hidden, Prev: Global, Up: Pseudo Ops -7.37 `.gnu_attribute TAG,VALUE' +7.37 '.gnu_attribute TAG,VALUE' =============================== Record a GNU object attribute for this file. *Note Object Attributes::. @@ -4122,161 +4038,161 @@  File: as.info, Node: Hidden, Next: hword, Prev: Gnu_attribute, Up: Pseudo Ops -7.38 `.hidden NAMES' +7.38 '.hidden NAMES' ==================== This is one of the ELF visibility directives. The other two are -`.internal' (*note `.internal': Internal.) and `.protected' (*note -`.protected': Protected.). +'.internal' (*note '.internal': Internal.) and '.protected' (*note +'.protected': Protected.). This directive overrides the named symbols default visibility (which -is set by their binding: local, global or weak). The directive sets -the visibility to `hidden' which means that the symbols are not visible -to other components. Such symbols are always considered to be -`protected' as well. +is set by their binding: local, global or weak). The directive sets the +visibility to 'hidden' which means that the symbols are not visible to +other components. Such symbols are always considered to be 'protected' +as well.  File: as.info, Node: hword, Next: Ident, Prev: Hidden, Up: Pseudo Ops -7.39 `.hword EXPRESSIONS' +7.39 '.hword EXPRESSIONS' ========================= This expects zero or more EXPRESSIONS, and emits a 16 bit number for each. - This directive is a synonym for `.short'; depending on the target -architecture, it may also be a synonym for `.word'. + This directive is a synonym for '.short'; depending on the target +architecture, it may also be a synonym for '.word'.  File: as.info, Node: Ident, Next: If, Prev: hword, Up: Pseudo Ops -7.40 `.ident' +7.40 '.ident' ============= -This directive is used by some assemblers to place tags in object -files. The behavior of this directive varies depending on the target. -When using the a.out object file format, `as' simply accepts the -directive for source-file compatibility with existing assemblers, but -does not emit anything for it. When using COFF, comments are emitted -to the `.comment' or `.rdata' section, depending on the target. When -using ELF, comments are emitted to the `.comment' section. +This directive is used by some assemblers to place tags in object files. +The behavior of this directive varies depending on the target. When +using the a.out object file format, 'as' simply accepts the directive +for source-file compatibility with existing assemblers, but does not +emit anything for it. When using COFF, comments are emitted to the +'.comment' or '.rdata' section, depending on the target. When using +ELF, comments are emitted to the '.comment' section.  File: as.info, Node: If, Next: Incbin, Prev: Ident, Up: Pseudo Ops -7.41 `.if ABSOLUTE EXPRESSION' +7.41 '.if ABSOLUTE EXPRESSION' ============================== -`.if' marks the beginning of a section of code which is only considered +'.if' marks the beginning of a section of code which is only considered part of the source program being assembled if the argument (which must be an ABSOLUTE EXPRESSION) is non-zero. The end of the conditional -section of code must be marked by `.endif' (*note `.endif': Endif.); +section of code must be marked by '.endif' (*note '.endif': Endif.); optionally, you may include code for the alternative condition, flagged -by `.else' (*note `.else': Else.). If you have several conditions to -check, `.elseif' may be used to avoid nesting blocks if/else within -each subsequent `.else' block. - - The following variants of `.if' are also supported: -`.ifdef SYMBOL' - Assembles the following section of code if the specified SYMBOL - has been defined. Note a symbol which has been referenced but not - yet defined is considered to be undefined. +by '.else' (*note '.else': Else.). If you have several conditions to +check, '.elseif' may be used to avoid nesting blocks if/else within each +subsequent '.else' block. + + The following variants of '.if' are also supported: +'.ifdef SYMBOL' + Assembles the following section of code if the specified SYMBOL has + been defined. Note a symbol which has been referenced but not yet + defined is considered to be undefined. -`.ifb TEXT' +'.ifb TEXT' Assembles the following section of code if the operand is blank (empty). -`.ifc STRING1,STRING2' +'.ifc STRING1,STRING2' Assembles the following section of code if the two strings are the - same. The strings may be optionally quoted with single quotes. - If they are not quoted, the first string stops at the first comma, - and the second string stops at the end of the line. Strings which - contain whitespace should be quoted. The string comparison is - case sensitive. + same. The strings may be optionally quoted with single quotes. If + they are not quoted, the first string stops at the first comma, and + the second string stops at the end of the line. Strings which + contain whitespace should be quoted. The string comparison is case + sensitive. -`.ifeq ABSOLUTE EXPRESSION' +'.ifeq ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is zero. -`.ifeqs STRING1,STRING2' - Another form of `.ifc'. The strings must be quoted using double +'.ifeqs STRING1,STRING2' + Another form of '.ifc'. The strings must be quoted using double quotes. -`.ifge ABSOLUTE EXPRESSION' +'.ifge ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is greater than or equal to zero. -`.ifgt ABSOLUTE EXPRESSION' +'.ifgt ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is greater than zero. -`.ifle ABSOLUTE EXPRESSION' +'.ifle ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is less than or equal to zero. -`.iflt ABSOLUTE EXPRESSION' +'.iflt ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is less than zero. -`.ifnb TEXT' - Like `.ifb', but the sense of the test is reversed: this assembles +'.ifnb TEXT' + Like '.ifb', but the sense of the test is reversed: this assembles the following section of code if the operand is non-blank (non-empty). -`.ifnc STRING1,STRING2.' - Like `.ifc', but the sense of the test is reversed: this assembles +'.ifnc STRING1,STRING2.' + Like '.ifc', but the sense of the test is reversed: this assembles the following section of code if the two strings are not the same. -`.ifndef SYMBOL' -`.ifnotdef SYMBOL' - Assembles the following section of code if the specified SYMBOL - has not been defined. Both spelling variants are equivalent. - Note a symbol which has been referenced but not yet defined is - considered to be undefined. +'.ifndef SYMBOL' +'.ifnotdef SYMBOL' + Assembles the following section of code if the specified SYMBOL has + not been defined. Both spelling variants are equivalent. Note a + symbol which has been referenced but not yet defined is considered + to be undefined. -`.ifne ABSOLUTE EXPRESSION' +'.ifne ABSOLUTE EXPRESSION' Assembles the following section of code if the argument is not - equal to zero (in other words, this is equivalent to `.if'). + equal to zero (in other words, this is equivalent to '.if'). -`.ifnes STRING1,STRING2' - Like `.ifeqs', but the sense of the test is reversed: this +'.ifnes STRING1,STRING2' + Like '.ifeqs', but the sense of the test is reversed: this assembles the following section of code if the two strings are not the same.  File: as.info, Node: Incbin, Next: Include, Prev: If, Up: Pseudo Ops -7.42 `.incbin "FILE"[,SKIP[,COUNT]]' +7.42 '.incbin "FILE"[,SKIP[,COUNT]]' ==================================== -The `incbin' directive includes FILE verbatim at the current location. -You can control the search paths used with the `-I' command-line option +The 'incbin' directive includes FILE verbatim at the current location. +You can control the search paths used with the '-I' command-line option (*note Command-Line Options: Invoking.). Quotation marks are required around FILE. - The SKIP argument skips a number of bytes from the start of the -FILE. The COUNT argument indicates the maximum number of bytes to -read. Note that the data is not aligned in any way, so it is the user's + The SKIP argument skips a number of bytes from the start of the FILE. +The COUNT argument indicates the maximum number of bytes to read. Note +that the data is not aligned in any way, so it is the user's responsibility to make sure that proper alignment is provided both -before and after the `incbin' directive. +before and after the 'incbin' directive.  File: as.info, Node: Include, Next: Int, Prev: Incbin, Up: Pseudo Ops -7.43 `.include "FILE"' +7.43 '.include "FILE"' ====================== This directive provides a way to include supporting files at specified -points in your source program. The code from FILE is assembled as if -it followed the point of the `.include'; when the end of the included -file is reached, assembly of the original file continues. You can -control the search paths used with the `-I' command-line option (*note +points in your source program. The code from FILE is assembled as if it +followed the point of the '.include'; when the end of the included file +is reached, assembly of the original file continues. You can control +the search paths used with the '-I' command-line option (*note Command-Line Options: Invoking.). Quotation marks are required around FILE.  File: as.info, Node: Int, Next: Internal, Prev: Include, Up: Pseudo Ops -7.44 `.int EXPRESSIONS' +7.44 '.int EXPRESSIONS' ======================= Expect zero or more EXPRESSIONS, of any section, separated by commas. @@ -4287,33 +4203,33 @@  File: as.info, Node: Internal, Next: Irp, Prev: Int, Up: Pseudo Ops -7.45 `.internal NAMES' +7.45 '.internal NAMES' ====================== This is one of the ELF visibility directives. The other two are -`.hidden' (*note `.hidden': Hidden.) and `.protected' (*note -`.protected': Protected.). +'.hidden' (*note '.hidden': Hidden.) and '.protected' (*note +'.protected': Protected.). This directive overrides the named symbols default visibility (which -is set by their binding: local, global or weak). The directive sets -the visibility to `internal' which means that the symbols are -considered to be `hidden' (i.e., not visible to other components), and -that some extra, processor specific processing must also be performed -upon the symbols as well. +is set by their binding: local, global or weak). The directive sets the +visibility to 'internal' which means that the symbols are considered to +be 'hidden' (i.e., not visible to other components), and that some +extra, processor specific processing must also be performed upon the +symbols as well.  File: as.info, Node: Irp, Next: Irpc, Prev: Internal, Up: Pseudo Ops -7.46 `.irp SYMBOL,VALUES'... +7.46 '.irp SYMBOL,VALUES'... ============================ Evaluate a sequence of statements assigning different values to SYMBOL. -The sequence of statements starts at the `.irp' directive, and is -terminated by an `.endr' directive. For each VALUE, SYMBOL is set to +The sequence of statements starts at the '.irp' directive, and is +terminated by an '.endr' directive. For each VALUE, SYMBOL is set to VALUE, and the sequence of statements is assembled. If no VALUE is -listed, the sequence of statements is assembled once, with SYMBOL set -to the null string. To refer to SYMBOL within the sequence of -statements, use \SYMBOL. +listed, the sequence of statements is assembled once, with SYMBOL set to +the null string. To refer to SYMBOL within the sequence of statements, +use \SYMBOL. For example, assembling @@ -4327,21 +4243,21 @@ move d2,sp@- move d3,sp@- - For some caveats with the spelling of SYMBOL, see also *Note Macro::. + For some caveats with the spelling of SYMBOL, see also *note Macro::.  File: as.info, Node: Irpc, Next: Lcomm, Prev: Irp, Up: Pseudo Ops -7.47 `.irpc SYMBOL,VALUES'... +7.47 '.irpc SYMBOL,VALUES'... ============================= Evaluate a sequence of statements assigning different values to SYMBOL. -The sequence of statements starts at the `.irpc' directive, and is -terminated by an `.endr' directive. For each character in VALUE, -SYMBOL is set to the character, and the sequence of statements is -assembled. If no VALUE is listed, the sequence of statements is -assembled once, with SYMBOL set to the null string. To refer to SYMBOL -within the sequence of statements, use \SYMBOL. +The sequence of statements starts at the '.irpc' directive, and is +terminated by an '.endr' directive. For each character in VALUE, SYMBOL +is set to the character, and the sequence of statements is assembled. +If no VALUE is listed, the sequence of statements is assembled once, +with SYMBOL set to the null string. To refer to SYMBOL within the +sequence of statements, use \SYMBOL. For example, assembling @@ -4361,64 +4277,64 @@  File: as.info, Node: Lcomm, Next: Lflags, Prev: Irpc, Up: Pseudo Ops -7.48 `.lcomm SYMBOL , LENGTH' +7.48 '.lcomm SYMBOL , LENGTH' ============================= -Reserve LENGTH (an absolute expression) bytes for a local common -denoted by SYMBOL. The section and value of SYMBOL are those of the -new local common. The addresses are allocated in the bss section, so -that at run-time the bytes start off zeroed. SYMBOL is not declared -global (*note `.global': Global.), so is normally not visible to `ld'. +Reserve LENGTH (an absolute expression) bytes for a local common denoted +by SYMBOL. The section and value of SYMBOL are those of the new local +common. The addresses are allocated in the bss section, so that at +run-time the bytes start off zeroed. SYMBOL is not declared global +(*note '.global': Global.), so is normally not visible to 'ld'. - Some targets permit a third argument to be used with `.lcomm'. This + Some targets permit a third argument to be used with '.lcomm'. This argument specifies the desired alignment of the symbol in the bss section. - The syntax for `.lcomm' differs slightly on the HPPA. The syntax is -`SYMBOL .lcomm, LENGTH'; SYMBOL is optional. + The syntax for '.lcomm' differs slightly on the HPPA. The syntax is +'SYMBOL .lcomm, LENGTH'; SYMBOL is optional.  File: as.info, Node: Lflags, Next: Line, Prev: Lcomm, Up: Pseudo Ops -7.49 `.lflags' +7.49 '.lflags' ============== -`as' accepts this directive, for compatibility with other assemblers, +'as' accepts this directive, for compatibility with other assemblers, but ignores it.  File: as.info, Node: Line, Next: Linkonce, Prev: Lflags, Up: Pseudo Ops -7.50 `.line LINE-NUMBER' +7.50 '.line LINE-NUMBER' ======================== Change the logical line number. LINE-NUMBER must be an absolute expression. The next line has that logical line number. Therefore any other statements on the current line (after a statement separator character) are reported as on logical line number LINE-NUMBER - 1. One -day `as' will no longer support this directive: it is recognized only +day 'as' will no longer support this directive: it is recognized only for compatibility with existing assembler programs. -Even though this is a directive associated with the `a.out' or `b.out' -object-code formats, `as' still recognizes it when producing COFF -output, and treats `.line' as though it were the COFF `.ln' _if_ it is -found outside a `.def'/`.endef' pair. + Even though this is a directive associated with the 'a.out' or +'b.out' object-code formats, 'as' still recognizes it when producing +COFF output, and treats '.line' as though it were the COFF '.ln' _if_ it +is found outside a '.def'/'.endef' pair. - Inside a `.def', `.line' is, instead, one of the directives used by + Inside a '.def', '.line' is, instead, one of the directives used by compilers to generate auxiliary symbol information for debugging.  File: as.info, Node: Linkonce, Next: List, Prev: Line, Up: Pseudo Ops -7.51 `.linkonce [TYPE]' +7.51 '.linkonce [TYPE]' ======================= Mark the current section so that the linker only includes a single copy of it. This may be used to include the same section in several different object files, but ensure that the linker will only include it -once in the final output file. The `.linkonce' pseudo-op must be used -for each instance of the section. Duplicate sections are detected -based on the section name, so it should be unique. +once in the final output file. The '.linkonce' pseudo-op must be used +for each instance of the section. Duplicate sections are detected based +on the section name, so it should be unique. This directive is only supported by a few object file formats; as of this writing, the only object file format which supports it is the @@ -4429,128 +4345,127 @@ .linkonce same_size Not all types may be supported on all object file formats. -`discard' +'discard' Silently discard duplicate sections. This is the default. -`one_only' +'one_only' Warn if there are duplicate sections, but still keep only one copy. -`same_size' +'same_size' Warn if any of the duplicates have different sizes. -`same_contents' +'same_contents' Warn if any of the duplicates do not have exactly the same contents.  File: as.info, Node: List, Next: Ln, Prev: Linkonce, Up: Pseudo Ops -7.52 `.list' +7.52 '.list' ============ -Control (in conjunction with the `.nolist' directive) whether or not +Control (in conjunction with the '.nolist' directive) whether or not assembly listings are generated. These two directives maintain an -internal counter (which is zero initially). `.list' increments the -counter, and `.nolist' decrements it. Assembly listings are generated +internal counter (which is zero initially). '.list' increments the +counter, and '.nolist' decrements it. Assembly listings are generated whenever the counter is greater than zero. By default, listings are disabled. When you enable them (with the -`-a' command line option; *note Command-Line Options: Invoking.), the +'-a' command line option; *note Command-Line Options: Invoking.), the initial value of the listing counter is one.  File: as.info, Node: Ln, Next: Loc, Prev: List, Up: Pseudo Ops -7.53 `.ln LINE-NUMBER' +7.53 '.ln LINE-NUMBER' ====================== -`.ln' is a synonym for `.line'. +'.ln' is a synonym for '.line'.  File: as.info, Node: Loc, Next: Loc_mark_labels, Prev: Ln, Up: Pseudo Ops -7.54 `.loc FILENO LINENO [COLUMN] [OPTIONS]' +7.54 '.loc FILENO LINENO [COLUMN] [OPTIONS]' ============================================ -When emitting DWARF2 line number information, the `.loc' directive will -add a row to the `.debug_line' line number matrix corresponding to the +When emitting DWARF2 line number information, the '.loc' directive will +add a row to the '.debug_line' line number matrix corresponding to the immediately following assembly instruction. The FILENO, LINENO, and -optional COLUMN arguments will be applied to the `.debug_line' state +optional COLUMN arguments will be applied to the '.debug_line' state machine before the row is added. The OPTIONS are a sequence of the following tokens in any order: -`basic_block' - This option will set the `basic_block' register in the - `.debug_line' state machine to `true'. - -`prologue_end' - This option will set the `prologue_end' register in the - `.debug_line' state machine to `true'. - -`epilogue_begin' - This option will set the `epilogue_begin' register in the - `.debug_line' state machine to `true'. - -`is_stmt VALUE' - This option will set the `is_stmt' register in the `.debug_line' - state machine to `value', which must be either 0 or 1. +'basic_block' + This option will set the 'basic_block' register in the + '.debug_line' state machine to 'true'. + +'prologue_end' + This option will set the 'prologue_end' register in the + '.debug_line' state machine to 'true'. + +'epilogue_begin' + This option will set the 'epilogue_begin' register in the + '.debug_line' state machine to 'true'. + +'is_stmt VALUE' + This option will set the 'is_stmt' register in the '.debug_line' + state machine to 'value', which must be either 0 or 1. -`isa VALUE' - This directive will set the `isa' register in the `.debug_line' +'isa VALUE' + This directive will set the 'isa' register in the '.debug_line' state machine to VALUE, which must be an unsigned integer. -`discriminator VALUE' - This directive will set the `discriminator' register in the - `.debug_line' state machine to VALUE, which must be an unsigned +'discriminator VALUE' + This directive will set the 'discriminator' register in the + '.debug_line' state machine to VALUE, which must be an unsigned integer. -  File: as.info, Node: Loc_mark_labels, Next: Local, Prev: Loc, Up: Pseudo Ops -7.55 `.loc_mark_labels ENABLE' +7.55 '.loc_mark_labels ENABLE' ============================== -When emitting DWARF2 line number information, the `.loc_mark_labels' -directive makes the assembler emit an entry to the `.debug_line' line -number matrix with the `basic_block' register in the state machine set +When emitting DWARF2 line number information, the '.loc_mark_labels' +directive makes the assembler emit an entry to the '.debug_line' line +number matrix with the 'basic_block' register in the state machine set whenever a code label is seen. The ENABLE argument should be either 1 or 0, to enable or disable this function respectively.  File: as.info, Node: Local, Next: Long, Prev: Loc_mark_labels, Up: Pseudo Ops -7.56 `.local NAMES' +7.56 '.local NAMES' =================== This directive, which is available for ELF targets, marks each symbol in -the comma-separated list of `names' as a local symbol so that it will +the comma-separated list of 'names' as a local symbol so that it will not be externally visible. If the symbols do not already exist, they will be created. - For targets where the `.lcomm' directive (*note Lcomm::) does not + For targets where the '.lcomm' directive (*note Lcomm::) does not accept an alignment argument, which is the case for most ELF targets, -the `.local' directive can be used in combination with `.comm' (*note +the '.local' directive can be used in combination with '.comm' (*note Comm::) to define aligned local common data.  File: as.info, Node: Long, Next: Macro, Prev: Local, Up: Pseudo Ops -7.57 `.long EXPRESSIONS' +7.57 '.long EXPRESSIONS' ======================== -`.long' is the same as `.int'. *Note `.int': Int. +'.long' is the same as '.int'. *Note '.int': Int.  File: as.info, Node: Macro, Next: MRI, Prev: Long, Up: Pseudo Ops -7.58 `.macro' +7.58 '.macro' ============= -The commands `.macro' and `.endm' allow you to define macros that +The commands '.macro' and '.endm' allow you to define macros that generate assembly output. For example, this definition specifies a -macro `sum' that puts a sequence of numbers into memory: +macro 'sum' that puts a sequence of numbers into memory: .macro sum from=0, to=5 .long \from @@ -4559,7 +4474,7 @@ .endif .endm -With that definition, `SUM 0,5' is equivalent to this assembly input: +With that definition, 'SUM 0,5' is equivalent to this assembly input: .long 0 .long 1 @@ -4568,56 +4483,55 @@ .long 4 .long 5 -`.macro MACNAME' -`.macro MACNAME MACARGS ...' +'.macro MACNAME' +'.macro MACNAME MACARGS ...' Begin the definition of a macro called MACNAME. If your macro definition requires arguments, specify their names after the macro name, separated by commas or spaces. You can qualify the macro argument to indicate whether all invocations must specify a - non-blank value (through `:`req''), or whether it takes all of the - remaining arguments (through `:`vararg''). You can supply a + non-blank value (through ':'req''), or whether it takes all of the + remaining arguments (through ':'vararg''). You can supply a default value for any macro argument by following the name with - `=DEFLT'. You cannot define two macros with the same MACNAME - unless it has been subject to the `.purgem' directive (*note + '=DEFLT'. You cannot define two macros with the same MACNAME + unless it has been subject to the '.purgem' directive (*note Purgem::) between the two definitions. For example, these are all - valid `.macro' statements: + valid '.macro' statements: - `.macro comm' - Begin the definition of a macro called `comm', which takes no + '.macro comm' + Begin the definition of a macro called 'comm', which takes no arguments. - `.macro plus1 p, p1' - `.macro plus1 p p1' + '.macro plus1 p, p1' + '.macro plus1 p p1' Either statement begins the definition of a macro called - `plus1', which takes two arguments; within the macro - definition, write `\p' or `\p1' to evaluate the arguments. + 'plus1', which takes two arguments; within the macro + definition, write '\p' or '\p1' to evaluate the arguments. - `.macro reserve_str p1=0 p2' - Begin the definition of a macro called `reserve_str', with two + '.macro reserve_str p1=0 p2' + Begin the definition of a macro called 'reserve_str', with two arguments. The first argument has a default value, but not the second. After the definition is complete, you can call - the macro either as `reserve_str A,B' (with `\p1' evaluating - to A and `\p2' evaluating to B), or as `reserve_str ,B' (with - `\p1' evaluating as the default, in this case `0', and `\p2' + the macro either as 'reserve_str A,B' (with '\p1' evaluating + to A and '\p2' evaluating to B), or as 'reserve_str ,B' (with + '\p1' evaluating as the default, in this case '0', and '\p2' evaluating to B). - `.macro m p1:req, p2=0, p3:vararg' - Begin the definition of a macro called `m', with at least + '.macro m p1:req, p2=0, p3:vararg' + Begin the definition of a macro called 'm', with at least three arguments. The first argument must always have a value specified, but not the second, which instead has a default - value. The third formal will get assigned all remaining + value. The third formal will get assigned all remaining arguments specified at invocation time. When you call a macro, you can specify the argument values - either by position, or by keyword. For example, `sum 9,17' - is equivalent to `sum to=17, from=9'. + either by position, or by keyword. For example, 'sum 9,17' is + equivalent to 'sum to=17, from=9'. - - Note that since each of the MACARGS can be an identifier exactly - as any other one permitted by the target architecture, there may be + Note that since each of the MACARGS can be an identifier exactly as + any other one permitted by the target architecture, there may be occasional problems if the target hand-crafts special meanings to certain characters when they occur in a special position. For - example, if the colon (`:') is generally permitted to be part of a + example, if the colon (':') is generally permitted to be part of a symbol name, but the architecture specific code special-cases it when occurring as the final character of a symbol (to denote a label), then the macro parameter replacement code will have no way @@ -4630,12 +4544,12 @@ \l: .endm - might not work as expected. Invoking `label foo' might not create - a label called `foo' but instead just insert the text `\l:' into + might not work as expected. Invoking 'label foo' might not create + a label called 'foo' but instead just insert the text '\l:' into the assembler source, probably generating an error about an unrecognised identifier. - Similarly problems might occur with the period character (`.') + Similarly problems might occur with the period character ('.') which is often allowed inside opcode names (and hence identifier names). So for example constructing a macro to build an opcode from a base name and a length specifier like this: @@ -4644,13 +4558,13 @@ \base.\length .endm - and invoking it as `opcode store l' will not create a `store.l' + and invoking it as 'opcode store l' will not create a 'store.l' instruction but instead generate some kind of error as the - assembler tries to interpret the text `\base.\length'. + assembler tries to interpret the text '\base.\length'. There are several possible ways around this problem: - `Insert white space' + 'Insert white space' If it is possible to use white space characters then this is the simplest solution. eg: @@ -4658,17 +4572,17 @@ \l : .endm - `Use `\()'' - The string `\()' can be used to separate the end of a macro + 'Use '\()'' + The string '\()' can be used to separate the end of a macro argument from the following text. eg: .macro opcode base length \base\().\length .endm - `Use the alternate macro syntax mode' + 'Use the alternate macro syntax mode' In the alternative macro syntax mode the ampersand character - (`&') can be used as a separator. eg: + ('&') can be used as a separator. eg: .altmacro .macro label l @@ -4676,40 +4590,40 @@ .endm Note: this problem of correctly identifying string parameters to - pseudo ops also applies to the identifiers used in `.irp' (*note - Irp::) and `.irpc' (*note Irpc::) as well. + pseudo ops also applies to the identifiers used in '.irp' (*note + Irp::) and '.irpc' (*note Irpc::) as well. -`.endm' +'.endm' Mark the end of a macro definition. -`.exitm' +'.exitm' Exit early from the current macro definition. -`\@' - `as' maintains a counter of how many macros it has executed in - this pseudo-variable; you can copy that number to your output with - `\@', but _only within a macro definition_. - -`LOCAL NAME [ , ... ]' - _Warning: `LOCAL' is only available if you select "alternate macro - syntax" with `--alternate' or `.altmacro'._ *Note `.altmacro': +'\@' + 'as' maintains a counter of how many macros it has executed in this + pseudo-variable; you can copy that number to your output with '\@', + but _only within a macro definition_. + +'LOCAL NAME [ , ... ]' + _Warning: 'LOCAL' is only available if you select "alternate macro + syntax" with '--alternate' or '.altmacro'._ *Note '.altmacro': Altmacro.  File: as.info, Node: MRI, Next: Noaltmacro, Prev: Macro, Up: Pseudo Ops -7.59 `.mri VAL' +7.59 '.mri VAL' =============== -If VAL is non-zero, this tells `as' to enter MRI mode. If VAL is zero, -this tells `as' to exit MRI mode. This change affects code assembled -until the next `.mri' directive, or until the end of the file. *Note +If VAL is non-zero, this tells 'as' to enter MRI mode. If VAL is zero, +this tells 'as' to exit MRI mode. This change affects code assembled +until the next '.mri' directive, or until the end of the file. *Note MRI mode: M.  File: as.info, Node: Noaltmacro, Next: Nolist, Prev: MRI, Up: Pseudo Ops -7.60 `.noaltmacro' +7.60 '.noaltmacro' ================== Disable alternate macro mode. *Note Altmacro::. @@ -4717,19 +4631,19 @@  File: as.info, Node: Nolist, Next: Octa, Prev: Noaltmacro, Up: Pseudo Ops -7.61 `.nolist' +7.61 '.nolist' ============== -Control (in conjunction with the `.list' directive) whether or not +Control (in conjunction with the '.list' directive) whether or not assembly listings are generated. These two directives maintain an -internal counter (which is zero initially). `.list' increments the -counter, and `.nolist' decrements it. Assembly listings are generated +internal counter (which is zero initially). '.list' increments the +counter, and '.nolist' decrements it. Assembly listings are generated whenever the counter is greater than zero.  File: as.info, Node: Octa, Next: Offset, Prev: Nolist, Up: Pseudo Ops -7.62 `.octa BIGNUMS' +7.62 '.octa BIGNUMS' ==================== This directive expects zero or more bignums, separated by commas. For @@ -4741,32 +4655,31 @@  File: as.info, Node: Offset, Next: Org, Prev: Octa, Up: Pseudo Ops -7.63 `.offset LOC' +7.63 '.offset LOC' ================== -Set the location counter to LOC in the absolute section. LOC must be -an absolute expression. This directive may be useful for defining -symbols with absolute values. Do not confuse it with the `.org' -directive. +Set the location counter to LOC in the absolute section. LOC must be an +absolute expression. This directive may be useful for defining symbols +with absolute values. Do not confuse it with the '.org' directive.  File: as.info, Node: Org, Next: P2align, Prev: Offset, Up: Pseudo Ops -7.64 `.org NEW-LC , FILL' +7.64 '.org NEW-LC , FILL' ========================= Advance the location counter of the current section to NEW-LC. NEW-LC is either an absolute expression or an expression with the same section -as the current subsection. That is, you can't use `.org' to cross -sections: if NEW-LC has the wrong section, the `.org' directive is +as the current subsection. That is, you can't use '.org' to cross +sections: if NEW-LC has the wrong section, the '.org' directive is ignored. To be compatible with former assemblers, if the section of -NEW-LC is absolute, `as' issues a warning, then pretends the section of +NEW-LC is absolute, 'as' issues a warning, then pretends the section of NEW-LC is the same as the current subsection. - `.org' may only increase the location counter, or leave it -unchanged; you cannot use `.org' to move the location counter backwards. + '.org' may only increase the location counter, or leave it unchanged; +you cannot use '.org' to move the location counter backwards. - Because `as' tries to assemble programs in one pass, NEW-LC may not + Because 'as' tries to assemble programs in one pass, NEW-LC may not be undefined. If you really detest this restriction we eagerly await a chance to share your improved assembler. @@ -4781,15 +4694,15 @@  File: as.info, Node: P2align, Next: PopSection, Prev: Org, Up: Pseudo Ops -7.65 `.p2align[wl] ABS-EXPR, ABS-EXPR, ABS-EXPR' +7.65 '.p2align[wl] ABS-EXPR, ABS-EXPR, ABS-EXPR' ================================================ Pad the location counter (in the current subsection) to a particular storage boundary. The first expression (which must be absolute) is the number of low-order zero bits the location counter must have after -advancement. For example `.p2align 3' advances the location counter -until it a multiple of 8. If the location counter is already a -multiple of 8, no change is needed. +advancement. For example '.p2align 3' advances the location counter +until it a multiple of 8. If the location counter is already a multiple +of 8, no change is needed. The second expression (also absolute) gives the fill value to be stored in the padding bytes. It (and the comma) may be omitted. If it @@ -4799,51 +4712,51 @@ The third expression is also absolute, and is also optional. If it is present, it is the maximum number of bytes that should be skipped by -this alignment directive. If doing the alignment would require -skipping more bytes than the specified maximum, then the alignment is -not done at all. You can omit the fill value (the second argument) -entirely by simply using two commas after the required alignment; this -can be useful if you want the alignment to be filled with no-op -instructions when appropriate. - - The `.p2alignw' and `.p2alignl' directives are variants of the -`.p2align' directive. The `.p2alignw' directive treats the fill -pattern as a two byte word value. The `.p2alignl' directives treats the -fill pattern as a four byte longword value. For example, `.p2alignw +this alignment directive. If doing the alignment would require skipping +more bytes than the specified maximum, then the alignment is not done at +all. You can omit the fill value (the second argument) entirely by +simply using two commas after the required alignment; this can be useful +if you want the alignment to be filled with no-op instructions when +appropriate. + + The '.p2alignw' and '.p2alignl' directives are variants of the +'.p2align' directive. The '.p2alignw' directive treats the fill pattern +as a two byte word value. The '.p2alignl' directives treats the fill +pattern as a four byte longword value. For example, '.p2alignw 2,0x368d' will align to a multiple of 4. If it skips two bytes, they will be filled in with the value 0x368d (the exact placement of the -bytes depends upon the endianness of the processor). If it skips 1 or -3 bytes, the fill value is undefined. +bytes depends upon the endianness of the processor). If it skips 1 or 3 +bytes, the fill value is undefined.  File: as.info, Node: PopSection, Next: Previous, Prev: P2align, Up: Pseudo Ops -7.66 `.popsection' +7.66 '.popsection' ================== This is one of the ELF section stack manipulation directives. The -others are `.section' (*note Section::), `.subsection' (*note -SubSection::), `.pushsection' (*note PushSection::), and `.previous' +others are '.section' (*note Section::), '.subsection' (*note +SubSection::), '.pushsection' (*note PushSection::), and '.previous' (*note Previous::). - This directive replaces the current section (and subsection) with -the top section (and subsection) on the section stack. This section is + This directive replaces the current section (and subsection) with the +top section (and subsection) on the section stack. This section is popped off the stack.  File: as.info, Node: Previous, Next: Print, Prev: PopSection, Up: Pseudo Ops -7.67 `.previous' +7.67 '.previous' ================ This is one of the ELF section stack manipulation directives. The -others are `.section' (*note Section::), `.subsection' (*note -SubSection::), `.pushsection' (*note PushSection::), and `.popsection' +others are '.section' (*note Section::), '.subsection' (*note +SubSection::), '.pushsection' (*note PushSection::), and '.popsection' (*note PopSection::). This directive swaps the current section (and subsection) with most recently referenced section/subsection pair prior to this one. Multiple -`.previous' directives in a row will flip between two sections (and +'.previous' directives in a row will flip between two sections (and their subsections). For example: .section A @@ -4855,7 +4768,7 @@ .word 0x9abc Will place 0x1234 and 0x9abc into subsection 1 and 0x5678 into -subsection 2 of section A. Whilst: +subsection 2 of section A. Whilst: .section A .subsection 1 @@ -4872,8 +4785,8 @@ # Now in section B subsection 0 .word 0xdef0 - Will place 0x1234 into section A, 0x5678 and 0xdef0 into subsection -0 of section B and 0x9abc into subsection 1 of section B. + Will place 0x1234 into section A, 0x5678 and 0xdef0 into subsection 0 +of section B and 0x9abc into subsection 1 of section B. In terms of the section stack, this directive swaps the current section with the top section on the section stack. @@ -4881,51 +4794,51 @@  File: as.info, Node: Print, Next: Protected, Prev: Previous, Up: Pseudo Ops -7.68 `.print STRING' +7.68 '.print STRING' ==================== -`as' will print STRING on the standard output during assembly. You -must put STRING in double quotes. +'as' will print STRING on the standard output during assembly. You must +put STRING in double quotes.  File: as.info, Node: Protected, Next: Psize, Prev: Print, Up: Pseudo Ops -7.69 `.protected NAMES' +7.69 '.protected NAMES' ======================= This is one of the ELF visibility directives. The other two are -`.hidden' (*note Hidden::) and `.internal' (*note Internal::). +'.hidden' (*note Hidden::) and '.internal' (*note Internal::). This directive overrides the named symbols default visibility (which -is set by their binding: local, global or weak). The directive sets -the visibility to `protected' which means that any references to the -symbols from within the components that defines them must be resolved -to the definition in that component, even if a definition in another -component would normally preempt this. +is set by their binding: local, global or weak). The directive sets the +visibility to 'protected' which means that any references to the symbols +from within the components that defines them must be resolved to the +definition in that component, even if a definition in another component +would normally preempt this.  File: as.info, Node: Psize, Next: Purgem, Prev: Protected, Up: Pseudo Ops -7.70 `.psize LINES , COLUMNS' +7.70 '.psize LINES , COLUMNS' ============================= Use this directive to declare the number of lines--and, optionally, the number of columns--to use for each page, when generating listings. - If you do not use `.psize', listings use a default line-count of 60. + If you do not use '.psize', listings use a default line-count of 60. You may omit the comma and COLUMNS specification; the default width is 200 columns. - `as' generates formfeeds whenever the specified number of lines is -exceeded (or whenever you explicitly request one, using `.eject'). + 'as' generates formfeeds whenever the specified number of lines is +exceeded (or whenever you explicitly request one, using '.eject'). - If you specify LINES as `0', no formfeeds are generated save those -explicitly specified with `.eject'. + If you specify LINES as '0', no formfeeds are generated save those +explicitly specified with '.eject'.  File: as.info, Node: Purgem, Next: PushSection, Prev: Psize, Up: Pseudo Ops -7.71 `.purgem NAME' +7.71 '.purgem NAME' =================== Undefine the macro NAME, so that later uses of the string will not be @@ -4934,30 +4847,30 @@  File: as.info, Node: PushSection, Next: Quad, Prev: Purgem, Up: Pseudo Ops -7.72 `.pushsection NAME [, SUBSECTION] [, "FLAGS"[, @TYPE[,ARGUMENTS]]]' +7.72 '.pushsection NAME [, SUBSECTION] [, "FLAGS"[, @TYPE[,ARGUMENTS]]]' ======================================================================== This is one of the ELF section stack manipulation directives. The -others are `.section' (*note Section::), `.subsection' (*note -SubSection::), `.popsection' (*note PopSection::), and `.previous' +others are '.section' (*note Section::), '.subsection' (*note +SubSection::), '.popsection' (*note PopSection::), and '.previous' (*note Previous::). This directive pushes the current section (and subsection) onto the top of the section stack, and then replaces the current section and -subsection with `name' and `subsection'. The optional `flags', `type' -and `arguments' are treated the same as in the `.section' (*note +subsection with 'name' and 'subsection'. The optional 'flags', 'type' +and 'arguments' are treated the same as in the '.section' (*note Section::) directive.  File: as.info, Node: Quad, Next: Reloc, Prev: PushSection, Up: Pseudo Ops -7.73 `.quad BIGNUMS' +7.73 '.quad BIGNUMS' ==================== -`.quad' expects zero or more bignums, separated by commas. For each -bignum, it emits an 8-byte integer. If the bignum won't fit in 8 -bytes, it prints a warning message; and just takes the lowest order 8 -bytes of the bignum. +'.quad' expects zero or more bignums, separated by commas. For each +bignum, it emits an 8-byte integer. If the bignum won't fit in 8 bytes, +it prints a warning message; and just takes the lowest order 8 bytes of +the bignum. The term "quad" comes from contexts in which a "word" is two bytes; hence _quad_-word for 8 bytes. @@ -4965,7 +4878,7 @@  File: as.info, Node: Reloc, Next: Rept, Prev: Quad, Up: Pseudo Ops -7.74 `.reloc OFFSET, RELOC_NAME[, EXPRESSION]' +7.74 '.reloc OFFSET, RELOC_NAME[, EXPRESSION]' ============================================== Generate a relocation at OFFSET of type RELOC_NAME with value @@ -4981,11 +4894,11 @@  File: as.info, Node: Rept, Next: Sbttl, Prev: Reloc, Up: Pseudo Ops -7.75 `.rept COUNT' +7.75 '.rept COUNT' ================== -Repeat the sequence of lines between the `.rept' directive and the next -`.endr' directive COUNT times. +Repeat the sequence of lines between the '.rept' directive and the next +'.endr' directive COUNT times. For example, assembling @@ -5002,7 +4915,7 @@  File: as.info, Node: Sbttl, Next: Scl, Prev: Rept, Up: Pseudo Ops -7.76 `.sbttl "SUBHEADING"' +7.76 '.sbttl "SUBHEADING"' ========================== Use SUBHEADING as the title (third line, immediately after the title @@ -5014,31 +4927,31 @@  File: as.info, Node: Scl, Next: Section, Prev: Sbttl, Up: Pseudo Ops -7.77 `.scl CLASS' +7.77 '.scl CLASS' ================= Set the storage-class value for a symbol. This directive may only be -used inside a `.def'/`.endef' pair. Storage class may flag whether a +used inside a '.def'/'.endef' pair. Storage class may flag whether a symbol is static or external, or it may record further symbolic debugging information.  File: as.info, Node: Section, Next: Set, Prev: Scl, Up: Pseudo Ops -7.78 `.section NAME' +7.78 '.section NAME' ==================== -Use the `.section' directive to assemble the following code into a +Use the '.section' directive to assemble the following code into a section named NAME. This directive is only supported for targets that actually support -arbitrarily named sections; on `a.out' targets, for example, it is not -accepted, even with a standard `a.out' section name. +arbitrarily named sections; on 'a.out' targets, for example, it is not +accepted, even with a standard 'a.out' section name. COFF Version ------------ - For COFF targets, the `.section' directive is used in one of the +For COFF targets, the '.section' directive is used in one of the following ways: .section NAME[, "FLAGS"] @@ -5048,64 +4961,54 @@ the section. Each flag is a single character. The following flags are recognized: -`b' +'b' bss section (uninitialized data) - -`n' +'n' section is not loaded - -`w' +'w' writable section - -`d' +'d' data section - -`e' +'e' exclude section from linking - -`r' +'r' read-only section - -`x' +'x' executable section - -`s' +'s' shared section (meaningful for PE targets) - -`a' +'a' ignored. (For compatibility with the ELF version) - -`y' +'y' section is not readable (meaningful for PE targets) - -`0-9' +'0-9' single-digit power-of-two section alignment (GNU extension) If no flags are specified, the default flags depend upon the section name. If the section name is not recognized, the default will be for -the section to be loaded and writable. Note the `n' and `w' flags +the section to be loaded and writable. Note the 'n' and 'w' flags remove attributes from the section, rather than adding them, so if they are used on their own it will be as if no flags had been specified at all. - If the optional argument to the `.section' directive is not quoted, + If the optional argument to the '.section' directive is not quoted, it is taken as a subsection number (*note Sub-Sections::). ELF Version ----------- - This is one of the ELF section stack manipulation directives. The -others are `.subsection' (*note SubSection::), `.pushsection' (*note -PushSection::), `.popsection' (*note PopSection::), and `.previous' +This is one of the ELF section stack manipulation directives. The +others are '.subsection' (*note SubSection::), '.pushsection' (*note +PushSection::), '.popsection' (*note PopSection::), and '.previous' (*note Previous::). - For ELF targets, the `.section' directive is used like this: + For ELF targets, the '.section' directive is used like this: .section NAME [, "FLAGS"[, @TYPE[,FLAG_SPECIFIC_ARGUMENTS]]] - If the `--sectname-subst' command-line option is provided, the NAME -argument may contain a substitution sequence. Only `%S' is supported at -the moment, and substitutes the current section name. For example: + If the '--sectname-subst' command-line option is provided, the NAME +argument may contain a substitution sequence. Only '%S' is supported at +the moment, and substitutes the current section name. For example: .macro exception_code .section %S.exception @@ -5123,115 +5026,98 @@ exception_code [...] - The two `exception_code' invocations above would create the -`.text.exception' and `.init.exception' sections respectively. This is -useful e.g. to discriminate between anciliary sections that are tied to + The two 'exception_code' invocations above would create the +'.text.exception' and '.init.exception' sections respectively. This is +useful e.g. to discriminate between anciliary sections that are tied to setup code to be discarded after use from anciliary sections that need -to stay resident without having to define multiple `exception_code' +to stay resident without having to define multiple 'exception_code' macros just for that purpose. The optional FLAGS argument is a quoted string which may contain any combination of the following characters: -`a' +'a' section is allocatable - -`e' +'e' section is excluded from executable and shared library. - -`w' +'w' section is writable - -`x' +'x' section is executable - -`M' +'M' section is mergeable - -`S' +'S' section contains zero terminated strings - -`G' +'G' section is a member of a section group - -`T' +'T' section is used for thread-local-storage - -`?' +'?' section is a member of the previously-current section's group, if any - -``'' +'' a numeric value indicating the bits to be set in the ELF section header's flags field. Note - if one or more of the alphabetic characters described above is also included in the flags field, their bit values will be ORed into the resulting value. - -``'' +'' some targets extend this list with their own flag characters Note - once a section's flags have been set they cannot be changed. There are a few exceptions to this rule however. Processor and application specific flags can be added to an already defined section. -The `.interp', `.strtab' and `.symtab' sections can have the allocate -flag (`a') set after they are initially defined, and the -`.note-GNU-stack' section may have the executable (`x') flag added. +The '.interp', '.strtab' and '.symtab' sections can have the allocate +flag ('a') set after they are initially defined, and the +'.note-GNU-stack' section may have the executable ('x') flag added. The optional TYPE argument may contain one of the following constants: -`@progbits' +'@progbits' section contains data - -`@nobits' +'@nobits' section does not contain data (i.e., section only occupies space) - -`@note' +'@note' section contains data which is used by things other than the program - -`@init_array' +'@init_array' section contains an array of pointers to init functions - -`@fini_array' +'@fini_array' section contains an array of pointers to finish functions - -`@preinit_array' +'@preinit_array' section contains an array of pointers to pre-init functions - -`@`'' +'@' a numeric value to be set as the ELF section header's type field. - -`@`'' +'@' some targets extend this list with their own types Many targets only support the first three section types. The type may be enclosed in double quotes if necessary. - Note on targets where the `@' character is the start of a comment (eg + Note on targets where the '@' character is the start of a comment (eg ARM) then another character is used instead. For example the ARM port -uses the `%' character. +uses the '%' character. - Note - some sections, eg `.text' and `.data' are considered to be + Note - some sections, eg '.text' and '.data' are considered to be special and have fixed types. Any attempt to declare them with a different type will generate an error from the assembler. - If FLAGS contains the `M' symbol then the TYPE argument must be + If FLAGS contains the 'M' symbol then the TYPE argument must be specified as well as an extra argument--ENTSIZE--like this: .section NAME , "FLAGS"M, @TYPE, ENTSIZE - Sections with the `M' flag but not `S' flag must contain fixed size -constants, each ENTSIZE octets long. Sections with both `M' and `S' + Sections with the 'M' flag but not 'S' flag must contain fixed size +constants, each ENTSIZE octets long. Sections with both 'M' and 'S' must contain zero terminated strings where each character is ENTSIZE -bytes long. The linker may remove duplicates within sections with the -same name, same entity size and same flags. ENTSIZE must be an -absolute expression. For sections with both `M' and `S', a string -which is a suffix of a larger string is considered a duplicate. Thus -`"def"' will be merged with `"abcdef"'; A reference to the first -`"def"' will be changed to a reference to `"abcdef"+3'. +bytes long. The linker may remove duplicates within sections with the +same name, same entity size and same flags. ENTSIZE must be an absolute +expression. For sections with both 'M' and 'S', a string which is a +suffix of a larger string is considered a duplicate. Thus '"def"' will +be merged with '"abcdef"'; A reference to the first '"def"' will be +changed to a reference to '"abcdef"+3'. - If FLAGS contains the `G' symbol then the TYPE argument must be + If FLAGS contains the 'G' symbol then the TYPE argument must be present along with an additional field like this: .section NAME , "FLAGS"G, @TYPE, GROUPNAME[, LINKAGE] @@ -5240,10 +5126,9 @@ this particular section belongs. The optional linkage field can contain: -`comdat' +'comdat' indicates that only one copy of this section should be retained - -`.gnu.linkonce' +'.gnu.linkonce' an alias for comdat Note: if both the M and G flags are present then the fields for the @@ -5251,19 +5136,19 @@ .section NAME , "FLAGS"MG, @TYPE, ENTSIZE, GROUPNAME[, LINKAGE] - If FLAGS contains the `?' symbol then it may not also contain the -`G' symbol and the GROUPNAME or LINKAGE fields should not be present. -Instead, `?' says to consider the section that's current before this -directive. If that section used `G', then the new section will use `G' + If FLAGS contains the '?' symbol then it may not also contain the 'G' +symbol and the GROUPNAME or LINKAGE fields should not be present. +Instead, '?' says to consider the section that's current before this +directive. If that section used 'G', then the new section will use 'G' with those same GROUPNAME and LINKAGE fields implicitly. If not, then -the `?' symbol has no effect. +the '?' symbol has no effect. If no flags are specified, the default flags depend upon the section name. If the section name is not recognized, the default will be for -the section to have none of the above flags: it will not be allocated -in memory, nor writable, nor executable. The section will contain data. +the section to have none of the above flags: it will not be allocated in +memory, nor writable, nor executable. The section will contain data. - For ELF targets, the assembler supports another type of `.section' + For ELF targets, the assembler supports another type of '.section' directive for compatibility with the Solaris assembler: .section "NAME"[, FLAGS...] @@ -5271,78 +5156,74 @@ Note that the section name is quoted. There may be a sequence of comma separated flags: -`#alloc' +'#alloc' section is allocatable - -`#write' +'#write' section is writable - -`#execinstr' +'#execinstr' section is executable - -`#exclude' +'#exclude' section is excluded from executable and shared library. - -`#tls' +'#tls' section is used for thread local storage This directive replaces the current section and subsection. See the -contents of the gas testsuite directory `gas/testsuite/gas/elf' for -some examples of how this directive and the other section stack -directives work. +contents of the gas testsuite directory 'gas/testsuite/gas/elf' for some +examples of how this directive and the other section stack directives +work.  File: as.info, Node: Set, Next: Short, Prev: Section, Up: Pseudo Ops -7.79 `.set SYMBOL, EXPRESSION' +7.79 '.set SYMBOL, EXPRESSION' ============================== Set the value of SYMBOL to EXPRESSION. This changes SYMBOL's value and type to conform to EXPRESSION. If SYMBOL was flagged as external, it remains flagged (*note Symbol Attributes::). - You may `.set' a symbol many times in the same assembly provided -that the values given to the symbol are constants. Values that are -based on expressions involving other symbols are allowed, but some -targets may restrict this to only being done once per assembly. This -is because those targets do not set the addresses of symbols at -assembly time, but rather delay the assignment until a final link is -performed. This allows the linker a chance to change the code in the -files, changing the location of, and the relative distance between, -various different symbols. + You may '.set' a symbol many times in the same assembly provided that +the values given to the symbol are constants. Values that are based on +expressions involving other symbols are allowed, but some targets may +restrict this to only being done once per assembly. This is because +those targets do not set the addresses of symbols at assembly time, but +rather delay the assignment until a final link is performed. This +allows the linker a chance to change the code in the files, changing the +location of, and the relative distance between, various different +symbols. - If you `.set' a global symbol, the value stored in the object file -is the last value stored into it. + If you '.set' a global symbol, the value stored in the object file is +the last value stored into it. - On Z80 `set' is a real instruction, use `SYMBOL defl EXPRESSION' + On Z80 'set' is a real instruction, use 'SYMBOL defl EXPRESSION' instead.  File: as.info, Node: Short, Next: Single, Prev: Set, Up: Pseudo Ops -7.80 `.short EXPRESSIONS' +7.80 '.short EXPRESSIONS' ========================= -`.short' is normally the same as `.word'. *Note `.word': Word. +'.short' is normally the same as '.word'. *Note '.word': Word. - In some configurations, however, `.short' and `.word' generate + In some configurations, however, '.short' and '.word' generate numbers of different lengths. *Note Machine Dependencies::.  File: as.info, Node: Single, Next: Size, Prev: Short, Up: Pseudo Ops -7.81 `.single FLONUMS' +7.81 '.single FLONUMS' ====================== This directive assembles zero or more flonums, separated by commas. It -has the same effect as `.float'. The exact kind of floating point -numbers emitted depends on how `as' is configured. *Note Machine +has the same effect as '.float'. The exact kind of floating point +numbers emitted depends on how 'as' is configured. *Note Machine Dependencies::.  File: as.info, Node: Size, Next: Skip, Prev: Single, Up: Pseudo Ops -7.82 `.size' +7.82 '.size' ============ This directive is used to set the size associated with a symbol. @@ -5350,80 +5231,80 @@ COFF Version ------------ - For COFF targets, the `.size' directive is only permitted inside -`.def'/`.endef' pairs. It is used like this: +For COFF targets, the '.size' directive is only permitted inside +'.def'/'.endef' pairs. It is used like this: .size EXPRESSION ELF Version ----------- - For ELF targets, the `.size' directive is used like this: +For ELF targets, the '.size' directive is used like this: .size NAME , EXPRESSION - This directive sets the size associated with a symbol NAME. The -size in bytes is computed from EXPRESSION which can make use of label + This directive sets the size associated with a symbol NAME. The size +in bytes is computed from EXPRESSION which can make use of label arithmetic. This directive is typically used to set the size of function symbols.  File: as.info, Node: Skip, Next: Sleb128, Prev: Size, Up: Pseudo Ops -7.83 `.skip SIZE , FILL' +7.83 '.skip SIZE , FILL' ======================== -This directive emits SIZE bytes, each of value FILL. Both SIZE and -FILL are absolute expressions. If the comma and FILL are omitted, FILL -is assumed to be zero. This is the same as `.space'. +This directive emits SIZE bytes, each of value FILL. Both SIZE and FILL +are absolute expressions. If the comma and FILL are omitted, FILL is +assumed to be zero. This is the same as '.space'.  File: as.info, Node: Sleb128, Next: Space, Prev: Skip, Up: Pseudo Ops -7.84 `.sleb128 EXPRESSIONS' +7.84 '.sleb128 EXPRESSIONS' =========================== SLEB128 stands for "signed little endian base 128." This is a compact, variable length representation of numbers used by the DWARF symbolic -debugging format. *Note `.uleb128': Uleb128. +debugging format. *Note '.uleb128': Uleb128.  File: as.info, Node: Space, Next: Stab, Prev: Sleb128, Up: Pseudo Ops -7.85 `.space SIZE , FILL' +7.85 '.space SIZE , FILL' ========================= -This directive emits SIZE bytes, each of value FILL. Both SIZE and -FILL are absolute expressions. If the comma and FILL are omitted, FILL -is assumed to be zero. This is the same as `.skip'. +This directive emits SIZE bytes, each of value FILL. Both SIZE and FILL +are absolute expressions. If the comma and FILL are omitted, FILL is +assumed to be zero. This is the same as '.skip'. - _Warning:_ `.space' has a completely different meaning for HPPA - targets; use `.block' as a substitute. See `HP9000 Series 800 + _Warning:_ '.space' has a completely different meaning for HPPA + targets; use '.block' as a substitute. See 'HP9000 Series 800 Assembly Language Reference Manual' (HP 92432-90001) for the - meaning of the `.space' directive. *Note HPPA Assembler + meaning of the '.space' directive. *Note HPPA Assembler Directives: HPPA Directives, for a summary.  File: as.info, Node: Stab, Next: String, Prev: Space, Up: Pseudo Ops -7.86 `.stabd, .stabn, .stabs' +7.86 '.stabd, .stabn, .stabs' ============================= -There are three directives that begin `.stab'. All emit symbols (*note +There are three directives that begin '.stab'. All emit symbols (*note Symbols::), for use by symbolic debuggers. The symbols are not entered -in the `as' hash table: they cannot be referenced elsewhere in the +in the 'as' hash table: they cannot be referenced elsewhere in the source file. Up to five fields are required: STRING This is the symbol's name. It may contain any character except - `\000', so is more general than ordinary symbol names. Some + '\000', so is more general than ordinary symbol names. Some debuggers used to code arbitrarily complex structures into symbol names using this field. TYPE - An absolute expression. The symbol's type is set to the low 8 - bits of this expression. Any bit pattern is permitted, but `ld' - and debuggers choke on silly bit patterns. + An absolute expression. The symbol's type is set to the low 8 bits + of this expression. Any bit pattern is permitted, but 'ld' and + debuggers choke on silly bit patterns. OTHER An absolute expression. The symbol's "other" attribute is set to @@ -5436,43 +5317,44 @@ VALUE An absolute expression which becomes the symbol's value. - If a warning is detected while reading a `.stabd', `.stabn', or -`.stabs' statement, the symbol has probably already been created; you + If a warning is detected while reading a '.stabd', '.stabn', or +'.stabs' statement, the symbol has probably already been created; you get a half-formed symbol in your object file. This is compatible with earlier assemblers! -`.stabd TYPE , OTHER , DESC' - The "name" of the symbol generated is not even an empty string. - It is a null pointer, for compatibility. Older assemblers used a - null pointer so they didn't waste space in object files with empty +'.stabd TYPE , OTHER , DESC' + + The "name" of the symbol generated is not even an empty string. It + is a null pointer, for compatibility. Older assemblers used a null + pointer so they didn't waste space in object files with empty strings. The symbol's value is set to the location counter, relocatably. When your program is linked, the value of this symbol is the - address of the location counter when the `.stabd' was assembled. + address of the location counter when the '.stabd' was assembled. -`.stabn TYPE , OTHER , DESC , VALUE' - The name of the symbol is set to the empty string `""'. +'.stabn TYPE , OTHER , DESC , VALUE' + The name of the symbol is set to the empty string '""'. -`.stabs STRING , TYPE , OTHER , DESC , VALUE' +'.stabs STRING , TYPE , OTHER , DESC , VALUE' All five fields are specified.  File: as.info, Node: String, Next: Struct, Prev: Stab, Up: Pseudo Ops -7.87 `.string' "STR", `.string8' "STR", `.string16' +7.87 '.string' "STR", '.string8' "STR", '.string16' =================================================== -"STR", `.string32' "STR", `.string64' "STR" +"STR", '.string32' "STR", '.string64' "STR" Copy the characters in STR to the object file. You may specify more than one string to copy, separated by commas. Unless otherwise specified for a particular machine, the assembler marks the end of each -string with a 0 byte. You can use any of the escape sequences -described in *Note Strings: Strings. +string with a 0 byte. You can use any of the escape sequences described +in *note Strings: Strings. - The variants `string16', `string32' and `string64' differ from the -`string' pseudo opcode in that each 8-bit character from STR is copied + The variants 'string16', 'string32' and 'string64' differ from the +'string' pseudo opcode in that each 8-bit character from STR is copied and expanded to 16, 32 or 64 bits respectively. The expanded characters are stored in target endianness byte order. @@ -5485,117 +5367,116 @@  File: as.info, Node: Struct, Next: SubSection, Prev: String, Up: Pseudo Ops -7.88 `.struct EXPRESSION' +7.88 '.struct EXPRESSION' ========================= Switch to the absolute section, and set the section offset to -EXPRESSION, which must be an absolute expression. You might use this -as follows: +EXPRESSION, which must be an absolute expression. You might use this as +follows: .struct 0 field1: .struct field1 + 4 field2: .struct field2 + 4 field3: - This would define the symbol `field1' to have the value 0, the symbol -`field2' to have the value 4, and the symbol `field3' to have the value + This would define the symbol 'field1' to have the value 0, the symbol +'field2' to have the value 4, and the symbol 'field3' to have the value 8. Assembly would be left in the absolute section, and you would need -to use a `.section' directive of some sort to change to some other +to use a '.section' directive of some sort to change to some other section before further assembly.  File: as.info, Node: SubSection, Next: Symver, Prev: Struct, Up: Pseudo Ops -7.89 `.subsection NAME' +7.89 '.subsection NAME' ======================= This is one of the ELF section stack manipulation directives. The -others are `.section' (*note Section::), `.pushsection' (*note -PushSection::), `.popsection' (*note PopSection::), and `.previous' +others are '.section' (*note Section::), '.pushsection' (*note +PushSection::), '.popsection' (*note PopSection::), and '.previous' (*note Previous::). - This directive replaces the current subsection with `name'. The -current section is not changed. The replaced subsection is put onto -the section stack in place of the then current top of stack subsection. + This directive replaces the current subsection with 'name'. The +current section is not changed. The replaced subsection is put onto the +section stack in place of the then current top of stack subsection.  File: as.info, Node: Symver, Next: Tag, Prev: SubSection, Up: Pseudo Ops -7.90 `.symver' +7.90 '.symver' ============== -Use the `.symver' directive to bind symbols to specific version nodes +Use the '.symver' directive to bind symbols to specific version nodes within a source file. This is only supported on ELF platforms, and is typically used when assembling files to be linked into a shared library. There are cases where it may make sense to use this in objects to be bound into an application itself so as to override a versioned symbol from a shared library. - For ELF targets, the `.symver' directive can be used like this: + For ELF targets, the '.symver' directive can be used like this: .symver NAME, NAME2@NODENAME If the symbol NAME is defined within the file being assembled, the -`.symver' directive effectively creates a symbol alias with the name +'.symver' directive effectively creates a symbol alias with the name NAME2@NODENAME, and in fact the main reason that we just don't try and -create a regular alias is that the @ character isn't permitted in -symbol names. The NAME2 part of the name is the actual name of the -symbol by which it will be externally referenced. The name NAME itself -is merely a name of convenience that is used so that it is possible to -have definitions for multiple versions of a function within a single -source file, and so that the compiler can unambiguously know which -version of a function is being mentioned. The NODENAME portion of the -alias should be the name of a node specified in the version script -supplied to the linker when building a shared library. If you are -attempting to override a versioned symbol from a shared library, then -NODENAME should correspond to the nodename of the symbol you are trying -to override. +create a regular alias is that the @ character isn't permitted in symbol +names. The NAME2 part of the name is the actual name of the symbol by +which it will be externally referenced. The name NAME itself is merely +a name of convenience that is used so that it is possible to have +definitions for multiple versions of a function within a single source +file, and so that the compiler can unambiguously know which version of a +function is being mentioned. The NODENAME portion of the alias should +be the name of a node specified in the version script supplied to the +linker when building a shared library. If you are attempting to +override a versioned symbol from a shared library, then NODENAME should +correspond to the nodename of the symbol you are trying to override. If the symbol NAME is not defined within the file being assembled, all references to NAME will be changed to NAME2@NODENAME. If no reference to NAME is made, NAME2@NODENAME will be removed from the symbol table. - Another usage of the `.symver' directive is: + Another usage of the '.symver' directive is: .symver NAME, NAME2@@NODENAME In this case, the symbol NAME must exist and be defined within the -file being assembled. It is similar to NAME2@NODENAME. The difference +file being assembled. It is similar to NAME2@NODENAME. The difference is NAME2@@NODENAME will also be used to resolve references to NAME2 by the linker. - The third usage of the `.symver' directive is: + The third usage of the '.symver' directive is: .symver NAME, NAME2@@@NODENAME When NAME is not defined within the file being assembled, it is -treated as NAME2@NODENAME. When NAME is defined within the file being +treated as NAME2@NODENAME. When NAME is defined within the file being assembled, the symbol name, NAME, will be changed to NAME2@@NODENAME.  File: as.info, Node: Tag, Next: Text, Prev: Symver, Up: Pseudo Ops -7.91 `.tag STRUCTNAME' +7.91 '.tag STRUCTNAME' ====================== This directive is generated by compilers to include auxiliary debugging information in the symbol table. It is only permitted inside -`.def'/`.endef' pairs. Tags are used to link structure definitions in +'.def'/'.endef' pairs. Tags are used to link structure definitions in the symbol table with instances of those structures.  File: as.info, Node: Text, Next: Title, Prev: Tag, Up: Pseudo Ops -7.92 `.text SUBSECTION' +7.92 '.text SUBSECTION' ======================= -Tells `as' to assemble the following statements onto the end of the -text subsection numbered SUBSECTION, which is an absolute expression. -If SUBSECTION is omitted, subsection number zero is used. +Tells 'as' to assemble the following statements onto the end of the text +subsection numbered SUBSECTION, which is an absolute expression. If +SUBSECTION is omitted, subsection number zero is used.  File: as.info, Node: Title, Next: Type, Prev: Text, Up: Pseudo Ops -7.93 `.title "HEADING"' +7.93 '.title "HEADING"' ======================= -Use HEADING as the title (second line, immediately after the source -file name and pagenumber) when generating assembly listings. +Use HEADING as the title (second line, immediately after the source file +name and pagenumber) when generating assembly listings. This directive affects subsequent pages, as well as the current page if it appears within ten lines of the top of a page. @@ -5603,7 +5484,7 @@  File: as.info, Node: Type, Next: Uleb128, Prev: Title, Up: Pseudo Ops -7.94 `.type' +7.94 '.type' ============ This directive is used to set the type of a symbol. @@ -5611,8 +5492,8 @@ COFF Version ------------ - For COFF targets, this directive is permitted only within -`.def'/`.endef' pairs. It is used like this: +For COFF targets, this directive is permitted only within +'.def'/'.endef' pairs. It is used like this: .type INT @@ -5622,7 +5503,7 @@ ELF Version ----------- - For ELF targets, the `.type' directive is used like this: +For ELF targets, the '.type' directive is used like this: .type NAME , TYPE DESCRIPTION @@ -5631,12 +5512,12 @@ TYPE DESCRIPTION field, in order to provide compatibility with various other assemblers. - Because some of the characters used in these syntaxes (such as `@' -and `#') are comment characters for some architectures, some of the -syntaxes below do not work on all architectures. The first variant -will be accepted by the GNU assembler on all architectures so that -variant should be used for maximum portability, if you do not need to -assemble your code with other assemblers. + Because some of the characters used in these syntaxes (such as '@' +and '#') are comment characters for some architectures, some of the +syntaxes below do not work on all architectures. The first variant will +be accepted by the GNU assembler on all architectures so that variant +should be used for maximum portability, if you do not need to assemble +your code with other assemblers. The syntaxes supported are: @@ -5648,113 +5529,112 @@ The types supported are: -`STT_FUNC' -`function' +'STT_FUNC' +'function' Mark the symbol as being a function name. -`STT_GNU_IFUNC' -`gnu_indirect_function' +'STT_GNU_IFUNC' +'gnu_indirect_function' Mark the symbol as an indirect function when evaluated during reloc processing. (This is only supported on assemblers targeting GNU systems). -`STT_OBJECT' -`object' +'STT_OBJECT' +'object' Mark the symbol as being a data object. -`STT_TLS' -`tls_object' +'STT_TLS' +'tls_object' Mark the symbol as being a thead-local data object. -`STT_COMMON' -`common' +'STT_COMMON' +'common' Mark the symbol as being a common data object. -`STT_NOTYPE' -`notype' +'STT_NOTYPE' +'notype' Does not mark the symbol in any way. It is supported just for completeness. -`gnu_unique_object' +'gnu_unique_object' Marks the symbol as being a globally unique data object. The dynamic linker will make sure that in the entire process there is just one symbol with this name and type in use. (This is only supported on assemblers targeting GNU systems). - Note: Some targets support extra types in addition to those listed above.  File: as.info, Node: Uleb128, Next: Val, Prev: Type, Up: Pseudo Ops -7.95 `.uleb128 EXPRESSIONS' +7.95 '.uleb128 EXPRESSIONS' =========================== ULEB128 stands for "unsigned little endian base 128." This is a compact, variable length representation of numbers used by the DWARF -symbolic debugging format. *Note `.sleb128': Sleb128. +symbolic debugging format. *Note '.sleb128': Sleb128.  File: as.info, Node: Val, Next: Version, Prev: Uleb128, Up: Pseudo Ops -7.96 `.val ADDR' +7.96 '.val ADDR' ================ -This directive, permitted only within `.def'/`.endef' pairs, records -the address ADDR as the value attribute of a symbol table entry. +This directive, permitted only within '.def'/'.endef' pairs, records the +address ADDR as the value attribute of a symbol table entry.  File: as.info, Node: Version, Next: VTableEntry, Prev: Val, Up: Pseudo Ops -7.97 `.version "STRING"' +7.97 '.version "STRING"' ======================== -This directive creates a `.note' section and places into it an ELF -formatted note of type NT_VERSION. The note's name is set to `string'. +This directive creates a '.note' section and places into it an ELF +formatted note of type NT_VERSION. The note's name is set to 'string'.  File: as.info, Node: VTableEntry, Next: VTableInherit, Prev: Version, Up: Pseudo Ops -7.98 `.vtable_entry TABLE, OFFSET' +7.98 '.vtable_entry TABLE, OFFSET' ================================== -This directive finds or creates a symbol `table' and creates a -`VTABLE_ENTRY' relocation for it with an addend of `offset'. +This directive finds or creates a symbol 'table' and creates a +'VTABLE_ENTRY' relocation for it with an addend of 'offset'.  File: as.info, Node: VTableInherit, Next: Warning, Prev: VTableEntry, Up: Pseudo Ops -7.99 `.vtable_inherit CHILD, PARENT' +7.99 '.vtable_inherit CHILD, PARENT' ==================================== -This directive finds the symbol `child' and finds or creates the symbol -`parent' and then creates a `VTABLE_INHERIT' relocation for the parent +This directive finds the symbol 'child' and finds or creates the symbol +'parent' and then creates a 'VTABLE_INHERIT' relocation for the parent whose addend is the value of the child symbol. As a special case the -parent name of `0' is treated as referring to the `*ABS*' section. +parent name of '0' is treated as referring to the '*ABS*' section.  File: as.info, Node: Warning, Next: Weak, Prev: VTableInherit, Up: Pseudo Ops -7.100 `.warning "STRING"' +7.100 '.warning "STRING"' ========================= -Similar to the directive `.error' (*note `.error "STRING"': Error.), -but just emits a warning. +Similar to the directive '.error' (*note '.error "STRING"': Error.), but +just emits a warning.  File: as.info, Node: Weak, Next: Weakref, Prev: Warning, Up: Pseudo Ops -7.101 `.weak NAMES' +7.101 '.weak NAMES' =================== This directive sets the weak attribute on the comma separated list of -symbol `names'. If the symbols do not already exist, they will be +symbol 'names'. If the symbols do not already exist, they will be created. On COFF targets other than PE, weak symbols are a GNU extension. This directive sets the weak attribute on the comma separated list of -symbol `names'. If the symbols do not already exist, they will be +symbol 'names'. If the symbols do not already exist, they will be created. On the PE target, weak symbols are supported natively as weak @@ -5764,15 +5644,15 @@  File: as.info, Node: Weakref, Next: Word, Prev: Weak, Up: Pseudo Ops -7.102 `.weakref ALIAS, TARGET' +7.102 '.weakref ALIAS, TARGET' ============================== This directive creates an alias to the target symbol that enables the -symbol to be referenced with weak-symbol semantics, but without -actually making it weak. If direct references or definitions of the -symbol are present, then the symbol will not be weak, but if all -references to it are through weak references, the symbol will be marked -as weak in the symbol table. +symbol to be referenced with weak-symbol semantics, but without actually +making it weak. If direct references or definitions of the symbol are +present, then the symbol will not be weak, but if all references to it +are through weak references, the symbol will be marked as weak in the +symbol table. The effect is equivalent to moving all references to the alias to a separate assembly source file, renaming the alias to the symbol in it, @@ -5787,7 +5667,7 @@  File: as.info, Node: Word, Next: Zero, Prev: Weakref, Up: Pseudo Ops -7.103 `.word EXPRESSIONS' +7.103 '.word EXPRESSIONS' ========================= This directive expects zero or more EXPRESSIONS, of any section, @@ -5803,37 +5683,35 @@ interest to you does 32-bit addressing (or doesn't require it; *note Machine Dependencies::), you can ignore this issue. - In order to assemble compiler output into something that works, `as' -occasionally does strange things to `.word' directives. Directives of -the form `.word sym1-sym2' are often emitted by compilers as part of -jump tables. Therefore, when `as' assembles a directive of the form -`.word sym1-sym2', and the difference between `sym1' and `sym2' does -not fit in 16 bits, `as' creates a "secondary jump table", immediately + In order to assemble compiler output into something that works, 'as' +occasionally does strange things to '.word' directives. Directives of +the form '.word sym1-sym2' are often emitted by compilers as part of +jump tables. Therefore, when 'as' assembles a directive of the form +'.word sym1-sym2', and the difference between 'sym1' and 'sym2' does not +fit in 16 bits, 'as' creates a "secondary jump table", immediately before the next label. This secondary jump table is preceded by a -short-jump to the first byte after the secondary table. This -short-jump prevents the flow of control from accidentally falling into -the new table. Inside the table is a long-jump to `sym2'. The -original `.word' contains `sym1' minus the address of the long-jump to -`sym2'. - - If there were several occurrences of `.word sym1-sym2' before the -secondary jump table, all of them are adjusted. If there was a `.word -sym3-sym4', that also did not fit in sixteen bits, a long-jump to -`sym4' is included in the secondary jump table, and the `.word' -directives are adjusted to contain `sym3' minus the address of the -long-jump to `sym4'; and so on, for as many entries in the original -jump table as necessary. +short-jump to the first byte after the secondary table. This short-jump +prevents the flow of control from accidentally falling into the new +table. Inside the table is a long-jump to 'sym2'. The original '.word' +contains 'sym1' minus the address of the long-jump to 'sym2'. + + If there were several occurrences of '.word sym1-sym2' before the +secondary jump table, all of them are adjusted. If there was a '.word +sym3-sym4', that also did not fit in sixteen bits, a long-jump to 'sym4' +is included in the secondary jump table, and the '.word' directives are +adjusted to contain 'sym3' minus the address of the long-jump to 'sym4'; +and so on, for as many entries in the original jump table as necessary.  File: as.info, Node: Zero, Next: Deprecated, Prev: Word, Up: Pseudo Ops -7.104 `.zero SIZE' +7.104 '.zero SIZE' ================== This directive emits SIZE 0-valued bytes. SIZE must be an absolute -expression. This directive is actually an alias for the `.skip' +expression. This directive is actually an alias for the '.skip' directive so in can take an optional second argument of the value to -store in the bytes instead of zero. Using `.zero' in this way would be +store in the bytes instead of zero. Using '.zero' in this way would be confusing however.  @@ -5845,7 +5723,6 @@ One day these directives won't work. They are included for compatibility with older assemblers. .abort - .line  @@ -5854,7 +5731,7 @@ 8 Object Attributes ******************* -`as' assembles source files written for a specific architecture into +'as' assembles source files written for a specific architecture into object files for that architecture. But not all object files are alike. Many architectures support incompatible variations. For instance, floating point arguments might be passed in floating point registers if @@ -5865,19 +5742,19 @@ the combination may require the newer generation at run-time. This information is useful during and after linking. At link time, -`ld' can warn about incompatible object files. After link time, tools -like `gdb' can use it to process the linked file correctly. +'ld' can warn about incompatible object files. After link time, tools +like 'gdb' can use it to process the linked file correctly. Compatibility information is recorded as a series of object attributes. Each attribute has a "vendor", "tag", and "value". The vendor is a string, and indicates who sets the meaning of the tag. The tag is an integer, and indicates what property the attribute describes. -The value may be a string or an integer, and indicates how the -property affects this object. Missing attributes are the same as -attributes with a zero value or empty string value. +The value may be a string or an integer, and indicates how the property +affects this object. Missing attributes are the same as attributes with +a zero value or empty string value. Object attributes were developed as part of the ABI for the ARM -Architecture. The file format is documented in `ELF for the ARM +Architecture. The file format is documented in 'ELF for the ARM Architecture'. * Menu: @@ -5891,14 +5768,14 @@ 8.1 GNU Object Attributes ========================= -The `.gnu_attribute' directive records an object attribute with vendor -`gnu'. +The '.gnu_attribute' directive records an object attribute with vendor +'gnu'. - Except for `Tag_compatibility', which has both an integer and a + Except for 'Tag_compatibility', which has both an integer and a string for its value, GNU attributes have a string value if the tag number is odd and an integer value if the tag number is even. The -second bit (`TAG & 2' is set for architecture-independent attributes -and clear for architecture-dependent ones. +second bit ('TAG & 2' is set for architecture-independent attributes and +clear for architecture-dependent ones. 8.1.1 Common GNU attributes --------------------------- @@ -5921,30 +5798,23 @@ be: * 0 for files not affected by the floating-point ABI. - * 1 for files using the hardware floating-point ABI with a standard double-precision FPU. - * 2 for files using the hardware floating-point ABI with a single-precision FPU. - * 3 for files using the software floating-point ABI. - * 4 for files using the deprecated hardware floating-point ABI which used 64-bit floating-point registers, 32-bit general-purpose registers and increased the number of callee-saved floating-point registers. - * 5 for files using the hardware floating-point ABI with a double-precision FPU with either 32-bit or 64-bit floating-point registers and 32-bit general-purpose registers. - * 6 for files using the hardware floating-point ABI with 64-bit floating-point registers and 32-bit general-purpose registers. - * 7 for files using the hardware floating-point ABI with 64-bit - floating-point registers, 32-bit general-purpose registers - and a rule that forbids the direct use of odd-numbered + floating-point registers, 32-bit general-purpose registers and + a rule that forbids the direct use of odd-numbered single-precision floating-point registers. 8.1.3 PowerPC Attributes @@ -5955,12 +5825,9 @@ be: * 0 for files not affected by the floating-point ABI. - * 1 for files using double-precision hardware floating-point ABI. - * 2 for files using the software floating-point ABI. - * 3 for files using single-precision hardware floating-point ABI. @@ -5968,11 +5835,8 @@ The vector ABI used by this object file. The value will be: * 0 for files not affected by the vector ABI. - * 1 for files using general purpose registers to pass vectors. - * 2 for files using AltiVec registers to pass vectors. - * 3 for files using SPE registers to pass vectors. 8.1.4 IBM z Systems Attributes @@ -5982,9 +5846,7 @@ The vector ABI used by this object file. The value will be: * 0 for files not affected by the vector ABI. - * 1 for files using software vector ABI. - * 2 for files using hardware vector ABI.  @@ -5995,19 +5857,14 @@ If you want to define a new GNU object attribute, here are the places you will need to modify. New attributes should be discussed on the -`binutils' mailing list. +'binutils' mailing list. * This manual, which is the official register of attributes. - - * The header for your architecture `include/elf', to define the tag. - - * The `bfd' support file for your architecture, to merge the + * The header for your architecture 'include/elf', to define the tag. + * The 'bfd' support file for your architecture, to merge the attribute and issue any appropriate link warnings. - - * Test cases in `ld/testsuite' for merging and link warnings. - - * `binutils/readelf.c' to display your attribute. - + * Test cases in 'ld/testsuite' for merging and link warnings. + * 'binutils/readelf.c' to display your attribute. * GCC, if you want the compiler to mark the attribute automatically.  @@ -6017,10 +5874,10 @@ **************************** The machine instruction sets are (almost by definition) different on -each machine where `as' runs. Floating point representations vary as -well, and `as' often supports a few additional directives or +each machine where 'as' runs. Floating point representations vary as +well, and 'as' often supports a few additional directives or command-line options for compatibility with other assemblers on a -particular platform. Finally, some versions of `as' support special +particular platform. Finally, some versions of 'as' support special pseudo-instructions for branch optimization. This chapter discusses most of these differences, though it does not @@ -6029,114 +5886,60 @@ * Menu: - * AArch64-Dependent:: AArch64 Dependent Features - * Alpha-Dependent:: Alpha Dependent Features - * ARC-Dependent:: ARC Dependent Features - * ARM-Dependent:: ARM Dependent Features - * AVR-Dependent:: AVR Dependent Features - * Blackfin-Dependent:: Blackfin Dependent Features - * CR16-Dependent:: CR16 Dependent Features - * CRIS-Dependent:: CRIS Dependent Features - * D10V-Dependent:: D10V Dependent Features - * D30V-Dependent:: D30V Dependent Features - * Epiphany-Dependent:: EPIPHANY Dependent Features - * H8/300-Dependent:: Renesas H8/300 Dependent Features - * HPPA-Dependent:: HPPA Dependent Features - * ESA/390-Dependent:: IBM ESA/390 Dependent Features - * i386-Dependent:: Intel 80386 and AMD x86-64 Dependent Features - * i860-Dependent:: Intel 80860 Dependent Features - * i960-Dependent:: Intel 80960 Dependent Features - * IA-64-Dependent:: Intel IA-64 Dependent Features - * IP2K-Dependent:: IP2K Dependent Features - * LM32-Dependent:: LM32 Dependent Features - * M32C-Dependent:: M32C Dependent Features - * M32R-Dependent:: M32R Dependent Features - * M68K-Dependent:: M680x0 Dependent Features - * M68HC11-Dependent:: M68HC11 and 68HC12 Dependent Features - * Meta-Dependent :: Meta Dependent Features - * MicroBlaze-Dependent:: MICROBLAZE Dependent Features - * MIPS-Dependent:: MIPS Dependent Features - * MMIX-Dependent:: MMIX Dependent Features - * MSP430-Dependent:: MSP430 Dependent Features - * NDS32-Dependent:: Andes NDS32 Dependent Features - * NiosII-Dependent:: Altera Nios II Dependent Features - * NS32K-Dependent:: NS32K Dependent Features - * PDP-11-Dependent:: PDP-11 Dependent Features - * PJ-Dependent:: picoJava Dependent Features - * PPC-Dependent:: PowerPC Dependent Features - * RL78-Dependent:: RL78 Dependent Features - * RISC-V-Dependent:: RISC-V Dependent Features - * RX-Dependent:: RX Dependent Features - * S/390-Dependent:: IBM S/390 Dependent Features - * SCORE-Dependent:: SCORE Dependent Features - * SH-Dependent:: Renesas / SuperH SH Dependent Features * SH64-Dependent:: SuperH SH64 Dependent Features - * Sparc-Dependent:: SPARC Dependent Features - * TIC54X-Dependent:: TI TMS320C54x Dependent Features - * TIC6X-Dependent :: TI TMS320C6x Dependent Features - * TILE-Gx-Dependent :: Tilera TILE-Gx Dependent Features - * TILEPro-Dependent :: Tilera TILEPro Dependent Features - * V850-Dependent:: V850 Dependent Features - * Vax-Dependent:: VAX Dependent Features - * Visium-Dependent:: Visium Dependent Features - * XGATE-Dependent:: XGATE Features - * XSTORMY16-Dependent:: XStormy16 Dependent Features - * Xtensa-Dependent:: Xtensa Dependent Features - * Z80-Dependent:: Z80 Dependent Features - * Z8000-Dependent:: Z8000 Dependent Features  @@ -6161,63 +5964,62 @@ 9.1.1 Options ------------- -`-EB' +'-EB' This option specifies that the output generated by the assembler should be marked as being encoded for a big-endian processor. -`-EL' +'-EL' This option specifies that the output generated by the assembler should be marked as being encoded for a little-endian processor. -`-mabi=ABI' +'-mabi=ABI' Specify which ABI the source code uses. The recognized arguments - are: `ilp32' and `lp64', which decides the generated object file - in ELF32 and ELF64 format respectively. The default is `lp64'. + are: 'ilp32' and 'lp64', which decides the generated object file in + ELF32 and ELF64 format respectively. The default is 'lp64'. -`-mcpu=PROCESSOR[+EXTENSION...]' +'-mcpu=PROCESSOR[+EXTENSION...]' This option specifies the target processor. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target processor. The - following processor names are recognized: `cortex-a35', - `cortex-a53', `cortex-a57', `cortex-a72', `cortex-a73', - `exynos-m1', `falkor', `qdf24xx', `thunderx', `vulcan', `xgene1' - and `xgene2'. The special name `all' may be used to allow the - assembler to accept instructions valid for any supported - processor, including all optional extensions. - - In addition to the basic instruction set, the assembler can be - told to accept, or restrict, various extension mnemonics that - extend the processor. *Note AArch64 Extensions::. + following processor names are recognized: 'cortex-a35', + 'cortex-a53', 'cortex-a57', 'cortex-a72', 'cortex-a73', + 'exynos-m1', 'falkor', 'qdf24xx', 'thunderx', 'vulcan', 'xgene1' + and 'xgene2'. The special name 'all' may be used to allow the + assembler to accept instructions valid for any supported processor, + including all optional extensions. + + In addition to the basic instruction set, the assembler can be told + to accept, or restrict, various extension mnemonics that extend the + processor. *Note AArch64 Extensions::. If some implementations of a particular processor can have an extension, then then those extensions are automatically enabled. Consequently, you will not normally have to specify any additional extensions. -`-march=ARCHITECTURE[+EXTENSION...]' +'-march=ARCHITECTURE[+EXTENSION...]' This option specifies the target architecture. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target architecture. The - following architecture names are recognized: `armv8-a', - `armv8.1-a', `armv8.2-a' and `armv8.3-a'. + following architecture names are recognized: 'armv8-a', + 'armv8.1-a', 'armv8.2-a' and 'armv8.3-a'. - If both `-mcpu' and `-march' are specified, the assembler will use - the setting for `-mcpu'. If neither are specified, the assembler - will default to `-mcpu=all'. + If both '-mcpu' and '-march' are specified, the assembler will use + the setting for '-mcpu'. If neither are specified, the assembler + will default to '-mcpu=all'. The architecture option can be extended with the same instruction - set extension options as the `-mcpu' option. Unlike `-mcpu', + set extension options as the '-mcpu' option. Unlike '-mcpu', extensions are not always enabled by default, *Note AArch64 Extensions::. -`-mverbose-error' +'-mverbose-error' This option enables verbose error messages for AArch64 gas. This option is enabled by default. -`-mno-verbose-error' +'-mno-verbose-error' This option disables verbose error messages in AArch64 gas. -  File: as.info, Node: AArch64 Extensions, Next: AArch64 Syntax, Prev: AArch64 Options, Up: AArch64-Dependent @@ -6228,9 +6030,9 @@ supported by the assembler and the conditions under which they are automatically enabled. - Multiple extensions may be specified, separated by a `+'. Extension -mnemonics may also be removed from those the assembler accepts. This -is done by prepending `no' to the option that adds the extension. + Multiple extensions may be specified, separated by a '+'. Extension +mnemonics may also be removed from those the assembler accepts. This is +done by prepending 'no' to the option that adds the extension. Extensions that are removed must be listed after all extensions that have been added. @@ -6240,36 +6042,36 @@ automatically cause those extensions to be disabled. Extension Minimum Enabled by Description - Architecture default ----------------------------------------------------------------------------- -`compnum' ARMv8.2-A ARMv8.3-A Enable the complex number SIMD - or later extensions. This implies `fp16' and - `simd'. -`crc' ARMv8-A ARMv8.1-A Enable CRC instructions. - or later -`crypto' ARMv8-A No Enable cryptographic extensions. This - implies `fp' and `simd'. -`fp' ARMv8-A ARMv8-A or Enable floating-point extensions. - later -`fp16' ARMv8.2-A ARMv8.2-A Enable ARMv8.2 16-bit floating-point - or later support. This implies `fp'. -`lor' ARMv8-A ARMv8.1-A Enable Limited Ordering Regions + Architecture default +---------------------------------------------------------------------------- +'compnum' ARMv8.2-A ARMv8.3-A Enable the complex number SIMD + or later extensions. This implies 'fp16' and + 'simd'. +'crc' ARMv8-A ARMv8.1-A Enable CRC instructions. + or later +'crypto' ARMv8-A No Enable cryptographic extensions. + This implies 'fp' and 'simd'. +'fp' ARMv8-A ARMv8-A or Enable floating-point extensions. + later +'fp16' ARMv8.2-A ARMv8.2-A Enable ARMv8.2 16-bit floating-point + or later support. This implies 'fp'. +'lor' ARMv8-A ARMv8.1-A Enable Limited Ordering Regions or later extensions. -`lse' ARMv8-A ARMv8.1-A Enable Large System extensions. - or later -`pan' ARMv8-A ARMv8.1-A Enable Privileged Access Never support. - or later -`profile' ARMv8.2-A No Enable statistical profiling +'lse' ARMv8-A ARMv8.1-A Enable Large System extensions. + or later +'pan' ARMv8-A ARMv8.1-A Enable Privileged Access Never + or later support. +'profile' ARMv8.2-A No Enable statistical profiling extensions. -`ras' ARMv8-A ARMv8.2-A Enable the Reliability, Availability - or later and Serviceability extension. -`rdma' ARMv8-A ARMv8.1-A Enable ARMv8.1 Advanced SIMD - or later extensions. This implies `simd'. -`simd' ARMv8-A ARMv8-A or Enable Advanced SIMD extensions. This - later implies `fp'. -`sve' ARMv8.2-A No Enable the Scalable Vector Extensions. - This implies `fp16', `simd' and - `compnum'. +'ras' ARMv8-A ARMv8.2-A Enable the Reliability, Availability + or later and Serviceability extension. +'rdma' ARMv8-A ARMv8.1-A Enable ARMv8.1 Advanced SIMD + or later extensions. This implies 'simd'. +'simd' ARMv8-A ARMv8-A or Enable Advanced SIMD extensions. + later This implies 'fp'. +'sve' ARMv8.2-A No Enable the Scalable Vector + Extensions. This implies 'fp16', + 'simd' and 'compnum'.  File: as.info, Node: AArch64 Syntax, Next: AArch64 Floating Point, Prev: AArch64 Extensions, Up: AArch64-Dependent @@ -6289,14 +6091,14 @@ 9.1.3.1 Special Characters .......................... -The presence of a `//' on a line indicates the start of a comment that -extends to the end of the current line. If a `#' appears as the first +The presence of a '//' on a line indicates the start of a comment that +extends to the end of the current line. If a '#' appears as the first character of a line, the whole line is treated as a comment. - The `;' character can be used instead of a newline to separate + The ';' character can be used instead of a newline to separate statements. - The `#' can be optionally used to indicate immediate operands. + The '#' can be optionally used to indicate immediate operands.  File: as.info, Node: AArch64-Regs, Next: AArch64-Relocations, Prev: AArch64-Chars, Up: AArch64 Syntax @@ -6304,8 +6106,8 @@ 9.1.3.2 Register Names ...................... -Please refer to the section `4.4 Register Names' of `ARMv8 Instruction -Set Overview', which is available at `http://infocenter.arm.com'. +Please refer to the section '4.4 Register Names' of 'ARMv8 Instruction +Set Overview', which is available at .  File: as.info, Node: AArch64-Relocations, Prev: AArch64-Regs, Up: AArch64 Syntax @@ -6313,20 +6115,20 @@ 9.1.3.3 Relocations ................... -Relocations for `MOVZ' and `MOVK' instructions can be generated by -prefixing the label with `#:abs_g2:' etc. For example to load the +Relocations for 'MOVZ' and 'MOVK' instructions can be generated by +prefixing the label with '#:abs_g2:' etc. For example to load the 48-bit absolute address of FOO into x0: movz x0, #:abs_g2:foo // bits 32-47, overflow check movk x0, #:abs_g1_nc:foo // bits 16-31, no overflow check movk x0, #:abs_g0_nc:foo // bits 0-15, no overflow check - Relocations for `ADRP', and `ADD', `LDR' or `STR' instructions can -be generated by prefixing the label with `:pg_hi21:' and `#:lo12:' + Relocations for 'ADRP', and 'ADD', 'LDR' or 'STR' instructions can be +generated by prefixing the label with ':pg_hi21:' and '#:lo12:' respectively. - For example to use 33-bit (+/-4GB) pc-relative addressing to load -the address of FOO into x0: + For example to use 33-bit (+/-4GB) pc-relative addressing to load the +address of FOO into x0: adrp x0, :pg_hi21:foo add x0, x0, #:lo12:foo @@ -6336,7 +6138,7 @@ adrp x0, :pg_hi21:foo ldr x0, [x0, #:lo12:foo] - Note that `:pg_hi21:' is optional. + Note that ':pg_hi21:' is optional. adrp x0, foo @@ -6358,74 +6160,73 @@ 9.1.5 AArch64 Machine Directives -------------------------------- -`.arch NAME' - Select the target architecture. Valid values for NAME are the - same as for the `-march' commandline option. +'.arch NAME' + Select the target architecture. Valid values for NAME are the same + as for the '-march' commandline option. - Specifying `.arch' clears any previously selected architecture + Specifying '.arch' clears any previously selected architecture extensions. -`.arch_extension NAME' - Add or remove an architecture extension to the target - architecture. Valid values for NAME are the same as those - accepted as architectural extensions by the `-mcpu' commandline - option. +'.arch_extension NAME' + Add or remove an architecture extension to the target architecture. + Valid values for NAME are the same as those accepted as + architectural extensions by the '-mcpu' commandline option. - `.arch_extension' may be used multiple times to add or remove + '.arch_extension' may be used multiple times to add or remove extensions incrementally to the architecture being compiled for. -`.bss' - This directive switches to the `.bss' section. +'.bss' + This directive switches to the '.bss' section. -`.cpu NAME' +'.cpu NAME' Set the target processor. Valid values for NAME are the same as - those accepted by the `-mcpu=' command line option. + those accepted by the '-mcpu=' command line option. -`.dword EXPRESSIONS' - The `.dword' directive produces 64 bit values. +'.dword EXPRESSIONS' + The '.dword' directive produces 64 bit values. -`.even' - The `.even' directive aligns the output on the next even byte +'.even' + The '.even' directive aligns the output on the next even byte boundary. -`.inst EXPRESSIONS' +'.inst EXPRESSIONS' Inserts the expressions into the output as if they were instructions, rather than data. -`.ltorg' +'.ltorg' This directive causes the current contents of the literal pool to be dumped into the current section (which is assumed to be the .text section) at the current location (aligned to a word boundary). GAS maintains a separate literal pool for each section - and each sub-section. The `.ltorg' directive will only affect the - literal pool of the current section and sub-section. At the end - of assembly all remaining, un-empty literal pools will - automatically be dumped. + and each sub-section. The '.ltorg' directive will only affect the + literal pool of the current section and sub-section. At the end of + assembly all remaining, un-empty literal pools will automatically + be dumped. Note - older versions of GAS would dump the current literal pool any time a section change occurred. This is no longer done, since it prevents accurate control of the placement of literal pools. -`.pool' +'.pool' This is a synonym for .ltorg. -`NAME .req REGISTER NAME' +'NAME .req REGISTER NAME' This creates an alias for REGISTER NAME called NAME. For example: foo .req w0 -``.tlsdescadd'' +'.tlsdescadd' Emits a TLSDESC_ADD reloc on the next instruction. -``.tlsdesccall'' +'.tlsdesccall' Emits a TLSDESC_CALL reloc on the next instruction. -``.tlsdescldr'' +'.tlsdescldr' Emits a TLSDESC_LDR reloc on the next instruction. -`.unreq ALIAS-NAME' +'.unreq ALIAS-NAME' This undefines a register alias which was previously defined using - the `req' directive. For example: + the 'req' directive. For example: foo .req w0 .unreq foo @@ -6434,10 +6235,9 @@ can be used to delete builtin in register name aliases (eg 'w0'). This should only be done if it is really necessary. -`.xword EXPRESSIONS' - The `.xword' directive produces 64 bit values. This is the same - as the `.dword' directive. - +'.xword EXPRESSIONS' + The '.xword' directive produces 64 bit values. This is the same as + the '.dword' directive.  File: as.info, Node: AArch64 Opcodes, Next: AArch64 Mapping Symbols, Prev: AArch64 Directives, Up: AArch64-Dependent @@ -6448,17 +6248,16 @@ GAS implements all the standard AArch64 opcodes. It also implements several pseudo opcodes, including several synthetic load instructions. -`LDR =' +'LDR =' ldr , = The constant expression will be placed into the nearest literal pool (if it not already there) and a PC-relative LDR instruction will be generated. - For more information on the AArch64 instruction set and assembly -language notation, see `ARMv8 Instruction Set Overview' available at -`http://infocenter.arm.com'. +language notation, see 'ARMv8 Instruction Set Overview' available at +.  File: as.info, Node: AArch64 Mapping Symbols, Prev: AArch64 Opcodes, Up: AArch64-Dependent @@ -6469,13 +6268,12 @@ The AArch64 ELF specification requires that special symbols be inserted into object files to mark certain features: -`$x' +'$x' At the start of a region of code containing AArch64 instructions. -`$d' +'$d' At the start of a region of data. -  File: as.info, Node: Alpha-Dependent, Next: ARC-Dependent, Prev: AArch64-Dependent, Up: Machine Dependencies @@ -6497,9 +6295,9 @@ 9.2.1 Notes ----------- -The documentation here is primarily for the ELF object format. `as' -also supports the ECOFF and EVAX formats, but features specific to -these formats are not yet documented. +The documentation here is primarily for the ELF object format. 'as' +also supports the ECOFF and EVAX formats, but features specific to these +formats are not yet documented.  File: as.info, Node: Alpha Options, Next: Alpha Syntax, Prev: Alpha Notes, Up: Alpha-Dependent @@ -6507,33 +6305,33 @@ 9.2.2 Options ------------- -`-mCPU' +'-mCPU' This option specifies the target processor. If an attempt is made to assemble an instruction which will not execute on the target processor, the assembler may either expand the instruction as a macro or issue an error message. This option is equivalent to the - `.arch' directive. + '.arch' directive. - The following processor names are recognized: `21064', `21064a', - `21066', `21068', `21164', `21164a', `21164pc', `21264', `21264a', - `21264b', `ev4', `ev5', `lca45', `ev5', `ev56', `pca56', `ev6', - `ev67', `ev68'. The special name `all' may be used to allow the + The following processor names are recognized: '21064', '21064a', + '21066', '21068', '21164', '21164a', '21164pc', '21264', '21264a', + '21264b', 'ev4', 'ev5', 'lca45', 'ev5', 'ev56', 'pca56', 'ev6', + 'ev67', 'ev68'. The special name 'all' may be used to allow the assembler to accept instructions valid for any Alpha processor. In order to support existing practice in OSF/1 with respect to - `.arch', and existing practice within `MILO' (the Linux ARC + '.arch', and existing practice within 'MILO' (the Linux ARC bootloader), the numbered processor names (e.g. 21064) enable the - processor-specific PALcode instructions, while the - "electro-vlasic" names (e.g. `ev4') do not. + processor-specific PALcode instructions, while the "electro-vlasic" + names (e.g. 'ev4') do not. -`-mdebug' -`-no-mdebug' - Enables or disables the generation of `.mdebug' encapsulation for +'-mdebug' +'-no-mdebug' + Enables or disables the generation of '.mdebug' encapsulation for stabs directives and procedure descriptors. The default is to - automatically enable `.mdebug' when the first stabs directive is + automatically enable '.mdebug' when the first stabs directive is seen. -`-relax' +'-relax' This option forces all relocations to be put into the object file, instead of saving space and resolving some relocations at assembly time. Note that this option does not propagate all symbol @@ -6541,25 +6339,25 @@ can be represented. However, the option can still be useful in specific applications. -`-replace' -`-noreplace' +'-replace' +'-noreplace' Enables or disables the optimization of procedure calls, both at assemblage and at link time. These options are only available for - VMS targets and `-replace' is the default. See section 1.4.1 of + VMS targets and '-replace' is the default. See section 1.4.1 of the OpenVMS Linker Utility Manual. -`-g' +'-g' This option is used when the compiler generates debug information. - When `gcc' is using `mips-tfile' to generate debug information - for ECOFF, local labels must be passed through to the object file. + When 'gcc' is using 'mips-tfile' to generate debug information for + ECOFF, local labels must be passed through to the object file. Otherwise this option has no effect. -`-GSIZE' - A local common symbol larger than SIZE is placed in `.bss', while - smaller symbols are placed in `.sbss'. +'-GSIZE' + A local common symbol larger than SIZE is placed in '.bss', while + smaller symbols are placed in '.sbss'. -`-F' -`-32addr' +'-F' +'-32addr' These options are ignored for backward compatibility.  @@ -6584,12 +6382,12 @@ 9.2.3.1 Special Characters .......................... -`#' is the line comment character. Note that if `#' is the first +'#' is the line comment character. Note that if '#' is the first character on a line then it can also be a logical line number directive (*note Comments::) or a preprocessor control command (*note Preprocessing::). - `;' can be used instead of a newline to separate statements. + ';' can be used instead of a newline to separate statements.  File: as.info, Node: Alpha-Regs, Next: Alpha-Relocs, Prev: Alpha-Chars, Up: Alpha Syntax @@ -6597,11 +6395,11 @@ 9.2.3.2 Register Names ...................... -The 32 integer registers are referred to as `$N' or `$rN'. In -addition, registers 15, 28, 29, and 30 may be referred to by the -symbols `$fp', `$at', `$gp', and `$sp' respectively. +The 32 integer registers are referred to as '$N' or '$rN'. In addition, +registers 15, 28, 29, and 30 may be referred to by the symbols '$fp', +'$at', '$gp', and '$sp' respectively. - The 32 floating-point registers are referred to as `$fN'. + The 32 floating-point registers are referred to as '$fN'.  File: as.info, Node: Alpha-Relocs, Prev: Alpha-Regs, Up: Alpha Syntax @@ -6610,10 +6408,10 @@ ................... Some of these relocations are available for ECOFF, but mostly only for -ELF. They are modeled after the relocation format introduced in -Digital Unix 4.0, but there are additions. +ELF. They are modeled after the relocation format introduced in Digital +Unix 4.0, but there are additions. - The format is `!TAG' or `!TAG!NUMBER' where TAG is the name of the + The format is '!TAG' or '!TAG!NUMBER' where TAG is the name of the relocation. In some cases NUMBER is used to relate specific instructions. @@ -6624,147 +6422,145 @@ ldq $1,b($29) !literal!100 ldl $2,0($1) !lituse_base!100 -`!literal' -`!literal!N' - Used with an `ldq' instruction to load the address of a symbol - from the GOT. +'!literal' +'!literal!N' + Used with an 'ldq' instruction to load the address of a symbol from + the GOT. A sequence number N is optional, and if present is used to pair - `lituse' relocations with this `literal' relocation. The `lituse' + 'lituse' relocations with this 'literal' relocation. The 'lituse' relocations are used by the linker to optimize the code based on the final location of the symbol. Note that these optimizations are dependent on the data flow of the - program. Therefore, if _any_ `lituse' is paired with a `literal' - relocation, then _all_ uses of the register set by the `literal' - instruction must also be marked with `lituse' relocations. This - is because the original `literal' instruction may be deleted or + program. Therefore, if _any_ 'lituse' is paired with a 'literal' + relocation, then _all_ uses of the register set by the 'literal' + instruction must also be marked with 'lituse' relocations. This is + because the original 'literal' instruction may be deleted or transformed into another instruction. Also note that there may be a one-to-many relationship between - `literal' and `lituse', but not a many-to-one. That is, if there - are two code paths that load up the same address and feed the - value to a single use, then the use may not use a `lituse' - relocation. + 'literal' and 'lituse', but not a many-to-one. That is, if there + are two code paths that load up the same address and feed the value + to a single use, then the use may not use a 'lituse' relocation. -`!lituse_base!N' - Used with any memory format instruction (e.g. `ldl') to indicate +'!lituse_base!N' + Used with any memory format instruction (e.g. 'ldl') to indicate that the literal is used for an address load. The offset field of the instruction must be zero. During relaxation, the code may be altered to use a gp-relative load. -`!lituse_jsr!N' - Used with a register branch format instruction (e.g. `jsr') to +'!lituse_jsr!N' + Used with a register branch format instruction (e.g. 'jsr') to indicate that the literal is used for a call. During relaxation, - the code may be altered to use a direct branch (e.g. `bsr'). + the code may be altered to use a direct branch (e.g. 'bsr'). -`!lituse_jsrdirect!N' - Similar to `lituse_jsr', but also that this call cannot be vectored +'!lituse_jsrdirect!N' + Similar to 'lituse_jsr', but also that this call cannot be vectored through a PLT entry. This is useful for functions with special calling conventions which do not allow the normal call-clobbered registers to be clobbered. -`!lituse_bytoff!N' - Used with a byte mask instruction (e.g. `extbl') to indicate that +'!lituse_bytoff!N' + Used with a byte mask instruction (e.g. 'extbl') to indicate that only the low 3 bits of the address are relevant. During relaxation, the code may be altered to use an immediate instead of a register shift. -`!lituse_addr!N' +'!lituse_addr!N' Used with any other instruction to indicate that the original - address is in fact used, and the original `ldq' instruction may - not be altered or deleted. This is useful in conjunction with - `lituse_jsr' to test whether a weak symbol is defined. + address is in fact used, and the original 'ldq' instruction may not + be altered or deleted. This is useful in conjunction with + 'lituse_jsr' to test whether a weak symbol is defined. ldq $27,foo($29) !literal!1 beq $27,is_undef !lituse_addr!1 jsr $26,($27),foo !lituse_jsr!1 -`!lituse_tlsgd!N' +'!lituse_tlsgd!N' Used with a register branch format instruction to indicate that the - literal is the call to `__tls_get_addr' used to compute the - address of the thread-local storage variable whose descriptor was - loaded with `!tlsgd!N'. + literal is the call to '__tls_get_addr' used to compute the address + of the thread-local storage variable whose descriptor was loaded + with '!tlsgd!N'. -`!lituse_tlsldm!N' +'!lituse_tlsldm!N' Used with a register branch format instruction to indicate that the - literal is the call to `__tls_get_addr' used to compute the - address of the base of the thread-local storage block for the - current module. The descriptor for the module must have been - loaded with `!tlsldm!N'. - -`!gpdisp!N' - Used with `ldah' and `lda' to load the GP from the current - address, a-la the `ldgp' macro. The source register for the - `ldah' instruction must contain the address of the `ldah' - instruction. There must be exactly one `lda' instruction paired - with the `ldah' instruction, though it may appear anywhere in the - instruction stream. The immediate operands must be zero. + literal is the call to '__tls_get_addr' used to compute the address + of the base of the thread-local storage block for the current + module. The descriptor for the module must have been loaded with + '!tlsldm!N'. + +'!gpdisp!N' + Used with 'ldah' and 'lda' to load the GP from the current address, + a-la the 'ldgp' macro. The source register for the 'ldah' + instruction must contain the address of the 'ldah' instruction. + There must be exactly one 'lda' instruction paired with the 'ldah' + instruction, though it may appear anywhere in the instruction + stream. The immediate operands must be zero. bsr $26,foo ldah $29,0($26) !gpdisp!1 lda $29,0($29) !gpdisp!1 -`!gprelhigh' - Used with an `ldah' instruction to add the high 16 bits of a - 32-bit displacement from the GP. +'!gprelhigh' + Used with an 'ldah' instruction to add the high 16 bits of a 32-bit + displacement from the GP. -`!gprellow' +'!gprellow' Used with any memory format instruction to add the low 16 bits of a 32-bit displacement from the GP. -`!gprel' +'!gprel' Used with any memory format instruction to add a 16-bit displacement from the GP. -`!samegp' +'!samegp' Used with any branch format instruction to skip the GP load at the target address. The referenced symbol must have the same GP as the - source object file, and it must be declared to either not use `$27' + source object file, and it must be declared to either not use '$27' or perform a standard GP load in the first two instructions via the - `.prologue' directive. + '.prologue' directive. -`!tlsgd' -`!tlsgd!N' - Used with an `lda' instruction to load the address of a TLS +'!tlsgd' +'!tlsgd!N' + Used with an 'lda' instruction to load the address of a TLS descriptor for a symbol in the GOT. The sequence number N is optional, and if present it used to pair - the descriptor load with both the `literal' loading the address of - the `__tls_get_addr' function and the `lituse_tlsgd' marking the + the descriptor load with both the 'literal' loading the address of + the '__tls_get_addr' function and the 'lituse_tlsgd' marking the call to that function. - For proper relaxation, both the `tlsgd', `literal' and `lituse' - relocations must be in the same extended basic block. That is, - the relocation with the lowest address must be executed first at + For proper relaxation, both the 'tlsgd', 'literal' and 'lituse' + relocations must be in the same extended basic block. That is, the + relocation with the lowest address must be executed first at runtime. -`!tlsldm' -`!tlsldm!N' - Used with an `lda' instruction to load the address of a TLS +'!tlsldm' +'!tlsldm!N' + Used with an 'lda' instruction to load the address of a TLS descriptor for the current module in the GOT. - Similar in other respects to `tlsgd'. + Similar in other respects to 'tlsgd'. -`!gotdtprel' - Used with an `ldq' instruction to load the offset of the TLS - symbol within its module's thread-local storage block. Also known - as the dynamic thread pointer offset or dtp-relative offset. - -`!dtprelhi' -`!dtprello' -`!dtprel' - Like `gprel' relocations except they compute dtp-relative offsets. - -`!gottprel' - Used with an `ldq' instruction to load the offset of the TLS - symbol from the thread pointer. Also known as the tp-relative - offset. - -`!tprelhi' -`!tprello' -`!tprel' - Like `gprel' relocations except they compute tp-relative offsets. +'!gotdtprel' + Used with an 'ldq' instruction to load the offset of the TLS symbol + within its module's thread-local storage block. Also known as the + dynamic thread pointer offset or dtp-relative offset. + +'!dtprelhi' +'!dtprello' +'!dtprel' + Like 'gprel' relocations except they compute dtp-relative offsets. + +'!gottprel' + Used with an 'ldq' instruction to load the offset of the TLS symbol + from the thread pointer. Also known as the tp-relative offset. + +'!tprelhi' +'!tprello' +'!tprel' + Like 'gprel' relocations except they compute tp-relative offsets.  File: as.info, Node: Alpha Floating Point, Next: Alpha Directives, Prev: Alpha Syntax, Up: Alpha-Dependent @@ -6780,122 +6576,121 @@ 9.2.5 Alpha Assembler Directives -------------------------------- -`as' for the Alpha supports many additional directives for -compatibility with the native assembler. This section describes them -only briefly. +'as' for the Alpha supports many additional directives for compatibility +with the native assembler. This section describes them only briefly. - These are the additional directives in `as' for the Alpha: + These are the additional directives in 'as' for the Alpha: -`.arch CPU' - Specifies the target processor. This is equivalent to the `-mCPU' +'.arch CPU' + Specifies the target processor. This is equivalent to the '-mCPU' command-line option. *Note Options: Alpha Options, for a list of values for CPU. -`.ent FUNCTION[, N]' +'.ent FUNCTION[, N]' Mark the beginning of FUNCTION. An optional number may follow for compatibility with the OSF/1 assembler, but is ignored. When - generating `.mdebug' information, this will create a procedure + generating '.mdebug' information, this will create a procedure descriptor for the function. In ELF, it will mark the symbol as a - function a-la the generic `.type' directive. + function a-la the generic '.type' directive. -`.end FUNCTION' +'.end FUNCTION' Mark the end of FUNCTION. In ELF, it will set the size of the - symbol a-la the generic `.size' directive. + symbol a-la the generic '.size' directive. -`.mask MASK, OFFSET' +'.mask MASK, OFFSET' Indicate which of the integer registers are saved in the current function's stack frame. MASK is interpreted a bit mask in which bit N set indicates that register N is saved. The registers are saved in a block located OFFSET bytes from the "canonical frame address" (CFA) which is the value of the stack pointer on entry to the function. The registers are saved sequentially, except that - the return address register (normally `$26') is saved first. + the return address register (normally '$26') is saved first. This and the other directives that describe the stack frame are - currently only used when generating `.mdebug' information. They - may in the future be used to generate DWARF2 `.debug_frame' unwind + currently only used when generating '.mdebug' information. They + may in the future be used to generate DWARF2 '.debug_frame' unwind information for hand written assembly. -`.fmask MASK, OFFSET' +'.fmask MASK, OFFSET' Indicate which of the floating-point registers are saved in the current stack frame. The MASK and OFFSET parameters are - interpreted as with `.mask'. + interpreted as with '.mask'. -`.frame FRAMEREG, FRAMEOFFSET, RETREG[, ARGOFFSET]' +'.frame FRAMEREG, FRAMEOFFSET, RETREG[, ARGOFFSET]' Describes the shape of the stack frame. The frame pointer in use - is FRAMEREG; normally this is either `$fp' or `$sp'. The frame - pointer is FRAMEOFFSET bytes below the CFA. The return address is + is FRAMEREG; normally this is either '$fp' or '$sp'. The frame + pointer is FRAMEOFFSET bytes below the CFA. The return address is initially located in RETREG until it is saved as indicated in - `.mask'. For compatibility with OSF/1 an optional ARGOFFSET + '.mask'. For compatibility with OSF/1 an optional ARGOFFSET parameter is accepted and ignored. It is believed to indicate the offset from the CFA to the saved argument registers. -`.prologue N' +'.prologue N' Indicate that the stack frame is set up and all registers have been spilled. The argument N indicates whether and how the function uses the incoming "procedure vector" (the address of the called - function) in `$27'. 0 indicates that `$27' is not used; 1 - indicates that the first two instructions of the function use `$27' - to perform a load of the GP register; 2 indicates that `$27' is + function) in '$27'. 0 indicates that '$27' is not used; 1 + indicates that the first two instructions of the function use '$27' + to perform a load of the GP register; 2 indicates that '$27' is used in some non-standard way and so the linker cannot elide the load of the procedure vector during relaxation. -`.usepv FUNCTION, WHICH' - Used to indicate the use of the `$27' register, similar to - `.prologue', but without the other semantics of needing to be - inside an open `.ent'/`.end' block. +'.usepv FUNCTION, WHICH' + Used to indicate the use of the '$27' register, similar to + '.prologue', but without the other semantics of needing to be + inside an open '.ent'/'.end' block. - The WHICH argument should be either `no', indicating that `$27' is - not used, or `std', indicating that the first two instructions of + The WHICH argument should be either 'no', indicating that '$27' is + not used, or 'std', indicating that the first two instructions of the function perform a GP load. - One might use this directive instead of `.prologue' if you are - also using dwarf2 CFI directives. + One might use this directive instead of '.prologue' if you are also + using dwarf2 CFI directives. -`.gprel32 EXPRESSION' +'.gprel32 EXPRESSION' Computes the difference between the address in EXPRESSION and the GP for the current object file, and stores it in 4 bytes. In addition to being smaller than a full 8 byte address, this also does not require a dynamic relocation when used in a shared library. -`.t_floating EXPRESSION' +'.t_floating EXPRESSION' Stores EXPRESSION as an IEEE double precision value. -`.s_floating EXPRESSION' +'.s_floating EXPRESSION' Stores EXPRESSION as an IEEE single precision value. -`.f_floating EXPRESSION' +'.f_floating EXPRESSION' Stores EXPRESSION as a VAX F format value. -`.g_floating EXPRESSION' +'.g_floating EXPRESSION' Stores EXPRESSION as a VAX G format value. -`.d_floating EXPRESSION' +'.d_floating EXPRESSION' Stores EXPRESSION as a VAX D format value. -`.set FEATURE' +'.set FEATURE' Enables or disables various assembler features. Using the positive - name of the feature enables while using `noFEATURE' disables. + name of the feature enables while using 'noFEATURE' disables. - `at' + 'at' Indicates that macro expansions may clobber the "assembler - temporary" (`$at' or `$28') register. Some macros may not be + temporary" ('$at' or '$28') register. Some macros may not be expanded without this and will generate an error message if - `noat' is in effect. When `at' is in effect, a warning will - be generated if `$at' is used by the programmer. + 'noat' is in effect. When 'at' is in effect, a warning will + be generated if '$at' is used by the programmer. - `macro' + 'macro' Enables the expansion of macro instructions. Note that - variants of real instructions, such as `br label' vs `br + variants of real instructions, such as 'br label' vs 'br $31,label' are considered alternate forms and not macros. - `move' - `reorder' - `volatile' + 'move' + 'reorder' + 'volatile' These control whether and how the assembler may re-order instructions. Accepted for compatibility with the OSF/1 - assembler, but `as' does not do instruction scheduling, so + assembler, but 'as' does not do instruction scheduling, so these features are ignored. The following directives are recognized for compatibility with the @@ -6941,114 +6736,112 @@ The following options control the type of CPU for which code is assembled, and generic constraints on the code generated: -`-mcpu=CPU' +'-mcpu=CPU' Set architecture type and register usage for CPU. There are also shortcut alias options available for backward compatibility and convenience. Supported values for CPU are - `arc600' - Assemble for ARC 600. Aliases: `-mA6', `-mARC600'. + 'arc600' + Assemble for ARC 600. Aliases: '-mA6', '-mARC600'. - `arc600_norm' + 'arc600_norm' Assemble for ARC 600 with norm instructions. - `arc600_mul64' + 'arc600_mul64' Assemble for ARC 600 with mul64 instructions. - `arc600_mul32x16' + 'arc600_mul32x16' Assemble for ARC 600 with mul32x16 instructions. - `arc601' - Assemble for ARC 601. Alias: `-mARC601'. + 'arc601' + Assemble for ARC 601. Alias: '-mARC601'. - `arc601_norm' + 'arc601_norm' Assemble for ARC 601 with norm instructions. - `arc601_mul64' + 'arc601_mul64' Assemble for ARC 601 with mul64 instructions. - `arc601_mul32x16' + 'arc601_mul32x16' Assemble for ARC 601 with mul32x16 instructions. - `arc700' - Assemble for ARC 700. Aliases: `-mA7', `-mARC700'. + 'arc700' + Assemble for ARC 700. Aliases: '-mA7', '-mARC700'. - `arcem' - Assemble for ARC EM. Aliases: `-mEM' + 'arcem' + Assemble for ARC EM. Aliases: '-mEM' - `em' + 'em' Assemble for ARC EM, identical as arcem variant. - `em4' + 'em4' Assemble for ARC EM with code-density instructions. - `em4_dmips' + 'em4_dmips' Assemble for ARC EM with code-density instructions. - `em4_fpus' + 'em4_fpus' Assemble for ARC EM with code-density instructions. - `em4_fpuda' + 'em4_fpuda' Assemble for ARC EM with code-density, and double-precision assist instructions. - `quarkse_em' + 'quarkse_em' Assemble for QuarkSE-EM cpu. - `archs' - Assemble for ARC HS. Aliases: `-mHS', `-mav2hs'. + 'archs' + Assemble for ARC HS. Aliases: '-mHS', '-mav2hs'. - `hs' + 'hs' Assemble for ARC HS. - `hs34' + 'hs34' Assemble for ARC HS34. - `hs38' + 'hs38' Assemble for ARC HS38. - `hs38_linux' + 'hs38_linux' Assemble for ARC HS38 with floating point support on. - `nps400' + 'nps400' Assemble for ARC 700 with NPS-400 extended instructions. - - Note: the `.cpu' directive (*note ARC Directives::) can to be used + Note: the '.cpu' directive (*note ARC Directives::) can to be used to select a core variant from within assembly code. -`-EB' +'-EB' This option specifies that the output generated by the assembler should be marked as being encoded for a big-endian processor. -`-EL' +'-EL' This option specifies that the output generated by the assembler should be marked as being encoded for a little-endian processor - this is the default. -`-mcode-density' - This option turns on Code Density instructions. Only valid for - ARC EM processors. +'-mcode-density' + This option turns on Code Density instructions. Only valid for ARC + EM processors. -`-mrelax' +'-mrelax' Enable support for assembly-time relaxation. The assembler will replace a longer version of an instruction with a shorter one, whenever it is possible. -`-mnps400' +'-mnps400' Enable support for NPS-400 extended instructions. -`-mspfp' +'-mspfp' Enable support for single-precision floating point instructions. -`-mdpfp' +'-mdpfp' Enable support for double-precision floating point instructions. -`-mfpuda' +'-mfpuda' Enable support for double-precision assist floating point instructions. Only valid for ARC EM processors. -  File: as.info, Node: ARC Syntax, Next: ARC Directives, Prev: ARC Options, Up: ARC-Dependent @@ -7066,35 +6859,34 @@ 9.3.2.1 Special Characters .......................... -`%' - A register name can optionally be prefixed by a `%' character. So - register `%r0' is equivalent to `r0' in the assembly code. - -`#' - The presence of a `#' character within a line (but not at the - start of a line) indicates the start of a comment that extends to - the end of the current line. - - _Note:_ if a line starts with a `#' character then it can also be - a logical line number directive (*note Comments::) or a - preprocessor control command (*note Preprocessing::). +'%' + A register name can optionally be prefixed by a '%' character. So + register '%r0' is equivalent to 'r0' in the assembly code. + +'#' + The presence of a '#' character within a line (but not at the start + of a line) indicates the start of a comment that extends to the end + of the current line. + + _Note:_ if a line starts with a '#' character then it can also be a + logical line number directive (*note Comments::) or a preprocessor + control command (*note Preprocessing::). -`@' - Prefixing an operand with an `@' specifies that the operand is a +'@' + Prefixing an operand with an '@' specifies that the operand is a symbol and not a register. This is how the assembler disambiguates the use of an ARC register name as a symbol. So the instruction mov r0, @r0 - moves the address of symbol `r0' into register `r0'. + moves the address of symbol 'r0' into register 'r0'. -``' - The ``' (backtick) character is used to separate statements on a +'`' + The '`' (backtick) character is used to separate statements on a single line. -`-' +'-' Used as a separator to obtain a sequence of commands from a C preprocessor macro. -  File: as.info, Node: ARC-Regs, Prev: ARC-Chars, Up: ARC Syntax @@ -7104,102 +6896,100 @@ The ARC assembler uses the following register names for its core registers: -`r0-r31' - The core general registers. Registers `r26' through `r31' have +'r0-r31' + The core general registers. Registers 'r26' through 'r31' have special functions, and are usually referred to by those synonyms. -`gp' - The global pointer and a synonym for `r26'. +'gp' + The global pointer and a synonym for 'r26'. -`fp' - The frame pointer and a synonym for `r27'. +'fp' + The frame pointer and a synonym for 'r27'. -`sp' - The stack pointer and a synonym for `r28'. +'sp' + The stack pointer and a synonym for 'r28'. -`ilink1' +'ilink1' For ARC 600 and ARC 700, the level 1 interrupt link register and a - synonym for `r29'. Not supported for ARCv2. + synonym for 'r29'. Not supported for ARCv2. -`ilink' - For ARCv2, the interrupt link register and a synonym for `r29'. +'ilink' + For ARCv2, the interrupt link register and a synonym for 'r29'. Not supported for ARC 600 and ARC 700. -`ilink2' +'ilink2' For ARC 600 and ARC 700, the level 2 interrupt link register and a - synonym for `r30'. Not supported for ARC v2. + synonym for 'r30'. Not supported for ARC v2. -`blink' - The link register and a synonym for `r31'. +'blink' + The link register and a synonym for 'r31'. -`r32-r59' +'r32-r59' The extension core registers. -`lp_count' +'lp_count' The loop count register. -`pcl' +'pcl' The word aligned program counter. - In addition the ARC processor has a large number of _auxiliary registers_. The precise set depends on the extensions being supported, but the following baseline set are always defined: -`identity' +'identity' Processor Identification register. Auxiliary register address 0x4. -`pc' +'pc' Program Counter. Auxiliary register address 0x6. -`status32' +'status32' Status register. Auxiliary register address 0x0a. -`bta' +'bta' Branch Target Address. Auxiliary register address 0x412. -`ecr' +'ecr' Exception Cause Register. Auxiliary register address 0x403. -`int_vector_base' +'int_vector_base' Interrupt Vector Base address. Auxiliary register address 0x25. -`status32_p0' +'status32_p0' Stored STATUS32 register on entry to level P0 interrupts. Auxiliary register address 0xb. -`aux_user_sp' +'aux_user_sp' Saved User Stack Pointer. Auxiliary register address 0xd. -`eret' +'eret' Exception Return Address. Auxiliary register address 0x400. -`erbta' +'erbta' BTA saved on exception entry. Auxiliary register address 0x401. -`erstatus' +'erstatus' STATUS32 saved on exception. Auxiliary register address 0x402. -`bcr_ver' +'bcr_ver' Build Configuration Registers Version. Auxiliary register address 0x60. -`bta_link_build' - Build configuration for: BTA Registers. Auxiliary register - address 0x63. +'bta_link_build' + Build configuration for: BTA Registers. Auxiliary register address + 0x63. -`vecbase_ac_build' +'vecbase_ac_build' Build configuration for: Interrupts. Auxiliary register address 0x68. -`rf_build' +'rf_build' Build configuration for: Core Registers. Auxiliary register address 0x6e. -`dccm_build' +'dccm_build' DCCM RAM Configuration Register. Auxiliary register address 0xc1. - Additional auxiliary register names are defined according to the processor architecture version and extensions selected by the options. @@ -7209,128 +6999,126 @@ 9.3.3 ARC Machine Directives ---------------------------- -The ARC version of `as' supports the following additional machine +The ARC version of 'as' supports the following additional machine directives: -`.lcomm SYMBOL, LENGTH[, ALIGNMENT]' +'.lcomm SYMBOL, LENGTH[, ALIGNMENT]' Reserve LENGTH (an absolute expression) bytes for a local common denoted by SYMBOL. The section and value of SYMBOL are those of the new local common. The addresses are allocated in the bss section, so that at run-time the bytes start off zeroed. Since - SYMBOL is not declared global, it is normally not visible to `ld'. + SYMBOL is not declared global, it is normally not visible to 'ld'. The optional third parameter, ALIGNMENT, specifies the desired alignment of the symbol in the bss section, specified as a byte boundary (for example, an alignment of 16 means that the least significant 4 bits of the address should be zero). The alignment must be an absolute expression, and it must be a power of two. If - no alignment is specified, as will set the alignment to the - largest power of two less than or equal to the size of the symbol, - up to a maximum of 16. + no alignment is specified, as will set the alignment to the largest + power of two less than or equal to the size of the symbol, up to a + maximum of 16. -`.lcommon SYMBOL, LENGTH[, ALIGNMENT]' - The same as `lcomm' directive. +'.lcommon SYMBOL, LENGTH[, ALIGNMENT]' + The same as 'lcomm' directive. -`.cpu CPU' - The `.cpu' directive must be followed by the desired core version. +'.cpu CPU' + The '.cpu' directive must be followed by the desired core version. Permitted values for CPU are: - `ARC600' + 'ARC600' Assemble for the ARC600 instruction set. - `arc600_norm' + 'arc600_norm' Assemble for ARC 600 with norm instructions. - `arc600_mul64' + 'arc600_mul64' Assemble for ARC 600 with mul64 instructions. - `arc600_mul32x16' + 'arc600_mul32x16' Assemble for ARC 600 with mul32x16 instructions. - `arc601' + 'arc601' Assemble for ARC 601 instruction set. - `arc601_norm' + 'arc601_norm' Assemble for ARC 601 with norm instructions. - `arc601_mul64' + 'arc601_mul64' Assemble for ARC 601 with mul64 instructions. - `arc601_mul32x16' + 'arc601_mul32x16' Assemble for ARC 601 with mul32x16 instructions. - `ARC700' + 'ARC700' Assemble for the ARC700 instruction set. - `NPS400' + 'NPS400' Assemble for the NPS400 instruction set. - `EM' + 'EM' Assemble for the ARC EM instruction set. - `arcem' + 'arcem' Assemble for ARC EM instruction set - `em4' + 'em4' Assemble for ARC EM with code-density instructions. - `em4_dmips' + 'em4_dmips' Assemble for ARC EM with code-density instructions. - `em4_fpus' + 'em4_fpus' Assemble for ARC EM with code-density instructions. - `em4_fpuda' + 'em4_fpuda' Assemble for ARC EM with code-density, and double-precision assist instructions. - `quarkse_em' + 'quarkse_em' Assemble for QuarkSE-EM instruction set. - `HS' + 'HS' Assemble for the ARC HS instruction set. - `archs' + 'archs' Assemble for ARC HS instruction set. - `hs' + 'hs' Assemble for ARC HS instruction set. - `hs34' + 'hs34' Assemble for ARC HS34 instruction set. - `hs38' + 'hs38' Assemble for ARC HS38 instruction set. - `hs38_linux' + 'hs38_linux' Assemble for ARC HS38 with floating point support on. - - Note: the `.cpu' directive overrides the command line option - `-mcpu=CPU'; a warning is emitted when the version is not + Note: the '.cpu' directive overrides the command line option + '-mcpu=CPU'; a warning is emitted when the version is not consistent between the two. -`.extAuxRegister NAME, ADDR, MODE' +'.extAuxRegister NAME, ADDR, MODE' Auxiliary registers can be defined in the assembler source code by using this directive. The first parameter, NAME, is the name of - the new auxiliary register. The second parameter, ADDR, is - address the of the auxiliary register. The third parameter, MODE, + the new auxiliary register. The second parameter, ADDR, is address + the of the auxiliary register. The third parameter, MODE, specifies whether the register is readable and/or writable and is one of: - `r' + 'r' Read only; - `w' + 'w' Write only; - `r|w' + 'r|w' Read and write. - For example: .extAuxRegister mulhi, 0x12, w specifies a write only extension auxiliary register, MULHI at address 0x12. -`.extCondCode SUFFIX, VAL' +'.extCondCode SUFFIX, VAL' ARC supports extensible condition codes. This directive defines a new condition code, to be known by the suffix, SUFFIX and will depend on the value, VAL in the condition code. @@ -7338,38 +7126,37 @@ For example: .extCondCode is_busy,0x14 add.is_busy r1,r2,r3 - will only execute the `add' instruction if the condition code - value is 0x14. + will only execute the 'add' instruction if the condition code value + is 0x14. -`.extCoreRegister NAME, REGNUM, MODE, SHORTCUT' +'.extCoreRegister NAME, REGNUM, MODE, SHORTCUT' Specifies an extension core register named NAME as a synonym for the register numbered REGNUM. The register number must be between 32 and 59. The third argument, MODE, indicates whether the register is readable and/or writable and is one of: - `r' + 'r' Read only; - `w' + 'w' Write only; - `r|w' + 'r|w' Read and write. - The final parameter, SHORTCUT indicates whether the register has a short cut in the pipeline. The valid values are: - `can_shortcut' + 'can_shortcut' The register has a short cut in the pipeline; - `cannot_shortcut' + 'cannot_shortcut' The register does not have a short cut in the pipeline. For example: .extCoreRegister mlo, 57, r , can_shortcut - defines a read only extension core register, `mlo', which is + defines a read only extension core register, 'mlo', which is register 57, and can short cut the pipeline. -`.extInstruction NAME, OPCODE, SUBOPCODE, SUFFIXCLASS, SYNTAXCLASS' +'.extInstruction NAME, OPCODE, SUBOPCODE, SUFFIXCLASS, SYNTAXCLASS' ARC allows the user to specify extension instructions. These extension instructions are not macros; the assembler creates encodings for use of these instructions according to the @@ -7385,45 +7172,45 @@ The fourth argument, SUFFIXCLASS, determines the kinds of suffixes to be allowed. Valid values are: - `SUFFIX_NONE' + 'SUFFIX_NONE' No suffixes are permitted; - `SUFFIX_COND' + 'SUFFIX_COND' Conditional suffixes are permitted; - `SUFFIX_FLAG' + 'SUFFIX_FLAG' Flag setting suffixes are permitted. - `SUFFIX_COND|SUFFIX_FLAG' + 'SUFFIX_COND|SUFFIX_FLAG' Both conditional and flag setting suffices are permitted. - The fifth and final argument, SYNTAXCLASS, determines the syntax class for the instruction. It can have the following values: - `SYNTAX_2OP' + 'SYNTAX_2OP' Two Operand Instruction; - `SYNTAX_3OP' + 'SYNTAX_3OP' Three Operand Instruction. - `SYNTAX_1OP' + 'SYNTAX_1OP' One Operand Instruction. - `SYNTAX_NOP' + 'SYNTAX_NOP' No Operand Instruction. - The syntax class may be followed by `|' and one of the following + The syntax class may be followed by '|' and one of the following modifiers. - `OP1_MUST_BE_IMM' - Modifies syntax class `SYNTAX_3OP', specifying that the first + + 'OP1_MUST_BE_IMM' + Modifies syntax class 'SYNTAX_3OP', specifying that the first operand of a three-operand instruction must be an immediate (i.e., the result is discarded). This is usually used to set the flags using specific instructions and not retain results. - `OP1_IMM_IMPLIED' - Modifies syntax class `SYNTAX_20P', specifying that there is - an implied immediate destination operand which does not - appear in the syntax. + 'OP1_IMM_IMPLIED' + Modifies syntax class 'SYNTAX_20P', specifying that there is + an implied immediate destination operand which does not appear + in the syntax. For example, if the source code contains an instruction like: inst r1,r2 @@ -7431,13 +7218,12 @@ result is discarded). This is the same as though the source code were: inst 0,r1,r2. - For example, defining a 64-bit multiplier with immediate operands: .extInstruction mp64, 0x07, 0x2d, SUFFIX_COND|SUFFIX_FLAG, SYNTAX_3OP|OP1_MUST_BE_IMM - which specifies an extension instruction named `mp64' with 3 + which specifies an extension instruction named 'mp64' with 3 operands. It sets the flags and can be used with a condition code, - for which the first operand is an immediate, i.e. equivalent to + for which the first operand is an immediate, i.e. equivalent to discarding the result of the operation. A two operands instruction variant would be: @@ -7447,7 +7233,6 @@ immediate operand. The result of this operation would be discarded. -  File: as.info, Node: ARC Modifiers, Next: ARC Symbols, Prev: ARC Directives, Up: ARC-Dependent @@ -7459,27 +7244,26 @@ ARC 700 and above processors and generate relocation entries, which are interpreted by the linker as follows: -`@pcl(SYMBOL)' +'@pcl(SYMBOL)' Relative distance of SYMBOL's from the current program counter location. -`@gotpc(SYMBOL)' +'@gotpc(SYMBOL)' Relative distance of SYMBOL's Global Offset Table entry from the current program counter location. -`@gotoff(SYMBOL)' +'@gotoff(SYMBOL)' Distance of SYMBOL from the base of the Global Offset Table. -`@plt(SYMBOL)' - Distance of SYMBOL's Procedure Linkage Table entry from the - current program counter. This is valid only with branch and link +'@plt(SYMBOL)' + Distance of SYMBOL's Procedure Linkage Table entry from the current + program counter. This is valid only with branch and link instructions and PC-relative calls. -`@sda(SYMBOL)' +'@sda(SYMBOL)' Relative distance of SYMBOL from the base of the Small Data Pointer. -  File: as.info, Node: ARC Symbols, Next: ARC Opcodes, Prev: ARC Modifiers, Up: ARC-Dependent @@ -7490,14 +7274,12 @@ position-independent code. These symbols are available only with the ARC 700 and above processors. -`__GLOBAL_OFFSET_TABLE__' +'__GLOBAL_OFFSET_TABLE__' Symbol referring to the base of the Global Offset Table. -`__DYNAMIC__' - An alias for the Global Offset Table - `Base__GLOBAL_OFFSET_TABLE__'. It can be used only with `@gotpc' - modifiers. - +'__DYNAMIC__' + An alias for the Global Offset Table 'Base__GLOBAL_OFFSET_TABLE__'. + It can be used only with '@gotpc' modifiers.  File: as.info, Node: ARC Opcodes, Prev: ARC Symbols, Up: ARC-Dependent @@ -7505,7 +7287,7 @@ 9.3.6 Opcodes ------------- -For information on the ARC instruction set, see `ARC Programmers +For information on the ARC instruction set, see 'ARC Programmers Reference Manual', available where you download the processor IP library. @@ -7531,106 +7313,107 @@ 9.4.1 Options ------------- -`-mcpu=PROCESSOR[+EXTENSION...]' +'-mcpu=PROCESSOR[+EXTENSION...]' This option specifies the target processor. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target processor. The - following processor names are recognized: `arm1', `arm2', `arm250', - `arm3', `arm6', `arm60', `arm600', `arm610', `arm620', `arm7', - `arm7m', `arm7d', `arm7dm', `arm7di', `arm7dmi', `arm70', `arm700', - `arm700i', `arm710', `arm710t', `arm720', `arm720t', `arm740t', - `arm710c', `arm7100', `arm7500', `arm7500fe', `arm7t', `arm7tdmi', - `arm7tdmi-s', `arm8', `arm810', `strongarm', `strongarm1', - `strongarm110', `strongarm1100', `strongarm1110', `arm9', `arm920', - `arm920t', `arm922t', `arm940t', `arm9tdmi', `fa526' (Faraday - FA526 processor), `fa626' (Faraday FA626 processor), `arm9e', - `arm926e', `arm926ej-s', `arm946e-r0', `arm946e', `arm946e-s', - `arm966e-r0', `arm966e', `arm966e-s', `arm968e-s', `arm10t', - `arm10tdmi', `arm10e', `arm1020', `arm1020t', `arm1020e', - `arm1022e', `arm1026ej-s', `fa606te' (Faraday FA606TE processor), - `fa616te' (Faraday FA616TE processor), `fa626te' (Faraday FA626TE - processor), `fmp626' (Faraday FMP626 processor), `fa726te' - (Faraday FA726TE processor), `arm1136j-s', `arm1136jf-s', - `arm1156t2-s', `arm1156t2f-s', `arm1176jz-s', `arm1176jzf-s', - `mpcore', `mpcorenovfp', `cortex-a5', `cortex-a7', `cortex-a8', - `cortex-a9', `cortex-a15', `cortex-a17', `cortex-a32', - `cortex-a35', `cortex-a53', `cortex-a57', `cortex-a72', - `cortex-a73', `cortex-r4', `cortex-r4f', `cortex-r5', `cortex-r7', - `cortex-r8', `cortex-m33', `cortex-m23', `cortex-m7', `cortex-m4', - `cortex-m3', `cortex-m1', `cortex-m0', `cortex-m0plus', - `exynos-m1', `marvell-pj4', `marvell-whitney', `falkor', `qdf24xx', - `xgene1', `xgene2', `ep9312' (ARM920 with Cirrus Maverick - coprocessor), `i80200' (Intel XScale processor) `iwmmxt' (Intel(r) - XScale processor with Wireless MMX(tm) technology coprocessor) and - `xscale'. The special name `all' may be used to allow the + following processor names are recognized: 'arm1', 'arm2', 'arm250', + 'arm3', 'arm6', 'arm60', 'arm600', 'arm610', 'arm620', 'arm7', + 'arm7m', 'arm7d', 'arm7dm', 'arm7di', 'arm7dmi', 'arm70', 'arm700', + 'arm700i', 'arm710', 'arm710t', 'arm720', 'arm720t', 'arm740t', + 'arm710c', 'arm7100', 'arm7500', 'arm7500fe', 'arm7t', 'arm7tdmi', + 'arm7tdmi-s', 'arm8', 'arm810', 'strongarm', 'strongarm1', + 'strongarm110', 'strongarm1100', 'strongarm1110', 'arm9', 'arm920', + 'arm920t', 'arm922t', 'arm940t', 'arm9tdmi', 'fa526' (Faraday FA526 + processor), 'fa626' (Faraday FA626 processor), 'arm9e', 'arm926e', + 'arm926ej-s', 'arm946e-r0', 'arm946e', 'arm946e-s', 'arm966e-r0', + 'arm966e', 'arm966e-s', 'arm968e-s', 'arm10t', 'arm10tdmi', + 'arm10e', 'arm1020', 'arm1020t', 'arm1020e', 'arm1022e', + 'arm1026ej-s', 'fa606te' (Faraday FA606TE processor), 'fa616te' + (Faraday FA616TE processor), 'fa626te' (Faraday FA626TE processor), + 'fmp626' (Faraday FMP626 processor), 'fa726te' (Faraday FA726TE + processor), 'arm1136j-s', 'arm1136jf-s', 'arm1156t2-s', + 'arm1156t2f-s', 'arm1176jz-s', 'arm1176jzf-s', 'mpcore', + 'mpcorenovfp', 'cortex-a5', 'cortex-a7', 'cortex-a8', 'cortex-a9', + 'cortex-a15', 'cortex-a17', 'cortex-a32', 'cortex-a35', + 'cortex-a53', 'cortex-a57', 'cortex-a72', 'cortex-a73', + 'cortex-r4', 'cortex-r4f', 'cortex-r5', 'cortex-r7', 'cortex-r8', + 'cortex-m33', 'cortex-m23', 'cortex-m7', 'cortex-m4', 'cortex-m3', + 'cortex-m1', 'cortex-m0', 'cortex-m0plus', 'exynos-m1', + 'marvell-pj4', 'marvell-whitney', 'falkor', 'qdf24xx', 'xgene1', + 'xgene2', 'ep9312' (ARM920 with Cirrus Maverick coprocessor), + 'i80200' (Intel XScale processor) 'iwmmxt' (Intel(r) XScale + processor with Wireless MMX(tm) technology coprocessor) and + 'xscale'. The special name 'all' may be used to allow the assembler to accept instructions valid for any ARM processor. - In addition to the basic instruction set, the assembler can be - told to accept various extension mnemonics that extend the - processor using the co-processor instruction space. For example, - `-mcpu=arm920+maverick' is equivalent to specifying `-mcpu=ep9312'. + In addition to the basic instruction set, the assembler can be told + to accept various extension mnemonics that extend the processor + using the co-processor instruction space. For example, + '-mcpu=arm920+maverick' is equivalent to specifying '-mcpu=ep9312'. - Multiple extensions may be specified, separated by a `+'. The + Multiple extensions may be specified, separated by a '+'. The extensions should be specified in ascending alphabetical order. - Some extensions may be restricted to particular architectures; - this is documented in the list of extensions below. + Some extensions may be restricted to particular architectures; this + is documented in the list of extensions below. Extension mnemonics may also be removed from those the assembler - accepts. This is done be prepending `no' to the option that adds + accepts. This is done be prepending 'no' to the option that adds the extension. Extensions that are removed should be listed after all extensions which have been added, again in ascending - alphabetical order. For example, `-mcpu=ep9312+nomaverick' is - equivalent to specifying `-mcpu=arm920'. + alphabetical order. For example, '-mcpu=ep9312+nomaverick' is + equivalent to specifying '-mcpu=arm920'. - The following extensions are currently supported: `crc' `crypto' - (Cryptography Extensions for v8-A architecture, implies `fp+simd'), - `fp' (Floating Point Extensions for v8-A architecture), `idiv' + The following extensions are currently supported: 'crc' 'crypto' + (Cryptography Extensions for v8-A architecture, implies 'fp+simd'), + 'fp' (Floating Point Extensions for v8-A architecture), 'idiv' (Integer Divide Extensions for v7-A and v7-R architectures), - `iwmmxt', `iwmmxt2', `xscale', `maverick', `mp' (Multiprocessing - Extensions for v7-A and v7-R architectures), `os' (Operating - System for v6M architecture), `sec' (Security Extensions for v6K - and v7-A architectures), `simd' (Advanced SIMD Extensions for v8-A - architecture, implies `fp'), `virt' (Virtualization Extensions for - v7-A architecture, implies `idiv'), `pan' (Priviliged Access Never - Extensions for v8-A architecture), `ras' (Reliability, - Availability and Serviceability extensions for v8-A architecture), - `rdma' (ARMv8.1 Advanced SIMD extensions for v8-A architecture, - implies `simd') and `xscale'. + 'iwmmxt', 'iwmmxt2', 'xscale', 'maverick', 'mp' (Multiprocessing + Extensions for v7-A and v7-R architectures), 'os' (Operating System + for v6M architecture), 'sec' (Security Extensions for v6K and v7-A + architectures), 'simd' (Advanced SIMD Extensions for v8-A + architecture, implies 'fp'), 'virt' (Virtualization Extensions for + v7-A architecture, implies 'idiv'), 'pan' (Priviliged Access Never + Extensions for v8-A architecture), 'ras' (Reliability, Availability + and Serviceability extensions for v8-A architecture), 'rdma' + (ARMv8.1 Advanced SIMD extensions for v8-A architecture, implies + 'simd') and 'xscale'. -`-march=ARCHITECTURE[+EXTENSION...]' +'-march=ARCHITECTURE[+EXTENSION...]' This option specifies the target architecture. The assembler will issue an error message if an attempt is made to assemble an - instruction which will not execute on the target architecture. - The following architecture names are recognized: `armv1', `armv2', - `armv2a', `armv2s', `armv3', `armv3m', `armv4', `armv4xm', - `armv4t', `armv4txm', `armv5', `armv5t', `armv5txm', `armv5te', - `armv5texp', `armv6', `armv6j', `armv6k', `armv6z', `armv6kz', - `armv6-m', `armv6s-m', `armv7', `armv7-a', `armv7ve', `armv7-r', - `armv7-m', `armv7e-m', `armv8-a', `armv8.1-a', `armv8.2-a', - `armv8.3-a', `iwmmxt' `iwmmxt2' and `xscale'. If both `-mcpu' and - `-march' are specified, the assembler will use the setting for - `-mcpu'. + instruction which will not execute on the target architecture. The + following architecture names are recognized: 'armv1', 'armv2', + 'armv2a', 'armv2s', 'armv3', 'armv3m', 'armv4', 'armv4xm', + 'armv4t', 'armv4txm', 'armv5', 'armv5t', 'armv5txm', 'armv5te', + 'armv5texp', 'armv6', 'armv6j', 'armv6k', 'armv6z', 'armv6kz', + 'armv6-m', 'armv6s-m', 'armv7', 'armv7-a', 'armv7ve', 'armv7-r', + 'armv7-m', 'armv7e-m', 'armv8-a', 'armv8.1-a', 'armv8.2-a', + 'armv8.3-a', 'iwmmxt' 'iwmmxt2' and 'xscale'. If both '-mcpu' and + '-march' are specified, the assembler will use the setting for + '-mcpu'. The architecture option can be extended with the same instruction - set extension options as the `-mcpu' option. + set extension options as the '-mcpu' option. + +'-mfpu=FLOATING-POINT-FORMAT' -`-mfpu=FLOATING-POINT-FORMAT' This option specifies the floating point format to assemble for. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target floating point unit. The following format options are recognized: - `softfpa', `fpe', `fpe2', `fpe3', `fpa', `fpa10', `fpa11', - `arm7500fe', `softvfp', `softvfp+vfp', `vfp', `vfp10', `vfp10-r0', - `vfp9', `vfpxd', `vfpv2', `vfpv3', `vfpv3-fp16', `vfpv3-d16', - `vfpv3-d16-fp16', `vfpv3xd', `vfpv3xd-d16', `vfpv4', `vfpv4-d16', - `fpv4-sp-d16', `fpv5-sp-d16', `fpv5-d16', `fp-armv8', `arm1020t', - `arm1020e', `arm1136jf-s', `maverick', `neon', `neon-vfpv4', - `neon-fp-armv8', `crypto-neon-fp-armv8', `neon-fp-armv8.1' and - `crypto-neon-fp-armv8.1'. + 'softfpa', 'fpe', 'fpe2', 'fpe3', 'fpa', 'fpa10', 'fpa11', + 'arm7500fe', 'softvfp', 'softvfp+vfp', 'vfp', 'vfp10', 'vfp10-r0', + 'vfp9', 'vfpxd', 'vfpv2', 'vfpv3', 'vfpv3-fp16', 'vfpv3-d16', + 'vfpv3-d16-fp16', 'vfpv3xd', 'vfpv3xd-d16', 'vfpv4', 'vfpv4-d16', + 'fpv4-sp-d16', 'fpv5-sp-d16', 'fpv5-d16', 'fp-armv8', 'arm1020t', + 'arm1020e', 'arm1136jf-s', 'maverick', 'neon', 'neon-vfpv4', + 'neon-fp-armv8', 'crypto-neon-fp-armv8', 'neon-fp-armv8.1' and + 'crypto-neon-fp-armv8.1'. In addition to determining which instructions are assembled, this - option also affects the way in which the `.double' assembler + option also affects the way in which the '.double' assembler directive behaves when assembling little-endian code. The default is dependent on the processor selected. For @@ -7638,101 +7421,100 @@ instructions; for earlier architectures the default is to assemble for FPA instructions. -`-mthumb' +'-mthumb' This option specifies that the assembler should start assembling Thumb instructions; that is, it should behave as though the file - starts with a `.code 16' directive. + starts with a '.code 16' directive. -`-mthumb-interwork' +'-mthumb-interwork' This option specifies that the output generated by the assembler should be marked as supporting interworking. -`-mimplicit-it=never' -`-mimplicit-it=always' -`-mimplicit-it=arm' -`-mimplicit-it=thumb' - The `-mimplicit-it' option controls the behavior of the assembler - when conditional instructions are not enclosed in IT blocks. - There are four possible behaviors. If `never' is specified, such +'-mimplicit-it=never' +'-mimplicit-it=always' +'-mimplicit-it=arm' +'-mimplicit-it=thumb' + The '-mimplicit-it' option controls the behavior of the assembler + when conditional instructions are not enclosed in IT blocks. There + are four possible behaviors. If 'never' is specified, such constructs cause a warning in ARM code and an error in Thumb-2 - code. If `always' is specified, such constructs are accepted in + code. If 'always' is specified, such constructs are accepted in both ARM and Thumb-2 code, where the IT instruction is added - implicitly. If `arm' is specified, such constructs are accepted - in ARM code and cause an error in Thumb-2 code. If `thumb' is + implicitly. If 'arm' is specified, such constructs are accepted in + ARM code and cause an error in Thumb-2 code. If 'thumb' is specified, such constructs cause a warning in ARM code and are - accepted in Thumb-2 code. If you omit this option, the behavior - is equivalent to `-mimplicit-it=arm'. + accepted in Thumb-2 code. If you omit this option, the behavior is + equivalent to '-mimplicit-it=arm'. -`-mapcs-26' -`-mapcs-32' +'-mapcs-26' +'-mapcs-32' These options specify that the output generated by the assembler should be marked as supporting the indicated version of the Arm Procedure. Calling Standard. -`-matpcs' +'-matpcs' This option specifies that the output generated by the assembler should be marked as supporting the Arm/Thumb Procedure Calling Standard. If enabled this option will cause the assembler to create an empty debugging section in the object file called - .arm.atpcs. Debuggers can use this to determine the ABI being - used by. + .arm.atpcs. Debuggers can use this to determine the ABI being used + by. -`-mapcs-float' +'-mapcs-float' This indicates the floating point variant of the APCS should be used. In this variant floating point arguments are passed in FP registers rather than integer registers. -`-mapcs-reentrant' +'-mapcs-reentrant' This indicates that the reentrant variant of the APCS should be used. This variant supports position independent code. -`-mfloat-abi=ABI' +'-mfloat-abi=ABI' This option specifies that the output generated by the assembler - should be marked as using specified floating point ABI. The - following values are recognized: `soft', `softfp' and `hard'. + should be marked as using specified floating point ABI. The + following values are recognized: 'soft', 'softfp' and 'hard'. -`-meabi=VER' +'-meabi=VER' This option specifies which EABI version the produced object files - should conform to. The following values are recognized: `gnu', `4' - and `5'. + should conform to. The following values are recognized: 'gnu', '4' + and '5'. -`-EB' +'-EB' This option specifies that the output generated by the assembler should be marked as being encoded for a big-endian processor. Note: If a program is being built for a system with big-endian data and little-endian instructions then it should be assembled with the - `-EB' option, (all of it, code and data) and then linked with the - `--be8' option. This will reverse the endianness of the + '-EB' option, (all of it, code and data) and then linked with the + '--be8' option. This will reverse the endianness of the instructions back to little-endian, but leave the data as big-endian. -`-EL' +'-EL' This option specifies that the output generated by the assembler should be marked as being encoded for a little-endian processor. -`-k' +'-k' This option specifies that the output of the assembler should be marked as position-independent code (PIC). -`--fix-v4bx' - Allow `BX' instructions in ARMv4 code. This is intended for use +'--fix-v4bx' + Allow 'BX' instructions in ARMv4 code. This is intended for use with the linker option of the same name. -`-mwarn-deprecated' -`-mno-warn-deprecated' +'-mwarn-deprecated' +'-mno-warn-deprecated' Enable or disable warnings about using deprecated options or features. The default is to warn. -`-mccs' +'-mccs' Turns on CodeComposer Studio assembly syntax compatibility mode. -`-mwarn-syms' -`-mno-warn-syms' +'-mwarn-syms' +'-mno-warn-syms' Enable or disable warnings about symbols that match the names of ARM instructions. The default is to warn. -  File: as.info, Node: ARM Syntax, Next: ARM Floating Point, Prev: ARM Options, Up: ARM-Dependent @@ -7754,29 +7536,28 @@ .............................. Two slightly different syntaxes are support for ARM and THUMB -instructions. The default, `divided', uses the old style where ARM and -THUMB instructions had their own, separate syntaxes. The new, -`unified' syntax, which can be selected via the `.syntax' directive, -and has the following main features: +instructions. The default, 'divided', uses the old style where ARM and +THUMB instructions had their own, separate syntaxes. The new, 'unified' +syntax, which can be selected via the '.syntax' directive, and has the +following main features: - * Immediate operands do not require a `#' prefix. + * Immediate operands do not require a '#' prefix. - * The `IT' instruction may appear, and if it does it is validated + * The 'IT' instruction may appear, and if it does it is validated against subsequent conditional affixes. In ARM mode it does not generate machine code, in THUMB mode it does. * For ARM instructions the conditional affixes always appear at the - end of the instruction. For THUMB instructions conditional - affixes can be used, but only inside the scope of an `IT' - instruction. + end of the instruction. For THUMB instructions conditional affixes + can be used, but only inside the scope of an 'IT' instruction. * All of the instructions new to the V6T2 architecture (and later) are available. (Only a few such instructions can be written in the - `divided' syntax). + 'divided' syntax). - * The `.N' and `.W' suffixes are recognized and honored. + * The '.N' and '.W' suffixes are recognized and honored. - * All instructions set the flags if and only if they have an `s' + * All instructions set the flags if and only if they have an 's' affix.  @@ -7785,18 +7566,18 @@ 9.4.2.2 Special Characters .......................... -The presence of a `@' anywhere on a line indicates the start of a +The presence of a '@' anywhere on a line indicates the start of a comment that extends to the end of that line. - If a `#' appears as the first character of a line then the whole -line is treated as a comment, but in this case the line could also be a + If a '#' appears as the first character of a line then the whole line +is treated as a comment, but in this case the line could also be a logical line number directive (*note Comments::) or a preprocessor control command (*note Preprocessing::). - The `;' character can be used instead of a newline to separate + The ';' character can be used instead of a newline to separate statements. - Either `#' or `$' can be used to indicate immediate operands. + Either '#' or '$' can be used to indicate immediate operands. *TODO* Explain about /data modifier on symbols. @@ -7819,27 +7600,27 @@ .word foo(TARGET1) - This will generate an `R_ARM_TARGET1' relocation against the symbol -FOO. The following relocations are supported: `GOT', `GOTOFF', -`TARGET1', `TARGET2', `SBREL', `TLSGD', `TLSLDM', `TLSLDO', `TLSDESC', -`TLSCALL', `GOTTPOFF', `GOT_PREL' and `TPOFF'. + This will generate an 'R_ARM_TARGET1' relocation against the symbol +FOO. The following relocations are supported: 'GOT', 'GOTOFF', +'TARGET1', 'TARGET2', 'SBREL', 'TLSGD', 'TLSLDM', 'TLSLDO', 'TLSDESC', +'TLSCALL', 'GOTTPOFF', 'GOT_PREL' and 'TPOFF'. For compatibility with older toolchains the assembler also accepts -`(PLT)' after branch targets. On legacy targets this will generate the -deprecated `R_ARM_PLT32' relocation. On EABI targets it will encode -either the `R_ARM_CALL' or `R_ARM_JUMP24' relocation, as appropriate. - - Relocations for `MOVW' and `MOVT' instructions can be generated by -prefixing the value with `#:lower16:' and `#:upper16' respectively. -For example to load the 32-bit address of foo into r0: +'(PLT)' after branch targets. On legacy targets this will generate the +deprecated 'R_ARM_PLT32' relocation. On EABI targets it will encode +either the 'R_ARM_CALL' or 'R_ARM_JUMP24' relocation, as appropriate. + + Relocations for 'MOVW' and 'MOVT' instructions can be generated by +prefixing the value with '#:lower16:' and '#:upper16' respectively. For +example to load the 32-bit address of foo into r0: MOVW r0, #:lower16:foo MOVT r0, #:upper16:foo - Relocations `R_ARM_THM_ALU_ABS_G0_NC', `R_ARM_THM_ALU_ABS_G1_NC', -`R_ARM_THM_ALU_ABS_G2_NC' and `R_ARM_THM_ALU_ABS_G3_NC' can be -generated by prefixing the value with `#:lower0_7:#', `#:lower8_15:#', -`#:upper0_7:#' and `#:upper8_15:#' respectively. For example to load + Relocations 'R_ARM_THM_ALU_ABS_G0_NC', 'R_ARM_THM_ALU_ABS_G1_NC', +'R_ARM_THM_ALU_ABS_G2_NC' and 'R_ARM_THM_ALU_ABS_G3_NC' can be generated +by prefixing the value with '#:lower0_7:#', '#:lower8_15:#', +'#:upper0_7:#' and '#:upper8_15:#' respectively. For example to load the 32-bit address of foo into r0: MOVS r0, #:upper8_15:#foo @@ -7857,9 +7638,9 @@ ................................. Some NEON load/store instructions allow an optional address alignment -qualifier. The ARM documentation specifies that this is indicated by -`@ ALIGN'. However GAS already interprets the `@' character as a "line -comment" start, so `: ALIGN' is used instead. For example: +qualifier. The ARM documentation specifies that this is indicated by '@ +ALIGN'. However GAS already interprets the '@' character as a "line +comment" start, so ': ALIGN' is used instead. For example: vld1.8 {q0}, [r0, :128] @@ -7877,66 +7658,66 @@ 9.4.4 ARM Machine Directives ---------------------------- -`.2byte EXPRESSION [, EXPRESSION]*' -`.4byte EXPRESSION [, EXPRESSION]*' -`.8byte EXPRESSION [, EXPRESSION]*' +'.2byte EXPRESSION [, EXPRESSION]*' +'.4byte EXPRESSION [, EXPRESSION]*' +'.8byte EXPRESSION [, EXPRESSION]*' These directives write 2, 4 or 8 byte values to the output section. -`.align EXPRESSION [, EXPRESSION]' +'.align EXPRESSION [, EXPRESSION]' This is the generic .ALIGN directive. For the ARM however if the first argument is zero (ie no alignment is needed) the assembler will behave as if the argument had been 2 (ie pad to the next four byte boundary). This is for compatibility with ARM's own assembler. -`.arch NAME' - Select the target architecture. Valid values for NAME are the - same as for the `-march' commandline option. +'.arch NAME' + Select the target architecture. Valid values for NAME are the same + as for the '-march' commandline option. - Specifying `.arch' clears any previously selected architecture + Specifying '.arch' clears any previously selected architecture extensions. -`.arch_extension NAME' - Add or remove an architecture extension to the target - architecture. Valid values for NAME are the same as those - accepted as architectural extensions by the `-mcpu' commandline - option. +'.arch_extension NAME' + Add or remove an architecture extension to the target architecture. + Valid values for NAME are the same as those accepted as + architectural extensions by the '-mcpu' commandline option. - `.arch_extension' may be used multiple times to add or remove + '.arch_extension' may be used multiple times to add or remove extensions incrementally to the architecture being compiled for. -`.arm' +'.arm' This performs the same action as .CODE 32. -`.bss' - This directive switches to the `.bss' section. +'.bss' + This directive switches to the '.bss' section. -`.cantunwind' +'.cantunwind' Prevents unwinding through the current function. No personality routine or exception table data is required or permitted. -`.code `[16|32]'' - This directive selects the instruction set being generated. The +'.code [16|32]' + This directive selects the instruction set being generated. The value 16 selects Thumb, with the value 32 selecting ARM. -`.cpu NAME' +'.cpu NAME' Select the target processor. Valid values for NAME are the same as - for the `-mcpu' commandline option. + for the '-mcpu' commandline option. - Specifying `.cpu' clears any previously selected architecture + Specifying '.cpu' clears any previously selected architecture extensions. -`NAME .dn REGISTER NAME [.TYPE] [[INDEX]]' -`NAME .qn REGISTER NAME [.TYPE] [[INDEX]]' - The `dn' and `qn' directives are used to create typed and/or +'NAME .dn REGISTER NAME [.TYPE] [[INDEX]]' +'NAME .qn REGISTER NAME [.TYPE] [[INDEX]]' + + The 'dn' and 'qn' directives are used to create typed and/or indexed register aliases for use in Advanced SIMD Extension (Neon) instructions. The former should be used to create aliases of double-precision registers, and the latter to create aliases of quad-precision registers. - If these directives are used to create typed aliases, those - aliases can be used in Neon instructions instead of writing types - after the mnemonic or after each operand. For example: + If these directives are used to create typed aliases, those aliases + can be used in Neon instructions instead of writing types after the + mnemonic or after each operand. For example: x .dn d2.f32 y .dn d3.f32 @@ -7947,135 +7728,134 @@ vmul.f32 d2,d3,d4[1] - Aliases created using `dn' or `qn' can be destroyed using `unreq'. + Aliases created using 'dn' or 'qn' can be destroyed using 'unreq'. -`.eabi_attribute TAG, VALUE' +'.eabi_attribute TAG, VALUE' Set the EABI object attribute TAG to VALUE. The TAG is either an attribute number, or one of the following: - `Tag_CPU_raw_name', `Tag_CPU_name', `Tag_CPU_arch', - `Tag_CPU_arch_profile', `Tag_ARM_ISA_use', `Tag_THUMB_ISA_use', - `Tag_FP_arch', `Tag_WMMX_arch', `Tag_Advanced_SIMD_arch', - `Tag_PCS_config', `Tag_ABI_PCS_R9_use', `Tag_ABI_PCS_RW_data', - `Tag_ABI_PCS_RO_data', `Tag_ABI_PCS_GOT_use', - `Tag_ABI_PCS_wchar_t', `Tag_ABI_FP_rounding', - `Tag_ABI_FP_denormal', `Tag_ABI_FP_exceptions', - `Tag_ABI_FP_user_exceptions', `Tag_ABI_FP_number_model', - `Tag_ABI_align_needed', `Tag_ABI_align_preserved', - `Tag_ABI_enum_size', `Tag_ABI_HardFP_use', `Tag_ABI_VFP_args', - `Tag_ABI_WMMX_args', `Tag_ABI_optimization_goals', - `Tag_ABI_FP_optimization_goals', `Tag_compatibility', - `Tag_CPU_unaligned_access', `Tag_FP_HP_extension', - `Tag_ABI_FP_16bit_format', `Tag_MPextension_use', `Tag_DIV_use', - `Tag_nodefaults', `Tag_also_compatible_with', `Tag_conformance', - `Tag_T2EE_use', `Tag_Virtualization_use' + 'Tag_CPU_raw_name', 'Tag_CPU_name', 'Tag_CPU_arch', + 'Tag_CPU_arch_profile', 'Tag_ARM_ISA_use', 'Tag_THUMB_ISA_use', + 'Tag_FP_arch', 'Tag_WMMX_arch', 'Tag_Advanced_SIMD_arch', + 'Tag_PCS_config', 'Tag_ABI_PCS_R9_use', 'Tag_ABI_PCS_RW_data', + 'Tag_ABI_PCS_RO_data', 'Tag_ABI_PCS_GOT_use', + 'Tag_ABI_PCS_wchar_t', 'Tag_ABI_FP_rounding', + 'Tag_ABI_FP_denormal', 'Tag_ABI_FP_exceptions', + 'Tag_ABI_FP_user_exceptions', 'Tag_ABI_FP_number_model', + 'Tag_ABI_align_needed', 'Tag_ABI_align_preserved', + 'Tag_ABI_enum_size', 'Tag_ABI_HardFP_use', 'Tag_ABI_VFP_args', + 'Tag_ABI_WMMX_args', 'Tag_ABI_optimization_goals', + 'Tag_ABI_FP_optimization_goals', 'Tag_compatibility', + 'Tag_CPU_unaligned_access', 'Tag_FP_HP_extension', + 'Tag_ABI_FP_16bit_format', 'Tag_MPextension_use', 'Tag_DIV_use', + 'Tag_nodefaults', 'Tag_also_compatible_with', 'Tag_conformance', + 'Tag_T2EE_use', 'Tag_Virtualization_use' - The VALUE is either a `number', `"string"', or `number, "string"' + The VALUE is either a 'number', '"string"', or 'number, "string"' depending on the tag. Note - the following legacy values are also accepted by TAG: - `Tag_VFP_arch', `Tag_ABI_align8_needed', - `Tag_ABI_align8_preserved', `Tag_VFP_HP_extension', + 'Tag_VFP_arch', 'Tag_ABI_align8_needed', + 'Tag_ABI_align8_preserved', 'Tag_VFP_HP_extension', -`.even' +'.even' This directive aligns to an even-numbered address. -`.extend EXPRESSION [, EXPRESSION]*' -`.ldouble EXPRESSION [, EXPRESSION]*' +'.extend EXPRESSION [, EXPRESSION]*' +'.ldouble EXPRESSION [, EXPRESSION]*' These directives write 12byte long double floating-point values to the output section. These are not compatible with current ARM processors or ABIs. -`.fnend' - Marks the end of a function with an unwind table entry. The - unwind index table entry is created when this directive is - processed. +'.fnend' + Marks the end of a function with an unwind table entry. The unwind + index table entry is created when this directive is processed. If no personality routine has been specified then standard - personality routine 0 or 1 will be used, depending on the number - of unwind opcodes required. + personality routine 0 or 1 will be used, depending on the number of + unwind opcodes required. -`.fnstart' +'.fnstart' Marks the start of a function with an unwind table entry. -`.force_thumb' +'.force_thumb' This directive forces the selection of Thumb instructions, even if the target processor does not support those instructions -`.fpu NAME' +'.fpu NAME' Select the floating-point unit to assemble for. Valid values for - NAME are the same as for the `-mfpu' commandline option. + NAME are the same as for the '-mfpu' commandline option. -`.handlerdata' +'.handlerdata' Marks the end of the current function, and the start of the exception table entry for that function. Anything between this - directive and the `.fnend' directive will be added to the - exception table entry. + directive and the '.fnend' directive will be added to the exception + table entry. - Must be preceded by a `.personality' or `.personalityindex' + Must be preceded by a '.personality' or '.personalityindex' directive. -`.inst OPCODE [ , ... ]' -`.inst.n OPCODE [ , ... ]' -`.inst.w OPCODE [ , ... ]' +'.inst OPCODE [ , ... ]' +'.inst.n OPCODE [ , ... ]' +'.inst.w OPCODE [ , ... ]' Generates the instruction corresponding to the numerical value - OPCODE. `.inst.n' and `.inst.w' allow the Thumb instruction size + OPCODE. '.inst.n' and '.inst.w' allow the Thumb instruction size to be specified explicitly, overriding the normal encoding rules. -`.ldouble EXPRESSION [, EXPRESSION]*' - See `.extend'. +'.ldouble EXPRESSION [, EXPRESSION]*' + See '.extend'. -`.ltorg' +'.ltorg' This directive causes the current contents of the literal pool to be dumped into the current section (which is assumed to be the .text section) at the current location (aligned to a word - boundary). `GAS' maintains a separate literal pool for each - section and each sub-section. The `.ltorg' directive will only - affect the literal pool of the current section and sub-section. - At the end of assembly all remaining, un-empty literal pools will + boundary). 'GAS' maintains a separate literal pool for each + section and each sub-section. The '.ltorg' directive will only + affect the literal pool of the current section and sub-section. At + the end of assembly all remaining, un-empty literal pools will automatically be dumped. - Note - older versions of `GAS' would dump the current literal pool + Note - older versions of 'GAS' would dump the current literal pool any time a section change occurred. This is no longer done, since it prevents accurate control of the placement of literal pools. -`.movsp REG [, #OFFSET]' +'.movsp REG [, #OFFSET]' Tell the unwinder that REG contains an offset from the current stack pointer. If OFFSET is not specified then it is assumed to be zero. -`.object_arch NAME' +'.object_arch NAME' Override the architecture recorded in the EABI object attribute - section. Valid values for NAME are the same as for the `.arch' + section. Valid values for NAME are the same as for the '.arch' directive. Typically this is useful when code uses runtime detection of CPU features. -`.packed EXPRESSION [, EXPRESSION]*' +'.packed EXPRESSION [, EXPRESSION]*' This directive writes 12-byte packed floating-point values to the output section. These are not compatible with current ARM processors or ABIs. -`.pad #COUNT' +'.pad #COUNT' Generate unwinder annotations for a stack adjustment of COUNT bytes. A positive value indicates the function prologue allocated stack space by decrementing the stack pointer. -`.personality NAME' +'.personality NAME' Sets the personality routine for the current function to NAME. -`.personalityindex INDEX' +'.personalityindex INDEX' Sets the personality routine for the current function to the EABI standard routine number INDEX -`.pool' +'.pool' This is a synonym for .ltorg. -`NAME .req REGISTER NAME' +'NAME .req REGISTER NAME' This creates an alias for REGISTER NAME called NAME. For example: foo .req r0 -`.save REGLIST' +'.save REGLIST' Generate unwinder annotations to restore the registers in REGLIST. The format of REGLIST is the same as the corresponding store-multiple instruction. @@ -8099,13 +7879,13 @@ .save wr10 wstrd wr10, [sp, #-8]! -`.setfp FPREG, SPREG [, #OFFSET]' - Make all unwinder annotations relative to a frame pointer. - Without this the unwinder will use offsets from the stack pointer. +'.setfp FPREG, SPREG [, #OFFSET]' + Make all unwinder annotations relative to a frame pointer. Without + this the unwinder will use offsets from the stack pointer. - The syntax of this directive is the same as the `add' or `mov' + The syntax of this directive is the same as the 'add' or 'mov' instruction used to set the frame pointer. SPREG must be either - `sp' or mentioned in a previous `.movsp' directive. + 'sp' or mentioned in a previous '.movsp' directive. .movsp ip mov ip, sp @@ -8113,44 +7893,44 @@ .setfp fp, ip, #4 add fp, ip, #4 -`.secrel32 EXPRESSION [, EXPRESSION]*' +'.secrel32 EXPRESSION [, EXPRESSION]*' This directive emits relocations that evaluate to the section-relative offset of each expression's symbol. This directive is only supported for PE targets. -`.syntax [`unified' | `divided']' +'.syntax [unified | divided]' This directive sets the Instruction Set Syntax as described in the - *Note ARM-Instruction-Set:: section. + *note ARM-Instruction-Set:: section. -`.thumb' +'.thumb' This performs the same action as .CODE 16. -`.thumb_func' +'.thumb_func' This directive specifies that the following symbol is the name of a Thumb encoded function. This information is necessary in order to allow the assembler and linker to generate correct code for interworking between Arm and Thumb instructions and should be used - even if interworking is not going to be performed. The presence - of this directive also implies `.thumb' + even if interworking is not going to be performed. The presence of + this directive also implies '.thumb' This directive is not neccessary when generating EABI objects. On these targets the encoding is implicit when generating Thumb code. -`.thumb_set' - This performs the equivalent of a `.set' directive in that it - creates a symbol which is an alias for another symbol (possibly - not yet defined). This directive also has the added property in - that it marks the aliased symbol as being a thumb function entry - point, in the same way that the `.thumb_func' directive does. +'.thumb_set' + This performs the equivalent of a '.set' directive in that it + creates a symbol which is an alias for another symbol (possibly not + yet defined). This directive also has the added property in that + it marks the aliased symbol as being a thumb function entry point, + in the same way that the '.thumb_func' directive does. -`.tlsdescseq TLS-VARIABLE' +'.tlsdescseq TLS-VARIABLE' This directive is used to annotate parts of an inlined TLS descriptor trampoline. Normally the trampoline is provided by the linker, and this directive is not needed. -`.unreq ALIAS-NAME' +'.unreq ALIAS-NAME' This undefines a register alias which was previously defined using - the `req', `dn' or `qn' directives. For example: + the 'req', 'dn' or 'qn' directives. For example: foo .req r0 .unreq foo @@ -8159,18 +7939,18 @@ can be used to delete builtin in register name aliases (eg 'r0'). This should only be done if it is really necessary. -`.unwind_raw OFFSET, BYTE1, ...' - Insert one of more arbitary unwind opcode bytes, which are known - to adjust the stack pointer by OFFSET bytes. +'.unwind_raw OFFSET, BYTE1, ...' + Insert one of more arbitary unwind opcode bytes, which are known to + adjust the stack pointer by OFFSET bytes. - For example `.unwind_raw 4, 0xb1, 0x01' is equivalent to `.save + For example '.unwind_raw 4, 0xb1, 0x01' is equivalent to '.save {r0}' -`.vsave VFP-REGLIST' +'.vsave VFP-REGLIST' Generate unwinder annotations to restore the VFP registers in - VFP-REGLIST using FLDMD. Also works for VFPv3 registers that are - to be restored using VLDM. The format of VFP-REGLIST is the same - as the corresponding store-multiple instruction. + VFP-REGLIST using FLDMD. Also works for VFPv3 registers that are to + be restored using VLDM. The format of VFP-REGLIST is the same as + the corresponding store-multiple instruction. _VFP registers_ .vsave {d8, d9, d10} @@ -8180,36 +7960,35 @@ vstm sp!, {d15, d16, d17} Since FLDMX and FSTMX are now deprecated, this directive should be - used in favour of `.save' for saving VFP registers for ARMv6 and + used in favour of '.save' for saving VFP registers for ARMv6 and above. -  File: as.info, Node: ARM Opcodes, Next: ARM Mapping Symbols, Prev: ARM Directives, Up: ARM-Dependent 9.4.5 Opcodes ------------- -`as' implements all the standard ARM opcodes. It also implements +'as' implements all the standard ARM opcodes. It also implements several pseudo opcodes, including several synthetic load instructions. -`NOP' +'NOP' nop - This pseudo op will always evaluate to a legal ARM instruction - that does nothing. Currently it will evaluate to MOV r0, r0. + This pseudo op will always evaluate to a legal ARM instruction that + does nothing. Currently it will evaluate to MOV r0, r0. -`LDR' +'LDR' ldr , = If expression evaluates to a numeric constant then a MOV or MVN instruction will be used in place of the LDR instruction, if the constant can be generated by either of these instructions. - Otherwise the constant will be placed into the nearest literal - pool (if it not already there) and a PC relative LDR instruction - will be generated. + Otherwise the constant will be placed into the nearest literal pool + (if it not already there) and a PC relative LDR instruction will be + generated. -`ADR' +'ADR' adr