Fix bug #667, pull in latest Linaro binutils

Source:
https://android-build.linaro.org/builds/~linaro-android/toolchain64-4.9-2014.09/#build=3

Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>

201 files changed, 27279 insertions, 18726 deletions

diff --git a/aarch64-linux-android/bin/ar b/aarch64-linux-android/bin/ar
index 6c7efc0..6a21b55 100755
--- a/aarch64-linux-android/bin/ar
+++ b/aarch64-linux-android/bin/ar
diff --git a/aarch64-linux-android/bin/as b/aarch64-linux-android/bin/as
index 0f25a68..6e4315a 100755
--- a/aarch64-linux-android/bin/as
+++ b/aarch64-linux-android/bin/as
diff --git a/aarch64-linux-android/bin/ld b/aarch64-linux-android/bin/ld
index 2e81a89..acbf820 100755
--- a/aarch64-linux-android/bin/ld
+++ b/aarch64-linux-android/bin/ld
diff --git a/aarch64-linux-android/bin/ld.bfd b/aarch64-linux-android/bin/ld.bfd
index 2e81a89..acbf820 100755
--- a/aarch64-linux-android/bin/ld.bfd
+++ b/aarch64-linux-android/bin/ld.bfd
diff --git a/aarch64-linux-android/bin/nm b/aarch64-linux-android/bin/nm
index 0dc3682..799ba33 100755
--- a/aarch64-linux-android/bin/nm
+++ b/aarch64-linux-android/bin/nm
diff --git a/aarch64-linux-android/bin/objcopy b/aarch64-linux-android/bin/objcopy
index 82ed611..d6ad6e1 100755
--- a/aarch64-linux-android/bin/objcopy
+++ b/aarch64-linux-android/bin/objcopy
diff --git a/aarch64-linux-android/bin/objdump b/aarch64-linux-android/bin/objdump
index cdc798d..31517b7 100755
--- a/aarch64-linux-android/bin/objdump
+++ b/aarch64-linux-android/bin/objdump
diff --git a/aarch64-linux-android/bin/ranlib b/aarch64-linux-android/bin/ranlib
index 61b73df..1f58919 100755
--- a/aarch64-linux-android/bin/ranlib
+++ b/aarch64-linux-android/bin/ranlib
diff --git a/aarch64-linux-android/bin/strip b/aarch64-linux-android/bin/strip
index d8f7916..0a590b3 100755
--- a/aarch64-linux-android/bin/strip
+++ b/aarch64-linux-android/bin/strip
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.x b/aarch64-linux-android/lib/ldscripts/aarch64elf.x
index 77ac412..27dfe37 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.x
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.x
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xbn b/aarch64-linux-android/lib/ldscripts/aarch64elf.xbn
index 6f8471a..751c361 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xbn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xbn
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xc b/aarch64-linux-android/lib/ldscripts/aarch64elf.xc
index bc233ed..2140fae 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xc
@@ -30,25 +30,23 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      *(.rela.iplt)
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -157,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -188,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -210,5 +208,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xn b/aarch64-linux-android/lib/ldscripts/aarch64elf.xn
index 6cb6bcc..fda3ef8 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xn
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xr b/aarch64-linux-android/lib/ldscripts/aarch64elf.xr
index 9e42555..071f8c9 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xr
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xr
@@ -30,10 +30,7 @@ SECTIONS
   .rela.dtors   0 : { *(.rela.dtors) }
   .rela.got     0 : { *(.rela.got) }
   .rela.bss     0 : { *(.rela.bss) }
-  .rela.iplt    0 :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
   .rela.plt     0 :
     {
       *(.rela.plt)
@@ -42,8 +39,7 @@ SECTIONS
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt          0 : { *(.plt) }
-  .iplt         0 : { *(.iplt) }
+  .plt          0 : { *(.plt) *(.iplt) }
   .text         0 :
   {
     *(.text .stub)
@@ -119,7 +115,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xs b/aarch64-linux-android/lib/ldscripts/aarch64elf.xs
index 4f75ee7..53d7e30 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xs
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xs
@@ -28,23 +28,20 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc     : { *(.rela.ifunc) }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -147,12 +144,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -178,7 +175,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -200,5 +197,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xsc b/aarch64-linux-android/lib/ldscripts/aarch64elf.xsc
index 29158e7..31e4b9b 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xsc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xsc
@@ -29,21 +29,21 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      *(.rela.iplt)
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -146,12 +146,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -177,7 +177,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -199,5 +199,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xsw b/aarch64-linux-android/lib/ldscripts/aarch64elf.xsw
index dd4be4e..56047fa 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xsw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xsw
@@ -29,21 +29,21 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      *(.rela.iplt)
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -145,12 +145,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -176,7 +176,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -198,5 +198,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xu b/aarch64-linux-android/lib/ldscripts/aarch64elf.xu
index ec511e9..e395fdf 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xu
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xu
@@ -30,10 +30,7 @@ SECTIONS
   .rela.dtors   0 : { *(.rela.dtors) }
   .rela.got     0 : { *(.rela.got) }
   .rela.bss     0 : { *(.rela.bss) }
-  .rela.iplt    0 :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
   .rela.plt     0 :
     {
       *(.rela.plt)
@@ -42,8 +39,7 @@ SECTIONS
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt          0 : { *(.plt) }
-  .iplt         0 : { *(.iplt) }
+  .plt          0 : { *(.plt) *(.iplt) }
   .text         0 :
   {
     *(.text .stub)
@@ -120,7 +116,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf.xw b/aarch64-linux-android/lib/ldscripts/aarch64elf.xw
index e9bd0c5..e66052e 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elf.xw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf.xw
@@ -30,25 +30,23 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      *(.rela.iplt)
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +185,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +207,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.x b/aarch64-linux-android/lib/ldscripts/aarch64elf32.x
new file mode 100644
index 0000000..f93f8bf
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.x
@@ -0,0 +1,210 @@
+/* Default linker script, for normal executables */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xbn b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xbn
new file mode 100644
index 0000000..1926b6e
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xbn
@@ -0,0 +1,210 @@
+/* Script for -N: mix text and data on same page; don't align data */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = .;
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xc b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xc
new file mode 100644
index 0000000..f56cd54
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xc
@@ -0,0 +1,212 @@
+/* Script for -z combreloc: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xn b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xn
new file mode 100644
index 0000000..0fdec47
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xn
@@ -0,0 +1,210 @@
+/* Script for -n: mix text and data on same page */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xr b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xr
new file mode 100644
index 0000000..a303c50
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xr
@@ -0,0 +1,139 @@
+/* Script for ld -r: link without relocation */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack        0 :
+  {
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xs b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xs
new file mode 100644
index 0000000..62426fa
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xs
@@ -0,0 +1,201 @@
+/* Script for ld --shared: link shared library */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsc b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsc
new file mode 100644
index 0000000..8ea7dfd
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsc
@@ -0,0 +1,203 @@
+/* Script for --shared -z combreloc: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsw b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsw
new file mode 100644
index 0000000..a7b2b25
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xsw
@@ -0,0 +1,202 @@
+/* Script for --shared -z combreloc -z now -z relro: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xu b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xu
new file mode 100644
index 0000000..5c44d0b
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xu
@@ -0,0 +1,140 @@
+/* Script for ld -Ur: link w/out relocation, do create constructors */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+    SORT(CONSTRUCTORS)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack        0 :
+  {
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32.xw b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xw
new file mode 100644
index 0000000..b5524ed
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32.xw
@@ -0,0 +1,211 @@
+/* Script for -z combreloc -z now -z relro: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.x b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.x
new file mode 100644
index 0000000..e211e53
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.x
@@ -0,0 +1,210 @@
+/* Default linker script, for normal executables */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xbn b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xbn
new file mode 100644
index 0000000..d0b5e2b
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xbn
@@ -0,0 +1,210 @@
+/* Script for -N: mix text and data on same page; don't align data */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = .;
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xc b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xc
new file mode 100644
index 0000000..02c0732
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xc
@@ -0,0 +1,212 @@
+/* Script for -z combreloc: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xn b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xn
new file mode 100644
index 0000000..dce1edb
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xn
@@ -0,0 +1,210 @@
+/* Script for -n: mix text and data on same page */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xr b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xr
new file mode 100644
index 0000000..ddc12df
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xr
@@ -0,0 +1,139 @@
+/* Script for ld -r: link without relocation */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack        0 :
+  {
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xs b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xs
new file mode 100644
index 0000000..dd07e14
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xs
@@ -0,0 +1,201 @@
+/* Script for ld --shared: link shared library */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsc b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsc
new file mode 100644
index 0000000..65a7214
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsc
@@ -0,0 +1,203 @@
+/* Script for --shared -z combreloc: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsw b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsw
new file mode 100644
index 0000000..46c2c67
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xsw
@@ -0,0 +1,202 @@
+/* Script for --shared -z combreloc -z now -z relro: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xu b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xu
new file mode 100644
index 0000000..8d037b1
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xu
@@ -0,0 +1,140 @@
+/* Script for ld -Ur: link w/out relocation, do create constructors */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+    SORT(CONSTRUCTORS)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack        0 :
+  {
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xw b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xw
new file mode 100644
index 0000000..00874ff
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elf32b.xw
@@ -0,0 +1,211 @@
+/* Script for -z combreloc -z now -z relro: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00400000)); . = SEGMENT_START("text-segment", 0x00400000);
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN(CONSTANT (MAXPAGESIZE)) + (. & (CONSTANT (MAXPAGESIZE) - 1));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  .data           :
+  {
+    __data_start = . ;
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+    .stack         0x80000 :
+  {
+    _stack = .;
+    *(.stack)
+  }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.x b/aarch64-linux-android/lib/ldscripts/aarch64elfb.x
index af0db0e..98280f2 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.x
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.x
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xbn b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xbn
index eab16c3..5329da1 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xbn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xbn
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xc b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xc
index 1ad38ea..92bb2a4 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xc
@@ -30,25 +30,23 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      *(.rela.iplt)
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -157,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -188,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -210,5 +208,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xn b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xn
index 8ecfdcd..f07af3d 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xn
@@ -29,25 +29,22 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
     {
+      *(.rela.plt)
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
-  .rela.plt       :
-    {
-      *(.rela.plt)
-    }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +206,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xr b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xr
index 18ecfad..3fd1e77 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xr
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xr
@@ -30,10 +30,7 @@ SECTIONS
   .rela.dtors   0 : { *(.rela.dtors) }
   .rela.got     0 : { *(.rela.got) }
   .rela.bss     0 : { *(.rela.bss) }
-  .rela.iplt    0 :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
   .rela.plt     0 :
     {
       *(.rela.plt)
@@ -42,8 +39,7 @@ SECTIONS
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt          0 : { *(.plt) }
-  .iplt         0 : { *(.iplt) }
+  .plt          0 : { *(.plt) *(.iplt) }
   .text         0 :
   {
     *(.text .stub)
@@ -119,7 +115,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xs b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xs
index 77c3488..a3b89a3 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xs
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xs
@@ -28,23 +28,20 @@ SECTIONS
   .rela.dtors     : { *(.rela.dtors) }
   .rela.got       : { *(.rela.got) }
   .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
-  .rela.iplt      :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc     : { *(.rela.ifunc) }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -147,12 +144,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -178,7 +175,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -200,5 +197,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsc b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsc
index a47c679..84b17dd 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsc
@@ -29,21 +29,21 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      *(.rela.iplt)
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -146,12 +146,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -177,7 +177,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -199,5 +199,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsw b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsw
index a87895d..25cdbda 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xsw
@@ -29,21 +29,21 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      *(.rela.iplt)
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      *(.rela.iplt)
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -145,12 +145,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -176,7 +176,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -198,5 +198,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xu b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xu
index 473b1fb..97ef7a4 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xu
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xu
@@ -30,10 +30,7 @@ SECTIONS
   .rela.dtors   0 : { *(.rela.dtors) }
   .rela.got     0 : { *(.rela.got) }
   .rela.bss     0 : { *(.rela.bss) }
-  .rela.iplt    0 :
-    {
-      *(.rela.iplt)
-    }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
   .rela.plt     0 :
     {
       *(.rela.plt)
@@ -42,8 +39,7 @@ SECTIONS
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt          0 : { *(.plt) }
-  .iplt         0 : { *(.iplt) }
+  .plt          0 : { *(.plt) *(.iplt) }
   .text         0 :
   {
     *(.text .stub)
@@ -120,7 +116,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xw b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xw
index f0a1656..f6c5208 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64elfb.xw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64elfb.xw
@@ -30,25 +30,23 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      *(.rela.iplt)
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
+      *(.rela.ifunc)
     }
   .rela.plt       :
     {
       *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .init           :
   {
     KEEP (*(SORT_NONE(.init)))
   } =0
-  .plt            : { *(.plt) }
-  .iplt           : { *(.iplt) }
+  .plt            : { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -187,7 +185,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -209,5 +207,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.x b/aarch64-linux-android/lib/ldscripts/aarch64linux.x
index 888b5e1..2f82f0d 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.x
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.x
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xbn b/aarch64-linux-android/lib/ldscripts/aarch64linux.xbn
index 19ff1cc..0f83eec 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xbn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xbn
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -153,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -184,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -201,5 +201,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xc b/aarch64-linux-android/lib/ldscripts/aarch64linux.xc
index 7adc704..a7fd149 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xc
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +156,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -188,7 +188,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -205,5 +205,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xd b/aarch64-linux-android/lib/ldscripts/aarch64linux.xd
index 2dc6fe2..5187fdb 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xd
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xd
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xdc b/aarch64-linux-android/lib/ldscripts/aarch64linux.xdc
index b082c22..f12abd1 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xdc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xdc
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +156,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -188,7 +188,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -205,5 +205,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xdw b/aarch64-linux-android/lib/ldscripts/aarch64linux.xdw
index 78a8c47..8fb84f9 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xdw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xdw
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -155,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -187,7 +187,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -204,5 +204,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xn b/aarch64-linux-android/lib/ldscripts/aarch64linux.xn
index 63512b7..f101248 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xn
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xr b/aarch64-linux-android/lib/ldscripts/aarch64linux.xr
index c09b857..58bf7aa 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xr
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xr
@@ -115,7 +115,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xs b/aarch64-linux-android/lib/ldscripts/aarch64linux.xs
index 65f72bd..9b7ba12 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xs
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xs
@@ -41,7 +41,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -145,12 +145,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -177,7 +177,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -194,5 +194,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xsc b/aarch64-linux-android/lib/ldscripts/aarch64linux.xsc
index 793d5b1..d602b41 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xsc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xsc
@@ -43,7 +43,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -147,12 +147,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -179,7 +179,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -196,5 +196,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xsw b/aarch64-linux-android/lib/ldscripts/aarch64linux.xsw
index db4a79e..a4a6568 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xsw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xsw
@@ -43,7 +43,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -146,12 +146,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -178,7 +178,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -195,5 +195,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xu b/aarch64-linux-android/lib/ldscripts/aarch64linux.xu
index 03cbcf2..f508fa6 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xu
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xu
@@ -116,7 +116,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux.xw b/aarch64-linux-android/lib/ldscripts/aarch64linux.xw
index 84b8d0b..de8e029 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linux.xw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux.xw
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -155,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -187,7 +187,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -204,5 +204,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.x b/aarch64-linux-android/lib/ldscripts/aarch64linux32.x
new file mode 100644
index 0000000..2d21393
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.x
@@ -0,0 +1,207 @@
+/* Default linker script, for normal executables */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xbn b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xbn
new file mode 100644
index 0000000..9f8d39c
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xbn
@@ -0,0 +1,205 @@
+/* Script for -N: mix text and data on same page; don't align data */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = .;
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xc b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xc
new file mode 100644
index 0000000..501f8f4
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xc
@@ -0,0 +1,209 @@
+/* Script for -z combreloc: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xd b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xd
new file mode 100644
index 0000000..e6a8267
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xd
@@ -0,0 +1,207 @@
+/* Script for ld -pie: link position independent executable */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdc b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdc
new file mode 100644
index 0000000..88947c6
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdc
@@ -0,0 +1,209 @@
+/* Script for -pie -z combreloc: position independent executable, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdw b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdw
new file mode 100644
index 0000000..10a04b3
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xdw
@@ -0,0 +1,208 @@
+/* Script for -pie -z combreloc -z now -z relro: position independent executable, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xn b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xn
new file mode 100644
index 0000000..22da3a2
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xn
@@ -0,0 +1,207 @@
+/* Script for -n: mix text and data on same page */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xr b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xr
new file mode 100644
index 0000000..3971c6d
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xr
@@ -0,0 +1,135 @@
+/* Script for ld -r: link without relocation */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : ALIGN(16) { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xs b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xs
new file mode 100644
index 0000000..21d28ba
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xs
@@ -0,0 +1,198 @@
+/* Script for ld --shared: link shared library */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsc b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsc
new file mode 100644
index 0000000..e98697b
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsc
@@ -0,0 +1,200 @@
+/* Script for --shared -z combreloc: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsw b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsw
new file mode 100644
index 0000000..26bcd72
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xsw
@@ -0,0 +1,199 @@
+/* Script for --shared -z combreloc -z now -z relro: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xu b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xu
new file mode 100644
index 0000000..10b1a3e
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xu
@@ -0,0 +1,136 @@
+/* Script for ld -Ur: link w/out relocation, do create constructors */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : ALIGN(16) { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+    SORT(CONSTRUCTORS)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32.xw b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xw
new file mode 100644
index 0000000..f4acda3
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32.xw
@@ -0,0 +1,208 @@
+/* Script for -z combreloc -z now -z relro: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-littleaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.x b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.x
new file mode 100644
index 0000000..f77b937
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.x
@@ -0,0 +1,207 @@
+/* Default linker script, for normal executables */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xbn b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xbn
new file mode 100644
index 0000000..486c00a
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xbn
@@ -0,0 +1,205 @@
+/* Script for -N: mix text and data on same page; don't align data */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = .;
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xc b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xc
new file mode 100644
index 0000000..fedb824
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xc
@@ -0,0 +1,209 @@
+/* Script for -z combreloc: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xd b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xd
new file mode 100644
index 0000000..2c88bee
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xd
@@ -0,0 +1,207 @@
+/* Script for ld -pie: link position independent executable */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdc b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdc
new file mode 100644
index 0000000..63480a0
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdc
@@ -0,0 +1,209 @@
+/* Script for -pie -z combreloc: position independent executable, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdw b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdw
new file mode 100644
index 0000000..8dc876a
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xdw
@@ -0,0 +1,208 @@
+/* Script for -pie -z combreloc -z now -z relro: position independent executable, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0)); . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xn b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xn
new file mode 100644
index 0000000..f7ec359
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xn
@@ -0,0 +1,207 @@
+/* Script for -n: mix text and data on same page */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xr b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xr
new file mode 100644
index 0000000..260bb95
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xr
@@ -0,0 +1,135 @@
+/* Script for ld -r: link without relocation */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : ALIGN(16) { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xs b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xs
new file mode 100644
index 0000000..72de963
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xs
@@ -0,0 +1,198 @@
+/* Script for ld --shared: link shared library */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.init      : { *(.rela.init) }
+  .rela.text      : { *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*) }
+  .rela.fini      : { *(.rela.fini) }
+  .rela.rodata    : { *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*) }
+  .rela.data.rel.ro   : { *(.rela.data.rel.ro .rela.data.rel.ro.* .rela.gnu.linkonce.d.rel.ro.*) }
+  .rela.data      : { *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*) }
+  .rela.tdata	  : { *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*) }
+  .rela.tbss	  : { *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*) }
+  .rela.ctors     : { *(.rela.ctors) }
+  .rela.dtors     : { *(.rela.dtors) }
+  .rela.got       : { *(.rela.got) }
+  .rela.bss       : { *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*) }
+  .rela.ifunc     : { *(.rela.ifunc) }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsc b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsc
new file mode 100644
index 0000000..ffd3ae8
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsc
@@ -0,0 +1,200 @@
+/* Script for --shared -z combreloc: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (12, .);
+  .got.plt        : { *(.got.plt)  *(.igot.plt) }
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsw b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsw
new file mode 100644
index 0000000..e60482b
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xsw
@@ -0,0 +1,199 @@
+/* Script for --shared -z combreloc -z now -z relro: shared library, combine & sort relocs */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  . = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      *(.rela.iplt)
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .init_array     :
+  {
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+  }
+  .fini_array     :
+  {
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xu b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xu
new file mode 100644
index 0000000..31bf14c
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xu
@@ -0,0 +1,136 @@
+/* Script for ld -Ur: link w/out relocation, do create constructors */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ /* For some reason, the Solaris linker makes bad executables
+  if gld -r is used and the intermediate file has sections starting
+  at non-zero addresses.  Could be a Solaris ld bug, could be a GNU ld
+  bug.  But for now assigning the zero vmas works.  */
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  .interp       0 : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash         0 : { *(.hash) }
+  .gnu.hash     0 : { *(.gnu.hash) }
+  .dynsym       0 : { *(.dynsym) }
+  .dynstr       0 : { *(.dynstr) }
+  .gnu.version  0 : { *(.gnu.version) }
+  .gnu.version_d 0: { *(.gnu.version_d) }
+  .gnu.version_r 0: { *(.gnu.version_r) }
+  .rela.init    0 : { *(.rela.init) }
+  .rela.text    0 : { *(.rela.text) }
+  .rela.fini    0 : { *(.rela.fini) }
+  .rela.rodata  0 : { *(.rela.rodata) }
+  .rela.data.rel.ro 0 : { *(.rela.data.rel.ro) }
+  .rela.data    0 : { *(.rela.data) }
+  .rela.tdata	0 : { *(.rela.tdata) }
+  .rela.tbss	0 : { *(.rela.tbss) }
+  .rela.ctors   0 : { *(.rela.ctors) }
+  .rela.dtors   0 : { *(.rela.dtors) }
+  .rela.got     0 : { *(.rela.got) }
+  .rela.bss     0 : { *(.rela.bss) }
+  .rela.ifunc   0 : { *(.rela.ifunc) }
+  .rela.plt     0 :
+    {
+      *(.rela.plt)
+    }
+  .init         0 :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt          0 : ALIGN(16) { *(.plt) *(.iplt) }
+  .text         0 :
+  {
+    *(.text .stub)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini         0 :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  .rodata       0 : { *(.rodata) }
+  .rodata1      0 : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame     0 : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges 0 : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  /* Exception handling  */
+  .eh_frame     0 : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table 0 : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges 0 : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	0 : { *(.tdata) }
+  .tbss		0 : { *(.tbss) }
+  .preinit_array   0 :
+  {
+    KEEP (*(.preinit_array))
+  }
+  .jcr          0 : { KEEP (*(.jcr)) }
+  .dynamic      0 : { *(.dynamic) }
+  .got          0 : { *(.got) *(.igot) }
+  .got.plt      0 : { *(.got.plt)  *(.igot.plt) }
+  .data         0 :
+  {
+    *(.data)
+    SORT(CONSTRUCTORS)
+  }
+  .data1        0 : { *(.data1) }
+  .bss          0 :
+  {
+   *(.dynbss)
+   *(.bss)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+  }
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xw b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xw
new file mode 100644
index 0000000..0f068e0
--- /dev/null
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linux32b.xw
@@ -0,0 +1,208 @@
+/* Script for -z combreloc -z now -z relro: combine and sort reloc sections */
+OUTPUT_FORMAT("elf32-bigaarch64", "elf32-bigaarch64",
+	      "elf32-littleaarch64")
+OUTPUT_ARCH(aarch64:ilp32)
+ENTRY(_start)
+SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib32"); SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
+SECTIONS
+{
+  /* Read-only sections, merged into text segment: */
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;
+  .interp         : { *(.interp) }
+  .note.gnu.build-id : { *(.note.gnu.build-id) }
+  .hash           : { *(.hash) }
+  .gnu.hash       : { *(.gnu.hash) }
+  .dynsym         : { *(.dynsym) }
+  .dynstr         : { *(.dynstr) }
+  .gnu.version    : { *(.gnu.version) }
+  .gnu.version_d  : { *(.gnu.version_d) }
+  .gnu.version_r  : { *(.gnu.version_r) }
+  .rela.dyn       :
+    {
+      *(.rela.init)
+      *(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
+      *(.rela.fini)
+      *(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
+      *(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
+      *(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
+      *(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
+      *(.rela.ctors)
+      *(.rela.dtors)
+      *(.rela.got)
+      *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
+      *(.rela.ifunc)
+    }
+  .rela.plt       :
+    {
+      *(.rela.plt)
+      PROVIDE_HIDDEN (__rela_iplt_start = .);
+      *(.rela.iplt)
+      PROVIDE_HIDDEN (__rela_iplt_end = .);
+    }
+  .init           :
+  {
+    KEEP (*(SORT_NONE(.init)))
+  } =0
+  .plt            : ALIGN(16) { *(.plt) *(.iplt) }
+  .text           :
+  {
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
+    *(.text.exit .text.exit.*)
+    *(.text.startup .text.startup.*)
+    *(.text.hot .text.hot.*)
+    *(.text .stub .text.* .gnu.linkonce.t.*)
+    /* .gnu.warning sections are handled specially by elf32.em.  */
+    *(.gnu.warning)
+  } =0
+  .fini           :
+  {
+    KEEP (*(SORT_NONE(.fini)))
+  } =0
+  PROVIDE (__etext = .);
+  PROVIDE (_etext = .);
+  PROVIDE (etext = .);
+  .rodata         : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
+  .rodata1        : { *(.rodata1) }
+  .eh_frame_hdr : { *(.eh_frame_hdr) }
+  .eh_frame       : ONLY_IF_RO { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RO { *(.gcc_except_table
+  .gcc_except_table.*) }
+  /* These sections are generated by the Sun/Oracle C++ compiler.  */
+  .exception_ranges   : ONLY_IF_RO { *(.exception_ranges
+  .exception_ranges*) }
+  /* Adjust the address for the data segment.  We want to adjust up to
+     the same address within the page on the next page up.  */
+  . = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
+  /* Exception handling  */
+  .eh_frame       : ONLY_IF_RW { KEEP (*(.eh_frame)) }
+  .gcc_except_table   : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
+  .exception_ranges   : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
+  /* Thread Local Storage sections  */
+  .tdata	  : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
+  .tbss		  : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
+  .preinit_array     :
+  {
+    PROVIDE_HIDDEN (__preinit_array_start = .);
+    KEEP (*(.preinit_array))
+    PROVIDE_HIDDEN (__preinit_array_end = .);
+  }
+  .init_array     :
+  {
+    PROVIDE_HIDDEN (__init_array_start = .);
+    KEEP (*(SORT(.init_array.*)))
+    KEEP (*(.init_array ))
+    PROVIDE_HIDDEN (__init_array_end = .);
+  }
+  .fini_array     :
+  {
+    PROVIDE_HIDDEN (__fini_array_start = .);
+    KEEP (*(SORT(.fini_array.*)))
+    KEEP (*(.fini_array ))
+    PROVIDE_HIDDEN (__fini_array_end = .);
+  }
+  .ctors          :
+  {
+    /* gcc uses crtbegin.o to find the start of
+       the constructors, so we make sure it is
+       first.  Because this is a wildcard, it
+       doesn't matter if the user does not
+       actually link against crtbegin.o; the
+       linker won't look for a file to match a
+       wildcard.  The wildcard also means that it
+       doesn't matter which directory crtbegin.o
+       is in.  */
+    KEEP (*crtbegin.o(.ctors))
+    KEEP (*crtbegin?.o(.ctors))
+    /* We don't want to include the .ctor section from
+       the crtend.o file until after the sorted ctors.
+       The .ctor section from the crtend file contains the
+       end of ctors marker and it must be last */
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
+    KEEP (*(SORT(.ctors.*)))
+    KEEP (*(.ctors))
+  }
+  .dtors          :
+  {
+    KEEP (*crtbegin.o(.dtors))
+    KEEP (*crtbegin?.o(.dtors))
+    KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
+    KEEP (*(SORT(.dtors.*)))
+    KEEP (*(.dtors))
+  }
+  .jcr            : { KEEP (*(.jcr)) }
+  .data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
+  .dynamic        : { *(.dynamic) }
+  .got            : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
+  . = DATA_SEGMENT_RELRO_END (0, .);
+  .data           :
+  {
+    PROVIDE (__data_start = .);
+    *(.data .data.* .gnu.linkonce.d.*)
+    SORT(CONSTRUCTORS)
+  }
+  .data1          : { *(.data1) }
+  _edata = .; PROVIDE (edata = .);
+  . = .;
+  __bss_start = .;
+  __bss_start__ = .;
+  .bss            :
+  {
+   *(.dynbss)
+   *(.bss .bss.* .gnu.linkonce.b.*)
+   *(COMMON)
+   /* Align here to ensure that the .bss section occupies space up to
+      _end.  Align after .bss to ensure correct alignment even if the
+      .bss section disappears because there are no input sections.
+      FIXME: Why do we need it? When there is no .bss section, we don't
+      pad the .data section.  */
+   . = ALIGN(. != 0 ? 32 / 8 : 1);
+  }
+  _bss_end__ = . ; __bss_end__ = . ;
+  . = ALIGN(32 / 8);
+  . = SEGMENT_START("ldata-segment", .);
+  . = ALIGN(32 / 8);
+  __end__ = . ;
+  _end = .; PROVIDE (end = .);
+  . = DATA_SEGMENT_END (.);
+  /* Stabs debugging sections.  */
+  .stab          0 : { *(.stab) }
+  .stabstr       0 : { *(.stabstr) }
+  .stab.excl     0 : { *(.stab.excl) }
+  .stab.exclstr  0 : { *(.stab.exclstr) }
+  .stab.index    0 : { *(.stab.index) }
+  .stab.indexstr 0 : { *(.stab.indexstr) }
+  .comment       0 : { *(.comment) }
+  /* DWARF debug sections.
+     Symbols in the DWARF debugging sections are relative to the beginning
+     of the section so we begin them at 0.  */
+  /* DWARF 1 */
+  .debug          0 : { *(.debug) }
+  .line           0 : { *(.line) }
+  /* GNU DWARF 1 extensions */
+  .debug_srcinfo  0 : { *(.debug_srcinfo) }
+  .debug_sfnames  0 : { *(.debug_sfnames) }
+  /* DWARF 1.1 and DWARF 2 */
+  .debug_aranges  0 : { *(.debug_aranges) }
+  .debug_pubnames 0 : { *(.debug_pubnames) }
+  /* DWARF 2 */
+  .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
+  .debug_abbrev   0 : { *(.debug_abbrev) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
+  .debug_frame    0 : { *(.debug_frame) }
+  .debug_str      0 : { *(.debug_str) }
+  .debug_loc      0 : { *(.debug_loc) }
+  .debug_macinfo  0 : { *(.debug_macinfo) }
+  /* SGI/MIPS DWARF 2 extensions */
+  .debug_weaknames 0 : { *(.debug_weaknames) }
+  .debug_funcnames 0 : { *(.debug_funcnames) }
+  .debug_typenames 0 : { *(.debug_typenames) }
+  .debug_varnames  0 : { *(.debug_varnames) }
+  /* DWARF 3 */
+  .debug_pubtypes 0 : { *(.debug_pubtypes) }
+  .debug_ranges   0 : { *(.debug_ranges) }
+  /* DWARF Extension.  */
+  .debug_macro    0 : { *(.debug_macro) }
+  .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
+  .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
+}
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.x b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.x
index 1afded0..fe3afd6 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.x
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.x
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xbn b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xbn
index 5d2ab21..4342825 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xbn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xbn
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -153,12 +153,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   /* Stabs debugging sections.  */
@@ -184,7 +184,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -201,5 +201,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xc b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xc
index 969993e..d13d2c4 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xc
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +156,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -188,7 +188,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -205,5 +205,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xd b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xd
index eb4d681..a2c6a67 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xd
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xd
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdc b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdc
index 7325748..d566166 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdc
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -156,12 +156,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -188,7 +188,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -205,5 +205,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdw b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdw
index b0e8087..d9f47da 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xdw
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -155,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -187,7 +187,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -204,5 +204,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xn b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xn
index 51675d3..8348714 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xn
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xn
@@ -44,7 +44,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -154,12 +154,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -186,7 +186,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -203,5 +203,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xr b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xr
index a16da6b..34e2113 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xr
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xr
@@ -115,7 +115,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xs b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xs
index 2cb725c..94f5f33 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xs
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xs
@@ -41,7 +41,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -145,12 +145,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -177,7 +177,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -194,5 +194,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsc b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsc
index abb0f32..4a86a8b 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsc
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsc
@@ -43,7 +43,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -147,12 +147,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -179,7 +179,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -196,5 +196,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsw b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsw
index 5f43c6d..df1477b 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xsw
@@ -43,7 +43,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -146,12 +146,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -178,7 +178,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -195,5 +195,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xu b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xu
index fa5ac2c..a8598ee 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xu
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xu
@@ -116,7 +116,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xw b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xw
index 2b184b1..2108435 100644
--- a/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xw
+++ b/aarch64-linux-android/lib/ldscripts/aarch64linuxb.xw
@@ -46,7 +46,7 @@ SECTIONS
   .plt            : ALIGN(16) { *(.plt) *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -155,12 +155,12 @@ SECTIONS
       .bss section disappears because there are no input sections.
       FIXME: Why do we need it? When there is no .bss section, we don't
       pad the .data section.  */
-   . = ALIGN(. != 0 ? 32 / 8 : 1);
+   . = ALIGN(. != 0 ? 64 / 8 : 1);
   }
   _bss_end__ = . ; __bss_end__ = . ;
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   . = SEGMENT_START("ldata-segment", .);
-  . = ALIGN(32 / 8);
+  . = ALIGN(64 / 8);
   __end__ = . ;
   _end = .; PROVIDE (end = .);
   . = DATA_SEGMENT_END (.);
@@ -187,7 +187,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -204,5 +204,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.x b/aarch64-linux-android/lib/ldscripts/armelf.x
index cf28c0d..ff14dbb 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.x
+++ b/aarch64-linux-android/lib/ldscripts/armelf.x
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xbn b/aarch64-linux-android/lib/ldscripts/armelf.xbn
index 3a18514..ee27e1c 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xbn
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xbn
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xc b/aarch64-linux-android/lib/ldscripts/armelf.xc
index 79b062c..eb75f53 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xc
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xc
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -216,7 +212,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -238,5 +234,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xn b/aarch64-linux-android/lib/ldscripts/armelf.xn
index 48ff1ed..16585a8 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xn
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xn
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xr b/aarch64-linux-android/lib/ldscripts/armelf.xr
index 74f6a1e..7f58d8f 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xr
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xr
@@ -140,7 +140,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xs b/aarch64-linux-android/lib/ldscripts/armelf.xs
index 11b887b..74a81be 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xs
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xs
@@ -64,7 +64,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -202,7 +202,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -224,5 +224,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xsc b/aarch64-linux-android/lib/ldscripts/armelf.xsc
index 3a32644..53192e8 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xsc
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xsc
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -201,7 +201,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -223,5 +223,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xsw b/aarch64-linux-android/lib/ldscripts/armelf.xsw
index 990c25f..062eb39 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xsw
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xsw
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -201,7 +201,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -223,5 +223,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xu b/aarch64-linux-android/lib/ldscripts/armelf.xu
index 52efb0e..61d228b 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xu
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xu
@@ -141,7 +141,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf.xw b/aarch64-linux-android/lib/ldscripts/armelf.xw
index 5c120e5..6322d72 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf.xw
+++ b/aarch64-linux-android/lib/ldscripts/armelf.xw
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -216,7 +212,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -238,5 +234,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.x b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.x
index d5b4eb5..b2460ac 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.x
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.x
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xbn b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xbn
index 624c854..c737b76 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xbn
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xbn
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -230,5 +230,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xc b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xc
index fc2ee25..ce913a4 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xc
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xc
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xd b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xd
index 01d6bd5..539efb2 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xd
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xd
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdc b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdc
index e501210..01ab467 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdc
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdc
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdw b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdw
index a257f61..3ce420f 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdw
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xdw
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xn b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xn
index ec39a11..47838fb 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xn
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xn
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xr b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xr
index 7c3c80e..2fd75b0 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xr
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xr
@@ -140,7 +140,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xs b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xs
index 39ad105..6e16007 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xs
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xs
@@ -64,7 +64,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -204,7 +204,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -221,5 +221,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsc b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsc
index 962d333..a3e771a 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsc
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsc
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -203,7 +203,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -220,5 +220,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsw b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsw
index 8490334..cc935dd 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsw
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xsw
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -203,7 +203,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -220,5 +220,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xu b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xu
index 1a60936..1187ef8 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xu
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xu
@@ -141,7 +141,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xw b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xw
index f3e3120..3367456 100644
--- a/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xw
+++ b/aarch64-linux-android/lib/ldscripts/armelf_linux_eabi.xw
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.x b/aarch64-linux-android/lib/ldscripts/armelfb.x
index fb2b86a..855d66b 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.x
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.x
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xbn b/aarch64-linux-android/lib/ldscripts/armelfb.xbn
index 106904b..3858c17 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xbn
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xbn
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xc b/aarch64-linux-android/lib/ldscripts/armelfb.xc
index 5b673b1..0ac1f2d 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xc
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xc
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -216,7 +212,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -238,5 +234,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xn b/aarch64-linux-android/lib/ldscripts/armelfb.xn
index 59fac3a..ec3b2b4 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xn
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xn
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +235,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xr b/aarch64-linux-android/lib/ldscripts/armelfb.xr
index 481af21..29faeee 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xr
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xr
@@ -140,7 +140,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xs b/aarch64-linux-android/lib/ldscripts/armelfb.xs
index 2c480ac..eded9f3 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xs
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xs
@@ -64,7 +64,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -202,7 +202,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -224,5 +224,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xsc b/aarch64-linux-android/lib/ldscripts/armelfb.xsc
index c0fe54a..81e7ea2 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xsc
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xsc
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -201,7 +201,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -223,5 +223,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xsw b/aarch64-linux-android/lib/ldscripts/armelfb.xsw
index 2b52a6e..f797f85 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xsw
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xsw
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -201,7 +201,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -223,5 +223,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xu b/aarch64-linux-android/lib/ldscripts/armelfb.xu
index 621d643..1f9b0ff 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xu
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xu
@@ -141,7 +141,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb.xw b/aarch64-linux-android/lib/ldscripts/armelfb.xw
index 991d483..d57b0b7 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb.xw
+++ b/aarch64-linux-android/lib/ldscripts/armelfb.xw
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -216,7 +212,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -238,5 +234,5 @@ SECTIONS
   }
   .ARM.attributes 0 : { KEEP (*(.ARM.attributes)) KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.x b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.x
index cd62673..e9fda92 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.x
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.x
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xbn b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xbn
index 26ea532..c7978ef 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xbn
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xbn
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -213,7 +213,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -230,5 +230,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xc b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xc
index 8834b3b..4bced92 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xc
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xc
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xd b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xd
index 5331b15..4b645a0 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xd
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xd
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdc b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdc
index 332f7aa..d269c13 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdc
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdc
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdw b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdw
index f1eec54..7a1719e 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdw
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xdw
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xn b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xn
index 972e075..a98f1d3 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xn
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xn
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -69,7 +69,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -215,7 +215,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -232,5 +232,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xr b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xr
index c13f16c..cadb64f 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xr
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xr
@@ -140,7 +140,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xs b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xs
index 600de29..4ddafba 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xs
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xs
@@ -64,7 +64,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -204,7 +204,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -221,5 +221,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsc b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsc
index a844253..0979be7 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsc
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsc
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -203,7 +203,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -220,5 +220,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsw b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsw
index 0c8006e..ccff421 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsw
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xsw
@@ -63,7 +63,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -203,7 +203,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -220,5 +220,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xu b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xu
index 78fc9e6..ff7acd3 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xu
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xu
@@ -141,7 +141,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
diff --git a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xw b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xw
index 9bfd116..5f8c31a 100644
--- a/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xw
+++ b/aarch64-linux-android/lib/ldscripts/armelfb_linux_eabi.xw
@@ -7,7 +7,7 @@ SEARCH_DIR("/tmp/android-toolchain-eabi/aarch64-linux-android/lib");
 SECTIONS
 {
   /* Read-only sections, merged into text segment: */
-  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00008000)); . = SEGMENT_START("text-segment", 0x00008000) + SIZEOF_HEADERS;
+  PROVIDE (__executable_start = SEGMENT_START("text-segment", 0x00010000)); . = SEGMENT_START("text-segment", 0x00010000) + SIZEOF_HEADERS;
   .interp         : { *(.interp) }
   .note.gnu.build-id : { *(.note.gnu.build-id) }
   .hash           : { *(.hash) }
@@ -34,8 +34,6 @@ SECTIONS
       PROVIDE_HIDDEN (__rel_iplt_start = .);
       *(.rel.iplt)
       PROVIDE_HIDDEN (__rel_iplt_end = .);
-      PROVIDE_HIDDEN (__rela_iplt_start = .);
-      PROVIDE_HIDDEN (__rela_iplt_end = .);
     }
   .rela.dyn       :
     {
@@ -50,8 +48,6 @@ SECTIONS
       *(.rela.dtors)
       *(.rela.got)
       *(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
-      PROVIDE_HIDDEN (__rel_iplt_start = .);
-      PROVIDE_HIDDEN (__rel_iplt_end = .);
       PROVIDE_HIDDEN (__rela_iplt_start = .);
       *(.rela.iplt)
       PROVIDE_HIDDEN (__rela_iplt_end = .);
@@ -72,7 +68,7 @@ SECTIONS
   .iplt           : { *(.iplt) }
   .text           :
   {
-    *(.text.unlikely .text.*_unlikely)
+    *(.text.unlikely .text.*_unlikely .text.unlikely.*)
     *(.text.exit .text.exit.*)
     *(.text.startup .text.startup.*)
     *(.text.hot .text.hot.*)
@@ -218,7 +214,7 @@ SECTIONS
   /* DWARF 2 */
   .debug_info     0 : { *(.debug_info .gnu.linkonce.wi.*) }
   .debug_abbrev   0 : { *(.debug_abbrev) }
-  .debug_line     0 : { *(.debug_line) }
+  .debug_line     0 : { *(.debug_line .debug_line.* .debug_line_end ) }
   .debug_frame    0 : { *(.debug_frame) }
   .debug_str      0 : { *(.debug_str) }
   .debug_loc      0 : { *(.debug_loc) }
@@ -235,5 +231,5 @@ SECTIONS
   .debug_macro    0 : { *(.debug_macro) }
   .gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
   .note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
-  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) *(.gnu_object_only) }
+  /DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
 }
diff --git a/bin/aarch64-linux-android-addr2line b/bin/aarch64-linux-android-addr2line
index 190f14e..323024d 100755
--- a/bin/aarch64-linux-android-addr2line
+++ b/bin/aarch64-linux-android-addr2line
diff --git a/bin/aarch64-linux-android-ar b/bin/aarch64-linux-android-ar
index 6c7efc0..6a21b55 100755
--- a/bin/aarch64-linux-android-ar
+++ b/bin/aarch64-linux-android-ar
diff --git a/bin/aarch64-linux-android-as b/bin/aarch64-linux-android-as
index 0f25a68..6e4315a 100755
--- a/bin/aarch64-linux-android-as
+++ b/bin/aarch64-linux-android-as
diff --git a/bin/aarch64-linux-android-c++ b/bin/aarch64-linux-android-c++
index b7aa570..5ab2ee6 100755
--- a/bin/aarch64-linux-android-c++
+++ b/bin/aarch64-linux-android-c++
diff --git a/bin/aarch64-linux-android-c++filt b/bin/aarch64-linux-android-c++filt
index 61ac8d5..46b89df 100755
--- a/bin/aarch64-linux-android-c++filt
+++ b/bin/aarch64-linux-android-c++filt
diff --git a/bin/aarch64-linux-android-cpp b/bin/aarch64-linux-android-cpp
index 6ec7531..6dc015c 100755
--- a/bin/aarch64-linux-android-cpp
+++ b/bin/aarch64-linux-android-cpp
diff --git a/bin/aarch64-linux-android-elfedit b/bin/aarch64-linux-android-elfedit
index 05d340b..6cd82e9 100755
--- a/bin/aarch64-linux-android-elfedit
+++ b/bin/aarch64-linux-android-elfedit
diff --git a/bin/aarch64-linux-android-g++ b/bin/aarch64-linux-android-g++
index b7aa570..5ab2ee6 100755
--- a/bin/aarch64-linux-android-g++
+++ b/bin/aarch64-linux-android-g++
diff --git a/bin/aarch64-linux-android-gcc b/bin/aarch64-linux-android-gcc
index 8ea39e6..ec535e8 100755
--- a/bin/aarch64-linux-android-gcc
+++ b/bin/aarch64-linux-android-gcc
diff --git a/bin/aarch64-linux-android-gcc-4.9.2 b/bin/aarch64-linux-android-gcc-4.9.2
index 8ea39e6..ec535e8 100755
--- a/bin/aarch64-linux-android-gcc-4.9.2
+++ b/bin/aarch64-linux-android-gcc-4.9.2
diff --git a/bin/aarch64-linux-android-gprof b/bin/aarch64-linux-android-gprof
index 476be82..89f3740 100755
--- a/bin/aarch64-linux-android-gprof
+++ b/bin/aarch64-linux-android-gprof
diff --git a/bin/aarch64-linux-android-ld b/bin/aarch64-linux-android-ld
index 2e81a89..acbf820 100755
--- a/bin/aarch64-linux-android-ld
+++ b/bin/aarch64-linux-android-ld
diff --git a/bin/aarch64-linux-android-ld.bfd b/bin/aarch64-linux-android-ld.bfd
index 2e81a89..acbf820 100755
--- a/bin/aarch64-linux-android-ld.bfd
+++ b/bin/aarch64-linux-android-ld.bfd
diff --git a/bin/aarch64-linux-android-nm b/bin/aarch64-linux-android-nm
index 0dc3682..799ba33 100755
--- a/bin/aarch64-linux-android-nm
+++ b/bin/aarch64-linux-android-nm
diff --git a/bin/aarch64-linux-android-objcopy b/bin/aarch64-linux-android-objcopy
index 82ed611..d6ad6e1 100755
--- a/bin/aarch64-linux-android-objcopy
+++ b/bin/aarch64-linux-android-objcopy
diff --git a/bin/aarch64-linux-android-objdump b/bin/aarch64-linux-android-objdump
index cdc798d..31517b7 100755
--- a/bin/aarch64-linux-android-objdump
+++ b/bin/aarch64-linux-android-objdump
diff --git a/bin/aarch64-linux-android-ranlib b/bin/aarch64-linux-android-ranlib
index 61b73df..1f58919 100755
--- a/bin/aarch64-linux-android-ranlib
+++ b/bin/aarch64-linux-android-ranlib
diff --git a/bin/aarch64-linux-android-readelf b/bin/aarch64-linux-android-readelf
index 3be21b7..6b16233 100755
--- a/bin/aarch64-linux-android-readelf
+++ b/bin/aarch64-linux-android-readelf
diff --git a/bin/aarch64-linux-android-size b/bin/aarch64-linux-android-size
index f0212dc..5627c93 100755
--- a/bin/aarch64-linux-android-size
+++ b/bin/aarch64-linux-android-size
diff --git a/bin/aarch64-linux-android-strings b/bin/aarch64-linux-android-strings
index d8bbd11..0ab269e 100755
--- a/bin/aarch64-linux-android-strings
+++ b/bin/aarch64-linux-android-strings
diff --git a/bin/aarch64-linux-android-strip b/bin/aarch64-linux-android-strip
index d8f7916..0a590b3 100755
--- a/bin/aarch64-linux-android-strip
+++ b/bin/aarch64-linux-android-strip
diff --git a/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a b/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a
index 5c1f29f..aac9194 100644
--- a/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a
+++ b/lib/gcc/aarch64-linux-android/4.9.2/libgcc.a
diff --git a/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a b/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a
index d4fd422..e61d66c 100644
--- a/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a
+++ b/lib/gcc/aarch64-linux-android/4.9.2/libgcov.a
diff --git a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/auto-host.h b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/auto-host.h
index b14aea0..41ac80b 100644
--- a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/auto-host.h
+++ b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/auto-host.h
@@ -426,7 +426,7 @@
 
 /* Define if your assembler supports the -mabi option. */
 #ifndef USED_FOR_TARGET
-/* #undef HAVE_AS_MABI_OPTION */
+#define HAVE_AS_MABI_OPTION 1
 #endif
 
 
@@ -1367,7 +1367,7 @@
 
 /* Define to the level of your linker's plugin support. */
 #ifndef USED_FOR_TARGET
-#define HAVE_LTO_PLUGIN 2
+#define HAVE_LTO_PLUGIN 0
 #endif
 
 
diff --git a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h
index 06fe6b1..6a6cd99 100644
--- a/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h
+++ b/lib/gcc/aarch64-linux-android/4.9.2/plugin/include/configargs.h
@@ -1,5 +1,5 @@
 /* Generated automatically. */
-static const char configuration_arguments[] = "/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../gcc/gcc-linaro-4.9-2014.09/configure --prefix=/tmp/android-toolchain-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --with-mpfr=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --with-mpc=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --disable-libssp --disable-nls --disable-libmudflap --disable-shared --disable-sjlj-exceptions --disable-libquadmath --disable-libitm --disable-libsanitizer --prefix=/tmp/android-toolchain-eabi --disable-docs --disable-nls --with-gcc-version=linaro-4.9-2014.09 --with-binutils-version=current --with-gmp-version=current --with-mpfr-version=current --with-mpc-version=current --disable-graphite --target=aarch64-linux-android --enable-threads --enable-tls --disable-libgomp --disable-libstdc__-v3 --disable-libitm --disable-libsanitizer --disable-libatomic";
+static const char configuration_arguments[] = "/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../gcc/gcc-linaro-4.9-2014.09/configure --prefix=/tmp/android-toolchain-eabi --host=x86_64-linux-gnu --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --with-mpfr=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --with-mpc=/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/temp-install --disable-libssp --disable-nls --disable-libmudflap --disable-shared --disable-sjlj-exceptions --disable-libquadmath --disable-libitm --disable-libsanitizer --prefix=/tmp/android-toolchain-eabi --disable-docs --disable-nls --with-gcc-version=linaro-4.9-2014.09 --with-binutils-version=linaro-2.24.0-2014.09 --with-gmp-version=current --with-mpfr-version=current --with-mpc-version=current --disable-graphite --target=aarch64-linux-android --enable-threads --enable-tls --disable-libgomp --disable-libstdc__-v3 --disable-libitm --disable-libsanitizer --disable-libatomic";
 static const char thread_model[] = "posix";
 
 static const struct {
diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/cc1 b/libexec/gcc/aarch64-linux-android/4.9.2/cc1
index 0f8eeba..04fa722 100755
--- a/libexec/gcc/aarch64-linux-android/4.9.2/cc1
+++ b/libexec/gcc/aarch64-linux-android/4.9.2/cc1
diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus b/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus
index 749c85f..21e31f8 100755
--- a/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus
+++ b/libexec/gcc/aarch64-linux-android/4.9.2/cc1plus
diff --git a/libexec/gcc/aarch64-linux-android/4.9.2/lto1 b/libexec/gcc/aarch64-linux-android/4.9.2/lto1
index 8368dbe..fa23024 100755
--- a/libexec/gcc/aarch64-linux-android/4.9.2/lto1
+++ b/libexec/gcc/aarch64-linux-android/4.9.2/lto1
diff --git a/share/info/as.info b/share/info/as.info
index 46f8db2..c5c5bf8 100644
--- a/share/info/as.info
+++ b/share/info/as.info
@@ -1,17 +1,8 @@
-This is as.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/gas/doc/as.texinfo.
+This is as.info, produced by makeinfo version 5.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, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-2000, 2001, 2002, 2006, 2007, 2008, 2009, 2010, 2011 Free Software
-Foundation, Inc.
+   Copyright (C) 1991-2013 Free Software Foundation, Inc.
 
    Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -20,18 +11,24 @@ Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
 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' (Linux/GNU Binutils)
-version 2.23.52.0.2.
+This file is a user guide to the GNU assembler 'as' (GNU Binutils)
+version 2.24.0.
 
    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:
 
@@ -42,7 +39,6 @@ section entitled "GNU Free Documentation License".
 * Symbols::                     Symbols
 * Expressions::                 Expressions
 * Pseudo Ops::                  Assembler Directives
-
 * Object Attributes::           Object Attributes
 * Machine Dependencies::        Machine Dependent Features
 * Reporting Bugs::              Reporting Bugs
@@ -56,14 +52,15 @@ File: as.info,  Node: Overview,  Next: Invoking,  Prev: Top,  Up: Top
 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]
       [-compress-debug-sections]  [-nocompress-debug-sections]
       [-debug-prefix-map OLD=NEW]
       [-defsym SYM=VAL] [-f] [-g] [-gstabs]
-      [-gstabs+] [-gdwarf-2] [-help] [-I DIR] [-J]
+      [-gstabs+] [-gdwarf-2] [-gdwarf-sections]
+      [-help] [-I DIR] [-J]
       [-K] [-L] [-listing-lhs-width=NUM]
       [-listing-lhs-width2=NUM] [-listing-rhs-width=NUM]
       [-listing-cont-lines=NUM] [-keep-locals] [-o
@@ -76,6 +73,7 @@ Command-Line Options: Invoking.
 
      _Target AArch64 options:_
         [-EB|-EL]
+        [-mabi=ABI]
 
      _Target Alpha options:_
         [-mCPU]
@@ -180,6 +178,7 @@ Command-Line Options: Invoking.
         [-mips3] [-mips4] [-mips5] [-mips32] [-mips32r2]
         [-mips64] [-mips64r2]
         [-construct-floats] [-no-construct-floats]
+        [-mnan=ENCODING]
         [-trap] [-no-break] [-break] [-no-trap]
         [-mips16] [-no-mips16]
         [-mmicromips] [-mno-micromips]
@@ -190,6 +189,7 @@ Command-Line Options: Invoking.
         [-mdspr2] [-mno-dspr2]
         [-mmt] [-mno-mt]
         [-mmcu] [-mno-mcu]
+        [-minsn32] [-mno-insn32]
         [-mfix7000] [-mno-fix7000]
         [-mfix-vr4120] [-mno-fix-vr4120]
         [-mfix-vr4130] [-mno-fix-vr4130]
@@ -285,96 +285,96 @@ Command-Line Options: Invoking.
        [ -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.  The debug sections are
-     renamed to begin with `.zdebug', and the resulting object file may
+     renamed to begin with '.zdebug', and the resulting object file may
      not be compatible with older linkers and object file utilities.
 
-`--nocompress-debug-sections'
+'--nocompress-debug-sections'
      Do not compress DWARF debug sections.  This is the default.
 
-`-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
@@ -382,111 +382,119 @@ Command-Line Options: Invoking.
      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.
 
-`--size-check=error'
-`--size-check=warning'
+'--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.
+
+'--size-check=error'
+'--size-check=warning'
      Issue an error or warning for invalid ELF .size directive.
 
-`--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.
 
-`-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.
 
      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.
 
-`--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).
 
@@ -496,41 +504,32 @@ configured for an Alpha processor.
    The following options are available when as is configured for an ARC
 processor.
 
-`-marc[5|6|7|8]'
+'-marc[5|6|7|8]'
      This option selects the core processor variant.
-
-`-EB | -EL'
+'-EB | -EL'
      Select either big-endian (-EB) or little-endian (-EL) output.
 
    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.
-
-`-k'
+'-k'
      Specify that PIC code has been generated.
 
    *Note Blackfin Options::, for the options available when as is
@@ -540,18 +539,18 @@ configured for the Blackfin processor family.
 
    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
@@ -560,82 +559,78 @@ Adapteva EPIPHANY series.
    *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
@@ -643,11 +638,9 @@ Motorola 68000 series.
      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.
@@ -655,315 +648,318 @@ configured for an Altera Nios II processor.
    For details about the PDP-11 machine dependent features options, see
 *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'
-`-mips64'
-`-mips64r2'
+'-mips1'
+'-mips2'
+'-mips3'
+'-mips4'
+'-mips5'
+'-mips32'
+'-mips32r2'
+'-mips64'
+'-mips64r2'
      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', `-mips64', and `-mips64r2' correspond to generic
-     `MIPS V', `MIPS32', `MIPS32 Release 2', `MIPS64', and `MIPS64
-     Release 2' ISA processors, respectively.
+     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', '-mips64', and '-mips64r2' correspond to generic MIPS
+     V, MIPS32, MIPS32 Release 2, MIPS64, and MIPS64 Release 2 ISA
+     processors, respectively.
 
-`-march=CPU'
-     Generate code for a particular MIPS cpu.
+'-march=CPU'
+     Generate code for a particular MIPS CPU.
 
-`-mtune=CPU'
-     Schedule and tune for a particular MIPS 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.
 
-`-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.
 
-`-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.
+     Release 2 instructions.  '-mno-dspr2' 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.
 
-`--construct-floats'
-`--no-construct-floats'
-     The `--no-construct-floats' option disables the construction of
+'-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 to be used.
+
+'--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.
-
-`--emulation=NAME'
-     This option causes `as' to emulate `as' configured for some other
-     target, in all respects, including output format (choosing between
-     ELF and ECOFF only), handling of pseudo-opcodes which may generate
-     debugging information or store symbol table information, and
-     default endianness.  The available configuration names are:
-     `mipsecoff', `mipself', `mipslecoff', `mipsbecoff', `mipslelf',
-     `mipsbelf'.  The first two do not alter the default endianness
-     from that of the primary target for which the assembler was
-     configured; the others change the default to little- or big-endian
-     as indicated by the `b' or `l' in the name.  Using `-EB' or `-EL'
-     will override the endianness selection in any case.
-
-     This option is currently supported only when the primary target
-     `as' is configured for is a MIPS ELF or ECOFF target.
-     Furthermore, the primary target or others specified with
-     `--enable-targets=...' at configuration time must include support
-     for the other format, if both are to be available.  For example,
-     the Irix 5 configuration includes support for both.
-
-     Eventually, this option will support more configurations, with more
-     fine-grained control over the assembler's behavior, and will be
-     supported for more processors.
-
-`-nocpp'
-     `as' ignores this option.  It is accepted for compatibility with
+     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.
+
+'-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'
+     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
+     preferred options instead.
+
+'-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.
 
@@ -977,25 +973,20 @@ for a PowerPC processor.
    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, `g6', `g6',
-     `z900', `z990', `z9-109', `z9-ec', `z10', `z196', or `zEC12'.
-
-`-mregnames'
-`-mno-regnames'
+'-march=PROCESSOR'
+     Specify which s390 processor variant is the target, 'g6', 'g6',
+     'z900', 'z990', 'z9-109', 'z9-ec', 'z10', 'z196', or 'zEC12'.
+'-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.
 
@@ -1010,37 +1001,30 @@ configured for an Xtensa processor.
 
    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.
 
@@ -1061,9 +1045,9 @@ File: as.info,  Node: Manual,  Next: GNU Assembler,  Up: Overview
 ============================
 
 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.
@@ -1082,24 +1066,24 @@ File: as.info,  Node: GNU Assembler,  Next: Object Formats,  Prev: Manual,  Up:
 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
@@ -1119,23 +1103,23 @@ File: as.info,  Node: Command Line,  Next: Input Files,  Prev: Object Formats,
 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
@@ -1147,30 +1131,30 @@ File: as.info,  Node: Input Files,  Next: Object,  Prev: Command Line,  Up: Over
 ===============
 
 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.
+   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 <ctl-D> to tell `as' there is no more program to assemble.
+   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 <ctl-D> 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
 --------------------------
@@ -1181,14 +1165,14 @@ line number in a physical file; the other refers to a line number in a
 "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
@@ -1196,19 +1180,19 @@ File: as.info,  Node: Object,  Next: Errors,  Prev: Input Files,  Up: Overview
 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.)
+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.
+   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
@@ -1216,9 +1200,9 @@ File: as.info,  Node: Errors,  Prev: Object,  Up: Overview
 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.
 
@@ -1227,9 +1211,9 @@ that stops the assembly.
      file_name:NNN:Warning Message Text
 
 (where NNN is a line number).  If a logical file name has been given
-(*note `.file': File.) it is used for the filename, otherwise the name
+(*note '.file': File.) it is used for the filename, otherwise the name
 of the current input file is used.  If a logical line number was given
-(*note `.line': Line.)  then it is used to calculate the number printed,
+(*note '.line': Line.) then it is used to calculate the number printed,
 otherwise the actual line in the current source file is printed.  The
 message text is intended to be self explanatory (in the grand Unix
 tradition).
@@ -1250,226 +1234,224 @@ This chapter describes command-line options available in _all_ versions
 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
+* listing::       -listing-XXX to configure listing output
+* M::		  -M or -mri to assemble in MRI compatibility mode
+* MD::            -MD for dependency tracking
 * 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.
+'-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.
+     _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 '-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 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
 
@@ -1478,31 +1460,31 @@ require enhancing each object file format individually.  These are:
      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.
+     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
+   * '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 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
 
@@ -1511,76 +1493,75 @@ supported in future releases.
    * 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: o,  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.
@@ -1590,108 +1571,108 @@ dependencies of the main source file.
 
 File: as.info,  Node: o,  Next: R,  Prev: MD,  Up: Invoking
 
-2.11 Name the Object File: `-o'
+2.11 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.12 Join Data and Text Sections: `-R'
+2.12 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.13 Display Assembly Statistics: `--statistics'
+2.13 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.14 Compatible Output: `--traditional-format'
+2.14 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.15 Announce Version: `-v'
+2.15 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.16 Control Warnings: `-W', `--warn', `--no-warn', `--fatal-warnings'
+2.16 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.17 Generate Object File in Spite of Errors: `-Z'
+2.17 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
@@ -1700,8 +1681,8 @@ File: as.info,  Node: Syntax,  Next: Sections,  Prev: Invoking,  Up: Top
 ********
 
 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:
@@ -1719,7 +1700,7 @@ File: as.info,  Node: Preprocessing,  Next: Whitespace,  Up: Syntax
 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.
@@ -1731,22 +1712,22 @@ The `as' internal preprocessor:
 
    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
@@ -1754,8 +1735,8 @@ File: as.info,  Node: Whitespace,  Next: Comments,  Prev: Preprocessing,  Up: Sy
 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.
 
@@ -1765,10 +1746,10 @@ File: as.info,  Node: Comments,  Next: Symbol Intro,  Prev: Whitespace,  Up: Syn
 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.
 
      /*
@@ -1781,22 +1762,22 @@ you may not nest these comments.
    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,
@@ -1805,8 +1786,8 @@ the line is ignored.  (Just like a comment.)
                                # 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
@@ -1815,14 +1796,14 @@ File: as.info,  Node: Symbol Intro,  Next: Statements,  Prev: Comments,  Up: Syn
 ===========
 
 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
+(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::.  
+not a possible symbol delimiter).  *Note Symbols::.
 
 
 File: as.info,  Node: Statements,  Next: Constants,  Prev: Symbol Intro,  Up: Syntax
@@ -1830,15 +1811,15 @@ File: as.info,  Node: Statements,  Next: Constants,  Prev: Symbol Intro,  Up: Sy
 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
@@ -1847,21 +1828,21 @@ ignored.
    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.
@@ -1912,51 +1893,51 @@ File: as.info,  Node: Strings,  Next: Chars,  Up: Characters
 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.
 
-`\f'
+'\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.
+'\"'
+     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
+'\ 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
@@ -1969,16 +1950,16 @@ File: as.info,  Node: Chars,  Prev: Strings,  Up: Characters
 3.6.1.2 Characters
 ..................
 
-A single character may be written as a single quote immediately
-followed by that character.  The same escapes apply to characters as to
-strings.  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.  The same escapes apply to characters as to strings.
+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
@@ -1986,9 +1967,9 @@ File: as.info,  Node: Numbers,  Prev: Characters,  Up: Constants
 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.
 
@@ -2004,20 +1985,20 @@ File: as.info,  Node: Integers,  Next: Bignums,  Up: Numbers
 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.).
 
 
@@ -2039,51 +2020,48 @@ File: as.info,  Node: Flonums,  Prev: Bignums,  Up: Numbers
 
 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
@@ -2109,82 +2087,79 @@ Roughly, a section is a range of addresses, with no gaps; all data "in"
 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 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 '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
@@ -2195,14 +2170,13 @@ be such a symbol: its value is unknown at assembly time so it has
 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
@@ -2210,16 +2184,16 @@ File: as.info,  Node: Ld Sections,  Next: As Sections,  Prev: Secs Background,
 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.
@@ -2235,17 +2209,17 @@ File: as.info,  Node: Ld Sections,  Next: As Sections,  Prev: Secs Background,
 
 *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.
 
                            +-----+----+--+
@@ -2271,16 +2245,16 @@ File: as.info,  Node: As Sections,  Next: Sub-Sections,  Prev: Ld Sections,  Up:
 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
@@ -2296,40 +2270,40 @@ File: as.info,  Node: Sub-Sections,  Next: bss,  Prev: As Sections,  Up: Section
 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
@@ -2343,12 +2317,12 @@ expression (*note Expressions::).  If you just say `.text' then `.text
 
    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
@@ -2361,17 +2335,17 @@ allocate address space in the bss section, but you may not dictate data
 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
@@ -2383,7 +2357,7 @@ Symbols are a central concept: the programmer uses symbols to name
 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:
@@ -2400,7 +2374,7 @@ File: as.info,  Node: Labels,  Next: Setting Symbols,  Up: Symbols
 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:
@@ -2409,7 +2383,7 @@ the first definition overrides any other definitions.
    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.
 
 
@@ -2419,12 +2393,12 @@ File: as.info,  Node: Setting Symbols,  Next: Symbol Names,  Prev: Labels,  Up:
 ===============================
 
 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
@@ -2432,18 +2406,18 @@ File: as.info,  Node: Symbol Names,  Next: Dot,  Prev: Setting Symbols,  Up: Sym
 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'.
 
    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
@@ -2454,36 +2428,36 @@ Local Symbol Names
 ------------------
 
 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': L.) to retain the local symbols in the object files.
+debugging.  You may use the '-L' option (*note Include Local Symbols:
+'-L': L.) to retain the local symbols in the object files.
 
 Local Labels
 ------------
 
-Local labels help 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:'
+Local labels help 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 positive integer).  To refer to the most recent
-previous definition of that label write `Nb', using the same number as
+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".
+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:
 
@@ -2505,52 +2479,51 @@ uses them.  The symbol names are stored in the symbol table, appear in
 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'.
-
-`C-B'
+     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'
      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
 -------------------
 
-`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.
+'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.
 
    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
@@ -2558,11 +2531,11 @@ File: as.info,  Node: Dot,  Next: Symbol Attributes,  Prev: Symbol Names,  Up: S
 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
@@ -2574,20 +2547,16 @@ Every symbol has, as well as its name, the attributes "Value" and
 "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
 
 
@@ -2600,15 +2569,15 @@ The value of a symbol is (usually) 32 bits.  For a symbol which labels a
 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.
@@ -2627,7 +2596,7 @@ format depends on the object-code output format in use.
 
 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:
@@ -2642,8 +2611,8 @@ File: as.info,  Node: Symbol Desc,  Next: Symbol Other,  Up: a.out Symbols
 ..................
 
 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
@@ -2651,7 +2620,7 @@ File: as.info,  Node: Symbol Other,  Prev: Symbol Desc,  Up: a.out Symbols
 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
@@ -2660,20 +2629,20 @@ File: as.info,  Node: COFF Symbols,  Next: SOM Symbols,  Prev: a.out Symbols,  U
 --------------------------------
 
 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
@@ -2682,10 +2651,10 @@ File: as.info,  Node: SOM Symbols,  Prev: COFF Symbols,  Up: Symbol Attributes
 -------------------------------
 
 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.
 
 
@@ -2698,11 +2667,11 @@ An "expression" specifies an address or numeric value.  Whitespace may
 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:
 
@@ -2717,7 +2686,7 @@ File: as.info,  Node: Empty Exprs,  Next: Integer Exprs,  Up: Expressions
 
 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.
 
 
@@ -2756,12 +2725,12 @@ complement 32 bit integer.
    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.
 
 
@@ -2770,10 +2739,9 @@ File: as.info,  Node: Operators,  Next: Prefix Ops,  Prev: Arguments,  Up: Integ
 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
@@ -2781,13 +2749,12 @@ File: as.info,  Node: Prefix Ops,  Next: Infix Ops,  Prev: Operators,  Up: Integ
 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.
 
 
@@ -2798,83 +2765,78 @@ File: as.info,  Node: Infix Ops,  Prev: Prefix Ops,  Up: Integer Exprs
 
 "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
@@ -2883,7 +2845,6 @@ the result is absolute.
           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.
@@ -2894,8 +2855,8 @@ File: as.info,  Node: Pseudo Ops,  Next: Object Attributes,  Prev: Expressions,
 7 Assembler Directives
 **********************
 
-All assembler directives have names that begin with a period (`.').
-The rest of the name is letters, usually in lower case.
+All assembler directives have names that begin with a period ('.').  The
+rest of the name is letters, usually in lower case.
 
    This chapter discusses directives that are available regardless of
 the target machine configuration for the GNU assembler.  Some machine
@@ -2904,179 +2865,155 @@ Dependencies::.
 
 * 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', `.bundle_lock', `.bundle_unlock'
-* 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'
-* Secondary::                   `.secondary 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 <INT | NAME , TYPE DESCRIPTION>'
-
-* 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'
+* 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', '.bundle_lock', '.bundle_unlock'
+* 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 <INT | NAME , TYPE DESCRIPTION>'
+
+* 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'
 * 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
@@ -3091,99 +3028,99 @@ is omitted, the space is filled with no-op instructions.
 
    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, or32,
 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.
 
-    `<STRING>'
+     '<STRING>'
           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.
 
@@ -3195,234 +3132,234 @@ is omitted, the space is filled with no-op instructions.
 
    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
 
-7.8 `.bundle_align_mode ABS-EXPR'
+7.8 '.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.9 `.bundle_lock' and `.bundle_unlock'
+7.9 '.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.10 `.byte EXPRESSIONS'
+7.10 '.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.
 
 
 File: as.info,  Node: CFI directives,  Next: Comm,  Prev: Byte,  Up: Pseudo Ops
 
-7.11 `.cfi_sections SECTION_LIST'
+7.11 '.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'.
 
-7.12 `.cfi_startproc [simple]'
+7.12 '.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.13 `.cfi_endproc'
+7.13 '.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.14 `.cfi_personality ENCODING [, EXP]'
+7.14 '.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.15 `.cfi_lsda ENCODING [, EXP]'
+7.15 '.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'), second argument is not present, otherwise second
+('DW_EH_PE_omit'), second argument is not present, otherwise second
 argument should be a constant or a symbol name.  The default after
-`.cfi_startproc' is `.cfi_lsda 0xff', no LSDA.
+'.cfi_startproc' is '.cfi_lsda 0xff', no LSDA.
 
-7.16 `.cfi_def_cfa REGISTER, OFFSET'
+7.16 '.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.17 `.cfi_def_cfa_register REGISTER'
+7.17 '.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.18 `.cfi_def_cfa_offset OFFSET'
+7.18 '.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.19 `.cfi_adjust_cfa_offset OFFSET'
+7.19 '.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.20 `.cfi_offset REGISTER, OFFSET'
+7.20 '.cfi_offset REGISTER, OFFSET'
 ===================================
 
 Previous value of REGISTER is saved at offset OFFSET from CFA.
 
-7.21 `.cfi_rel_offset REGISTER, OFFSET'
+7.21 '.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.22 `.cfi_register REGISTER1, REGISTER2'
+7.22 '.cfi_register REGISTER1, REGISTER2'
 =========================================
 
 Previous value of REGISTER1 is saved in register REGISTER2.
 
-7.23 `.cfi_restore REGISTER'
+7.23 '.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.24 `.cfi_undefined REGISTER'
+7.24 '.cfi_undefined REGISTER'
 ==============================
 
 From now on the previous value of REGISTER can't be restored anymore.
 
-7.25 `.cfi_same_value REGISTER'
+7.25 '.cfi_same_value REGISTER'
 ===============================
 
 Current value of REGISTER is the same like in the previous frame, i.e.
 no restoration needed.
 
-7.26 `.cfi_remember_state',
+7.26 '.cfi_remember_state',
 ===========================
 
-First save all current rules for all registers by `.cfi_remember_state',
-then totally screw them up by subsequent `.cfi_*' directives and when
-everything is hopelessly bad, use `.cfi_restore_state' to restore the
+First save all current rules for all registers by '.cfi_remember_state',
+then totally screw them up by subsequent '.cfi_*' directives and when
+everything is hopelessly bad, use '.cfi_restore_state' to restore the
 previous saved state.
 
-7.27 `.cfi_return_column REGISTER'
+7.27 '.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.28 `.cfi_signal_frame'
+7.28 '.cfi_signal_frame'
 ========================
 
 Mark current function as signal trampoline.
 
-7.29 `.cfi_window_save'
+7.29 '.cfi_window_save'
 =======================
 
 SPARC register window has been saved.
 
-7.30 `.cfi_escape' EXPRESSION[, ...]
+7.30 '.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.31 `.cfi_val_encoded_addr REGISTER, ENCODING, LABEL'
+7.31 '.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
@@ -3433,101 +3370,101 @@ another register.
 
 File: as.info,  Node: Comm,  Next: Data,  Prev: CFI directives,  Up: Pseudo Ops
 
-7.32 `.comm SYMBOL , LENGTH '
+7.32 '.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.33 `.data SUBSECTION'
+7.33 '.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.34 `.def NAME'
+7.34 '.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.35 `.desc SYMBOL, ABS-EXPRESSION'
+7.35 '.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.36 `.dim'
+7.36 '.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.37 `.double FLONUMS'
+7.37 '.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.38 `.eject'
+7.38 '.eject'
 =============
 
 Force a page break at this point, when generating assembly listings.
@@ -3535,80 +3472,80 @@ Force a page break at this point, when generating assembly listings.
 
 File: as.info,  Node: Else,  Next: Elseif,  Prev: Eject,  Up: Pseudo Ops
 
-7.39 `.else'
+7.39 '.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.40 `.elseif'
+7.40 '.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.41 `.end'
+7.41 '.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.42 `.endef'
+7.42 '.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.43 `.endfunc'
+7.43 '.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.44 `.endif'
+7.44 '.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.45 `.equ SYMBOL, EXPRESSION'
+7.45 '.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::.
 
 
 File: as.info,  Node: Equiv,  Next: Eqv,  Prev: Equ,  Up: Pseudo Ops
 
-7.46 `.equiv SYMBOL, EXPRESSION'
+7.46 '.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.
@@ -3624,10 +3561,10 @@ equivalent to
 
 File: as.info,  Node: Eqv,  Next: Err,  Prev: Equiv,  Up: Pseudo Ops
 
-7.47 `.eqv SYMBOL, EXPRESSION'
+7.47 '.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.
@@ -3635,31 +3572,31 @@ current value is taken.
 
 File: as.info,  Node: Err,  Next: Error,  Prev: Eqv,  Up: Pseudo Ops
 
-7.48 `.err'
+7.48 '.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.49 `.error "STRING"'
+7.49 '.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.50 `.exitm'
+7.50 '.exitm'
 =============
 
 Exit early from the current macro definition.  *Note Macro::.
@@ -3667,54 +3604,54 @@ Exit early from the current macro definition.  *Note Macro::.
 
 File: as.info,  Node: Extern,  Next: Fail,  Prev: Exitm,  Up: Pseudo Ops
 
-7.51 `.extern'
+7.51 '.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.52 `.fail EXPRESSION'
+7.52 '.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.53 `.file'
+7.53 '.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
 
@@ -3723,14 +3660,14 @@ index of the entry in the table.  The FILENAME operand is a C string
 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.54 `.fill REPEAT , SIZE , VALUE'
+7.54 '.fill REPEAT , SIZE , VALUE'
 ==================================
 
 REPEAT, SIZE and VALUE are absolute expressions.  This emits REPEAT
@@ -3739,8 +3676,8 @@ more, but if it is more than 8, then it is deemed to have the value 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.
 
@@ -3751,51 +3688,51 @@ are absent, SIZE is assumed to be 1.
 
 File: as.info,  Node: Float,  Next: Func,  Prev: Fill,  Up: Pseudo Ops
 
-7.55 `.float FLONUMS'
+7.55 '.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.56 `.func NAME[,LABEL]'
+7.56 '.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.57 `.global SYMBOL', `.globl SYMBOL'
+7.57 '.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.58 `.gnu_attribute TAG,VALUE'
+7.58 '.gnu_attribute TAG,VALUE'
 ===============================
 
 Record a GNU object attribute for this file.  *Note Object Attributes::.
@@ -3803,161 +3740,161 @@ Record a GNU object attribute for this file.  *Note Object Attributes::.
 
 File: as.info,  Node: Hidden,  Next: hword,  Prev: Gnu_attribute,  Up: Pseudo Ops
 
-7.59 `.hidden NAMES'
+7.59 '.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.60 `.hword EXPRESSIONS'
+7.60 '.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.61 `.ident'
+7.61 '.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.62 `.if ABSOLUTE EXPRESSION'
+7.62 '.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.
+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.
+   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.63 `.incbin "FILE"[,SKIP[,COUNT]]'
+7.63 '.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.64 `.include "FILE"'
+7.64 '.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.65 `.int EXPRESSIONS'
+7.65 '.int EXPRESSIONS'
 =======================
 
 Expect zero or more EXPRESSIONS, of any section, separated by commas.
@@ -3968,33 +3905,33 @@ what kind of target the assembly is for.
 
 File: as.info,  Node: Internal,  Next: Irp,  Prev: Int,  Up: Pseudo Ops
 
-7.66 `.internal NAMES'
+7.66 '.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.67 `.irp SYMBOL,VALUES'...
+7.67 '.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
 
@@ -4013,16 +3950,16 @@ statements, use \SYMBOL.
 
 File: as.info,  Node: Irpc,  Next: Lcomm,  Prev: Irp,  Up: Pseudo Ops
 
-7.68 `.irpc SYMBOL,VALUES'...
+7.68 '.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
 
@@ -4042,64 +3979,64 @@ at *Note Macro::.
 
 File: as.info,  Node: Lcomm,  Next: Lflags,  Prev: Irpc,  Up: Pseudo Ops
 
-7.69 `.lcomm SYMBOL , LENGTH'
+7.69 '.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.70 `.lflags'
+7.70 '.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.71 `.line LINE-NUMBER'
+7.71 '.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.72 `.linkonce [TYPE]'
+7.72 '.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
@@ -4110,128 +4047,127 @@ following strings.  For example:
      .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.73 `.list'
+7.73 '.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.74 `.ln LINE-NUMBER'
+7.74 '.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.75 `.loc FILENO LINENO [COLUMN] [OPTIONS]'
+7.75 '.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'.
+'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'.
+'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'.
+'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.
+'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.76 `.loc_mark_labels ENABLE'
+7.76 '.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.77 `.local NAMES'
+7.77 '.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.78 `.long EXPRESSIONS'
+7.78 '.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.79 `.macro'
+7.79 '.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
@@ -4240,7 +4176,7 @@ macro `sum' that puts a sequence of numbers into memory:
              .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
@@ -4249,56 +4185,55 @@ With that definition, `SUM 0,5' is equivalent to this assembly input:
              .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
@@ -4311,12 +4246,12 @@ With that definition, `SUM 0,5' is equivalent to this assembly input:
           \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:
@@ -4325,13 +4260,13 @@ With that definition, `SUM 0,5' is equivalent to this assembly input:
                   \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:
 
@@ -4339,17 +4274,17 @@ With that definition, `SUM 0,5' is equivalent to this assembly input:
                \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
@@ -4357,40 +4292,40 @@ With that definition, `SUM 0,5' is equivalent to this assembly input:
                	.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_.
+'\@'
+     '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':
+'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.80 `.mri VAL'
+7.80 '.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.81 `.noaltmacro'
+7.81 '.noaltmacro'
 ==================
 
 Disable alternate macro mode.  *Note Altmacro::.
@@ -4398,19 +4333,19 @@ Disable alternate macro mode.  *Note Altmacro::.
 
 File: as.info,  Node: Nolist,  Next: Octa,  Prev: Noaltmacro,  Up: Pseudo Ops
 
-7.82 `.nolist'
+7.82 '.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.83 `.octa BIGNUMS'
+7.83 '.octa BIGNUMS'
 ====================
 
 This directive expects zero or more bignums, separated by commas.  For
@@ -4422,32 +4357,31 @@ hence _octa_-word for 16 bytes.
 
 File: as.info,  Node: Offset,  Next: Org,  Prev: Octa,  Up: Pseudo Ops
 
-7.84 `.offset LOC'
+7.84 '.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.85 `.org NEW-LC , FILL'
+7.85 '.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.
 
@@ -4462,15 +4396,15 @@ expression.  If the comma and FILL are omitted, FILL defaults to zero.
 
 File: as.info,  Node: P2align,  Next: PopSection,  Prev: Org,  Up: Pseudo Ops
 
-7.86 `.p2align[wl] ABS-EXPR, ABS-EXPR, ABS-EXPR'
+7.86 '.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
@@ -4480,51 +4414,51 @@ is omitted, the space is filled with no-op instructions.
 
    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.87 `.popsection'
+7.87 '.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.88 `.previous'
+7.88 '.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
@@ -4536,7 +4470,7 @@ their subsections).  For example:
       .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
@@ -4553,8 +4487,8 @@ subsection 2 of section A.  Whilst:
        # 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.
@@ -4562,61 +4496,51 @@ section with the top section on the section stack.
 
 File: as.info,  Node: Print,  Next: Protected,  Prev: Previous,  Up: Pseudo Ops
 
-7.89 `.print STRING'
+7.89 '.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: Secondary,  Prev: Print,  Up: Pseudo Ops
+File: as.info,  Node: Protected,  Next: Psize,  Prev: Print,  Up: Pseudo Ops
 
-7.90 `.protected NAMES'
+7.90 '.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: Secondary,  Next: Psize,  Prev: Protected,  Up: Pseudo Ops
+File: as.info,  Node: Psize,  Next: Purgem,  Prev: Protected,  Up: Pseudo Ops
 
-7.91 `.secondary NAMES'
-=======================
-
-This directive sets the secondary attribute on the comma separated list
-of symbol `names'.  If the symbols do not already exist, they will be
-created.
-
-
-File: as.info,  Node: Psize,  Next: Purgem,  Prev: Secondary,  Up: Pseudo Ops
-
-7.92 `.psize LINES , COLUMNS'
+7.91 '.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.93 `.purgem NAME'
+7.92 '.purgem NAME'
 ===================
 
 Undefine the macro NAME, so that later uses of the string will not be
@@ -4625,30 +4549,30 @@ expanded.  *Note Macro::.
 
 File: as.info,  Node: PushSection,  Next: Quad,  Prev: Purgem,  Up: Pseudo Ops
 
-7.94 `.pushsection NAME [, SUBSECTION] [, "FLAGS"[, @TYPE[,ARGUMENTS]]]'
+7.93 '.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.95 `.quad BIGNUMS'
+7.94 '.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.
@@ -4656,7 +4580,7 @@ hence _quad_-word for 8 bytes.
 
 File: as.info,  Node: Reloc,  Next: Rept,  Prev: Quad,  Up: Pseudo Ops
 
-7.96 `.reloc OFFSET, RELOC_NAME[, EXPRESSION]'
+7.95 '.reloc OFFSET, RELOC_NAME[, EXPRESSION]'
 ==============================================
 
 Generate a relocation at OFFSET of type RELOC_NAME with value
@@ -4672,11 +4596,11 @@ support addends stored in the section.
 
 File: as.info,  Node: Rept,  Next: Sbttl,  Prev: Reloc,  Up: Pseudo Ops
 
-7.97 `.rept COUNT'
+7.96 '.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
 
@@ -4693,7 +4617,7 @@ Repeat the sequence of lines between the `.rept' directive and the next
 
 File: as.info,  Node: Sbttl,  Next: Scl,  Prev: Rept,  Up: Pseudo Ops
 
-7.98 `.sbttl "SUBHEADING"'
+7.97 '.sbttl "SUBHEADING"'
 ==========================
 
 Use SUBHEADING as the title (third line, immediately after the title
@@ -4705,31 +4629,31 @@ if it appears within ten lines of the top of a page.
 
 File: as.info,  Node: Scl,  Next: Section,  Prev: Sbttl,  Up: Pseudo Ops
 
-7.99 `.scl CLASS'
+7.98 '.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.100 `.section NAME'
-=====================
+7.99 '.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"]
@@ -4738,134 +4662,111 @@ following ways:
    If the optional argument is quoted, it is taken as flags to use for
 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]]]
 
    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
 
    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
 
    Many targets only support the first three section types.
 
-   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.
 
-   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'.
-
-   If FLAGS contains the `G' symbol then the TYPE argument must be
+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
 present along with an additional field like this:
 
      .section NAME , "FLAGS"G, @TYPE, GROUPNAME[, LINKAGE]
@@ -4873,10 +4774,9 @@ present along with an additional field like this:
    The GROUPNAME field specifies the name of the section group to which
 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
@@ -4884,89 +4784,85 @@ Merge flag should come first, like this:
 
      .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...]
 
    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.101 `.set SYMBOL, EXPRESSION'
+7.100 '.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.
+   You may '.set' a symbol many times in the same assembly.
 
-   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.102 `.short EXPRESSIONS'
+7.101 '.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.103 `.single FLONUMS'
+7.102 '.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.104 `.size'
+7.103 '.size'
 =============
 
 This directive is used to set the size associated with a symbol.
@@ -4974,80 +4870,80 @@ This directive is used to set the size associated with a symbol.
 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.105 `.skip SIZE , FILL'
+7.104 '.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.106 `.sleb128 EXPRESSIONS'
+7.105 '.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.107 `.space SIZE , FILL'
+7.106 '.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.108 `.stabd, .stabn, .stabs'
+7.107 '.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
@@ -5060,43 +4956,44 @@ DESC
 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.109 `.string' "STR", `.string8' "STR", `.string16'
+7.108 '.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.
 
@@ -5109,117 +5006,116 @@ are stored in target endianness byte order.
 
 File: as.info,  Node: Struct,  Next: SubSection,  Prev: String,  Up: Pseudo Ops
 
-7.110 `.struct EXPRESSION'
+7.109 '.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.111 `.subsection NAME'
+7.110 '.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.112 `.symver'
+7.111 '.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.113 `.tag STRUCTNAME'
+7.112 '.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.114 `.text SUBSECTION'
+7.113 '.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.115 `.title "HEADING"'
+7.114 '.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.
@@ -5227,7 +5123,7 @@ if it appears within ten lines of the top of a page.
 
 File: as.info,  Node: Type,  Next: Uleb128,  Prev: Title,  Up: Pseudo Ops
 
-7.116 `.type'
+7.115 '.type'
 =============
 
 This directive is used to set the type of a symbol.
@@ -5235,8 +5131,8 @@ This directive is used to set the type of a symbol.
 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
 
@@ -5246,7 +5142,7 @@ entry.
 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
 
@@ -5255,12 +5151,12 @@ an object symbol.  There are five different syntaxes supported for the
 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:
 
@@ -5272,113 +5168,112 @@ assemble your code with other assemblers.
 
    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.117 `.uleb128 EXPRESSIONS'
+7.116 '.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.118 `.val ADDR'
+7.117 '.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.119 `.version "STRING"'
+7.118 '.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.120 `.vtable_entry TABLE, OFFSET'
+7.119 '.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.121 `.vtable_inherit CHILD, PARENT'
+7.120 '.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.122 `.warning "STRING"'
+7.121 '.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.123 `.weak NAMES'
+7.122 '.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
@@ -5388,15 +5283,15 @@ creates an alternate symbol to hold the default value.
 
 File: as.info,  Node: Weakref,  Next: Word,  Prev: Weak,  Up: Pseudo Ops
 
-7.124 `.weakref ALIAS, TARGET'
+7.123 '.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,
@@ -5411,7 +5306,7 @@ handled within the assembler.
 
 File: as.info,  Node: Word,  Next: Deprecated,  Prev: Weakref,  Up: Pseudo Ops
 
-7.125 `.word EXPRESSIONS'
+7.124 '.word EXPRESSIONS'
 =========================
 
 This directive expects zero or more EXPRESSIONS, of any section,
@@ -5427,37 +5322,34 @@ addressing, require the following special treatment.  If the machine of
 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'.
+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.
+   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: Deprecated,  Prev: Word,  Up: Pseudo Ops
 
-7.126 Deprecated Directives
+7.125 Deprecated Directives
 ===========================
 
 One day these directives won't work.  They are included for
 compatibility with older assemblers.
 .abort
-
 .line
 
 
@@ -5466,7 +5358,7 @@ File: as.info,  Node: Object Attributes,  Next: Machine Dependencies,  Prev: Pse
 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
@@ -5477,19 +5369,19 @@ objects are built for different generations of the same architecture,
 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.
+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:
@@ -5503,14 +5395,14 @@ File: as.info,  Node: GNU Object Attributes,  Next: Defining New Object Attribut
 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
 ---------------------------
@@ -5533,18 +5425,14 @@ Tag_GNU_MIPS_ABI_FP (4)
      be:
 
         * 0 for files not affected by the floating-point ABI.
-
         * 1 for files using the hardware floating-point 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 hardware floating-point ABI with 64-bit
-          wide double-precision floating-point registers and 32-bit
-          wide general purpose registers.
+          wide double-precision floating-point registers and 32-bit wide
+          general purpose registers.
 
 8.1.3 PowerPC Attributes
 ------------------------
@@ -5554,12 +5442,9 @@ Tag_GNU_Power_ABI_FP (4)
      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.
 
@@ -5567,11 +5452,8 @@ Tag_GNU_Power_ABI_Vector (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.
 
 
@@ -5582,19 +5464,14 @@ File: as.info,  Node: Defining New Object Attributes,  Prev: GNU Object Attribut
 
 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.
 
 
@@ -5604,10 +5481,10 @@ File: as.info,  Node: Machine Dependencies,  Next: Reporting Bugs,  Prev: Object
 ****************************
 
 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
@@ -5616,108 +5493,57 @@ subject, see the hardware manufacturer's manual.
 
 * 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
-
 * NiosII-Dependent::            Altera Nios II Dependent Features
-
 * NS32K-Dependent::		NS32K Dependent Features
-
 * SH-Dependent::                Renesas / SuperH SH Dependent Features
 * SH64-Dependent::              SuperH SH64 Dependent Features
-
 * PDP-11-Dependent::            PDP-11 Dependent Features
-
 * PJ-Dependent::                picoJava Dependent Features
-
 * PPC-Dependent::               PowerPC Dependent Features
-
 * RL78-Dependent::              RL78 Dependent Features
-
 * RX-Dependent::                RX Dependent Features
-
 * S/390-Dependent::             IBM S/390 Dependent Features
-
 * SCORE-Dependent::             SCORE 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
-
 * XGATE-Dependent::             XGATE Features
-
 * XSTORMY16-Dependent::         XStormy16 Dependent Features
-
 * Xtensa-Dependent::            Xtensa Dependent Features
-
 * Z80-Dependent::               Z80 Dependent Features
-
 * Z8000-Dependent::             Z8000 Dependent Features
-
 * Vax-Dependent::               VAX Dependent Features
 
 
@@ -5741,14 +5567,18 @@ File: as.info,  Node: AArch64 Options,  Next: AArch64 Syntax,  Up: AArch64-Depen
 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'
+     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'.
 
 
 File: as.info,  Node: AArch64 Syntax,  Next: AArch64 Floating Point,  Prev: AArch64 Options,  Up: AArch64-Dependent
@@ -5768,14 +5598,14 @@ File: as.info,  Node: AArch64-Chars,  Next: AArch64-Regs,  Up: AArch64 Syntax
 9.1.2.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
@@ -5783,8 +5613,8 @@ File: as.info,  Node: AArch64-Regs,  Next: AArch64-Relocations,  Prev: AArch64-C
 9.1.2.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 <http://infocenter.arm.com>.
 
 
 File: as.info,  Node: AArch64-Relocations,  Prev: AArch64-Regs,  Up: AArch64 Syntax
@@ -5792,20 +5622,20 @@ File: as.info,  Node: AArch64-Relocations,  Prev: AArch64-Regs,  Up: AArch64 Syn
 9.1.2.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
@@ -5815,7 +5645,7 @@ the address of FOO into x0:
              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
 
@@ -5837,34 +5667,34 @@ File: as.info,  Node: AArch64 Directives,  Next: AArch64 Opcodes,  Prev: AArch64
 9.1.4 AArch64 Machine Directives
 --------------------------------
 
-`.bss'
-     This directive switches to the `.bss' section.
+'.bss'
+     This directive switches to the '.bss' section.
 
-`.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.
 
-`.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
 
-`.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
@@ -5873,27 +5703,25 @@ File: as.info,  Node: AArch64 Directives,  Next: AArch64 Opcodes,  Prev: AArch64
      can be used to delete builtin in register name aliases (eg 'w0').
      This should only be done if it is really necessary.
 
-
 
 File: as.info,  Node: AArch64 Opcodes,  Next: AArch64 Mapping Symbols,  Prev: AArch64 Directives,  Up: AArch64-Dependent
 
 9.1.5 Opcodes
 -------------
 
-`as' implements all the standard AArch64 opcodes.  It also implements
+'as' implements all the standard AArch64 opcodes.  It also implements
 several pseudo opcodes, including several synthetic load instructions.
 
-`LDR ='
+'LDR ='
             ldr <register> , =<expression>
 
      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
+<http://infocenter.arm.com>.
 
 
 File: as.info,  Node: AArch64 Mapping Symbols,  Prev: AArch64 Opcodes,  Up: AArch64-Dependent
@@ -5904,13 +5732,12 @@ File: as.info,  Node: AArch64 Mapping Symbols,  Prev: AArch64 Opcodes,  Up: AArc
 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
 
@@ -5932,9 +5759,9 @@ File: as.info,  Node: Alpha Notes,  Next: Alpha Options,  Up: Alpha-Dependent
 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
@@ -5942,33 +5769,33 @@ File: as.info,  Node: Alpha Options,  Next: Alpha Syntax,  Prev: Alpha Notes,  U
 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
@@ -5976,25 +5803,25 @@ File: as.info,  Node: Alpha Options,  Next: Alpha Syntax,  Prev: Alpha Notes,  U
      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
+     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.
 
 
@@ -6019,12 +5846,12 @@ File: as.info,  Node: Alpha-Chars,  Next: Alpha-Regs,  Up: Alpha Syntax
 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
@@ -6032,11 +5859,11 @@ File: as.info,  Node: Alpha-Regs,  Next: Alpha-Relocs,  Prev: Alpha-Chars,  Up:
 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
@@ -6045,10 +5872,10 @@ File: as.info,  Node: Alpha-Relocs,  Prev: Alpha-Regs,  Up: Alpha Syntax
 ...................
 
 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.
 
@@ -6059,147 +5886,145 @@ instructions.
      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.
+'!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.
+'!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.
+'!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.
+'!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
@@ -6215,122 +6040,121 @@ File: as.info,  Node: Alpha Directives,  Next: Alpha Opcodes,  Prev: Alpha Float
 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
@@ -6372,14 +6196,14 @@ File: as.info,  Node: ARC Options,  Next: ARC Syntax,  Up: ARC-Dependent
 9.3.1 Options
 -------------
 
-`-marc[5|6|7|8]'
-     This option selects the core processor variant.  Using `-marc' is
-     the same as `-marc6', which is also the default.
+'-marc[5|6|7|8]'
+     This option selects the core processor variant.  Using '-marc' is
+     the same as '-marc6', which is also the default.
 
-    `arc5'
+     'arc5'
           Base instruction set.
 
-    `arc6'
+     'arc6'
           Jump-and-link (jl) instruction.  No requirement of an
           instruction between setting flags and conditional jump.  For
           example:
@@ -6387,26 +6211,24 @@ File: as.info,  Node: ARC Options,  Next: ARC Syntax,  Up: ARC-Dependent
                  mov.f r0,r1
                  beq   foo
 
-    `arc7'
+     'arc7'
           Break (brk) and sleep (sleep) instructions.
 
-    `arc8'
+     'arc8'
           Software interrupt (swi) instruction.
 
-
-     Note: the `.option' directive can to be used to select a core
+     Note: the '.option' directive 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.
 
-
 
 File: as.info,  Node: ARC Syntax,  Next: ARC Floating Point,  Prev: ARC Options,  Up: ARC-Dependent
 
@@ -6424,10 +6246,10 @@ File: as.info,  Node: ARC-Chars,  Next: ARC-Regs,  Up: ARC Syntax
 9.3.2.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.  Note that 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
+The presence of a '#' on a line indicates the start of a comment that
+extends to the end of the current line.  Note that 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::).
 
    The ARC assembler does not support a line separator character.
@@ -6447,7 +6269,7 @@ File: as.info,  Node: ARC Floating Point,  Next: ARC Directives,  Prev: ARC Synt
 --------------------
 
 The ARC core does not currently have hardware floating point support.
-Software floating point support is provided by `GCC' and uses IEEE
+Software floating point support is provided by 'GCC' and uses IEEE
 floating-point numbers.
 
 
@@ -6456,42 +6278,39 @@ File: as.info,  Node: ARC Directives,  Next: ARC Opcodes,  Prev: ARC Floating Po
 9.3.4 ARC Machine Directives
 ----------------------------
 
-The ARC version of `as' supports the following additional machine
+The ARC version of 'as' supports the following additional machine
 directives:
 
-`.2byte EXPRESSIONS'
+'.2byte EXPRESSIONS'
      *TODO*
 
-`.3byte EXPRESSIONS'
+'.3byte EXPRESSIONS'
      *TODO*
 
-`.4byte EXPRESSIONS'
+'.4byte EXPRESSIONS'
      *TODO*
 
-`.extAuxRegister NAME,ADDRESS,MODE'
+'.extAuxRegister NAME,ADDRESS,MODE'
      The ARCtangent A4 has extensible auxiliary register space.  The
      auxiliary registers can be defined in the assembler source code by
      using this directive.  The first parameter is the NAME of the new
      auxiallry register.  The second parameter is the ADDRESS of the
      register in the auxiliary register memory map for the variant of
-     the ARC.  The third parameter specifies the MODE in which the
+     the ARC. The third parameter specifies the MODE in which the
      register can be operated is and it can be one of:
 
-    `r          (readonly)'
-
-    `w          (write only)'
-
-    `r|w        (read or write)'
+     'r (readonly)'
+     'w (write only)'
+     'r|w (read or write)'
 
      For example:
 
             .extAuxRegister mulhi,0x12,w
 
-     This specifies an extension auxiliary register called _mulhi_
-     which is at address 0x12 in the memory space and which is only
-     writable.
+     This specifies an extension auxiliary register called _mulhi_ which
+     is at address 0x12 in the memory space and which is only writable.
 
-`.extCondCode SUFFIX,VALUE'
+'.extCondCode SUFFIX,VALUE'
      The condition codes on the ARCtangent A4 are extensible and can be
      specified by means of this assembler directive.  They are specified
      by the suffix and the value for the condition code.  They can be
@@ -6503,23 +6322,20 @@ directives:
              add.is_busy  r1,r2,r3
              bis_busy     _main
 
-`.extCoreRegister NAME,REGNUM,MODE,SHORTCUT'
+'.extCoreRegister NAME,REGNUM,MODE,SHORTCUT'
      Specifies an extension core register NAME for the application.
      This allows a register NAME with a valid REGNUM between 0 and 60,
      with the following as valid values for MODE
 
-    `_r_   (readonly)'
-
-    `_w_   (write only)'
-
-    `_r|w_ (read or write)'
+     '_r_ (readonly)'
+     '_w_ (write only)'
+     '_r|w_ (read or write)'
 
      The other parameter gives a description of the register having a
      SHORTCUT in the pipeline.  The valid values are:
 
-    `can_shortcut'
-
-    `cannot_shortcut'
+     'can_shortcut'
+     'cannot_shortcut'
 
      For example:
 
@@ -6528,15 +6344,15 @@ directives:
      This defines an extension core register mlo with the value 57 which
      can shortcut the pipeline.
 
-`.extInstruction NAME,OPCODE,SUBOPCODE,SUFFIXCLASS,SYNTAXCLASS'
+'.extInstruction NAME,OPCODE,SUBOPCODE,SUFFIXCLASS,SYNTAXCLASS'
      The ARCtangent A4 allows the user to specify extension
      instructions.  The extension instructions are not macros.  The
-     assembler creates encodings for use of these instructions
-     according to the specification by the user.  The parameters are:
+     assembler creates encodings for use of these instructions according
+     to the specification by the user.  The parameters are:
 
         * NAME Name of the extension instruction
 
-        * OPCODE Opcode to be used. (Bits 27:31 in the encoding).
+        * OPCODE Opcode to be used.  (Bits 27:31 in the encoding).
           Valid values 0x10-0x1f or 0x03
 
         * SUBOPCODE Subopcode to be used.  Valid values are from
@@ -6544,20 +6360,18 @@ directives:
           SYNTAXCLASS
 
         * SUFFIXCLASS Determines the kinds of suffixes to be allowed.
-          Valid values are `SUFFIX_NONE', `SUFFIX_COND', `SUFFIX_FLAG'
+          Valid values are 'SUFFIX_NONE', 'SUFFIX_COND', 'SUFFIX_FLAG'
           which indicates the absence or presence of conditional
-          suffixes and flag setting by the extension instruction.  It
-          is also possible to specify that an instruction sets the
-          flags and is conditional by using `SUFFIX_CODE' |
-          `SUFFIX_FLAG'.
+          suffixes and flag setting by the extension instruction.  It is
+          also possible to specify that an instruction sets the flags
+          and is conditional by using 'SUFFIX_CODE' | 'SUFFIX_FLAG'.
 
         * SYNTAXCLASS Determines the syntax class for the instruction.
           It can have the following values:
 
-         ``SYNTAX_2OP':'
+          'SYNTAX_2OP:'
                2 Operand Instruction
-
-         ``SYNTAX_3OP':'
+          'SYNTAX_3OP:'
                3 Operand Instruction
 
           In addition there could be modifiers for the syntax class as
@@ -6565,7 +6379,7 @@ directives:
 
                Syntax Class Modifiers are:
 
-             - `OP1_MUST_BE_IMM': Modifies syntax class SYNTAX_3OP,
+             - '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).  OP1_MUST_BE_IMM is used by bitwise ORing it
@@ -6573,7 +6387,7 @@ directives:
                could usually be used to set the flags using specific
                instructions and not retain results.
 
-             - `OP1_IMM_IMPLIED': Modifies syntax class SYNTAX_20P, it
+             - 'OP1_IMM_IMPLIED': Modifies syntax class SYNTAX_20P, it
                specifies 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:
@@ -6586,7 +6400,6 @@ directives:
                You use OP1_IMM_IMPLIED by bitwise ORing it with
                SYNTAX_20P.
 
-
      For example, defining 64-bit multiplier with immediate operands:
 
           .extInstruction mp64,0x14,0x0,SUFFIX_COND | SUFFIX_FLAG ,
@@ -6594,8 +6407,8 @@ directives:
 
      The above specifies an extension instruction called mp64 which has
      3 operands, sets the flags, can be used with a condition code, for
-     which the first operand is an immediate.  (Equivalent to
-     discarding the result of the operation).
+     which the first operand is an immediate.  (Equivalent to discarding
+     the result of the operation).
 
            .extInstruction mul64,0x14,0x00,SUFFIX_COND, SYNTAX_2OP|OP1_IMM_IMPLIED
 
@@ -6603,35 +6416,34 @@ directives:
      immediate operand.  The result of this operation would be
      discarded.
 
-`.half EXPRESSIONS'
+'.half EXPRESSIONS'
      *TODO*
 
-`.long EXPRESSIONS'
+'.long EXPRESSIONS'
      *TODO*
 
-`.option ARC|ARC5|ARC6|ARC7|ARC8'
-     The `.option' directive must be followed by the desired core
-     version. Again `arc' is an alias for `arc6'.
+'.option ARC|ARC5|ARC6|ARC7|ARC8'
+     The '.option' directive must be followed by the desired core
+     version.  Again 'arc' is an alias for 'arc6'.
 
-     Note: the `.option' directive overrides the command line option
-     `-marc'; a warning is emitted when the version is not consistent
+     Note: the '.option' directive overrides the command line option
+     '-marc'; a warning is emitted when the version is not consistent
      between the two - even for the implicit default core version
      (arc6).
 
-`.short EXPRESSIONS'
+'.short EXPRESSIONS'
      *TODO*
 
-`.word EXPRESSIONS'
+'.word EXPRESSIONS'
      *TODO*
 
-
 
 File: as.info,  Node: ARC Opcodes,  Prev: ARC Directives,  Up: ARC-Dependent
 
 9.3.5 Opcodes
 -------------
 
-For information on the ARC instruction set, see `ARC Programmers
+For information on the ARC instruction set, see 'ARC Programmers
 Reference Manual', ARC International (www.arc.com)
 
 
@@ -6656,96 +6468,97 @@ File: as.info,  Node: ARM Options,  Next: ARM Syntax,  Up: ARM-Dependent
 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-r4', `cortex-r4f', `cortex-r5',
-     `cortex-r7', `cortex-m4', `cortex-m3', `cortex-m1', `cortex-m0',
-     `cortex-m0plus', `ep9312' (ARM920 with Cirrus Maverick
-     coprocessor), `i80200' (Intel XScale processor) `iwmmxt' (Intel(r)
+     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-r4', 'cortex-r4f', 'cortex-r5', 'cortex-r7',
+     'cortex-m4', 'cortex-m3', 'cortex-m1', 'cortex-m0',
+     'cortex-m0plus', '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
+     '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: `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: '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', `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'), and `xscale'.
-
-`-march=ARCHITECTURE[+EXTENSION...]'
+     'iwmmxt', 'iwmmxt2', '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'), and 'xscale'.
+
+'-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', `armv6zk',
-     `armv6-m', `armv6s-m', `armv7', `armv7-a', `armv7-r', `armv7-m',
-     `armv7e-m', `armv8-a', `iwmmxt' 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', 'armv6zk',
+     'armv6-m', 'armv6s-m', 'armv7', 'armv7-a', 'armv7ve', 'armv7-r',
+     'armv7-m', 'armv7e-m', 'armv8-a', 'iwmmxt' 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', `fp-armv8', `arm1020t', `arm1020e', `arm1136jf-s',
-     `maverick', `neon', `neon-vfpv4', `neon-fp-armv8', and
-     `crypto-neon-fp-armv8'.
+     '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', 'fp-armv8', 'arm1020t', 'arm1020e', 'arm1136jf-s',
+     'maverick', 'neon', 'neon-vfpv4', 'neon-fp-armv8', and
+     'crypto-neon-fp-armv8'.
 
      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
@@ -6753,86 +6566,85 @@ File: as.info,  Node: ARM Options,  Next: ARM Syntax,  Up: ARM-Dependent
      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.
 
-`-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.
 
-
 
 File: as.info,  Node: ARM Syntax,  Next: ARM Floating Point,  Prev: ARM Options,  Up: ARM-Dependent
 
@@ -6854,29 +6666,28 @@ File: as.info,  Node: ARM-Instruction-Set,  Next: ARM-Chars,  Up: ARM Syntax
 ..............................
 
 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.
 
 
@@ -6885,18 +6696,18 @@ File: as.info,  Node: ARM-Chars,  Next: ARM-Regs,  Prev: ARM-Instruction-Set,  U
 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.
 
@@ -6919,19 +6730,19 @@ name in parentheses after the symbol name.  For example:
 
              .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.
+'(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:
+   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
@@ -6943,9 +6754,9 @@ File: as.info,  Node: ARM-Neon-Alignment,  Prev: ARM-Relocations,  Up: ARM Synta
 .................................
 
 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]
 
@@ -6963,71 +6774,71 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
 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.
 
-`.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.
 
-`.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
@@ -7038,135 +6849,134 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
 
                   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'
-
-     The VALUE is either a `number', `"string"', or `number, "string"'
+     '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"'
      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.
@@ -7190,13 +7000,13 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
             .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
@@ -7204,44 +7014,44 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
           .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.
 
-`.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
@@ -7250,18 +7060,18 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
      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}
@@ -7271,36 +7081,35 @@ File: as.info,  Node: ARM Directives,  Next: ARM Opcodes,  Prev: ARM Floating Po
             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 <register> , = <expression>
 
      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 <register> <label>
 
      This instruction will load the address of LABEL into the indicated
@@ -7310,7 +7119,7 @@ several pseudo opcodes, including several synthetic load instructions.
      (and section) as the ADR instruction, then an error will be
      generated.  This instruction will not make use of the literal pool.
 
-`ADRL'
+'ADRL'
             adrl <register> <label>
 
      This instruction will load the address of LABEL into the indicated
@@ -7324,8 +7133,7 @@ several pseudo opcodes, including several synthetic load instructions.
      file (and section) as the ADRL instruction, then an error will be
      generated.  This instruction will not make use of the literal pool.
 
-
-   For information on the ARM or Thumb instruction sets, see `ARM
+   For information on the ARM or Thumb instruction sets, see 'ARM
 Software Development Toolkit Reference Manual', Advanced RISC Machines
 Ltd.
 
@@ -7335,24 +7143,23 @@ File: as.info,  Node: ARM Mapping Symbols,  Next: ARM Unwinding Tutorial,  Prev:
 9.4.6 Mapping Symbols
 ---------------------
 
-The ARM ELF specification requires that special symbols be inserted
-into object files to mark certain features:
+The ARM ELF specification requires that special symbols be inserted into
+object files to mark certain features:
 
-`$a'
+'$a'
      At the start of a region of code containing ARM instructions.
 
-`$t'
+'$t'
      At the start of a region of code containing THUMB instructions.
 
-`$d'
+'$d'
      At the start of a region of data.
 
-
    The assembler will automatically insert these symbols for you - there
 is no need to code them yourself.  Support for tagging symbols ($b, $f,
 $p and $m) which is also mentioned in the current ARM ELF specification
-is not implemented.  This is because they have been dropped from the
-new EABI and so tools cannot rely upon their presence.
+is not implemented.  This is because they have been dropped from the new
+EABI and so tools cannot rely upon their presence.
 
 
 File: as.info,  Node: ARM Unwinding Tutorial,  Prev: ARM Mapping Symbols,  Up: ARM-Dependent
@@ -7366,12 +7173,12 @@ exception is thrown to determine where control should be transferred.
 In particular, the unwind information is used to determine which
 function called the function that threw the exception, and which
 function called that one, and so forth.  This information is also used
-to restore the values of callee-saved registers in the function
-catching the exception.
+to restore the values of callee-saved registers in the function catching
+the exception.
 
    If you are writing functions in assembly code, and those functions
-call other functions that throw exceptions, you must use assembly
-pseudo ops to ensure that appropriate exception unwind information is
+call other functions that throw exceptions, you must use assembly pseudo
+ops to ensure that appropriate exception unwind information is
 generated.  Otherwise, if one of the functions called by your assembly
 code throws an exception, the run-time library will be unable to unwind
 the stack through your assembly code and your program will not behave
@@ -7431,64 +7238,63 @@ that are used to generate unwind information.
 
    An important assumption made by the unwinder is that the stack frame
 does not change during the body of the function.  In particular, since
-we assume that the assembly code does not itself throw an exception,
-the only point where an exception can be thrown is from a call, such as
-the `bl' instruction above.  At each call site, the same saved
-registers (including `lr', which indicates the return address) must be
-located in the same locations relative to the frame pointer.
+we assume that the assembly code does not itself throw an exception, the
+only point where an exception can be thrown is from a call, such as the
+'bl' instruction above.  At each call site, the same saved registers
+(including 'lr', which indicates the return address) must be located in
+the same locations relative to the frame pointer.
 
-   The `.fnstart' (*note .fnstart pseudo op: arm_fnstart.) pseudo op
+   The '.fnstart' (*note .fnstart pseudo op: arm_fnstart.) pseudo op
 appears immediately before the first instruction of the function while
-the `.fnend' (*note .fnend pseudo op: arm_fnend.) pseudo op appears
+the '.fnend' (*note .fnend pseudo op: arm_fnend.) pseudo op appears
 immediately after the last instruction of the function.  These pseudo
 ops specify the range of the function.
 
-   Only the order of the other pseudos ops (e.g., `.setfp' or `.pad')
+   Only the order of the other pseudos ops (e.g., '.setfp' or '.pad')
 matters; their exact locations are irrelevant.  In the example above,
 the compiler emits the pseudo ops with particular instructions.  That
 makes it easier to understand the code, but it is not required for
 correctness.  It would work just as well to emit all of the pseudo ops
-other than `.fnend' in the same order, but immediately after `.fnstart'.
-
-   The `.save' (*note .save pseudo op: arm_save.) pseudo op indicates
-registers that have been saved to the stack so that they can be
-restored before the function returns.  The argument to the `.save'
-pseudo op is a list of registers to save.  If a register is
-"callee-saved" (as specified by the ABI) and is modified by the
-function you are writing, then your code must save the value before it
-is modified and restore the original value before the function returns.
-If an exception is thrown, the run-time library restores the values of
-these registers from their locations on the stack before returning
-control to the exception handler.  (Of course, if an exception is not
-thrown, the function that contains the `.save' pseudo op restores these
-registers in the function epilogue, as is done with the `ldmfd'
-instruction above.)
+other than '.fnend' in the same order, but immediately after '.fnstart'.
+
+   The '.save' (*note .save pseudo op: arm_save.) pseudo op indicates
+registers that have been saved to the stack so that they can be restored
+before the function returns.  The argument to the '.save' pseudo op is a
+list of registers to save.  If a register is "callee-saved" (as
+specified by the ABI) and is modified by the function you are writing,
+then your code must save the value before it is modified and restore the
+original value before the function returns.  If an exception is thrown,
+the run-time library restores the values of these registers from their
+locations on the stack before returning control to the exception
+handler.  (Of course, if an exception is not thrown, the function that
+contains the '.save' pseudo op restores these registers in the function
+epilogue, as is done with the 'ldmfd' instruction above.)
 
    You do not have to save callee-saved registers at the very beginning
-of the function and you do not need to use the `.save' pseudo op
+of the function and you do not need to use the '.save' pseudo op
 immediately following the point at which the registers are saved.
 However, if you modify a callee-saved register, you must save it on the
 stack before modifying it and before calling any functions which might
-throw an exception.  And, you must use the `.save' pseudo op to
-indicate that you have done so.
+throw an exception.  And, you must use the '.save' pseudo op to indicate
+that you have done so.
 
-   The `.pad' (*note .pad: arm_pad.) pseudo op indicates a modification
+   The '.pad' (*note .pad: arm_pad.) pseudo op indicates a modification
 of the stack pointer that does not save any registers.  The argument is
 the number of bytes (in decimal) that are subtracted from the stack
 pointer.  (On ARM CPUs, the stack grows downwards, so subtracting from
 the stack pointer increases the size of the stack.)
 
-   The `.setfp' (*note .setfp pseudo op: arm_setfp.) pseudo op
-indicates the register that contains the frame pointer.  The first
-argument is the register that is set, which is typically `fp'.  The
-second argument indicates the register from which the frame pointer
-takes its value.  The third argument, if present, is the value (in
-decimal) added to the register specified by the second argument to
-compute the value of the frame pointer.  You should not modify the
-frame pointer in the body of the function.
+   The '.setfp' (*note .setfp pseudo op: arm_setfp.) pseudo op indicates
+the register that contains the frame pointer.  The first argument is the
+register that is set, which is typically 'fp'.  The second argument
+indicates the register from which the frame pointer takes its value.
+The third argument, if present, is the value (in decimal) added to the
+register specified by the second argument to compute the value of the
+frame pointer.  You should not modify the frame pointer in the body of
+the function.
 
    If you do not use a frame pointer, then you should not use the
-`.setfp' pseudo op.  If you do not use a frame pointer, then you should
+'.setfp' pseudo op.  If you do not use a frame pointer, then you should
 avoid modifying the stack pointer outside of the function prologue.
 Otherwise, the run-time library will be unable to find saved registers
 when it is unwinding the stack.
@@ -7496,8 +7302,8 @@ when it is unwinding the stack.
    The pseudo ops described above are sufficient for writing assembly
 code that calls functions which may throw exceptions.  If you need to
 know more about the object-file format used to represent unwind
-information, you may consult the `Exception Handling ABI for the ARM
-Architecture' available from `http://infocenter.arm.com'.
+information, you may consult the 'Exception Handling ABI for the ARM
+Architecture' available from <http://infocenter.arm.com>.
 
 
 File: as.info,  Node: AVR-Dependent,  Next: Blackfin-Dependent,  Prev: ARM-Dependent,  Up: Machine Dependencies
@@ -7517,7 +7323,7 @@ File: as.info,  Node: AVR Options,  Next: AVR Syntax,  Up: AVR-Dependent
 9.5.1 Options
 -------------
 
-`-mmcu=MCU'
+'-mmcu=MCU'
      Specify ATMEL AVR instruction set or MCU type.
 
      Instruction set avr1 is for the minimal AVR core, not supported by
@@ -7535,13 +7341,13 @@ File: as.info,  Node: AVR Options,  Next: AVR Syntax,  Up: AVR-Dependent
      attiny4313, attiny44, attiny44a, attiny84, attiny84a, attiny25,
      attiny45, attiny85, attiny261, attiny261a, attiny461, attiny461a,
      attiny861, attiny861a, attiny87, attiny43u, attiny48, attiny88,
-     at86rf401, ata6289).
+     at86rf401).
 
      Instruction set avr3 is for the classic AVR core with up to 128K
      program memory space (MCU types: at43usb355, at76c711).
 
-     Instruction set avr31 is for the classic AVR core with exactly
-     128K program memory space (MCU types: atmega103, at43usb320).
+     Instruction set avr31 is for the classic AVR core with exactly 128K
+     program memory space (MCU types: atmega103, at43usb320).
 
      Instruction set avr35 is for classic AVR core plus MOVW, CALL, and
      JMP instructions (MCU types: attiny167, at90usb82, at90usb162,
@@ -7551,7 +7357,7 @@ File: as.info,  Node: AVR Options,  Next: AVR Syntax,  Up: AVR-Dependent
      program memory space (MCU types: atmega48, atmega48a, atmega48p,
      atmega8, atmega88, atmega88a, atmega88p, atmega88pa, atmega8515,
      atmega8535, atmega8hva, at90pwm1, at90pwm2, at90pwm2b, at90pwm3,
-     at90pwm3b, at90pwm81).
+     at90pwm3b, at90pwm81, ata6289).
 
      Instruction set avr5 is for the enhanced AVR core with up to 128K
      program memory space (MCU types: atmega16, atmega16a, atmega161,
@@ -7598,25 +7404,24 @@ File: as.info,  Node: AVR Options,  Next: AVR Syntax,  Up: AVR-Dependent
      program memory space and greater than 64K data space (MCU types:
      atxmega64a1, atxmega64a1u).
 
-     Instruction set avrxmega6 is for the XMEGA AVR core with up to
-     256K program memory space and less than 64K data space (MCU types:
+     Instruction set avrxmega6 is for the XMEGA AVR core with up to 256K
+     program memory space and less than 64K data space (MCU types:
      atxmega128a3, atxmega128d3, atxmega192a3, atxmega128b1,
      atxmega192d3, atxmega256a3, atxmega256a3b, atxmega256a3bu,
      atxmega192d3).
 
-     Instruction set avrxmega7 is for the XMEGA AVR core with up to
-     256K program memory space and greater than 64K data space (MCU
-     types: atxmega128a1, atxmega128a1u).
+     Instruction set avrxmega7 is for the XMEGA AVR core with up to 256K
+     program memory space and greater than 64K data space (MCU types:
+     atxmega128a1, atxmega128a1u).
 
-`-mall-opcodes'
-     Accept all AVR opcodes, even if not supported by `-mmcu'.
+'-mall-opcodes'
+     Accept all AVR opcodes, even if not supported by '-mmcu'.
 
-`-mno-skip-bug'
+'-mno-skip-bug'
      This option disable warnings for skipping two-word instructions.
 
-`-mno-wrap'
-     This option reject `rjmp/rcall' instructions with 8K wrap-around.
-
+'-mno-wrap'
+     This option reject 'rjmp/rcall' instructions with 8K wrap-around.
 
 
 File: as.info,  Node: AVR Syntax,  Next: AVR Opcodes,  Prev: AVR Options,  Up: AVR-Dependent
@@ -7636,15 +7441,15 @@ File: as.info,  Node: AVR-Chars,  Next: AVR-Regs,  Up: AVR Syntax
 9.5.2.1 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, the whole line is
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can 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.
 
 
@@ -7653,12 +7458,12 @@ File: as.info,  Node: AVR-Regs,  Next: AVR-Modifiers,  Prev: AVR-Chars,  Up: AVR
 9.5.2.2 Register Names
 ......................
 
-The AVR has 32 x 8-bit general purpose working registers `r0', `r1',
-... `r31'.  Six of the 32 registers can be used as three 16-bit
-indirect address register pointers for Data Space addressing. One of
-the these address pointers can also be used as an address pointer for
-look up tables in Flash program memory. These added function registers
-are the 16-bit `X', `Y' and `Z' - registers.
+The AVR has 32 x 8-bit general purpose working registers 'r0', 'r1', ...
+'r31'.  Six of the 32 registers can be used as three 16-bit indirect
+address register pointers for Data Space addressing.  One of the these
+address pointers can also be used as an address pointer for look up
+tables in Flash program memory.  These added function registers are the
+16-bit 'X', 'Y' and 'Z' - registers.
 
      X = r26:r27
      Y = r28:r29
@@ -7676,33 +7481,37 @@ following:
 
      modifier(relocatable-expression)
 
-`lo8'
+'lo8'
+
      This modifier allows you to use bits 0 through 7 of an address
      expression as 8 bit relocatable expression.
 
-`hi8'
+'hi8'
+
      This modifier allows you to use bits 7 through 15 of an address
      expression as 8 bit relocatable expression.  This is useful with,
-     for example, the AVR `ldi' instruction and `lo8' modifier.
+     for example, the AVR 'ldi' instruction and 'lo8' modifier.
 
      For example
 
           ldi r26, lo8(sym+10)
           ldi r27, hi8(sym+10)
 
-`hh8'
+'hh8'
+
      This modifier allows you to use bits 16 through 23 of an address
      expression as 8 bit relocatable expression.  Also, can be useful
      for loading 32 bit constants.
 
-`hlo8'
-     Synonym of `hh8'.
+'hlo8'
+
+     Synonym of 'hh8'.
 
-`hhi8'
-     This modifier allows you to use bits 24 through 31 of an
-     expression as 8 bit expression. This is useful with, for example,
-     the AVR `ldi' instruction and `lo8', `hi8', `hlo8', `hhi8',
-     modifier.
+'hhi8'
+
+     This modifier allows you to use bits 24 through 31 of an expression
+     as 8 bit expression.  This is useful with, for example, the AVR
+     'ldi' instruction and 'lo8', 'hi8', 'hlo8', 'hhi8', modifier.
 
      For example
 
@@ -7712,23 +7521,25 @@ following:
           ldi r29, hhi8(285774925)
           ; r29,r28,r27,r26 = 285774925
 
-`pm_lo8'
+'pm_lo8'
+
      This modifier allows you to use bits 0 through 7 of an address
      expression as 8 bit relocatable expression.  This modifier useful
-     for addressing data or code from Flash/Program memory. The using
-     of `pm_lo8' similar to `lo8'.
+     for addressing data or code from Flash/Program memory.  The using
+     of 'pm_lo8' similar to 'lo8'.
+
+'pm_hi8'
 
-`pm_hi8'
      This modifier allows you to use bits 8 through 15 of an address
      expression as 8 bit relocatable expression.  This modifier useful
      for addressing data or code from Flash/Program memory.
 
-`pm_hh8'
+'pm_hh8'
+
      This modifier allows you to use bits 15 through 23 of an address
      expression as 8 bit relocatable expression.  This modifier useful
      for addressing data or code from Flash/Program memory.
 
-
 
 File: as.info,  Node: AVR Opcodes,  Prev: AVR Syntax,  Up: AVR-Dependent
 
@@ -7736,17 +7547,17 @@ File: as.info,  Node: AVR Opcodes,  Prev: AVR Syntax,  Up: AVR-Dependent
 -------------
 
 For detailed information on the AVR machine instruction set, see
-`www.atmel.com/products/AVR'.
+<www.atmel.com/products/AVR>.
 
-   `as' implements all the standard AVR opcodes.  The following table
+   'as' implements all the standard AVR opcodes.  The following table
 summarizes the AVR opcodes, and their arguments.
 
      Legend:
         r   any register
-        d   `ldi' register (r16-r31)
-        v   `movw' even register (r0, r2, ..., r28, r30)
-        a   `fmul' register (r16-r23)
-        w   `adiw' register (r24,r26,r28,r30)
+        d   'ldi' register (r16-r31)
+        v   'movw' even register (r0, r2, ..., r28, r30)
+        a   'fmul' register (r16-r23)
+        w   'adiw' register (r24,r26,r28,r30)
         e   pointer registers (X,Y,Z)
         b   base pointer register and displacement ([YZ]+disp)
         z   Z pointer register (for [e]lpm Rd,Z[+])
@@ -7755,7 +7566,7 @@ summarizes the AVR opcodes, and their arguments.
         s   immediate value from 0 to 7
         P   Port address value from 0 to 63. (in, out)
         p   Port address value from 0 to 31. (cbi, sbi, sbic, sbis)
-        K   immediate value from 0 to 63 (used in `adiw', `sbiw')
+        K   immediate value from 0 to 63 (used in 'adiw', 'sbiw')
         i   immediate value
         l   signed pc relative offset from -64 to 63
         L   signed pc relative offset from -2048 to 2047
@@ -7898,24 +7709,24 @@ File: as.info,  Node: Blackfin Options,  Next: Blackfin Syntax,  Up: Blackfin-De
 9.6.1 Options
 -------------
 
-`-mcpu=PROCESSOR[-SIREVISION]'
+'-mcpu=PROCESSOR[-SIREVISION]'
      This option specifies the target processor.  The optional
      SIREVISION is not used in assembler.  It's here such that GCC can
-     easily pass down its `-mcpu=' option.  The assembler will issue an
+     easily pass down its '-mcpu=' option.  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: `bf504', `bf506', `bf512', `bf514',
-     `bf516', `bf518', `bf522', `bf523', `bf524', `bf525', `bf526',
-     `bf527', `bf531', `bf532', `bf533', `bf534', `bf535' (not
-     implemented yet), `bf536', `bf537', `bf538', `bf539', `bf542',
-     `bf542m', `bf544', `bf544m', `bf547', `bf547m', `bf548', `bf548m',
-     `bf549', `bf549m', `bf561', and `bf592'.
-
-`-mfdpic'
+     processor names are recognized: 'bf504', 'bf506', 'bf512', 'bf514',
+     'bf516', 'bf518', 'bf522', 'bf523', 'bf524', 'bf525', 'bf526',
+     'bf527', 'bf531', 'bf532', 'bf533', 'bf534', 'bf535' (not
+     implemented yet), 'bf536', 'bf537', 'bf538', 'bf539', 'bf542',
+     'bf542m', 'bf544', 'bf544m', 'bf547', 'bf547m', 'bf548', 'bf548m',
+     'bf549', 'bf549m', 'bf561', and 'bf592'.
+
+'-mfdpic'
      Assemble for the FDPIC ABI.
 
-`-mno-fdpic'
-`-mnopic'
+'-mno-fdpic'
+'-mnopic'
      Disable -mfdpic.
 
 
@@ -7924,7 +7735,7 @@ File: as.info,  Node: Blackfin Syntax,  Next: Blackfin Directives,  Prev: Blackf
 9.6.2 Syntax
 ------------
 
-`Special Characters'
+'Special Characters'
      Assembler input is free format and may appear anywhere on the line.
      One instruction may extend across multiple lines or more than one
      instruction may appear on the same line.  White space (space, tab,
@@ -7933,14 +7744,14 @@ File: as.info,  Node: Blackfin Syntax,  Next: Blackfin Directives,  Prev: Blackf
      names, keywords, user identifiers, and also some multicharacter
      special symbols like "+=", "/*" or "||".
 
-     Comments are introduced by the `#' character and extend to the end
-     of the current line.  If the `#' appears as the first character of
+     Comments are introduced by the '#' character and extend to the end
+     of the current line.  If the '#' appears as the first character of
      a line, the whole line is treated as a comment, but in this case
      the line can also be a logical line number directive (*note
      Comments::) or a preprocessor control command (*note
      Preprocessing::).
 
-`Instruction Delimiting'
+'Instruction Delimiting'
      A semicolon must terminate every instruction.  Sometimes a complete
      instruction will consist of more than one operation.  There are two
      cases where this occurs.  The first is when two general operations
@@ -7958,7 +7769,8 @@ File: as.info,  Node: Blackfin Syntax,  Next: Blackfin Directives,  Prev: Blackf
      Multiple instructions can occur on the same line.  Each must be
      terminated by a semicolon character.
 
-`Register Names'
+'Register Names'
+
      The assembler treats register names and instruction keywords in a
      case insensitive manner.  User identifiers are case sensitive.
      Thus, R3.l, R3.L, r3.l and r3.L are all equivalent input to the
@@ -7975,104 +7787,100 @@ File: as.info,  Node: Blackfin Syntax,  Next: Blackfin Directives,  Prev: Blackf
 
      Some instructions (such as -SP (Push Multiple)) require a group of
      adjacent registers.  Adjacent registers are denoted in the syntax
-     by the range enclosed in parentheses and separated by a colon,
-     eg., (R7:3).  Again, the larger number appears first.
+     by the range enclosed in parentheses and separated by a colon, eg.,
+     (R7:3).  Again, the larger number appears first.
 
      Portions of a particular register may be individually specified.
-     This is written with a dot (".") following the register name and
+     This is written with a dot (".")  following the register name and
      then a letter denoting the desired portion.  For 32-bit registers,
      ".H" denotes the most significant ("High") portion.  ".L" denotes
      the least-significant portion.  The subdivisions of the 40-bit
      registers are described later.
 
-`Accumulators'
+'Accumulators'
      The set of 40-bit registers A1 and A0 that normally contain data
      that is being manipulated.  Each accumulator can be accessed in
      four ways.
 
-    `one 40-bit register'
+     'one 40-bit register'
           The register will be referred to as A1 or A0.
-
-    `one 32-bit register'
+     'one 32-bit register'
           The registers are designated as A1.W or A0.W.
-
-    `two 16-bit registers'
+     'two 16-bit registers'
           The registers are designated as A1.H, A1.L, A0.H or A0.L.
-
-    `one 8-bit register'
+     'one 8-bit register'
           The registers are designated as A1.X or A0.X for the bits that
           extend beyond bit 31.
 
-`Data Registers'
+'Data Registers'
      The set of 32-bit registers (R0, R1, R2, R3, R4, R5, R6 and R7)
-     that normally contain data for manipulation.  These are
-     abbreviated as D-register or Dreg.  Data registers can be accessed
-     as 32-bit registers or as two independent 16-bit registers.  The
-     least significant 16 bits of each register is called the "low"
-     half and is designated with ".L" following the register name.  The
-     most significant 16 bits are called the "high" half and is
-     designated with ".H" following the name.
+     that normally contain data for manipulation.  These are abbreviated
+     as D-register or Dreg.  Data registers can be accessed as 32-bit
+     registers or as two independent 16-bit registers.  The least
+     significant 16 bits of each register is called the "low" half and
+     is designated with ".L" following the register name.  The most
+     significant 16 bits are called the "high" half and is designated
+     with ".H" following the name.
 
              R7.L, r2.h, r4.L, R0.H
 
-`Pointer Registers'
+'Pointer Registers'
      The set of 32-bit registers (P0, P1, P2, P3, P4, P5, SP and FP)
      that normally contain byte addresses of data structures.  These are
      abbreviated as P-register or Preg.
 
           p2, p5, fp, sp
 
-`Stack Pointer SP'
+'Stack Pointer SP'
      The stack pointer contains the 32-bit address of the last occupied
      byte location in the stack.  The stack grows by decrementing the
      stack pointer.
 
-`Frame Pointer FP'
+'Frame Pointer FP'
      The frame pointer contains the 32-bit address of the previous frame
      pointer in the stack.  It is located at the top of a frame.
 
-`Loop Top'
-     LT0 and LT1.  These registers contain the 32-bit address of the
-     top of a zero overhead loop.
+'Loop Top'
+     LT0 and LT1.  These registers contain the 32-bit address of the top
+     of a zero overhead loop.
 
-`Loop Count'
+'Loop Count'
      LC0 and LC1.  These registers contain the 32-bit counter of the
      zero overhead loop executions.
 
-`Loop Bottom'
+'Loop Bottom'
      LB0 and LB1.  These registers contain the 32-bit address of the
      bottom of a zero overhead loop.
 
-`Index Registers'
+'Index Registers'
      The set of 32-bit registers (I0, I1, I2, I3) that normally contain
      byte addresses of data structures.  Abbreviated I-register or Ireg.
 
-`Modify Registers'
+'Modify Registers'
      The set of 32-bit registers (M0, M1, M2, M3) that normally contain
      offset values that are added and subtracted to one of the index
      registers.  Abbreviated as Mreg.
 
-`Length Registers'
+'Length Registers'
      The set of 32-bit registers (L0, L1, L2, L3) that normally contain
      the length in bytes of the circular buffer.  Abbreviated as Lreg.
-     Clear the Lreg to disable circular addressing for the
-     corresponding Ireg.
+     Clear the Lreg to disable circular addressing for the corresponding
+     Ireg.
 
-`Base Registers'
+'Base Registers'
      The set of 32-bit registers (B0, B1, B2, B3) that normally contain
      the base address in bytes of the circular buffer.  Abbreviated as
      Breg.
 
-`Floating Point'
+'Floating Point'
      The Blackfin family has no hardware floating point but the .float
      directive generates ieee floating point numbers for use with
      software floating point libraries.
 
-`Blackfin Opcodes'
+'Blackfin Opcodes'
      For detailed information on the Blackfin machine instruction set,
      see the Blackfin(r) Processor Instruction Set Reference.
 
-
 
 File: as.info,  Node: Blackfin Directives,  Prev: Blackfin Syntax,  Up: Blackfin-Dependent
 
@@ -8082,32 +7890,27 @@ File: as.info,  Node: Blackfin Directives,  Prev: Blackfin Syntax,  Up: Blackfin
 The following directives are provided for compatibility with the VDSP
 assembler.
 
-`.byte2'
+'.byte2'
      Initializes a two byte data object.
 
-     This maps to the `.short' directive.
-
-`.byte4'
+     This maps to the '.short' directive.
+'.byte4'
      Initializes a four byte data object.
 
-     This maps to the `.int' directive.
-
-`.db'
+     This maps to the '.int' directive.
+'.db'
      Initializes a single byte data object.
 
-     This directive is a synonym for `.byte'.
-
-`.dw'
+     This directive is a synonym for '.byte'.
+'.dw'
      Initializes a two byte data object.
 
-     This directive is a synonym for `.byte2'.
-
-`.dd'
+     This directive is a synonym for '.byte2'.
+'.dd'
      Initializes a four byte data object.
 
-     This directive is a synonym for `.byte4'.
-
-`.var'
+     This directive is a synonym for '.byte4'.
+'.var'
      Define and initialize a 32 bit data object.
 
 
@@ -8127,91 +7930,85 @@ File: as.info,  Node: CR16 Operand Qualifiers,  Next: CR16 Syntax,  Up: CR16-Dep
 9.7.1 CR16 Operand Qualifiers
 -----------------------------
 
-The National Semiconductor CR16 target of `as' has a few machine
+The National Semiconductor CR16 target of 'as' has a few machine
 dependent operand qualifiers.
 
    Operand expression type qualifier is an optional field in the
 instruction operand, to determines the type of the expression field of
-an operand. The `@' is required. CR16 architecture uses one of the
+an operand.  The '@' is required.  CR16 architecture uses one of the
 following expression qualifiers:
 
-`s'
-     - `Specifies expression operand type as small'
-
-`m'
-     - `Specifies expression operand type as medium'
-
-`l'
-     - `Specifies expression operand type as large'
-
-`c'
-     - `Specifies the CR16 Assembler generates a relocation entry for
+'s'
+     - 'Specifies expression operand type as small'
+'m'
+     - 'Specifies expression operand type as medium'
+'l'
+     - 'Specifies expression operand type as large'
+'c'
+     - 'Specifies the CR16 Assembler generates a relocation entry for
      the operand, where pc has implied bit, the expression is adjusted
      accordingly. The linker uses the relocation entry to update the
      operand address at link time.'
-
-`got/GOT'
-     - `Specifies the CR16 Assembler generates a relocation entry for
+'got/GOT'
+     - 'Specifies the CR16 Assembler generates a relocation entry for
      the operand, offset from Global Offset Table. The linker uses this
      relocation entry to update the operand address at link time'
-
-`cgot/cGOT'
-     - `Specifies the CompactRISC Assembler generates a relocation
-     entry for the operand, where pc has implied bit, the expression is
+'cgot/cGOT'
+     - 'Specifies the CompactRISC Assembler generates a relocation entry
+     for the operand, where pc has implied bit, the expression is
      adjusted accordingly. The linker uses the relocation entry to
      update the operand address at link time.'
 
    CR16 target operand qualifiers and its size (in bits):
 
-`Immediate Operand: s'
+'Immediate Operand: s'
      4 bits.
 
-`Immediate Operand: m'
+'Immediate Operand: m'
      16 bits, for movb and movw instructions.
 
-`Immediate Operand: m'
+'Immediate Operand: m'
      20 bits, movd instructions.
 
-`Immediate Operand: l'
+'Immediate Operand: l'
      32 bits.
 
-`Absolute Operand: s'
+'Absolute Operand: s'
      Illegal specifier for this operand.
 
-`Absolute Operand: m'
+'Absolute Operand: m'
      20 bits, movd instructions.
 
-`Displacement Operand: s'
+'Displacement Operand: s'
      8 bits.
 
-`Displacement Operand: m'
+'Displacement Operand: m'
      16 bits.
 
-`Displacement Operand: l'
+'Displacement Operand: l'
      24 bits.
 
-
    For example:
-     1   `movw $_myfun@c,r1'
+     1   movw $_myfun@c,r1
 
          This loads the address of _myfun, shifted right by 1, into r1.
 
-     2   `movd $_myfun@c,(r2,r1)'
+     2   movd $_myfun@c,(r2,r1)
 
          This loads the address of _myfun, shifted right by 1, into register-pair r2-r1.
 
-     3   `_myfun_ptr:'
-         `.long _myfun@c'
-         `loadd _myfun_ptr, (r1,r0)'
-         `jal (r1,r0)'
+     3   _myfun_ptr:
+         .long _myfun@c
+         loadd _myfun_ptr, (r1,r0)
+         jal (r1,r0)
 
          This .long directive, the address of _myfunc, shifted right by 1 at link time.
 
-     4   `loadd  _data1@GOT(r12), (r1,r0)'
+     4   loadd  _data1@GOT(r12), (r1,r0)
 
          This loads the address of _data1, into global offset table (ie GOT) and its offset value from GOT loads into register-pair r2-r1.
 
-     5   `loadd  _myfunc@cGOT(r12), (r1,r0)'
+     5   loadd  _myfunc@cGOT(r12), (r1,r0)
 
          This loads the address of _myfun, shifted right by 1, into global offset table (ie GOT) and its offset value from GOT loads into register-pair r1-r0.
 
@@ -8231,14 +8028,13 @@ File: as.info,  Node: CR16-Chars,  Up: CR16 Syntax
 9.7.2.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 the `#' appears as the
-first character of a line, the whole line is treated as a comment, but
-in this case the line can also be a logical line number directive
-(*note Comments::) or a preprocessor control command (*note
-Preprocessing::).
+The presence of a '#' on a line indicates the start of a comment that
+extends to the end of the current line.  If the '#' appears as the first
+character of a line, the whole line is treated as a comment, but in this
+case the line can also be a logical line number directive (*note
+Comments::) or a preprocessor control command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -8260,72 +8056,73 @@ File: as.info,  Node: CRIS-Opts,  Next: CRIS-Expand,  Up: CRIS-Dependent
 9.8.1 Command-line Options
 --------------------------
 
-The CRIS version of `as' has these machine-dependent command-line
+The CRIS version of 'as' has these machine-dependent command-line
 options.
 
    The format of the generated object files can be either ELF or a.out,
-specified by the command-line options `--emulation=crisaout' and
-`--emulation=criself'.  The default is ELF (criself), unless `as' has
+specified by the command-line options '--emulation=crisaout' and
+'--emulation=criself'.  The default is ELF (criself), unless 'as' has
 been configured specifically for a.out by using the configuration name
-`cris-axis-aout'.
+'cris-axis-aout'.
 
    There are two different link-incompatible ELF object file variants
 for CRIS, for use in environments where symbols are expected to be
-prefixed by a leading `_' character and for environments without such a
+prefixed by a leading '_' character and for environments without such a
 symbol prefix.  The variant used for GNU/Linux port has no symbol
 prefix.  Which variant to produce is specified by either of the options
-`--underscore' and `--no-underscore'.  The default is `--underscore'.
-Since symbols in CRIS a.out objects are expected to have a `_' prefix,
-specifying `--no-underscore' when generating a.out objects is an error.
+'--underscore' and '--no-underscore'.  The default is '--underscore'.
+Since symbols in CRIS a.out objects are expected to have a '_' prefix,
+specifying '--no-underscore' when generating a.out objects is an error.
 Besides the object format difference, the effect of this option is to
 parse register names differently (*note crisnous::).  The
-`--no-underscore' option makes a `$' register prefix mandatory.
+'--no-underscore' option makes a '$' register prefix mandatory.
 
-   The option `--pic' must be passed to `as' in order to recognize the
+   The option '--pic' must be passed to 'as' in order to recognize the
 symbol syntax used for ELF (SVR4 PIC) position-independent-code (*note
 crispic::).  This will also affect expansion of instructions.  The
-expansion with `--pic' will use PC-relative rather than (slightly
+expansion with '--pic' will use PC-relative rather than (slightly
 faster) absolute addresses in those expansions.  This option is only
 valid when generating ELF format object files.
 
-   The option `--march=ARCHITECTURE' specifies the recognized
+   The option '--march=ARCHITECTURE' specifies the recognized
 instruction set and recognized register names.  It also controls the
 architecture type of the object file.  Valid values for ARCHITECTURE
 are:
-`v0_v10'
-     All instructions and register names for any architecture variant
-     in the set v0...v10 are recognized.  This is the default if the
-     target is configured as cris-*.
 
-`v10'
+'v0_v10'
+     All instructions and register names for any architecture variant in
+     the set v0...v10 are recognized.  This is the default if the target
+     is configured as cris-*.
+
+'v10'
      Only instructions and register names for CRIS v10 (as found in
-     ETRAX 100 LX) are recognized.  This is the default if the target
-     is configured as crisv10-*.
+     ETRAX 100 LX) are recognized.  This is the default if the target is
+     configured as crisv10-*.
 
-`v32'
+'v32'
      Only instructions and register names for CRIS v32 (code name
      Guinness) are recognized.  This is the default if the target is
-     configured as crisv32-*.  This value implies `--no-mul-bug-abort'.
-     (A subsequent `--mul-bug-abort' will turn it back on.)
+     configured as crisv32-*.  This value implies '--no-mul-bug-abort'.
+     (A subsequent '--mul-bug-abort' will turn it back on.)
 
-`common_v10_v32'
+'common_v10_v32'
      Only instructions with register names and addressing modes with
      opcodes common to the v10 and v32 are recognized.
 
-   When `-N' is specified, `as' will emit a warning when a 16-bit
-branch instruction is expanded into a 32-bit multiple-instruction
-construct (*note CRIS-Expand::).
+   When '-N' is specified, 'as' will emit a warning when a 16-bit branch
+instruction is expanded into a 32-bit multiple-instruction construct
+(*note CRIS-Expand::).
 
    Some versions of the CRIS v10, for example in the Etrax 100 LX,
 contain a bug that causes destabilizing memory accesses when a multiply
 instruction is executed with certain values in the first operand just
-before a cache-miss.  When the `--mul-bug-abort' command line option is
-active (the default value), `as' will refuse to assemble a file
+before a cache-miss.  When the '--mul-bug-abort' command line option is
+active (the default value), 'as' will refuse to assemble a file
 containing a multiply instruction at a dangerous offset, one that could
 be the last on a cache-line, or is in a section with insufficient
 alignment.  This placement checking does not catch any case where the
 multiply instruction is dangerously placed because it is located in a
-delay-slot.  The `--mul-bug-abort' command line option turns off the
+delay-slot.  The '--mul-bug-abort' command line option turns off the
 checking.
 
 
@@ -8334,25 +8131,25 @@ File: as.info,  Node: CRIS-Expand,  Next: CRIS-Symbols,  Prev: CRIS-Opts,  Up: C
 9.8.2 Instruction expansion
 ---------------------------
 
-`as' will silently choose an instruction that fits the operand size for
-`[register+constant]' operands.  For example, the offset `127' in
-`move.d [r3+127],r4' fits in an instruction using a signed-byte offset.
-Similarly, `move.d [r2+32767],r1' will generate an instruction using a
+'as' will silently choose an instruction that fits the operand size for
+'[register+constant]' operands.  For example, the offset '127' in
+'move.d [r3+127],r4' fits in an instruction using a signed-byte offset.
+Similarly, 'move.d [r2+32767],r1' will generate an instruction using a
 16-bit offset.  For symbolic expressions and constants that do not fit
 in 16 bits including the sign bit, a 32-bit offset is generated.
 
-   For branches, `as' will expand from a 16-bit branch instruction into
+   For branches, 'as' will expand from a 16-bit branch instruction into
 a sequence of instructions that can reach a full 32-bit address.  Since
 this does not correspond to a single instruction, such expansions can
 optionally be warned about.  *Note CRIS-Opts::.
 
-   If the operand is found to fit the range, a `lapc' mnemonic will
-translate to a `lapcq' instruction.  Use `lapc.d' to force the 32-bit
-`lapc' instruction.
+   If the operand is found to fit the range, a 'lapc' mnemonic will
+translate to a 'lapcq' instruction.  Use 'lapc.d' to force the 32-bit
+'lapc' instruction.
 
-   Similarly, the `addo' mnemonic will translate to the shortest
-fitting instruction of `addoq', `addo.w' and `addo.d', when used with a
-operand that is a constant known at assembly time.
+   Similarly, the 'addo' mnemonic will translate to the shortest fitting
+instruction of 'addoq', 'addo.w' and 'addo.d', when used with a operand
+that is a constant known at assembly time.
 
 
 File: as.info,  Node: CRIS-Symbols,  Next: CRIS-Syntax,  Prev: CRIS-Expand,  Up: CRIS-Dependent
@@ -8373,23 +8170,24 @@ in conditional assembly, for example:
       .endif
 
    These symbols are defined in the assembler, reflecting command-line
-options, either when specified or the default.  They are always
-defined, to 0 or 1.
-`..asm.arch.cris.any_v0_v10'
-     This symbol is non-zero when `--march=v0_v10' is specified or the
+options, either when specified or the default.  They are always defined,
+to 0 or 1.
+
+'..asm.arch.cris.any_v0_v10'
+     This symbol is non-zero when '--march=v0_v10' is specified or the
      default.
 
-`..asm.arch.cris.common_v10_v32'
-     Set according to the option `--march=common_v10_v32'.
+'..asm.arch.cris.common_v10_v32'
+     Set according to the option '--march=common_v10_v32'.
 
-`..asm.arch.cris.v10'
-     Reflects the option `--march=v10'.
+'..asm.arch.cris.v10'
+     Reflects the option '--march=v10'.
 
-`..asm.arch.cris.v32'
-     Corresponds to `--march=v10'.
+'..asm.arch.cris.v32'
+     Corresponds to '--march=v10'.
 
    Speaking of symbols, when a symbol is used in code, it can have a
-suffix modifying its value for use in position-independent code. *Note
+suffix modifying its value for use in position-independent code.  *Note
 CRIS-Pic::.
 
 
@@ -8413,13 +8211,13 @@ File: as.info,  Node: CRIS-Chars,  Next: CRIS-Pic,  Up: CRIS-Syntax
 9.8.4.1 Special Characters
 ..........................
 
-The character `#' is a line comment character.  It starts a comment if
+The character '#' is a line comment character.  It starts a comment if
 and only if it is placed at the beginning of a line.
 
-   A `;' character starts a comment anywhere on the line, causing all
+   A ';' character starts a comment anywhere on the line, causing all
 characters up to the end of the line to be ignored.
 
-   A `@' character is handled as a line separator equivalent to a
+   A '@' character is handled as a line separator equivalent to a
 logical new-line character (except in a comment), so separate
 instructions can be specified on a single line.
 
@@ -8431,71 +8229,78 @@ File: as.info,  Node: CRIS-Pic,  Next: CRIS-Regs,  Prev: CRIS-Chars,  Up: CRIS-S
 
 When generating position-independent code (SVR4 PIC) for use in
 cris-axis-linux-gnu or crisv32-axis-linux-gnu shared libraries, symbol
-suffixes are used to specify what kind of run-time symbol lookup will
-be used, expressed in the object as different _relocation types_.
-Usually, all absolute symbol values must be located in a table, the
-_global offset table_, leaving the code position-independent;
-independent of values of global symbols and independent of the address
-of the code.  The suffix modifies the value of the symbol, into for
-example an index into the global offset table where the real symbol
-value is entered, or a PC-relative value, or a value relative to the
-start of the global offset table.  All symbol suffixes start with the
-character `:' (omitted in the list below).  Every symbol use in code or
-a read-only section must therefore have a PIC suffix to enable a useful
-shared library to be created.  Usually, these constructs must not be
-used with an additive constant offset as is usually allowed, i.e. no 4
-as in `symbol + 4' is allowed.  This restriction is checked at
-link-time, not at assembly-time.
-
-`GOT'
+suffixes are used to specify what kind of run-time symbol lookup will be
+used, expressed in the object as different _relocation types_.  Usually,
+all absolute symbol values must be located in a table, the _global
+offset table_, leaving the code position-independent; independent of
+values of global symbols and independent of the address of the code.
+The suffix modifies the value of the symbol, into for example an index
+into the global offset table where the real symbol value is entered, or
+a PC-relative value, or a value relative to the start of the global
+offset table.  All symbol suffixes start with the character ':' (omitted
+in the list below).  Every symbol use in code or a read-only section
+must therefore have a PIC suffix to enable a useful shared library to be
+created.  Usually, these constructs must not be used with an additive
+constant offset as is usually allowed, i.e. no 4 as in 'symbol + 4' is
+allowed.  This restriction is checked at link-time, not at
+assembly-time.
+
+'GOT'
+
      Attaching this suffix to a symbol in an instruction causes the
      symbol to be entered into the global offset table.  The value is a
      32-bit index for that symbol into the global offset table.  The
-     name of the corresponding relocation is `R_CRIS_32_GOT'.  Example:
-     `move.d [$r0+extsym:GOT],$r9'
+     name of the corresponding relocation is 'R_CRIS_32_GOT'.  Example:
+     'move.d [$r0+extsym:GOT],$r9'
 
-`GOT16'
-     Same as for `GOT', but the value is a 16-bit index into the global
-     offset table.  The corresponding relocation is `R_CRIS_16_GOT'.
-     Example: `move.d [$r0+asymbol:GOT16],$r10'
+'GOT16'
+
+     Same as for 'GOT', but the value is a 16-bit index into the global
+     offset table.  The corresponding relocation is 'R_CRIS_16_GOT'.
+     Example: 'move.d [$r0+asymbol:GOT16],$r10'
+
+'PLT'
 
-`PLT'
      This suffix is used for function symbols.  It causes a _procedure
      linkage table_, an array of code stubs, to be created at the time
      the shared object is created or linked against, together with a
      global offset table entry.  The value is a pc-relative offset to
      the corresponding stub code in the procedure linkage table.  This
      arrangement causes the run-time symbol resolver to be called to
-     look up and set the value of the symbol the first time the
-     function is called (at latest; depending environment variables).
-     It is only safe to leave the symbol unresolved this way if all
-     references are function calls.  The name of the relocation is
-     `R_CRIS_32_PLT_PCREL'.  Example: `add.d fnname:PLT,$pc'
+     look up and set the value of the symbol the first time the function
+     is called (at latest; depending environment variables).  It is only
+     safe to leave the symbol unresolved this way if all references are
+     function calls.  The name of the relocation is
+     'R_CRIS_32_PLT_PCREL'.  Example: 'add.d fnname:PLT,$pc'
+
+'PLTG'
 
-`PLTG'
      Like PLT, but the value is relative to the beginning of the global
-     offset table.  The relocation is `R_CRIS_32_PLT_GOTREL'.  Example:
-     `move.d fnname:PLTG,$r3'
+     offset table.  The relocation is 'R_CRIS_32_PLT_GOTREL'.  Example:
+     'move.d fnname:PLTG,$r3'
 
-`GOTPLT'
-     Similar to `PLT', but the value of the symbol is a 32-bit index
+'GOTPLT'
+
+     Similar to 'PLT', but the value of the symbol is a 32-bit index
      into the global offset table.  This is somewhat of a mix between
-     the effect of the `GOT' and the `PLT' suffix; the difference to
-     `GOT' is that there will be a procedure linkage table entry
+     the effect of the 'GOT' and the 'PLT' suffix; the difference to
+     'GOT' is that there will be a procedure linkage table entry
      created, and that the symbol is assumed to be a function entry and
-     will be resolved by the run-time resolver as with `PLT'.  The
-     relocation is `R_CRIS_32_GOTPLT'.  Example: `jsr
+     will be resolved by the run-time resolver as with 'PLT'.  The
+     relocation is 'R_CRIS_32_GOTPLT'.  Example: 'jsr
      [$r0+fnname:GOTPLT]'
 
-`GOTPLT16'
-     A variant of `GOTPLT' giving a 16-bit value.  Its relocation name
-     is `R_CRIS_16_GOTPLT'.  Example: `jsr [$r0+fnname:GOTPLT16]'
+'GOTPLT16'
+
+     A variant of 'GOTPLT' giving a 16-bit value.  Its relocation name
+     is 'R_CRIS_16_GOTPLT'.  Example: 'jsr [$r0+fnname:GOTPLT16]'
+
+'GOTOFF'
 
-`GOTOFF'
      This suffix must only be attached to a local symbol, but may be
      used in an expression adding an offset.  The value is the address
      of the symbol relative to the start of the global offset table.
-     The relocation name is `R_CRIS_32_GOTREL'.  Example: `move.d
+     The relocation name is 'R_CRIS_32_GOTREL'.  Example: 'move.d
      [$r0+localsym:GOTOFF],r3'
 
 
@@ -8504,9 +8309,9 @@ File: as.info,  Node: CRIS-Regs,  Next: CRIS-Pseudos,  Prev: CRIS-Pic,  Up: CRIS
 9.8.4.3 Register names
 ......................
 
-A `$' character may always prefix a general or special register name in
+A '$' character may always prefix a general or special register name in
 an instruction operand but is mandatory when the option
-`--no-underscore' is specified or when the `.syntax register_prefix'
+'--no-underscore' is specified or when the '.syntax register_prefix'
 directive is in effect (*note crisnous::).  Register names are
 case-insensitive.
 
@@ -8518,47 +8323,51 @@ File: as.info,  Node: CRIS-Pseudos,  Prev: CRIS-Regs,  Up: CRIS-Syntax
 
 There are a few CRIS-specific pseudo-directives in addition to the
 generic ones.  *Note Pseudo Ops::.  Constants emitted by
-pseudo-directives are in little-endian order for CRIS.  There is no
+pseudo-directives are in little-endian order for CRIS. There is no
 support for floating-point-specific directives for CRIS.
 
-`.dword EXPRESSIONS'
-     The `.dword' directive is a synonym for `.int', expecting zero or
+'.dword EXPRESSIONS'
+
+     The '.dword' directive is a synonym for '.int', expecting zero or
      more EXPRESSIONS, separated by commas.  For each expression, a
      32-bit little-endian constant is emitted.
 
-`.syntax ARGUMENT'
-     The `.syntax' directive takes as ARGUMENT one of the following
+'.syntax ARGUMENT'
+     The '.syntax' directive takes as ARGUMENT one of the following
      case-sensitive choices.
 
-    `no_register_prefix'
-          The `.syntax no_register_prefix' directive makes a `$'
+     'no_register_prefix'
+
+          The '.syntax no_register_prefix' directive makes a '$'
           character prefix on all registers optional.  It overrides a
           previous setting, including the corresponding effect of the
-          option `--no-underscore'.  If this directive is used when
-          ordinary symbols do not have a `_' character prefix, care
-          must be taken to avoid ambiguities whether an operand is a
-          register or a symbol; using symbols with names the same as
-          general or special registers then invoke undefined behavior.
-
-    `register_prefix'
-          This directive makes a `$' character prefix on all registers
+          option '--no-underscore'.  If this directive is used when
+          ordinary symbols do not have a '_' character prefix, care must
+          be taken to avoid ambiguities whether an operand is a register
+          or a symbol; using symbols with names the same as general or
+          special registers then invoke undefined behavior.
+
+     'register_prefix'
+
+          This directive makes a '$' character prefix on all registers
           mandatory.  It overrides a previous setting, including the
-          corresponding effect of the option `--underscore'.
+          corresponding effect of the option '--underscore'.
+
+     'leading_underscore'
 
-    `leading_underscore'
           This is an assertion directive, emitting an error if the
-          `--no-underscore' option is in effect.
+          '--no-underscore' option is in effect.
+
+     'no_leading_underscore'
 
-    `no_leading_underscore'
-          This is the opposite of the `.syntax leading_underscore'
-          directive and emits an error if the option `--underscore' is
+          This is the opposite of the '.syntax leading_underscore'
+          directive and emits an error if the option '--underscore' is
           in effect.
 
-`.arch ARGUMENT'
+'.arch ARGUMENT'
      This is an assertion directive, giving an error if the specified
      ARGUMENT is not the same as the specified or default value for the
-     `--march=ARCHITECTURE' option (*note march-option::).
-
+     '--march=ARCHITECTURE' option (*note march-option::).
 
 
 File: as.info,  Node: D10V-Dependent,  Next: D30V-Dependent,  Prev: CRIS-Dependent,  Up: Machine Dependencies
@@ -8579,25 +8388,24 @@ File: as.info,  Node: D10V-Opts,  Next: D10V-Syntax,  Up: D10V-Dependent
 9.9.1 D10V Options
 ------------------
 
-The Mitsubishi D10V version of `as' has a few machine dependent options.
+The Mitsubishi D10V version of 'as' has a few machine dependent options.
 
-`-O'
-     The D10V can often execute two sub-instructions in parallel. When
-     this option is used, `as' will attempt to optimize its output by
+'-O'
+     The D10V can often execute two sub-instructions in parallel.  When
+     this option is used, 'as' will attempt to optimize its output by
      detecting when instructions can be executed in parallel.
-
-`--nowarnswap'
-     To optimize execution performance, `as' will sometimes swap the
-     order of instructions. Normally this generates a warning. When
-     this option is used, no warning will be generated when
-     instructions are swapped.
-
-`--gstabs-packing'
-`--no-gstabs-packing'
-     `as' packs adjacent short instructions into a single packed
-     instruction. `--no-gstabs-packing' turns instruction packing off if
-     `--gstabs' is specified as well; `--gstabs-packing' (the default)
-     turns instruction packing on even when `--gstabs' is specified.
+'--nowarnswap'
+     To optimize execution performance, 'as' will sometimes swap the
+     order of instructions.  Normally this generates a warning.  When
+     this option is used, no warning will be generated when instructions
+     are swapped.
+'--gstabs-packing'
+'--no-gstabs-packing'
+     'as' packs adjacent short instructions into a single packed
+     instruction.  '--no-gstabs-packing' turns instruction packing off
+     if '--gstabs' is specified as well; '--gstabs-packing' (the
+     default) turns instruction packing on even when '--gstabs' is
+     specified.
 
 
 File: as.info,  Node: D10V-Syntax,  Next: D10V-Float,  Prev: D10V-Opts,  Up: D10V-Dependent
@@ -8605,8 +8413,8 @@ File: as.info,  Node: D10V-Syntax,  Next: D10V-Float,  Prev: D10V-Opts,  Up: D10
 9.9.2 Syntax
 ------------
 
-The D10V syntax is based on the syntax in Mitsubishi's D10V
-architecture manual.  The differences are detailed below.
+The D10V syntax is based on the syntax in Mitsubishi's D10V architecture
+manual.  The differences are detailed below.
 
 * Menu:
 
@@ -8623,19 +8431,19 @@ File: as.info,  Node: D10V-Size,  Next: D10V-Subs,  Up: D10V-Syntax
 9.9.2.1 Size Modifiers
 ......................
 
-The D10V version of `as' uses the instruction names in the D10V
+The D10V version of 'as' uses the instruction names in the D10V
 Architecture Manual.  However, the names in the manual are sometimes
 ambiguous.  There are instruction names that can assemble to a short or
-long form opcode.  How does the assembler pick the correct form?  `as'
+long form opcode.  How does the assembler pick the correct form?  'as'
 will always pick the smallest form if it can.  When dealing with a
 symbol that is not defined yet when a line is being assembled, it will
 always use the long form.  If you need to force the assembler to use
 either the short or long form of the instruction, you can append either
-`.s' (short) or `.l' (long) to it.  For example, if you are writing an
-assembly program and you want to do a branch to a symbol that is
-defined later in your program, you can write `bra.s   foo'.  Objdump
-and GDB will always append `.s' or `.l' to instructions which have both
-short and long forms.
+'.s' (short) or '.l' (long) to it.  For example, if you are writing an
+assembly program and you want to do a branch to a symbol that is defined
+later in your program, you can write 'bra.s foo'.  Objdump and GDB will
+always append '.s' or '.l' to instructions which have both short and
+long forms.
 
 
 File: as.info,  Node: D10V-Subs,  Next: D10V-Chars,  Prev: D10V-Size,  Up: D10V-Syntax
@@ -8650,13 +8458,13 @@ sub-instructions.  These sub-instructions can be packed into a single
 instruction.  The assembler will do this automatically.  It will also
 detect when it should not pack instructions.  For example, when a label
 is defined, the next instruction will never be packaged with the
-previous one.  Whenever a branch and link instruction is called, it
-will not be packaged with the next instruction so the return address
-will be valid.  Nops are automatically inserted when necessary.
+previous one.  Whenever a branch and link instruction is called, it will
+not be packaged with the next instruction so the return address will be
+valid.  Nops are automatically inserted when necessary.
 
    If you do not want the assembler automatically making these
-decisions, you can control the packaging and execution type (parallel
-or sequential) with the special execution symbols described in the next
+decisions, you can control the packaging and execution type (parallel or
+sequential) with the special execution symbols described in the next
 section.
 
 
@@ -8665,10 +8473,10 @@ File: as.info,  Node: D10V-Chars,  Next: D10V-Regs,  Prev: D10V-Subs,  Up: D10V-
 9.9.2.3 Special Characters
 ..........................
 
-A semicolon (`;') can be used anywhere on a line to start a comment
-that extends to the end of the line.
+A semicolon (';') can be used anywhere on a line to start a comment that
+extends to the end of the line.
 
-   If a `#' appears as the first character of a line, the whole line is
+   If a '#' appears as the first character of a line, 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::).
@@ -8677,42 +8485,35 @@ command (*note Preprocessing::).
 parallel.  Instructions listed in the standard one-per-line format will
 be executed sequentially.  To specify the executing order, use the
 following symbols:
-`->'
+'->'
      Sequential with instruction on the left first.
-
-`<-'
+'<-'
      Sequential with instruction on the right first.
-
-`||'
+'||'
      Parallel
    The D10V syntax allows either one instruction per line, one
 instruction per line with the execution symbol, or two instructions per
 line.  For example
-`abs       a1      ->      abs     r0'
-     Execute these sequentially.  The instruction on the right is in
-     the right container and is executed second.
-
-`abs       r0      <-      abs     a1'
+'abs a1 -> abs r0'
+     Execute these sequentially.  The instruction on the right is in the
+     right container and is executed second.
+'abs r0 <- abs a1'
      Execute these reverse-sequentially.  The instruction on the right
      is in the right container, and is executed first.
-
-`ld2w    r2,@r8+         ||      mac     a0,r0,r7'
+'ld2w r2,@r8+ || mac a0,r0,r7'
      Execute these in parallel.
-
-`ld2w    r2,@r8+         ||'
-`mac     a0,r0,r7'
-     Two-line format. Execute these in parallel.
-
-`ld2w    r2,@r8+'
-`mac     a0,r0,r7'
-     Two-line format. Execute these sequentially.  Assembler will put
+'ld2w r2,@r8+ ||'
+'mac a0,r0,r7'
+     Two-line format.  Execute these in parallel.
+'ld2w r2,@r8+'
+'mac a0,r0,r7'
+     Two-line format.  Execute these sequentially.  Assembler will put
      them in the proper containers.
-
-`ld2w    r2,@r8+         ->'
-`mac     a0,r0,r7'
-     Two-line format. Execute these sequentially.  Same as above but
+'ld2w r2,@r8+ ->'
+'mac a0,r0,r7'
+     Two-line format.  Execute these sequentially.  Same as above but
      second instruction will always go into right container.
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: D10V-Regs,  Next: D10V-Addressing,  Prev: D10V-Chars,  Up: D10V-Syntax
@@ -8720,68 +8521,49 @@ File: as.info,  Node: D10V-Regs,  Next: D10V-Addressing,  Prev: D10V-Chars,  Up:
 9.9.2.4 Register Names
 ......................
 
-You can use the predefined symbols `r0' through `r15' to refer to the
-D10V registers.  You can also use `sp' as an alias for `r15'.  The
-accumulators are `a0' and `a1'.  There are special register-pair names
+You can use the predefined symbols 'r0' through 'r15' to refer to the
+D10V registers.  You can also use 'sp' as an alias for 'r15'.  The
+accumulators are 'a0' and 'a1'.  There are special register-pair names
 that may optionally be used in opcodes that require even-numbered
-registers. Register names are not case sensitive.
+registers.  Register names are not case sensitive.
 
    Register Pairs
-`r0-r1'
-
-`r2-r3'
-
-`r4-r5'
-
-`r6-r7'
-
-`r8-r9'
-
-`r10-r11'
-
-`r12-r13'
-
-`r14-r15'
+'r0-r1'
+'r2-r3'
+'r4-r5'
+'r6-r7'
+'r8-r9'
+'r10-r11'
+'r12-r13'
+'r14-r15'
 
    The D10V also has predefined symbols for these control registers and
 status bits:
-`psw'
+'psw'
      Processor Status Word
-
-`bpsw'
+'bpsw'
      Backup Processor Status Word
-
-`pc'
+'pc'
      Program Counter
-
-`bpc'
+'bpc'
      Backup Program Counter
-
-`rpt_c'
+'rpt_c'
      Repeat Count
-
-`rpt_s'
+'rpt_s'
      Repeat Start address
-
-`rpt_e'
+'rpt_e'
      Repeat End address
-
-`mod_s'
+'mod_s'
      Modulo Start address
-
-`mod_e'
+'mod_e'
      Modulo End address
-
-`iba'
+'iba'
      Instruction Break Address
-
-`f0'
+'f0'
      Flag 0
-
-`f1'
+'f1'
      Flag 1
-
-`c'
+'c'
      Carry flag
 
 
@@ -8790,32 +8572,25 @@ File: as.info,  Node: D10V-Addressing,  Next: D10V-Word,  Prev: D10V-Regs,  Up:
 9.9.2.5 Addressing Modes
 ........................
 
-`as' understands the following addressing modes for the D10V.  `RN' in
+'as' understands the following addressing modes for the D10V. 'RN' in
 the following refers to any of the numbered registers, but _not_ the
 control registers.
-`RN'
+'RN'
      Register direct
-
-`@RN'
+'@RN'
      Register indirect
-
-`@RN+'
+'@RN+'
      Register indirect with post-increment
-
-`@RN-'
+'@RN-'
      Register indirect with post-decrement
-
-`@-SP'
+'@-SP'
      Register indirect with pre-decrement
-
-`@(DISP, RN)'
+'@(DISP, RN)'
      Register indirect with displacement
-
-`ADDR'
+'ADDR'
      PC relative address (for branch or rep).
-
-`#IMM'
-     Immediate data (the `#' is optional and ignored)
+'#IMM'
+     Immediate data (the '#' is optional and ignored)
 
 
 File: as.info,  Node: D10V-Word,  Prev: D10V-Addressing,  Up: D10V-Syntax
@@ -8823,11 +8598,11 @@ File: as.info,  Node: D10V-Word,  Prev: D10V-Addressing,  Up: D10V-Syntax
 9.9.2.6 @WORD Modifier
 ......................
 
-Any symbol followed by `@word' will be replaced by the symbol's value
+Any symbol followed by '@word' will be replaced by the symbol's value
 shifted right by 2.  This is used in situations such as loading a
 register with the address of a function (or any other code fragment).
 For example, if you want to load a register with the location of the
-function `main' then jump to that function, you could do it as follows:
+function 'main' then jump to that function, you could do it as follows:
      ldi     r2, main@word
      jmp     r2
 
@@ -8837,7 +8612,7 @@ File: as.info,  Node: D10V-Float,  Next: D10V-Opcodes,  Prev: D10V-Syntax,  Up:
 9.9.3 Floating Point
 --------------------
 
-The D10V has no hardware floating point, but the `.float' and `.double'
+The D10V has no hardware floating point, but the '.float' and '.double'
 directives generates IEEE floating-point numbers for compatibility with
 other development tools.
 
@@ -8847,9 +8622,9 @@ File: as.info,  Node: D10V-Opcodes,  Prev: D10V-Float,  Up: D10V-Dependent
 9.9.4 Opcodes
 -------------
 
-For detailed information on the D10V machine instruction set, see `D10V
+For detailed information on the D10V machine instruction set, see 'D10V
 Architecture: A VLIW Microprocessor for Multimedia Applications'
-(Mitsubishi Electric Corp.).  `as' implements all the standard D10V
+(Mitsubishi Electric Corp.).  'as' implements all the standard D10V
 opcodes.  The only changes are those described in the section on size
 modifiers
 
@@ -8872,19 +8647,19 @@ File: as.info,  Node: D30V-Opts,  Next: D30V-Syntax,  Up: D30V-Dependent
 9.10.1 D30V Options
 -------------------
 
-The Mitsubishi D30V version of `as' has a few machine dependent options.
+The Mitsubishi D30V version of 'as' has a few machine dependent options.
 
-`-O'
-     The D30V can often execute two sub-instructions in parallel. When
-     this option is used, `as' will attempt to optimize its output by
+'-O'
+     The D30V can often execute two sub-instructions in parallel.  When
+     this option is used, 'as' will attempt to optimize its output by
      detecting when instructions can be executed in parallel.
 
-`-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
      adds a nop instruction.
 
-`-N'
-     When this option is used, `as' will issue a warning if it needs to
+'-N'
+     When this option is used, 'as' will issue a warning if it needs to
      insert a nop after a 32-bit multiply before a load or 16-bit
      multiply instruction.
 
@@ -8894,8 +8669,8 @@ File: as.info,  Node: D30V-Syntax,  Next: D30V-Float,  Prev: D30V-Opts,  Up: D30
 9.10.2 Syntax
 -------------
 
-The D30V syntax is based on the syntax in Mitsubishi's D30V
-architecture manual.  The differences are detailed below.
+The D30V syntax is based on the syntax in Mitsubishi's D30V architecture
+manual.  The differences are detailed below.
 
 * Menu:
 
@@ -8912,19 +8687,19 @@ File: as.info,  Node: D30V-Size,  Next: D30V-Subs,  Up: D30V-Syntax
 9.10.2.1 Size Modifiers
 .......................
 
-The D30V version of `as' uses the instruction names in the D30V
+The D30V version of 'as' uses the instruction names in the D30V
 Architecture Manual.  However, the names in the manual are sometimes
 ambiguous.  There are instruction names that can assemble to a short or
-long form opcode.  How does the assembler pick the correct form?  `as'
+long form opcode.  How does the assembler pick the correct form?  'as'
 will always pick the smallest form if it can.  When dealing with a
 symbol that is not defined yet when a line is being assembled, it will
 always use the long form.  If you need to force the assembler to use
 either the short or long form of the instruction, you can append either
-`.s' (short) or `.l' (long) to it.  For example, if you are writing an
-assembly program and you want to do a branch to a symbol that is
-defined later in your program, you can write `bra.s foo'.  Objdump and
-GDB will always append `.s' or `.l' to instructions which have both
-short and long forms.
+'.s' (short) or '.l' (long) to it.  For example, if you are writing an
+assembly program and you want to do a branch to a symbol that is defined
+later in your program, you can write 'bra.s foo'.  Objdump and GDB will
+always append '.s' or '.l' to instructions which have both short and
+long forms.
 
 
 File: as.info,  Node: D30V-Subs,  Next: D30V-Chars,  Prev: D30V-Size,  Up: D30V-Syntax
@@ -8939,13 +8714,13 @@ sub-instructions.  These sub-instructions can be packed into a single
 instruction.  The assembler will do this automatically.  It will also
 detect when it should not pack instructions.  For example, when a label
 is defined, the next instruction will never be packaged with the
-previous one.  Whenever a branch and link instruction is called, it
-will not be packaged with the next instruction so the return address
-will be valid.  Nops are automatically inserted when necessary.
+previous one.  Whenever a branch and link instruction is called, it will
+not be packaged with the next instruction so the return address will be
+valid.  Nops are automatically inserted when necessary.
 
    If you do not want the assembler automatically making these
-decisions, you can control the packaging and execution type (parallel
-or sequential) with the special execution symbols described in the next
+decisions, you can control the packaging and execution type (parallel or
+sequential) with the special execution symbols described in the next
 section.
 
 
@@ -8954,71 +8729,71 @@ File: as.info,  Node: D30V-Chars,  Next: D30V-Guarded,  Prev: D30V-Subs,  Up: D3
 9.10.2.3 Special Characters
 ...........................
 
-A semicolon (`;') can be used anywhere on a line to start a comment
-that extends to the end of the line.
+A semicolon (';') can be used anywhere on a line to start a comment that
+extends to the end of the line.
 
-   If a `#' appears as the first character of a line, the whole line is
+   If a '#' appears as the first character of a line, 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::).
 
    Sub-instructions may be executed in order, in reverse-order, or in
 parallel.  Instructions listed in the standard one-per-line format will
-be executed sequentially unless you use the `-O' option.
+be executed sequentially unless you use the '-O' option.
 
    To specify the executing order, use the following symbols:
-`->'
+'->'
      Sequential with instruction on the left first.
 
-`<-'
+'<-'
      Sequential with instruction on the right first.
 
-`||'
+'||'
      Parallel
 
    The D30V syntax allows either one instruction per line, one
 instruction per line with the execution symbol, or two instructions per
 line.  For example
-`abs r2,r3 -> abs r4,r5'
-     Execute these sequentially.  The instruction on the right is in
-     the right container and is executed second.
+'abs r2,r3 -> abs r4,r5'
+     Execute these sequentially.  The instruction on the right is in the
+     right container and is executed second.
 
-`abs r2,r3 <- abs r4,r5'
+'abs r2,r3 <- abs r4,r5'
      Execute these reverse-sequentially.  The instruction on the right
      is in the right container, and is executed first.
 
-`abs r2,r3 || abs r4,r5'
+'abs r2,r3 || abs r4,r5'
      Execute these in parallel.
 
-`ldw r2,@(r3,r4) ||'
-`mulx r6,r8,r9'
-     Two-line format. Execute these in parallel.
+'ldw r2,@(r3,r4) ||'
+'mulx r6,r8,r9'
+     Two-line format.  Execute these in parallel.
 
-`mulx a0,r8,r9'
-`stw r2,@(r3,r4)'
-     Two-line format. Execute these sequentially unless `-O' option is
-     used.  If the `-O' option is used, the assembler will determine if
+'mulx a0,r8,r9'
+'stw r2,@(r3,r4)'
+     Two-line format.  Execute these sequentially unless '-O' option is
+     used.  If the '-O' option is used, the assembler will determine if
      the instructions could be done in parallel (the above two
      instructions can be done in parallel), and if so, emit them as
      parallel instructions.  The assembler will put them in the proper
-     containers.  In the above example, the assembler will put the
-     `stw' instruction in left container and the `mulx' instruction in
-     the right container.
-
-`stw r2,@(r3,r4) ->'
-`mulx a0,r8,r9'
-     Two-line format.  Execute the `stw' instruction followed by the
-     `mulx' instruction sequentially.  The first instruction goes in the
+     containers.  In the above example, the assembler will put the 'stw'
+     instruction in left container and the 'mulx' instruction in the
+     right container.
+
+'stw r2,@(r3,r4) ->'
+'mulx a0,r8,r9'
+     Two-line format.  Execute the 'stw' instruction followed by the
+     'mulx' instruction sequentially.  The first instruction goes in the
      left container and the second instruction goes into right
      container.  The assembler will give an error if the machine
      ordering constraints are violated.
 
-`stw r2,@(r3,r4) <-'
-`mulx a0,r8,r9'
-     Same as previous example, except that the `mulx' instruction is
-     executed before the `stw' instruction.
+'stw r2,@(r3,r4) <-'
+'mulx a0,r8,r9'
+     Same as previous example, except that the 'mulx' instruction is
+     executed before the 'stw' instruction.
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: D30V-Guarded,  Next: D30V-Regs,  Prev: D30V-Chars,  Up: D30V-Syntax
@@ -9026,26 +8801,21 @@ File: as.info,  Node: D30V-Guarded,  Next: D30V-Regs,  Prev: D30V-Chars,  Up: D3
 9.10.2.4 Guarded Execution
 ..........................
 
-`as' supports the full range of guarded execution directives for each
+'as' supports the full range of guarded execution directives for each
 instruction.  Just append the directive after the instruction proper.
 The directives are:
 
-`/tx'
+'/tx'
      Execute the instruction if flag f0 is true.
-
-`/fx'
+'/fx'
      Execute the instruction if flag f0 is false.
-
-`/xt'
+'/xt'
      Execute the instruction if flag f1 is true.
-
-`/xf'
+'/xf'
      Execute the instruction if flag f1 is false.
-
-`/tt'
+'/tt'
      Execute the instruction if both flags f0 and f1 are true.
-
-`/tf'
+'/tf'
      Execute the instruction if flag f0 is true and flag f1 is false.
 
 
@@ -9054,79 +8824,57 @@ File: as.info,  Node: D30V-Regs,  Next: D30V-Addressing,  Prev: D30V-Guarded,  U
 9.10.2.5 Register Names
 .......................
 
-You can use the predefined symbols `r0' through `r63' to refer to the
-D30V registers.  You can also use `sp' as an alias for `r63' and `link'
-as an alias for `r62'.  The accumulators are `a0' and `a1'.
+You can use the predefined symbols 'r0' through 'r63' to refer to the
+D30V registers.  You can also use 'sp' as an alias for 'r63' and 'link'
+as an alias for 'r62'.  The accumulators are 'a0' and 'a1'.
 
    The D30V also has predefined symbols for these control registers and
 status bits:
-`psw'
+'psw'
      Processor Status Word
-
-`bpsw'
+'bpsw'
      Backup Processor Status Word
-
-`pc'
+'pc'
      Program Counter
-
-`bpc'
+'bpc'
      Backup Program Counter
-
-`rpt_c'
+'rpt_c'
      Repeat Count
-
-`rpt_s'
+'rpt_s'
      Repeat Start address
-
-`rpt_e'
+'rpt_e'
      Repeat End address
-
-`mod_s'
+'mod_s'
      Modulo Start address
-
-`mod_e'
+'mod_e'
      Modulo End address
-
-`iba'
+'iba'
      Instruction Break Address
-
-`f0'
+'f0'
      Flag 0
-
-`f1'
+'f1'
      Flag 1
-
-`f2'
+'f2'
      Flag 2
-
-`f3'
+'f3'
      Flag 3
-
-`f4'
+'f4'
      Flag 4
-
-`f5'
+'f5'
      Flag 5
-
-`f6'
+'f6'
      Flag 6
-
-`f7'
+'f7'
      Flag 7
-
-`s'
+'s'
      Same as flag 4 (saturation flag)
-
-`v'
+'v'
      Same as flag 5 (overflow flag)
-
-`va'
+'va'
      Same as flag 6 (sticky overflow flag)
-
-`c'
+'c'
      Same as flag 7 (carry/borrow flag)
-
-`b'
+'b'
      Same as flag 7 (carry/borrow flag)
 
 
@@ -9135,32 +8883,25 @@ File: as.info,  Node: D30V-Addressing,  Prev: D30V-Regs,  Up: D30V-Syntax
 9.10.2.6 Addressing Modes
 .........................
 
-`as' understands the following addressing modes for the D30V.  `RN' in
+'as' understands the following addressing modes for the D30V. 'RN' in
 the following refers to any of the numbered registers, but _not_ the
 control registers.
-`RN'
+'RN'
      Register direct
-
-`@RN'
+'@RN'
      Register indirect
-
-`@RN+'
+'@RN+'
      Register indirect with post-increment
-
-`@RN-'
+'@RN-'
      Register indirect with post-decrement
-
-`@-SP'
+'@-SP'
      Register indirect with pre-decrement
-
-`@(DISP, RN)'
+'@(DISP, RN)'
      Register indirect with displacement
-
-`ADDR'
+'ADDR'
      PC relative address (for branch or rep).
-
-`#IMM'
-     Immediate data (the `#' is optional and ignored)
+'#IMM'
+     Immediate data (the '#' is optional and ignored)
 
 
 File: as.info,  Node: D30V-Float,  Next: D30V-Opcodes,  Prev: D30V-Syntax,  Up: D30V-Dependent
@@ -9168,7 +8909,7 @@ File: as.info,  Node: D30V-Float,  Next: D30V-Opcodes,  Prev: D30V-Syntax,  Up:
 9.10.3 Floating Point
 ---------------------
 
-The D30V has no hardware floating point, but the `.float' and `.double'
+The D30V has no hardware floating point, but the '.float' and '.double'
 directives generates IEEE floating-point numbers for compatibility with
 other development tools.
 
@@ -9178,9 +8919,9 @@ File: as.info,  Node: D30V-Opcodes,  Prev: D30V-Float,  Up: D30V-Dependent
 9.10.4 Opcodes
 --------------
 
-For detailed information on the D30V machine instruction set, see `D30V
+For detailed information on the D30V machine instruction set, see 'D30V
 Architecture: A VLIW Microprocessor for Multimedia Applications'
-(Mitsubishi Electric Corp.).  `as' implements all the standard D30V
+(Mitsubishi Electric Corp.).  'as' implements all the standard D30V
 opcodes.  The only changes are those described in the section on size
 modifiers
 
@@ -9201,14 +8942,14 @@ File: as.info,  Node: Epiphany Options,  Next: Epiphany Syntax,  Up: Epiphany-De
 9.11.1 Options
 --------------
 
-`as' has two additional command-line options for the Epiphany
+'as' has two additional command-line options for the Epiphany
 architecture.
 
-`-mepiphany'
+'-mepiphany'
      Specifies that the both 32 and 16 bit instructions are allowed.
      This is the default behavior.
 
-`-mepiphany16'
+'-mepiphany16'
      Restricts the permitted instructions to just the 16 bit set.
 
 
@@ -9227,15 +8968,15 @@ File: as.info,  Node: Epiphany-Chars,  Up: Epiphany Syntax
 9.11.2.1 Special Characters
 ...........................
 
-The presence of a `;' on a line indicates the start of a comment that
+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 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 to separate statements on the same
+   The '`' character can be used to separate statements on the same
 line.
 
 
@@ -9258,12 +8999,11 @@ File: as.info,  Node: H8/300 Options,  Next: H8/300 Syntax,  Up: H8/300-Dependen
 9.12.1 Options
 --------------
 
-The Renesas H8/300 version of `as' has one machine-dependent option:
+The Renesas H8/300 version of 'as' has one machine-dependent option:
 
-`-h-tick-hex'
+'-h-tick-hex'
      Support H'00 style hex constants in addition to 0x00 style.
 
-
 
 File: as.info,  Node: H8/300 Syntax,  Next: H8/300 Floating Point,  Prev: H8/300 Options,  Up: H8/300-Dependent
 
@@ -9282,10 +9022,10 @@ File: as.info,  Node: H8/300-Chars,  Next: H8/300-Regs,  Up: H8/300 Syntax
 9.12.2.1 Special Characters
 ...........................
 
-`;' is the line comment character.
+';' is the line comment character.
 
-   `$' can be used instead of a newline to separate statements.
-Therefore _you may not use `$' in symbol names_ on the H8/300.
+   '$' can be used instead of a newline to separate statements.
+Therefore _you may not use '$' in symbol names_ on the H8/300.
 
 
 File: as.info,  Node: H8/300-Regs,  Next: H8/300-Addressing,  Prev: H8/300-Chars,  Up: H8/300 Syntax
@@ -9293,22 +9033,22 @@ File: as.info,  Node: H8/300-Regs,  Next: H8/300-Addressing,  Prev: H8/300-Chars
 9.12.2.2 Register Names
 .......................
 
-You can use predefined symbols of the form `rNh' and `rNl' to refer to
-the H8/300 registers as sixteen 8-bit general-purpose registers.  N is
-a digit from `0' to `7'); for instance, both `r0h' and `r7l' are valid
+You can use predefined symbols of the form 'rNh' and 'rNl' to refer to
+the H8/300 registers as sixteen 8-bit general-purpose registers.  N is a
+digit from '0' to '7'); for instance, both 'r0h' and 'r7l' are valid
 register names.
 
-   You can also use the eight predefined symbols `rN' to refer to the
+   You can also use the eight predefined symbols 'rN' to refer to the
 H8/300 registers as 16-bit registers (you must use this form for
 addressing).
 
-   On the H8/300H, you can also use the eight predefined symbols `erN'
-(`er0' ... `er7') to refer to the 32-bit general purpose registers.
+   On the H8/300H, you can also use the eight predefined symbols 'erN'
+('er0' ... 'er7') to refer to the 32-bit general purpose registers.
 
-   The two control registers are called `pc' (program counter; a 16-bit
-register, except on the H8/300H where it is 24 bits) and `ccr'
-(condition code register; an 8-bit register).  `r7' is used as the
-stack pointer, and can also be called `sp'.
+   The two control registers are called 'pc' (program counter; a 16-bit
+register, except on the H8/300H where it is 24 bits) and 'ccr'
+(condition code register; an 8-bit register).  'r7' is used as the stack
+pointer, and can also be called 'sp'.
 
 
 File: as.info,  Node: H8/300-Addressing,  Prev: H8/300-Regs,  Up: H8/300 Syntax
@@ -9317,43 +9057,43 @@ File: as.info,  Node: H8/300-Addressing,  Prev: H8/300-Regs,  Up: H8/300 Syntax
 .........................
 
 as understands the following addressing modes for the H8/300:
-`rN'
+'rN'
      Register direct
 
-`@rN'
+'@rN'
      Register indirect
 
-`@(D, rN)'
-`@(D:16, rN)'
-`@(D:24, rN)'
-     Register indirect: 16-bit or 24-bit displacement D from register
-     N.  (24-bit displacements are only meaningful on the H8/300H.)
+'@(D, rN)'
+'@(D:16, rN)'
+'@(D:24, rN)'
+     Register indirect: 16-bit or 24-bit displacement D from register N.
+     (24-bit displacements are only meaningful on the H8/300H.)
 
-`@rN+'
+'@rN+'
      Register indirect with post-increment
 
-`@-rN'
+'@-rN'
      Register indirect with pre-decrement
 
-``@'AA'
-``@'AA:8'
-``@'AA:16'
-``@'AA:24'
-     Absolute address `aa'.  (The address size `:24' only makes sense
-     on the H8/300H.)
-
-`#XX'
-`#XX:8'
-`#XX:16'
-`#XX:32'
-     Immediate data XX.  You may specify the `:8', `:16', or `:32' for
-     clarity, if you wish; but `as' neither requires this nor uses
+'@AA'
+'@AA:8'
+'@AA:16'
+'@AA:24'
+     Absolute address 'aa'.  (The address size ':24' only makes sense on
+     the H8/300H.)
+
+'#XX'
+'#XX:8'
+'#XX:16'
+'#XX:32'
+     Immediate data XX.  You may specify the ':8', ':16', or ':32' for
+     clarity, if you wish; but 'as' neither requires this nor uses
      it--the data size required is taken from context.
 
-``@'`@'AA'
-``@'`@'AA:8'
-     Memory indirect.  You may specify the `:8' for clarity, if you
-     wish; but `as' neither requires this nor uses it.
+'@@AA'
+'@@AA:8'
+     Memory indirect.  You may specify the ':8' for clarity, if you
+     wish; but 'as' neither requires this nor uses it.
 
 
 File: as.info,  Node: H8/300 Floating Point,  Next: H8/300 Directives,  Prev: H8/300 Syntax,  Up: H8/300-Dependent
@@ -9361,7 +9101,7 @@ File: as.info,  Node: H8/300 Floating Point,  Next: H8/300 Directives,  Prev: H8
 9.12.3 Floating Point
 ---------------------
 
-The H8/300 family has no hardware floating point, but the `.float'
+The H8/300 family has no hardware floating point, but the '.float'
 directive generates IEEE floating-point numbers for compatibility with
 other development tools.
 
@@ -9371,29 +9111,29 @@ File: as.info,  Node: H8/300 Directives,  Next: H8/300 Opcodes,  Prev: H8/300 Fl
 9.12.4 H8/300 Machine Directives
 --------------------------------
 
-`as' has the following machine-dependent directives for the H8/300:
+'as' has the following machine-dependent directives for the H8/300:
 
-`.h8300h'
-     Recognize and emit additional instructions for the H8/300H
-     variant, and also make `.int' emit 32-bit numbers rather than the
-     usual (16-bit) for the H8/300 family.
+'.h8300h'
+     Recognize and emit additional instructions for the H8/300H variant,
+     and also make '.int' emit 32-bit numbers rather than the usual
+     (16-bit) for the H8/300 family.
 
-`.h8300s'
+'.h8300s'
      Recognize and emit additional instructions for the H8S variant, and
-     also make `.int' emit 32-bit numbers rather than the usual (16-bit)
+     also make '.int' emit 32-bit numbers rather than the usual (16-bit)
      for the H8/300 family.
 
-`.h8300hn'
+'.h8300hn'
      Recognize and emit additional instructions for the H8/300H variant
-     in normal mode, and also make `.int' emit 32-bit numbers rather
+     in normal mode, and also make '.int' emit 32-bit numbers rather
      than the usual (16-bit) for the H8/300 family.
 
-`.h8300sn'
+'.h8300sn'
      Recognize and emit additional instructions for the H8S variant in
-     normal mode, and also make `.int' emit 32-bit numbers rather than
+     normal mode, and also make '.int' emit 32-bit numbers rather than
      the usual (16-bit) for the H8/300 family.
 
-   On the H8/300 family (including the H8/300H) `.word' directives
+   On the H8/300 family (including the H8/300H) '.word' directives
 generate 16-bit numbers.
 
 
@@ -9403,14 +9143,14 @@ File: as.info,  Node: H8/300 Opcodes,  Prev: H8/300 Directives,  Up: H8/300-Depe
 --------------
 
 For detailed information on the H8/300 machine instruction set, see
-`H8/300 Series Programming Manual'.  For information specific to the
-H8/300H, see `H8/300H Series Programming Manual' (Renesas).
+'H8/300 Series Programming Manual'.  For information specific to the
+H8/300H, see 'H8/300H Series Programming Manual' (Renesas).
 
-   `as' implements all the standard H8/300 opcodes.  No additional
+   'as' implements all the standard H8/300 opcodes.  No additional
 pseudo-instructions are needed on this family.
 
    The following table summarizes the H8/300 opcodes, and their
-arguments.  Entries marked `*' are opcodes used only on the H8/300H.
+arguments.  Entries marked '*' are opcodes used only on the H8/300H.
 
               Legend:
                  Rs   source register
@@ -9435,7 +9175,6 @@ arguments.  Entries marked `*' are opcodes used only on the H8/300H.
      *  and.w #imm,rd                 bhi  pcrel:8
      *  and.l #imm,rd              *  bhi  pcrel:16
      *  and.l rs,rd                   bls  pcrel:8
-
      *  bls  pcrel:16                 bld  #imm,rd
         bcc  pcrel:8                  bld  #imm,@rd
      *  bcc  pcrel:16                 bld  #imm,@abs:8
@@ -9486,7 +9225,6 @@ arguments.  Entries marked `*' are opcodes used only on the H8/300H.
         bixor #imm,rd              *  divxs.w rs,rd
         bixor #imm,@rd                eepmov
         bixor #imm,@abs:8          *  eepmovw
-
      *  exts.w rd                     mov.w rs,@abs:16
      *  exts.l rd                  *  mov.l #imm,rd
      *  extu.w rd                  *  mov.l rs,rd
@@ -9537,7 +9275,6 @@ arguments.  Entries marked `*' are opcodes used only on the H8/300H.
         mov.w @abs:16,rd           *  rotxl.l rs
         mov.w rs,@(disp:16,rd)        rotxr.b rs
         mov.w rs,@-rd              *  rotxr.w rs
-
      *  rotxr.l rs                 *  stc  ccr,@(disp:24,rd)
         bpt                        *  stc  ccr,@-rd
         rte                        *  stc  ccr,@abs:16
@@ -9559,18 +9296,18 @@ arguments.  Entries marked `*' are opcodes used only on the H8/300H.
      *  stc  ccr,@rs               *  xor.l rs,rd
      *  stc  ccr,@(disp:16,rd)        xorc #imm,ccr
 
-   Four H8/300 instructions (`add', `cmp', `mov', `sub') are defined
-with variants using the suffixes `.b', `.w', and `.l' to specify the
-size of a memory operand.  `as' supports these suffixes, but does not
-require them; since one of the operands is always a register, `as' can
+   Four H8/300 instructions ('add', 'cmp', 'mov', 'sub') are defined
+with variants using the suffixes '.b', '.w', and '.l' to specify the
+size of a memory operand.  'as' supports these suffixes, but does not
+require them; since one of the operands is always a register, 'as' can
 deduce the correct size.
 
-   For example, since `r0' refers to a 16-bit register,
+   For example, since 'r0' refers to a 16-bit register,
      mov    r0,@foo
 is equivalent to
      mov.w  r0,@foo
 
-   If you use the size suffixes, `as' issues a warning when the suffix
+   If you use the size suffixes, 'as' issues a warning when the suffix
 and the register size do not match.
 
 
@@ -9594,17 +9331,17 @@ File: as.info,  Node: HPPA Notes,  Next: HPPA Options,  Up: HPPA-Dependent
 9.13.1 Notes
 ------------
 
-As a back end for GNU CC `as' has been throughly tested and should work
+As a back end for GNU CC 'as' has been throughly tested and should work
 extremely well.  We have tested it only minimally on hand written
 assembly code and no one has tested it much on the assembly output from
 the HP compilers.
 
    The format of the debugging sections has changed since the original
-`as' port (version 1.3X) was released; therefore, you must rebuild all
+'as' port (version 1.3X) was released; therefore, you must rebuild all
 HPPA objects and libraries with the new assembler so that you can debug
 the final executable.
 
-   The HPPA `as' port generates a small subset of the relocations
+   The HPPA 'as' port generates a small subset of the relocations
 available in the SOM and ELF object file formats.  Additional relocation
 support will be added as it becomes necessary.
 
@@ -9614,7 +9351,7 @@ File: as.info,  Node: HPPA Options,  Next: HPPA Syntax,  Prev: HPPA Notes,  Up:
 9.13.2 Options
 --------------
 
-`as' has no machine-dependent command-line options for the HPPA.
+'as' has no machine-dependent command-line options for the HPPA.
 
 
 File: as.info,  Node: HPPA Syntax,  Next: HPPA Floating Point,  Prev: HPPA Options,  Up: HPPA-Dependent
@@ -9630,25 +9367,25 @@ assembly language reference manual, with a few noteworthy differences.
 simply for compatibility with how most assembly language programmers
 write code.
 
-   Some obscure expression parsing problems may affect hand written
-code which uses the `spop' instructions, or code which makes significant
-use of the `!' line separator.
+   Some obscure expression parsing problems may affect hand written code
+which uses the 'spop' instructions, or code which makes significant use
+of the '!' line separator.
 
-   `as' is much less forgiving about missing arguments and other
-similar oversights than the HP assembler.  `as' notifies you of missing
+   'as' is much less forgiving about missing arguments and other similar
+oversights than the HP assembler.  'as' notifies you of missing
 arguments as syntax errors; this is regarded as a feature, not a bug.
 
-   Finally, `as' allows you to use an external symbol without
-explicitly importing the symbol.  _Warning:_ in the future this will be
-an error for HPPA targets.
+   Finally, 'as' allows you to use an external symbol without explicitly
+importing the symbol.  _Warning:_ in the future this will be an error
+for HPPA targets.
 
    Special characters for HPPA targets include:
 
-   `;' is the line comment character.
+   ';' is the line comment character.
 
-   `!' can be used instead of a newline to separate statements.
+   '!' can be used instead of a newline to separate statements.
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: HPPA Floating Point,  Next: HPPA Directives,  Prev: HPPA Syntax,  Up: HPPA-Dependent
@@ -9664,12 +9401,12 @@ File: as.info,  Node: HPPA Directives,  Next: HPPA Opcodes,  Prev: HPPA Floating
 9.13.5 HPPA Assembler Directives
 --------------------------------
 
-`as' for the HPPA supports many additional directives for compatibility
+'as' for the HPPA supports many additional directives for compatibility
 with the native assembler.  This section describes them only briefly.
 For detailed information on HPPA-specific assembler directives, see
-`HP9000 Series 800 Assembly Language Reference Manual' (HP 92432-90001).
+'HP9000 Series 800 Assembly Language Reference Manual' (HP 92432-90001).
 
-   `as' does _not_ support the following assembler directives described
+   'as' does _not_ support the following assembler directives described
 in the HP manual:
 
      .endm           .liston
@@ -9677,195 +9414,194 @@ in the HP manual:
      .leave          .macro
      .listoff
 
-   Beyond those implemented for compatibility, `as' supports one
-additional assembler directive for the HPPA: `.param'.  It conveys
+   Beyond those implemented for compatibility, 'as' supports one
+additional assembler directive for the HPPA: '.param'.  It conveys
 register argument locations for static functions.  Its syntax closely
-follows the `.export' directive.
+follows the '.export' directive.
 
-   These are the additional directives in `as' for the HPPA:
+   These are the additional directives in 'as' for the HPPA:
 
-`.block N'
-`.blockz N'
+'.block N'
+'.blockz N'
      Reserve N bytes of storage, and initialize them to zero.
 
-`.call'
-     Mark the beginning of a procedure call.  Only the special case
-     with _no arguments_ is allowed.
+'.call'
+     Mark the beginning of a procedure call.  Only the special case with
+     _no arguments_ is allowed.
 
-`.callinfo [ PARAM=VALUE, ... ]  [ FLAG, ... ]'
+'.callinfo [ PARAM=VALUE, ... ] [ FLAG, ... ]'
      Specify a number of parameters and flags that define the
      environment for a procedure.
 
-     PARAM may be any of `frame' (frame size), `entry_gr' (end of
-     general register range), `entry_fr' (end of float register range),
-     `entry_sr' (end of space register range).
+     PARAM may be any of 'frame' (frame size), 'entry_gr' (end of
+     general register range), 'entry_fr' (end of float register range),
+     'entry_sr' (end of space register range).
 
-     The values for FLAG are `calls' or `caller' (proc has
-     subroutines), `no_calls' (proc does not call subroutines),
-     `save_rp' (preserve return pointer), `save_sp' (proc preserves
-     stack pointer), `no_unwind' (do not unwind this proc), `hpux_int'
-     (proc is interrupt routine).
+     The values for FLAG are 'calls' or 'caller' (proc has subroutines),
+     'no_calls' (proc does not call subroutines), 'save_rp' (preserve
+     return pointer), 'save_sp' (proc preserves stack pointer),
+     'no_unwind' (do not unwind this proc), 'hpux_int' (proc is
+     interrupt routine).
 
-`.code'
-     Assemble into the standard section called `$TEXT$', subsection
-     `$CODE$'.
+'.code'
+     Assemble into the standard section called '$TEXT$', subsection
+     '$CODE$'.
 
-`.copyright "STRING"'
+'.copyright "STRING"'
      In the SOM object format, insert STRING into the object code,
      marked as a copyright string.
 
-`.copyright "STRING"'
+'.copyright "STRING"'
      In the ELF object format, insert STRING into the object code,
      marked as a version string.
 
-`.enter'
+'.enter'
      Not yet supported; the assembler rejects programs containing this
      directive.
 
-`.entry'
+'.entry'
      Mark the beginning of a procedure.
 
-`.exit'
+'.exit'
      Mark the end of a procedure.
 
-`.export NAME [ ,TYP ]  [ ,PARAM=R ]'
+'.export NAME [ ,TYP ] [ ,PARAM=R ]'
      Make a procedure NAME available to callers.  TYP, if present, must
-     be one of `absolute', `code' (ELF only, not SOM), `data', `entry',
-     `data', `entry', `millicode', `plabel', `pri_prog', or `sec_prog'.
+     be one of 'absolute', 'code' (ELF only, not SOM), 'data', 'entry',
+     'data', 'entry', 'millicode', 'plabel', 'pri_prog', or 'sec_prog'.
 
      PARAM, if present, provides either relocation information for the
      procedure arguments and result, or a privilege level.  PARAM may be
-     `argwN' (where N ranges from `0' to `3', and indicates one of four
-     one-word arguments); `rtnval' (the procedure's result); or
-     `priv_lev' (privilege level).  For arguments or the result, R
-     specifies how to relocate, and must be one of `no' (not
-     relocatable), `gr' (argument is in general register), `fr' (in
-     floating point register), or `fu' (upper half of float register).
-     For `priv_lev', R is an integer.
-
-`.half N'
-     Define a two-byte integer constant N; synonym for the portable
-     `as' directive `.short'.
-
-`.import NAME [ ,TYP ]'
-     Converse of `.export'; make a procedure available to call.  The
+     'argwN' (where N ranges from '0' to '3', and indicates one of four
+     one-word arguments); 'rtnval' (the procedure's result); or
+     'priv_lev' (privilege level).  For arguments or the result, R
+     specifies how to relocate, and must be one of 'no' (not
+     relocatable), 'gr' (argument is in general register), 'fr' (in
+     floating point register), or 'fu' (upper half of float register).
+     For 'priv_lev', R is an integer.
+
+'.half N'
+     Define a two-byte integer constant N; synonym for the portable 'as'
+     directive '.short'.
+
+'.import NAME [ ,TYP ]'
+     Converse of '.export'; make a procedure available to call.  The
      arguments use the same conventions as the first two arguments for
-     `.export'.
+     '.export'.
 
-`.label NAME'
+'.label NAME'
      Define NAME as a label for the current assembly location.
 
-`.leave'
+'.leave'
      Not yet supported; the assembler rejects programs containing this
      directive.
 
-`.origin LC'
-     Advance location counter to LC. Synonym for the `as' portable
-     directive `.org'.
+'.origin LC'
+     Advance location counter to LC.  Synonym for the 'as' portable
+     directive '.org'.
 
-`.param NAME [ ,TYP ]  [ ,PARAM=R ]'
-     Similar to `.export', but used for static procedures.
+'.param NAME [ ,TYP ] [ ,PARAM=R ]'
+     Similar to '.export', but used for static procedures.
 
-`.proc'
+'.proc'
      Use preceding the first statement of a procedure.
 
-`.procend'
+'.procend'
      Use following the last statement of a procedure.
 
-`LABEL .reg EXPR'
-     Synonym for `.equ'; define LABEL with the absolute expression EXPR
+'LABEL .reg EXPR'
+     Synonym for '.equ'; define LABEL with the absolute expression EXPR
      as its value.
 
-`.space SECNAME [ ,PARAMS ]'
+'.space SECNAME [ ,PARAMS ]'
      Switch to section SECNAME, creating a new section by that name if
      necessary.  You may only use PARAMS when creating a new section,
      not when switching to an existing one.  SECNAME may identify a
      section by number rather than by name.
 
      If specified, the list PARAMS declares attributes of the section,
-     identified by keywords.  The keywords recognized are `spnum=EXP'
+     identified by keywords.  The keywords recognized are 'spnum=EXP'
      (identify this section by the number EXP, an absolute expression),
-     `sort=EXP' (order sections according to this sort key when linking;
-     EXP is an absolute expression), `unloadable' (section contains no
-     loadable data), `notdefined' (this section defined elsewhere), and
-     `private' (data in this section not available to other programs).
+     'sort=EXP' (order sections according to this sort key when linking;
+     EXP is an absolute expression), 'unloadable' (section contains no
+     loadable data), 'notdefined' (this section defined elsewhere), and
+     'private' (data in this section not available to other programs).
 
-`.spnum SECNAM'
+'.spnum SECNAM'
      Allocate four bytes of storage, and initialize them with the
      section number of the section named SECNAM.  (You can define the
-     section number with the HPPA `.space' directive.)
+     section number with the HPPA '.space' directive.)
 
-`.string "STR"'
+'.string "STR"'
      Copy the characters in the string STR to the object file.  *Note
      Strings: Strings, for information on escape sequences you can use
-     in `as' strings.
+     in 'as' strings.
 
-     _Warning!_ The HPPA version of `.string' differs from the usual
-     `as' definition: it does _not_ write a zero byte after copying STR.
+     _Warning!_  The HPPA version of '.string' differs from the usual
+     'as' definition: it does _not_ write a zero byte after copying STR.
 
-`.stringz "STR"'
-     Like `.string', but appends a zero byte after copying STR to object
+'.stringz "STR"'
+     Like '.string', but appends a zero byte after copying STR to object
      file.
 
-`.subspa NAME [ ,PARAMS ]'
-`.nsubspa NAME [ ,PARAMS ]'
-     Similar to `.space', but selects a subsection NAME within the
+'.subspa NAME [ ,PARAMS ]'
+'.nsubspa NAME [ ,PARAMS ]'
+     Similar to '.space', but selects a subsection NAME within the
      current section.  You may only specify PARAMS when you create a
-     subsection (in the first instance of `.subspa' for this NAME).
+     subsection (in the first instance of '.subspa' for this NAME).
 
      If specified, the list PARAMS declares attributes of the
      subsection, identified by keywords.  The keywords recognized are
-     `quad=EXPR' ("quadrant" for this subsection), `align=EXPR'
+     'quad=EXPR' ("quadrant" for this subsection), 'align=EXPR'
      (alignment for beginning of this subsection; a power of two),
-     `access=EXPR' (value for "access rights" field), `sort=EXPR'
-     (sorting order for this subspace in link), `code_only' (subsection
-     contains only code), `unloadable' (subsection cannot be loaded
-     into memory), `comdat' (subsection is comdat), `common'
-     (subsection is common block), `dup_comm' (subsection may have
-     duplicate names), or `zero' (subsection is all zeros, do not write
-     in object file).
-
-     `.nsubspa' always creates a new subspace with the given name, even
+     'access=EXPR' (value for "access rights" field), 'sort=EXPR'
+     (sorting order for this subspace in link), 'code_only' (subsection
+     contains only code), 'unloadable' (subsection cannot be loaded into
+     memory), 'comdat' (subsection is comdat), 'common' (subsection is
+     common block), 'dup_comm' (subsection may have duplicate names), or
+     'zero' (subsection is all zeros, do not write in object file).
+
+     '.nsubspa' always creates a new subspace with the given name, even
      if one with the same name already exists.
 
-     `comdat', `common' and `dup_comm' can be used to implement various
+     'comdat', 'common' and 'dup_comm' can be used to implement various
      flavors of one-only support when using the SOM linker.  The SOM
      linker only supports specific combinations of these flags.  The
      details are not documented.  A brief description is provided here.
 
-     `comdat' provides a form of linkonce support.  It is useful for
-     both code and data subspaces.  A `comdat' subspace has a key symbol
-     marked by the `is_comdat' flag or `ST_COMDAT'.  Only the first
+     'comdat' provides a form of linkonce support.  It is useful for
+     both code and data subspaces.  A 'comdat' subspace has a key symbol
+     marked by the 'is_comdat' flag or 'ST_COMDAT'.  Only the first
      subspace for any given key is selected.  The key symbol becomes
      universal in shared links.  This is similar to the behavior of
-     `secondary_def' symbols.
+     'secondary_def' symbols.
 
-     `common' provides Fortran named common support.  It is only useful
-     for data subspaces.  Symbols with the flag `is_common' retain this
-     flag in shared links.  Referencing a `is_common' symbol in a shared
-     library from outside the library doesn't work.  Thus, `is_common'
+     'common' provides Fortran named common support.  It is only useful
+     for data subspaces.  Symbols with the flag 'is_common' retain this
+     flag in shared links.  Referencing a 'is_common' symbol in a shared
+     library from outside the library doesn't work.  Thus, 'is_common'
      symbols must be output whenever they are needed.
 
-     `common' and `dup_comm' together provide Cobol common support.
-     The subspaces in this case must all be the same length.
-     Otherwise, this support is similar to the Fortran common support.
+     'common' and 'dup_comm' together provide Cobol common support.  The
+     subspaces in this case must all be the same length.  Otherwise,
+     this support is similar to the Fortran common support.
 
-     `dup_comm' by itself provides a type of one-only support for code.
-     Only the first `dup_comm' subspace is selected.  There is a rather
+     'dup_comm' by itself provides a type of one-only support for code.
+     Only the first 'dup_comm' subspace is selected.  There is a rather
      complex algorithm to compare subspaces.  Code symbols marked with
-     the `dup_common' flag are hidden.  This support was intended for
+     the 'dup_common' flag are hidden.  This support was intended for
      "C++ duplicate inlines".
 
      A simplified technique is used to mark the flags of symbols based
      on the flags of their subspace.  A symbol with the scope
      SS_UNIVERSAL and type ST_ENTRY, ST_CODE or ST_DATA is marked with
-     the corresponding settings of `comdat', `common' and `dup_comm'
+     the corresponding settings of 'comdat', 'common' and 'dup_comm'
      from the subspace, respectively.  This avoids having to introduce
-     additional directives to mark these symbols.  The HP assembler
-     sets `is_common' from `common'.  However, it doesn't set the
-     `dup_common' from `dup_comm'.  It doesn't have `comdat' support.
+     additional directives to mark these symbols.  The HP assembler sets
+     'is_common' from 'common'.  However, it doesn't set the
+     'dup_common' from 'dup_comm'.  It doesn't have 'comdat' support.
 
-`.version "STR"'
+'.version "STR"'
      Write STR as version identifier in object code.
 
 
@@ -9875,7 +9611,7 @@ File: as.info,  Node: HPPA Opcodes,  Prev: HPPA Directives,  Up: HPPA-Dependent
 --------------
 
 For detailed information on the HPPA machine instruction set, see
-`PA-RISC Architecture and Instruction Set Reference Manual' (HP
+'PA-RISC Architecture and Instruction Set Reference Manual' (HP
 09740-90039).
 
 
@@ -9899,13 +9635,13 @@ File: as.info,  Node: ESA/390 Notes,  Next: ESA/390 Options,  Up: ESA/390-Depend
 9.14.1 Notes
 ------------
 
-The ESA/390 `as' port is currently intended to be a back-end for the
-GNU CC compiler.  It is not HLASM compatible, although it does support
-a subset of some of the HLASM directives.  The only supported binary
-file format is ELF; none of the usual MVS/VM/OE/USS object file
-formats, such as ESD or XSD, are supported.
+The ESA/390 'as' port is currently intended to be a back-end for the GNU
+CC compiler.  It is not HLASM compatible, although it does support a
+subset of some of the HLASM directives.  The only supported binary file
+format is ELF; none of the usual MVS/VM/OE/USS object file formats, such
+as ESD or XSD, are supported.
 
-   When used with the GNU CC compiler, the ESA/390 `as' will produce
+   When used with the GNU CC compiler, the ESA/390 'as' will produce
 correct, fully relocated, functional binaries, and has been used to
 compile and execute large projects.  However, many aspects should still
 be considered experimental; these include shared library support,
@@ -9918,7 +9654,7 @@ File: as.info,  Node: ESA/390 Options,  Next: ESA/390 Syntax,  Prev: ESA/390 Not
 9.14.2 Options
 --------------
 
-`as' has no machine-dependent command-line options for the ESA/390.
+'as' has no machine-dependent command-line options for the ESA/390.
 
 
 File: as.info,  Node: ESA/390 Syntax,  Next: ESA/390 Floating Point,  Prev: ESA/390 Options,  Up: ESA/390-Dependent
@@ -9940,24 +9676,24 @@ effect.
 for compatibility with how most assembly language programmers write
 code.
 
-   `#' is the line comment character.
+   '#' is the line comment character.
 
-   `;' can be used instead of a newline to separate statements.
+   ';' can be used instead of a newline to separate statements.
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
    Registers can be given the symbolic names r0..r15, fp0, fp2, fp4,
-fp6.  By using thesse symbolic names, `as' can detect simple syntax
-errors. The name rarg or r.arg is a synonym for r11, rtca or r.tca for
+fp6.  By using thesse symbolic names, 'as' can detect simple syntax
+errors.  The name rarg or r.arg is a synonym for r11, rtca or r.tca for
 r12, sp, r.sp, dsa r.dsa for r13, lr or r.lr for r14, rbase or r.base
 for r3 and rpgt or r.pgt for r4.
 
-   `*' is the current location counter.  Unlike `.' it is always
+   '*' is the current location counter.  Unlike '.' it is always
 relative to the last USING directive.  Note that this means that
-expressions cannot use multiplication, as any occurrence of `*' will be
+expressions cannot use multiplication, as any occurrence of '*' will be
 interpreted as a location counter.
 
-   All labels are relative to the last USING.  Thus, branches to a label
+   All labels are relative to the last USING. Thus, branches to a label
 always imply the use of base+displacement.
 
    Many of the usual forms of address constants / address literals are
@@ -9974,7 +9710,7 @@ supported.  Thus,
    should all behave as expected: that is, an entry in the literal pool
 will be created (or reused if it already exists), and the instruction
 operands will be the displacement into the literal pool using the
-current base register (as last declared with the `.using' directive).
+current base register (as last declared with the '.using' directive).
 
 
 File: as.info,  Node: ESA/390 Floating Point,  Next: ESA/390 Directives,  Prev: ESA/390 Syntax,  Up: ESA/390-Dependent
@@ -9991,59 +9727,59 @@ File: as.info,  Node: ESA/390 Directives,  Next: ESA/390 Opcodes,  Prev: ESA/390
 9.14.5 ESA/390 Assembler Directives
 -----------------------------------
 
-`as' for the ESA/390 supports all of the standard ELF/SVR4 assembler
+'as' for the ESA/390 supports all of the standard ELF/SVR4 assembler
 directives that are documented in the main part of this documentation.
 Several additional directives are supported in order to implement the
-ESA/390 addressing model.  The most important of these are `.using' and
-`.ltorg'
+ESA/390 addressing model.  The most important of these are '.using' and
+'.ltorg'
 
-   These are the additional directives in `as' for the ESA/390:
+   These are the additional directives in 'as' for the ESA/390:
 
-`.dc'
+'.dc'
      A small subset of the usual DC directive is supported.
 
-`.drop REGNO'
+'.drop REGNO'
      Stop using REGNO as the base register.  The REGNO must have been
-     previously declared with a `.using' directive in the same section
+     previously declared with a '.using' directive in the same section
      as the current section.
 
-`.ebcdic STRING'
+'.ebcdic STRING'
      Emit the EBCDIC equivalent of the indicated string.  The emitted
-     string will be null terminated.  Note that the directives
-     `.string' etc. emit ascii strings by default.
+     string will be null terminated.  Note that the directives '.string'
+     etc.  emit ascii strings by default.
 
-`EQU'
+'EQU'
      The standard HLASM-style EQU directive is not supported; however,
-     the standard `as' directive .equ can be used to the same effect.
+     the standard 'as' directive .equ can be used to the same effect.
 
-`.ltorg'
+'.ltorg'
      Dump the literal pool accumulated so far; begin a new literal pool.
      The literal pool will be written in the current section; in order
-     to generate correct assembly, a `.using' must have been previously
+     to generate correct assembly, a '.using' must have been previously
      specified in the same section.
 
-`.using EXPR,REGNO'
+'.using EXPR,REGNO'
      Use REGNO as the base register for all subsequent RX, RS, and SS
-     form instructions. The EXPR will be evaluated to obtain the base
-     address; usually, EXPR will merely be `*'.
+     form instructions.  The EXPR will be evaluated to obtain the base
+     address; usually, EXPR will merely be '*'.
 
-     This assembler allows two `.using' directives to be simultaneously
-     outstanding, one in the `.text' section, and one in another section
-     (typically, the `.data' section).  This feature allows dynamically
+     This assembler allows two '.using' directives to be simultaneously
+     outstanding, one in the '.text' section, and one in another section
+     (typically, the '.data' section).  This feature allows dynamically
      loaded objects to be implemented in a relatively straightforward
-     way.  A `.using' directive must always be specified in the `.text'
+     way.  A '.using' directive must always be specified in the '.text'
      section; this will specify the base register that will be used for
-     branches in the `.text' section.  A second `.using' may be
+     branches in the '.text' section.  A second '.using' may be
      specified in another section; this will specify the base register
      that is used for non-label address literals.  When a second
-     `.using' is specified, then the subsequent `.ltorg' must be put in
+     '.using' is specified, then the subsequent '.ltorg' must be put in
      the same section; otherwise an error will result.
 
-     Thus, for example, the following code uses `r3' to address branch
-     targets and `r4' to address the literal pool, which has been
-     written to the `.data' section.  The is, the constants
-     `=A(some_routine)', `=H'42'' and `=E'3.1416'' will all appear in
-     the `.data' section.
+     Thus, for example, the following code uses 'r3' to address branch
+     targets and 'r4' to address the literal pool, which has been
+     written to the '.data' section.  The is, the constants
+     '=A(some_routine)', '=H'42'' and '=E'3.1416'' will all appear in
+     the '.data' section.
 
           .data
           	.using  LITPOOL,r4
@@ -10064,11 +9800,10 @@ ESA/390 addressing model.  The most important of these are `.using' and
           LITPOOL:
           	.ltorg
 
-     Note that this dual-`.using' directive semantics extends and is
-     not compatible with HLASM semantics.  Note that this assembler
+     Note that this dual-'.using' directive semantics extends and is not
+     compatible with HLASM semantics.  Note that this assembler
      directive does not support the full range of HLASM semantics.
 
-
 
 File: as.info,  Node: ESA/390 Opcodes,  Prev: ESA/390 Directives,  Up: ESA/390-Dependent
 
@@ -10076,7 +9811,7 @@ File: as.info,  Node: ESA/390 Opcodes,  Prev: ESA/390 Directives,  Up: ESA/390-D
 --------------
 
 For detailed information on the ESA/390 machine instruction set, see
-`ESA/390 Principles of Operation' (IBM Publication Number DZ9AR004).
+'ESA/390 Principles of Operation' (IBM Publication Number DZ9AR004).
 
 
 File: as.info,  Node: i386-Dependent,  Next: i860-Dependent,  Prev: ESA/390-Dependent,  Up: Machine Dependencies
@@ -10084,9 +9819,9 @@ File: as.info,  Node: i386-Dependent,  Next: i860-Dependent,  Prev: ESA/390-Depe
 9.15 80386 Dependent Features
 =============================
 
-   The i386 version `as' supports both the original Intel 386
-architecture in both 16 and 32-bit mode as well as AMD x86-64
-architecture extending the Intel architecture to 64-bits.
+The i386 version 'as' supports both the original Intel 386 architecture
+in both 16 and 32-bit mode as well as AMD x86-64 architecture extending
+the Intel architecture to 64-bits.
 
 * Menu:
 
@@ -10114,11 +9849,11 @@ File: as.info,  Node: i386-Options,  Next: i386-Directives,  Up: i386-Dependent
 9.15.1 Options
 --------------
 
-The i386 version of `as' has a few machine dependent options:
+The i386 version of 'as' has a few machine dependent options:
 
-`--32 | --x32 | --64'
-     Select the word size, either 32 bits or 64 bits.  `--32' implies
-     Intel i386 architecture, while `--x32' and `--64' imply AMD x86-64
+'--32 | --x32 | --64'
+     Select the word size, either 32 bits or 64 bits.  '--32' implies
+     Intel i386 architecture, while '--x32' and '--64' imply AMD x86-64
      architecture with 32-bit or 64-bit word-size respectively.
 
      These options are only available with the ELF object file format,
@@ -10126,94 +9861,116 @@ The i386 version of `as' has a few machine dependent options:
      32-bit platform you have to add -enable-64-bit-bfd to configure
      enable 64-bit usage and use x86-64 as target platform).
 
-`-n'
+'-n'
      By default, x86 GAS replaces multiple nop instructions used for
      alignment within code sections with multi-byte nop instructions
      such as leal 0(%esi,1),%esi.  This switch disables the
      optimization.
 
-`--divide'
-     On SVR4-derived platforms, the character `/' is treated as a
+'--divide'
+     On SVR4-derived platforms, the character '/' is treated as a
      comment character, which means that it cannot be used in
-     expressions.  The `--divide' option turns `/' into a normal
-     character.  This does not disable `/' at the beginning of a line
-     starting a comment, or affect using `#' for starting a comment.
+     expressions.  The '--divide' option turns '/' into a normal
+     character.  This does not disable '/' at the beginning of a line
+     starting a comment, or affect using '#' for starting a comment.
 
-`-march=CPU[+EXTENSION...]'
+'-march=CPU[+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: `i8086', `i186', `i286',
-     `i386', `i486', `i586', `i686', `pentium', `pentiumpro',
-     `pentiumii', `pentiumiii', `pentium4', `prescott', `nocona',
-     `core', `core2', `corei7', `l1om', `k1om', `k6', `k6_2', `athlon',
-     `opteron', `k8', `amdfam10', `bdver1', `bdver2', `bdver3',
-     `btver1', `btver2', `generic32' and `generic64'.
-
-     In addition to the basic instruction set, the assembler can be
-     told to accept various extension mnemonics.  For example,
-     `-march=i686+sse4+vmx' extends I686 with SSE4 and VMX.  The
-     following extensions are currently supported: `8087', `287', `387',
-     `no87', `mmx', `nommx', `sse', `sse2', `sse3', `ssse3', `sse4.1',
-     `sse4.2', `sse4', `nosse', `avx', `avx2', `adx', `rdseed',
-     `prfchw', `smap', `noavx', `vmx', `vmfunc', `smx', `xsave',
-     `xsaveopt', `aes', `pclmul', `fsgsbase', `rdrnd', `f16c', `bmi2',
-     `fma', `movbe', `ept', `lzcnt', `hle', `rtm', `invpcid', `clflush',
-     `lwp', `fma4', `xop', `cx16', `syscall', `rdtscp', `3dnow',
-     `3dnowa', `sse4a', `sse5', `svme', `abm' and `padlock'.  Note that
-     rather than extending a basic instruction set, the extension
-     mnemonics starting with `no' revoke the respective functionality.
-
-     When the `.arch' directive is used with `-march', the `.arch'
+     following processor names are recognized: 'i8086', 'i186', 'i286',
+     'i386', 'i486', 'i586', 'i686', 'pentium', 'pentiumpro',
+     'pentiumii', 'pentiumiii', 'pentium4', 'prescott', 'nocona',
+     'core', 'core2', 'corei7', 'l1om', 'k1om', 'k6', 'k6_2', 'athlon',
+     'opteron', 'k8', 'amdfam10', 'bdver1', 'bdver2', 'bdver3',
+     'btver1', 'btver2', 'generic32' and 'generic64'.
+
+     In addition to the basic instruction set, the assembler can be told
+     to accept various extension mnemonics.  For example,
+     '-march=i686+sse4+vmx' extends I686 with SSE4 and VMX.  The
+     following extensions are currently supported: '8087', '287', '387',
+     'no87', 'mmx', 'nommx', 'sse', 'sse2', 'sse3', 'ssse3', 'sse4.1',
+     'sse4.2', 'sse4', 'nosse', 'avx', 'avx2', 'adx', 'rdseed',
+     'prfchw', 'smap', 'mpx', 'sha', 'avx512f', 'avx512cd', 'avx512er',
+     'avx512pf', 'noavx', 'vmx', 'vmfunc', 'smx', 'xsave', 'xsaveopt',
+     'aes', 'pclmul', 'fsgsbase', 'rdrnd', 'f16c', 'bmi2', 'fma',
+     'movbe', 'ept', 'lzcnt', 'hle', 'rtm', 'invpcid', 'clflush', 'lwp',
+     'fma4', 'xop', 'cx16', 'syscall', 'rdtscp', '3dnow', '3dnowa',
+     'sse4a', 'sse5', 'svme', 'abm' and 'padlock'.  Note that rather
+     than extending a basic instruction set, the extension mnemonics
+     starting with 'no' revoke the respective functionality.
+
+     When the '.arch' directive is used with '-march', the '.arch'
      directive will take precedent.
 
-`-mtune=CPU'
-     This option specifies a processor to optimize for. When used in
-     conjunction with the `-march' option, only instructions of the
-     processor specified by the `-march' option will be generated.
+'-mtune=CPU'
+     This option specifies a processor to optimize for.  When used in
+     conjunction with the '-march' option, only instructions of the
+     processor specified by the '-march' option will be generated.
 
      Valid CPU values are identical to the processor list of
-     `-march=CPU'.
+     '-march=CPU'.
 
-`-msse2avx'
+'-msse2avx'
      This option specifies that the assembler should encode SSE
      instructions with VEX prefix.
 
-`-msse-check=NONE'
-`-msse-check=WARNING'
-`-msse-check=ERROR'
+'-msse-check=NONE'
+'-msse-check=WARNING'
+'-msse-check=ERROR'
      These options control if the assembler should check SSE
-     intructions.  `-msse-check=NONE' will make the assembler not to
-     check SSE instructions,  which is the default.
-     `-msse-check=WARNING' will make the assembler issue a warning for
-     any SSE intruction.  `-msse-check=ERROR' will make the assembler
-     issue an error for any SSE intruction.
-
-`-mavxscalar=128'
-`-mavxscalar=256'
+     instructions.  '-msse-check=NONE' will make the assembler not to
+     check SSE instructions, which is the default.
+     '-msse-check=WARNING' will make the assembler issue a warning for
+     any SSE instruction.  '-msse-check=ERROR' will make the assembler
+     issue an error for any SSE instruction.
+
+'-mavxscalar=128'
+'-mavxscalar=256'
      These options control how the assembler should encode scalar AVX
-     instructions.  `-mavxscalar=128' will encode scalar AVX
+     instructions.  '-mavxscalar=128' will encode scalar AVX
      instructions with 128bit vector length, which is the default.
-     `-mavxscalar=256' will encode scalar AVX instructions with 256bit
+     '-mavxscalar=256' will encode scalar AVX instructions with 256bit
      vector length.
 
-`-mmnemonic=ATT'
-`-mmnemonic=INTEL'
+'-mevexlig=128'
+'-mevexlig=256'
+'-mevexlig=512'
+     These options control how the assembler should encode
+     length-ignored (LIG) EVEX instructions.  '-mevexlig=128' will
+     encode LIG EVEX instructions with 128bit vector length, which is
+     the default.  '-mevexlig=256' and '-mevexlig=512' will encode LIG
+     EVEX instructions with 256bit and 512bit vector length,
+     respectively.
+
+'-mevexwig=0'
+'-mevexwig=1'
+     These options control how the assembler should encode w-ignored
+     (WIG) EVEX instructions.  '-mevexwig=0' will encode WIG EVEX
+     instructions with evex.w = 0, which is the default.  '-mevexwig=1'
+     will encode WIG EVEX instructions with evex.w = 1.
+
+'-mmnemonic=ATT'
+'-mmnemonic=INTEL'
      This option specifies instruction mnemonic for matching
-     instructions.  The `.att_mnemonic' and `.intel_mnemonic'
-     directives will take precedent.
+     instructions.  The '.att_mnemonic' and '.intel_mnemonic' directives
+     will take precedent.
 
-`-msyntax=ATT'
-`-msyntax=INTEL'
+'-msyntax=ATT'
+'-msyntax=INTEL'
      This option specifies instruction syntax when processing
-     instructions.  The `.att_syntax' and `.intel_syntax' directives
+     instructions.  The '.att_syntax' and '.intel_syntax' directives
      will take precedent.
 
-`-mnaked-reg'
-     This opetion specifies that registers don't require a `%' prefix.
-     The `.att_syntax' and `.intel_syntax' directives will take
+'-mnaked-reg'
+     This opetion specifies that registers don't require a '%' prefix.
+     The '.att_syntax' and '.intel_syntax' directives will take
      precedent.
 
+'-madd-bnd-prefix'
+     This option forces the assembler to add BND prefix to all branches,
+     even if such prefix was not explicitly specified in the source
+     code.
 
 
 File: as.info,  Node: i386-Directives,  Next: i386-Syntax,  Prev: i386-Options,  Up: i386-Dependent
@@ -10221,18 +9978,17 @@ File: as.info,  Node: i386-Directives,  Next: i386-Syntax,  Prev: i386-Options,
 9.15.2 x86 specific 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.
 
      This directive is only available for COFF based x86 targets.
 
-
 
 File: as.info,  Node: i386-Syntax,  Next: i386-Mnemonics,  Prev: i386-Directives,  Up: i386-Dependent
 
@@ -10250,45 +10006,44 @@ File: as.info,  Node: i386-Variations,  Next: i386-Chars,  Up: i386-Syntax
 9.15.3.1 AT&T Syntax versus Intel Syntax
 ........................................
 
-`as' now supports assembly using Intel assembler syntax.
-`.intel_syntax' selects Intel mode, and `.att_syntax' switches back to
-the usual AT&T mode for compatibility with the output of `gcc'.  Either
-of these directives may have an optional argument, `prefix', or
-`noprefix' specifying whether registers require a `%' prefix.  AT&T
+'as' now supports assembly using Intel assembler syntax.
+'.intel_syntax' selects Intel mode, and '.att_syntax' switches back to
+the usual AT&T mode for compatibility with the output of 'gcc'.  Either
+of these directives may have an optional argument, 'prefix', or
+'noprefix' specifying whether registers require a '%' prefix.  AT&T
 System V/386 assembler syntax is quite different from Intel syntax.  We
 mention these differences because almost all 80386 documents use Intel
 syntax.  Notable differences between the two syntaxes are:
 
-   * AT&T immediate operands are preceded by `$'; Intel immediate
-     operands are undelimited (Intel `push 4' is AT&T `pushl $4').
-     AT&T register operands are preceded by `%'; Intel register operands
-     are undelimited.  AT&T absolute (as opposed to PC relative)
-     jump/call operands are prefixed by `*'; they are undelimited in
-     Intel syntax.
+   * AT&T immediate operands are preceded by '$'; Intel immediate
+     operands are undelimited (Intel 'push 4' is AT&T 'pushl $4').  AT&T
+     register operands are preceded by '%'; Intel register operands are
+     undelimited.  AT&T absolute (as opposed to PC relative) jump/call
+     operands are prefixed by '*'; they are undelimited in Intel syntax.
 
    * AT&T and Intel syntax use the opposite order for source and
-     destination operands.  Intel `add eax, 4' is `addl $4, %eax'.  The
-     `source, dest' convention is maintained for compatibility with
-     previous Unix assemblers.  Note that `bound', `invlpga', and
-     instructions with 2 immediate operands, such as the `enter'
+     destination operands.  Intel 'add eax, 4' is 'addl $4, %eax'.  The
+     'source, dest' convention is maintained for compatibility with
+     previous Unix assemblers.  Note that 'bound', 'invlpga', and
+     instructions with 2 immediate operands, such as the 'enter'
      instruction, do _not_ have reversed order.  *note i386-Bugs::.
 
    * In AT&T syntax the size of memory operands is determined from the
      last character of the instruction mnemonic.  Mnemonic suffixes of
-     `b', `w', `l' and `q' specify byte (8-bit), word (16-bit), long
+     'b', 'w', 'l' and 'q' specify byte (8-bit), word (16-bit), long
      (32-bit) and quadruple word (64-bit) memory references.  Intel
      syntax accomplishes this by prefixing memory operands (_not_ the
-     instruction mnemonics) with `byte ptr', `word ptr', `dword ptr'
-     and `qword ptr'.  Thus, Intel `mov al, byte ptr FOO' is `movb FOO,
-     %al' in AT&T syntax.
+     instruction mnemonics) with 'byte ptr', 'word ptr', 'dword ptr' and
+     'qword ptr'.  Thus, Intel 'mov al, byte ptr FOO' is 'movb FOO, %al'
+     in AT&T syntax.
 
-     In 64-bit code, `movabs' can be used to encode the `mov'
+     In 64-bit code, 'movabs' can be used to encode the 'mov'
      instruction with the 64-bit displacement or immediate operand.
 
-   * Immediate form long jumps and calls are `lcall/ljmp $SECTION,
-     $OFFSET' in AT&T syntax; the Intel syntax is `call/jmp far
-     SECTION:OFFSET'.  Also, the far return instruction is `lret
-     $STACK-ADJUST' in AT&T syntax; Intel syntax is `ret far
+   * Immediate form long jumps and calls are 'lcall/ljmp $SECTION,
+     $OFFSET' in AT&T syntax; the Intel syntax is 'call/jmp far
+     SECTION:OFFSET'.  Also, the far return instruction is 'lret
+     $STACK-ADJUST' in AT&T syntax; Intel syntax is 'ret far
      STACK-ADJUST'.
 
    * The AT&T assembler does not provide support for multiple section
@@ -10301,19 +10056,19 @@ File: as.info,  Node: i386-Chars,  Prev: i386-Variations,  Up: i386-Syntax
 9.15.3.2 Special Characters
 ...........................
 
-The presence of a `#' appearing anywhere on a line indicates the start
+The presence of a '#' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   If the `--divide' command line option has not been specified then
-the `/' character appearing anywhere on a line also introduces a line
+   If the '--divide' command line option has not been specified then the
+'/' character appearing anywhere on a line also introduces a line
 comment.
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -10323,69 +10078,68 @@ File: as.info,  Node: i386-Mnemonics,  Next: i386-Regs,  Prev: i386-Syntax,  Up:
 -------------------------
 
 Instruction mnemonics are suffixed with one character modifiers which
-specify the size of operands.  The letters `b', `w', `l' and `q'
-specify byte, word, long and quadruple word operands.  If no suffix is
-specified by an instruction then `as' tries to fill in the missing
-suffix based on the destination register operand (the last one by
-convention).  Thus, `mov %ax, %bx' is equivalent to `movw %ax, %bx';
-also, `mov $1, %bx' is equivalent to `movw $1, bx'.  Note that this is
-incompatible with the AT&T Unix assembler which assumes that a missing
-mnemonic suffix implies long operand size.  (This incompatibility does
-not affect compiler output since compilers always explicitly specify
-the mnemonic suffix.)
+specify the size of operands.  The letters 'b', 'w', 'l' and 'q' specify
+byte, word, long and quadruple word operands.  If no suffix is specified
+by an instruction then 'as' tries to fill in the missing suffix based on
+the destination register operand (the last one by convention).  Thus,
+'mov %ax, %bx' is equivalent to 'movw %ax, %bx'; also, 'mov $1, %bx' is
+equivalent to 'movw $1, bx'.  Note that this is incompatible with the
+AT&T Unix assembler which assumes that a missing mnemonic suffix implies
+long operand size.  (This incompatibility does not affect compiler
+output since compilers always explicitly specify the mnemonic suffix.)
 
    Almost all instructions have the same names in AT&T and Intel format.
 There are a few exceptions.  The sign extend and zero extend
 instructions need two sizes to specify them.  They need a size to
 sign/zero extend _from_ and a size to zero extend _to_.  This is
 accomplished by using two instruction mnemonic suffixes in AT&T syntax.
-Base names for sign extend and zero extend are `movs...' and `movz...'
-in AT&T syntax (`movsx' and `movzx' in Intel syntax).  The instruction
+Base names for sign extend and zero extend are 'movs...' and 'movz...'
+in AT&T syntax ('movsx' and 'movzx' in Intel syntax).  The instruction
 mnemonic suffixes are tacked on to this base name, the _from_ suffix
-before the _to_ suffix.  Thus, `movsbl %al, %edx' is AT&T syntax for
+before the _to_ suffix.  Thus, 'movsbl %al, %edx' is AT&T syntax for
 "move sign extend _from_ %al _to_ %edx."  Possible suffixes, thus, are
-`bl' (from byte to long), `bw' (from byte to word), `wl' (from word to
-long), `bq' (from byte to quadruple word), `wq' (from word to quadruple
-word), and `lq' (from long to quadruple word).
+'bl' (from byte to long), 'bw' (from byte to word), 'wl' (from word to
+long), 'bq' (from byte to quadruple word), 'wq' (from word to quadruple
+word), and 'lq' (from long to quadruple word).
 
    Different encoding options can be specified via optional mnemonic
-suffix.  `.s' suffix swaps 2 register operands in encoding when moving
-from one register to another.  `.d8' or `.d32' suffix prefers 8bit or
+suffix.  '.s' suffix swaps 2 register operands in encoding when moving
+from one register to another.  '.d8' or '.d32' suffix prefers 8bit or
 32bit displacement in encoding.
 
    The Intel-syntax conversion instructions
 
-   * `cbw' -- sign-extend byte in `%al' to word in `%ax',
+   * 'cbw' -- sign-extend byte in '%al' to word in '%ax',
 
-   * `cwde' -- sign-extend word in `%ax' to long in `%eax',
+   * 'cwde' -- sign-extend word in '%ax' to long in '%eax',
 
-   * `cwd' -- sign-extend word in `%ax' to long in `%dx:%ax',
+   * 'cwd' -- sign-extend word in '%ax' to long in '%dx:%ax',
 
-   * `cdq' -- sign-extend dword in `%eax' to quad in `%edx:%eax',
+   * 'cdq' -- sign-extend dword in '%eax' to quad in '%edx:%eax',
 
-   * `cdqe' -- sign-extend dword in `%eax' to quad in `%rax' (x86-64
+   * 'cdqe' -- sign-extend dword in '%eax' to quad in '%rax' (x86-64
      only),
 
-   * `cqo' -- sign-extend quad in `%rax' to octuple in `%rdx:%rax'
+   * 'cqo' -- sign-extend quad in '%rax' to octuple in '%rdx:%rax'
      (x86-64 only),
 
-are called `cbtw', `cwtl', `cwtd', `cltd', `cltq', and `cqto' in AT&T
-naming.  `as' accepts either naming for these instructions.
+are called 'cbtw', 'cwtl', 'cwtd', 'cltd', 'cltq', and 'cqto' in AT&T
+naming.  'as' accepts either naming for these instructions.
 
-   Far call/jump instructions are `lcall' and `ljmp' in AT&T syntax,
-but are `call far' and `jump far' in Intel convention.
+   Far call/jump instructions are 'lcall' and 'ljmp' in AT&T syntax, but
+are 'call far' and 'jump far' in Intel convention.
 
 9.15.5 AT&T Mnemonic versus Intel Mnemonic
 ------------------------------------------
 
-`as' supports assembly using Intel mnemonic.  `.intel_mnemonic' selects
-Intel mnemonic with Intel syntax, and `.att_mnemonic' switches back to
+'as' supports assembly using Intel mnemonic.  '.intel_mnemonic' selects
+Intel mnemonic with Intel syntax, and '.att_mnemonic' switches back to
 the usual AT&T mnemonic with AT&T syntax for compatibility with the
-output of `gcc'.  Several x87 instructions, `fadd', `fdiv', `fdivp',
-`fdivr', `fdivrp', `fmul', `fsub', `fsubp', `fsubr' and `fsubrp',  are
-implemented in AT&T System V/386 assembler with different mnemonics
-from those in Intel IA32 specification.  `gcc' generates those
-instructions with AT&T mnemonic.
+output of 'gcc'.  Several x87 instructions, 'fadd', 'fdiv', 'fdivp',
+'fdivr', 'fdivrp', 'fmul', 'fsub', 'fsubp', 'fsubr' and 'fsubrp', are
+implemented in AT&T System V/386 assembler with different mnemonics from
+those in Intel IA32 specification.  'gcc' generates those instructions
+with AT&T mnemonic.
 
 
 File: as.info,  Node: i386-Regs,  Next: i386-Prefixes,  Prev: i386-Mnemonics,  Up: i386-Dependent
@@ -10393,58 +10147,57 @@ File: as.info,  Node: i386-Regs,  Next: i386-Prefixes,  Prev: i386-Mnemonics,  U
 9.15.6 Register Naming
 ----------------------
 
-Register operands are always prefixed with `%'.  The 80386 registers
+Register operands are always prefixed with '%'.  The 80386 registers
 consist of
 
-   * the 8 32-bit registers `%eax' (the accumulator), `%ebx', `%ecx',
-     `%edx', `%edi', `%esi', `%ebp' (the frame pointer), and `%esp'
-     (the stack pointer).
+   * the 8 32-bit registers '%eax' (the accumulator), '%ebx', '%ecx',
+     '%edx', '%edi', '%esi', '%ebp' (the frame pointer), and '%esp' (the
+     stack pointer).
 
-   * the 8 16-bit low-ends of these: `%ax', `%bx', `%cx', `%dx', `%di',
-     `%si', `%bp', and `%sp'.
+   * the 8 16-bit low-ends of these: '%ax', '%bx', '%cx', '%dx', '%di',
+     '%si', '%bp', and '%sp'.
 
-   * the 8 8-bit registers: `%ah', `%al', `%bh', `%bl', `%ch', `%cl',
-     `%dh', and `%dl' (These are the high-bytes and low-bytes of `%ax',
-     `%bx', `%cx', and `%dx')
+   * the 8 8-bit registers: '%ah', '%al', '%bh', '%bl', '%ch', '%cl',
+     '%dh', and '%dl' (These are the high-bytes and low-bytes of '%ax',
+     '%bx', '%cx', and '%dx')
 
-   * the 6 section registers `%cs' (code section), `%ds' (data
-     section), `%ss' (stack section), `%es', `%fs', and `%gs'.
+   * the 6 section registers '%cs' (code section), '%ds' (data section),
+     '%ss' (stack section), '%es', '%fs', and '%gs'.
 
-   * the 3 processor control registers `%cr0', `%cr2', and `%cr3'.
+   * the 3 processor control registers '%cr0', '%cr2', and '%cr3'.
 
-   * the 6 debug registers `%db0', `%db1', `%db2', `%db3', `%db6', and
-     `%db7'.
+   * the 6 debug registers '%db0', '%db1', '%db2', '%db3', '%db6', and
+     '%db7'.
 
-   * the 2 test registers `%tr6' and `%tr7'.
+   * the 2 test registers '%tr6' and '%tr7'.
 
-   * the 8 floating point register stack `%st' or equivalently
-     `%st(0)', `%st(1)', `%st(2)', `%st(3)', `%st(4)', `%st(5)',
-     `%st(6)', and `%st(7)'.  These registers are overloaded by 8 MMX
-     registers `%mm0', `%mm1', `%mm2', `%mm3', `%mm4', `%mm5', `%mm6'
-     and `%mm7'.
+   * the 8 floating point register stack '%st' or equivalently '%st(0)',
+     '%st(1)', '%st(2)', '%st(3)', '%st(4)', '%st(5)', '%st(6)', and
+     '%st(7)'.  These registers are overloaded by 8 MMX registers
+     '%mm0', '%mm1', '%mm2', '%mm3', '%mm4', '%mm5', '%mm6' and '%mm7'.
 
-   * the 8 SSE registers registers `%xmm0', `%xmm1', `%xmm2', `%xmm3',
-     `%xmm4', `%xmm5', `%xmm6' and `%xmm7'.
+   * the 8 SSE registers registers '%xmm0', '%xmm1', '%xmm2', '%xmm3',
+     '%xmm4', '%xmm5', '%xmm6' and '%xmm7'.
 
    The AMD x86-64 architecture extends the register set by:
 
-   * enhancing the 8 32-bit registers to 64-bit: `%rax' (the
-     accumulator), `%rbx', `%rcx', `%rdx', `%rdi', `%rsi', `%rbp' (the
-     frame pointer), `%rsp' (the stack pointer)
+   * enhancing the 8 32-bit registers to 64-bit: '%rax' (the
+     accumulator), '%rbx', '%rcx', '%rdx', '%rdi', '%rsi', '%rbp' (the
+     frame pointer), '%rsp' (the stack pointer)
 
-   * the 8 extended registers `%r8'-`%r15'.
+   * the 8 extended registers '%r8'-'%r15'.
 
-   * the 8 32-bit low ends of the extended registers: `%r8d'-`%r15d'
+   * the 8 32-bit low ends of the extended registers: '%r8d'-'%r15d'
 
-   * the 8 16-bit low ends of the extended registers: `%r8w'-`%r15w'
+   * the 8 16-bit low ends of the extended registers: '%r8w'-'%r15w'
 
-   * the 8 8-bit low ends of the extended registers: `%r8b'-`%r15b'
+   * the 8 8-bit low ends of the extended registers: '%r8b'-'%r15b'
 
-   * the 4 8-bit registers: `%sil', `%dil', `%bpl', `%spl'.
+   * the 4 8-bit registers: '%sil', '%dil', '%bpl', '%spl'.
 
-   * the 8 debug registers: `%db8'-`%db15'.
+   * the 8 debug registers: '%db8'-'%db15'.
 
-   * the 8 SSE registers: `%xmm8'-`%xmm15'.
+   * the 8 SSE registers: '%xmm8'-'%xmm15'.
 
 
 File: as.info,  Node: i386-Prefixes,  Next: i386-Memory,  Prev: i386-Regs,  Up: i386-Dependent
@@ -10458,51 +10211,50 @@ perform bus lock operations, and to change operand and address sizes.
 (Most instructions that normally operate on 32-bit operands will use
 16-bit operands if the instruction has an "operand size" prefix.)
 Instruction prefixes are best written on the same line as the
-instruction they act upon. For example, the `scas' (scan string)
+instruction they act upon.  For example, the 'scas' (scan string)
 instruction is repeated with:
 
              repne scas %es:(%edi),%al
 
    You may also place prefixes on the lines immediately preceding the
-instruction, but this circumvents checks that `as' does with prefixes,
+instruction, but this circumvents checks that 'as' does with prefixes,
 and will not work with all prefixes.
 
    Here is a list of instruction prefixes:
 
-   * Section override prefixes `cs', `ds', `ss', `es', `fs', `gs'.
+   * Section override prefixes 'cs', 'ds', 'ss', 'es', 'fs', 'gs'.
      These are automatically added by specifying using the
      SECTION:MEMORY-OPERAND form for memory references.
 
-   * Operand/Address size prefixes `data16' and `addr16' change 32-bit
-     operands/addresses into 16-bit operands/addresses, while `data32'
-     and `addr32' change 16-bit ones (in a `.code16' section) into
+   * Operand/Address size prefixes 'data16' and 'addr16' change 32-bit
+     operands/addresses into 16-bit operands/addresses, while 'data32'
+     and 'addr32' change 16-bit ones (in a '.code16' section) into
      32-bit operands/addresses.  These prefixes _must_ appear on the
-     same line of code as the instruction they modify. For example, in
-     a 16-bit `.code16' section, you might write:
+     same line of code as the instruction they modify.  For example, in
+     a 16-bit '.code16' section, you might write:
 
                   addr32 jmpl *(%ebx)
 
-   * The bus lock prefix `lock' inhibits interrupts during execution of
+   * The bus lock prefix 'lock' inhibits interrupts during execution of
      the instruction it precedes.  (This is only valid with certain
      instructions; see a 80386 manual for details).
 
-   * The wait for coprocessor prefix `wait' waits for the coprocessor to
+   * The wait for coprocessor prefix 'wait' waits for the coprocessor to
      complete the current instruction.  This should never be needed for
      the 80386/80387 combination.
 
-   * The `rep', `repe', and `repne' prefixes are added to string
-     instructions to make them repeat `%ecx' times (`%cx' times if the
-     current address size is 16-bits).  
-
-   * The `rex' family of prefixes is used by x86-64 to encode
-     extensions to i386 instruction set.  The `rex' prefix has four
-     bits -- an operand size overwrite (`64') used to change operand
-     size from 32-bit to 64-bit and X, Y and Z extensions bits used to
-     extend the register set.
-
-     You may write the `rex' prefixes directly. The `rex64xyz'
-     instruction emits `rex' prefix with all the bits set.  By omitting
-     the `64', `x', `y' or `z' you may write other prefixes as well.
+   * The 'rep', 'repe', and 'repne' prefixes are added to string
+     instructions to make them repeat '%ecx' times ('%cx' times if the
+     current address size is 16-bits).
+   * The 'rex' family of prefixes is used by x86-64 to encode extensions
+     to i386 instruction set.  The 'rex' prefix has four bits -- an
+     operand size overwrite ('64') used to change operand size from
+     32-bit to 64-bit and X, Y and Z extensions bits used to extend the
+     register set.
+
+     You may write the 'rex' prefixes directly.  The 'rex64xyz'
+     instruction emits 'rex' prefix with all the bits set.  By omitting
+     the '64', 'x', 'y' or 'z' you may write other prefixes as well.
      Normally, there is no need to write the prefixes explicitly, since
      gas will automatically generate them based on the instruction
      operands.
@@ -10522,56 +10274,56 @@ is translated into the AT&T syntax
      SECTION:DISP(BASE, INDEX, SCALE)
 
 where BASE and INDEX are the optional 32-bit base and index registers,
-DISP is the optional displacement, and SCALE, taking the values 1, 2,
-4, and 8, multiplies INDEX to calculate the address of the operand.  If
-no SCALE is specified, SCALE is taken to be 1.  SECTION specifies the
+DISP is the optional displacement, and SCALE, taking the values 1, 2, 4,
+and 8, multiplies INDEX to calculate the address of the operand.  If no
+SCALE is specified, SCALE is taken to be 1.  SECTION specifies the
 optional section register for the memory operand, and may override the
 default section register (see a 80386 manual for section register
-defaults). Note that section overrides in AT&T syntax _must_ be
-preceded by a `%'.  If you specify a section override which coincides
-with the default section register, `as' does _not_ output any section
+defaults).  Note that section overrides in AT&T syntax _must_ be
+preceded by a '%'.  If you specify a section override which coincides
+with the default section register, 'as' does _not_ output any section
 register override prefixes to assemble the given instruction.  Thus,
 section overrides can be specified to emphasize which section register
 is used for a given memory operand.
 
    Here are some examples of Intel and AT&T style memory references:
 
-AT&T: `-4(%ebp)', Intel:  `[ebp - 4]'
-     BASE is `%ebp'; DISP is `-4'. SECTION is missing, and the default
-     section is used (`%ss' for addressing with `%ebp' as the base
+AT&T: '-4(%ebp)', Intel: '[ebp - 4]'
+     BASE is '%ebp'; DISP is '-4'.  SECTION is missing, and the default
+     section is used ('%ss' for addressing with '%ebp' as the base
      register).  INDEX, SCALE are both missing.
 
-AT&T: `foo(,%eax,4)', Intel: `[foo + eax*4]'
-     INDEX is `%eax' (scaled by a SCALE 4); DISP is `foo'.  All other
-     fields are missing.  The section register here defaults to `%ds'.
+AT&T: 'foo(,%eax,4)', Intel: '[foo + eax*4]'
+     INDEX is '%eax' (scaled by a SCALE 4); DISP is 'foo'.  All other
+     fields are missing.  The section register here defaults to '%ds'.
 
-AT&T: `foo(,1)'; Intel `[foo]'
-     This uses the value pointed to by `foo' as a memory operand.  Note
-     that BASE and INDEX are both missing, but there is only _one_ `,'.
+AT&T: 'foo(,1)'; Intel '[foo]'
+     This uses the value pointed to by 'foo' as a memory operand.  Note
+     that BASE and INDEX are both missing, but there is only _one_ ','.
      This is a syntactic exception.
 
-AT&T: `%gs:foo'; Intel `gs:foo'
-     This selects the contents of the variable `foo' with section
-     register SECTION being `%gs'.
+AT&T: '%gs:foo'; Intel 'gs:foo'
+     This selects the contents of the variable 'foo' with section
+     register SECTION being '%gs'.
 
    Absolute (as opposed to PC relative) call and jump operands must be
-prefixed with `*'.  If no `*' is specified, `as' always chooses PC
+prefixed with '*'.  If no '*' is specified, 'as' always chooses PC
 relative addressing for jump/call labels.
 
    Any instruction that has a memory operand, but no register operand,
 _must_ specify its size (byte, word, long, or quadruple) with an
-instruction mnemonic suffix (`b', `w', `l' or `q', respectively).
+instruction mnemonic suffix ('b', 'w', 'l' or 'q', respectively).
 
    The x86-64 architecture adds an RIP (instruction pointer relative)
-addressing.  This addressing mode is specified by using `rip' as a base
-register.  Only constant offsets are valid. For example:
+addressing.  This addressing mode is specified by using 'rip' as a base
+register.  Only constant offsets are valid.  For example:
 
-AT&T: `1234(%rip)', Intel: `[rip + 1234]'
+AT&T: '1234(%rip)', Intel: '[rip + 1234]'
      Points to the address 1234 bytes past the end of the current
      instruction.
 
-AT&T: `symbol(%rip)', Intel: `[rip + symbol]'
-     Points to the `symbol' in RIP relative way, this is shorter than
+AT&T: 'symbol(%rip)', Intel: '[rip + symbol]'
+     Points to the 'symbol' in RIP relative way, this is shorter than
      the default absolute addressing.
 
    Other addressing modes remain unchanged in x86-64 architecture,
@@ -10587,16 +10339,16 @@ Jump instructions are always optimized to use the smallest possible
 displacements.  This is accomplished by using byte (8-bit) displacement
 jumps whenever the target is sufficiently close.  If a byte displacement
 is insufficient a long displacement is used.  We do not support word
-(16-bit) displacement jumps in 32-bit mode (i.e. prefixing the jump
-instruction with the `data16' instruction prefix), since the 80386
-insists upon masking `%eip' to 16 bits after the word displacement is
-added. (See also *note i386-Arch::)
+(16-bit) displacement jumps in 32-bit mode (i.e.  prefixing the jump
+instruction with the 'data16' instruction prefix), since the 80386
+insists upon masking '%eip' to 16 bits after the word displacement is
+added.  (See also *note i386-Arch::)
 
-   Note that the `jcxz', `jecxz', `loop', `loopz', `loope', `loopnz'
-and `loopne' instructions only come in byte displacements, so that if
-you use these instructions (`gcc' does not use them) you may get an
-error message (and incorrect code).  The AT&T 80386 assembler tries to
-get around this problem by expanding `jcxz foo' to
+   Note that the 'jcxz', 'jecxz', 'loop', 'loopz', 'loope', 'loopnz' and
+'loopne' instructions only come in byte displacements, so that if you
+use these instructions ('gcc' does not use them) you may get an error
+message (and incorrect code).  The AT&T 80386 assembler tries to get
+around this problem by expanding 'jcxz foo' to
 
               jcxz cx_zero
               jmp cx_nonzero
@@ -10612,31 +10364,31 @@ File: as.info,  Node: i386-Float,  Next: i386-SIMD,  Prev: i386-Jumps,  Up: i386
 All 80387 floating point types except packed BCD are supported.  (BCD
 support may be added without much difficulty).  These data types are
 16-, 32-, and 64- bit integers, and single (32-bit), double (64-bit),
-and extended (80-bit) precision floating point.  Each supported type
-has an instruction mnemonic suffix and a constructor associated with
-it.  Instruction mnemonic suffixes specify the operand's data type.
+and extended (80-bit) precision floating point.  Each supported type has
+an instruction mnemonic suffix and a constructor associated with it.
+Instruction mnemonic suffixes specify the operand's data type.
 Constructors build these data types into memory.
 
-   * Floating point constructors are `.float' or `.single', `.double',
-     and `.tfloat' for 32-, 64-, and 80-bit formats.  These correspond
-     to instruction mnemonic suffixes `s', `l', and `t'. `t' stands for
+   * Floating point constructors are '.float' or '.single', '.double',
+     and '.tfloat' for 32-, 64-, and 80-bit formats.  These correspond
+     to instruction mnemonic suffixes 's', 'l', and 't'.  't' stands for
      80-bit (ten byte) real.  The 80387 only supports this format via
-     the `fldt' (load 80-bit real to stack top) and `fstpt' (store
+     the 'fldt' (load 80-bit real to stack top) and 'fstpt' (store
      80-bit real and pop stack) instructions.
 
-   * Integer constructors are `.word', `.long' or `.int', and `.quad'
+   * Integer constructors are '.word', '.long' or '.int', and '.quad'
      for the 16-, 32-, and 64-bit integer formats.  The corresponding
-     instruction mnemonic suffixes are `s' (single), `l' (long), and
-     `q' (quad).  As with the 80-bit real format, the 64-bit `q' format
-     is only present in the `fildq' (load quad integer to stack top)
-     and `fistpq' (store quad integer and pop stack) instructions.
+     instruction mnemonic suffixes are 's' (single), 'l' (long), and 'q'
+     (quad).  As with the 80-bit real format, the 64-bit 'q' format is
+     only present in the 'fildq' (load quad integer to stack top) and
+     'fistpq' (store quad integer and pop stack) instructions.
 
    Register to register operations should not use instruction mnemonic
-suffixes.  `fstl %st, %st(1)' will give a warning, and be assembled as
-if you wrote `fst %st, %st(1)', since all register to register
-operations use 80-bit floating point operands. (Contrast this with
-`fstl %st, mem', which converts `%st' from 80-bit to 64-bit floating
-point format, then stores the result in the 4 byte location `mem')
+suffixes.  'fstl %st, %st(1)' will give a warning, and be assembled as
+if you wrote 'fst %st, %st(1)', since all register to register
+operations use 80-bit floating point operands.  (Contrast this with
+'fstl %st, mem', which converts '%st' from 80-bit to 64-bit floating
+point format, then stores the result in the 4 byte location 'mem')
 
 
 File: as.info,  Node: i386-SIMD,  Next: i386-LWP,  Prev: i386-Float,  Up: i386-Dependent
@@ -10644,18 +10396,18 @@ File: as.info,  Node: i386-SIMD,  Next: i386-LWP,  Prev: i386-Float,  Up: i386-D
 9.15.11 Intel's MMX and AMD's 3DNow! SIMD Operations
 ----------------------------------------------------
 
-`as' supports Intel's MMX instruction set (SIMD instructions for
-integer data), available on Intel's Pentium MMX processors and Pentium
-II processors, AMD's K6 and K6-2 processors, Cyrix' M2 processor, and
-probably others.  It also supports AMD's 3DNow!  instruction set (SIMD
+'as' supports Intel's MMX instruction set (SIMD instructions for integer
+data), available on Intel's Pentium MMX processors and Pentium II
+processors, AMD's K6 and K6-2 processors, Cyrix' M2 processor, and
+probably others.  It also supports AMD's 3DNow! instruction set (SIMD
 instructions for 32-bit floating point data) available on AMD's K6-2
 processor and possibly others in the future.
 
-   Currently, `as' does not support Intel's floating point SIMD, Katmai
+   Currently, 'as' does not support Intel's floating point SIMD, Katmai
 (KNI).
 
    The eight 64-bit MMX operands, also used by 3DNow!, are called
-`%mm0', `%mm1', ... `%mm7'.  They contain eight 8-bit integers, four
+'%mm0', '%mm1', ...  '%mm7'.  They contain eight 8-bit integers, four
 16-bit integers, two 32-bit integers, one 64-bit integer, or two 32-bit
 floating point values.  The MMX registers cannot be used at the same
 time as the floating point stack.
@@ -10669,7 +10421,7 @@ File: as.info,  Node: i386-LWP,  Next: i386-BMI,  Prev: i386-SIMD,  Up: i386-Dep
 9.15.12 AMD's Lightweight Profiling Instructions
 ------------------------------------------------
 
-`as' supports AMD's Lightweight Profiling (LWP) instruction set,
+'as' supports AMD's Lightweight Profiling (LWP) instruction set,
 available on AMD's Family 15h (Orochi) processors.
 
    LWP enables applications to collect and manage performance data, and
@@ -10678,7 +10430,7 @@ requires no context switches.  LWP runs in the context of a thread and
 so several counters can be used independently across multiple threads.
 LWP can be used in both 64-bit and legacy 32-bit modes.
 
-   For detailed information on the LWP instruction set, see the `AMD
+   For detailed information on the LWP instruction set, see the 'AMD
 Lightweight Profiling Specification' available at Lightweight Profiling
 Specification (http://developer.amd.com/cpu/LWP).
 
@@ -10688,7 +10440,7 @@ File: as.info,  Node: i386-BMI,  Next: i386-TBM,  Prev: i386-LWP,  Up: i386-Depe
 9.15.13 Bit Manipulation Instructions
 -------------------------------------
 
-`as' supports the Bit Manipulation (BMI) instruction set.
+'as' supports the Bit Manipulation (BMI) instruction set.
 
    BMI instructions provide several instructions implementing individual
 bit manipulation operations such as isolation, masking, setting, or
@@ -10700,7 +10452,7 @@ File: as.info,  Node: i386-TBM,  Next: i386-16bit,  Prev: i386-BMI,  Up: i386-De
 9.15.14 AMD's Trailing Bit Manipulation Instructions
 ----------------------------------------------------
 
-`as' supports AMD's Trailing Bit Manipulation (TBM) instruction set,
+'as' supports AMD's Trailing Bit Manipulation (TBM) instruction set,
 available on AMD's BDVER2 processors (Trinity and Viperfish).
 
    TBM instructions provide instructions implementing individual bit
@@ -10708,49 +10460,49 @@ manipulation operations such as isolating, masking, setting, resetting,
 complementing, and operations on trailing zeros and ones.
 
 
-File: as.info,  Node: i386-16bit,  Next: i386-Arch,  Prev: i386-TBM,  Up: i386-Dependent
+File: as.info,  Node: i386-16bit,  Next: i386-Bugs,  Prev: i386-TBM,  Up: i386-Dependent
 
 9.15.15 Writing 16-bit Code
 ---------------------------
 
-While `as' normally writes only "pure" 32-bit i386 code or 64-bit
-x86-64 code depending on the default configuration, it also supports
-writing code to run in real mode or in 16-bit protected mode code
-segments.  To do this, put a `.code16' or `.code16gcc' directive before
-the assembly language instructions to be run in 16-bit mode.  You can
-switch `as' to writing 32-bit code with the `.code32' directive or
-64-bit code with the `.code64' directive.
-
-   `.code16gcc' provides experimental support for generating 16-bit
-code from gcc, and differs from `.code16' in that `call', `ret',
-`enter', `leave', `push', `pop', `pusha', `popa', `pushf', and `popf'
+While 'as' normally writes only "pure" 32-bit i386 code or 64-bit x86-64
+code depending on the default configuration, it also supports writing
+code to run in real mode or in 16-bit protected mode code segments.  To
+do this, put a '.code16' or '.code16gcc' directive before the assembly
+language instructions to be run in 16-bit mode.  You can switch 'as' to
+writing 32-bit code with the '.code32' directive or 64-bit code with the
+'.code64' directive.
+
+   '.code16gcc' provides experimental support for generating 16-bit code
+from gcc, and differs from '.code16' in that 'call', 'ret', 'enter',
+'leave', 'push', 'pop', 'pusha', 'popa', 'pushf', and 'popf'
 instructions default to 32-bit size.  This is so that the stack pointer
 is manipulated in the same way over function calls, allowing access to
 function parameters at the same stack offsets as in 32-bit mode.
-`.code16gcc' also automatically adds address size prefixes where
+'.code16gcc' also automatically adds address size prefixes where
 necessary to use the 32-bit addressing modes that gcc generates.
 
-   The code which `as' generates in 16-bit mode will not necessarily
-run on a 16-bit pre-80386 processor.  To write code that runs on such a
+   The code which 'as' generates in 16-bit mode will not necessarily run
+on a 16-bit pre-80386 processor.  To write code that runs on such a
 processor, you must refrain from using _any_ 32-bit constructs which
-require `as' to output address or operand size prefixes.
+require 'as' to output address or operand size prefixes.
 
    Note that writing 16-bit code instructions by explicitly specifying a
 prefix or an instruction mnemonic suffix within a 32-bit code section
 generates different machine instructions than those generated for a
 16-bit code segment.  In a 32-bit code section, the following code
-generates the machine opcode bytes `66 6a 04', which pushes the value
-`4' onto the stack, decrementing `%esp' by 2.
+generates the machine opcode bytes '66 6a 04', which pushes the value
+'4' onto the stack, decrementing '%esp' by 2.
 
              pushw $4
 
    The same code in a 16-bit code section would generate the machine
-opcode bytes `6a 04' (i.e., without the operand size prefix), which is
+opcode bytes '6a 04' (i.e., without the operand size prefix), which is
 correct since the processor default operand size is assumed to be 16
 bits in a 16-bit code section.
 
 
-File: as.info,  Node: i386-Bugs,  Next: i386-Notes,  Prev: i386-Arch,  Up: i386-Dependent
+File: as.info,  Node: i386-Bugs,  Next: i386-Arch,  Prev: i386-16bit,  Up: i386-Dependent
 
 9.15.16 AT&T Syntax bugs
 ------------------------
@@ -10764,89 +10516,96 @@ with it.
    For example
 
              fsub %st,%st(3)
-   results in `%st(3)' being updated to `%st - %st(3)' rather than the
-expected `%st(3) - %st'.  This happens with all the non-commutative
+results in '%st(3)' being updated to '%st - %st(3)' rather than the
+expected '%st(3) - %st'.  This happens with all the non-commutative
 arithmetic floating point operations with two register operands where
-the source register is `%st' and the destination register is `%st(i)'.
+the source register is '%st' and the destination register is '%st(i)'.
 
 
-File: as.info,  Node: i386-Arch,  Next: i386-Bugs,  Prev: i386-16bit,  Up: i386-Dependent
+File: as.info,  Node: i386-Arch,  Next: i386-Notes,  Prev: i386-Bugs,  Up: i386-Dependent
 
 9.15.17 Specifying CPU Architecture
 -----------------------------------
 
-`as' may be told to assemble for a particular CPU (sub-)architecture
-with the `.arch CPU_TYPE' directive.  This directive enables a warning
+'as' may be told to assemble for a particular CPU (sub-)architecture
+with the '.arch CPU_TYPE' directive.  This directive enables a warning
 when gas detects an instruction that is not supported on the CPU
 specified.  The choices for CPU_TYPE are:
 
-`i8086'        `i186'         `i286'         `i386'
-`i486'         `i586'         `i686'         `pentium'
-`pentiumpro'   `pentiumii'    `pentiumiii'   `pentium4'
-`prescott'     `nocona'       `core'         `core2'
-`corei7'       `l1om'         `k1om'         
-`k6'           `k6_2'         `athlon'       `k8'
-`amdfam10'     `bdver1'       `bdver2'       `bdver3'
-`btver1'       `btver2'                      
-`generic32'    `generic64'                   
-`.mmx'         `.sse'         `.sse2'        `.sse3'
-`.ssse3'       `.sse4.1'      `.sse4.2'      `.sse4'
-`.avx'         `.vmx'         `.smx'         `.ept'
-`.clflush'     `.movbe'       `.xsave'       `.xsaveopt'
-`.aes'         `.pclmul'      `.fma'         `.fsgsbase'
-`.rdrnd'       `.f16c'        `.avx2'        `.bmi2'
-`.lzcnt'       `.invpcid'     `.vmfunc'      `.hle'
-`.rtm'         `.adx'         `.rdseed'      `.prfchw'
-`.smap'                                      
-`.3dnow'       `.3dnowa'      `.sse4a'       `.sse5'
-`.syscall'     `.rdtscp'      `.svme'        `.abm'
-`.lwp'         `.fma4'        `.xop'         `.cx16'
-`.padlock'                                   
-
-   Apart from the warning, there are only two other effects on `as'
-operation;  Firstly, if you specify a CPU other than `i486', then shift
-by one instructions such as `sarl $1, %eax' will automatically use a
-two byte opcode sequence.  The larger three byte opcode sequence is
-used on the 486 (and when no architecture is specified) because it
-executes faster on the 486.  Note that you can explicitly request the
-two byte opcode by writing `sarl %eax'.  Secondly, if you specify
-`i8086', `i186', or `i286', _and_ `.code16' or `.code16gcc' then byte
-offset conditional jumps will be promoted when necessary to a two
-instruction sequence consisting of a conditional jump of the opposite
-sense around an unconditional jump to the target.
-
-   Following the CPU architecture (but not a sub-architecture, which
-are those starting with a dot), you may specify `jumps' or `nojumps' to
-control automatic promotion of conditional jumps. `jumps' is the
-default, and enables jump promotion;  All external jumps will be of the
+'i8086'        'i186'         'i286'         'i386'
+'i486'         'i586'         'i686'         'pentium'
+'pentiumpro'   'pentiumii'    'pentiumiii'   'pentium4'
+'prescott'     'nocona'       'core'         'core2'
+'corei7'       'l1om'         'k1om'
+'k6'           'k6_2'         'athlon'       'k8'
+'amdfam10'     'bdver1'       'bdver2'       'bdver3'
+'btver1'       'btver2'
+'generic32'    'generic64'
+'.mmx'         '.sse'         '.sse2'        '.sse3'
+'.ssse3'       '.sse4.1'      '.sse4.2'      '.sse4'
+'.avx'         '.vmx'         '.smx'         '.ept'
+'.clflush'     '.movbe'       '.xsave'       '.xsaveopt'
+'.aes'         '.pclmul'      '.fma'         '.fsgsbase'
+'.rdrnd'       '.f16c'        '.avx2'        '.bmi2'
+'.lzcnt'       '.invpcid'     '.vmfunc'      '.hle'
+'.rtm'         '.adx'         '.rdseed'      '.prfchw'
+'.smap'        '.mpx'
+'.smap'        '.sha'
+'.smap'        '.clflushopt'  '.xsavec'      '.xsaves'
+'.smap'        '.prefetchwt1'
+'.3dnow'       '.3dnowa'      '.sse4a'       '.sse5'
+'.syscall'     '.rdtscp'      '.svme'        '.abm'
+'.lwp'         '.fma4'        '.xop'         '.cx16'
+'.padlock'
+'.smap'        '.avx512f'     '.avx512cd'    '.avx512er'
+'.avx512pf'    '.3dnow'       '.3dnowa'      '.sse4a'
+'.sse5'        '.syscall'     '.rdtscp'      '.svme'
+'.abm'         '.lwp'         '.fma4'        '.xop'
+'.cx16'        '.padlock'
+
+   Apart from the warning, there are only two other effects on 'as'
+operation; Firstly, if you specify a CPU other than 'i486', then shift
+by one instructions such as 'sarl $1, %eax' will automatically use a two
+byte opcode sequence.  The larger three byte opcode sequence is used on
+the 486 (and when no architecture is specified) because it executes
+faster on the 486.  Note that you can explicitly request the two byte
+opcode by writing 'sarl %eax'.  Secondly, if you specify 'i8086',
+'i186', or 'i286', _and_ '.code16' or '.code16gcc' then byte offset
+conditional jumps will be promoted when necessary to a two instruction
+sequence consisting of a conditional jump of the opposite sense around
+an unconditional jump to the target.
+
+   Following the CPU architecture (but not a sub-architecture, which are
+those starting with a dot), you may specify 'jumps' or 'nojumps' to
+control automatic promotion of conditional jumps.  'jumps' is the
+default, and enables jump promotion; All external jumps will be of the
 long variety, and file-local jumps will be promoted as necessary.
-(*note i386-Jumps::)  `nojumps' leaves external conditional jumps as
-byte offset jumps, and warns about file-local conditional jumps that
-`as' promotes.  Unconditional jumps are treated as for `jumps'.
+(*note i386-Jumps::) 'nojumps' leaves external conditional jumps as byte
+offset jumps, and warns about file-local conditional jumps that 'as'
+promotes.  Unconditional jumps are treated as for 'jumps'.
 
    For example
 
       .arch i8086,nojumps
 
 
-File: as.info,  Node: i386-Notes,  Prev: i386-Bugs,  Up: i386-Dependent
+File: as.info,  Node: i386-Notes,  Prev: i386-Arch,  Up: i386-Dependent
 
 9.15.18 Notes
 -------------
 
-There is some trickery concerning the `mul' and `imul' instructions
-that deserves mention.  The 16-, 32-, 64- and 128-bit expanding
-multiplies (base opcode `0xf6'; extension 4 for `mul' and 5 for `imul')
-can be output only in the one operand form.  Thus, `imul %ebx, %eax'
-does _not_ select the expanding multiply; the expanding multiply would
-clobber the `%edx' register, and this would confuse `gcc' output.  Use
-`imul %ebx' to get the 64-bit product in `%edx:%eax'.
+There is some trickery concerning the 'mul' and 'imul' instructions that
+deserves mention.  The 16-, 32-, 64- and 128-bit expanding multiplies
+(base opcode '0xf6'; extension 4 for 'mul' and 5 for 'imul') can be
+output only in the one operand form.  Thus, 'imul %ebx, %eax' does _not_
+select the expanding multiply; the expanding multiply would clobber the
+'%edx' register, and this would confuse 'gcc' output.  Use 'imul %ebx'
+to get the 64-bit product in '%edx:%eax'.
 
-   We have added a two operand form of `imul' when the first operand is
-an immediate mode expression and the second operand is a register.
-This is just a shorthand, so that, multiplying `%eax' by 69, for
-example, can be done with `imul $69, %eax' rather than `imul $69, %eax,
-%eax'.
+   We have added a two operand form of 'imul' when the first operand is
+an immediate mode expression and the second operand is a register.  This
+is just a shorthand, so that, multiplying '%eax' by 69, for example, can
+be done with 'imul $69, %eax' rather than 'imul $69, %eax, %eax'.
 
 
 File: as.info,  Node: i860-Dependent,  Next: i960-Dependent,  Prev: i386-Dependent,  Up: Machine Dependencies
@@ -10869,19 +10628,19 @@ File: as.info,  Node: Notes-i860,  Next: Options-i860,  Up: i860-Dependent
 -----------------
 
 This is a fairly complete i860 assembler which is compatible with the
-UNIX System V/860 Release 4 assembler. However, it does not currently
-support SVR4 PIC (i.e., `@GOT, @GOTOFF, @PLT').
+UNIX System V/860 Release 4 assembler.  However, it does not currently
+support SVR4 PIC (i.e., '@GOT, @GOTOFF, @PLT').
 
    Like the SVR4/860 assembler, the output object format is ELF32.
-Currently, this is the only supported object format. If there is
+Currently, this is the only supported object format.  If there is
 sufficient interest, other formats such as COFF may be implemented.
 
    Both the Intel and AT&T/SVR4 syntaxes are supported, with the latter
 being the default.  One difference is that AT&T syntax requires the '%'
 prefix on register names while Intel syntax does not.  Another
 difference is in the specification of relocatable expressions.  The
-Intel syntax is `ha%expression' whereas the SVR4 syntax is
-`[expression]@ha' (and similarly for the "l" and "h" selectors).
+Intel syntax is 'ha%expression' whereas the SVR4 syntax is
+'[expression]@ha' (and similarly for the "l" and "h" selectors).
 
 
 File: as.info,  Node: Options-i860,  Next: Directives-i860,  Prev: Notes-i860,  Up: i860-Dependent
@@ -10892,41 +10651,35 @@ File: as.info,  Node: Options-i860,  Next: Directives-i860,  Prev: Notes-i860,
 9.16.2.1 SVR4 compatibility options
 ...................................
 
-`-V'
+'-V'
      Print assembler version.
-
-`-Qy'
+'-Qy'
      Ignored.
-
-`-Qn'
+'-Qn'
      Ignored.
 
 9.16.2.2 Other options
 ......................
 
-`-EL'
+'-EL'
      Select little endian output (this is the default).
-
-`-EB'
-     Select big endian output. Note that the i860 always reads
+'-EB'
+     Select big endian output.  Note that the i860 always reads
      instructions as little endian data, so this option only effects
      data and not instructions.
-
-`-mwarn-expand'
+'-mwarn-expand'
      Emit a warning message if any pseudo-instruction expansions
-     occurred.  For example, a `or' instruction with an immediate
-     larger than 16-bits will be expanded into two instructions. This
-     is a very undesirable feature to rely on, so this flag can help
-     detect any code where it happens. One use of it, for instance, has
-     been to find and eliminate any place where `gcc' may emit these
+     occurred.  For example, a 'or' instruction with an immediate larger
+     than 16-bits will be expanded into two instructions.  This is a
+     very undesirable feature to rely on, so this flag can help detect
+     any code where it happens.  One use of it, for instance, has been
+     to find and eliminate any place where 'gcc' may emit these
      pseudo-instructions.
-
-`-mxp'
+'-mxp'
      Enable support for the i860XP instructions and control registers.
      By default, this option is disabled so that only the base
      instruction set (i.e., i860XR) is supported.
-
-`-mintel-syntax'
+'-mintel-syntax'
      The i860 assembler defaults to AT&T/SVR4 syntax.  This option
      enables the Intel syntax.
 
@@ -10936,27 +10689,27 @@ File: as.info,  Node: Directives-i860,  Next: Opcodes for i860,  Prev: Options-i
 9.16.3 i860 Machine Directives
 ------------------------------
 
-`.dual'
-     Enter dual instruction mode. While this directive is supported, the
-     preferred way to use dual instruction mode is to explicitly code
-     the dual bit with the `d.' prefix.
+'.dual'
+     Enter dual instruction mode.  While this directive is supported,
+     the preferred way to use dual instruction mode is to explicitly
+     code the dual bit with the 'd.' prefix.
 
-`.enddual'
-     Exit dual instruction mode. While this directive is supported, the
+'.enddual'
+     Exit dual instruction mode.  While this directive is supported, the
      preferred way to use dual instruction mode is to explicitly code
-     the dual bit with the `d.' prefix.
+     the dual bit with the 'd.' prefix.
 
-`.atmp'
+'.atmp'
      Change the temporary register used when expanding pseudo
-     operations. The default register is `r31'.
+     operations.  The default register is 'r31'.
 
-   The `.dual', `.enddual', and `.atmp' directives are available only
-in the Intel syntax mode.
+   The '.dual', '.enddual', and '.atmp' directives are available only in
+the Intel syntax mode.
 
-   Both syntaxes allow for the standard `.align' directive.  However,
+   Both syntaxes allow for the standard '.align' directive.  However,
 the Intel syntax additionally allows keywords for the alignment
-parameter: "`.align type'", where `type' is one of `.short', `.long',
-`.quad', `.single', `.double' representing alignments of 2, 4, 16, 4,
+parameter: "'.align type'", where 'type' is one of '.short', '.long',
+'.quad', '.single', '.double' representing alignments of 2, 4, 16, 4,
 and 8, respectively.
 
 
@@ -10966,53 +10719,50 @@ File: as.info,  Node: Opcodes for i860,  Next: Syntax of i860,  Prev: Directives
 -------------------
 
 All of the Intel i860XR and i860XP machine instructions are supported.
-Please see either _i860 Microprocessor Programmer's Reference Manual_
-or _i860 Microprocessor Architecture_ for more information.
+Please see either _i860 Microprocessor Programmer's Reference Manual_ or
+_i860 Microprocessor Architecture_ for more information.
 
 9.16.4.1 Other instruction support (pseudo-instructions)
 ........................................................
 
 For compatibility with some other i860 assemblers, a number of
-pseudo-instructions are supported. While these are supported, they are
+pseudo-instructions are supported.  While these are supported, they are
 a very undesirable feature that should be avoided - in particular, when
-they result in an expansion to multiple actual i860 instructions. Below
+they result in an expansion to multiple actual i860 instructions.  Below
 are the pseudo-instructions that result in expansions.
    * Load large immediate into general register:
 
-     The pseudo-instruction `mov imm,%rn' (where the immediate does not
+     The pseudo-instruction 'mov imm,%rn' (where the immediate does not
      fit within a signed 16-bit field) will be expanded into:
           orh large_imm@h,%r0,%rn
           or large_imm@l,%rn,%rn
-
    * Load/store with relocatable address expression:
 
-     For example, the pseudo-instruction `ld.b addr_exp(%rx),%rn' will
+     For example, the pseudo-instruction 'ld.b addr_exp(%rx),%rn' will
      be expanded into:
           orh addr_exp@ha,%rx,%r31
           ld.l addr_exp@l(%r31),%rn
 
-     The analogous expansions apply to `ld.x, st.x, fld.x, pfld.x,
-     fst.x', and `pst.x' as well.
-
+     The analogous expansions apply to 'ld.x, st.x, fld.x, pfld.x,
+     fst.x', and 'pst.x' as well.
    * Signed large immediate with add/subtract:
 
-     If any of the arithmetic operations `adds, addu, subs, subu' are
-     used with an immediate larger than 16-bits (signed), then they
-     will be expanded.  For instance, the pseudo-instruction `adds
+     If any of the arithmetic operations 'adds, addu, subs, subu' are
+     used with an immediate larger than 16-bits (signed), then they will
+     be expanded.  For instance, the pseudo-instruction 'adds
      large_imm,%rx,%rn' expands to:
           orh large_imm@h,%r0,%r31
           or large_imm@l,%r31,%r31
           adds %r31,%rx,%rn
-
    * Unsigned large immediate with logical operations:
 
-     Logical operations (`or, andnot, or, xor') also result in
-     expansions.  The pseudo-instruction `or large_imm,%rx,%rn' results
+     Logical operations ('or, andnot, or, xor') also result in
+     expansions.  The pseudo-instruction 'or large_imm,%rx,%rn' results
      in:
           orh large_imm@h,%rx,%r31
           or large_imm@l,%r31,%rn
 
-     Similarly for the others, except for `and' which expands to:
+     Similarly for the others, except for 'and' which expands to:
           andnot (-1 - large_imm)@h,%rx,%r31
           andnot (-1 - large_imm)@l,%r31,%rn
 
@@ -11032,15 +10782,15 @@ File: as.info,  Node: i860-Chars,  Up: Syntax of i860
 9.16.5.1 Special Characters
 ...........................
 
-The presence of a `#' appearing anywhere on a line indicates the start
+The presence of a '#' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -11063,29 +10813,29 @@ File: as.info,  Node: Options-i960,  Next: Floating Point-i960,  Up: i960-Depend
 9.17.1 i960 Command-line Options
 --------------------------------
 
-`-ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC'
+'-ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC'
      Select the 80960 architecture.  Instructions or features not
      supported by the selected architecture cause fatal errors.
 
-     `-ACA' is equivalent to `-ACA_A'; `-AKC' is equivalent to `-AMC'.
+     '-ACA' is equivalent to '-ACA_A'; '-AKC' is equivalent to '-AMC'.
      Synonyms are provided for compatibility with other tools.
 
-     If you do not specify any of these options, `as' generates code
-     for any instruction or feature that is supported by _some_ version
-     of the 960 (even if this means mixing architectures!).  In
-     principle, `as' attempts to deduce the minimal sufficient
-     processor type if none is specified; depending on the object code
-     format, the processor type may be recorded in the object file.  If
-     it is critical that the `as' output match a specific architecture,
+     If you do not specify any of these options, 'as' generates code for
+     any instruction or feature that is supported by _some_ version of
+     the 960 (even if this means mixing architectures!).  In principle,
+     'as' attempts to deduce the minimal sufficient processor type if
+     none is specified; depending on the object code format, the
+     processor type may be recorded in the object file.  If it is
+     critical that the 'as' output match a specific architecture,
      specify that architecture explicitly.
 
-`-b'
+'-b'
      Add code to collect information about conditional branches taken,
      for later optimization using branch prediction bits.  (The
      conditional branch instructions have branch prediction bits in the
      CA, CB, and CC architectures.)  If BR represents a conditional
      branch instruction, the following represents the code generated by
-     the assembler when `-b' is specified:
+     the assembler when '-b' is specified:
 
                   call    INCREMENT ROUTINE
                   .word   0       # pre-counter
@@ -11097,9 +10847,9 @@ File: as.info,  Node: Options-i960,  Next: Floating Point-i960,  Up: i960-Depend
      branch was _not_ taken; the difference between the two counters is
      the number of times the branch _was_ taken.
 
-     A table of every such `Label' is also generated, so that the
-     external postprocessor `gbr960' (supplied by Intel) can locate all
-     the counters.  This table is always labeled `__BRANCH_TABLE__';
+     A table of every such 'Label' is also generated, so that the
+     external postprocessor 'gbr960' (supplied by Intel) can locate all
+     the counters.  This table is always labeled '__BRANCH_TABLE__';
      this is a local symbol to permit collecting statistics for many
      separate object files.  The table is word aligned, and begins with
      a two-word header.  The first word, initialized to 0, is used in
@@ -11117,24 +10867,24 @@ File: as.info,  Node: Options-i960,  Next: Floating Point-i960,  Up: i960-Depend
                          __BRANCH_TABLE__ layout
 
      The first word of the header is used to locate multiple branch
-     tables, since each object file may contain one. Normally the links
+     tables, since each object file may contain one.  Normally the links
      are maintained with a call to an initialization routine, placed at
      the beginning of each function in the file.  The GNU C compiler
-     generates these calls automatically when you give it a `-b' option.
-     For further details, see the documentation of `gbr960'.
+     generates these calls automatically when you give it a '-b' option.
+     For further details, see the documentation of 'gbr960'.
 
-`-no-relax'
+'-no-relax'
      Normally, Compare-and-Branch instructions with targets that require
      displacements greater than 13 bits (or that have external targets)
-     are replaced with the corresponding compare (or `chkbit') and
-     branch instructions.  You can use the `-no-relax' option to
-     specify that `as' should generate errors instead, if the target
+     are replaced with the corresponding compare (or 'chkbit') and
+     branch instructions.  You can use the '-no-relax' option to specify
+     that 'as' should generate errors instead, if the target
      displacement is larger than 13 bits.
 
      This option does not affect the Compare-and-Jump instructions; the
      code emitted for them is _always_ adjusted when necessary
      (depending on displacement size), regardless of whether you use
-     `-no-relax'.
+     '-no-relax'.
 
 
 File: as.info,  Node: Floating Point-i960,  Next: Directives-i960,  Prev: Options-i960,  Up: i960-Dependent
@@ -11142,8 +10892,8 @@ File: as.info,  Node: Floating Point-i960,  Next: Directives-i960,  Prev: Option
 9.17.2 Floating Point
 ---------------------
 
-`as' generates IEEE floating-point numbers for the directives `.float',
-`.double', `.extended', and `.single'.
+'as' generates IEEE floating-point numbers for the directives '.float',
+'.double', '.extended', and '.single'.
 
 
 File: as.info,  Node: Directives-i960,  Next: Opcodes for i960,  Prev: Floating Point-i960,  Up: i960-Dependent
@@ -11151,42 +10901,42 @@ File: as.info,  Node: Directives-i960,  Next: Opcodes for i960,  Prev: Floating
 9.17.3 i960 Machine Directives
 ------------------------------
 
-`.bss SYMBOL, LENGTH, ALIGN'
-     Reserve LENGTH bytes in the bss section for a local SYMBOL,
-     aligned to the power of two specified by ALIGN.  LENGTH and ALIGN
-     must be positive absolute expressions.  This directive differs
-     from `.lcomm' only in that it permits you to specify an alignment.
-     *Note `.lcomm': Lcomm.
+'.bss SYMBOL, LENGTH, ALIGN'
+     Reserve LENGTH bytes in the bss section for a local SYMBOL, aligned
+     to the power of two specified by ALIGN.  LENGTH and ALIGN must be
+     positive absolute expressions.  This directive differs from
+     '.lcomm' only in that it permits you to specify an alignment.
+     *Note '.lcomm': Lcomm.
 
-`.extended FLONUMS'
-     `.extended' expects zero or more flonums, separated by commas; for
-     each flonum, `.extended' emits an IEEE extended-format (80-bit)
+'.extended FLONUMS'
+     '.extended' expects zero or more flonums, separated by commas; for
+     each flonum, '.extended' emits an IEEE extended-format (80-bit)
      floating-point number.
 
-`.leafproc CALL-LAB, BAL-LAB'
-     You can use the `.leafproc' directive in conjunction with the
-     optimized `callj' instruction to enable faster calls of leaf
+'.leafproc CALL-LAB, BAL-LAB'
+     You can use the '.leafproc' directive in conjunction with the
+     optimized 'callj' instruction to enable faster calls of leaf
      procedures.  If a procedure is known to call no other procedures,
-     you may define an entry point that skips procedure prolog code
-     (and that does not depend on system-supplied saved context), and
-     declare it as the BAL-LAB using `.leafproc'.  If the procedure
-     also has an entry point that goes through the normal prolog, you
-     can specify that entry point as CALL-LAB.
+     you may define an entry point that skips procedure prolog code (and
+     that does not depend on system-supplied saved context), and declare
+     it as the BAL-LAB using '.leafproc'.  If the procedure also has an
+     entry point that goes through the normal prolog, you can specify
+     that entry point as CALL-LAB.
 
-     A `.leafproc' declaration is meant for use in conjunction with the
-     optimized call instruction `callj'; the directive records the data
-     needed later to choose between converting the `callj' into a `bal'
-     or a `call'.
+     A '.leafproc' declaration is meant for use in conjunction with the
+     optimized call instruction 'callj'; the directive records the data
+     needed later to choose between converting the 'callj' into a 'bal'
+     or a 'call'.
 
      CALL-LAB is optional; if only one argument is present, or if the
      two arguments are identical, the single argument is assumed to be
-     the `bal' entry point.
+     the 'bal' entry point.
 
-`.sysproc NAME, INDEX'
-     The `.sysproc' directive defines a name for a system procedure.
-     After you define it using `.sysproc', you can use NAME to refer to
+'.sysproc NAME, INDEX'
+     The '.sysproc' directive defines a name for a system procedure.
+     After you define it using '.sysproc', you can use NAME to refer to
      the system procedure identified by INDEX when calling procedures
-     with the optimized call instruction `callj'.
+     with the optimized call instruction 'callj'.
 
      Both arguments are required; INDEX must be between 0 and 31
      (inclusive).
@@ -11202,26 +10952,26 @@ Command-line Options: Options-i960. for a discussion of selecting the
 instruction subset for a particular 960 architecture.
 
    Some opcodes are processed beyond simply emitting a single
-corresponding instruction: `callj', and Compare-and-Branch or
+corresponding instruction: 'callj', and Compare-and-Branch or
 Compare-and-Jump instructions with target displacements larger than 13
 bits.
 
 * Menu:
 
-* callj-i960::                  `callj'
+* callj-i960::                  'callj'
 * Compare-and-branch-i960::     Compare-and-Branch
 
 
 File: as.info,  Node: callj-i960,  Next: Compare-and-branch-i960,  Up: Opcodes for i960
 
-9.17.4.1 `callj'
+9.17.4.1 'callj'
 ................
 
-You can write `callj' to have the assembler or the linker determine the
-most appropriate form of subroutine call: `call', `bal', or `calls'.
-If the assembly source contains enough information--a `.leafproc' or
-`.sysproc' directive defining the operand--then `as' translates the
-`callj'; if not, it simply emits the `callj', leaving it for the linker
+You can write 'callj' to have the assembler or the linker determine the
+most appropriate form of subroutine call: 'call', 'bal', or 'calls'.  If
+the assembly source contains enough information--a '.leafproc' or
+'.sysproc' directive defining the operand--then 'as' translates the
+'callj'; if not, it simply emits the 'callj', leaving it for the linker
 to resolve.
 
 
@@ -11237,12 +10987,12 @@ enough away that its address won't fit in 13 bits, the assembler can
 either issue an error, or convert your Compare-and-Branch instruction
 into separate instructions to do the compare and the branch.
 
-   Whether `as' gives an error or expands the instruction depends on
-two choices you can make: whether you use the `-no-relax' option, and
+   Whether 'as' gives an error or expands the instruction depends on two
+choices you can make: whether you use the '-no-relax' option, and
 whether you use a "Compare and Branch" instruction or a "Compare and
 Jump" instruction.  The "Jump" instructions are _always_ expanded if
 necessary; the "Branch" instructions are expanded when necessary
-_unless_ you specify `-no-relax'--in which case `as' gives an error
+_unless_ you specify '-no-relax'--in which case 'as' gives an error
 instead.
 
    These are the Compare-and-Branch instructions, their "Jump" variants,
@@ -11284,15 +11034,15 @@ File: as.info,  Node: i960-Chars,  Up: Syntax of i960
 9.17.5.1 Special Characters
 ...........................
 
-The presence of a `#' on a line indicates the start of a comment that
+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
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can also be a logical
 line number directive (*note Comments::) or a preprocessor control
 command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -11313,7 +11063,7 @@ File: as.info,  Node: IA-64 Options,  Next: IA-64 Syntax,  Up: IA-64-Dependent
 9.18.1 Options
 --------------
 
-`-mconstant-gp'
+'-mconstant-gp'
      This option instructs the assembler to mark the resulting object
      file as using the "constant GP" model.  With this model, it is
      assumed that the entire program uses a single global pointer (GP)
@@ -11321,79 +11071,78 @@ File: as.info,  Node: IA-64 Options,  Next: IA-64 Syntax,  Up: IA-64-Dependent
      machine code emitted by the assembler.  All it does is turn on the
      EF_IA_64_CONS_GP flag in the ELF file header.
 
-`-mauto-pic'
+'-mauto-pic'
      This option instructs the assembler to mark the resulting object
      file as using the "constant GP without function descriptor" data
      model.  This model is like the "constant GP" model, except that it
      additionally does away with function descriptors.  What this means
-     is that the address of a function refers directly to the
-     function's code entry-point.  Normally, such an address would
-     refer to a function descriptor, which contains both the code
-     entry-point and the GP-value needed by the function.  Note that
-     this option does not in any fashion affect the machine code
-     emitted by the assembler.  All it does is turn on the
-     EF_IA_64_NOFUNCDESC_CONS_GP flag in the ELF file header.
-
-`-milp32'
-`-milp64'
-`-mlp64'
-`-mp64'
+     is that the address of a function refers directly to the function's
+     code entry-point.  Normally, such an address would refer to a
+     function descriptor, which contains both the code entry-point and
+     the GP-value needed by the function.  Note that this option does
+     not in any fashion affect the machine code emitted by the
+     assembler.  All it does is turn on the EF_IA_64_NOFUNCDESC_CONS_GP
+     flag in the ELF file header.
+
+'-milp32'
+'-milp64'
+'-mlp64'
+'-mp64'
      These options select the data model.  The assembler defaults to
-     `-mlp64' (LP64 data model).
-
-`-mle'
-`-mbe'
-     These options select the byte order.  The `-mle' option selects
-     little-endian byte order (default) and `-mbe' selects big-endian
-     byte order.  Note that IA-64 machine code always uses
-     little-endian byte order.
-
-`-mtune=itanium1'
-`-mtune=itanium2'
-     Tune for a particular IA-64 CPU, ITANIUM1 or ITANIUM2. The default
+     '-mlp64' (LP64 data model).
+
+'-mle'
+'-mbe'
+     These options select the byte order.  The '-mle' option selects
+     little-endian byte order (default) and '-mbe' selects big-endian
+     byte order.  Note that IA-64 machine code always uses little-endian
+     byte order.
+
+'-mtune=itanium1'
+'-mtune=itanium2'
+     Tune for a particular IA-64 CPU, ITANIUM1 or ITANIUM2.  The default
      is ITANIUM2.
 
-`-munwind-check=warning'
-`-munwind-check=error'
+'-munwind-check=warning'
+'-munwind-check=error'
      These options control what the assembler will do when performing
-     consistency checks on unwind directives.  `-munwind-check=warning'
+     consistency checks on unwind directives.  '-munwind-check=warning'
      will make the assembler issue a warning when an unwind directive
-     check fails.  This is the default.  `-munwind-check=error' will
+     check fails.  This is the default.  '-munwind-check=error' will
      make the assembler issue an error when an unwind directive check
      fails.
 
-`-mhint.b=ok'
-`-mhint.b=warning'
-`-mhint.b=error'
-     These options control what the assembler will do when the `hint.b'
-     instruction is used.  `-mhint.b=ok' will make the assembler accept
-     `hint.b'.  `-mint.b=warning' will make the assembler issue a
-     warning when `hint.b' is used.  `-mhint.b=error' will make the
-     assembler treat `hint.b' as an error, which is the default.
-
-`-x'
-`-xexplicit'
+'-mhint.b=ok'
+'-mhint.b=warning'
+'-mhint.b=error'
+     These options control what the assembler will do when the 'hint.b'
+     instruction is used.  '-mhint.b=ok' will make the assembler accept
+     'hint.b'.  '-mint.b=warning' will make the assembler issue a
+     warning when 'hint.b' is used.  '-mhint.b=error' will make the
+     assembler treat 'hint.b' as an error, which is the default.
+
+'-x'
+'-xexplicit'
      These options turn on dependency violation checking.
 
-`-xauto'
+'-xauto'
      This option instructs the assembler to automatically insert stop
      bits where necessary to remove dependency violations.  This is the
      default mode.
 
-`-xnone'
+'-xnone'
      This option turns off dependency violation checking.
 
-`-xdebug'
+'-xdebug'
      This turns on debug output intended to help tracking down bugs in
      the dependency violation checker.
 
-`-xdebugn'
+'-xdebugn'
      This is a shortcut for -xnone -xdebug.
 
-`-xdebugx'
+'-xdebugx'
      This is a shortcut for -xexplicit -xdebug.
 
-
 
 File: as.info,  Node: IA-64 Syntax,  Next: IA-64 Opcodes,  Prev: IA-64 Options,  Up: IA-64-Dependent
 
@@ -11416,9 +11165,9 @@ File: as.info,  Node: IA-64-Chars,  Next: IA-64-Regs,  Up: IA-64 Syntax
 9.18.2.1 Special Characters
 ...........................
 
-`//' is the line comment token.
+'//' is the line comment token.
 
-   `;' can be used instead of a newline to separate statements.
+   ';' can be used instead of a newline to separate statements.
 
 
 File: as.info,  Node: IA-64-Regs,  Next: IA-64-Bits,  Prev: IA-64-Chars,  Up: IA-64 Syntax
@@ -11426,19 +11175,19 @@ File: as.info,  Node: IA-64-Regs,  Next: IA-64-Bits,  Prev: IA-64-Chars,  Up: IA
 9.18.2.2 Register Names
 .......................
 
-The 128 integer registers are referred to as `rN'.  The 128
-floating-point registers are referred to as `fN'.  The 128 application
-registers are referred to as `arN'.  The 128 control registers are
-referred to as `crN'.  The 64 one-bit predicate registers are referred
-to as `pN'.  The 8 branch registers are referred to as `bN'.  In
-addition, the assembler defines a number of aliases: `gp' (`r1'), `sp'
-(`r12'), `rp' (`b0'), `ret0' (`r8'), `ret1' (`r9'), `ret2' (`r10'),
-`ret3' (`r9'), `fargN' (`f8+N'), and `fretN' (`f8+N').
+The 128 integer registers are referred to as 'rN'.  The 128
+floating-point registers are referred to as 'fN'.  The 128 application
+registers are referred to as 'arN'.  The 128 control registers are
+referred to as 'crN'.  The 64 one-bit predicate registers are referred
+to as 'pN'.  The 8 branch registers are referred to as 'bN'.  In
+addition, the assembler defines a number of aliases: 'gp' ('r1'), 'sp'
+('r12'), 'rp' ('b0'), 'ret0' ('r8'), 'ret1' ('r9'), 'ret2' ('r10'),
+'ret3' ('r9'), 'fargN' ('f8+N'), and 'fretN' ('f8+N').
 
    For convenience, the assembler also defines aliases for all named
-application and control registers.  For example, `ar.bsp' refers to the
-register backing store pointer (`ar17').  Similarly, `cr.eoi' refers to
-the end-of-interrupt register (`cr67').
+application and control registers.  For example, 'ar.bsp' refers to the
+register backing store pointer ('ar17').  Similarly, 'cr.eoi' refers to
+the end-of-interrupt register ('cr67').
 
 
 File: as.info,  Node: IA-64-Bits,  Next: IA-64-Relocs,  Prev: IA-64-Regs,  Up: IA-64 Syntax
@@ -11447,9 +11196,9 @@ File: as.info,  Node: IA-64-Bits,  Next: IA-64-Relocs,  Prev: IA-64-Regs,  Up: I
 ........................................................
 
 The assembler defines bit masks for each of the bits in the IA-64
-processor status register.  For example, `psr.ic' corresponds to a
-value of 0x2000.  These masks are primarily intended for use with the
-`ssm'/`sum' and `rsm'/`rum' instructions, but they can be used anywhere
+processor status register.  For example, 'psr.ic' corresponds to a value
+of 0x2000.  These masks are primarily intended for use with the
+'ssm'/'sum' and 'rsm'/'rum' instructions, but they can be used anywhere
 else where an integer constant is expected.
 
 
@@ -11458,12 +11207,12 @@ File: as.info,  Node: IA-64-Relocs,  Prev: IA-64-Bits,  Up: IA-64 Syntax
 9.18.2.4 Relocations
 ....................
 
-In addition to the standard IA-64 relocations, the following
-relocations are implemented by `as':
+In addition to the standard IA-64 relocations, the following relocations
+are implemented by 'as':
 
-`@slotcount(V)'
+'@slotcount(V)'
      Convert the address offset V into a slot count.  This pseudo
-     function is available only on VMS.  The expression V must be known
+     function is available only on VMS. The expression V must be known
      at assembly time: it can't reference undefined symbols or symbols
      in different sections.
 
@@ -11494,18 +11243,17 @@ File: as.info,  Node: IP2K-Opts,  Next: IP2K-Syntax,  Up: IP2K-Dependent
 9.19.1 IP2K Options
 -------------------
 
-The Ubicom IP2K version of `as' has a few machine dependent options:
+The Ubicom IP2K version of 'as' has a few machine dependent options:
 
-`-mip2022ext'
-     `as' can assemble the extended IP2022 instructions, but it will
+'-mip2022ext'
+     'as' can assemble the extended IP2022 instructions, but it will
      only do so if this is specifically allowed via this command line
      option.
 
-`-mip2022'
+'-mip2022'
      This option restores the assembler's default behaviour of not
      permitting the extended IP2022 instructions to be assembled.
 
-
 
 File: as.info,  Node: IP2K-Syntax,  Prev: IP2K-Opts,  Up: IP2K-Dependent
 
@@ -11522,10 +11270,10 @@ File: as.info,  Node: IP2K-Chars,  Up: IP2K-Syntax
 9.19.2.1 Special Characters
 ...........................
 
-The presence of a `;' on a line indicates the start of a comment that
+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
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can also be a logical
 line number directive (*note Comments::) or a preprocessor control
 command (*note Preprocessing::).
@@ -11551,34 +11299,33 @@ File: as.info,  Node: LM32 Options,  Next: LM32 Syntax,  Up: LM32-Dependent
 9.20.1 Options
 --------------
 
-`-mmultiply-enabled'
+'-mmultiply-enabled'
      Enable multiply instructions.
 
-`-mdivide-enabled'
+'-mdivide-enabled'
      Enable divide instructions.
 
-`-mbarrel-shift-enabled'
+'-mbarrel-shift-enabled'
      Enable barrel-shift instructions.
 
-`-msign-extend-enabled'
+'-msign-extend-enabled'
      Enable sign extend instructions.
 
-`-muser-enabled'
+'-muser-enabled'
      Enable user defined instructions.
 
-`-micache-enabled'
+'-micache-enabled'
      Enable instruction cache related CSRs.
 
-`-mdcache-enabled'
+'-mdcache-enabled'
      Enable data cache related CSRs.
 
-`-mbreak-enabled'
+'-mbreak-enabled'
      Enable break instructions.
 
-`-mall-enabled'
+'-mall-enabled'
      Enable all instructions and CSRs.
 
-
 
 File: as.info,  Node: LM32 Syntax,  Next: LM32 Opcodes,  Prev: LM32 Options,  Up: LM32-Dependent
 
@@ -11597,71 +11344,52 @@ File: as.info,  Node: LM32-Regs,  Next: LM32-Modifiers,  Up: LM32 Syntax
 9.20.2.1 Register Names
 .......................
 
-LM32 has 32 x 32-bit general purpose registers `r0', `r1', ... `r31'.
+LM32 has 32 x 32-bit general purpose registers 'r0', 'r1', ...  'r31'.
 
-   The following aliases are defined: `gp' - `r26', `fp' - `r27', `sp'
-- `r28', `ra' - `r29', `ea' - `r30', `ba' - `r31'.
+   The following aliases are defined: 'gp' - 'r26', 'fp' - 'r27', 'sp' -
+'r28', 'ra' - 'r29', 'ea' - 'r30', 'ba' - 'r31'.
 
    LM32 has the following Control and Status Registers (CSRs).
 
-`IE'
+'IE'
      Interrupt enable.
-
-`IM'
+'IM'
      Interrupt mask.
-
-`IP'
+'IP'
      Interrupt pending.
-
-`ICC'
+'ICC'
      Instruction cache control.
-
-`DCC'
+'DCC'
      Data cache control.
-
-`CC'
+'CC'
      Cycle counter.
-
-`CFG'
+'CFG'
      Configuration.
-
-`EBA'
+'EBA'
      Exception base address.
-
-`DC'
+'DC'
      Debug control.
-
-`DEBA'
+'DEBA'
      Debug exception base address.
-
-`JTX'
+'JTX'
      JTAG transmit.
-
-`JRX'
+'JRX'
      JTAG receive.
-
-`BP0'
+'BP0'
      Breakpoint 0.
-
-`BP1'
+'BP1'
      Breakpoint 1.
-
-`BP2'
+'BP2'
      Breakpoint 2.
-
-`BP3'
+'BP3'
      Breakpoint 3.
-
-`WP0'
+'WP0'
      Watchpoint 0.
-
-`WP1'
+'WP1'
      Watchpoint 1.
-
-`WP2'
+'WP2'
      Watchpoint 2.
-
-`WP3'
+'WP3'
      Watchpoint 3.
 
 
@@ -11676,11 +11404,13 @@ following:
 
      modifier(relocatable-expression)
 
-`lo'
+'lo'
+
      This modifier allows you to use bits 0 through 15 of an address
      expression as 16 bit relocatable expression.
 
-`hi'
+'hi'
+
      This modifier allows you to use bits 16 through 23 of an address
      expression as 16 bit relocatable expression.
 
@@ -11689,44 +11419,47 @@ following:
           ori  r4, r4, lo(sym+10)
           orhi r4, r4, hi(sym+10)
 
-`gp'
+'gp'
+
      This modified creates a 16-bit relocatable expression that is the
      offset of the symbol from the global pointer.
 
           mva r4, gp(sym)
 
-`got'
+'got'
+
      This modifier places a symbol in the GOT and creates a 16-bit
      relocatable expression that is the offset into the GOT of this
      symbol.
 
           lw r4, (gp+got(sym))
 
-`gotofflo16'
-     This modifier allows you to use the bits 0 through 15 of an
-     address which is an offset from the GOT.
+'gotofflo16'
+
+     This modifier allows you to use the bits 0 through 15 of an address
+     which is an offset from the GOT.
+
+'gotoffhi16'
 
-`gotoffhi16'
      This modifier allows you to use the bits 16 through 31 of an
      address which is an offset from the GOT.
 
           orhi r4, r4, gotoffhi16(lsym)
           addi r4, r4, gotofflo16(lsym)
 
-
 
 File: as.info,  Node: LM32-Chars,  Prev: LM32-Modifiers,  Up: LM32 Syntax
 
 9.20.2.3 Special Characters
 ...........................
 
-The presence of a `#' on a line indicates the start of a comment that
-extends to the end of the current line.  Note that 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
+The presence of a '#' on a line indicates the start of a comment that
+extends to the end of the current line.  Note that 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 semicolon (`;') can be used to separate multiple statements on the
+   A semicolon (';') can be used to separate multiple statements on the
 same line.
 
 
@@ -11736,9 +11469,9 @@ File: as.info,  Node: LM32 Opcodes,  Prev: LM32 Syntax,  Up: LM32-Dependent
 --------------
 
 For detailed information on the LM32 machine instruction set, see
-`http://www.latticesemi.com/products/intellectualproperty/ipcores/mico32/'.
+<http://www.latticesemi.com/products/intellectualproperty/ipcores/mico32/>.
 
-   `as' implements all the standard LM32 opcodes.
+   'as' implements all the standard LM32 opcodes.
 
 
 File: as.info,  Node: M32C-Dependent,  Next: M32R-Dependent,  Prev: LM32-Dependent,  Up: Machine Dependencies
@@ -11746,10 +11479,10 @@ File: as.info,  Node: M32C-Dependent,  Next: M32R-Dependent,  Prev: LM32-Depende
 9.21 M32C Dependent Features
 ============================
 
-   `as' can assemble code for several different members of the Renesas
-M32C family.  Normally the default is to assemble code for the M16C
-microprocessor.  The `-m32c' option may be used to change the default
-to the M32C microprocessor.
+'as' can assemble code for several different members of the Renesas M32C
+family.  Normally the default is to assemble code for the M16C
+microprocessor.  The '-m32c' option may be used to change the default to
+the M32C microprocessor.
 
 * Menu:
 
@@ -11762,21 +11495,20 @@ File: as.info,  Node: M32C-Opts,  Next: M32C-Syntax,  Up: M32C-Dependent
 9.21.1 M32C Options
 -------------------
 
-The Renesas M32C version of `as' has these machine-dependent options:
+The Renesas M32C version of 'as' has these machine-dependent options:
 
-`-m32c'
+'-m32c'
      Assemble M32C instructions.
 
-`-m16c'
+'-m16c'
      Assemble M16C instructions (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.
 
-
 
 File: as.info,  Node: M32C-Syntax,  Prev: M32C-Opts,  Up: M32C-Dependent
 
@@ -11799,12 +11531,13 @@ M32C instruction operands.  The general syntax is the following:
 
      %modifier(symbol)
 
-`%dsp8'
-`%dsp16'
+'%dsp8'
+'%dsp16'
+
      These modifiers override the assembler's assumptions about how big
      a symbol's address is.  Normally, when it sees an operand like
-     `sym[a0]' it assumes `sym' may require the widest displacement
-     field (16 bits for `-m16c', 24 bits for `-m32c').  These modifiers
+     'sym[a0]' it assumes 'sym' may require the widest displacement
+     field (16 bits for '-m16c', 24 bits for '-m32c').  These modifiers
      tell it to assume the address will fit in an 8 or 16 bit
      (respectively) unsigned displacement.  Note that, of course, if it
      doesn't actually fit you will get linker errors.  Example:
@@ -11812,25 +11545,28 @@ M32C instruction operands.  The general syntax is the following:
           mov.w %dsp8(sym)[a0],r1
           mov.b #0,%dsp8(sym)[a0]
 
-`%hi8'
+'%hi8'
+
      This modifier allows you to load bits 16 through 23 of a 24 bit
      address into an 8 bit register.  This is useful with, for example,
-     the M16C `smovf' instruction, which expects a 20 bit address in
-     `r1h' and `a0'.  Example:
+     the M16C 'smovf' instruction, which expects a 20 bit address in
+     'r1h' and 'a0'.  Example:
 
           mov.b #%hi8(sym),r1h
           mov.w #%lo16(sym),a0
           smovf.b
 
-`%lo16'
+'%lo16'
+
      Likewise, this modifier allows you to load bits 0 through 15 of a
      24 bit address into a 16 bit register.
 
-`%hi16'
+'%hi16'
+
      This modifier allows you to load bits 16 through 31 of a 32 bit
      address into a 16 bit register.  While the M32C family only has 24
      bits of address space, it does support addresses in pairs of 16 bit
-     registers (like `a1a0' for the `lde' instruction).  This modifier
+     registers (like 'a1a0' for the 'lde' instruction).  This modifier
      is for loading the upper half in such cases.  Example:
 
           mov.w #%hi16(sym),a1
@@ -11838,22 +11574,21 @@ M32C instruction operands.  The general syntax is the following:
           ...
           lde.w [a1a0],r1
 
-
 
 File: as.info,  Node: M32C-Chars,  Prev: M32C-Modifiers,  Up: M32C-Syntax
 
 9.21.2.2 Special Characters
 ...........................
 
-The presence of a `;' character on a line indicates the start of a
+The presence of a ';' character 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, the whole line is
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can also be a logical
 line number directive (*note Comments::) or a preprocessor control
 command (*note Preprocessing::).
 
-   The `|' character can be used to separate statements on the same
+   The '|' character can be used to separate statements on the same
 line.
 
 
@@ -11874,153 +11609,152 @@ File: as.info,  Node: M32R-Opts,  Next: M32R-Directives,  Up: M32R-Dependent
 9.22.1 M32R Options
 -------------------
 
-The Renease M32R version of `as' has a few machine dependent options:
+The Renease M32R version of 'as' has a few machine dependent options:
 
-`-m32rx'
-     `as' can assemble code for several different members of the
-     Renesas M32R family.  Normally the default is to assemble code for
-     the M32R microprocessor.  This option may be used to change the
-     default to the M32RX microprocessor, which adds some more
-     instructions to the basic M32R instruction set, and some
-     additional parameters to some of the original instructions.
+'-m32rx'
+     'as' can assemble code for several different members of the Renesas
+     M32R family.  Normally the default is to assemble code for the M32R
+     microprocessor.  This option may be used to change the default to
+     the M32RX microprocessor, which adds some more instructions to the
+     basic M32R instruction set, and some additional parameters to some
+     of the original instructions.
 
-`-m32r2'
-     This option changes the target processor to the the M32R2
+'-m32r2'
+     This option changes the target processor to the M32R2
      microprocessor.
 
-`-m32r'
+'-m32r'
      This option can be used to restore the assembler's default
      behaviour of assembling for the M32R microprocessor.  This can be
      useful if the default has been changed by a previous command line
      option.
 
-`-little'
+'-little'
      This option tells the assembler to produce little-endian code and
      data.  The default is dependent upon how the toolchain was
      configured.
 
-`-EL'
+'-EL'
      This is a synonym for _-little_.
 
-`-big'
+'-big'
      This option tells the assembler to produce big-endian code and
      data.
 
-`-EB'
+'-EB'
      This is a synonum for _-big_.
 
-`-KPIC'
+'-KPIC'
      This option specifies that the output of the assembler should be
      marked as position-independent code (PIC).
 
-`-parallel'
+'-parallel'
      This option tells the assembler to attempts to combine two
      sequential instructions into a single, parallel instruction, where
      it is legal to do so.
 
-`-no-parallel'
+'-no-parallel'
      This option disables a previously enabled _-parallel_ option.
 
-`-no-bitinst'
+'-no-bitinst'
      This option disables the support for the extended bit-field
      instructions provided by the M32R2.  If this support needs to be
      re-enabled the _-bitinst_ switch can be used to restore it.
 
-`-O'
+'-O'
      This option tells the assembler to attempt to optimize the
      instructions that it produces.  This includes filling delay slots
      and converting sequential instructions into parallel ones.  This
      option implies _-parallel_.
 
-`-warn-explicit-parallel-conflicts'
-     Instructs `as' to produce warning messages when questionable
+'-warn-explicit-parallel-conflicts'
+     Instructs 'as' to produce warning messages when questionable
      parallel instructions are encountered.  This option is enabled by
-     default, but `gcc' disables it when it invokes `as' directly.
+     default, but 'gcc' disables it when it invokes 'as' directly.
      Questionable instructions are those whose behaviour would be
-     different if they were executed sequentially.  For example the
-     code fragment `mv r1, r2 || mv r3, r1' produces a different result
-     from `mv r1, r2 \n mv r3, r1' since the former moves r1 into r3
-     and then r2 into r1, whereas the later moves r2 into r1 and r3.
+     different if they were executed sequentially.  For example the code
+     fragment 'mv r1, r2 || mv r3, r1' produces a different result from
+     'mv r1, r2 \n mv r3, r1' since the former moves r1 into r3 and then
+     r2 into r1, whereas the later moves r2 into r1 and r3.
 
-`-Wp'
+'-Wp'
      This is a shorter synonym for the
      _-warn-explicit-parallel-conflicts_ option.
 
-`-no-warn-explicit-parallel-conflicts'
-     Instructs `as' not to produce warning messages when questionable
+'-no-warn-explicit-parallel-conflicts'
+     Instructs 'as' not to produce warning messages when questionable
      parallel instructions are encountered.
 
-`-Wnp'
+'-Wnp'
      This is a shorter synonym for the
      _-no-warn-explicit-parallel-conflicts_ option.
 
-`-ignore-parallel-conflicts'
+'-ignore-parallel-conflicts'
      This option tells the assembler's to stop checking parallel
      instructions for constraint violations.  This ability is provided
      for hardware vendors testing chip designs and should not be used
      under normal circumstances.
 
-`-no-ignore-parallel-conflicts'
+'-no-ignore-parallel-conflicts'
      This option restores the assembler's default behaviour of checking
      parallel instructions to detect constraint violations.
 
-`-Ip'
+'-Ip'
      This is a shorter synonym for the _-ignore-parallel-conflicts_
      option.
 
-`-nIp'
+'-nIp'
      This is a shorter synonym for the _-no-ignore-parallel-conflicts_
      option.
 
-`-warn-unmatched-high'
+'-warn-unmatched-high'
      This option tells the assembler to produce a warning message if a
-     `.high' pseudo op is encountered without a matching `.low' pseudo
+     '.high' pseudo op is encountered without a matching '.low' pseudo
      op.  The presence of such an unmatched pseudo op usually indicates
      a programming error.
 
-`-no-warn-unmatched-high'
+'-no-warn-unmatched-high'
      Disables a previously enabled _-warn-unmatched-high_ option.
 
-`-Wuh'
+'-Wuh'
      This is a shorter synonym for the _-warn-unmatched-high_ option.
 
-`-Wnuh'
+'-Wnuh'
      This is a shorter synonym for the _-no-warn-unmatched-high_ option.
 
-
 
 File: as.info,  Node: M32R-Directives,  Next: M32R-Warnings,  Prev: M32R-Opts,  Up: M32R-Dependent
 
 9.22.2 M32R Directives
 ----------------------
 
-The Renease M32R version of `as' has a few architecture specific
+The Renease M32R version of 'as' has a few architecture specific
 directives:
 
-`low EXPRESSION'
-     The `low' directive computes the value of its expression and
-     places the lower 16-bits of the result into the immediate-field of
-     the instruction.  For example:
+'low EXPRESSION'
+     The 'low' directive computes the value of its expression and places
+     the lower 16-bits of the result into the immediate-field of the
+     instruction.  For example:
 
              or3   r0, r0, #low(0x12345678) ; compute r0 = r0 | 0x5678
              add3, r0, r0, #low(fred)   ; compute r0 = r0 + low 16-bits of address of fred
 
-`high EXPRESSION'
-     The `high' directive computes the value of its expression and
+'high EXPRESSION'
+     The 'high' directive computes the value of its expression and
      places the upper 16-bits of the result into the immediate-field of
      the instruction.  For example:
 
              seth  r0, #high(0x12345678) ; compute r0 = 0x12340000
              seth, r0, #high(fred)       ; compute r0 = upper 16-bits of address of fred
 
-`shigh EXPRESSION'
-     The `shigh' directive is very similar to the `high' directive.  It
+'shigh EXPRESSION'
+     The 'shigh' directive is very similar to the 'high' directive.  It
      also computes the value of its expression and places the upper
      16-bits of the result into the immediate-field of the instruction.
-     The difference is that `shigh' also checks to see if the lower
+     The difference is that 'shigh' also checks to see if the lower
      16-bits could be interpreted as a signed number, and if so it
      assumes that a borrow will occur from the upper-16 bits.  To
-     compensate for this the `shigh' directive pre-biases the upper 16
+     compensate for this the 'shigh' directive pre-biases the upper 16
      bit value by adding one to it.  For example:
 
      For example:
@@ -12033,10 +11767,10 @@ directives:
      value becomes 0xffff8000.  If this value is then added to
      0x00010000 then the result is 0x00008000.
 
-     This behaviour is to allow for the different semantics of the
-     `or3' and `add3' instructions.  The `or3' instruction treats its
-     16-bit immediate argument as unsigned whereas the `add3' treats
-     its 16-bit immediate as a signed value.  So for example:
+     This behaviour is to allow for the different semantics of the 'or3'
+     and 'add3' instructions.  The 'or3' instruction treats its 16-bit
+     immediate argument as unsigned whereas the 'add3' treats its 16-bit
+     immediate as a signed value.  So for example:
 
              seth  r0, #shigh(0x00008000)
              add3  r0, r0, #low(0x00008000)
@@ -12048,41 +11782,40 @@ directives:
 
      Stores 0xffff8000 into r0.
 
-     Note - the `shigh' directive does not know where in the assembly
+     Note - the 'shigh' directive does not know where in the assembly
      source code the lower 16-bits of the value are going set, so it
-     cannot check to make sure that an `or3' instruction is being used
-     rather than an `add3' instruction.  It is up to the programmer to
+     cannot check to make sure that an 'or3' instruction is being used
+     rather than an 'add3' instruction.  It is up to the programmer to
      make sure that correct directives are used.
 
-`.m32r'
+'.m32r'
      The directive performs a similar thing as the _-m32r_ command line
      option.  It tells the assembler to only accept M32R instructions
      from now on.  An instructions from later M32R architectures are
      refused.
 
-`.m32rx'
-     The directive performs a similar thing as the _-m32rx_ command
-     line option.  It tells the assembler to start accepting the extra
+'.m32rx'
+     The directive performs a similar thing as the _-m32rx_ command line
+     option.  It tells the assembler to start accepting the extra
      instructions in the M32RX ISA as well as the ordinary M32R ISA.
 
-`.m32r2'
-     The directive performs a similar thing as the _-m32r2_ command
-     line option.  It tells the assembler to start accepting the extra
+'.m32r2'
+     The directive performs a similar thing as the _-m32r2_ command line
+     option.  It tells the assembler to start accepting the extra
      instructions in the M32R2 ISA as well as the ordinary M32R ISA.
 
-`.little'
+'.little'
      The directive performs a similar thing as the _-little_ command
      line option.  It tells the assembler to start producing
      little-endian code and data.  This option should be used with care
      as producing mixed-endian binary files is fraught with danger.
 
-`.big'
+'.big'
      The directive performs a similar thing as the _-big_ command line
      option.  It tells the assembler to start producing big-endian code
      and data.  This option should be used with care as producing
      mixed-endian binary files is fraught with danger.
 
-
 
 File: as.info,  Node: M32R-Warnings,  Prev: M32R-Directives,  Up: M32R-Dependent
 
@@ -12090,60 +11823,59 @@ File: as.info,  Node: M32R-Warnings,  Prev: M32R-Directives,  Up: M32R-Dependent
 --------------------
 
 There are several warning and error messages that can be produced by
-`as' which are specific to the M32R:
+'as' which are specific to the M32R:
 
-`output of 1st instruction is the same as an input to 2nd instruction - is this intentional ?'
+'output of 1st instruction is the same as an input to 2nd instruction - is this intentional ?'
      This message is only produced if warnings for explicit parallel
      conflicts have been enabled.  It indicates that the assembler has
      encountered a parallel instruction in which the destination
      register of the left hand instruction is used as an input register
      in the right hand instruction.  For example in this code fragment
-     `mv r1, r2 || neg r3, r1' register r1 is the destination of the
+     'mv r1, r2 || neg r3, r1' register r1 is the destination of the
      move instruction and the input to the neg instruction.
 
-`output of 2nd instruction is the same as an input to 1st instruction - is this intentional ?'
+'output of 2nd instruction is the same as an input to 1st instruction - is this intentional ?'
      This message is only produced if warnings for explicit parallel
      conflicts have been enabled.  It indicates that the assembler has
      encountered a parallel instruction in which the destination
-     register of the right hand instruction is used as an input
-     register in the left hand instruction.  For example in this code
-     fragment `mv r1, r2 || neg r2, r3' register r2 is the destination
-     of the neg instruction and the input to the move instruction.
+     register of the right hand instruction is used as an input register
+     in the left hand instruction.  For example in this code fragment
+     'mv r1, r2 || neg r2, r3' register r2 is the destination of the neg
+     instruction and the input to the move instruction.
 
-`instruction `...' is for the M32RX only'
+'instruction '...' is for the M32RX only'
      This message is produced when the assembler encounters an
-     instruction which is only supported by the M32Rx processor, and
-     the `-m32rx' command line flag has not been specified to allow
-     assembly of such instructions.
+     instruction which is only supported by the M32Rx processor, and the
+     '-m32rx' command line flag has not been specified to allow assembly
+     of such instructions.
 
-`unknown instruction `...''
+'unknown instruction '...''
      This message is produced when the assembler encounters an
      instruction which it does not recognize.
 
-`only the NOP instruction can be issued in parallel on the m32r'
+'only the NOP instruction can be issued in parallel on the m32r'
      This message is produced when the assembler encounters a parallel
      instruction which does not involve a NOP instruction and the
-     `-m32rx' command line flag has not been specified.  Only the M32Rx
+     '-m32rx' command line flag has not been specified.  Only the M32Rx
      processor is able to execute two instructions in parallel.
 
-`instruction `...' cannot be executed in parallel.'
+'instruction '...' cannot be executed in parallel.'
      This message is produced when the assembler encounters a parallel
      instruction which is made up of one or two instructions which
      cannot be executed in parallel.
 
-`Instructions share the same execution pipeline'
+'Instructions share the same execution pipeline'
      This message is produced when the assembler encounters a parallel
      instruction whoes components both use the same execution pipeline.
 
-`Instructions write to the same destination register.'
+'Instructions write to the same destination register.'
      This message is produced when the assembler encounters a parallel
      instruction where both components attempt to modify the same
      register.  For example these code fragments will produce this
-     message: `mv r1, r2 || neg r1, r3' `jl r0 || mv r14, r1' `st r2,
-     @-r1 || mv r1, r3' `mv r1, r2 || ld r0, @r1+' `cmp r1, r2 || addx
+     message: 'mv r1, r2 || neg r1, r3' 'jl r0 || mv r14, r1' 'st r2,
+     @-r1 || mv r1, r3' 'mv r1, r2 || ld r0, @r1+' 'cmp r1, r2 || addx
      r3, r4' (Both write to the condition bit)
 
-
 
 File: as.info,  Node: M68K-Dependent,  Next: M68HC11-Dependent,  Prev: M32R-Dependent,  Up: Machine Dependencies
 
@@ -12165,90 +11897,91 @@ File: as.info,  Node: M68K-Opts,  Next: M68K-Syntax,  Up: M68K-Dependent
 9.23.1 M680x0 Options
 ---------------------
 
-The Motorola 680x0 version of `as' has a few machine dependent options:
+The Motorola 680x0 version of 'as' has a few machine dependent options:
 
-`-march=ARCHITECTURE'
+'-march=ARCHITECTURE'
      This option specifies a target architecture.  The following
-     architectures are recognized: `68000', `68010', `68020', `68030',
-     `68040', `68060', `cpu32', `isaa', `isaaplus', `isab', `isac' and
-     `cfv4e'.
+     architectures are recognized: '68000', '68010', '68020', '68030',
+     '68040', '68060', 'cpu32', 'isaa', 'isaaplus', 'isab', 'isac' and
+     'cfv4e'.
 
-`-mcpu=CPU'
+'-mcpu=CPU'
      This option specifies a target cpu.  When used in conjunction with
-     the `-march' option, the cpu must be within the specified
+     the '-march' option, the cpu must be within the specified
      architecture.  Also, the generic features of the architecture are
      used for instruction generation, rather than those of the specific
      chip.
 
-`-m[no-]68851'
-`-m[no-]68881'
-`-m[no-]div'
-`-m[no-]usp'
-`-m[no-]float'
-`-m[no-]mac'
-`-m[no-]emac'
+'-m[no-]68851'
+'-m[no-]68881'
+'-m[no-]div'
+'-m[no-]usp'
+'-m[no-]float'
+'-m[no-]mac'
+'-m[no-]emac'
+
      Enable or disable various architecture specific features.  If a
      chip or architecture by default supports an option (for instance
-     `-march=isaaplus' includes the `-mdiv' option), explicitly
+     '-march=isaaplus' includes the '-mdiv' option), explicitly
      disabling the option will override the default.
 
-`-l'
-     You can use the `-l' option to shorten the size of references to
-     undefined symbols.  If you do not use the `-l' option, references
-     to undefined symbols are wide enough for a full `long' (32 bits).
-     (Since `as' cannot know where these symbols end up, `as' can only
-     allocate space for the linker to fill in later.  Since `as' does
-     not know how far away these symbols are, it allocates as much
-     space as it can.)  If you use this option, the references are only
-     one word wide (16 bits).  This may be useful if you want the
-     object file to be as small as possible, and you know that the
-     relevant symbols are always less than 17 bits away.
-
-`--register-prefix-optional'
+'-l'
+     You can use the '-l' option to shorten the size of references to
+     undefined symbols.  If you do not use the '-l' option, references
+     to undefined symbols are wide enough for a full 'long' (32 bits).
+     (Since 'as' cannot know where these symbols end up, 'as' can only
+     allocate space for the linker to fill in later.  Since 'as' does
+     not know how far away these symbols are, it allocates as much space
+     as it can.)  If you use this option, the references are only one
+     word wide (16 bits).  This may be useful if you want the object
+     file to be as small as possible, and you know that the relevant
+     symbols are always less than 17 bits away.
+
+'--register-prefix-optional'
      For some configurations, especially those where the compiler
      normally does not prepend an underscore to the names of user
-     variables, the assembler requires a `%' before any use of a
+     variables, the assembler requires a '%' before any use of a
      register name.  This is intended to let the assembler distinguish
-     between C variables and functions named `a0' through `a7', and so
-     on.  The `%' is always accepted, but is not required for certain
-     configurations, notably `sun3'.  The `--register-prefix-optional'
-     option may be used to permit omitting the `%' even for
-     configurations for which it is normally required.  If this is
-     done, it will generally be impossible to refer to C variables and
+     between C variables and functions named 'a0' through 'a7', and so
+     on.  The '%' is always accepted, but is not required for certain
+     configurations, notably 'sun3'.  The '--register-prefix-optional'
+     option may be used to permit omitting the '%' even for
+     configurations for which it is normally required.  If this is done,
+     it will generally be impossible to refer to C variables and
      functions with the same names as register names.
 
-`--bitwise-or'
-     Normally the character `|' is treated as a comment character, which
-     means that it can not be used in expressions.  The `--bitwise-or'
-     option turns `|' into a normal character.  In this mode, you must
-     either use C style comments, or start comments with a `#' character
+'--bitwise-or'
+     Normally the character '|' is treated as a comment character, which
+     means that it can not be used in expressions.  The '--bitwise-or'
+     option turns '|' into a normal character.  In this mode, you must
+     either use C style comments, or start comments with a '#' character
      at the beginning of a line.
 
-`--base-size-default-16  --base-size-default-32'
+'--base-size-default-16 --base-size-default-32'
      If you use an addressing mode with a base register without
-     specifying the size, `as' will normally use the full 32 bit value.
-     For example, the addressing mode `%a0@(%d0)' is equivalent to
-     `%a0@(%d0:l)'.  You may use the `--base-size-default-16' option to
-     tell `as' to default to using the 16 bit value.  In this case,
-     `%a0@(%d0)' is equivalent to `%a0@(%d0:w)'.  You may use the
-     `--base-size-default-32' option to restore the default behaviour.
-
-`--disp-size-default-16  --disp-size-default-32'
-     If you use an addressing mode with a displacement, and the value
-     of the displacement is not known, `as' will normally assume that
-     the value is 32 bits.  For example, if the symbol `disp' has not
-     been defined, `as' will assemble the addressing mode
-     `%a0@(disp,%d0)' as though `disp' is a 32 bit value.  You may use
-     the `--disp-size-default-16' option to tell `as' to instead assume
-     that the displacement is 16 bits.  In this case, `as' will
-     assemble `%a0@(disp,%d0)' as though `disp' is a 16 bit value.  You
-     may use the `--disp-size-default-32' option to restore the default
+     specifying the size, 'as' will normally use the full 32 bit value.
+     For example, the addressing mode '%a0@(%d0)' is equivalent to
+     '%a0@(%d0:l)'.  You may use the '--base-size-default-16' option to
+     tell 'as' to default to using the 16 bit value.  In this case,
+     '%a0@(%d0)' is equivalent to '%a0@(%d0:w)'.  You may use the
+     '--base-size-default-32' option to restore the default behaviour.
+
+'--disp-size-default-16 --disp-size-default-32'
+     If you use an addressing mode with a displacement, and the value of
+     the displacement is not known, 'as' will normally assume that the
+     value is 32 bits.  For example, if the symbol 'disp' has not been
+     defined, 'as' will assemble the addressing mode '%a0@(disp,%d0)' as
+     though 'disp' is a 32 bit value.  You may use the
+     '--disp-size-default-16' option to tell 'as' to instead assume that
+     the displacement is 16 bits.  In this case, 'as' will assemble
+     '%a0@(disp,%d0)' as though 'disp' is a 16 bit value.  You may use
+     the '--disp-size-default-32' option to restore the default
      behaviour.
 
-`--pcrel'
+'--pcrel'
      Always keep branches PC-relative.  In the M680x0 architecture all
      branches are defined as PC-relative.  However, on some processors
-     they are limited to word displacements maximum.  When `as' needs a
+     they are limited to word displacements maximum.  When 'as' needs a
      long branch that is not available, it normally emits an absolute
      jump instead.  This option disables this substitution.  When this
      option is given and no long branches are available, only word
@@ -12257,9 +11990,9 @@ The Motorola 680x0 version of `as' has a few machine dependent options:
      68020 and other processors that have long branches.  *note Branch
      Improvement: M68K-Branch.
 
-`-m68000'
-     `as' can assemble code for several different members of the
-     Motorola 680x0 family.  The default depends upon how `as' was
+'-m68000'
+     'as' can assemble code for several different members of the
+     Motorola 680x0 family.  The default depends upon how 'as' was
      configured when it was built; normally, the default is to assemble
      code for the 68020 microprocessor.  The following options may be
      used to change the default.  These options control which
@@ -12267,87 +12000,87 @@ The Motorola 680x0 version of `as' has a few machine dependent options:
      the 680x0 family are very similar.  For detailed information about
      the differences, see the Motorola manuals.
 
-    `-m68000'
-    `-m68ec000'
-    `-m68hc000'
-    `-m68hc001'
-    `-m68008'
-    `-m68302'
-    `-m68306'
-    `-m68307'
-    `-m68322'
-    `-m68356'
-          Assemble for the 68000. `-m68008', `-m68302', and so on are
-          synonyms for `-m68000', since the chips are the same from the
+     '-m68000'
+     '-m68ec000'
+     '-m68hc000'
+     '-m68hc001'
+     '-m68008'
+     '-m68302'
+     '-m68306'
+     '-m68307'
+     '-m68322'
+     '-m68356'
+          Assemble for the 68000.  '-m68008', '-m68302', and so on are
+          synonyms for '-m68000', since the chips are the same from the
           point of view of the assembler.
 
-    `-m68010'
+     '-m68010'
           Assemble for the 68010.
 
-    `-m68020'
-    `-m68ec020'
+     '-m68020'
+     '-m68ec020'
           Assemble for the 68020.  This is normally the default.
 
-    `-m68030'
-    `-m68ec030'
+     '-m68030'
+     '-m68ec030'
           Assemble for the 68030.
 
-    `-m68040'
-    `-m68ec040'
+     '-m68040'
+     '-m68ec040'
           Assemble for the 68040.
 
-    `-m68060'
-    `-m68ec060'
+     '-m68060'
+     '-m68ec060'
           Assemble for the 68060.
 
-    `-mcpu32'
-    `-m68330'
-    `-m68331'
-    `-m68332'
-    `-m68333'
-    `-m68334'
-    `-m68336'
-    `-m68340'
-    `-m68341'
-    `-m68349'
-    `-m68360'
+     '-mcpu32'
+     '-m68330'
+     '-m68331'
+     '-m68332'
+     '-m68333'
+     '-m68334'
+     '-m68336'
+     '-m68340'
+     '-m68341'
+     '-m68349'
+     '-m68360'
           Assemble for the CPU32 family of chips.
 
-    `-m5200'
-    `-m5202'
-    `-m5204'
-    `-m5206'
-    `-m5206e'
-    `-m521x'
-    `-m5249'
-    `-m528x'
-    `-m5307'
-    `-m5407'
-    `-m547x'
-    `-m548x'
-    `-mcfv4'
-    `-mcfv4e'
+     '-m5200'
+     '-m5202'
+     '-m5204'
+     '-m5206'
+     '-m5206e'
+     '-m521x'
+     '-m5249'
+     '-m528x'
+     '-m5307'
+     '-m5407'
+     '-m547x'
+     '-m548x'
+     '-mcfv4'
+     '-mcfv4e'
           Assemble for the ColdFire family of chips.
 
-    `-m68881'
-    `-m68882'
+     '-m68881'
+     '-m68882'
           Assemble 68881 floating point instructions.  This is the
           default for the 68020, 68030, and the CPU32.  The 68040 and
           68060 always support floating point instructions.
 
-    `-mno-68881'
+     '-mno-68881'
           Do not assemble 68881 floating point instructions.  This is
           the default for 68000 and the 68010.  The 68040 and 68060
           always support floating point instructions, even if this
           option is used.
 
-    `-m68851'
+     '-m68851'
           Assemble 68851 MMU instructions.  This is the default for the
           68020, 68030, and 68060.  The 68040 accepts a somewhat
-          different set of MMU instructions; `-m68851' and `-m68040'
+          different set of MMU instructions; '-m68851' and '-m68040'
           should not be used together.
 
-    `-mno-68851'
+     '-mno-68851'
           Do not assemble 68851 MMU instructions.  This is the default
           for the 68000, 68010, and the CPU32.  The 68040 accepts a
           somewhat different set of MMU instructions.
@@ -12360,61 +12093,61 @@ File: as.info,  Node: M68K-Syntax,  Next: M68K-Moto-Syntax,  Prev: M68K-Opts,  U
 
 This syntax for the Motorola 680x0 was developed at MIT.
 
-   The 680x0 version of `as' uses instructions names and syntax
-compatible with the Sun assembler.  Intervening periods are ignored;
-for example, `movl' is equivalent to `mov.l'.
+   The 680x0 version of 'as' uses instructions names and syntax
+compatible with the Sun assembler.  Intervening periods are ignored; for
+example, 'movl' is equivalent to 'mov.l'.
 
    In the following table APC stands for any of the address registers
-(`%a0' through `%a7'), the program counter (`%pc'), the zero-address
-relative to the program counter (`%zpc'), a suppressed address register
-(`%za0' through `%za7'), or it may be omitted entirely.  The use of
-SIZE means one of `w' or `l', and it may be omitted, along with the
-leading colon, unless a scale is also specified.  The use of SCALE
-means one of `1', `2', `4', or `8', and it may always be omitted along
-with the leading colon.
+('%a0' through '%a7'), the program counter ('%pc'), the zero-address
+relative to the program counter ('%zpc'), a suppressed address register
+('%za0' through '%za7'), or it may be omitted entirely.  The use of SIZE
+means one of 'w' or 'l', and it may be omitted, along with the leading
+colon, unless a scale is also specified.  The use of SCALE means one of
+'1', '2', '4', or '8', and it may always be omitted along with the
+leading colon.
 
    The following addressing modes are understood:
 "Immediate"
-     `#NUMBER'
+     '#NUMBER'
 
 "Data Register"
-     `%d0' through `%d7'
+     '%d0' through '%d7'
 
 "Address Register"
-     `%a0' through `%a7'
-     `%a7' is also known as `%sp', i.e., the Stack Pointer.  `%a6' is
-     also known as `%fp', the Frame Pointer.
+     '%a0' through '%a7'
+     '%a7' is also known as '%sp', i.e., the Stack Pointer.  '%a6' is
+     also known as '%fp', the Frame Pointer.
 
 "Address Register Indirect"
-     `%a0@' through `%a7@'
+     '%a0@' through '%a7@'
 
 "Address Register Postincrement"
-     `%a0@+' through `%a7@+'
+     '%a0@+' through '%a7@+'
 
 "Address Register Predecrement"
-     `%a0@-' through `%a7@-'
+     '%a0@-' through '%a7@-'
 
 "Indirect Plus Offset"
-     `APC@(NUMBER)'
+     'APC@(NUMBER)'
 
 "Index"
-     `APC@(NUMBER,REGISTER:SIZE:SCALE)'
+     'APC@(NUMBER,REGISTER:SIZE:SCALE)'
 
      The NUMBER may be omitted.
 
 "Postindex"
-     `APC@(NUMBER)@(ONUMBER,REGISTER:SIZE:SCALE)'
+     'APC@(NUMBER)@(ONUMBER,REGISTER:SIZE:SCALE)'
 
      The ONUMBER or the REGISTER, but not both, may be omitted.
 
 "Preindex"
-     `APC@(NUMBER,REGISTER:SIZE:SCALE)@(ONUMBER)'
+     'APC@(NUMBER,REGISTER:SIZE:SCALE)@(ONUMBER)'
 
      The NUMBER may be omitted.  Omitting the REGISTER produces the
      Postindex addressing mode.
 
 "Absolute"
-     `SYMBOL', or `DIGITS', optionally followed by `:b', `:w', or `:l'.
+     'SYMBOL', or 'DIGITS', optionally followed by ':b', ':w', or ':l'.
 
 
 File: as.info,  Node: M68K-Moto-Syntax,  Next: M68K-Float,  Prev: M68K-Syntax,  Up: M68K-Dependent
@@ -12423,65 +12156,64 @@ File: as.info,  Node: M68K-Moto-Syntax,  Next: M68K-Float,  Prev: M68K-Syntax,
 ----------------------
 
 The standard Motorola syntax for this chip differs from the syntax
-already discussed (*note Syntax: M68K-Syntax.).  `as' can accept
+already discussed (*note Syntax: M68K-Syntax.).  'as' can accept
 Motorola syntax for operands, even if MIT syntax is used for other
 operands in the same instruction.  The two kinds of syntax are fully
 compatible.
 
    In the following table APC stands for any of the address registers
-(`%a0' through `%a7'), the program counter (`%pc'), the zero-address
-relative to the program counter (`%zpc'), or a suppressed address
-register (`%za0' through `%za7').  The use of SIZE means one of `w' or
-`l', and it may always be omitted along with the leading dot.  The use
-of SCALE means one of `1', `2', `4', or `8', and it may always be
+('%a0' through '%a7'), the program counter ('%pc'), the zero-address
+relative to the program counter ('%zpc'), or a suppressed address
+register ('%za0' through '%za7').  The use of SIZE means one of 'w' or
+'l', and it may always be omitted along with the leading dot.  The use
+of SCALE means one of '1', '2', '4', or '8', and it may always be
 omitted along with the leading asterisk.
 
    The following additional addressing modes are understood:
 
 "Address Register Indirect"
-     `(%a0)' through `(%a7)'
-     `%a7' is also known as `%sp', i.e., the Stack Pointer.  `%a6' is
-     also known as `%fp', the Frame Pointer.
+     '(%a0)' through '(%a7)'
+     '%a7' is also known as '%sp', i.e., the Stack Pointer.  '%a6' is
+     also known as '%fp', the Frame Pointer.
 
 "Address Register Postincrement"
-     `(%a0)+' through `(%a7)+'
+     '(%a0)+' through '(%a7)+'
 
 "Address Register Predecrement"
-     `-(%a0)' through `-(%a7)'
+     '-(%a0)' through '-(%a7)'
 
 "Indirect Plus Offset"
-     `NUMBER(%A0)' through `NUMBER(%A7)', or `NUMBER(%PC)'.
+     'NUMBER(%A0)' through 'NUMBER(%A7)', or 'NUMBER(%PC)'.
 
      The NUMBER may also appear within the parentheses, as in
-     `(NUMBER,%A0)'.  When used with the PC, the NUMBER may be omitted
+     '(NUMBER,%A0)'.  When used with the PC, the NUMBER may be omitted
      (with an address register, omitting the NUMBER produces Address
      Register Indirect mode).
 
 "Index"
-     `NUMBER(APC,REGISTER.SIZE*SCALE)'
+     'NUMBER(APC,REGISTER.SIZE*SCALE)'
 
-     The NUMBER may be omitted, or it may appear within the
-     parentheses.  The APC may be omitted.  The REGISTER and the APC
-     may appear in either order.  If both APC and REGISTER are address
-     registers, and the SIZE and SCALE are omitted, then the first
-     register is taken as the base register, and the second as the
-     index register.
+     The NUMBER may be omitted, or it may appear within the parentheses.
+     The APC may be omitted.  The REGISTER and the APC may appear in
+     either order.  If both APC and REGISTER are address registers, and
+     the SIZE and SCALE are omitted, then the first register is taken as
+     the base register, and the second as the index register.
 
 "Postindex"
-     `([NUMBER,APC],REGISTER.SIZE*SCALE,ONUMBER)'
+     '([NUMBER,APC],REGISTER.SIZE*SCALE,ONUMBER)'
 
      The ONUMBER, or the REGISTER, or both, may be omitted.  Either the
      NUMBER or the APC may be omitted, but not both.
 
 "Preindex"
-     `([NUMBER,APC,REGISTER.SIZE*SCALE],ONUMBER)'
+     '([NUMBER,APC,REGISTER.SIZE*SCALE],ONUMBER)'
 
-     The NUMBER, or the APC, or the REGISTER, or any two of them, may
-     be omitted.  The ONUMBER may be omitted.  The REGISTER and the APC
-     may appear in either order.  If both APC and REGISTER are address
+     The NUMBER, or the APC, or the REGISTER, or any two of them, may be
+     omitted.  The ONUMBER may be omitted.  The REGISTER and the APC may
+     appear in either order.  If both APC and REGISTER are address
      registers, and the SIZE and SCALE are omitted, then the first
-     register is taken as the base register, and the second as the
-     index register.
+     register is taken as the base register, and the second as the index
+     register.
 
 
 File: as.info,  Node: M68K-Float,  Next: M68K-Directives,  Prev: M68K-Moto-Syntax,  Up: M68K-Dependent
@@ -12494,15 +12226,15 @@ free to add the code!
 
    The floating point formats generated by directives are these.
 
-`.float'
-     `Single' precision floating point constants.
+'.float'
+     'Single' precision floating point constants.
 
-`.double'
-     `Double' precision floating point constants.
+'.double'
+     'Double' precision floating point constants.
 
-`.extend'
-`.ldouble'
-     `Extended' precision (`long double') floating point constants.
+'.extend'
+'.ldouble'
+     'Extended' precision ('long double') floating point constants.
 
 
 File: as.info,  Node: M68K-Directives,  Next: M68K-opcodes,  Prev: M68K-Float,  Up: M68K-Dependent
@@ -12513,35 +12245,34 @@ File: as.info,  Node: M68K-Directives,  Next: M68K-opcodes,  Prev: M68K-Float,
 In order to be compatible with the Sun assembler the 680x0 assembler
 understands the following directives.
 
-`.data1'
-     This directive is identical to a `.data 1' directive.
+'.data1'
+     This directive is identical to a '.data 1' directive.
 
-`.data2'
-     This directive is identical to a `.data 2' directive.
+'.data2'
+     This directive is identical to a '.data 2' directive.
 
-`.even'
-     This directive is a special case of the `.align' directive; it
+'.even'
+     This directive is a special case of the '.align' directive; it
      aligns the output to an even byte boundary.
 
-`.skip'
-     This directive is identical to a `.space' directive.
+'.skip'
+     This directive is identical to a '.space' directive.
 
-`.arch NAME'
+'.arch NAME'
      Select the target architecture and extension features.  Valid
-     values for NAME are the same as for the `-march' command line
+     values for NAME are the same as for the '-march' command line
      option.  This directive cannot be specified after any instructions
      have been assembled.  If it is given multiple times, or in
-     conjunction with the `-march' option, all uses must be for the
-     same architecture and extension set.
+     conjunction with the '-march' option, all uses must be for the same
+     architecture and extension set.
 
-`.cpu NAME'
+'.cpu NAME'
      Select the target cpu.  Valid valuse for NAME are the same as for
-     the `-mcpu' command line option.  This directive cannot be
+     the '-mcpu' command line option.  This directive cannot be
      specified after any instructions have been assembled.  If it is
-     given multiple times, or in conjunction with the `-mopt' option,
+     given multiple times, or in conjunction with the '-mopt' option,
      all uses must be for the same cpu.
 
-
 
 File: as.info,  Node: M68K-opcodes,  Prev: M68K-Directives,  Up: M68K-Dependent
 
@@ -12561,10 +12292,10 @@ File: as.info,  Node: M68K-Branch,  Next: M68K-Chars,  Up: M68K-opcodes
 
 Certain pseudo opcodes are permitted for branch instructions.  They
 expand to the shortest branch instruction that reach the target.
-Generally these mnemonics are made by substituting `j' for `b' at the
+Generally these mnemonics are made by substituting 'j' for 'b' at the
 start of a Motorola mnemonic.
 
-   The following table summarizes the pseudo-operations.  A `*' flags
+   The following table summarizes the pseudo-operations.  A '*' flags
 cases that are more fully described after the table:
 
                Displacement
@@ -12580,36 +12311,37 @@ cases that are more fully described after the table:
 
      XX: condition
      NX: negative of condition XX
-                       `*'--see full description below
-         `**'--this expansion mode is disallowed by `--pcrel'
 
-`jbsr'
-`jra'
+                    '*'--see full description below
+         '**'--this expansion mode is disallowed by '--pcrel'
+
+'jbsr'
+'jra'
      These are the simplest jump pseudo-operations; they always map to
      one particular machine instruction, depending on the displacement
      to the branch target.  This instruction will be a byte or word
      branch is that is sufficient.  Otherwise, a long branch will be
      emitted if available.  If no long branches are available and the
-     `--pcrel' option is not given, an absolute long jump will be
-     emitted instead.  If no long branches are available, the `--pcrel'
+     '--pcrel' option is not given, an absolute long jump will be
+     emitted instead.  If no long branches are available, the '--pcrel'
      option is given, and a word branch cannot reach the target, an
      error message is generated.
 
-     In addition to standard branch operands, `as' allows these
-     pseudo-operations to have all operands that are allowed for jsr
-     and jmp, substituting these instructions if the operand given is
-     not valid for a branch instruction.
+     In addition to standard branch operands, 'as' allows these
+     pseudo-operations to have all operands that are allowed for jsr and
+     jmp, substituting these instructions if the operand given is not
+     valid for a branch instruction.
 
-`jXX'
-     Here, `jXX' stands for an entire family of pseudo-operations,
-     where XX is a conditional branch or condition-code test.  The full
-     list of pseudo-ops in this family is:
+'jXX'
+     Here, 'jXX' stands for an entire family of pseudo-operations, where
+     XX is a conditional branch or condition-code test.  The full list
+     of pseudo-ops in this family is:
            jhi   jls   jcc   jcs   jne   jeq   jvc
            jvs   jpl   jmi   jge   jlt   jgt   jle
 
      Usually, each of these pseudo-operations expands to a single branch
      instruction.  However, if a word branch is not sufficient, no long
-     branches are available, and the `--pcrel' option is not given, `as'
+     branches are available, and the '--pcrel' option is not given, 'as'
      issues a longer code fragment in terms of NX, the opposite
      condition to XX.  For example, under these conditions:
               jXX foo
@@ -12618,30 +12350,30 @@ cases that are more fully described after the table:
                jmp foo
            oof:
 
-`dbXX'
+'dbXX'
      The full family of pseudo-operations covered here is
            dbhi   dbls   dbcc   dbcs   dbne   dbeq   dbvc
            dbvs   dbpl   dbmi   dbge   dblt   dbgt   dble
            dbf    dbra   dbt
 
-     Motorola `dbXX' instructions allow word displacements only.  When
-     a word displacement is sufficient, each of these pseudo-operations
+     Motorola 'dbXX' instructions allow word displacements only.  When a
+     word displacement is sufficient, each of these pseudo-operations
      expands to the corresponding Motorola instruction.  When a word
      displacement is not sufficient and long branches are available,
-     when the source reads `dbXX foo', `as' emits
+     when the source reads 'dbXX foo', 'as' emits
                dbXX oo1
                bras oo2
            oo1:bral foo
            oo2:
 
-     If, however, long branches are not available and the `--pcrel'
-     option is not given, `as' emits
+     If, however, long branches are not available and the '--pcrel'
+     option is not given, 'as' emits
                dbXX oo1
                bras oo2
            oo1:jmp foo
            oo2:
 
-`fjXX'
+'fjXX'
      This family includes
            fjne   fjeq   fjge   fjlt   fjgt   fjle   fjf
            fjt    fjgl   fjgle  fjnge  fjngl  fjngle fjngt
@@ -12654,29 +12386,28 @@ cases that are more fully described after the table:
      coprocessor branch instructions allow both word and long
      displacements.
 
-
 
 File: as.info,  Node: M68K-Chars,  Prev: M68K-Branch,  Up: M68K-opcodes
 
 9.23.6.2 Special Characters
 ...........................
 
-Line comments are introduced by the `|' character appearing anywhere on
-a line, unless the `--bitwise-or' command line option has been
+Line comments are introduced by the '|' character appearing anywhere on
+a line, unless the '--bitwise-or' command line option has been
 specified.
 
-   An asterisk (`*') as the first character on a line marks the start
-of a line comment as well.
+   An asterisk ('*') as the first character on a line marks the start of
+a line comment as well.
 
-   A hash character (`#') as the first character on a line also marks
-the start of a line comment, but in this case it could also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).  If the hash character appears
+   A hash character ('#') as the first character on a line also marks
+the start of a line comment, but in this case it could also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).  If the hash character appears
 elsewhere on a line it is used to introduce an immediate value.  (This
 is for compatibility with Sun's assembler).
 
    Multiple statements on the same line can appear if they are separated
-by the `;' character.
+by the ';' character.
 
 
 File: as.info,  Node: M68HC11-Dependent,  Next: Meta-Dependent,  Prev: M68K-Dependent,  Up: Machine Dependencies
@@ -12699,102 +12430,101 @@ File: as.info,  Node: M68HC11-Opts,  Next: M68HC11-Syntax,  Up: M68HC11-Dependen
 9.24.1 M68HC11 and M68HC12 Options
 ----------------------------------
 
-The Motorola 68HC11 and 68HC12 version of `as' have a few machine
+The Motorola 68HC11 and 68HC12 version of 'as' have a few machine
 dependent options.
 
-`-m68hc11'
-     This option switches the assembler into the M68HC11 mode. In this
-     mode, the assembler only accepts 68HC11 operands and mnemonics. It
+'-m68hc11'
+     This option switches the assembler into the M68HC11 mode.  In this
+     mode, the assembler only accepts 68HC11 operands and mnemonics.  It
      produces code for the 68HC11.
 
-`-m68hc12'
-     This option switches the assembler into the M68HC12 mode. In this
-     mode, the assembler also accepts 68HC12 operands and mnemonics. It
-     produces code for the 68HC12. A few 68HC11 instructions are
+'-m68hc12'
+     This option switches the assembler into the M68HC12 mode.  In this
+     mode, the assembler also accepts 68HC12 operands and mnemonics.  It
+     produces code for the 68HC12.  A few 68HC11 instructions are
      replaced by some 68HC12 instructions as recommended by Motorola
      specifications.
 
-`-m68hcs12'
+'-m68hcs12'
      This option switches the assembler into the M68HCS12 mode.  This
-     mode is similar to `-m68hc12' but specifies to assemble for the
+     mode is similar to '-m68hc12' but specifies to assemble for the
      68HCS12 series.  The only difference is on the assembling of the
-     `movb' and `movw' instruction when a PC-relative operand is used.
+     'movb' and 'movw' instruction when a PC-relative operand is used.
 
-`-mm9s12x'
-     This option switches the assembler into the M9S12X mode.  This
-     mode is similar to `-m68hc12' but specifies to assemble for the
-     S12X series which is a superset of the HCS12.
+'-mm9s12x'
+     This option switches the assembler into the M9S12X mode.  This mode
+     is similar to '-m68hc12' but specifies to assemble for the S12X
+     series which is a superset of the HCS12.
 
-`-mm9s12xg'
+'-mm9s12xg'
      This option switches the assembler into the XGATE mode for the RISC
      co-processor featured on some S12X-family chips.
 
-`--xgate-ramoffset'
+'--xgate-ramoffset'
      This option instructs the linker to offset RAM addresses from S12X
      address space into XGATE address space.
 
-`-mshort'
+'-mshort'
      This option controls the ABI and indicates to use a 16-bit integer
-     ABI.  It has no effect on the assembled instructions.  This is the
+     ABI. It has no effect on the assembled instructions.  This is the
      default.
 
-`-mlong'
+'-mlong'
      This option controls the ABI and indicates to use a 32-bit integer
      ABI.
 
-`-mshort-double'
+'-mshort-double'
      This option controls the ABI and indicates to use a 32-bit float
-     ABI.  This is the default.
+     ABI. This is the default.
 
-`-mlong-double'
+'-mlong-double'
      This option controls the ABI and indicates to use a 64-bit float
      ABI.
 
-`--strict-direct-mode'
-     You can use the `--strict-direct-mode' option to disable the
+'--strict-direct-mode'
+     You can use the '--strict-direct-mode' option to disable the
      automatic translation of direct page mode addressing into extended
      mode when the instruction does not support direct mode.  For
-     example, the `clr' instruction does not support direct page mode
-     addressing. When it is used with the direct page mode, `as' will
+     example, the 'clr' instruction does not support direct page mode
+     addressing.  When it is used with the direct page mode, 'as' will
      ignore it and generate an absolute addressing.  This option
-     prevents `as' from doing this, and the wrong usage of the direct
+     prevents 'as' from doing this, and the wrong usage of the direct
      page mode will raise an error.
 
-`--short-branches'
-     The `--short-branches' option turns off the translation of
-     relative branches into absolute branches when the branch offset is
-     out of range. By default `as' transforms the relative branch
-     (`bsr', `bgt', `bge', `beq', `bne', `ble', `blt', `bhi', `bcc',
-     `bls', `bcs', `bmi', `bvs', `bvs', `bra') into an absolute branch
-     when the offset is out of the -128 .. 127 range.  In that case,
-     the `bsr' instruction is translated into a `jsr', the `bra'
-     instruction is translated into a `jmp' and the conditional
-     branches instructions are inverted and followed by a `jmp'. This
-     option disables these translations and `as' will generate an error
-     if a relative branch is out of range. This option does not affect
-     the optimization associated to the `jbra', `jbsr' and `jbXX'
+'--short-branches'
+     The '--short-branches' option turns off the translation of relative
+     branches into absolute branches when the branch offset is out of
+     range.  By default 'as' transforms the relative branch ('bsr',
+     'bgt', 'bge', 'beq', 'bne', 'ble', 'blt', 'bhi', 'bcc', 'bls',
+     'bcs', 'bmi', 'bvs', 'bvs', 'bra') into an absolute branch when the
+     offset is out of the -128 ..  127 range.  In that case, the 'bsr'
+     instruction is translated into a 'jsr', the 'bra' instruction is
+     translated into a 'jmp' and the conditional branches instructions
+     are inverted and followed by a 'jmp'.  This option disables these
+     translations and 'as' will generate an error if a relative branch
+     is out of range.  This option does not affect the optimization
+     associated to the 'jbra', 'jbsr' and 'jbXX' pseudo opcodes.
+
+'--force-long-branches'
+     The '--force-long-branches' option forces the translation of
+     relative branches into absolute branches.  This option does not
+     affect the optimization associated to the 'jbra', 'jbsr' and 'jbXX'
      pseudo opcodes.
 
-`--force-long-branches'
-     The `--force-long-branches' option forces the translation of
-     relative branches into absolute branches. This option does not
-     affect the optimization associated to the `jbra', `jbsr' and
-     `jbXX' pseudo opcodes.
-
-`--print-insn-syntax'
-     You can use the `--print-insn-syntax' option to obtain the syntax
+'--print-insn-syntax'
+     You can use the '--print-insn-syntax' option to obtain the syntax
      description of the instruction when an error is detected.
 
-`--print-opcodes'
-     The `--print-opcodes' option prints the list of all the
-     instructions with their syntax. The first item of each line
+'--print-opcodes'
+     The '--print-opcodes' option prints the list of all the
+     instructions with their syntax.  The first item of each line
      represents the instruction name and the rest of the line indicates
-     the possible operands for that instruction. The list is printed in
-     alphabetical order. Once the list is printed `as' exits.
+     the possible operands for that instruction.  The list is printed in
+     alphabetical order.  Once the list is printed 'as' exits.
 
-`--generate-example'
-     The `--generate-example' option is similar to `--print-opcodes'
-     but it generates an example for each instruction instead.
+'--generate-example'
+     The '--generate-example' option is similar to '--print-opcodes' but
+     it generates an example for each instruction instead.
 
 
 File: as.info,  Node: M68HC11-Syntax,  Next: M68HC11-Modifiers,  Prev: M68HC11-Opts,  Up: M68HC11-Dependent
@@ -12803,23 +12533,22 @@ File: as.info,  Node: M68HC11-Syntax,  Next: M68HC11-Modifiers,  Prev: M68HC11-O
 -------------
 
 In the M68HC11 syntax, the instruction name comes first and it may be
-followed by one or several operands (up to three). Operands are
-separated by comma (`,'). In the normal mode, `as' will complain if too
-many operands are specified for a given instruction. In the MRI mode
-(turned on with `-M' option), it will treat them as comments. Example:
+followed by one or several operands (up to three).  Operands are
+separated by comma (',').  In the normal mode, 'as' will complain if too
+many operands are specified for a given instruction.  In the MRI mode
+(turned on with '-M' option), it will treat them as comments.  Example:
 
      inx
      lda  #23
      bset 2,x #4
      brclr *bot #8 foo
 
-   The presence of a `;' character or a `!' character anywhere on a
-line indicates the start of a comment that extends to the end of that
-line.
+   The presence of a ';' character or a '!' character anywhere on a line
+indicates the start of a comment that extends to the end of that line.
 
-   A `*' or a `#' character at the start of a line also introduces a
+   A '*' or a '#' character at the start of a line also introduces a
 line comment, but these characters do not work elsewhere on the line.
-If the first character of the line is a `#' then as well as starting a
+If the first character of the line is a '#' then as well as starting a
 comment, the line could also be logical line number directive (*note
 Comments::) or a preprocessor control command (*note Preprocessing::).
 
@@ -12828,55 +12557,54 @@ character.
 
    The following addressing modes are understood for 68HC11 and 68HC12:
 "Immediate"
-     `#NUMBER'
+     '#NUMBER'
 
 "Address Register"
-     `NUMBER,X', `NUMBER,Y'
+     'NUMBER,X', 'NUMBER,Y'
 
      The NUMBER may be omitted in which case 0 is assumed.
 
 "Direct Addressing mode"
-     `*SYMBOL', or `*DIGITS'
+     '*SYMBOL', or '*DIGITS'
 
 "Absolute"
-     `SYMBOL', or `DIGITS'
+     'SYMBOL', or 'DIGITS'
 
-   The M68HC12 has other more complex addressing modes. All of them are
+   The M68HC12 has other more complex addressing modes.  All of them are
 supported and they are represented below:
 
 "Constant Offset Indexed Addressing Mode"
-     `NUMBER,REG'
+     'NUMBER,REG'
 
-     The NUMBER may be omitted in which case 0 is assumed.  The
-     register can be either `X', `Y', `SP' or `PC'.  The assembler will
-     use the smaller post-byte definition according to the constant
-     value (5-bit constant offset, 9-bit constant offset or 16-bit
-     constant offset).  If the constant is not known by the assembler
-     it will use the 16-bit constant offset post-byte and the value
-     will be resolved at link time.
+     The NUMBER may be omitted in which case 0 is assumed.  The register
+     can be either 'X', 'Y', 'SP' or 'PC'.  The assembler will use the
+     smaller post-byte definition according to the constant value (5-bit
+     constant offset, 9-bit constant offset or 16-bit constant offset).
+     If the constant is not known by the assembler it will use the
+     16-bit constant offset post-byte and the value will be resolved at
+     link time.
 
 "Offset Indexed Indirect"
-     `[NUMBER,REG]'
+     '[NUMBER,REG]'
 
-     The register can be either `X', `Y', `SP' or `PC'.
+     The register can be either 'X', 'Y', 'SP' or 'PC'.
 
 "Auto Pre-Increment/Pre-Decrement/Post-Increment/Post-Decrement"
-     `NUMBER,-REG' `NUMBER,+REG' `NUMBER,REG-' `NUMBER,REG+'
+     'NUMBER,-REG' 'NUMBER,+REG' 'NUMBER,REG-' 'NUMBER,REG+'
 
-     The number must be in the range `-8'..`+8' and must not be 0.  The
-     register can be either `X', `Y', `SP' or `PC'.
+     The number must be in the range '-8'..'+8' and must not be 0.  The
+     register can be either 'X', 'Y', 'SP' or 'PC'.
 
 "Accumulator Offset"
-     `ACC,REG'
+     'ACC,REG'
 
-     The accumulator register can be either `A', `B' or `D'.  The
-     register can be either `X', `Y', `SP' or `PC'.
+     The accumulator register can be either 'A', 'B' or 'D'.  The
+     register can be either 'X', 'Y', 'SP' or 'PC'.
 
 "Accumulator D offset indexed-indirect"
-     `[D,REG]'
-
-     The register can be either `X', `Y', `SP' or `PC'.
+     '[D,REG]'
 
+     The register can be either 'X', 'Y', 'SP' or 'PC'.
 
    For example:
 
@@ -12899,33 +12627,32 @@ following:
 
      %modifier(symbol)
 
-`%addr'
+'%addr'
      This modifier indicates to the assembler and linker to use the
      16-bit physical address corresponding to the symbol.  This is
-     intended to be used on memory window systems to map a symbol in
-     the memory bank window.  If the symbol is in a memory expansion
-     part, the physical address corresponds to the symbol address
-     within the memory bank window.  If the symbol is not in a memory
-     expansion part, this is the symbol address (using or not using the
-     %addr modifier has no effect in that case).
-
-`%page'
+     intended to be used on memory window systems to map a symbol in the
+     memory bank window.  If the symbol is in a memory expansion part,
+     the physical address corresponds to the symbol address within the
+     memory bank window.  If the symbol is not in a memory expansion
+     part, this is the symbol address (using or not using the %addr
+     modifier has no effect in that case).
+
+'%page'
      This modifier indicates to use the memory page number corresponding
      to the symbol.  If the symbol is in a memory expansion part, its
      page number is computed by the linker as a number used to map the
      page containing the symbol in the memory bank window.  If the
      symbol is not in a memory expansion part, the page number is 0.
 
-`%hi'
+'%hi'
      This modifier indicates to use the 8-bit high part of the physical
      address of the symbol.
 
-`%lo'
+'%lo'
      This modifier indicates to use the 8-bit low part of the physical
      address of the symbol.
 
-
-   For example a 68HC12 call to a function `foo_example' stored in
+   For example a 68HC12 call to a function 'foo_example' stored in
 memory expansion part could be written as follows:
 
      call %addr(foo_example),%page(foo_example)
@@ -12946,35 +12673,34 @@ File: as.info,  Node: M68HC11-Directives,  Next: M68HC11-Float,  Prev: M68HC11-M
 9.24.4 Assembler Directives
 ---------------------------
 
-The 68HC11 and 68HC12 version of `as' have the following specific
+The 68HC11 and 68HC12 version of 'as' have the following specific
 assembler directives:
 
-`.relax'
-     The relax directive is used by the `GNU Compiler' to emit a
+'.relax'
+     The relax directive is used by the 'GNU Compiler' to emit a
      specific relocation to mark a group of instructions for linker
      relaxation.  The sequence of instructions within the group must be
      known to the linker so that relaxation can be performed.
 
-`.mode [mshort|mlong|mshort-double|mlong-double]'
-     This directive specifies the ABI.  It overrides the `-mshort',
-     `-mlong', `-mshort-double' and `-mlong-double' options.
+'.mode [mshort|mlong|mshort-double|mlong-double]'
+     This directive specifies the ABI. It overrides the '-mshort',
+     '-mlong', '-mshort-double' and '-mlong-double' options.
 
-`.far SYMBOL'
-     This directive marks the symbol as a `far' symbol meaning that it
-     uses a `call/rtc' calling convention as opposed to `jsr/rts'.
+'.far SYMBOL'
+     This directive marks the symbol as a 'far' symbol meaning that it
+     uses a 'call/rtc' calling convention as opposed to 'jsr/rts'.
      During a final link, the linker will identify references to the
-     `far' symbol and will verify the proper calling convention.
+     'far' symbol and will verify the proper calling convention.
 
-`.interrupt SYMBOL'
+'.interrupt SYMBOL'
      This directive marks the symbol as an interrupt entry point.  This
      information is then used by the debugger to correctly unwind the
      frame across interrupts.
 
-`.xrefb SYMBOL'
-     This directive is defined for compatibility with the
-     `Specification for Motorola 8 and 16-Bit Assembly Language Input
-     Standard' and is ignored.
-
+'.xrefb SYMBOL'
+     This directive is defined for compatibility with the 'Specification
+     for Motorola 8 and 16-Bit Assembly Language Input Standard' and is
+     ignored.
 
 
 File: as.info,  Node: M68HC11-Float,  Next: M68HC11-opcodes,  Prev: M68HC11-Directives,  Up: M68HC11-Dependent
@@ -12987,15 +12713,15 @@ free to add the code!
 
    The floating point formats generated by directives are these.
 
-`.float'
-     `Single' precision floating point constants.
+'.float'
+     'Single' precision floating point constants.
 
-`.double'
-     `Double' precision floating point constants.
+'.double'
+     'Double' precision floating point constants.
 
-`.extend'
-`.ldouble'
-     `Extended' precision (`long double') floating point constants.
+'.extend'
+'.ldouble'
+     'Extended' precision ('long double') floating point constants.
 
 
 File: as.info,  Node: M68HC11-opcodes,  Prev: M68HC11-Float,  Up: M68HC11-Dependent
@@ -13015,9 +12741,9 @@ File: as.info,  Node: M68HC11-Branch,  Up: M68HC11-opcodes
 
 Certain pseudo opcodes are permitted for branch instructions.  They
 expand to the shortest branch instruction that reach the target.
-Generally these mnemonics are made by prepending `j' to the start of
-Motorola mnemonic. These pseudo opcodes are not affected by the
-`--short-branches' or `--force-long-branches' options.
+Generally these mnemonics are made by prepending 'j' to the start of
+Motorola mnemonic.  These pseudo opcodes are not affected by the
+'--short-branches' or '--force-long-branches' options.
 
    The following table summarizes the pseudo-operations.
 
@@ -13039,30 +12765,29 @@ Motorola mnemonic. These pseudo opcodes are not affected by the
      XX: condition
      NX: negative of condition XX
 
-`jbsr'
-`jbra'
+'jbsr'
+'jbra'
      These are the simplest jump pseudo-operations; they always map to
      one particular machine instruction, depending on the displacement
      to the branch target.
 
-`jbXX'
-     Here, `jbXX' stands for an entire family of pseudo-operations,
+'jbXX'
+     Here, 'jbXX' stands for an entire family of pseudo-operations,
      where XX is a conditional branch or condition-code test.  The full
      list of pseudo-ops in this family is:
            jbcc   jbeq   jbge   jbgt   jbhi   jbvs   jbpl  jblo
            jbcs   jbne   jblt   jble   jbls   jbvc   jbmi
 
      For the cases of non-PC relative displacements and long
-     displacements, `as' issues a longer code fragment in terms of NX,
-     the opposite condition to XX.  For example, for the non-PC
-     relative case:
+     displacements, 'as' issues a longer code fragment in terms of NX,
+     the opposite condition to XX.  For example, for the non-PC relative
+     case:
               jbXX foo
      gives
                bNXs oof
                jmp foo
            oof:
 
-
 
 File: as.info,  Node: Meta-Dependent,  Next: MicroBlaze-Dependent,  Prev: M68HC11-Dependent,  Up: Machine Dependencies
 
@@ -13082,24 +12807,23 @@ File: as.info,  Node: Meta Options,  Next: Meta Syntax,  Up: Meta-Dependent
 
 The Imagination Technologies Meta architecture is implemented in a
 number of versions, with each new version adding new features such as
-instructions and registers. For precise details of what instructions
+instructions and registers.  For precise details of what instructions
 each core supports, please see the chip's technical reference manual.
 
    The following table lists all available Meta options.
 
-`-mcpu=metac11'
+'-mcpu=metac11'
      Generate code for Meta 1.1.
 
-`-mcpu=metac12'
+'-mcpu=metac12'
      Generate code for Meta 1.2.
 
-`-mcpu=metac21'
+'-mcpu=metac21'
      Generate code for Meta 2.1.
 
-`-mfpu=metac21'
+'-mfpu=metac21'
      Allow code to use FPU hardware of Meta 2.1.
 
-
 
 File: as.info,  Node: Meta Syntax,  Prev: Meta Options,  Up: Meta-Dependent
 
@@ -13117,11 +12841,11 @@ File: as.info,  Node: Meta-Chars,  Next: Meta-Regs,  Up: Meta Syntax
 9.25.2.1 Special Characters
 ...........................
 
-`!' is the line comment character.
+'!' is the line comment character.
 
-   You can use `;' instead of a newline to separate statements.
+   You can use ';' instead of a newline to separate statements.
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: Meta-Regs,  Prev: Meta-Chars,  Up: Meta Syntax
@@ -13130,8 +12854,8 @@ File: as.info,  Node: Meta-Regs,  Prev: Meta-Chars,  Up: Meta Syntax
 .......................
 
 Registers can be specified either using their mnemonic names, such as
-`D0Re0', or using the unit plus register number separated by a `.',
-such as `D0.0'.
+'D0Re0', or using the unit plus register number separated by a '.', such
+as 'D0.0'.
 
 
 File: as.info,  Node: MicroBlaze-Dependent,  Next: MIPS-Dependent,  Prev: Meta-Dependent,  Up: Machine Dependencies
@@ -13139,12 +12863,11 @@ File: as.info,  Node: MicroBlaze-Dependent,  Next: MIPS-Dependent,  Prev: Meta-D
 9.26 MicroBlaze Dependent Features
 ==================================
 
-   The Xilinx MicroBlaze processor family includes several variants,
-all using the same core instruction set.  This chapter covers features
-of the GNU assembler that are specific to the MicroBlaze architecture.
-For details about the MicroBlaze instruction set, please see the
-`MicroBlaze Processor Reference Guide (UG081)' available at
-www.xilinx.com.
+The Xilinx MicroBlaze processor family includes several variants, all
+using the same core instruction set.  This chapter covers features of
+the GNU assembler that are specific to the MicroBlaze architecture.  For
+details about the MicroBlaze instruction set, please see the 'MicroBlaze
+Processor Reference Guide (UG081)' available at www.xilinx.com.
 
 * Menu:
 
@@ -13159,47 +12882,47 @@ File: as.info,  Node: MicroBlaze Directives,  Next: MicroBlaze Syntax,  Up: Micr
 
 A number of assembler directives are available for MicroBlaze.
 
-`.data8 EXPRESSION,...'
-     This directive is an alias for `.byte'. Each expression is
+'.data8 EXPRESSION,...'
+     This directive is an alias for '.byte'.  Each expression is
      assembled into an eight-bit value.
 
-`.data16 EXPRESSION,...'
-     This directive is an alias for `.hword'. Each expression is
+'.data16 EXPRESSION,...'
+     This directive is an alias for '.hword'.  Each expression is
      assembled into an 16-bit value.
 
-`.data32 EXPRESSION,...'
-     This directive is an alias for `.word'. Each expression is
+'.data32 EXPRESSION,...'
+     This directive is an alias for '.word'.  Each expression is
      assembled into an 32-bit value.
 
-`.ent NAME[,LABEL]'
-     This directive is an alias for `.func' denoting the start of
+'.ent NAME[,LABEL]'
+     This directive is an alias for '.func' denoting the start of
      function NAME at (optional) LABEL.
 
-`.end NAME[,LABEL]'
-     This directive is an alias for `.endfunc' denoting the end of
+'.end NAME[,LABEL]'
+     This directive is an alias for '.endfunc' denoting the end of
      function NAME.
 
-`.gpword LABEL,...'
-     This directive is an alias for `.rva'.  The resolved address of
+'.gpword LABEL,...'
+     This directive is an alias for '.rva'.  The resolved address of
      LABEL is stored in the data section.
 
-`.weakext LABEL'
+'.weakext LABEL'
      Declare that LABEL is a weak external symbol.
 
-`.rodata'
-     Switch to .rodata section. Equivalent to `.section .rodata'
+'.rodata'
+     Switch to .rodata section.  Equivalent to '.section .rodata'
 
-`.sdata2'
-     Switch to .sdata2 section. Equivalent to `.section .sdata2'
+'.sdata2'
+     Switch to .sdata2 section.  Equivalent to '.section .sdata2'
 
-`.sdata'
-     Switch to .sdata section. Equivalent to `.section .sdata'
+'.sdata'
+     Switch to .sdata section.  Equivalent to '.section .sdata'
 
-`.bss'
-     Switch to .bss section. Equivalent to `.section .bss'
+'.bss'
+     Switch to .bss section.  Equivalent to '.section .bss'
 
-`.sbss'
-     Switch to .sbss section. Equivalent to `.section .sbss'
+'.sbss'
+     Switch to .sbss section.  Equivalent to '.section .sbss'
 
 
 File: as.info,  Node: MicroBlaze Syntax,  Prev: MicroBlaze Directives,  Up: MicroBlaze-Dependent
@@ -13217,15 +12940,15 @@ File: as.info,  Node: MicroBlaze-Chars,  Up: MicroBlaze Syntax
 9.26.2.1 Special Characters
 ...........................
 
-The presence of a `#' on a line indicates the start of a comment that
+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
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can also be a logical
 line number directive (*note Comments::) or a preprocessor control
 command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -13234,224 +12957,242 @@ File: as.info,  Node: MIPS-Dependent,  Next: MMIX-Dependent,  Prev: MicroBlaze-D
 9.27 MIPS Dependent Features
 ============================
 
-   GNU `as' for MIPS architectures supports several different MIPS
+GNU 'as' for MIPS architectures supports several different MIPS
 processors, and MIPS ISA levels I through V, MIPS32, and MIPS64.  For
-information about the MIPS instruction set, see `MIPS RISC
+information about the MIPS instruction set, see 'MIPS RISC
 Architecture', by Kane and Heindrich (Prentice-Hall).  For an overview
 of MIPS assembly conventions, see "Appendix D: Assembly Language
 Programming" in the same work.
 
 * Menu:
 
-* MIPS Opts::   	Assembler options
-* MIPS Object:: 	ECOFF object code
-* MIPS Stabs::  	Directives for debugging information
+* MIPS Options::   	Assembler options
+* MIPS Macros:: 	High-level assembly macros
+* MIPS Symbol Sizes::	Directives to override the size of symbols
+* MIPS Small Data:: 	Controlling the use of small data accesses
 * MIPS ISA::    	Directives to override the ISA level
-* MIPS symbol sizes::   Directives to override the size of symbols
+* MIPS assembly options:: Directives to control code generation
 * MIPS autoextend::	Directives for extending MIPS 16 bit instructions
 * MIPS insn::		Directive to mark data as an instruction
-* MIPS option stack::	Directives to save and restore options
-* MIPS ASE instruction generation overrides:: Directives to control
+* MIPS NaN Encodings::	Directives to record which NaN encoding is being used
+* MIPS Option Stack::	Directives to save and restore options
+* MIPS ASE Instruction Generation Overrides:: Directives to control
   			generation of MIPS ASE instructions
-* MIPS floating-point:: Directives to override floating-point options
+* MIPS Floating-Point:: Directives to override floating-point options
 * MIPS Syntax::         MIPS specific syntactical considerations
 
 
-File: as.info,  Node: MIPS Opts,  Next: MIPS Object,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Options,  Next: MIPS Macros,  Up: MIPS-Dependent
 
 9.27.1 Assembler options
 ------------------------
 
-The MIPS configurations of GNU `as' support these special options:
+The MIPS configurations of GNU 'as' support these special options:
 
-`-G NUM'
-     This option sets the largest size of an object that can be
-     referenced implicitly with the `gp' register.  It is only accepted
-     for targets that use ECOFF format.  The default value is 8.
+'-G NUM'
+     Set the "small data" limit to N bytes.  The default limit is 8
+     bytes.  *Note Controlling the use of small data accesses: MIPS
+     Small Data.
 
-`-EB'
-`-EL'
-     Any MIPS configuration of `as' can select big-endian or
+'-EB'
+'-EL'
+     Any MIPS configuration of 'as' can select big-endian or
      little-endian output at run time (unlike the other GNU development
-     tools, which must be configured for one or the other).  Use `-EB'
-     to select big-endian output, and `-EL' for little-endian.
+     tools, which must be configured for one or the other).  Use '-EB'
+     to select big-endian output, and '-EL' for little-endian.
 
-`-KPIC'
-     Generate SVR4-style PIC.  This option tells the assembler to
-     generate SVR4-style position-independent macro expansions.  It
-     also tells the assembler to mark the output file as PIC.
+'-KPIC'
+     Generate SVR4-style PIC. This option tells the assembler to
+     generate SVR4-style position-independent macro expansions.  It also
+     tells the assembler to mark the output file as PIC.
 
-`-mvxworks-pic'
-     Generate VxWorks PIC.  This option tells the assembler to generate
+'-mvxworks-pic'
+     Generate VxWorks PIC. This option tells the assembler to generate
      VxWorks-style position-independent macro expansions.
 
-`-mips1'
-`-mips2'
-`-mips3'
-`-mips4'
-`-mips5'
-`-mips32'
-`-mips32r2'
-`-mips64'
-`-mips64r2'
+'-mips1'
+'-mips2'
+'-mips3'
+'-mips4'
+'-mips5'
+'-mips32'
+'-mips32r2'
+'-mips64'
+'-mips64r2'
      Generate code for a particular MIPS Instruction Set Architecture
-     level.  `-mips1' corresponds to the R2000 and R3000 processors,
-     `-mips2' to the R6000 processor, `-mips3' to the R4000 processor,
-     and `-mips4' to the R8000 and R10000 processors.  `-mips5',
-     `-mips32', `-mips32r2', `-mips64', and `-mips64r2' correspond to
-     generic MIPS V, MIPS32, MIPS32 RELEASE 2, MIPS64, and MIPS64
-     RELEASE 2 ISA processors, respectively.  You can also switch
+     level.  '-mips1' corresponds to the R2000 and R3000 processors,
+     '-mips2' to the R6000 processor, '-mips3' to the R4000 processor,
+     and '-mips4' to the R8000 and R10000 processors.  '-mips5',
+     '-mips32', '-mips32r2', '-mips64', and '-mips64r2' correspond to
+     generic MIPS V, MIPS32, MIPS32 Release 2, MIPS64, and MIPS64
+     Release 2 ISA processors, respectively.  You can also switch
      instruction sets during the assembly; see *note Directives to
      override the ISA level: MIPS ISA.
 
-`-mgp32'
-`-mfp32'
+'-mgp32'
+'-mfp32'
      Some macros have different expansions for 32-bit and 64-bit
      registers.  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
+     treated as 32 bits wide at all times.  '-mgp32' controls the size
+     of general-purpose registers and '-mfp32' controls the size of
      floating-point registers.
 
-     The `.set gp=32' and `.set fp=32' directives allow the size of
-     registers to be changed for parts of an object. The default value
-     is restored by `.set gp=default' and `.set fp=default'.
+     The '.set gp=32' and '.set fp=32' directives allow the size of
+     registers to be changed for parts of an object.  The default value
+     is restored by '.set gp=default' and '.set fp=default'.
 
      On some MIPS variants there is a 32-bit mode flag; when this flag
      is set, 64-bit instructions generate a trap.  Also, some 32-bit
      OSes only save the 32-bit registers on a context switch, so it is
      essential never to use the 64-bit registers.
 
-`-mgp64'
-`-mfp64'
+'-mgp64'
+'-mfp64'
      Assume that 64-bit registers are available.  This is provided in
-     the interests of symmetry with `-mgp32' and `-mfp32'.
+     the interests of symmetry with '-mgp32' and '-mfp32'.
 
-     The `.set gp=64' and `.set fp=64' directives allow the size of
-     registers to be changed for parts of an object. The default value
-     is restored by `.set gp=default' and `.set fp=default'.
+     The '.set gp=64' and '.set fp=64' directives allow the size of
+     registers to be changed for parts of an object.  The default value
+     is restored by '.set gp=default' and '.set fp=default'.
 
-`-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 extensions to the MIPS32 instruction set,
      which provides a number of new instructions which target smartcard
      and cryptographic applications.  This is equivalent to putting
-     `.set smartmips' at the start of the assembly file.
-     `-mno-smartmips' turns off this option.
+     '.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.
+     Release 2 instructions.  '-mno-dspr2' 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.
 
-`-mfix7000'
-`-mno-fix7000'
+'-mvirt'
+'-mno-virt'
+     Generate code for the Virtualization Application Specific
+     Extension.  This tells the assembler to accept Virtualization
+     instructions.  '-mno-virt' turns off this option.
+
+'-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 to be used.
+
+'-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-loongson2f-jump'
-`-mno-fix-loongson2f-jump'
-     Eliminate instruction fetch from outside 256M region to work
-     around the Loongson2F `jump' instructions.  Without it, under
-     extreme cases, the kernel may crash.  The issue has been solved in
-     latest processor batches, but this fix has no side effect to them.
-
-`-mfix-loongson2f-nop'
-`-mno-fix-loongson2f-nop'
-     Replace nops by `or at,at,zero' to work around the Loongson2F
-     `nop' errata.  Without it, under extreme cases, cpu might
-     deadlock.  The issue has been solved in latest loongson2f batches,
-     but this fix has no side effect to them.
-
-`-mfix-vr4120'
-`-mno-fix-vr4120'
+'-mfix-loongson2f-jump'
+'-mno-fix-loongson2f-jump'
+     Eliminate instruction fetch from outside 256M region to work around
+     the Loongson2F 'jump' instructions.  Without it, under extreme
+     cases, the kernel may crash.  The issue has been solved in latest
+     processor batches, but this fix has no side effect to them.
+
+'-mfix-loongson2f-nop'
+'-mno-fix-loongson2f-nop'
+     Replace nops by 'or at,at,zero' to work around the Loongson2F 'nop'
+     errata.  Without it, under extreme cases, the CPU might deadlock.
+     The issue has been solved in later Loongson2F batches, but this fix
+     has no side effect to them.
+
+'-mfix-vr4120'
+'-mno-fix-vr4120'
      Insert nops to work around certain VR4120 errata.  This option is
      intended to be used on GCC-generated code: it is not designed to
      catch all problems in hand-written assembler code.
 
-`-mfix-vr4130'
-`-mno-fix-vr4130'
-     Insert nops to work around the VR4130 `mflo'/`mfhi' errata.
+'-mfix-vr4130'
+'-mno-fix-vr4130'
+     Insert nops to work around the VR4130 'mflo'/'mfhi' errata.
 
-`-mfix-24k'
-`-mno-fix-24k'
-     Insert nops to work around the 24K `eret'/`deret' errata.
+'-mfix-24k'
+'-mno-fix-24k'
+     Insert nops to work around the 24K 'eret'/'deret' errata.
 
-`-mfix-cn63xxp1'
-`-mno-fix-cn63xxp1'
-     Replace `pref' hints 0 - 4 and 6 - 24 with hint 28 to work around
+'-mfix-cn63xxp1'
+'-mno-fix-cn63xxp1'
+     Replace 'pref' hints 0 - 4 and 6 - 24 with hint 28 to work around
      certain CN63XXP1 errata.
 
-`-m4010'
-`-no-m4010'
+'-m4010'
+'-no-m4010'
      Generate code for the LSI R4010 chip.  This tells the assembler to
-     accept the R4010 specific instructions (`addciu', `ffc', etc.),
-     and to not schedule `nop' instructions around accesses to the `HI'
-     and `LO' registers.  `-no-m4010' turns off this option.
-
-`-m4650'
-`-no-m4650'
-     Generate code for the MIPS R4650 chip.  This tells the assembler
-     to accept the `mad' and `madu' instruction, and to not schedule
-     `nop' instructions around accesses to the `HI' and `LO' registers.
-     `-no-m4650' turns off this option.
-
-`-m3900'
-`-no-m3900'
-`-m4100'
-`-no-m4100'
-     For each option `-mNNNN', generate code for the MIPS RNNNN chip.
+     accept the R4010-specific instructions ('addciu', 'ffc', etc.), and
+     to not schedule 'nop' instructions around accesses to the 'HI' and
+     'LO' registers.  '-no-m4010' turns off this option.
+
+'-m4650'
+'-no-m4650'
+     Generate code for the MIPS R4650 chip.  This tells the assembler to
+     accept the 'mad' and 'madu' instruction, and to not schedule 'nop'
+     instructions around accesses to the 'HI' and 'LO' registers.
+     '-no-m4650' turns off this option.
+
+'-m3900'
+'-no-m3900'
+'-m4100'
+'-no-m4100'
+     For each option '-mNNNN', generate code for the MIPS RNNNN chip.
      This tells the assembler to accept instructions specific to that
      chip, and to schedule for that chip's hazards.
 
-`-march=CPU'
-     Generate code for a particular MIPS cpu.  It is exactly equivalent
-     to `-mCPU', except that there are more value of CPU understood.
+'-march=CPU'
+     Generate code for a particular MIPS CPU. It is exactly equivalent
+     to '-mCPU', except that there are more value of CPU understood.
      Valid CPU value are:
 
           2000, 3000, 3900, 4000, 4010, 4100, 4111, vr4120, vr4130,
@@ -13465,142 +13206,183 @@ The MIPS configurations of GNU `as' support these special options:
           5kf, 20kc, 25kf, sb1, sb1a, loongson2e, loongson2f,
           loongson3a, octeon, octeon+, octeon2, xlr, xlp
 
-     For compatibility reasons, `Nx' and `Bfx' are accepted as synonyms
-     for `Nf1_1'.  These values are deprecated.
+     For compatibility reasons, 'Nx' and 'Bfx' are accepted as synonyms
+     for 'Nf1_1'.  These values are deprecated.
 
-`-mtune=CPU'
-     Schedule and tune for a particular MIPS cpu.  Valid CPU values are
-     identical to `-march=CPU'.
+'-mtune=CPU'
+     Schedule and tune for a particular MIPS CPU. Valid CPU values are
+     identical to '-march=CPU'.
 
-`-mabi=ABI'
+'-mabi=ABI'
      Record which ABI the source code uses.  The recognized arguments
-     are: `32', `n32', `o64', `64' and `eabi'.
+     are: '32', 'n32', 'o64', '64' and 'eabi'.
 
-`-msym32'
-`-mno-sym32'
-     Equivalent to adding `.set sym32' or `.set nosym32' to the
-     beginning of the assembler input.  *Note MIPS symbol sizes::.
+'-msym32'
+'-mno-sym32'
+     Equivalent to adding '.set sym32' or '.set nosym32' to the
+     beginning of the assembler input.  *Note MIPS Symbol Sizes::.
 
-`-nocpp'
+'-nocpp'
      This option is ignored.  It is accepted for command-line
      compatibility with other assemblers, which use it to turn off C
-     style preprocessing.  With GNU `as', there is no need for
-     `-nocpp', because the GNU assembler itself never runs the C
-     preprocessor.
+     style preprocessing.  With GNU 'as', there is no need for '-nocpp',
+     because the GNU assembler itself never runs the C preprocessor.
 
-`-msoft-float'
-`-mhard-float'
+'-msoft-float'
+'-mhard-float'
      Disable or enable floating-point instructions.  Note that by
      default floating-point instructions are always allowed even with
      CPU targets that don't have support for these instructions.
 
-`-msingle-float'
-`-mdouble-float'
+'-msingle-float'
+'-mdouble-float'
      Disable or enable double-precision floating-point operations.  Note
      that by default double-precision floating-point operations are
      always allowed even with CPU targets that don't have support for
      these operations.
 
-`--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.  This feature is useful if the
-     processor support the FR bit in its status  register, and this bit
+     processor support the FR bit in its status register, and this bit
      is known (by the programmer) to be set.  This bit prevents the
      aliasing of the double width register by the single width
      registers.
 
-     By default `--construct-floats' is selected, allowing construction
+     By default '--construct-floats' is selected, allowing construction
      of these floating point constants.
 
-`--trap'
-`--no-break'
-     `as' automatically macro expands certain division and
+'--relax-branch'
+'--no-relax-branch'
+     The '--relax-branch' option enables the relaxation of out-of-range
+     branches.  Any branches whose target cannot be reached directly are
+     converted to a small instruction sequence including an
+     inverse-condition branch to the physically next instruction, and a
+     jump to the original target is inserted between the two
+     instructions.  In PIC code the jump will involve further
+     instructions for address calculation.
+
+     The 'BC1ANY2F', 'BC1ANY2T', 'BC1ANY4F', 'BC1ANY4T', 'BPOSGE32' and
+     'BPOSGE64' instructions are excluded from relaxation, because they
+     have no complementing counterparts.  They could be relaxed with the
+     use of a longer sequence involving another branch, however this has
+     not been implemented and if their target turns out of reach, they
+     produce an error even if branch relaxation is enabled.
+
+     Also no MIPS16 branches are ever relaxed.
+
+     By default '--no-relax-branch' is selected, causing any
+     out-of-range branches to produce an error.
+
+'-mnan=ENCODING'
+     This option indicates whether the source code uses the IEEE 2008
+     NaN encoding ('-mnan=2008') or the original MIPS encoding
+     ('-mnan=legacy').  It is equivalent to adding a '.nan' directive to
+     the beginning of the source file.  *Note MIPS NaN Encodings::.
+
+     '-mnan=legacy' is the default if no '-mnan' option or '.nan'
+     directive is used.
+
+'--trap'
+'--no-break'
+     'as' automatically macro expands certain division and
      multiplication instructions to check for overflow and division by
-     zero.  This option causes `as' to generate code to take a trap
+     zero.  This option causes 'as' to generate code to take a trap
      exception rather than a break exception when an error is detected.
      The trap instructions are only supported at Instruction Set
      Architecture level 2 and higher.
 
-`--break'
-`--no-trap'
+'--break'
+'--no-trap'
      Generate code to take a break exception rather than a trap
      exception when an error is detected.  This is the default.
 
-`-mpdr'
-`-mno-pdr'
-     Control generation of `.pdr' sections.  Off by default on IRIX, on
+'-mpdr'
+'-mno-pdr'
+     Control generation of '.pdr' sections.  Off by default on IRIX, on
      elsewhere.
 
-`-mshared'
-`-mno-shared'
+'-mshared'
+'-mno-shared'
      When generating code using the Unix calling conventions (selected
-     by `-KPIC' or `-mcall_shared'), gas will normally generate code
-     which can go into a shared library.  The `-mno-shared' option
-     tells gas to generate code which uses the calling convention, but
-     can not go into a shared library.  The resulting code is slightly
-     more efficient.  This option only affects the handling of the
-     `.cpload' and `.cpsetup' pseudo-ops.
+     by '-KPIC' or '-mcall_shared'), gas will normally generate code
+     which can go into a shared library.  The '-mno-shared' option tells
+     gas to generate code which uses the calling convention, but can not
+     go into a shared library.  The resulting code is slightly more
+     efficient.  This option only affects the handling of the '.cpload'
+     and '.cpsetup' pseudo-ops.
 
 
-File: as.info,  Node: MIPS Object,  Next: MIPS Stabs,  Prev: MIPS Opts,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Macros,  Next: MIPS Symbol Sizes,  Prev: MIPS Options,  Up: MIPS-Dependent
 
-9.27.2 MIPS ECOFF object code
------------------------------
+9.27.2 High-level assembly macros
+---------------------------------
 
-Assembling for a MIPS ECOFF target supports some additional sections
-besides the usual `.text', `.data' and `.bss'.  The additional sections
-are `.rdata', used for read-only data, `.sdata', used for small data,
-and `.sbss', used for small common objects.
-
-   When assembling for ECOFF, the assembler uses the `$gp' (`$28')
-register to form the address of a "small object".  Any object in the
-`.sdata' or `.sbss' sections is considered "small" in this sense.  For
-external objects, or for objects in the `.bss' section, you can use the
-`gcc' `-G' option to control the size of objects addressed via `$gp';
-the default value is 8, meaning that a reference to any object eight
-bytes or smaller uses `$gp'.  Passing `-G 0' to `as' prevents it from
-using the `$gp' register on the basis of object size (but the assembler
-uses `$gp' for objects in `.sdata' or `sbss' in any case).  The size of
-an object in the `.bss' section is set by the `.comm' or `.lcomm'
-directive that defines it.  The size of an external object may be set
-with the `.extern' directive.  For example, `.extern sym,4' declares
-that the object at `sym' is 4 bytes in length, whie leaving `sym'
-otherwise undefined.
-
-   Using small ECOFF objects requires linker support, and assumes that
-the `$gp' register is correctly initialized (normally done
-automatically by the startup code).  MIPS ECOFF assembly code must not
-modify the `$gp' register.
-
-
-File: as.info,  Node: MIPS Stabs,  Next: MIPS ISA,  Prev: MIPS Object,  Up: MIPS-Dependent
-
-9.27.3 Directives for debugging information
--------------------------------------------
+MIPS assemblers have traditionally provided a wider range of
+instructions than the MIPS architecture itself.  These extra
+instructions are usually referred to as "macro" instructions (1).
+
+   Some MIPS macro instructions extend an underlying architectural
+instruction while others are entirely new.  An example of the former
+type is 'and', which allows the third operand to be either a register or
+an arbitrary immediate value.  Examples of the latter type include
+'bgt', which branches to the third operand when the first operand is
+greater than the second operand, and 'ulh', which implements an
+unaligned 2-byte load.
+
+   One of the most common extensions provided by macros is to expand
+memory offsets to the full address range (32 or 64 bits) and to allow
+symbolic offsets such as 'my_data + 4' to be used in place of integer
+constants.  For example, the architectural instruction 'lbu' allows only
+a signed 16-bit offset, whereas the macro 'lbu' allows code such as 'lbu
+$4,array+32769($5)'.  The implementation of these symbolic offsets
+depends on several factors, such as whether the assembler is generating
+SVR4-style PIC (selected by '-KPIC', *note Assembler options: MIPS
+Options.), the size of symbols (*note Directives to override the size of
+symbols: MIPS Symbol Sizes.), and the small data limit (*note
+Controlling the use of small data accesses: MIPS Small Data.).
+
+   Sometimes it is undesirable to have one assembly instruction expand
+to several machine instructions.  The directive '.set nomacro' tells the
+assembler to warn when this happens.  '.set macro' restores the default
+behavior.
+
+   Some macro instructions need a temporary register to store
+intermediate results.  This register is usually '$1', also known as
+'$at', but it can be changed to any core register REG using '.set
+at=REG'.  Note that '$at' always refers to '$1' regardless of which
+register is being used as the temporary register.
+
+   Implicit uses of the temporary register in macros could interfere
+with explicit uses in the assembly code.  The assembler therefore warns
+whenever it sees an explicit use of the temporary register.  The
+directive '.set noat' silences this warning while '.set at' restores the
+default behavior.  It is safe to use '.set noat' while '.set nomacro' is
+in effect since single-instruction macros never need a temporary
+register.
+
+   Note that while the GNU assembler provides these macros for
+compatibility, it does not make any attempt to optimize them with the
+surrounding code.
+
+   ---------- Footnotes ----------
 
-MIPS ECOFF `as' supports several directives used for generating
-debugging information which are not support by traditional MIPS
-assemblers.  These are `.def', `.endef', `.dim', `.file', `.scl',
-`.size', `.tag', `.type', `.val', `.stabd', `.stabn', and `.stabs'.
-The debugging information generated by the three `.stab' directives can
-only be read by GDB, not by traditional MIPS debuggers (this
-enhancement is required to fully support C++ debugging).  These
-directives are primarily used by compilers, not assembly language
-programmers!
+   (1) The term "macro" is somewhat overloaded here, since these macros
+have no relation to those defined by '.macro', *note '.macro': Macro.
 
 
-File: as.info,  Node: MIPS symbol sizes,  Next: MIPS autoextend,  Prev: MIPS ISA,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Symbol Sizes,  Next: MIPS Small Data,  Prev: MIPS Macros,  Up: MIPS-Dependent
 
-9.27.4 Directives to override the size of symbols
+9.27.3 Directives to override the size of symbols
 -------------------------------------------------
 
 The n64 ABI allows symbols to have any 64-bit value.  Although this
 provides a great deal of flexibility, it means that some macros have
-much longer expansions than their 32-bit counterparts.  For example,
-the non-PIC expansion of `dla $4,sym' is usually:
+much longer expansions than their 32-bit counterparts.  For example, the
+non-PIC expansion of 'dla $4,sym' is usually:
 
      lui     $4,%highest(sym)
      lui     $1,%hi(sym)
@@ -13618,8 +13400,8 @@ the non-PIC expansion of `dla $4,sym' is usually:
 constants are known to have 32-bit values, and in such cases, it's
 preferable to use the 32-bit expansion instead of the 64-bit expansion.
 
-   You can use the `.set sym32' directive to tell the assembler that,
-from this point on, all expressions of the form `SYMBOL' or `SYMBOL +
+   You can use the '.set sym32' directive to tell the assembler that,
+from this point on, all expressions of the form 'SYMBOL' or 'SYMBOL +
 OFFSET' have 32-bit values.  For example:
 
      .set sym32
@@ -13627,91 +13409,153 @@ OFFSET' have 32-bit values.  For example:
      lw      $4,sym+16
      sw      $4,sym+0x8000($4)
 
-   will cause the assembler to treat `sym', `sym+16' and `sym+0x8000'
-as 32-bit values.  The handling of non-symbolic addresses is not
-affected.
+   will cause the assembler to treat 'sym', 'sym+16' and 'sym+0x8000' as
+32-bit values.  The handling of non-symbolic addresses is not affected.
 
-   The directive `.set nosym32' ends a `.set sym32' block and reverts
-to the normal behavior.  It is also possible to change the symbol size
-using the command-line options `-msym32' and `-mno-sym32'.
+   The directive '.set nosym32' ends a '.set sym32' block and reverts to
+the normal behavior.  It is also possible to change the symbol size
+using the command-line options '-msym32' and '-mno-sym32'.
 
    These options and directives are always accepted, but at present,
 they have no effect for anything other than n64.
 
 
-File: as.info,  Node: MIPS ISA,  Next: MIPS symbol sizes,  Prev: MIPS Stabs,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Small Data,  Next: MIPS ISA,  Prev: MIPS Symbol Sizes,  Up: MIPS-Dependent
+
+9.27.4 Controlling the use of small data accesses
+-------------------------------------------------
+
+It often takes several instructions to load the address of a symbol.
+For example, when 'addr' is a 32-bit symbol, the non-PIC expansion of
+'dla $4,addr' is usually:
+
+     lui     $4,%hi(addr)
+     daddiu  $4,$4,%lo(addr)
+
+   The sequence is much longer when 'addr' is a 64-bit symbol.  *Note
+Directives to override the size of symbols: MIPS Symbol Sizes.
+
+   In order to cut down on this overhead, most embedded MIPS systems set
+aside a 64-kilobyte "small data" area and guarantee that all data of
+size N and smaller will be placed in that area.  The limit N is passed
+to both the assembler and the linker using the command-line option '-G
+N', *note Assembler options: MIPS Options.  Note that the same value of
+N must be used when linking and when assembling all input files to the
+link; any inconsistency could cause a relocation overflow error.
+
+   The size of an object in the '.bss' section is set by the '.comm' or
+'.lcomm' directive that defines it.  The size of an external object may
+be set with the '.extern' directive.  For example, '.extern sym,4'
+declares that the object at 'sym' is 4 bytes in length, while leaving
+'sym' otherwise undefined.
+
+   When no '-G' option is given, the default limit is 8 bytes.  The
+option '-G 0' prevents any data from being automatically classified as
+small.
+
+   It is also possible to mark specific objects as small by putting them
+in the special sections '.sdata' and '.sbss', which are "small"
+counterparts of '.data' and '.bss' respectively.  The toolchain will
+treat such data as small regardless of the '-G' setting.
+
+   On startup, systems that support a small data area are expected to
+initialize register '$28', also known as '$gp', in such a way that small
+data can be accessed using a 16-bit offset from that register.  For
+example, when 'addr' is small data, the 'dla $4,addr' instruction above
+is equivalent to:
+
+     daddiu  $4,$28,%gp_rel(addr)
+
+   Small data is not supported for SVR4-style PIC.
+
+
+File: as.info,  Node: MIPS ISA,  Next: MIPS assembly options,  Prev: MIPS Small Data,  Up: MIPS-Dependent
 
 9.27.5 Directives to override the ISA level
 -------------------------------------------
 
-GNU `as' supports an additional directive to change the MIPS
-Instruction Set Architecture level on the fly: `.set mipsN'.  N should
-be a number from 0 to 5, or 32, 32r2, 64 or 64r2.  The values other
-than 0 make the assembler accept instructions for the corresponding ISA
-level, from that point on in the assembly.  `.set mipsN' affects not
-only which instructions are permitted, but also how certain macros are
-expanded.  `.set mips0' restores the ISA level to its original level:
-either the level you selected with command line options, or the default
-for your configuration.  You can use this feature to permit specific
-MIPS3 instructions while assembling in 32 bit mode.  Use this directive
-with care!
-
-   The `.set arch=CPU' directive provides even finer control.  It
+GNU 'as' supports an additional directive to change the MIPS Instruction
+Set Architecture level on the fly: '.set mipsN'.  N should be a number
+from 0 to 5, or 32, 32r2, 64 or 64r2.  The values other than 0 make the
+assembler accept instructions for the corresponding ISA level, from that
+point on in the assembly.  '.set mipsN' affects not only which
+instructions are permitted, but also how certain macros are expanded.
+'.set mips0' restores the ISA level to its original level: either the
+level you selected with command line options, or the default for your
+configuration.  You can use this feature to permit specific MIPS III
+instructions while assembling in 32 bit mode.  Use this directive with
+care!
+
+   The '.set arch=CPU' directive provides even finer control.  It
 changes the effective CPU target and allows the assembler to use
-instructions specific to a particular CPU.  All CPUs supported by the
-`-march' command line option are also selectable by this directive.
-The original value is restored by `.set arch=default'.
+instructions specific to a particular CPU. All CPUs supported by the
+'-march' command line option are also selectable by this directive.  The
+original value is restored by '.set arch=default'.
 
-   The directive `.set mips16' puts the assembler into MIPS 16 mode, in
+   The directive '.set mips16' puts the assembler into MIPS 16 mode, in
 which it will assemble instructions for the MIPS 16 processor.  Use
-`.set nomips16' to return to normal 32 bit mode.
+'.set nomips16' to return to normal 32 bit mode.
 
    Traditional MIPS assemblers do not support this directive.
 
-   The directive `.set micromips' puts the assembler into microMIPS
+   The directive '.set micromips' puts the assembler into microMIPS
 mode, in which it will assemble instructions for the microMIPS
-processor.  Use `.set nomicromips' to return to normal 32 bit mode.
+processor.  Use '.set nomicromips' to return to normal 32 bit mode.
 
    Traditional MIPS assemblers do not support this directive.
 
 
-File: as.info,  Node: MIPS autoextend,  Next: MIPS insn,  Prev: MIPS symbol sizes,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS assembly options,  Next: MIPS autoextend,  Prev: MIPS ISA,  Up: MIPS-Dependent
+
+9.27.6 Directives to control code generation
+--------------------------------------------
+
+The directive '.set insn32' makes the assembler only use 32-bit
+instruction encodings when generating code for the microMIPS processor.
+This directive inhibits the use of any 16-bit instructions from that
+point on in the assembly.  The '.set noinsn32' directive allows 16-bit
+instructions to be accepted.
 
-9.27.6 Directives for extending MIPS 16 bit instructions
+   Traditional MIPS assemblers do not support this directive.
+
+
+File: as.info,  Node: MIPS autoextend,  Next: MIPS insn,  Prev: MIPS assembly options,  Up: MIPS-Dependent
+
+9.27.7 Directives for extending MIPS 16 bit instructions
 --------------------------------------------------------
 
 By default, MIPS 16 instructions are automatically extended to 32 bits
-when necessary.  The directive `.set noautoextend' will turn this off.
-When `.set noautoextend' is in effect, any 32 bit instruction must be
-explicitly extended with the `.e' modifier (e.g., `li.e $4,1000').  The
-directive `.set autoextend' may be used to once again automatically
+when necessary.  The directive '.set noautoextend' will turn this off.
+When '.set noautoextend' is in effect, any 32 bit instruction must be
+explicitly extended with the '.e' modifier (e.g., 'li.e $4,1000').  The
+directive '.set autoextend' may be used to once again automatically
 extend instructions when necessary.
 
    This directive is only meaningful when in MIPS 16 mode.  Traditional
 MIPS assemblers do not support this directive.
 
 
-File: as.info,  Node: MIPS insn,  Next: MIPS option stack,  Prev: MIPS autoextend,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS insn,  Next: MIPS NaN Encodings,  Prev: MIPS autoextend,  Up: MIPS-Dependent
 
-9.27.7 Directive to mark data as an instruction
+9.27.8 Directive to mark data as an instruction
 -----------------------------------------------
 
-The `.insn' directive tells `as' that the following data is actually
+The '.insn' directive tells 'as' that the following data is actually
 instructions.  This makes a difference in MIPS 16 and microMIPS modes:
-when loading the address of a label which precedes instructions, `as'
-automatically adds 1 to the value, so that jumping to the loaded
-address will do the right thing.
+when loading the address of a label which precedes instructions, 'as'
+automatically adds 1 to the value, so that jumping to the loaded address
+will do the right thing.
 
-   The `.global' and `.globl' directives supported by `as' will by
+   The '.global' and '.globl' directives supported by 'as' will by
 default mark the symbol as pointing to a region of data not code.  This
 means that, for example, any instructions following such a symbol will
-not be disassembled by `objdump' as it will regard them as data.  To
+not be disassembled by 'objdump' as it will regard them as data.  To
 change this behaviour an optional section name can be placed after the
-symbol name in the `.global' directive.  If this section exists and is
+symbol name in the '.global' directive.  If this section exists and is
 known to be a code section, then the symbol will be marked as poiting at
 code not data.  Ie the syntax for the directive is:
 
-   `.global SYMBOL[ SECTION][, SYMBOL[ SECTION]] ...',
+   '.global SYMBOL[ SECTION][, SYMBOL[ SECTION]] ...',
 
    Here is a short example:
 
@@ -13724,15 +13568,56 @@ code not data.  Ie the syntax for the directive is:
              .word 0x1
 
 
-File: as.info,  Node: MIPS option stack,  Next: MIPS ASE instruction generation overrides,  Prev: MIPS insn,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS NaN Encodings,  Next: MIPS Option Stack,  Prev: MIPS insn,  Up: MIPS-Dependent
+
+9.27.9 Directives to record which NaN encoding is being used
+------------------------------------------------------------
+
+The IEEE 754 floating-point standard defines two types of not-a-number
+(NaN) data: "signalling" NaNs and "quiet" NaNs.  The original version of
+the standard did not specify how these two types should be
+distinguished.  Most implementations followed the i387 model, in which
+the first bit of the significand is set for quiet NaNs and clear for
+signalling NaNs.  However, the original MIPS implementation assigned the
+opposite meaning to the bit, so that it was set for signalling NaNs and
+clear for quiet NaNs.
+
+   The 2008 revision of the standard formally suggested the i387 choice
+and as from Sep 2012 the current release of the MIPS architecture
+therefore optionally supports that form.  Code that uses one NaN
+encoding would usually be incompatible with code that uses the other NaN
+encoding, so MIPS ELF objects have a flag ('EF_MIPS_NAN2008') to record
+which encoding is being used.
+
+   Assembly files can use the '.nan' directive to select between the two
+encodings.  '.nan 2008' says that the assembly file uses the IEEE
+754-2008 encoding while '.nan legacy' says that the file uses the
+original MIPS encoding.  If several '.nan' directives are given, the
+final setting is the one that is used.
+
+   The command-line options '-mnan=legacy' and '-mnan=2008' can be used
+instead of '.nan legacy' and '.nan 2008' respectively.  However, any
+'.nan' directive overrides the command-line setting.
+
+   '.nan legacy' is the default if no '.nan' directive or '-mnan' option
+is given.
+
+   Note that GNU 'as' does not produce NaNs itself and therefore these
+directives do not affect code generation.  They simply control the
+setting of the 'EF_MIPS_NAN2008' flag.
+
+   Traditional MIPS assemblers do not support these directives.
+
+
+File: as.info,  Node: MIPS Option Stack,  Next: MIPS ASE Instruction Generation Overrides,  Prev: MIPS NaN Encodings,  Up: MIPS-Dependent
 
-9.27.8 Directives to save and restore options
----------------------------------------------
+9.27.10 Directives to save and restore options
+----------------------------------------------
 
-The directives `.set push' and `.set pop' may be used to save and
-restore the current settings for all the options which are controlled
-by `.set'.  The `.set push' directive saves the current settings on a
-stack.  The `.set pop' directive pops the stack and restores the
+The directives '.set push' and '.set pop' may be used to save and
+restore the current settings for all the options which are controlled by
+'.set'.  The '.set push' directive saves the current settings on a
+stack.  The '.set pop' directive pops the stack and restores the
 settings.
 
    These directives can be useful inside an macro which must change an
@@ -13742,73 +13627,77 @@ to change the state of the code which invoked the macro.
    Traditional MIPS assemblers do not support these directives.
 
 
-File: as.info,  Node: MIPS ASE instruction generation overrides,  Next: MIPS floating-point,  Prev: MIPS option stack,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS ASE Instruction Generation Overrides,  Next: MIPS Floating-Point,  Prev: MIPS Option Stack,  Up: MIPS-Dependent
 
-9.27.9 Directives to control generation of MIPS ASE instructions
-----------------------------------------------------------------
+9.27.11 Directives to control generation of MIPS ASE instructions
+-----------------------------------------------------------------
 
-The directive `.set mips3d' makes the assembler accept instructions
-from the MIPS-3D Application Specific Extension from that point on in
-the assembly.  The `.set nomips3d' directive prevents MIPS-3D
-instructions from being accepted.
+The directive '.set mips3d' makes the assembler accept instructions from
+the MIPS-3D Application Specific Extension from that point on in the
+assembly.  The '.set nomips3d' directive prevents MIPS-3D instructions
+from being accepted.
 
-   The directive `.set smartmips' makes the assembler accept
+   The directive '.set smartmips' makes the assembler accept
 instructions from the SmartMIPS Application Specific Extension to the
-MIPS32 ISA from that point on in the assembly.  The `.set nosmartmips'
+MIPS32 ISA from that point on in the assembly.  The '.set nosmartmips'
 directive prevents SmartMIPS instructions from being accepted.
 
-   The directive `.set mdmx' makes the assembler accept instructions
+   The directive '.set mdmx' makes the assembler accept instructions
 from the MDMX Application Specific Extension from that point on in the
-assembly.  The `.set nomdmx' directive prevents MDMX instructions from
+assembly.  The '.set nomdmx' directive prevents MDMX instructions from
 being accepted.
 
-   The directive `.set dsp' makes the assembler accept instructions
-from the DSP Release 1 Application Specific Extension from that point
-on in the assembly.  The `.set nodsp' directive prevents DSP Release 1
+   The directive '.set dsp' makes the assembler accept instructions from
+the DSP Release 1 Application Specific Extension from that point on in
+the assembly.  The '.set nodsp' directive prevents DSP Release 1
 instructions from being accepted.
 
-   The directive `.set dspr2' makes the assembler accept instructions
-from the DSP Release 2 Application Specific Extension from that point
-on in the assembly.  This dirctive implies `.set dsp'.  The `.set
-nodspr2' directive prevents DSP Release 2 instructions from being
-accepted.
+   The directive '.set dspr2' makes the assembler accept instructions
+from the DSP Release 2 Application Specific Extension from that point on
+in the assembly.  This dirctive implies '.set dsp'.  The '.set nodspr2'
+directive prevents DSP Release 2 instructions from being accepted.
 
-   The directive `.set mt' makes the assembler accept instructions from
+   The directive '.set mt' makes the assembler accept instructions from
 the MT Application Specific Extension from that point on in the
-assembly.  The `.set nomt' directive prevents MT instructions from
-being accepted.
+assembly.  The '.set nomt' directive prevents MT instructions from being
+accepted.
 
-   The directive `.set mcu' makes the assembler accept instructions
-from the MCU Application Specific Extension from that point on in the
-assembly.  The `.set nomcu' directive prevents MCU instructions from
+   The directive '.set mcu' makes the assembler accept instructions from
+the MCU Application Specific Extension from that point on in the
+assembly.  The '.set nomcu' directive prevents MCU instructions from
 being accepted.
 
+   The directive '.set virt' makes the assembler accept instructions
+from the Virtualization Application Specific Extension from that point
+on in the assembly.  The '.set novirt' directive prevents Virtualization
+instructions from being accepted.
+
    Traditional MIPS assemblers do not support these directives.
 
 
-File: as.info,  Node: MIPS floating-point,  Next: MIPS Syntax,  Prev: MIPS ASE instruction generation overrides,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Floating-Point,  Next: MIPS Syntax,  Prev: MIPS ASE Instruction Generation Overrides,  Up: MIPS-Dependent
 
-9.27.10 Directives to override floating-point options
+9.27.12 Directives to override floating-point options
 -----------------------------------------------------
 
-The directives `.set softfloat' and `.set hardfloat' provide finer
+The directives '.set softfloat' and '.set hardfloat' provide finer
 control of disabling and enabling float-point instructions.  These
-directives always override the default (that hard-float instructions
-are accepted) or the command-line options (`-msoft-float' and
-`-mhard-float').
+directives always override the default (that hard-float instructions are
+accepted) or the command-line options ('-msoft-float' and
+'-mhard-float').
 
-   The directives `.set singlefloat' and `.set doublefloat' provide
+   The directives '.set singlefloat' and '.set doublefloat' provide
 finer control of disabling and enabling double-precision float-point
 operations.  These directives always override the default (that
 double-precision operations are accepted) or the command-line options
-(`-msingle-float' and `-mdouble-float').
+('-msingle-float' and '-mdouble-float').
 
    Traditional MIPS assemblers do not support these directives.
 
 
-File: as.info,  Node: MIPS Syntax,  Prev: MIPS floating-point,  Up: MIPS-Dependent
+File: as.info,  Node: MIPS Syntax,  Prev: MIPS Floating-Point,  Up: MIPS-Dependent
 
-9.27.11 Syntactical considerations for the MIPS assembler
+9.27.13 Syntactical considerations for the MIPS assembler
 ---------------------------------------------------------
 
 * Menu:
@@ -13818,18 +13707,18 @@ File: as.info,  Node: MIPS Syntax,  Prev: MIPS floating-point,  Up: MIPS-Depende
 
 File: as.info,  Node: MIPS-Chars,  Up: MIPS Syntax
 
-9.27.11.1 Special Characters
+9.27.13.1 Special Characters
 ............................
 
-The presence of a `#' on a line indicates the start of a comment that
+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
+   If a '#' appears as the first character of a line, the whole line is
 treated as a comment, but in this case the line can also be a logical
 line number directive (*note Comments::) or a preprocessor control
 command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -13843,7 +13732,7 @@ File: as.info,  Node: MMIX-Dependent,  Next: MSP430-Dependent,  Prev: MIPS-Depen
 * MMIX-Opts::              Command-line Options
 * MMIX-Expand::            Instruction expansion
 * MMIX-Syntax::            Syntax
-* MMIX-mmixal::		   Differences to `mmixal' syntax and semantics
+* MMIX-mmixal::		   Differences to 'mmixal' syntax and semantics
 
 
 File: as.info,  Node: MMIX-Opts,  Next: MMIX-Expand,  Up: MMIX-Dependent
@@ -13851,70 +13740,70 @@ File: as.info,  Node: MMIX-Opts,  Next: MMIX-Expand,  Up: MMIX-Dependent
 9.28.1 Command-line Options
 ---------------------------
 
-The MMIX version of `as' has some machine-dependent options.
+The MMIX version of 'as' has some machine-dependent options.
 
-   When `--fixed-special-register-names' is specified, only the register
+   When '--fixed-special-register-names' is specified, only the register
 names specified in *note MMIX-Regs:: are recognized in the instructions
-`PUT' and `GET'.
+'PUT' and 'GET'.
 
-   You can use the `--globalize-symbols' to make all symbols global.
-This option is useful when splitting up a `mmixal' program into several
+   You can use the '--globalize-symbols' to make all symbols global.
+This option is useful when splitting up a 'mmixal' program into several
 files.
 
-   The `--gnu-syntax' turns off most syntax compatibility with
-`mmixal'.  Its usability is currently doubtful.
+   The '--gnu-syntax' turns off most syntax compatibility with 'mmixal'.
+Its usability is currently doubtful.
 
-   The `--relax' option is not fully supported, but will eventually make
+   The '--relax' option is not fully supported, but will eventually make
 the object file prepared for linker relaxation.
 
    If you want to avoid inadvertently calling a predefined symbol and
-would rather get an error, for example when using `as' with a compiler
-or other machine-generated code, specify `--no-predefined-syms'.  This
-turns off built-in predefined definitions of all such symbols,
-including rounding-mode symbols, segment symbols, `BIT' symbols, and
-`TRAP' symbols used in `mmix' "system calls".  It also turns off
-predefined special-register names, except when used in `PUT' and `GET'
+would rather get an error, for example when using 'as' with a compiler
+or other machine-generated code, specify '--no-predefined-syms'.  This
+turns off built-in predefined definitions of all such symbols, including
+rounding-mode symbols, segment symbols, 'BIT' symbols, and 'TRAP'
+symbols used in 'mmix' "system calls".  It also turns off predefined
+special-register names, except when used in 'PUT' and 'GET'
 instructions.
 
    By default, some instructions are expanded to fit the size of the
 operand or an external symbol (*note MMIX-Expand::).  By passing
-`--no-expand', no such expansion will be done, instead causing errors
-at link time if the operand does not fit.
+'--no-expand', no such expansion will be done, instead causing errors at
+link time if the operand does not fit.
 
-   The `mmixal' documentation (*note mmixsite::) specifies that global
-registers allocated with the `GREG' directive (*note MMIX-greg::) and
+   The 'mmixal' documentation (*note mmixsite::) specifies that global
+registers allocated with the 'GREG' directive (*note MMIX-greg::) and
 initialized to the same non-zero value, will refer to the same global
-register.  This isn't strictly enforceable in `as' since the final
+register.  This isn't strictly enforceable in 'as' since the final
 addresses aren't known until link-time, but it will do an effort unless
-the `--no-merge-gregs' option is specified.  (Register merging isn't
-yet implemented in `ld'.)
-
-   `as' will warn every time it expands an instruction to fit an
-operand unless the option `-x' is specified.  It is believed that this
-behaviour is more useful than just mimicking `mmixal''s behaviour, in
-which instructions are only expanded if the `-x' option is specified,
-and assembly fails otherwise, when an instruction needs to be expanded.
-It needs to be kept in mind that `mmixal' is both an assembler and
-linker, while `as' will expand instructions that at link stage can be
-contracted.  (Though linker relaxation isn't yet implemented in `ld'.)
-The option `-x' also imples `--linker-allocated-gregs'.
-
-   If instruction expansion is enabled, `as' can expand a `PUSHJ'
-instruction into a series of instructions.  The shortest expansion is
-to not expand it, but just mark the call as redirectable to a stub,
-which `ld' creates at link-time, but only if the original `PUSHJ'
-instruction is found not to reach the target.  The stub consists of the
-necessary instructions to form a jump to the target.  This happens if
-`as' can assert that the `PUSHJ' instruction can reach such a stub.
-The option `--no-pushj-stubs' disables this shorter expansion, and the
-longer series of instructions is then created at assembly-time.  The
-option `--no-stubs' is a synonym, intended for compatibility with
-future releases, where generation of stubs for other instructions may
-be implemented.
+the '--no-merge-gregs' option is specified.  (Register merging isn't yet
+implemented in 'ld'.)
+
+   'as' will warn every time it expands an instruction to fit an operand
+unless the option '-x' is specified.  It is believed that this behaviour
+is more useful than just mimicking 'mmixal''s behaviour, in which
+instructions are only expanded if the '-x' option is specified, and
+assembly fails otherwise, when an instruction needs to be expanded.  It
+needs to be kept in mind that 'mmixal' is both an assembler and linker,
+while 'as' will expand instructions that at link stage can be
+contracted.  (Though linker relaxation isn't yet implemented in 'ld'.)
+The option '-x' also imples '--linker-allocated-gregs'.
+
+   If instruction expansion is enabled, 'as' can expand a 'PUSHJ'
+instruction into a series of instructions.  The shortest expansion is to
+not expand it, but just mark the call as redirectable to a stub, which
+'ld' creates at link-time, but only if the original 'PUSHJ' instruction
+is found not to reach the target.  The stub consists of the necessary
+instructions to form a jump to the target.  This happens if 'as' can
+assert that the 'PUSHJ' instruction can reach such a stub.  The option
+'--no-pushj-stubs' disables this shorter expansion, and the longer
+series of instructions is then created at assembly-time.  The option
+'--no-stubs' is a synonym, intended for compatibility with future
+releases, where generation of stubs for other instructions may be
+implemented.
 
    Usually a two-operand-expression (*note GREG-base::) without a
-matching `GREG' directive is treated as an error by `as'.  When the
-option `--linker-allocated-gregs' is in effect, they are instead passed
+matching 'GREG' directive is treated as an error by 'as'.  When the
+option '--linker-allocated-gregs' is in effect, they are instead passed
 through to the linker, which will allocate as many global registers as
 is needed.
 
@@ -13924,33 +13813,30 @@ File: as.info,  Node: MMIX-Expand,  Next: MMIX-Syntax,  Prev: MMIX-Opts,  Up: MM
 9.28.2 Instruction expansion
 ----------------------------
 
-When `as' encounters an instruction with an operand that is either not
-known or does not fit the operand size of the instruction, `as' (and
-`ld') will expand the instruction into a sequence of instructions
+When 'as' encounters an instruction with an operand that is either not
+known or does not fit the operand size of the instruction, 'as' (and
+'ld') will expand the instruction into a sequence of instructions
 semantically equivalent to the operand fitting the instruction.
 Expansion will take place for the following instructions:
 
-`GETA'
-     Expands to a sequence of four instructions: `SETL', `INCML',
-     `INCMH' and `INCH'.  The operand must be a multiple of four.
-
+'GETA'
+     Expands to a sequence of four instructions: 'SETL', 'INCML',
+     'INCMH' and 'INCH'.  The operand must be a multiple of four.
 Conditional branches
      A branch instruction is turned into a branch with the complemented
      condition and prediction bit over five instructions; four
-     instructions setting `$255' to the operand value, which like with
-     `GETA' must be a multiple of four, and a final `GO $255,$255,0'.
-
-`PUSHJ'
+     instructions setting '$255' to the operand value, which like with
+     'GETA' must be a multiple of four, and a final 'GO $255,$255,0'.
+'PUSHJ'
      Similar to expansion for conditional branches; four instructions
-     set `$255' to the operand value, followed by a `PUSHGO
+     set '$255' to the operand value, followed by a 'PUSHGO
      $255,$255,0'.
+'JMP'
+     Similar to conditional branches and 'PUSHJ'.  The final instruction
+     is 'GO $255,$255,0'.
 
-`JMP'
-     Similar to conditional branches and `PUSHJ'.  The final instruction
-     is `GO $255,$255,0'.
-
-   The linker `ld' is expected to shrink these expansions for code
-assembled with `--relax' (though not currently implemented).
+   The linker 'ld' is expected to shrink these expansions for code
+assembled with '--relax' (though not currently implemented).
 
 
 File: as.info,  Node: MMIX-Syntax,  Next: MMIX-mmixal,  Prev: MMIX-Expand,  Up: MMIX-Dependent
@@ -13959,10 +13845,10 @@ File: as.info,  Node: MMIX-Syntax,  Next: MMIX-mmixal,  Prev: MMIX-Expand,  Up:
 -------------
 
 The assembly syntax is supposed to be upward compatible with that
-described in Sections 1.3 and 1.4 of `The Art of Computer Programming,
+described in Sections 1.3 and 1.4 of 'The Art of Computer Programming,
 Volume 1'.  Draft versions of those chapters as well as other MMIX
 information is located at
-`http://www-cs-faculty.stanford.edu/~knuth/mmix-news.html'.  Most code
+<http://www-cs-faculty.stanford.edu/~knuth/mmix-news.html>.  Most code
 examples from the mmixal package located there should work unmodified
 when assembled and linked as single files, with a few noteworthy
 exceptions (*note MMIX-mmixal::).
@@ -13971,8 +13857,8 @@ exceptions (*note MMIX-mmixal::).
 the next four-byte boundary.  If a label is defined at the beginning of
 the line, its value will be the aligned value.
 
-   In addition to the traditional hex-prefix `0x', a hexadecimal number
-can also be specified by the prefix character `#'.
+   In addition to the traditional hex-prefix '0x', a hexadecimal number
+can also be specified by the prefix character '#'.
 
    After all operands to an MMIX instruction or directive have been
 specified, the rest of the line is ignored, treated as a comment.
@@ -13990,19 +13876,19 @@ File: as.info,  Node: MMIX-Chars,  Next: MMIX-Symbols,  Up: MMIX-Syntax
 9.28.3.1 Special Characters
 ...........................
 
-The characters `*' and `#' are line comment characters; each start a
-comment at the beginning of a line, but only at the beginning of a
-line.  A `#' prefixes a hexadecimal number if found elsewhere on a
-line.  If a `#' appears at the start of a line the whole line is
-treated as a comment, but the line can also act as a logical line
-number directive (*note Comments::) or a preprocessor control command
-(*note Preprocessing::).
+The characters '*' and '#' are line comment characters; each start a
+comment at the beginning of a line, but only at the beginning of a line.
+A '#' prefixes a hexadecimal number if found elsewhere on a line.  If a
+'#' appears at the start of a line the whole line is treated as a
+comment, but the line can also act as a logical line number directive
+(*note Comments::) or a preprocessor control command (*note
+Preprocessing::).
 
-   Two other characters, `%' and `!', each start a comment anywhere on
-the line.  Thus you can't use the `modulus' and `not' operators in
+   Two other characters, '%' and '!', each start a comment anywhere on
+the line.  Thus you can't use the 'modulus' and 'not' operators in
 expressions normally associated with these two characters.
 
-   A `;' is a line separator, treated as a new-line, so separate
+   A ';' is a line separator, treated as a new-line, so separate
 instructions can be specified on a single line.
 
 
@@ -14011,40 +13897,39 @@ File: as.info,  Node: MMIX-Symbols,  Next: MMIX-Regs,  Prev: MMIX-Chars,  Up: MM
 9.28.3.2 Symbols
 ................
 
-The character `:' is permitted in identifiers.  There are two
-exceptions to it being treated as any other symbol character: if a
-symbol begins with `:', it means that the symbol is in the global
-namespace and that the current prefix should not be prepended to that
-symbol (*note MMIX-prefix::).  The `:' is then not considered part of
-the symbol.  For a symbol in the label position (first on a line), a `:'
-at the end of a symbol is silently stripped off.  A label is permitted,
-but not required, to be followed by a `:', as with many other assembly
-formats.
+The character ':' is permitted in identifiers.  There are two exceptions
+to it being treated as any other symbol character: if a symbol begins
+with ':', it means that the symbol is in the global namespace and that
+the current prefix should not be prepended to that symbol (*note
+MMIX-prefix::).  The ':' is then not considered part of the symbol.  For
+a symbol in the label position (first on a line), a ':' at the end of a
+symbol is silently stripped off.  A label is permitted, but not
+required, to be followed by a ':', as with many other assembly formats.
 
-   The character `@' in an expression, is a synonym for `.', the
-current location.
+   The character '@' in an expression, is a synonym for '.', the current
+location.
 
    In addition to the common forward and backward local symbol formats
-(*note Symbol Names::), they can be specified with upper-case `B' and
-`F', as in `8B' and `9F'.  A local label defined for the current
-position is written with a `H' appended to the number:
+(*note Symbol Names::), they can be specified with upper-case 'B' and
+'F', as in '8B' and '9F'.  A local label defined for the current
+position is written with a 'H' appended to the number:
      3H LDB $0,$1,2
    This and traditional local-label formats cannot be mixed: a label
 must be defined and referred to using the same format.
 
    There's a minor caveat: just as for the ordinary local symbols, the
 local symbols are translated into ordinary symbols using control
-characters are to hide the ordinal number of the symbol.
-Unfortunately, these symbols are not translated back in error messages.
-Thus you may see confusing error messages when local symbols are used.
-Control characters `\003' (control-C) and `\004' (control-D) are used
-for the MMIX-specific local-symbol syntax.
+characters are to hide the ordinal number of the symbol.  Unfortunately,
+these symbols are not translated back in error messages.  Thus you may
+see confusing error messages when local symbols are used.  Control
+characters '\003' (control-C) and '\004' (control-D) are used for the
+MMIX-specific local-symbol syntax.
 
-   The symbol `Main' is handled specially; it is always global.
+   The symbol 'Main' is handled specially; it is always global.
 
-   By defining the symbols `__.MMIX.start..text' and
-`__.MMIX.start..data', the address of respectively the `.text' and
-`.data' segments of the final program can be defined, though when
+   By defining the symbols '__.MMIX.start..text' and
+'__.MMIX.start..data', the address of respectively the '.text' and
+'.data' segments of the final program can be defined, though when
 linking more than one object file, the code or data in the object file
 containing the symbol is not guaranteed to be start at that position;
 just the final executable.  *Note MMIX-loc::.
@@ -14055,11 +13940,11 @@ File: as.info,  Node: MMIX-Regs,  Next: MMIX-Pseudos,  Prev: MMIX-Symbols,  Up:
 9.28.3.3 Register names
 .......................
 
-Local and global registers are specified as `$0' to `$255'.  The
-recognized special register names are `rJ', `rA', `rB', `rC', `rD',
-`rE', `rF', `rG', `rH', `rI', `rK', `rL', `rM', `rN', `rO', `rP', `rQ',
-`rR', `rS', `rT', `rU', `rV', `rW', `rX', `rY', `rZ', `rBB', `rTT',
-`rWW', `rXX', `rYY' and `rZZ'.  A leading `:' is optional for special
+Local and global registers are specified as '$0' to '$255'.  The
+recognized special register names are 'rJ', 'rA', 'rB', 'rC', 'rD',
+'rE', 'rF', 'rG', 'rH', 'rI', 'rK', 'rL', 'rM', 'rN', 'rO', 'rP', 'rQ',
+'rR', 'rS', 'rT', 'rU', 'rV', 'rW', 'rX', 'rY', 'rZ', 'rBB', 'rTT',
+'rWW', 'rXX', 'rYY' and 'rZZ'.  A leading ':' is optional for special
 register names.
 
    Local and global symbols can be equated to register names and used in
@@ -14068,9 +13953,9 @@ place of ordinary registers.
    Similarly for special registers, local and global symbols can be
 used.  Also, symbols equated from numbers and constant expressions are
 allowed in place of a special register, except when either of the
-options `--no-predefined-syms' and `--fixed-special-register-names' are
+options '--no-predefined-syms' and '--fixed-special-register-names' are
 specified.  Then only the special register names above are allowed for
-the instructions having a special register operand; `GET' and `PUT'.
+the instructions having a special register operand; 'GET' and 'PUT'.
 
 
 File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
@@ -14078,12 +13963,13 @@ File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
 9.28.3.4 Assembler Directives
 .............................
 
-`LOC'
-     The `LOC' directive sets the current location to the value of the
-     operand field, which may include changing sections.  If the
-     operand is a constant, the section is set to either `.data' if the
-     value is `0x2000000000000000' or larger, else it is set to `.text'.
-     Within a section, the current location may only be changed to
+'LOC'
+
+     The 'LOC' directive sets the current location to the value of the
+     operand field, which may include changing sections.  If the operand
+     is a constant, the section is set to either '.data' if the value is
+     '0x2000000000000000' or larger, else it is set to '.text'.  Within
+     a section, the current location may only be changed to
      monotonically higher addresses.  A LOC expression must be a
      previously defined symbol or a "pure" constant.
 
@@ -14092,14 +13978,15 @@ File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
           prev LOC @+8
 
      When a LOC has a constant as its operand, a symbol
-     `__.MMIX.start..text' or `__.MMIX.start..data' is defined
-     depending on the address as mentioned above.  Each such symbol is
-     interpreted as special by the linker, locating the section at that
-     address.  Note that if multiple files are linked, the first object
-     file with that section will be mapped to that address (not
-     necessarily the file with the LOC definition).
-
-`LOCAL'
+     '__.MMIX.start..text' or '__.MMIX.start..data' is defined depending
+     on the address as mentioned above.  Each such symbol is interpreted
+     as special by the linker, locating the section at that address.
+     Note that if multiple files are linked, the first object file with
+     that section will be mapped to that address (not necessarily the
+     file with the LOC definition).
+
+'LOCAL'
+
      Example:
            LOCAL external_symbol
            LOCAL 42
@@ -14110,18 +13997,20 @@ File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
      an expression that at link-time resolves to a register symbol or a
      number.  A number is treated as the register having that number.
      There is one restriction on the use of this directive: the
-     pseudo-directive must be placed in a section with contents, code
-     or data.
+     pseudo-directive must be placed in a section with contents, code or
+     data.
 
-`IS'
-     The `IS' directive:
+'IS'
+
+     The 'IS' directive:
           asymbol IS an_expression
-     sets the symbol `asymbol' to `an_expression'.  A symbol may not be
+     sets the symbol 'asymbol' to 'an_expression'.  A symbol may not be
      set more than once using this directive.  Local labels may be set
      using this directive, for example:
           5H IS @+4
 
-`GREG'
+'GREG'
+
      This directive reserves a global register, gives it an initial
      value and optionally gives it a symbolic name.  Some examples:
 
@@ -14132,26 +14021,26 @@ File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
 
      The symbolic register name can be used in place of a (non-special)
      register.  If a value isn't provided, it defaults to zero.  Unless
-     the option `--no-merge-gregs' is specified, non-zero registers
-     allocated with this directive may be eliminated by `as'; another
+     the option '--no-merge-gregs' is specified, non-zero registers
+     allocated with this directive may be eliminated by 'as'; another
      register with the same value used in its place.  Any of the
-     instructions `CSWAP', `GO', `LDA', `LDBU', `LDB', `LDHT', `LDOU',
-     `LDO', `LDSF', `LDTU', `LDT', `LDUNC', `LDVTS', `LDWU', `LDW',
-     `PREGO', `PRELD', `PREST', `PUSHGO', `STBU', `STB', `STCO', `STHT',
-     `STOU', `STSF', `STTU', `STT', `STUNC', `SYNCD', `SYNCID', can
-     have a value nearby an initial value in place of its second and
-     third operands.  Here, "nearby" is defined as within the range
-     0...255 from the initial value of such an allocated register.
+     instructions 'CSWAP', 'GO', 'LDA', 'LDBU', 'LDB', 'LDHT', 'LDOU',
+     'LDO', 'LDSF', 'LDTU', 'LDT', 'LDUNC', 'LDVTS', 'LDWU', 'LDW',
+     'PREGO', 'PRELD', 'PREST', 'PUSHGO', 'STBU', 'STB', 'STCO', 'STHT',
+     'STOU', 'STSF', 'STTU', 'STT', 'STUNC', 'SYNCD', 'SYNCID', can have
+     a value nearby an initial value in place of its second and third
+     operands.  Here, "nearby" is defined as within the range 0...255
+     from the initial value of such an allocated register.
 
           buffer1 BYTE 0,0,0,0,0
           buffer2 BYTE 0,0,0,0,0
            ...
            GREG buffer1
            LDOU $42,buffer2
-     In the example above, the `Y' field of the `LDOUI' instruction
+     In the example above, the 'Y' field of the 'LDOUI' instruction
      (LDOU with a constant Z) will be replaced with the global register
-     allocated for `buffer1', and the `Z' field will have the value 5,
-     the offset from `buffer1' to `buffer2'.  The result is equivalent
+     allocated for 'buffer1', and the 'Z' field will have the value 5,
+     the offset from 'buffer1' to 'buffer2'.  The result is equivalent
      to this code:
           buffer1 BYTE 0,0,0,0,0
           buffer2 BYTE 0,0,0,0,0
@@ -14163,72 +14052,75 @@ File: as.info,  Node: MMIX-Pseudos,  Prev: MMIX-Regs,  Up: MMIX-Syntax
      order higher-to-lower within a file.  Other than that, the exact
      order of register allocation and elimination is undefined.  For
      example, the order is undefined when more than one file with such
-     directives are linked together.  With the options `-x' and
-     `--linker-allocated-gregs', `GREG' directives for two-operand
-     cases like the one mentioned above can be omitted.  Sufficient
-     global registers will then be allocated by the linker.
-
-`BYTE'
-     The `BYTE' directive takes a series of operands separated by a
-     comma.  If an operand is a string (*note Strings::), each
-     character of that string is emitted as a byte.  Other operands
-     must be constant expressions without forward references, in the
-     range 0...255.  If you need operands having expressions with
-     forward references, use `.byte' (*note Byte::).  An operand can be
-     omitted, defaulting to a zero value.
-
-`WYDE'
-`TETRA'
-`OCTA'
-     The directives `WYDE', `TETRA' and `OCTA' emit constants of two,
+     directives are linked together.  With the options '-x' and
+     '--linker-allocated-gregs', 'GREG' directives for two-operand cases
+     like the one mentioned above can be omitted.  Sufficient global
+     registers will then be allocated by the linker.
+
+'BYTE'
+
+     The 'BYTE' directive takes a series of operands separated by a
+     comma.  If an operand is a string (*note Strings::), each character
+     of that string is emitted as a byte.  Other operands must be
+     constant expressions without forward references, in the range
+     0...255.  If you need operands having expressions with forward
+     references, use '.byte' (*note Byte::).  An operand can be omitted,
+     defaulting to a zero value.
+
+'WYDE'
+'TETRA'
+'OCTA'
+
+     The directives 'WYDE', 'TETRA' and 'OCTA' emit constants of two,
      four and eight bytes size respectively.  Before anything else
      happens for the directive, the current location is aligned to the
      respective constant-size boundary.  If a label is defined at the
      beginning of the line, its value will be that after the alignment.
-     A single operand can be omitted, defaulting to a zero value
-     emitted for the directive.  Operands can be expressed as strings
-     (*note Strings::), in which case each character in the string is
-     emitted as a separate constant of the size indicated by the
-     directive.
+     A single operand can be omitted, defaulting to a zero value emitted
+     for the directive.  Operands can be expressed as strings (*note
+     Strings::), in which case each character in the string is emitted
+     as a separate constant of the size indicated by the directive.
+
+'PREFIX'
 
-`PREFIX'
-     The `PREFIX' directive sets a symbol name prefix to be prepended to
+     The 'PREFIX' directive sets a symbol name prefix to be prepended to
      all symbols (except local symbols, *note MMIX-Symbols::), that are
-     not prefixed with `:', until the next `PREFIX' directive.  Such
+     not prefixed with ':', until the next 'PREFIX' directive.  Such
      prefixes accumulate.  For example,
            PREFIX a
            PREFIX b
           c IS 0
-     defines a symbol `abc' with the value 0.
+     defines a symbol 'abc' with the value 0.
 
-`BSPEC'
-`ESPEC'
-     A pair of `BSPEC' and `ESPEC' directives delimit a section of
+'BSPEC'
+'ESPEC'
+
+     A pair of 'BSPEC' and 'ESPEC' directives delimit a section of
      special contents (without specified semantics).  Example:
            BSPEC 42
            TETRA 1,2,3
            ESPEC
-     The single operand to `BSPEC' must be number in the range 0...255.
-     The `BSPEC' number 80 is used by the GNU binutils implementation.
+     The single operand to 'BSPEC' must be number in the range 0...255.
+     The 'BSPEC' number 80 is used by the GNU binutils implementation.
 
 
 File: as.info,  Node: MMIX-mmixal,  Prev: MMIX-Syntax,  Up: MMIX-Dependent
 
-9.28.4 Differences to `mmixal'
+9.28.4 Differences to 'mmixal'
 ------------------------------
 
-The binutils `as' and `ld' combination has a few differences in
-function compared to `mmixal' (*note mmixsite::).
+The binutils 'as' and 'ld' combination has a few differences in function
+compared to 'mmixal' (*note mmixsite::).
 
    The replacement of a symbol with a GREG-allocated register (*note
-GREG-base::) is not handled the exactly same way in `as' as in
-`mmixal'.  This is apparent in the `mmixal' example file `inout.mms',
-where different registers with different offsets, eventually yielding
-the same address, are used in the first instruction.  This type of
-difference should however not affect the function of any program unless
-it has specific assumptions about the allocated register number.
-
-   Line numbers (in the `mmo' object format) are currently not
+GREG-base::) is not handled the exactly same way in 'as' as in 'mmixal'.
+This is apparent in the 'mmixal' example file 'inout.mms', where
+different registers with different offsets, eventually yielding the same
+address, are used in the first instruction.  This type of difference
+should however not affect the function of any program unless it has
+specific assumptions about the allocated register number.
+
+   Line numbers (in the 'mmo' object format) are currently not
 supported.
 
    Expression operator precedence is not that of mmixal: operator
@@ -14236,16 +14128,16 @@ precedence is that of the C programming language.  It's recommended to
 use parentheses to explicitly specify wanted operator precedence
 whenever more than one type of operators are used.
 
-   The serialize unary operator `&', the fractional division operator
-`//', the logical not operator `!' and the modulus operator `%' are not
+   The serialize unary operator '&', the fractional division operator
+'//', the logical not operator '!' and the modulus operator '%' are not
 available.
 
    Symbols are not global by default, unless the option
-`--globalize-symbols' is passed.  Use the `.global' directive to
+'--globalize-symbols' is passed.  Use the '.global' directive to
 globalize symbols (*note Global::).
 
-   Operand syntax is a bit stricter with `as' than `mmixal'.  For
-example, you can't say `addu 1,2,3', instead you must write `addu
+   Operand syntax is a bit stricter with 'as' than 'mmixal'.  For
+example, you can't say 'addu 1,2,3', instead you must write 'addu
 $1,$2,3'.
 
    You can't LOC to a lower address than those already visited (i.e.,
@@ -14259,9 +14151,9 @@ symbol.)
 
    Some mapping of constant expressions to sections in LOC expressions
 is attempted, but that functionality is easily confused and should be
-avoided unless compatibility with `mmixal' is required.  A LOC
-expression to `0x2000000000000000' or higher, maps to the `.data'
-section and lower addresses map to the `.text' section (*note
+avoided unless compatibility with 'mmixal' is required.  A LOC
+expression to '0x2000000000000000' or higher, maps to the '.data'
+section and lower addresses map to the '.text' section (*note
 MMIX-loc::).
 
    The code and data areas are each contiguous.  Sparse programs with
@@ -14270,38 +14162,36 @@ contiguous program with zeros filled in the gaps between the LOC
 directives.  If you need sparse programs, you might try and get the
 wanted effect with a linker script and splitting up the code parts into
 sections (*note Section::).  Assembly code for this, to be compatible
-with `mmixal', would look something like:
+with 'mmixal', would look something like:
       .if 0
       LOC away_expression
       .else
       .section away,"ax"
       .fi
-   `as' will not execute the LOC directive and `mmixal' ignores the
-lines with `.'.  This construct can be used generally to help
+   'as' will not execute the LOC directive and 'mmixal' ignores the
+lines with '.'.  This construct can be used generally to help
 compatibility.
 
    Symbols can't be defined twice-not even to the same value.
 
    Instruction mnemonics are recognized case-insensitive, though the
-`IS' and `GREG' pseudo-operations must be specified in upper-case
+'IS' and 'GREG' pseudo-operations must be specified in upper-case
 characters.
 
    There's no unicode support.
 
-   The following is a list of programs in `mmix.tar.gz', available at
-`http://www-cs-faculty.stanford.edu/~knuth/mmix-news.html', last
-checked with the version dated 2001-08-25 (md5sum
-c393470cfc86fac040487d22d2bf0172) that assemble with `mmixal' but do
-not assemble with `as':
+   The following is a list of programs in 'mmix.tar.gz', available at
+<http://www-cs-faculty.stanford.edu/~knuth/mmix-news.html>, last checked
+with the version dated 2001-08-25 (md5sum
+c393470cfc86fac040487d22d2bf0172) that assemble with 'mmixal' but do not
+assemble with 'as':
 
-`silly.mms'
+'silly.mms'
      LOC to a previous address.
-
-`sim.mms'
-     Redefines symbol `Done'.
-
-`test.mms'
-     Uses the serial operator `&'.
+'sim.mms'
+     Redefines symbol 'Done'.
+'test.mms'
+     Uses the serial operator '&'.
 
 
 File: as.info,  Node: MSP430-Dependent,  Next: NiosII-Dependent,  Prev: MMIX-Dependent,  Up: Machine Dependencies
@@ -14324,15 +14214,38 @@ File: as.info,  Node: MSP430 Options,  Next: MSP430 Syntax,  Up: MSP430-Dependen
 9.29.1 Options
 --------------
 
-`-m'
-     select the mpu arch. Currently has no effect.
+'-mmcu'
+     selects the mpu arch.  If the architecture is 430Xv2 then this also
+     enables NOP generation unless the '-mN' is also specified.
 
-`-mP'
+'-mcpu'
+     selects the cpu architecture.  If the architecture is 430Xv2 then
+     this also enables NOP generation unless the '-mN' is also
+     specified.
+
+'-mP'
      enables polymorph instructions handler.
 
-`-mQ'
-     enables relaxation at assembly time. DANGEROUS!
+'-mQ'
+     enables relaxation at assembly time.  DANGEROUS!
+
+'-ml'
+     indicates that the input uses the large code model.
 
+'-mN'
+     disables the generation of a NOP instruction following any
+     instruction that might change the interrupts enabled/disabled
+     state.  For the 430Xv2 architecture the instructions: 'EINT',
+     'DINT', 'BIC #8, SR', 'BIS #8, SR' and 'MOV.W <>, SR' must be
+     followed by a NOP instruction in order to ensure the correct
+     processing of interrupts.  By default generation of the NOP
+     instruction happens automatically, but this command line option
+     disables this behaviour.  It is then up to the programmer to ensure
+     that interrupts are enabled and disabled correctly.
+
+'-md'
+     mark the object file as one that requires data to copied from ROM
+     to RAM at execution startup.  Disabled by default.
 
 
 File: as.info,  Node: MSP430 Syntax,  Next: MSP430 Floating Point,  Prev: MSP430 Options,  Up: MSP430-Dependent
@@ -14354,24 +14267,23 @@ File: as.info,  Node: MSP430-Macros,  Next: MSP430-Chars,  Up: MSP430 Syntax
 ...............
 
 The macro syntax used on the MSP 430 is like that described in the MSP
-430 Family Assembler Specification.  Normal `as' macros should still
+430 Family Assembler Specification.  Normal 'as' macros should still
 work.
 
    Additional built-in macros are:
 
-`llo(exp)'
+'llo(exp)'
      Extracts least significant word from 32-bit expression 'exp'.
 
-`lhi(exp)'
+'lhi(exp)'
      Extracts most significant word from 32-bit expression 'exp'.
 
-`hlo(exp)'
+'hlo(exp)'
      Extracts 3rd word from 64-bit expression 'exp'.
 
-`hhi(exp)'
+'hhi(exp)'
      Extracts 4rd word from 64-bit expression 'exp'.
 
-
    They normally being used as an immediate source operand.
          mov	#llo(1), r10	;	== mov	#1, r10
          mov	#lhi(1), r10	;	== mov	#0, r10
@@ -14382,18 +14294,18 @@ File: as.info,  Node: MSP430-Chars,  Next: MSP430-Regs,  Prev: MSP430-Macros,  U
 9.29.2.2 Special Characters
 ...........................
 
-A semicolon (`;') appearing anywhere on a line starts a comment that
+A semicolon (';') appearing anywhere on a line starts 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 it can also be a logical line number
+   If a '#' appears as the first character of a line then the whole line
+is treated as a comment, but it can also be a logical line number
 directive (*note Comments::) or a preprocessor control command (*note
 Preprocessing::).
 
    Multiple statements can appear on the same line provided that they
-are separated by the `{' character.
+are separated by the '{' character.
 
-   The character `$' in jump instructions indicates current location and
+   The character '$' in jump instructions indicates current location and
 implemented only for TI syntax compatibility.
 
 
@@ -14403,12 +14315,12 @@ File: as.info,  Node: MSP430-Regs,  Next: MSP430-Ext,  Prev: MSP430-Chars,  Up:
 .......................
 
 General-purpose registers are represented by predefined symbols of the
-form `rN' (for global registers), where N represents a number between
-`0' and `15'.  The leading letters may be in either upper or lower
-case; for example, `r13' and `R7' are both valid register names.
+form 'rN' (for global registers), where N represents a number between
+'0' and '15'.  The leading letters may be in either upper or lower case;
+for example, 'r13' and 'R7' are both valid register names.
 
-   Register names `PC', `SP' and `SR' cannot be used as register names
-and will be treated as variables. Use `r0', `r1', and `r2' instead.
+   Register names 'PC', 'SP' and 'SR' cannot be used as register names
+and will be treated as variables.  Use 'r0', 'r1', and 'r2' instead.
 
 
 File: as.info,  Node: MSP430-Ext,  Prev: MSP430-Regs,  Up: MSP430 Syntax
@@ -14416,65 +14328,64 @@ File: as.info,  Node: MSP430-Ext,  Prev: MSP430-Regs,  Up: MSP430 Syntax
 9.29.2.4 Assembler Extensions
 .............................
 
-`@rN'
-     As destination operand being treated as `0(rn)'
+'@rN'
+     As destination operand being treated as '0(rn)'
 
-`0(rN)'
-     As source operand being treated as `@rn'
+'0(rN)'
+     As source operand being treated as '@rn'
 
-`jCOND +N'
+'jCOND +N'
      Skips next N bytes followed by jump instruction and equivalent to
-     `jCOND $+N+2'
-
+     'jCOND $+N+2'
 
    Also, there are some instructions, which cannot be found in other
 assemblers.  These are branch instructions, which has different opcodes
 upon jump distance.  They all got PC relative addressing mode.
 
-`beq label'
-     A polymorph instruction which is `jeq label' in case if jump
-     distance within allowed range for cpu's jump instruction. If not,
+'beq label'
+     A polymorph instruction which is 'jeq label' in case if jump
+     distance within allowed range for cpu's jump instruction.  If not,
      this unrolls into a sequence of
             jne $+6
             br  label
 
-`bne label'
-     A polymorph instruction which is `jne label' or `jeq +4; br label'
+'bne label'
+     A polymorph instruction which is 'jne label' or 'jeq +4; br label'
 
-`blt label'
-     A polymorph instruction which is `jl label' or `jge +4; br label'
+'blt label'
+     A polymorph instruction which is 'jl label' or 'jge +4; br label'
 
-`bltn label'
-     A polymorph instruction which is `jn label' or `jn +2; jmp +4; br
+'bltn label'
+     A polymorph instruction which is 'jn label' or 'jn +2; jmp +4; br
      label'
 
-`bltu label'
-     A polymorph instruction which is `jlo label' or `jhs +2; br label'
+'bltu label'
+     A polymorph instruction which is 'jlo label' or 'jhs +2; br label'
 
-`bge label'
-     A polymorph instruction which is `jge label' or `jl +4; br label'
+'bge label'
+     A polymorph instruction which is 'jge label' or 'jl +4; br label'
 
-`bgeu label'
-     A polymorph instruction which is `jhs label' or `jlo +4; br label'
+'bgeu label'
+     A polymorph instruction which is 'jhs label' or 'jlo +4; br label'
 
-`bgt label'
-     A polymorph instruction which is `jeq +2; jge label' or `jeq +6;
-     jl  +4; br label'
+'bgt label'
+     A polymorph instruction which is 'jeq +2; jge label' or 'jeq +6; jl
+     +4; br label'
 
-`bgtu label'
-     A polymorph instruction which is `jeq +2; jhs label' or `jeq +6;
+'bgtu label'
+     A polymorph instruction which is 'jeq +2; jhs label' or 'jeq +6;
      jlo +4; br label'
 
-`bleu label'
-     A polymorph instruction which is `jeq label; jlo label' or `jeq
-     +2; jhs +4; br label'
+'bleu label'
+     A polymorph instruction which is 'jeq label; jlo label' or 'jeq +2;
+     jhs +4; br label'
 
-`ble label'
-     A polymorph instruction which is `jeq label; jl  label' or `jeq
-     +2; jge +4; br label'
+'ble label'
+     A polymorph instruction which is 'jeq label; jl label' or 'jeq +2;
+     jge +4; br label'
 
-`jump label'
-     A polymorph instruction which is `jmp label' or `br label'
+'jump label'
+     A polymorph instruction which is 'jmp label' or 'br label'
 
 
 File: as.info,  Node: MSP430 Floating Point,  Next: MSP430 Directives,  Prev: MSP430 Syntax,  Up: MSP430-Dependent
@@ -14490,37 +14401,40 @@ File: as.info,  Node: MSP430 Directives,  Next: MSP430 Opcodes,  Prev: MSP430 Fl
 9.29.4 MSP 430 Machine Directives
 ---------------------------------
 
-`.file'
+'.file'
      This directive is ignored; it is accepted for compatibility with
      other MSP 430 assemblers.
 
-          _Warning:_ in other versions of the GNU assembler, `.file' is
-          used for the directive called `.app-file' in the MSP 430
+          _Warning:_ in other versions of the GNU assembler, '.file' is
+          used for the directive called '.app-file' in the MSP 430
           support.
 
-`.line'
+'.line'
      This directive is ignored; it is accepted for compatibility with
      other MSP 430 assemblers.
 
-`.arch'
-     Currently this directive is ignored; it is accepted for
-     compatibility with other MSP 430 assemblers.
+'.arch'
+     Sets the target microcontroller in the same way as the '-mmcu'
+     command line option.
+
+'.cpu'
+     Sets the target architecture in the same way as the '-mcpu' command
+     line option.
 
-`.profiler'
+'.profiler'
      This directive instructs assembler to add new profile entry to the
      object file.
 
-
 
 File: as.info,  Node: MSP430 Opcodes,  Next: MSP430 Profiling Capability,  Prev: MSP430 Directives,  Up: MSP430-Dependent
 
 9.29.5 Opcodes
 --------------
 
-`as' implements all the standard MSP 430 opcodes.  No additional
+'as' implements all the standard MSP 430 opcodes.  No additional
 pseudo-instructions are needed on this family.
 
-   For information on the 430 machine instruction set, see `MSP430
+   For information on the 430 machine instruction set, see 'MSP430
 User's Manual, document slau049d', Texas Instrument, Inc.
 
 
@@ -14534,75 +14448,58 @@ target.  Even more - jtag hardware facility does not perform any
 profiling functions.  However we've got gdb's built-in simulator where
 we can do anything.
 
-   We define new section `.profiler' which holds all profiling
-information.  We define new pseudo operation `.profiler' which will
-instruct assembler to add new profile entry to the object file. Profile
+   We define new section '.profiler' which holds all profiling
+information.  We define new pseudo operation '.profiler' which will
+instruct assembler to add new profile entry to the object file.  Profile
 should take place at the present address.
 
    Pseudo operation format:
 
-   `.profiler flags,function_to_profile [, cycle_corrector, extra]'
+   '.profiler flags,function_to_profile [, cycle_corrector, extra]'
 
    where:
 
-          `flags' is a combination of the following characters:
+          'flags' is a combination of the following characters:
 
-    `s'
+     's'
           function entry
-
-    `x'
+     'x'
           function exit
-
-    `i'
+     'i'
           function is in init section
-
-    `f'
+     'f'
           function is in fini section
-
-    `l'
+     'l'
           library call
-
-    `c'
+     'c'
           libc standard call
-
-    `d'
+     'd'
           stack value demand
-
-    `I'
+     'I'
           interrupt service routine
-
-    `P'
+     'P'
           prologue start
-
-    `p'
+     'p'
           prologue end
-
-    `E'
+     'E'
           epilogue start
-
-    `e'
+     'e'
           epilogue end
-
-    `j'
+     'j'
           long jump / sjlj unwind
-
-    `a'
+     'a'
           an arbitrary code fragment
-
-    `t'
+     't'
           extra parameter saved (a constant value like frame size)
 
-`function_to_profile'
+'function_to_profile'
      a function address
-
-`cycle_corrector'
+'cycle_corrector'
      a value which should be added to the cycle counter, zero if
      omitted.
-
-`extra'
+'extra'
      any extra parameter, zero if omitted.
 
-
    For example:
      .global fxx
      .type fxx,@function
@@ -14648,30 +14545,28 @@ File: as.info,  Node: Nios II Options,  Next: Nios II Syntax,  Up: NiosII-Depend
 9.30.1 Options
 --------------
 
-`-relax-section'
-     Replace identified out-of-range branches with PC-relative `jmp'
+'-relax-section'
+     Replace identified out-of-range branches with PC-relative 'jmp'
      sequences when possible.  The generated code sequences are suitable
      for use in position-independent code, but there is a practical
      limit on the extended branch range because of the length of the
      sequences.  This option is the default.
 
-`-relax-all'
-     Replace branch instructions not determinable to be in range and
-     all call instructions with `jmp' and `callr' sequences
-     (respectively).  This option generates absolute relocations
-     against the target symbols and is not appropriate for
-     position-independent code.
+'-relax-all'
+     Replace branch instructions not determinable to be in range and all
+     call instructions with 'jmp' and 'callr' sequences (respectively).
+     This option generates absolute relocations against the target
+     symbols and is not appropriate for position-independent code.
 
-`-no-relax'
+'-no-relax'
      Do not replace any branches or calls.
 
-`-EB'
+'-EB'
      Generate big-endian output.
 
-`-EL'
+'-EL'
      Generate little-endian output.  This is the default.
 
-
 
 File: as.info,  Node: Nios II Syntax,  Next: Nios II Relocations,  Prev: Nios II Options,  Up: NiosII-Dependent
 
@@ -14688,7 +14583,7 @@ File: as.info,  Node: Nios II Chars,  Up: Nios II Syntax
 9.30.2.1 Special Characters
 ...........................
 
-`#' is the line comment character.  `;' is the line separator character.
+'#' is the line comment character.  ';' is the line separator character.
 
 
 File: as.info,  Node: Nios II Relocations,  Next: Nios II Directives,  Prev: Nios II Syntax,  Up: NiosII-Dependent
@@ -14696,30 +14591,30 @@ File: as.info,  Node: Nios II Relocations,  Next: Nios II Directives,  Prev: Nio
 9.30.3 Nios II Machine Relocations
 ----------------------------------
 
-`%hiadj(EXPRESSION)'
-     Extract the upper 16 bits of EXPRESSION and add one if the 15th
-     bit is set.
+'%hiadj(EXPRESSION)'
+     Extract the upper 16 bits of EXPRESSION and add one if the 15th bit
+     is set.
 
-     The value of `%hiadj(EXPRESSION)' is:
+     The value of '%hiadj(EXPRESSION)' is:
           ((EXPRESSION >> 16) & 0xffff) + ((EXPRESSION >> 15) & 0x01)
 
-     The `%hiadj' relocation is intended to be used with the `addi',
-     `ld' or `st' instructions along with a `%lo', in order to load a
+     The '%hiadj' relocation is intended to be used with the 'addi',
+     'ld' or 'st' instructions along with a '%lo', in order to load a
      32-bit constant.
 
           movhi r2, %hiadj(symbol)
           addi r2, r2, %lo(symbol)
 
-`%hi(EXPRESSION)'
+'%hi(EXPRESSION)'
      Extract the upper 16 bits of EXPRESSION.
 
-`%lo(EXPRESSION)'
+'%lo(EXPRESSION)'
      Extract the lower 16 bits of EXPRESSION.
 
-`%gprel(EXPRESSION)'
-     Subtract the value of the symbol `_gp' from EXPRESSION.
+'%gprel(EXPRESSION)'
+     Subtract the value of the symbol '_gp' from EXPRESSION.
 
-     The intention of the `%gprel' relocation is to have a fast small
+     The intention of the '%gprel' relocation is to have a fast small
      area of memory which only takes a 16-bit immediate to access.
 
           	.section .sdata
@@ -14728,18 +14623,19 @@ File: as.info,  Node: Nios II Relocations,  Next: Nios II Directives,  Prev: Nio
           	.section .text
           	ldw r4, %gprel(fastint)(gp)
 
-`%call(EXPRESSION)'
-`%got(EXPRESSION)'
-`%gotoff(EXPRESSION)'
-`%gotoff_lo(EXPRESSION)'
-`%gotoff_hiadj(EXPRESSION)'
-`%tls_gd(EXPRESSION)'
-`%tls_ie(EXPRESSION)'
-`%tls_le(EXPRESSION)'
-`%tls_ldm(EXPRESSION)'
-`%tls_ldo(EXPRESSION)'
+'%call(EXPRESSION)'
+'%got(EXPRESSION)'
+'%gotoff(EXPRESSION)'
+'%gotoff_lo(EXPRESSION)'
+'%gotoff_hiadj(EXPRESSION)'
+'%tls_gd(EXPRESSION)'
+'%tls_ie(EXPRESSION)'
+'%tls_le(EXPRESSION)'
+'%tls_ldm(EXPRESSION)'
+'%tls_ldo(EXPRESSION)'
+
      These relocations support the ABI for Linux Systems documented in
-     the `Nios II Processor Reference Handbook'.
+     the 'Nios II Processor Reference Handbook'.
 
 
 File: as.info,  Node: Nios II Directives,  Next: Nios II Opcodes,  Prev: Nios II Relocations,  Up: NiosII-Dependent
@@ -14747,60 +14643,59 @@ File: as.info,  Node: Nios II Directives,  Next: Nios II Opcodes,  Prev: Nios II
 9.30.4 Nios II Machine Directives
 ---------------------------------
 
-`.align EXPRESSION [, EXPRESSION]'
-     This is the generic `.align' directive, however this aligns to a
+'.align EXPRESSION [, EXPRESSION]'
+     This is the generic '.align' directive, however this aligns to a
      power of two.
 
-`.half EXPRESSION'
+'.half EXPRESSION'
      Create an aligned constant 2 bytes in size.
 
-`.word EXPRESSION'
+'.word EXPRESSION'
      Create an aligned constant 4 bytes in size.
 
-`.dword EXPRESSION'
+'.dword EXPRESSION'
      Create an aligned constant 8 bytes in size.
 
-`.2byte EXPRESSION'
+'.2byte EXPRESSION'
      Create an unaligned constant 2 bytes in size.
 
-`.4byte EXPRESSION'
+'.4byte EXPRESSION'
      Create an unaligned constant 4 bytes in size.
 
-`.8byte EXPRESSION'
+'.8byte EXPRESSION'
      Create an unaligned constant 8 bytes in size.
 
-`.16byte EXPRESSION'
+'.16byte EXPRESSION'
      Create an unaligned constant 16 bytes in size.
 
-`.set noat'
-     Allows assembly code to use `at' register without warning.  Macro
+'.set noat'
+     Allows assembly code to use 'at' register without warning.  Macro
      or relaxation expansions generate warnings.
 
-`.set at'
-     Assembly code using `at' register generates warnings, and macro
+'.set at'
+     Assembly code using 'at' register generates warnings, and macro
      expansion and relaxation are enabled.
 
-`.set nobreak'
-     Allows assembly code to use `ba' and `bt' registers without
+'.set nobreak'
+     Allows assembly code to use 'ba' and 'bt' registers without
      warning.
 
-`.set break'
-     Turns warnings back on for using `ba' and `bt' registers.
+'.set break'
+     Turns warnings back on for using 'ba' and 'bt' registers.
 
-`.set norelax'
+'.set norelax'
      Do not replace any branches or calls.
 
-`.set relaxsection'
-     Replace identified out-of-range branches with `jmp' sequences
+'.set relaxsection'
+     Replace identified out-of-range branches with 'jmp' sequences
      (default).
 
-`.set relaxsection'
-     Replace all branch and call instructions with `jmp' and `callr'
+'.set relaxsection'
+     Replace all branch and call instructions with 'jmp' and 'callr'
      sequences.
 
-`.set ...'
-     All other `.set' are the normal use.
-
+'.set ...'
+     All other '.set' are the normal use.
 
 
 File: as.info,  Node: Nios II Opcodes,  Prev: Nios II Directives,  Up: NiosII-Dependent
@@ -14808,12 +14703,12 @@ File: as.info,  Node: Nios II Opcodes,  Prev: Nios II Directives,  Up: NiosII-De
 9.30.5 Opcodes
 --------------
 
-`as' implements all the standard Nios II opcodes documented in the
-`Nios II Processor Reference Handbook', including the assembler
+'as' implements all the standard Nios II opcodes documented in the 'Nios
+II Processor Reference Handbook', including the assembler
 pseudo-instructions.
 
 
-File: as.info,  Node: NS32K-Dependent,  Next: SH-Dependent,  Prev: NiosII-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: NS32K-Dependent,  Next: PDP-11-Dependent,  Prev: NiosII-Dependent,  Up: Machine Dependencies
 
 9.31 NS32K Dependent Features
 =============================
@@ -14838,23 +14733,23 @@ File: as.info,  Node: NS32K-Chars,  Up: NS32K Syntax
 9.31.1.1 Special Characters
 ...........................
 
-The presence of a `#' appearing anywhere on a line indicates the start
+The presence of a '#' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
    If Sequent compatibility has been configured into the assembler then
-the `|' character appearing as the first character on a line will also
+the '|' character appearing as the first character on a line will also
 indicate the start of a line comment.
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
-File: as.info,  Node: PDP-11-Dependent,  Next: PJ-Dependent,  Prev: SH64-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: PDP-11-Dependent,  Next: PJ-Dependent,  Prev: NS32K-Dependent,  Up: Machine Dependencies
 
 9.32 PDP-11 Dependent Features
 ==============================
@@ -14873,12 +14768,12 @@ File: as.info,  Node: PDP-11-Options,  Next: PDP-11-Pseudos,  Up: PDP-11-Depende
 9.32.1 Options
 --------------
 
-The PDP-11 version of `as' has a rich set of machine dependent options.
+The PDP-11 version of 'as' has a rich set of machine dependent options.
 
 9.32.1.1 Code Generation Options
 ................................
 
-`-mpic | -mno-pic'
+'-mpic | -mno-pic'
      Generate position-independent (or position-dependent) code.
 
      The default is to generate position-independent code.
@@ -14888,70 +14783,70 @@ The PDP-11 version of `as' has a rich set of machine dependent options.
 
 These options enables or disables the use of extensions over the base
 line instruction set as introduced by the first PDP-11 CPU: the KA11.
-Most options come in two variants: a `-m'EXTENSION that enables
-EXTENSION, and a `-mno-'EXTENSION that disables EXTENSION.
+Most options come in two variants: a '-m'EXTENSION that enables
+EXTENSION, and a '-mno-'EXTENSION that disables EXTENSION.
 
    The default is to enable all extensions.
 
-`-mall | -mall-extensions'
+'-mall | -mall-extensions'
      Enable all instruction set extensions.
 
-`-mno-extensions'
+'-mno-extensions'
      Disable all instruction set extensions.
 
-`-mcis | -mno-cis'
+'-mcis | -mno-cis'
      Enable (or disable) the use of the commercial instruction set,
-     which consists of these instructions: `ADDNI', `ADDN', `ADDPI',
-     `ADDP', `ASHNI', `ASHN', `ASHPI', `ASHP', `CMPCI', `CMPC',
-     `CMPNI', `CMPN', `CMPPI', `CMPP', `CVTLNI', `CVTLN', `CVTLPI',
-     `CVTLP', `CVTNLI', `CVTNL', `CVTNPI', `CVTNP', `CVTPLI', `CVTPL',
-     `CVTPNI', `CVTPN', `DIVPI', `DIVP', `L2DR', `L3DR', `LOCCI',
-     `LOCC', `MATCI', `MATC', `MOVCI', `MOVC', `MOVRCI', `MOVRC',
-     `MOVTCI', `MOVTC', `MULPI', `MULP', `SCANCI', `SCANC', `SKPCI',
-     `SKPC', `SPANCI', `SPANC', `SUBNI', `SUBN', `SUBPI', and `SUBP'.
-
-`-mcsm | -mno-csm'
-     Enable (or disable) the use of the `CSM' instruction.
-
-`-meis | -mno-eis'
+     which consists of these instructions: 'ADDNI', 'ADDN', 'ADDPI',
+     'ADDP', 'ASHNI', 'ASHN', 'ASHPI', 'ASHP', 'CMPCI', 'CMPC', 'CMPNI',
+     'CMPN', 'CMPPI', 'CMPP', 'CVTLNI', 'CVTLN', 'CVTLPI', 'CVTLP',
+     'CVTNLI', 'CVTNL', 'CVTNPI', 'CVTNP', 'CVTPLI', 'CVTPL', 'CVTPNI',
+     'CVTPN', 'DIVPI', 'DIVP', 'L2DR', 'L3DR', 'LOCCI', 'LOCC', 'MATCI',
+     'MATC', 'MOVCI', 'MOVC', 'MOVRCI', 'MOVRC', 'MOVTCI', 'MOVTC',
+     'MULPI', 'MULP', 'SCANCI', 'SCANC', 'SKPCI', 'SKPC', 'SPANCI',
+     'SPANC', 'SUBNI', 'SUBN', 'SUBPI', and 'SUBP'.
+
+'-mcsm | -mno-csm'
+     Enable (or disable) the use of the 'CSM' instruction.
+
+'-meis | -mno-eis'
      Enable (or disable) the use of the extended instruction set, which
-     consists of these instructions: `ASHC', `ASH', `DIV', `MARK',
-     `MUL', `RTT', `SOB' `SXT', and `XOR'.
+     consists of these instructions: 'ASHC', 'ASH', 'DIV', 'MARK',
+     'MUL', 'RTT', 'SOB' 'SXT', and 'XOR'.
 
-`-mfis | -mkev11'
-`-mno-fis | -mno-kev11'
+'-mfis | -mkev11'
+'-mno-fis | -mno-kev11'
      Enable (or disable) the use of the KEV11 floating-point
-     instructions: `FADD', `FDIV', `FMUL', and `FSUB'.
+     instructions: 'FADD', 'FDIV', 'FMUL', and 'FSUB'.
 
-`-mfpp | -mfpu | -mfp-11'
-`-mno-fpp | -mno-fpu | -mno-fp-11'
+'-mfpp | -mfpu | -mfp-11'
+'-mno-fpp | -mno-fpu | -mno-fp-11'
      Enable (or disable) the use of FP-11 floating-point instructions:
-     `ABSF', `ADDF', `CFCC', `CLRF', `CMPF', `DIVF', `LDCFF', `LDCIF',
-     `LDEXP', `LDF', `LDFPS', `MODF', `MULF', `NEGF', `SETD', `SETF',
-     `SETI', `SETL', `STCFF', `STCFI', `STEXP', `STF', `STFPS', `STST',
-     `SUBF', and `TSTF'.
+     'ABSF', 'ADDF', 'CFCC', 'CLRF', 'CMPF', 'DIVF', 'LDCFF', 'LDCIF',
+     'LDEXP', 'LDF', 'LDFPS', 'MODF', 'MULF', 'NEGF', 'SETD', 'SETF',
+     'SETI', 'SETL', 'STCFF', 'STCFI', 'STEXP', 'STF', 'STFPS', 'STST',
+     'SUBF', and 'TSTF'.
 
-`-mlimited-eis | -mno-limited-eis'
+'-mlimited-eis | -mno-limited-eis'
      Enable (or disable) the use of the limited extended instruction
-     set: `MARK', `RTT', `SOB', `SXT', and `XOR'.
+     set: 'MARK', 'RTT', 'SOB', 'SXT', and 'XOR'.
 
      The -mno-limited-eis options also implies -mno-eis.
 
-`-mmfpt | -mno-mfpt'
-     Enable (or disable) the use of the `MFPT' instruction.
+'-mmfpt | -mno-mfpt'
+     Enable (or disable) the use of the 'MFPT' instruction.
 
-`-mmultiproc | -mno-multiproc'
+'-mmultiproc | -mno-multiproc'
      Enable (or disable) the use of multiprocessor instructions:
-     `TSTSET' and `WRTLCK'.
+     'TSTSET' and 'WRTLCK'.
 
-`-mmxps | -mno-mxps'
-     Enable (or disable) the use of the `MFPS' and `MTPS' instructions.
+'-mmxps | -mno-mxps'
+     Enable (or disable) the use of the 'MFPS' and 'MTPS' instructions.
 
-`-mspl | -mno-spl'
-     Enable (or disable) the use of the `SPL' instruction.
+'-mspl | -mno-spl'
+     Enable (or disable) the use of the 'SPL' instruction.
 
-     Enable (or disable) the use of the microcode instructions: `LDUB',
-     `MED', and `XFC'.
+     Enable (or disable) the use of the microcode instructions: 'LDUB',
+     'MED', and 'XFC'.
 
 9.32.1.3 CPU Model Options
 ..........................
@@ -14959,47 +14854,47 @@ EXTENSION, and a `-mno-'EXTENSION that disables EXTENSION.
 These options enable the instruction set extensions supported by a
 particular CPU, and disables all other extensions.
 
-`-mka11'
-     KA11 CPU.  Base line instruction set only.
+'-mka11'
+     KA11 CPU. Base line instruction set only.
 
-`-mkb11'
-     KB11 CPU.  Enable extended instruction set and `SPL'.
+'-mkb11'
+     KB11 CPU. Enable extended instruction set and 'SPL'.
 
-`-mkd11a'
-     KD11-A CPU.  Enable limited extended instruction set.
+'-mkd11a'
+     KD11-A CPU. Enable limited extended instruction set.
 
-`-mkd11b'
-     KD11-B CPU.  Base line instruction set only.
+'-mkd11b'
+     KD11-B CPU. Base line instruction set only.
 
-`-mkd11d'
-     KD11-D CPU.  Base line instruction set only.
+'-mkd11d'
+     KD11-D CPU. Base line instruction set only.
 
-`-mkd11e'
-     KD11-E CPU.  Enable extended instruction set, `MFPS', and `MTPS'.
+'-mkd11e'
+     KD11-E CPU. Enable extended instruction set, 'MFPS', and 'MTPS'.
 
-`-mkd11f | -mkd11h | -mkd11q'
-     KD11-F, KD11-H, or KD11-Q CPU.  Enable limited extended
-     instruction set, `MFPS', and `MTPS'.
+'-mkd11f | -mkd11h | -mkd11q'
+     KD11-F, KD11-H, or KD11-Q CPU. Enable limited extended instruction
+     set, 'MFPS', and 'MTPS'.
 
-`-mkd11k'
-     KD11-K CPU.  Enable extended instruction set, `LDUB', `MED',
-     `MFPS', `MFPT', `MTPS', and `XFC'.
+'-mkd11k'
+     KD11-K CPU. Enable extended instruction set, 'LDUB', 'MED', 'MFPS',
+     'MFPT', 'MTPS', and 'XFC'.
 
-`-mkd11z'
-     KD11-Z CPU.  Enable extended instruction set, `CSM', `MFPS',
-     `MFPT', `MTPS', and `SPL'.
+'-mkd11z'
+     KD11-Z CPU. Enable extended instruction set, 'CSM', 'MFPS', 'MFPT',
+     'MTPS', and 'SPL'.
 
-`-mf11'
-     F11 CPU.  Enable extended instruction set, `MFPS', `MFPT', and
-     `MTPS'.
+'-mf11'
+     F11 CPU. Enable extended instruction set, 'MFPS', 'MFPT', and
+     'MTPS'.
 
-`-mj11'
-     J11 CPU.  Enable extended instruction set, `CSM', `MFPS', `MFPT',
-     `MTPS', `SPL', `TSTSET', and `WRTLCK'.
+'-mj11'
+     J11 CPU. Enable extended instruction set, 'CSM', 'MFPS', 'MFPT',
+     'MTPS', 'SPL', 'TSTSET', and 'WRTLCK'.
 
-`-mt11'
-     T11 CPU.  Enable limited extended instruction set, `MFPS', and
-     `MTPS'.
+'-mt11'
+     T11 CPU. Enable limited extended instruction set, 'MFPS', and
+     'MTPS'.
 
 9.32.1.4 Machine Model Options
 ..............................
@@ -15007,44 +14902,44 @@ particular CPU, and disables all other extensions.
 These options enable the instruction set extensions supported by a
 particular machine model, and disables all other extensions.
 
-`-m11/03'
-     Same as `-mkd11f'.
+'-m11/03'
+     Same as '-mkd11f'.
 
-`-m11/04'
-     Same as `-mkd11d'.
+'-m11/04'
+     Same as '-mkd11d'.
 
-`-m11/05 | -m11/10'
-     Same as `-mkd11b'.
+'-m11/05 | -m11/10'
+     Same as '-mkd11b'.
 
-`-m11/15 | -m11/20'
-     Same as `-mka11'.
+'-m11/15 | -m11/20'
+     Same as '-mka11'.
 
-`-m11/21'
-     Same as `-mt11'.
+'-m11/21'
+     Same as '-mt11'.
 
-`-m11/23 | -m11/24'
-     Same as `-mf11'.
+'-m11/23 | -m11/24'
+     Same as '-mf11'.
 
-`-m11/34'
-     Same as `-mkd11e'.
+'-m11/34'
+     Same as '-mkd11e'.
 
-`-m11/34a'
-     Ame as `-mkd11e' `-mfpp'.
+'-m11/34a'
+     Ame as '-mkd11e' '-mfpp'.
 
-`-m11/35 | -m11/40'
-     Same as `-mkd11a'.
+'-m11/35 | -m11/40'
+     Same as '-mkd11a'.
 
-`-m11/44'
-     Same as `-mkd11z'.
+'-m11/44'
+     Same as '-mkd11z'.
 
-`-m11/45 | -m11/50 | -m11/55 | -m11/70'
-     Same as `-mkb11'.
+'-m11/45 | -m11/50 | -m11/55 | -m11/70'
+     Same as '-mkb11'.
 
-`-m11/53 | -m11/73 | -m11/83 | -m11/84 | -m11/93 | -m11/94'
-     Same as `-mj11'.
+'-m11/53 | -m11/73 | -m11/83 | -m11/84 | -m11/93 | -m11/94'
+     Same as '-mj11'.
 
-`-m11/60'
-     Same as `-mkd11k'.
+'-m11/60'
+     Same as '-mkd11k'.
 
 
 File: as.info,  Node: PDP-11-Pseudos,  Next: PDP-11-Syntax,  Prev: PDP-11-Options,  Up: PDP-11-Dependent
@@ -15052,13 +14947,13 @@ File: as.info,  Node: PDP-11-Pseudos,  Next: PDP-11-Syntax,  Prev: PDP-11-Option
 9.32.2 Assembler Directives
 ---------------------------
 
-The PDP-11 version of `as' has a few machine dependent assembler
+The PDP-11 version of 'as' has a few machine dependent assembler
 directives.
 
-`.bss'
-     Switch to the `bss' section.
+'.bss'
+     Switch to the 'bss' section.
 
-`.even'
+'.even'
      Align the location counter to an even number.
 
 
@@ -15067,20 +14962,20 @@ File: as.info,  Node: PDP-11-Syntax,  Next: PDP-11-Mnemonics,  Prev: PDP-11-Pseu
 9.32.3 PDP-11 Assembly Language Syntax
 --------------------------------------
 
-`as' supports both DEC syntax and BSD syntax.  The only difference is
-that in DEC syntax, a `#' character is used to denote an immediate
-constants, while in BSD syntax the character for this purpose is `$'.
+'as' supports both DEC syntax and BSD syntax.  The only difference is
+that in DEC syntax, a '#' character is used to denote an immediate
+constants, while in BSD syntax the character for this purpose is '$'.
 
-   general-purpose registers are named `r0' through `r7'.  Mnemonic
-alternatives for `r6' and `r7' are `sp' and `pc', respectively.
+   general-purpose registers are named 'r0' through 'r7'.  Mnemonic
+alternatives for 'r6' and 'r7' are 'sp' and 'pc', respectively.
 
-   Floating-point registers are named `ac0' through `ac3', or
-alternatively `fr0' through `fr3'.
+   Floating-point registers are named 'ac0' through 'ac3', or
+alternatively 'fr0' through 'fr3'.
 
-   Comments are started with a `#' or a `/' character, and extend to
-the end of the line.  (FIXME: clash with immediates?)
+   Comments are started with a '#' or a '/' character, and extend to the
+end of the line.  (FIXME: clash with immediates?)
 
-   Multiple statements on the same line can be separated by the `;'
+   Multiple statements on the same line can be separated by the ';'
 character.
 
 
@@ -15091,20 +14986,20 @@ File: as.info,  Node: PDP-11-Mnemonics,  Next: PDP-11-Synthetic,  Prev: PDP-11-S
 
 Some instructions have alternative names.
 
-`BCC'
-     `BHIS'
+'BCC'
+     'BHIS'
 
-`BCS'
-     `BLO'
+'BCS'
+     'BLO'
 
-`L2DR'
-     `L2D'
+'L2DR'
+     'L2D'
 
-`L3DR'
-     `L3D'
+'L3DR'
+     'L3D'
 
-`SYS'
-     `TRAP'
+'SYS'
+     'TRAP'
 
 
 File: as.info,  Node: PDP-11-Synthetic,  Prev: PDP-11-Mnemonics,  Up: PDP-11-Dependent
@@ -15112,7 +15007,7 @@ File: as.info,  Node: PDP-11-Synthetic,  Prev: PDP-11-Mnemonics,  Up: PDP-11-Dep
 9.32.5 Synthetic Instructions
 -----------------------------
 
-The `JBR' and `J'CC synthetic instructions are not supported yet.
+The 'JBR' and 'J'CC synthetic instructions are not supported yet.
 
 
 File: as.info,  Node: PJ-Dependent,  Next: PPC-Dependent,  Prev: PDP-11-Dependent,  Up: Machine Dependencies
@@ -15131,12 +15026,12 @@ File: as.info,  Node: PJ Options,  Next: PJ Syntax,  Up: PJ-Dependent
 9.33.1 Options
 --------------
 
-`as' has two additional command-line options for the picoJava
+'as' has two additional command-line options for the picoJava
 architecture.
-`-ml'
+'-ml'
      This option selects little endian data output.
 
-`-mb'
+'-mb'
      This option selects big endian data output.
 
 
@@ -15155,15 +15050,15 @@ File: as.info,  Node: PJ-Chars,  Up: PJ Syntax
 9.33.2.1 Special Characters
 ...........................
 
-The presence of a `!' or `/' on a line indicates the start of a comment
+The presence of a '!' or '/' 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 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 to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -15192,148 +15087,147 @@ architecture reference manual.
 
    The following table lists all available PowerPC options.
 
-`-a32'
+'-a32'
      Generate ELF32 or XCOFF32.
 
-`-a64'
+'-a64'
      Generate ELF64 or XCOFF64.
 
-`-K PIC'
+'-K PIC'
      Set EF_PPC_RELOCATABLE_LIB in ELF flags.
 
-`-mpwrx | -mpwr2'
+'-mpwrx | -mpwr2'
      Generate code for POWER/2 (RIOS2).
 
-`-mpwr'
+'-mpwr'
      Generate code for POWER (RIOS1)
 
-`-m601'
+'-m601'
      Generate code for PowerPC 601.
 
-`-mppc, -mppc32, -m603, -m604'
+'-mppc, -mppc32, -m603, -m604'
      Generate code for PowerPC 603/604.
 
-`-m403, -m405'
+'-m403, -m405'
      Generate code for PowerPC 403/405.
 
-`-m440'
+'-m440'
      Generate code for PowerPC 440.  BookE and some 405 instructions.
 
-`-m464'
+'-m464'
      Generate code for PowerPC 464.
 
-`-m476'
+'-m476'
      Generate code for PowerPC 476.
 
-`-m7400, -m7410, -m7450, -m7455'
+'-m7400, -m7410, -m7450, -m7455'
      Generate code for PowerPC 7400/7410/7450/7455.
 
-`-m750cl'
+'-m750cl'
      Generate code for PowerPC 750CL.
 
-`-mppc64, -m620'
+'-mppc64, -m620'
      Generate code for PowerPC 620/625/630.
 
-`-me500, -me500x2'
+'-me500, -me500x2'
      Generate code for Motorola e500 core complex.
 
-`-me500mc'
+'-me500mc'
      Generate code for Freescale e500mc core complex.
 
-`-me500mc64'
+'-me500mc64'
      Generate code for Freescale e500mc64 core complex.
 
-`-me5500'
+'-me5500'
      Generate code for Freescale e5500 core complex.
 
-`-me6500'
+'-me6500'
      Generate code for Freescale e6500 core complex.
 
-`-mspe'
+'-mspe'
      Generate code for Motorola SPE instructions.
 
-`-mtitan'
+'-mtitan'
      Generate code for AppliedMicro Titan core complex.
 
-`-mppc64bridge'
+'-mppc64bridge'
      Generate code for PowerPC 64, including bridge insns.
 
-`-mbooke'
+'-mbooke'
      Generate code for 32-bit BookE.
 
-`-ma2'
+'-ma2'
      Generate code for A2 architecture.
 
-`-me300'
+'-me300'
      Generate code for PowerPC e300 family.
 
-`-maltivec'
+'-maltivec'
      Generate code for processors with AltiVec instructions.
 
-`-mvle'
+'-mvle'
      Generate code for Freescale PowerPC VLE instructions.
 
-`-mvsx'
+'-mvsx'
      Generate code for processors with Vector-Scalar (VSX) instructions.
 
-`-mhtm'
+'-mhtm'
      Generate code for processors with Hardware Transactional Memory
      instructions.
 
-`-mpower4, -mpwr4'
+'-mpower4, -mpwr4'
      Generate code for Power4 architecture.
 
-`-mpower5, -mpwr5, -mpwr5x'
+'-mpower5, -mpwr5, -mpwr5x'
      Generate code for Power5 architecture.
 
-`-mpower6, -mpwr6'
+'-mpower6, -mpwr6'
      Generate code for Power6 architecture.
 
-`-mpower7, -mpwr7'
+'-mpower7, -mpwr7'
      Generate code for Power7 architecture.
 
-`-mpower8, -mpwr8'
+'-mpower8, -mpwr8'
      Generate code for Power8 architecture.
 
-`-mcell'
-
-`-mcell'
+'-mcell'
+'-mcell'
      Generate code for Cell Broadband Engine architecture.
 
-`-mcom'
+'-mcom'
      Generate code Power/PowerPC common instructions.
 
-`-many'
+'-many'
      Generate code for any architecture (PWR/PWRX/PPC).
 
-`-mregnames'
+'-mregnames'
      Allow symbolic names for registers.
 
-`-mno-regnames'
+'-mno-regnames'
      Do not allow symbolic names for registers.
 
-`-mrelocatable'
+'-mrelocatable'
      Support for GCC's -mrelocatable option.
 
-`-mrelocatable-lib'
+'-mrelocatable-lib'
      Support for GCC's -mrelocatable-lib option.
 
-`-memb'
+'-memb'
      Set PPC_EMB bit in ELF flags.
 
-`-mlittle, -mlittle-endian, -le'
+'-mlittle, -mlittle-endian, -le'
      Generate code for a little endian machine.
 
-`-mbig, -mbig-endian, -be'
+'-mbig, -mbig-endian, -be'
      Generate code for a big endian machine.
 
-`-msolaris'
+'-msolaris'
      Generate code for Solaris.
 
-`-mno-solaris'
+'-mno-solaris'
      Do not generate code for Solaris.
 
-`-nops=COUNT'
+'-nops=COUNT'
      If an alignment directive inserts more than COUNT nops, put a
      branch at the beginning to skip execution of the nops.
 
@@ -15343,15 +15237,15 @@ File: as.info,  Node: PowerPC-Pseudo,  Next: PowerPC-Syntax,  Prev: PowerPC-Opts
 9.34.2 PowerPC Assembler Directives
 -----------------------------------
 
-A number of assembler directives are available for PowerPC.  The
+A number of assembler directives are available for PowerPC. The
 following table is far from complete.
 
-`.machine "string"'
+'.machine "string"'
      This directive allows you to change the machine for which code is
-     generated.  `"string"' may be any of the -m cpu selection options
-     (without the -m) enclosed in double quotes, `"push"', or `"pop"'.
-     `.machine "push"' saves the currently selected cpu, which may be
-     restored with `.machine "pop"'.
+     generated.  '"string"' may be any of the -m cpu selection options
+     (without the -m) enclosed in double quotes, '"push"', or '"pop"'.
+     '.machine "push"' saves the currently selected cpu, which may be
+     restored with '.machine "pop"'.
 
 
 File: as.info,  Node: PowerPC-Syntax,  Prev: PowerPC-Pseudo,  Up: PPC-Dependent
@@ -15369,19 +15263,19 @@ File: as.info,  Node: PowerPC-Chars,  Up: PowerPC-Syntax
 9.34.3.1 Special Characters
 ...........................
 
-The presence of a `#' on a line indicates the start of a comment that
+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 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::).
 
    If the assembler has been configured for the ppc-*-solaris* target
-then the `!' character also acts as a line comment character.  This can
-be disabled via the `-mno-solaris' command line option.
+then the '!' character also acts as a line comment character.  This can
+be disabled via the '-mno-solaris' command line option.
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -15403,7 +15297,12 @@ File: as.info,  Node: RL78-Opts,  Next: RL78-Modifiers,  Up: RL78-Dependent
 9.35.1 RL78 Options
 -------------------
 
-The Renesas RL78 port of `as' has no target-specific options.
+'relax'
+     Enable support for link-time relaxation.
+
+'mg10'
+     Mark the generated binary as targeting the G10 variant of the RL78
+     architecture.
 
 
 File: as.info,  Node: RL78-Modifiers,  Next: RL78-Directives,  Prev: RL78-Opts,  Up: RL78-Dependent
@@ -15414,26 +15313,28 @@ File: as.info,  Node: RL78-Modifiers,  Next: RL78-Directives,  Prev: RL78-Opts,
 The RL78 has three modifiers that adjust the relocations used by the
 linker:
 
-`%lo16()'
+'%lo16()'
+
      When loading a 20-bit (or wider) address into registers, this
      modifier selects the 16 least significant bits.
 
             movw ax,#%lo16(_sym)
 
-`%hi16()'
+'%hi16()'
+
      When loading a 20-bit (or wider) address into registers, this
      modifier selects the 16 most significant bits.
 
             movw ax,#%hi16(_sym)
 
-`%hi8()'
+'%hi8()'
+
      When loading a 20-bit (or wider) address into registers, this
-     modifier selects the 8 bits that would go into CS or ES (i.e. bits
+     modifier selects the 8 bits that would go into CS or ES (i.e.  bits
      23..16).
 
             mov es, #%hi8(_sym)
 
-
 
 File: as.info,  Node: RL78-Directives,  Next: RL78-Syntax,  Prev: RL78-Modifiers,  Up: RL78-Dependent
 
@@ -15442,21 +15343,20 @@ File: as.info,  Node: RL78-Directives,  Next: RL78-Syntax,  Prev: RL78-Modifiers
 
 In addition to the common directives, the RL78 adds these:
 
-`.double'
+'.double'
      Output a constant in "double" format, which is a 32-bit floating
      point value on RL78.
 
-`.bss'
+'.bss'
      Select the BSS section.
 
-`.3byte'
+'.3byte'
      Output a constant value in a three byte format.
 
-`.int'
-`.word'
+'.int'
+'.word'
      Output a constant value in a four byte format.
 
-
 
 File: as.info,  Node: RL78-Syntax,  Prev: RL78-Directives,  Up: RL78-Dependent
 
@@ -15473,15 +15373,15 @@ File: as.info,  Node: RL78-Chars,  Up: RL78-Syntax
 9.35.4.1 Special Characters
 ...........................
 
-The presence of a `;' appearing anywhere on a line indicates the start
+The presence of a ';' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The `|' character can be used to separate statements on the same
+   The '|' character can be used to separate statements on the same
 line.
 
 
@@ -15504,75 +15404,80 @@ File: as.info,  Node: RX-Opts,  Next: RX-Modifiers,  Up: RX-Dependent
 9.36.1 RX Options
 -----------------
 
-The Renesas RX port of `as' has a few target specfic command line
+The Renesas RX port of 'as' has a few target specfic command line
 options:
 
-`-m32bit-doubles'
+'-m32bit-doubles'
      This option controls the ABI and indicates to use a 32-bit float
-     ABI.  It has no effect on the assembled instructions, but it does
-     influence the behaviour of the `.double' pseudo-op.  This is the
+     ABI. It has no effect on the assembled instructions, but it does
+     influence the behaviour of the '.double' pseudo-op.  This is the
      default.
 
-`-m64bit-doubles'
+'-m64bit-doubles'
      This option controls the ABI and indicates to use a 64-bit float
-     ABI.  It has no effect on the assembled instructions, but it does
-     influence the behaviour of the `.double' pseudo-op.
+     ABI. It has no effect on the assembled instructions, but it does
+     influence the behaviour of the '.double' pseudo-op.
 
-`-mbig-endian'
+'-mbig-endian'
      This option controls the ABI and indicates to use a big-endian data
-     ABI.  It has no effect on the assembled instructions, but it does
-     influence the behaviour of the `.short', `.hword', `.int',
-     `.word', `.long', `.quad' and `.octa' pseudo-ops.
+     ABI. It has no effect on the assembled instructions, but it does
+     influence the behaviour of the '.short', '.hword', '.int', '.word',
+     '.long', '.quad' and '.octa' pseudo-ops.
 
-`-mlittle-endian'
+'-mlittle-endian'
      This option controls the ABI and indicates to use a little-endian
-     data ABI.  It has no effect on the assembled instructions, but it
-     does influence the behaviour of the `.short', `.hword', `.int',
-     `.word', `.long', `.quad' and `.octa' pseudo-ops.  This is the
+     data ABI. It has no effect on the assembled instructions, but it
+     does influence the behaviour of the '.short', '.hword', '.int',
+     '.word', '.long', '.quad' and '.octa' pseudo-ops.  This is the
      default.
 
-`-muse-conventional-section-names'
+'-muse-conventional-section-names'
      This option controls the default names given to the code (.text),
      initialised data (.data) and uninitialised data sections (.bss).
 
-`-muse-renesas-section-names'
+'-muse-renesas-section-names'
      This option controls the default names given to the code (.P),
      initialised data (.D_1) and uninitialised data sections (.B_1).
      This is the default.
 
-`-msmall-data-limit'
+'-msmall-data-limit'
      This option tells the assembler that the small data limit feature
      of the RX port of GCC is being used.  This results in the assembler
-     generating an undefined reference to a symbol called `__gp' for
-     use by the relocations that are needed to support the small data
-     limit feature.   This option is not enabled by default as it would
+     generating an undefined reference to a symbol called '__gp' for use
+     by the relocations that are needed to support the small data limit
+     feature.  This option is not enabled by default as it would
      otherwise pollute the symbol table.
 
-`-mpid'
+'-mpid'
      This option tells the assembler that the position independent data
      of the RX port of GCC is being used.  This results in the assembler
-     generating an undefined reference to a symbol called `__pid_base',
+     generating an undefined reference to a symbol called '__pid_base',
      and also setting the RX_PID flag bit in the e_flags field of the
      ELF header of the object file.
 
-`-mint-register=NUM'
+'-mint-register=NUM'
      This option tells the assembler how many registers have been
-     reserved for use by interrupt handlers.  This is needed in order
-     to compute the correct values for the `%gpreg' and `%pidreg' meta
+     reserved for use by interrupt handlers.  This is needed in order to
+     compute the correct values for the '%gpreg' and '%pidreg' meta
      registers.
 
-`-mgcc-abi'
+'-mgcc-abi'
      This option tells the assembler that the old GCC ABI is being used
      by the assembled code.  With this version of the ABI function
      arguments that are passed on the stack are aligned to a 32-bit
      boundary.
 
-`-mrx-abi'
+'-mrx-abi'
      This option tells the assembler that the official RX ABI is being
      used by the assembled code.  With this version of the ABI function
      arguments that are passed on the stack are aligned to their natural
      alignments.  This option is the default.
 
+'-mcpu=NAME'
+     This option tells the assembler the target CPU type.  Currently the
+     'rx200', 'rx600' and 'rx610' are recognised as valid cpu names.
+     Attempting to assemble an instruction not supported by the
+     indicated cpu type will result in an error message being generated.
 
 
 File: as.info,  Node: RX-Modifiers,  Next: RX-Directives,  Prev: RX-Opts,  Up: RX-Dependent
@@ -15585,10 +15490,10 @@ instruction operands.  The general syntax is the following:
 
      %gp(symbol)
 
-   The modifier returns the offset from the __GP symbol to the
-specified symbol as a 16-bit value.  The intent is that this offset
-should be used in a register+offset move instruction when generating
-references to small data.  Ie, like this:
+   The modifier returns the offset from the __GP symbol to the specified
+symbol as a 16-bit value.  The intent is that this offset should be used
+in a register+offset move instruction when generating references to
+small data.  Ie, like this:
 
        mov.W	 %gp(_foo)[%gpreg], r1
 
@@ -15596,13 +15501,12 @@ references to small data.  Ie, like this:
 to refer to registers whose values may not be known to the programmer.
 These meta register names are:
 
-`%gpreg'
+'%gpreg'
      The small data address register.
 
-`%pidreg'
+'%pidreg'
      The PID base address register.
 
-
    Both registers normally have the value r13, but this can change if
 some registers have been reserved for use by interrupt handlers or if
 both the small data limit and position independent data features are
@@ -15614,13 +15518,13 @@ File: as.info,  Node: RX-Directives,  Next: RX-Float,  Prev: RX-Modifiers,  Up:
 9.36.3 Assembler Directives
 ---------------------------
 
-The RX version of `as' has the following specific assembler directives:
+The RX version of 'as' has the following specific assembler directives:
 
-`.3byte'
+'.3byte'
      Inserts a 3-byte value into the output file at the current
      location.
 
-`.fetchalign'
+'.fetchalign'
      If the next opcode following this directive spans a fetch line
      boundary (8 byte boundary), the opcode is aligned to that boundary.
      If the next opcode does not span a fetch line, this directive has
@@ -15628,7 +15532,6 @@ The RX version of `as' has the following specific assembler directives:
      directive and the opcode; those labels are aligned as well.  Any
      inserted bytes due to alignment will form a NOP opcode.
 
-
 
 File: as.info,  Node: RX-Float,  Next: RX-Syntax,  Prev: RX-Directives,  Up: RX-Dependent
 
@@ -15637,17 +15540,15 @@ File: as.info,  Node: RX-Float,  Next: RX-Syntax,  Prev: RX-Directives,  Up: RX-
 
 The floating point formats generated by directives are these.
 
-`.float'
-     `Single' precision (32-bit) floating point constants.
-
-`.double'
-     If the `-m64bit-doubles' command line option has been specified
-     then then `double' directive generates `double' precision (64-bit)
-     floating point constants, otherwise it generates `single'
-     precision (32-bit) floating point constants.  To force the
-     generation of 64-bit floating point constants used the `dc.d'
-     directive instead.
+'.float'
+     'Single' precision (32-bit) floating point constants.
 
+'.double'
+     If the '-m64bit-doubles' command line option has been specified
+     then then 'double' directive generates 'double' precision (64-bit)
+     floating point constants, otherwise it generates 'single' precision
+     (32-bit) floating point constants.  To force the generation of
+     64-bit floating point constants used the 'dc.d' directive instead.
 
 
 File: as.info,  Node: RX-Syntax,  Prev: RX-Float,  Up: RX-Dependent
@@ -15665,15 +15566,15 @@ File: as.info,  Node: RX-Chars,  Up: RX-Syntax
 9.36.5.1 Special Characters
 ...........................
 
-The presence of a `;' appearing anywhere on a line indicates the start
+The presence of a ';' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The `!' character can be used to separate statements on the same
+   The '!' character can be used to separate statements on the same
 line.
 
 
@@ -15682,10 +15583,10 @@ File: as.info,  Node: S/390-Dependent,  Next: SCORE-Dependent,  Prev: RX-Depende
 9.37 IBM S/390 Dependent Features
 =================================
 
-   The s390 version of `as' supports two architectures modes and seven
-chip levels. The architecture modes are the Enterprise System
-Architecture (ESA) and the newer z/Architecture mode. The chip levels
-are g5, g6, z900, z990, z9-109, z9-ec, z10, z196, and zEC12.
+The s390 version of 'as' supports two architectures modes and seven chip
+levels.  The architecture modes are the Enterprise System Architecture
+(ESA) and the newer z/Architecture mode.  The chip levels are g5, g6,
+z900, z990, z9-109, z9-ec, z10, z196, and zEC12.
 
 * Menu:
 
@@ -15703,7 +15604,7 @@ File: as.info,  Node: s390 Options,  Next: s390 Characters,  Up: S/390-Dependent
 
 The following table lists all available s390 specific options:
 
-`-m31 | -m64'
+'-m31 | -m64'
      Select 31- or 64-bit ABI implying a word size of 32- or 64-bit.
 
      These options are only available with the ELF object file format,
@@ -15712,47 +15613,46 @@ The following table lists all available s390 specific options:
      configure script to enable 64-bit usage and use s390x as target
      platform).
 
-`-mesa | -mzarch'
+'-mesa | -mzarch'
      Select the architecture mode, either the Enterprise System
      Architecture (esa) mode or the z/Architecture mode (zarch).
 
      The 64-bit instructions are only available with the z/Architecture
-     mode.  The combination of `-m64' and `-mesa' results in a warning
+     mode.  The combination of '-m64' and '-mesa' results in a warning
      message.
 
-`-march=CPU'
-     This option specifies the target processor. The following
-     processor names are recognized: `g5', `g6', `z900', `z990',
-     `z9-109', `z9-ec', `z10' and `z196'.  Assembling an instruction
+'-march=CPU'
+     This option specifies the target processor.  The following
+     processor names are recognized: 'g5', 'g6', 'z900', 'z990',
+     'z9-109', 'z9-ec', 'z10' and 'z196'.  Assembling an instruction
      that is not supported on the target processor results in an error
-     message. Do not specify `g5' or `g6' with `-mzarch'.
+     message.  Do not specify 'g5' or 'g6' with '-mzarch'.
 
-`-mregnames'
+'-mregnames'
      Allow symbolic names for registers.
 
-`-mno-regnames'
+'-mno-regnames'
      Do not allow 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. This can indicate the misuse of
+     specified but evaluates to zero.  This can indicate the misuse of
      general purpose register 0 as an address register.
 
-
 
 File: as.info,  Node: s390 Characters,  Next: s390 Syntax,  Prev: s390 Options,  Up: S/390-Dependent
 
 9.37.2 Special Characters
 -------------------------
 
-`#' is the line comment character.
+'#' is the line comment character.
 
-   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.
 
 
@@ -15766,7 +15666,7 @@ Systems Architecture/390 Principles of Operation (SA22-7201) and the
 z/Architecture Principles of Operation (SA22-7832).
 
    Each instruction has two major parts, the instruction mnemonic and
-the instruction operands. The instruction format varies.
+the instruction operands.  The instruction format varies.
 
 * Menu:
 
@@ -15785,12 +15685,12 @@ File: as.info,  Node: s390 Register,  Next: s390 Mnemonics,  Up: s390 Syntax
 9.37.3.1 Register naming
 ........................
 
-The `as' recognizes a number of predefined symbols for the various
-processor registers. A register specification in one of the instruction
-formats is an unsigned integer between 0 and 15. The specific
+The 'as' recognizes a number of predefined symbols for the various
+processor registers.  A register specification in one of the instruction
+formats is an unsigned integer between 0 and 15.  The specific
 instruction and the position of the register in the instruction format
-denotes the type of the register. The register symbols are prefixed with
-`%':
+denotes the type of the register.  The register symbols are prefixed
+with '%':
 
      %rN   the 16 general purpose registers, 0 <= N <= 15
      %fN   the 16 floating point registers, 0 <= N <= 15
@@ -15808,32 +15708,32 @@ File: as.info,  Node: s390 Mnemonics,  Next: s390 Operands,  Prev: s390 Register
 All instructions documented in the Principles of Operation are supported
 with the mnemonic and order of operands as described.  The instruction
 mnemonic identifies the instruction format (*note s390 Formats::) and
-the specific operation code for the instruction.  For example, the `lr'
-mnemonic denotes the instruction format `RR' with the operation code
-`0x18'.
+the specific operation code for the instruction.  For example, the 'lr'
+mnemonic denotes the instruction format 'RR' with the operation code
+'0x18'.
 
    The definition of the various mnemonics follows a scheme, where the
 first character usually hint at the type of the instruction:
 
-     a          add instruction, for example `al' for add logical 32-bit
-     b          branch instruction, for example `bc' for branch on condition
-     c          compare or convert instruction, for example `cr' for compare
+     a          add instruction, for example 'al' for add logical 32-bit
+     b          branch instruction, for example 'bc' for branch on condition
+     c          compare or convert instruction, for example 'cr' for compare
                 register 32-bit
-     d          divide instruction, for example `dlr' devide logical register
+     d          divide instruction, for example 'dlr' devide logical register
                 64-bit to 32-bit
-     i          insert instruction, for example `ic' insert character
-     l          load instruction, for example `ltr' load and test register
-     mv         move instruction, for example `mvc' move character
-     m          multiply instruction, for example `mh' multiply halfword
-     n          and instruction, for example `ni' and immediate
-     o          or instruction, for example `oc' or character
+     i          insert instruction, for example 'ic' insert character
+     l          load instruction, for example 'ltr' load and test register
+     mv         move instruction, for example 'mvc' move character
+     m          multiply instruction, for example 'mh' multiply halfword
+     n          and instruction, for example 'ni' and immediate
+     o          or instruction, for example 'oc' or character
      sla, sll   shift left single instruction
      sra, srl   shift right single instruction
-     st         store instruction, for example `stm' store multiple
-     s          subtract instruction, for example `slr' subtract
+     st         store instruction, for example 'stm' store multiple
+     s          subtract instruction, for example 'slr' subtract
                 logical 32-bit
-     t          test or translate instruction, of example `tm' test under mask
-     x          exclusive or instruction, for example `xc' exclusive or
+     t          test or translate instruction, of example 'tm' test under mask
+     x          exclusive or instruction, for example 'xc' exclusive or
                 character
 
    Certain characters at the end of the mnemonic may describe a property
@@ -15850,13 +15750,13 @@ of the instruction:
      y   the instruction uses 20-bit displacements
 
    There are many exceptions to the scheme outlined in the above lists,
-in particular for the priviledged instructions. For non-priviledged
-instruction it works quite well, for example the instruction `clgfr' c:
-compare instruction, l: unsigned operands, g: 64-bit operands, f: 32-
-to 64-bit extension, r: register operands. The instruction compares an
+in particular for the priviledged instructions.  For non-priviledged
+instruction it works quite well, for example the instruction 'clgfr' c:
+compare instruction, l: unsigned operands, g: 64-bit operands, f: 32- to
+64-bit extension, r: register operands.  The instruction compares an
 64-bit value in a register with the zero extended 32-bit value from a
-second register.  For a complete list of all mnemonics see appendix B
-in the Principles of Operation.
+second register.  For a complete list of all mnemonics see appendix B in
+the Principles of Operation.
 
 
 File: as.info,  Node: s390 Operands,  Next: s390 Formats,  Prev: s390 Mnemonics,  Up: s390 Syntax
@@ -15868,68 +15768,60 @@ Instruction operands can be grouped into three classes, operands located
 in registers, immediate operands, and operands in storage.
 
    A register operand can be located in general, floating-point, access,
-or control register. The register is identified by a four-bit field.
+or control register.  The register is identified by a four-bit field.
 The field containing the register operand is called the R field.
 
    Immediate operands are contained within the instruction and can have
-8, 16 or 32 bits. The field containing the immediate operand is called
-the I field. Dependent on the instruction the I field is either signed
+8, 16 or 32 bits.  The field containing the immediate operand is called
+the I field.  Dependent on the instruction the I field is either signed
 or unsigned.
 
-   A storage operand consists of an address and a length. The address
+   A storage operand consists of an address and a length.  The address
 of a storage operands can be specified in any of these ways:
 
    * The content of a single general R
-
    * The sum of the content of a general register called the base
      register B plus the content of a displacement field D
-
    * The sum of the contents of two general registers called the index
      register X and the base register B plus the content of a
      displacement field
-
    * The sum of the current instruction address and a 32-bit signed
      immediate field multiplied by two.
 
    The length of a storage operand can be:
 
    * Implied by the instruction
-
    * Specified by a bitmask
-
    * Specified by a four-bit or eight-bit length field L
-
    * Specified by the content of a general register
 
    The notation for storage operand addresses formed from multiple
 fields is as follows:
 
-`Dn(Bn)'
+'Dn(Bn)'
      the address for operand number n is formed from the content of
      general register Bn called the base register and the displacement
      field Dn.
-
-`Dn(Xn,Bn)'
+'Dn(Xn,Bn)'
      the address for operand number n is formed from the content of
      general register Xn called the index register, general register Bn
      called the base register and the displacement field Dn.
-
-`Dn(Ln,Bn)'
+'Dn(Ln,Bn)'
      the address for operand number n is formed from the content of
      general regiser Bn called the base register and the displacement
      field Dn.  The length of the operand n is specified by the field
      Ln.
 
-   The base registers Bn and the index registers Xn of a storage
-operand can be skipped. If Bn and Xn are skipped, a zero will be stored
-to the operand field. The notation changes as follows:
+   The base registers Bn and the index registers Xn of a storage operand
+can be skipped.  If Bn and Xn are skipped, a zero will be stored to the
+operand field.  The notation changes as follows:
 
-     full notation        short notation
-     ------------------------------------------ 
-     Dn(0,Bn)             Dn(Bn)
-     Dn(0,0)              Dn
-     Dn(0)                Dn
-     Dn(Ln,0)             Dn(Ln)
+     full notation          short notation
+     ----------------------------------------------
+     Dn(0,Bn)               Dn(Bn)
+     Dn(0,0)                Dn
+     Dn(0)                  Dn
+     Dn(Ln,0)               Dn(Ln)
 
 
 File: as.info,  Node: s390 Formats,  Next: s390 Aliases,  Prev: s390 Operands,  Up: s390 Syntax
@@ -15938,9 +15830,9 @@ File: as.info,  Node: s390 Formats,  Next: s390 Aliases,  Prev: s390 Operands,
 ............................
 
 The Principles of Operation manuals lists 26 instruction formats where
-some of the formats have multiple variants. For the `.insn' pseudo
+some of the formats have multiple variants.  For the '.insn' pseudo
 directive the assembler recognizes some of the formats.  Typically, the
-most general variant of the instruction format is used by the `.insn'
+most general variant of the instruction format is used by the '.insn'
 directive.
 
    The following table lists the abbreviations used in the table of
@@ -15957,165 +15849,164 @@ instruction formats:
      Ux              Unsigned immediate for operand x.
 
    An instruction is two, four, or six bytes in length and must be
-aligned on a 2 byte boundary. The first two bits of the instruction
+aligned on a 2 byte boundary.  The first two bits of the instruction
 specify the length of the instruction, 00 indicates a two byte
 instruction, 01 and 10 indicates a four byte instruction, and 11
 indicates a six byte instruction.
 
    The following table lists the s390 instruction formats that are
-available with the `.insn' pseudo directive:
+available with the '.insn' pseudo directive:
 
-`E format'
+'E format'
      +-------------+
      |    OpCode   |
      +-------------+
      0            15
 
-`RI format: <insn> R1,I2'
+'RI format: <insn> R1,I2'
      +--------+----+----+------------------+
      | OpCode | R1 |OpCd|        I2        |
      +--------+----+----+------------------+
      0        8    12   16                31
 
-`RIE format: <insn> R1,R3,I2'
+'RIE format: <insn> R1,R3,I2'
      +--------+----+----+------------------+--------+--------+
      | OpCode | R1 | R3 |        I2        |////////| OpCode |
      +--------+----+----+------------------+--------+--------+
      0        8    12   16                 32       40      47
 
-`RIL format: <insn> R1,I2'
+'RIL format: <insn> R1,I2'
      +--------+----+----+------------------------------------+
      | OpCode | R1 |OpCd|                  I2                |
      +--------+----+----+------------------------------------+
      0        8    12   16                                  47
 
-`RILU format: <insn> R1,U2'
+'RILU format: <insn> R1,U2'
      +--------+----+----+------------------------------------+
      | OpCode | R1 |OpCd|                  U2                |
      +--------+----+----+------------------------------------+
      0        8    12   16                                  47
 
-`RIS format: <insn> R1,I2,M3,D4(B4)'
+'RIS format: <insn> R1,I2,M3,D4(B4)'
      +--------+----+----+----+-------------+--------+--------+
      | OpCode | R1 | M3 | B4 |     D4      |   I2   | Opcode |
      +--------+----+----+----+-------------+--------+--------+
      0        8    12   16   20            32       36      47
 
-`RR format: <insn> R1,R2'
+'RR format: <insn> R1,R2'
      +--------+----+----+
      | OpCode | R1 | R2 |
      +--------+----+----+
      0        8    12  15
 
-`RRE format: <insn> R1,R2'
+'RRE format: <insn> R1,R2'
      +------------------+--------+----+----+
      |      OpCode      |////////| R1 | R2 |
      +------------------+--------+----+----+
      0                  16       24   28  31
 
-`RRF format: <insn> R1,R2,R3,M4'
+'RRF format: <insn> R1,R2,R3,M4'
      +------------------+----+----+----+----+
      |      OpCode      | R3 | M4 | R1 | R2 |
      +------------------+----+----+----+----+
      0                  16   20   24   28  31
 
-`RRS format: <insn> R1,R2,M3,D4(B4)'
+'RRS format: <insn> R1,R2,M3,D4(B4)'
      +--------+----+----+----+-------------+----+----+--------+
      | OpCode | R1 | R3 | B4 |     D4      | M3 |////| OpCode |
      +--------+----+----+----+-------------+----+----+--------+
      0        8    12   16   20            32   36   40      47
 
-`RS format: <insn> R1,R3,D2(B2)'
+'RS format: <insn> R1,R3,D2(B2)'
      +--------+----+----+----+-------------+
      | OpCode | R1 | R3 | B2 |     D2      |
      +--------+----+----+----+-------------+
      0        8    12   16   20           31
 
-`RSE format: <insn> R1,R3,D2(B2)'
+'RSE format: <insn> R1,R3,D2(B2)'
      +--------+----+----+----+-------------+--------+--------+
      | OpCode | R1 | R3 | B2 |     D2      |////////| OpCode |
      +--------+----+----+----+-------------+--------+--------+
      0        8    12   16   20            32       40      47
 
-`RSI format: <insn> R1,R3,I2'
+'RSI format: <insn> R1,R3,I2'
      +--------+----+----+------------------------------------+
      | OpCode | R1 | R3 |                  I2                |
      +--------+----+----+------------------------------------+
      0        8    12   16                                  47
 
-`RSY format: <insn> R1,R3,D2(B2)'
+'RSY format: <insn> R1,R3,D2(B2)'
      +--------+----+----+----+-------------+--------+--------+
      | OpCode | R1 | R3 | B2 |    DL2      |  DH2   | OpCode |
      +--------+----+----+----+-------------+--------+--------+
      0        8    12   16   20            32       40      47
 
-`RX format: <insn> R1,D2(X2,B2)'
+'RX format: <insn> R1,D2(X2,B2)'
      +--------+----+----+----+-------------+
      | OpCode | R1 | X2 | B2 |     D2      |
      +--------+----+----+----+-------------+
      0        8    12   16   20           31
 
-`RXE format: <insn> R1,D2(X2,B2)'
+'RXE format: <insn> R1,D2(X2,B2)'
      +--------+----+----+----+-------------+--------+--------+
      | OpCode | R1 | X2 | B2 |     D2      |////////| OpCode |
      +--------+----+----+----+-------------+--------+--------+
      0        8    12   16   20            32       40      47
 
-`RXF format: <insn> R1,R3,D2(X2,B2)'
+'RXF format: <insn> R1,R3,D2(X2,B2)'
      +--------+----+----+----+-------------+----+---+--------+
      | OpCode | R3 | X2 | B2 |     D2      | R1 |///| OpCode |
      +--------+----+----+----+-------------+----+---+--------+
      0        8    12   16   20            32   36  40      47
 
-`RXY format: <insn> R1,D2(X2,B2)'
+'RXY format: <insn> R1,D2(X2,B2)'
      +--------+----+----+----+-------------+--------+--------+
      | OpCode | R1 | X2 | B2 |     DL2     |   DH2  | OpCode |
      +--------+----+----+----+-------------+--------+--------+
      0        8    12   16   20            32   36   40      47
 
-`S format: <insn> D2(B2)'
+'S format: <insn> D2(B2)'
      +------------------+----+-------------+
      |      OpCode      | B2 |     D2      |
      +------------------+----+-------------+
      0                  16   20           31
 
-`SI format: <insn> D1(B1),I2'
+'SI format: <insn> D1(B1),I2'
      +--------+---------+----+-------------+
      | OpCode |   I2    | B1 |     D1      |
      +--------+---------+----+-------------+
      0        8         16   20           31
 
-`SIY format: <insn> D1(B1),U2'
+'SIY format: <insn> D1(B1),U2'
      +--------+---------+----+-------------+--------+--------+
      | OpCode |   I2    | B1 |     DL1     |  DH1   | OpCode |
      +--------+---------+----+-------------+--------+--------+
      0        8         16   20            32   36   40      47
 
-`SIL format: <insn> D1(B1),I2'
+'SIL format: <insn> D1(B1),I2'
      +------------------+----+-------------+-----------------+
      |      OpCode      | B1 |      D1     |       I2        |
      +------------------+----+-------------+-----------------+
      0                  16   20            32               47
 
-`SS format: <insn> D1(R1,B1),D2(B3),R3'
+'SS format: <insn> D1(R1,B1),D2(B3),R3'
      +--------+----+----+----+-------------+----+------------+
      | OpCode | R1 | R3 | B1 |     D1      | B2 |     D2     |
      +--------+----+----+----+-------------+----+------------+
      0        8    12   16   20            32   36          47
 
-`SSE format: <insn> D1(B1),D2(B2)'
+'SSE format: <insn> D1(B1),D2(B2)'
      +------------------+----+-------------+----+------------+
      |      OpCode      | B1 |     D1      | B2 |     D2     |
      +------------------+----+-------------+----+------------+
      0        8    12   16   20            32   36           47
 
-`SSF format: <insn> D1(B1),D2(B2),R3'
+'SSF format: <insn> D1(B1),D2(B2),R3'
      +--------+----+----+----+-------------+----+------------+
      | OpCode | R3 |OpCd| B1 |     D1      | B2 |     D2     |
      +--------+----+----+----+-------------+----+------------+
      0        8    12   16   20            32   36           47
 
-
    For the complete list of all instruction format variants see the
 Principles of Operation manuals.
 
@@ -16126,23 +16017,23 @@ File: as.info,  Node: s390 Aliases,  Next: s390 Operand Modifier,  Prev: s390 Fo
 ............................
 
 A specific bit pattern can have multiple mnemonics, for example the bit
-pattern `0xa7000000' has the mnemonics `tmh' and `tmlh'. In addition,
-there are a number of mnemonics recognized by `as' that are not present
-in the Principles of Operation.  These are the short forms of the
-branch instructions, where the condition code mask operand is encoded
-in the mnemonic. This is relevant for the branch instructions, the
-compare and branch instructions, and the compare and trap instructions.
+pattern '0xa7000000' has the mnemonics 'tmh' and 'tmlh'.  In addition,
+there are a number of mnemonics recognized by 'as' that are not present
+in the Principles of Operation.  These are the short forms of the branch
+instructions, where the condition code mask operand is encoded in the
+mnemonic.  This is relevant for the branch instructions, the compare and
+branch instructions, and the compare and trap instructions.
 
    For the branch instructions there are 20 condition code strings that
 can be used as part of the mnemonic in place of a mask operand in the
 instruction format:
 
-     instruction          short form
-     ------------------------------------------ 
-     bcr   M1,R2          b<m>r  R2
-     bc    M1,D2(X2,B2)   b<m>   D2(X2,B2)
-     brc   M1,I2          j<m>   I2
-     brcl  M1,I2          jg<m>  I2
+     instruction            short form
+     ----------------------------------------------
+     bcr   M1,R2            b<m>r  R2
+     bc    M1,D2(X2,B2)     b<m>   D2(X2,B2)
+     brc   M1,I2            j<m>   I2
+     brcl  M1,I2            jg<m>  I2
 
    In the mnemonic for a branch instruction the condition code string
 <m> can be any of the following:
@@ -16172,32 +16063,32 @@ instruction format:
 are 12 condition code strings that can be used as part of the mnemonic
 in place of a mask operand in the instruction format:
 
-     instruction                 short form
-     -------------------------------------------------------- 
-     crb    R1,R2,M3,D4(B4)      crb<m>    R1,R2,D4(B4)
-     cgrb   R1,R2,M3,D4(B4)      cgrb<m>   R1,R2,D4(B4)
-     crj    R1,R2,M3,I4          crj<m>    R1,R2,I4
-     cgrj   R1,R2,M3,I4          cgrj<m>   R1,R2,I4
-     cib    R1,I2,M3,D4(B4)      cib<m>    R1,I2,D4(B4)
-     cgib   R1,I2,M3,D4(B4)      cgib<m>   R1,I2,D4(B4)
-     cij    R1,I2,M3,I4          cij<m>    R1,I2,I4
-     cgij   R1,I2,M3,I4          cgij<m>   R1,I2,I4
-     crt    R1,R2,M3             crt<m>    R1,R2
-     cgrt   R1,R2,M3             cgrt<m>   R1,R2
-     cit    R1,I2,M3             cit<m>    R1,I2
-     cgit   R1,I2,M3             cgit<m>   R1,I2
-     clrb   R1,R2,M3,D4(B4)      clrb<m>   R1,R2,D4(B4)
-     clgrb  R1,R2,M3,D4(B4)      clgrb<m>  R1,R2,D4(B4)
-     clrj   R1,R2,M3,I4          clrj<m>   R1,R2,I4
-     clgrj  R1,R2,M3,I4          clgrj<m>  R1,R2,I4
-     clib   R1,I2,M3,D4(B4)      clib<m>   R1,I2,D4(B4)
-     clgib  R1,I2,M3,D4(B4)      clgib<m>  R1,I2,D4(B4)
-     clij   R1,I2,M3,I4          clij<m>   R1,I2,I4
-     clgij  R1,I2,M3,I4          clgij<m>  R1,I2,I4
-     clrt   R1,R2,M3             clrt<m>   R1,R2
-     clgrt  R1,R2,M3             clgrt<m>  R1,R2
-     clfit  R1,I2,M3             clfit<m>  R1,I2
-     clgit  R1,I2,M3             clgit<m>  R1,I2
+     instruction                   short form
+     ------------------------------------------------------------
+     crb    R1,R2,M3,D4(B4)        crb<m>    R1,R2,D4(B4)
+     cgrb   R1,R2,M3,D4(B4)        cgrb<m>   R1,R2,D4(B4)
+     crj    R1,R2,M3,I4            crj<m>    R1,R2,I4
+     cgrj   R1,R2,M3,I4            cgrj<m>   R1,R2,I4
+     cib    R1,I2,M3,D4(B4)        cib<m>    R1,I2,D4(B4)
+     cgib   R1,I2,M3,D4(B4)        cgib<m>   R1,I2,D4(B4)
+     cij    R1,I2,M3,I4            cij<m>    R1,I2,I4
+     cgij   R1,I2,M3,I4            cgij<m>   R1,I2,I4
+     crt    R1,R2,M3               crt<m>    R1,R2
+     cgrt   R1,R2,M3               cgrt<m>   R1,R2
+     cit    R1,I2,M3               cit<m>    R1,I2
+     cgit   R1,I2,M3               cgit<m>   R1,I2
+     clrb   R1,R2,M3,D4(B4)        clrb<m>   R1,R2,D4(B4)
+     clgrb  R1,R2,M3,D4(B4)        clgrb<m>  R1,R2,D4(B4)
+     clrj   R1,R2,M3,I4            clrj<m>   R1,R2,I4
+     clgrj  R1,R2,M3,I4            clgrj<m>  R1,R2,I4
+     clib   R1,I2,M3,D4(B4)        clib<m>   R1,I2,D4(B4)
+     clgib  R1,I2,M3,D4(B4)        clgib<m>  R1,I2,D4(B4)
+     clij   R1,I2,M3,I4            clij<m>   R1,I2,I4
+     clgij  R1,I2,M3,I4            clgij<m>  R1,I2,I4
+     clrt   R1,R2,M3               clrt<m>   R1,R2
+     clgrt  R1,R2,M3               clgrt<m>  R1,R2
+     clfit  R1,I2,M3               clfit<m>  R1,I2
+     clgit  R1,I2,M3               clgit<m>  R1,I2
 
    In the mnemonic for a compare and branch and compare and trap
 instruction the condition code string <m> can be any of the following:
@@ -16224,76 +16115,69 @@ File: as.info,  Node: s390 Operand Modifier,  Next: s390 Instruction Marker,  Pr
 If a symbol modifier is attached to a symbol in an expression for an
 instruction operand field, the symbol term is replaced with a reference
 to an object in the global offset table (GOT) or the procedure linkage
-table (PLT). The following expressions are allowed: `symbol@modifier +
-constant', `symbol@modifier + label + constant', and `symbol@modifier -
-label + constant'.  The term `symbol' is the symbol that will be
-entered into the GOT or PLT, `label' is a local label, and `constant'
-is an arbitrary expression that the assembler can evaluate to a
-constant value.
-
-   The term `(symbol + constant1)@modifier +/- label + constant2' is
-also accepted but a warning message is printed and the term is
-converted to `symbol@modifier +/- label + constant1 + constant2'.
-
-`@got'
-`@got12'
+table (PLT). The following expressions are allowed: 'symbol@modifier +
+constant', 'symbol@modifier + label + constant', and 'symbol@modifier -
+label + constant'.  The term 'symbol' is the symbol that will be entered
+into the GOT or PLT, 'label' is a local label, and 'constant' is an
+arbitrary expression that the assembler can evaluate to a constant
+value.
+
+   The term '(symbol + constant1)@modifier +/- label + constant2' is
+also accepted but a warning message is printed and the term is converted
+to 'symbol@modifier +/- label + constant1 + constant2'.
+
+'@got'
+'@got12'
      The @got modifier can be used for displacement fields, 16-bit
-     immediate fields and 32-bit pc-relative immediate fields. The
-     @got12 modifier is synonym to @got. The symbol is added to the
-     GOT. For displacement fields and 16-bit immediate fields the
-     symbol term is replaced with the offset from the start of the GOT
-     to the GOT slot for the symbol.  For a 32-bit pc-relative field
-     the pc-relative offset to the GOT slot from the current
-     instruction address is used.
-
-`@gotent'
+     immediate fields and 32-bit pc-relative immediate fields.  The
+     @got12 modifier is synonym to @got.  The symbol is added to the
+     GOT. For displacement fields and 16-bit immediate fields the symbol
+     term is replaced with the offset from the start of the GOT to the
+     GOT slot for the symbol.  For a 32-bit pc-relative field the
+     pc-relative offset to the GOT slot from the current instruction
+     address is used.
+'@gotent'
      The @gotent modifier can be used for 32-bit pc-relative immediate
      fields.  The symbol is added to the GOT and the symbol term is
      replaced with the pc-relative offset from the current instruction
      to the GOT slot for the symbol.
-
-`@gotoff'
-     The @gotoff modifier can be used for 16-bit immediate fields. The
+'@gotoff'
+     The @gotoff modifier can be used for 16-bit immediate fields.  The
      symbol term is replaced with the offset from the start of the GOT
      to the address of the symbol.
-
-`@gotplt'
+'@gotplt'
      The @gotplt modifier can be used for displacement fields, 16-bit
-     immediate fields, and 32-bit pc-relative immediate fields. A
+     immediate fields, and 32-bit pc-relative immediate fields.  A
      procedure linkage table entry is generated for the symbol and a
      jump slot for the symbol is added to the GOT. For displacement
-     fields and 16-bit immediate fields the symbol term is replaced
-     with the offset from the start of the GOT to the jump slot for the
-     symbol. For a 32-bit pc-relative field the pc-relative offset to
+     fields and 16-bit immediate fields the symbol term is replaced with
+     the offset from the start of the GOT to the jump slot for the
+     symbol.  For a 32-bit pc-relative field the pc-relative offset to
      the jump slot from the current instruction address is used.
-
-`@plt'
+'@plt'
      The @plt modifier can be used for 16-bit and 32-bit pc-relative
-     immediate fields. A procedure linkage table entry is generated for
+     immediate fields.  A procedure linkage table entry is generated for
      the symbol.  The symbol term is replaced with the relative offset
      from the current instruction to the PLT entry for the symbol.
-
-`@pltoff'
-     The @pltoff modifier can be used for 16-bit immediate fields. The
+'@pltoff'
+     The @pltoff modifier can be used for 16-bit immediate fields.  The
      symbol term is replaced with the offset from the start of the PLT
      to the address of the symbol.
-
-`@gotntpoff'
-     The @gotntpoff modifier can be used for displacement fields. The
+'@gotntpoff'
+     The @gotntpoff modifier can be used for displacement fields.  The
      symbol is added to the static TLS block and the negated offset to
      the symbol in the static TLS block is added to the GOT. The symbol
      term is replaced with the offset to the GOT slot from the start of
      the GOT.
-
-`@indntpoff'
+'@indntpoff'
      The @indntpoff modifier can be used for 32-bit pc-relative
-     immediate fields. The symbol is added to the static TLS block and
+     immediate fields.  The symbol is added to the static TLS block and
      the negated offset to the symbol in the static TLS block is added
-     to the GOT. The symbol term is replaced with the pc-relative
-     offset to the GOT slot from the current instruction address.
+     to the GOT. The symbol term is replaced with the pc-relative offset
+     to the GOT slot from the current instruction address.
 
    For more information about the thread local storage modifiers
-`gotntpoff' and `indntpoff' see the ELF extension documentation `ELF
+'gotntpoff' and 'indntpoff' see the ELF extension documentation 'ELF
 Handling For Thread-Local Storage'.
 
 
@@ -16305,24 +16189,22 @@ File: as.info,  Node: s390 Instruction Marker,  Next: s390 Literal Pool Entries,
 The thread local storage instruction markers are used by the linker to
 perform code optimization.
 
-`:tls_load'
+':tls_load'
      The :tls_load marker is used to flag the load instruction in the
      initial exec TLS model that retrieves the offset from the thread
      pointer to a thread local storage variable from the GOT.
-
-`:tls_gdcall'
+':tls_gdcall'
      The :tls_gdcall marker is used to flag the branch-and-save
      instruction to the __tls_get_offset function in the global dynamic
      TLS model.
-
-`:tls_ldcall'
+':tls_ldcall'
      The :tls_ldcall marker is used to flag the branch-and-save
      instruction to the __tls_get_offset function in the local dynamic
      TLS model.
 
    For more information about the thread local storage instruction
 marker and the linker optimizations see the ELF extension documentation
-`ELF Handling For Thread-Local Storage'.
+'ELF Handling For Thread-Local Storage'.
 
 
 File: as.info,  Node: s390 Literal Pool Entries,  Prev: s390 Instruction Marker,  Up: s390 Syntax
@@ -16330,41 +16212,39 @@ File: as.info,  Node: s390 Literal Pool Entries,  Prev: s390 Instruction Marker,
 9.37.3.8 Literal Pool Entries
 .............................
 
-A literal pool is a collection of values. To access the values a pointer
-to the literal pool is loaded to a register, the literal pool register.
-Usually, register %r13 is used as the literal pool register (*note s390
-Register::). Literal pool entries are created by adding the suffix
-:lit1, :lit2, :lit4, or :lit8 to the end of an expression for an
-instruction operand. The expression is added to the literal pool and the
-operand is replaced with the offset to the literal in the literal pool.
+A literal pool is a collection of values.  To access the values a
+pointer to the literal pool is loaded to a register, the literal pool
+register.  Usually, register %r13 is used as the literal pool register
+(*note s390 Register::).  Literal pool entries are created by adding the
+suffix :lit1, :lit2, :lit4, or :lit8 to the end of an expression for an
+instruction operand.  The expression is added to the literal pool and
+the operand is replaced with the offset to the literal in the literal
+pool.
 
-`:lit1'
-     The literal pool entry is created as an 8-bit value. An operand
+':lit1'
+     The literal pool entry is created as an 8-bit value.  An operand
      modifier must not be used for the original expression.
-
-`:lit2'
-     The literal pool entry is created as a 16 bit value. The operand
-     modifier @got may be used in the original expression. The term
-     `x@got:lit2' will put the got offset for the global symbol x to
-     the literal pool as 16 bit value.
-
-`:lit4'
-     The literal pool entry is created as a 32-bit value. The operand
-     modifier @got and @plt may be used in the original expression. The
-     term `x@got:lit4' will put the got offset for the global symbol x
-     to the literal pool as a 32-bit value. The term `x@plt:lit4' will
-     put the plt offset for the global symbol x to the literal pool as
-     a 32-bit value.
-
-`:lit8'
-     The literal pool entry is created as a 64-bit value. The operand
-     modifier @got and @plt may be used in the original expression. The
-     term `x@got:lit8' will put the got offset for the global symbol x
-     to the literal pool as a 64-bit value. The term `x@plt:lit8' will
-     put the plt offset for the global symbol x to the literal pool as
-     a 64-bit value.
-
-   The assembler directive `.ltorg' is used to emit all literal pool
+':lit2'
+     The literal pool entry is created as a 16 bit value.  The operand
+     modifier @got may be used in the original expression.  The term
+     'x@got:lit2' will put the got offset for the global symbol x to the
+     literal pool as 16 bit value.
+':lit4'
+     The literal pool entry is created as a 32-bit value.  The operand
+     modifier @got and @plt may be used in the original expression.  The
+     term 'x@got:lit4' will put the got offset for the global symbol x
+     to the literal pool as a 32-bit value.  The term 'x@plt:lit4' will
+     put the plt offset for the global symbol x to the literal pool as a
+     32-bit value.
+':lit8'
+     The literal pool entry is created as a 64-bit value.  The operand
+     modifier @got and @plt may be used in the original expression.  The
+     term 'x@got:lit8' will put the got offset for the global symbol x
+     to the literal pool as a 64-bit value.  The term 'x@plt:lit8' will
+     put the plt offset for the global symbol x to the literal pool as a
+     64-bit value.
+
+   The assembler directive '.ltorg' is used to emit all literal pool
 entries to the current position.
 
 
@@ -16373,113 +16253,103 @@ File: as.info,  Node: s390 Directives,  Next: s390 Floating Point,  Prev: s390 S
 9.37.4 Assembler Directives
 ---------------------------
 
-`as' for s390 supports all of the standard ELF assembler directives as
+'as' for s390 supports all of the standard ELF assembler directives as
 outlined in the main part of this document.  Some directives have been
 extended and there are some additional directives, which are only
-available for the s390 `as'.
+available for the s390 'as'.
 
-`.insn'
+'.insn'
      This directive permits the numeric representation of an
      instructions and makes the assembler insert the operands according
-     to one of the instructions formats for `.insn' (*note s390
-     Formats::).  For example, the instruction `l %r1,24(%r15)' could
-     be written as `.insn rx,0x58000000,%r1,24(%r15)'.  
-
-`.short'
-`.long'
-`.quad'
+     to one of the instructions formats for '.insn' (*note s390
+     Formats::).  For example, the instruction 'l %r1,24(%r15)' could be
+     written as '.insn rx,0x58000000,%r1,24(%r15)'.
+'.short'
+'.long'
+'.quad'
      This directive places one or more 16-bit (.short), 32-bit (.long),
-     or 64-bit (.quad) values into the current section. If an ELF or
+     or 64-bit (.quad) values into the current section.  If an ELF or
      TLS modifier is used only the following expressions are allowed:
-     `symbol@modifier + constant', `symbol@modifier + label +
-     constant', and `symbol@modifier - label + constant'.  The
-     following modifiers are available:
-    `@got'
-    `@got12'
+     'symbol@modifier + constant', 'symbol@modifier + label + constant',
+     and 'symbol@modifier - label + constant'.  The following modifiers
+     are available:
+     '@got'
+     '@got12'
           The @got modifier can be used for .short, .long and .quad.
-          The @got12 modifier is synonym to @got. The symbol is added
+          The @got12 modifier is synonym to @got.  The symbol is added
           to the GOT. The symbol term is replaced with offset from the
           start of the GOT to the GOT slot for the symbol.
-
-    `@gotoff'
+     '@gotoff'
           The @gotoff modifier can be used for .short, .long and .quad.
           The symbol term is replaced with the offset from the start of
           the GOT to the address of the symbol.
-
-    `@gotplt'
-          The @gotplt modifier can be used for .long and .quad. A
+     '@gotplt'
+          The @gotplt modifier can be used for .long and .quad.  A
           procedure linkage table entry is generated for the symbol and
           a jump slot for the symbol is added to the GOT. The symbol
           term is replaced with the offset from the start of the GOT to
           the jump slot for the symbol.
-
-    `@plt'
-          The @plt modifier can be used for .long and .quad. A
+     '@plt'
+          The @plt modifier can be used for .long and .quad.  A
           procedure linkage table entry us generated for the symbol.
           The symbol term is replaced with the address of the PLT entry
           for the symbol.
-
-    `@pltoff'
+     '@pltoff'
           The @pltoff modifier can be used for .short, .long and .quad.
           The symbol term is replaced with the offset from the start of
           the PLT to the address of the symbol.
-
-    `@tlsgd'
-    `@tlsldm'
+     '@tlsgd'
+     '@tlsldm'
           The @tlsgd and @tlsldm modifier can be used for .long and
-          .quad. A tls_index structure for the symbol is added to the
+          .quad.  A tls_index structure for the symbol is added to the
           GOT. The symbol term is replaced with the offset from the
           start of the GOT to the tls_index structure.
-
-    `@gotntpoff'
-    `@indntpoff'
+     '@gotntpoff'
+     '@indntpoff'
           The @gotntpoff and @indntpoff modifier can be used for .long
           and .quad.  The symbol is added to the static TLS block and
           the negated offset to the symbol in the static TLS block is
           added to the GOT. For @gotntpoff the symbol term is replaced
-          with the offset from the start of the GOT to the GOT slot,
-          for @indntpoff the symbol term is replaced with the address
-          of the GOT slot.
-
-    `@dtpoff'
-          The @dtpoff modifier can be used for .long and .quad. The
-          symbol term is replaced with the offset of the symbol
-          relative to the start of the TLS block it is contained in.
-
-    `@ntpoff'
-          The @ntpoff modifier can be used for .long and .quad. The
-          symbol term is replaced with the offset of the symbol
-          relative to the TCB pointer.
+          with the offset from the start of the GOT to the GOT slot, for
+          @indntpoff the symbol term is replaced with the address of the
+          GOT slot.
+     '@dtpoff'
+          The @dtpoff modifier can be used for .long and .quad.  The
+          symbol term is replaced with the offset of the symbol relative
+          to the start of the TLS block it is contained in.
+     '@ntpoff'
+          The @ntpoff modifier can be used for .long and .quad.  The
+          symbol term is replaced with the offset of the symbol relative
+          to the TCB pointer.
 
      For more information about the thread local storage modifiers see
-     the ELF extension documentation `ELF Handling For Thread-Local
+     the ELF extension documentation 'ELF Handling For Thread-Local
      Storage'.
 
-`.ltorg'
+'.ltorg'
      This directive causes the current contents of the literal pool to
      be dumped to the current location (*note s390 Literal Pool
      Entries::).
 
-`.machine string'
+'.machine string'
      This directive allows you to change the machine for which code is
-     generated.  `string' may be any of the `-march=' selection options
-     (without the -march=), `push', or `pop'.  `.machine push' saves
-     the currently selected cpu, which may be restored with `.machine
-     pop'.  Be aware that the cpu string has to be put into double
-     quotes in case it contains characters not appropriate for
-     identifiers.  So you have to write `"z9-109"' instead of just
-     `z9-109'.
-
-`.machinemode string'
+     generated.  'string' may be any of the '-march=' selection options
+     (without the -march=), 'push', or 'pop'.  '.machine push' saves the
+     currently selected cpu, which may be restored with '.machine pop'.
+     Be aware that the cpu string has to be put into double quotes in
+     case it contains characters not appropriate for identifiers.  So
+     you have to write '"z9-109"' instead of just 'z9-109'.
+
+'.machinemode string'
      This directive allows to change the architecture mode for which
-     code is being generated.  `string' may be `esa', `zarch',
-     `zarch_nohighgprs', `push', or `pop'.  `.machinemode
-     zarch_nohighgprs' can be used to prevent the `highgprs' flag from
+     code is being generated.  'string' may be 'esa', 'zarch',
+     'zarch_nohighgprs', 'push', or 'pop'.  '.machinemode
+     zarch_nohighgprs' can be used to prevent the 'highgprs' flag from
      being set in the ELF header of the output file.  This is useful in
-     situations where the code is gated with a runtime check which
-     makes sure that the code is only executed on kernels providing the
-     `highgprs' feature.  `.machinemode push' saves the currently
-     selected mode, which may be restored with `.machinemode pop'.
+     situations where the code is gated with a runtime check which makes
+     sure that the code is only executed on kernels providing the
+     'highgprs' feature.  '.machinemode push' saves the currently
+     selected mode, which may be restored with '.machinemode pop'.
 
 
 File: as.info,  Node: s390 Floating Point,  Prev: s390 Directives,  Up: S/390-Dependent
@@ -16488,13 +16358,13 @@ File: as.info,  Node: s390 Floating Point,  Prev: s390 Directives,  Up: S/390-De
 ---------------------
 
 The assembler recognizes both the IEEE floating-point instruction and
-the hexadecimal floating-point instructions. The floating-point
-constructors `.float', `.single', and `.double' always emit the IEEE
-format. To assemble hexadecimal floating-point constants the `.long'
-and `.quad' directives must be used.
+the hexadecimal floating-point instructions.  The floating-point
+constructors '.float', '.single', and '.double' always emit the IEEE
+format.  To assemble hexadecimal floating-point constants the '.long'
+and '.quad' directives must be used.
 
 
-File: as.info,  Node: SCORE-Dependent,  Next: Sparc-Dependent,  Prev: S/390-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: SCORE-Dependent,  Next: SH-Dependent,  Prev: S/390-Dependent,  Up: Machine Dependencies
 
 9.38 SCORE Dependent Features
 =============================
@@ -16513,117 +16383,115 @@ File: as.info,  Node: SCORE-Opts,  Next: SCORE-Pseudo,  Up: SCORE-Dependent
 
 The following table lists all available SCORE options.
 
-`-G NUM'
+'-G NUM'
      This option sets the largest size of an object that can be
-     referenced implicitly with the `gp' register. The default value is
+     referenced implicitly with the 'gp' register.  The default value is
      8.
 
-`-EB'
+'-EB'
      Assemble code for a big-endian cpu
 
-`-EL'
+'-EL'
      Assemble code for a little-endian cpu
 
-`-FIXDD'
+'-FIXDD'
      Assemble code for fix data dependency
 
-`-NWARN'
+'-NWARN'
      Assemble code for no warning message for fix data dependency
 
-`-SCORE5'
+'-SCORE5'
      Assemble code for target is SCORE5
 
-`-SCORE5U'
+'-SCORE5U'
      Assemble code for target is SCORE5U
 
-`-SCORE7'
+'-SCORE7'
      Assemble code for target is SCORE7, this is default setting
 
-`-SCORE3'
+'-SCORE3'
      Assemble code for target is SCORE3
 
-`-march=score7'
+'-march=score7'
      Assemble code for target is SCORE7, this is default setting
 
-`-march=score3'
+'-march=score3'
      Assemble code for target is SCORE3
 
-`-USE_R1'
+'-USE_R1'
      Assemble code for no warning message when using temp register r1
 
-`-KPIC'
-     Generate code for PIC.  This option tells the assembler to generate
+'-KPIC'
+     Generate code for PIC. This option tells the assembler to generate
      score position-independent macro expansions.  It also tells the
      assembler to mark the output file as PIC.
 
-`-O0'
+'-O0'
      Assembler will not perform any optimizations
 
-`-V'
+'-V'
      Sunplus release version
 
-
 
 File: as.info,  Node: SCORE-Pseudo,  Next: SCORE-Syntax,  Prev: SCORE-Opts,  Up: SCORE-Dependent
 
 9.38.2 SCORE Assembler Directives
 ---------------------------------
 
-A number of assembler directives are available for SCORE.  The
-following table is far from complete.
+A number of assembler directives are available for SCORE. The following
+table is far from complete.
 
-`.set nwarn'
+'.set nwarn'
      Let the assembler not to generate warnings if the source machine
      language instructions happen data dependency.
 
-`.set fixdd'
+'.set fixdd'
      Let the assembler to insert bubbles (32 bit nop instruction / 16
-     bit nop! Instruction) if the source machine language instructions
+     bit nop!  Instruction) if the source machine language instructions
      happen data dependency.
 
-`.set nofixdd'
+'.set nofixdd'
      Let the assembler to generate warnings if the source machine
-     language instructions happen data dependency. (Default)
+     language instructions happen data dependency.  (Default)
 
-`.set r1'
+'.set r1'
      Let the assembler not to generate warnings if the source program
-     uses r1. allow user to use r1
+     uses r1.  allow user to use r1
 
-`set nor1'
+'set nor1'
      Let the assembler to generate warnings if the source program uses
-     r1. (Default)
+     r1.  (Default)
 
-`.sdata'
+'.sdata'
      Tell the assembler to add subsequent data into the sdata section
 
-`.rdata'
+'.rdata'
      Tell the assembler to add subsequent data into the rdata section
 
-`.frame "frame-register", "offset", "return-pc-register"'
-     Describe a stack frame. "frame-register" is the frame register,
+'.frame "frame-register", "offset", "return-pc-register"'
+     Describe a stack frame.  "frame-register" is the frame register,
      "offset" is the distance from the frame register to the virtual
      frame pointer, "return-pc-register" is the return program register.
      You must use ".ent" before ".frame" and only one ".frame" can be
      used per ".ent".
 
-`.mask "bitmask", "frameoffset"'
+'.mask "bitmask", "frameoffset"'
      Indicate which of the integer registers are saved in the current
      function's stack frame, this is for the debugger to explain the
      frame chain.
 
-`.ent "proc-name"'
-     Set the beginning of the procedure "proc_name". Use this directive
+'.ent "proc-name"'
+     Set the beginning of the procedure "proc_name".  Use this directive
      when you want to generate information for the debugger.
 
-`.end proc-name'
-     Set the end of a procedure. Use this directive to generate
+'.end proc-name'
+     Set the end of a procedure.  Use this directive to generate
      information for the debugger.
 
-`.bss'
+'.bss'
      Switch the destination of following statements into the bss
      section, which is used for data that is uninitialized anywhere.
 
-
 
 File: as.info,  Node: SCORE-Syntax,  Prev: SCORE-Pseudo,  Up: SCORE-Dependent
 
@@ -16640,19 +16508,19 @@ File: as.info,  Node: SCORE-Chars,  Up: SCORE-Syntax
 9.38.3.1 Special Characters
 ...........................
 
-The presence of a `#' appearing anywhere on a line indicates the start
+The presence of a '#' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
-File: as.info,  Node: SH-Dependent,  Next: SH64-Dependent,  Prev: NS32K-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: SH-Dependent,  Next: SH64-Dependent,  Prev: SCORE-Dependent,  Up: Machine Dependencies
 
 9.39 Renesas / SuperH SH Dependent Features
 ===========================================
@@ -16671,50 +16539,46 @@ File: as.info,  Node: SH Options,  Next: SH Syntax,  Up: SH-Dependent
 9.39.1 Options
 --------------
 
-`as' has following command-line options for the Renesas (formerly
+'as' has following command-line options for the Renesas (formerly
 Hitachi) / SuperH SH family.
 
-`--little'
+'--little'
      Generate little endian code.
 
-`--big'
+'--big'
      Generate big endian code.
 
-`--relax'
+'--relax'
      Alter jump instructions for long displacements.
 
-`--small'
+'--small'
      Align sections to 4 byte boundaries, not 16.
 
-`--dsp'
+'--dsp'
      Enable sh-dsp insns, and disable sh3e / sh4 insns.
 
-`--renesas'
+'--renesas'
      Disable optimization with section symbol for compatibility with
      Renesas assembler.
 
-`--allow-reg-prefix'
+'--allow-reg-prefix'
      Allow '$' as a register name prefix.
 
-`--fdpic'
+'--fdpic'
      Generate an FDPIC object file.
 
-`--isa=sh4 | sh4a'
+'--isa=sh4 | sh4a'
      Specify the sh4 or sh4a instruction set.
-
-`--isa=dsp'
+'--isa=dsp'
      Enable sh-dsp insns, and disable sh3e / sh4 insns.
-
-`--isa=fp'
+'--isa=fp'
      Enable sh2e, sh3e, sh4, and sh4a insn sets.
-
-`--isa=all'
+'--isa=all'
      Enable sh1, sh2, sh2e, sh3, sh3e, sh4, sh4a, and sh-dsp insn sets.
 
-`-h-tick-hex'
+'-h-tick-hex'
      Support H'00 style hex constants in addition to 0x00 style.
 
-
 
 File: as.info,  Node: SH Syntax,  Next: SH Floating Point,  Prev: SH Options,  Up: SH-Dependent
 
@@ -16733,16 +16597,16 @@ File: as.info,  Node: SH-Chars,  Next: SH-Regs,  Up: SH Syntax
 9.39.2.1 Special Characters
 ...........................
 
-`!' is the line comment character.
+'!' is the line comment character.
 
-   You can use `;' instead of a newline to separate statements.
+   You can use ';' instead of a newline to separate statements.
 
-   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::).
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: SH-Regs,  Next: SH-Addressing,  Prev: SH-Chars,  Up: SH Syntax
@@ -16750,29 +16614,29 @@ File: as.info,  Node: SH-Regs,  Next: SH-Addressing,  Prev: SH-Chars,  Up: SH Sy
 9.39.2.2 Register Names
 .......................
 
-You can use the predefined symbols `r0', `r1', `r2', `r3', `r4', `r5',
-`r6', `r7', `r8', `r9', `r10', `r11', `r12', `r13', `r14', and `r15' to
+You can use the predefined symbols 'r0', 'r1', 'r2', 'r3', 'r4', 'r5',
+'r6', 'r7', 'r8', 'r9', 'r10', 'r11', 'r12', 'r13', 'r14', and 'r15' to
 refer to the SH registers.
 
    The SH also has these control registers:
 
-`pr'
+'pr'
      procedure register (holds return address)
 
-`pc'
+'pc'
      program counter
 
-`mach'
-`macl'
+'mach'
+'macl'
      high and low multiply accumulator registers
 
-`sr'
+'sr'
      status register
 
-`gbr'
+'gbr'
      global base register
 
-`vbr'
+'vbr'
      vector base register (for interrupt vectors)
 
 
@@ -16781,42 +16645,42 @@ File: as.info,  Node: SH-Addressing,  Prev: SH-Regs,  Up: SH Syntax
 9.39.2.3 Addressing Modes
 .........................
 
-`as' understands the following addressing modes for the SH.  `RN' in
-the following refers to any of the numbered registers, but _not_ the
-control registers.
+'as' understands the following addressing modes for the SH. 'RN' in the
+following refers to any of the numbered registers, but _not_ the control
+registers.
 
-`RN'
+'RN'
      Register direct
 
-`@RN'
+'@RN'
      Register indirect
 
-`@-RN'
+'@-RN'
      Register indirect with pre-decrement
 
-`@RN+'
+'@RN+'
      Register indirect with post-increment
 
-`@(DISP, RN)'
+'@(DISP, RN)'
      Register indirect with displacement
 
-`@(R0, RN)'
+'@(R0, RN)'
      Register indexed
 
-`@(DISP, GBR)'
-     `GBR' offset
+'@(DISP, GBR)'
+     'GBR' offset
 
-`@(R0, GBR)'
+'@(R0, GBR)'
      GBR indexed
 
-`ADDR'
-`@(DISP, PC)'
+'ADDR'
+'@(DISP, PC)'
      PC relative address (for branch or for addressing memory).  The
-     `as' implementation allows you to use the simpler form ADDR
-     anywhere a PC relative address is called for; the alternate form
-     is supported for compatibility with other assemblers.
+     'as' implementation allows you to use the simpler form ADDR
+     anywhere a PC relative address is called for; the alternate form is
+     supported for compatibility with other assemblers.
 
-`#IMM'
+'#IMM'
      Immediate data
 
 
@@ -16826,22 +16690,22 @@ File: as.info,  Node: SH Floating Point,  Next: SH Directives,  Prev: SH Syntax,
 ---------------------
 
 SH2E, SH3E and SH4 groups have on-chip floating-point unit (FPU). Other
-SH groups can use `.float' directive to generate IEEE floating-point
+SH groups can use '.float' directive to generate IEEE floating-point
 numbers.
 
    SH2E and SH3E support single-precision floating point calculations as
-well as entirely PCAPI compatible emulation of double-precision
-floating point calculations. SH2E and SH3E instructions are a subset of
-the floating point calculations conforming to the IEEE754 standard.
+well as entirely PCAPI compatible emulation of double-precision floating
+point calculations.  SH2E and SH3E instructions are a subset of the
+floating point calculations conforming to the IEEE754 standard.
 
    In addition to single-precision and double-precision floating-point
 operation capability, the on-chip FPU of SH4 has a 128-bit graphic
 engine that enables 32-bit floating-point data to be processed 128 bits
-at a time. It also supports 4 * 4 array operations and inner product
-operations. Also, a superscalar architecture is employed that enables
-simultaneous execution of two instructions (including FPU
-instructions), providing performance of up to twice that of
-conventional architectures at the same frequency.
+at a time.  It also supports 4 * 4 array operations and inner product
+operations.  Also, a superscalar architecture is employed that enables
+simultaneous execution of two instructions (including FPU instructions),
+providing performance of up to twice that of conventional architectures
+at the same frequency.
 
 
 File: as.info,  Node: SH Directives,  Next: SH Opcodes,  Prev: SH Floating Point,  Up: SH-Dependent
@@ -16849,12 +16713,12 @@ File: as.info,  Node: SH Directives,  Next: SH Opcodes,  Prev: SH Floating Point
 9.39.4 SH Machine Directives
 ----------------------------
 
-`uaword'
-`ualong'
-`uaquad'
-     `as' will issue a warning when a misaligned `.word', `.long', or
-     `.quad' directive is used.  You may use `.uaword', `.ualong', or
-     `.uaquad' to indicate that the value is intentionally misaligned.
+'uaword'
+'ualong'
+'uaquad'
+     'as' will issue a warning when a misaligned '.word', '.long', or
+     '.quad' directive is used.  You may use '.uaword', '.ualong', or
+     '.uaquad' to indicate that the value is intentionally misaligned.
 
 
 File: as.info,  Node: SH Opcodes,  Prev: SH Directives,  Up: SH-Dependent
@@ -16863,17 +16727,17 @@ File: as.info,  Node: SH Opcodes,  Prev: SH Directives,  Up: SH-Dependent
 --------------
 
 For detailed information on the SH machine instruction set, see
-`SH-Microcomputer User's Manual' (Renesas) or `SH-4 32-bit CPU Core
-Architecture' (SuperH) and `SuperH (SH) 64-Bit RISC Series' (SuperH).
+'SH-Microcomputer User's Manual' (Renesas) or 'SH-4 32-bit CPU Core
+Architecture' (SuperH) and 'SuperH (SH) 64-Bit RISC Series' (SuperH).
 
-   `as' implements all the standard SH opcodes.  No additional
+   'as' implements all the standard SH opcodes.  No additional
 pseudo-instructions are needed on this family.  Note, however, that
-because `as' supports a simpler form of PC-relative addressing, you may
+because 'as' supports a simpler form of PC-relative addressing, you may
 simply write (for example)
 
      mov.l  bar,r0
 
-where other assemblers might require an explicit displacement to `bar'
+where other assemblers might require an explicit displacement to 'bar'
 from the program counter:
 
      mov.l  @(DISP, PC)
@@ -16930,7 +16794,6 @@ from the program counter:
      lds Rn,PR                      mulu Rm,Rn
      lds.l @Rn+,MACH                neg Rm,Rn
      lds.l @Rn+,MACL                negc Rm,Rn
-
      nop                            stc VBR,Rn
      not Rm,Rn                      stc.l GBR,@-Rn
      or #imm,R0                     stc.l SR,@-Rn
@@ -16958,7 +16821,7 @@ from the program counter:
      stc SR,Rn
 
 
-File: as.info,  Node: SH64-Dependent,  Next: PDP-11-Dependent,  Prev: SH-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: SH64-Dependent,  Next: Sparc-Dependent,  Prev: SH-Dependent,  Up: Machine Dependencies
 
 9.40 SuperH SH64 Dependent Features
 ===================================
@@ -16976,56 +16839,51 @@ File: as.info,  Node: SH64 Options,  Next: SH64 Syntax,  Up: SH64-Dependent
 9.40.1 Options
 --------------
 
-`-isa=sh4 | sh4a'
+'-isa=sh4 | sh4a'
      Specify the sh4 or sh4a instruction set.
-
-`-isa=dsp'
+'-isa=dsp'
      Enable sh-dsp insns, and disable sh3e / sh4 insns.
-
-`-isa=fp'
+'-isa=fp'
      Enable sh2e, sh3e, sh4, and sh4a insn sets.
-
-`-isa=all'
+'-isa=all'
      Enable sh1, sh2, sh2e, sh3, sh3e, sh4, sh4a, and sh-dsp insn sets.
-
-`-isa=shmedia | -isa=shcompact'
-     Specify the default instruction set.  `SHmedia' specifies the
-     32-bit opcodes, and `SHcompact' specifies the 16-bit opcodes
+'-isa=shmedia | -isa=shcompact'
+     Specify the default instruction set.  'SHmedia' specifies the
+     32-bit opcodes, and 'SHcompact' specifies the 16-bit opcodes
      compatible with previous SH families.  The default depends on the
      ABI selected; the default for the 64-bit ABI is SHmedia, and the
      default for the 32-bit ABI is SHcompact.  If neither the ABI nor
      the ISA is specified, the default is 32-bit SHcompact.
 
-     Note that the `.mode' pseudo-op is not permitted if the ISA is not
+     Note that the '.mode' pseudo-op is not permitted if the ISA is not
      specified on the command line.
 
-`-abi=32 | -abi=64'
-     Specify the default ABI.  If the ISA is specified and the ABI is
-     not, the default ABI depends on the ISA, with SHmedia defaulting
-     to 64-bit and SHcompact defaulting to 32-bit.
+'-abi=32 | -abi=64'
+     Specify the default ABI. If the ISA is specified and the ABI is
+     not, the default ABI depends on the ISA, with SHmedia defaulting to
+     64-bit and SHcompact defaulting to 32-bit.
 
-     Note that the `.abi' pseudo-op is not permitted if the ABI is not
+     Note that the '.abi' pseudo-op is not permitted if the ABI is not
      specified on the command line.  When the ABI is specified on the
-     command line, any `.abi' pseudo-ops in the source must match it.
+     command line, any '.abi' pseudo-ops in the source must match it.
 
-`-shcompact-const-crange'
+'-shcompact-const-crange'
      Emit code-range descriptors for constants in SHcompact code
      sections.
 
-`-no-mix'
+'-no-mix'
      Disallow SHmedia code in the same section as constants and
      SHcompact code.
 
-`-no-expand'
+'-no-expand'
      Do not expand MOVI, PT, PTA or PTB instructions.
 
-`-expand-pt32'
+'-expand-pt32'
      With -abi=64, expand PT, PTA and PTB instructions to 32 bits only.
 
-`-h-tick-hex'
+'-h-tick-hex'
      Support H'00 style hex constants in addition to 0x00 style.
 
-
 
 File: as.info,  Node: SH64 Syntax,  Next: SH64 Directives,  Prev: SH64 Options,  Up: SH64-Dependent
 
@@ -17044,16 +16902,16 @@ File: as.info,  Node: SH64-Chars,  Next: SH64-Regs,  Up: SH64 Syntax
 9.40.2.1 Special Characters
 ...........................
 
-`!' is the line comment character.
+'!' is the line comment character.
 
-   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::).
 
-   You can use `;' instead of a newline to separate statements.
+   You can use ';' instead of a newline to separate statements.
 
-   Since `$' has no special meaning, you may use it in symbol names.
+   Since '$' has no special meaning, you may use it in symbol names.
 
 
 File: as.info,  Node: SH64-Regs,  Next: SH64-Addressing,  Prev: SH64-Chars,  Up: SH64 Syntax
@@ -17061,21 +16919,21 @@ File: as.info,  Node: SH64-Regs,  Next: SH64-Addressing,  Prev: SH64-Chars,  Up:
 9.40.2.2 Register Names
 .......................
 
-You can use the predefined symbols `r0' through `r63' to refer to the
-SH64 general registers, `cr0' through `cr63' for control registers,
-`tr0' through `tr7' for target address registers, `fr0' through `fr63'
-for single-precision floating point registers, `dr0' through `dr62'
+You can use the predefined symbols 'r0' through 'r63' to refer to the
+SH64 general registers, 'cr0' through 'cr63' for control registers,
+'tr0' through 'tr7' for target address registers, 'fr0' through 'fr63'
+for single-precision floating point registers, 'dr0' through 'dr62'
 (even numbered registers only) for double-precision floating point
-registers, `fv0' through `fv60' (multiples of four only) for
-single-precision floating point vectors, `fp0' through `fp62' (even
+registers, 'fv0' through 'fv60' (multiples of four only) for
+single-precision floating point vectors, 'fp0' through 'fp62' (even
 numbered registers only) for single-precision floating point pairs,
-`mtrx0' through `mtrx48' (multiples of 16 only) for 4x4 matrices of
-single-precision floating point registers, `pc' for the program
-counter, and `fpscr' for the floating point status and control register.
+'mtrx0' through 'mtrx48' (multiples of 16 only) for 4x4 matrices of
+single-precision floating point registers, 'pc' for the program counter,
+and 'fpscr' for the floating point status and control register.
 
-   You can also refer to the control registers by the mnemonics `sr',
-`ssr', `pssr', `intevt', `expevt', `pexpevt', `tra', `spc', `pspc',
-`resvec', `vbr', `tea', `dcr', `kcr0', `kcr1', `ctc', and `usr'.
+   You can also refer to the control registers by the mnemonics 'sr',
+'ssr', 'pssr', 'intevt', 'expevt', 'pexpevt', 'tra', 'spc', 'pspc',
+'resvec', 'vbr', 'tea', 'dcr', 'kcr0', 'kcr1', 'ctc', and 'usr'.
 
 
 File: as.info,  Node: SH64-Addressing,  Prev: SH64-Regs,  Up: SH64 Syntax
@@ -17095,10 +16953,10 @@ label reference), as in this example:
 
    Instruction label references can reference labels in either SHmedia
 or SHcompact.  To differentiate between the two, labels in SHmedia
-sections will always have the least significant bit set (i.e. they will
+sections will always have the least significant bit set (i.e.  they will
 be odd), which SHcompact labels will have the least significant bit
-reset (i.e. they will be even).  If you need to reference the actual
-address of a label, you can use the `datalabel' modifier, as in this
+reset (i.e.  they will be even).  If you need to reference the actual
+address of a label, you can use the 'datalabel' modifier, as in this
 example:
 
      	.long	function
@@ -17118,22 +16976,21 @@ File: as.info,  Node: SH64 Directives,  Next: SH64 Opcodes,  Prev: SH64 Syntax,
 In addition to the SH directives, the SH64 provides the following
 directives:
 
-`.mode [shmedia|shcompact]'
-`.isa [shmedia|shcompact]'
+'.mode [shmedia|shcompact]'
+'.isa [shmedia|shcompact]'
      Specify the ISA for the following instructions (the two directives
-     are equivalent).  Note that programs such as `objdump' rely on
+     are equivalent).  Note that programs such as 'objdump' rely on
      symbolic labels to determine when such mode switches occur (by
-     checking the least significant bit of the label's address), so
-     such mode/isa changes should always be followed by a label (in
-     practice, this is true anyway).  Note that you cannot use these
-     directives if you didn't specify an ISA on the command line.
+     checking the least significant bit of the label's address), so such
+     mode/isa changes should always be followed by a label (in practice,
+     this is true anyway).  Note that you cannot use these directives if
+     you didn't specify an ISA on the command line.
 
-`.abi [32|64]'
+'.abi [32|64]'
      Specify the ABI for the following instructions.  Note that you
      cannot use this directive unless you specified an ABI on the
      command line, and the ABIs specified must match.
 
-
 
 File: as.info,  Node: SH64 Opcodes,  Prev: SH64 Directives,  Up: SH64-Dependent
 
@@ -17141,24 +16998,23 @@ File: as.info,  Node: SH64 Opcodes,  Prev: SH64 Directives,  Up: SH64-Dependent
 --------------
 
 For detailed information on the SH64 machine instruction set, see
-`SuperH 64 bit RISC Series Architecture Manual' (SuperH, Inc.).
+'SuperH 64 bit RISC Series Architecture Manual' (SuperH, Inc.).
 
-   `as' implements all the standard SH64 opcodes.  In addition, the
+   'as' implements all the standard SH64 opcodes.  In addition, the
 following pseudo-opcodes may be expanded into one or more alternate
 opcodes:
 
-`movi'
-     If the value doesn't fit into a standard `movi' opcode, `as' will
-     replace the `movi' with a sequence of `movi' and `shori' opcodes.
+'movi'
+     If the value doesn't fit into a standard 'movi' opcode, 'as' will
+     replace the 'movi' with a sequence of 'movi' and 'shori' opcodes.
 
-`pt'
-     This expands to a sequence of `movi' and `shori' opcode, followed
-     by a `ptrel' opcode, or to a `pta' or `ptb' opcode, depending on
+'pt'
+     This expands to a sequence of 'movi' and 'shori' opcode, followed
+     by a 'ptrel' opcode, or to a 'pta' or 'ptb' opcode, depending on
      the label referenced.
 
-
 
-File: as.info,  Node: Sparc-Dependent,  Next: TIC54X-Dependent,  Prev: SCORE-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: Sparc-Dependent,  Next: TIC54X-Dependent,  Prev: SH64-Dependent,  Up: Machine Dependencies
 
 9.41 SPARC Dependent Features
 =============================
@@ -17183,98 +17039,98 @@ at each version.  There are exceptions to this however.  For details on
 what instructions each variant supports, please see the chip's
 architecture reference manual.
 
-   By default, `as' assumes the core instruction set (SPARC v6), but
+   By default, 'as' assumes the core instruction set (SPARC v6), but
 "bumps" the architecture level as needed: it switches to successively
 higher architectures as it encounters instructions that only exist in
 the higher levels.
 
-   If not configured for SPARC v9 (`sparc64-*-*') GAS will not bump
-past sparclite by default, an option must be passed to enable the v9
+   If not configured for SPARC v9 ('sparc64-*-*') GAS will not bump past
+sparclite by default, an option must be passed to enable the v9
 instructions.
 
    GAS treats sparclite as being compatible with v8, unless an
 architecture is explicitly requested.  SPARC v9 is always incompatible
 with sparclite.
 
-`-Av6 | -Av7 | -Av8 | -Asparclet | -Asparclite'
-`-Av8plus | -Av8plusa | -Av8plusb | -Av8plusc | -Av8plusd | -Av8plusv'
-`-Av9 | -Av9a | -Av9b | -Av9c | -Av9d | -Av9v'
-`-Asparc | -Asparcvis | -Asparcvis2 | -Asparcfmaf | -Asparcima'
-`-Asparcvis3 | -Asparcvis3r'
-     Use one of the `-A' options to select one of the SPARC
+'-Av6 | -Av7 | -Av8 | -Aleon | -Asparclet | -Asparclite'
+'-Av8plus | -Av8plusa | -Av8plusb | -Av8plusc | -Av8plusd | -Av8plusv'
+'-Av9 | -Av9a | -Av9b | -Av9c | -Av9d | -Av9v'
+'-Asparc | -Asparcvis | -Asparcvis2 | -Asparcfmaf | -Asparcima'
+'-Asparcvis3 | -Asparcvis3r'
+     Use one of the '-A' options to select one of the SPARC
      architectures explicitly.  If you select an architecture
-     explicitly, `as' reports a fatal error if it encounters an
+     explicitly, 'as' reports a fatal error if it encounters an
      instruction or feature requiring an incompatible or higher level.
 
-     `-Av8plus', `-Av8plusa', `-Av8plusb', `-Av8plusc', `-Av8plusd',
-     and `-Av8plusv' select a 32 bit environment.
+     '-Av8plus', '-Av8plusa', '-Av8plusb', '-Av8plusc', '-Av8plusd', and
+     '-Av8plusv' select a 32 bit environment.
 
-     `-Av9', `-Av9a', `-Av9b', `-Av9c', `-Av9d', and `-Av9v' select a
-     64 bit environment and are not available unless GAS is explicitly
+     '-Av9', '-Av9a', '-Av9b', '-Av9c', '-Av9d', and '-Av9v' select a 64
+     bit environment and are not available unless GAS is explicitly
      configured with 64 bit environment support.
 
-     `-Av8plusa' and `-Av9a' enable the SPARC V9 instruction set with
+     '-Av8plusa' and '-Av9a' enable the SPARC V9 instruction set with
      UltraSPARC VIS 1.0 extensions.
 
-     `-Av8plusb' and `-Av9b' enable the UltraSPARC VIS 2.0 instructions,
-     as well as the instructions enabled by `-Av8plusa' and `-Av9a'.
+     '-Av8plusb' and '-Av9b' enable the UltraSPARC VIS 2.0 instructions,
+     as well as the instructions enabled by '-Av8plusa' and '-Av9a'.
 
-     `-Av8plusc' and `-Av9c' enable the UltraSPARC Niagara instructions,
-     as well as the instructions enabled by `-Av8plusb' and `-Av9b'.
+     '-Av8plusc' and '-Av9c' enable the UltraSPARC Niagara instructions,
+     as well as the instructions enabled by '-Av8plusb' and '-Av9b'.
 
-     `-Av8plusd' and `-Av9d' enable the floating point fused
+     '-Av8plusd' and '-Av9d' enable the floating point fused
      multiply-add, VIS 3.0, and HPC extension instructions, as well as
-     the instructions enabled by `-Av8plusc' and `-Av9c'.
+     the instructions enabled by '-Av8plusc' and '-Av9c'.
 
-     `-Av8plusv' and `-Av9v' enable the 'random', transactional memory,
+     '-Av8plusv' and '-Av9v' enable the 'random', transactional memory,
      floating point unfused multiply-add, integer multiply-add, and
      cache sparing store instructions, as well as the instructions
-     enabled by `-Av8plusd' and `-Av9d'.
+     enabled by '-Av8plusd' and '-Av9d'.
 
-     `-Asparc' specifies a v9 environment.  It is equivalent to `-Av9'
-     if the word size is 64-bit, and `-Av8plus' otherwise.
+     '-Asparc' specifies a v9 environment.  It is equivalent to '-Av9'
+     if the word size is 64-bit, and '-Av8plus' otherwise.
 
-     `-Asparcvis' specifies a v9a environment.  It is equivalent to
-     `-Av9a' if the word size is 64-bit, and `-Av8plusa' otherwise.
+     '-Asparcvis' specifies a v9a environment.  It is equivalent to
+     '-Av9a' if the word size is 64-bit, and '-Av8plusa' otherwise.
 
-     `-Asparcvis2' specifies a v9b environment.  It is equivalent to
-     `-Av9b' if the word size is 64-bit, and `-Av8plusb' otherwise.
+     '-Asparcvis2' specifies a v9b environment.  It is equivalent to
+     '-Av9b' if the word size is 64-bit, and '-Av8plusb' otherwise.
 
-     `-Asparcfmaf' specifies a v9b environment with the floating point
+     '-Asparcfmaf' specifies a v9b environment with the floating point
      fused multiply-add instructions enabled.
 
-     `-Asparcima' specifies a v9b environment with the integer
+     '-Asparcima' specifies a v9b environment with the integer
      multiply-add instructions enabled.
 
-     `-Asparcvis3' specifies a v9b environment with the VIS 3.0, HPC ,
+     '-Asparcvis3' specifies a v9b environment with the VIS 3.0, HPC ,
      and floating point fused multiply-add instructions enabled.
 
-     `-Asparcvis3r' specifies a v9b environment with the VIS 3.0, HPC,
+     '-Asparcvis3r' specifies a v9b environment with the VIS 3.0, HPC,
      transactional memory, random, and floating point unfused
      multiply-add instructions enabled.
 
-`-xarch=v8plus | -xarch=v8plusa | -xarch=v8plusb | -xarch=v8plusc'
-`-xarch=v8plusd | -xarch=v8plusv | -xarch=v9 | -xarch=v9a'
-`-xarch=v9b | -xarch=v9c | -xarch=v9d | -xarch=v9v'
-`-xarch=sparc | -xarch=sparcvis | -xarch=sparcvis2'
-`-xarch=sparcfmaf | -xarch=sparcima | -xarch=sparcvis3'
-`-xarch=sparcvis3r'
+'-xarch=v8plus | -xarch=v8plusa | -xarch=v8plusb | -xarch=v8plusc'
+'-xarch=v8plusd | -xarch=v8plusv | -xarch=v9 | -xarch=v9a'
+'-xarch=v9b | -xarch=v9c | -xarch=v9d | -xarch=v9v'
+'-xarch=sparc | -xarch=sparcvis | -xarch=sparcvis2'
+'-xarch=sparcfmaf | -xarch=sparcima | -xarch=sparcvis3'
+'-xarch=sparcvis3r'
      For compatibility with the SunOS v9 assembler.  These options are
      equivalent to -Av8plus, -Av8plusa, -Av8plusb, -Av8plusc, -Av8plusd,
      -Av8plusv, -Av9, -Av9a, -Av9b, -Av9c, -Av9d, -Av9v, -Asparc,
      -Asparcvis, -Asparcvis2, -Asparcfmaf, -Asparcima, -Asparcvis3, and
      -Asparcvis3r, respectively.
 
-`-bump'
+'-bump'
      Warn whenever it is necessary to switch to another level.  If an
      architecture level is explicitly requested, GAS will not issue
      warnings until that level is reached, and will then bump the level
      as required (except between incompatible levels).
 
-`-32 | -64'
-     Select the word size, either 32 bits or 64 bits.  These options
-     are only available with the ELF object file format, and require
-     that the necessary BFD support has been included.
+'-32 | -64'
+     Select the word size, either 32 bits or 64 bits.  These options are
+     only available with the ELF object file format, and require that
+     the necessary BFD support has been included.
 
 
 File: as.info,  Node: Sparc-Aligned-Data,  Next: Sparc-Syntax,  Prev: Sparc-Opts,  Up: Sparc-Dependent
@@ -17283,17 +17139,17 @@ File: as.info,  Node: Sparc-Aligned-Data,  Next: Sparc-Syntax,  Prev: Sparc-Opts
 -----------------------------
 
 SPARC GAS normally permits data to be misaligned.  For example, it
-permits the `.long' pseudo-op to be used on a byte boundary.  However,
+permits the '.long' pseudo-op to be used on a byte boundary.  However,
 the native SunOS assemblers issue an error when they see misaligned
 data.
 
-   You can use the `--enforce-aligned-data' option to make SPARC GAS
+   You can use the '--enforce-aligned-data' option to make SPARC GAS
 also issue an error about misaligned data, just as the SunOS assemblers
 do.
 
-   The `--enforce-aligned-data' option is not the default because gcc
+   The '--enforce-aligned-data' option is not the default because gcc
 issues misaligned data pseudo-ops when it initializes certain packed
-data structures (structures defined using the `packed' attribute).  You
+data structures (structures defined using the 'packed' attribute).  You
 may have to assemble with GAS in order to initialize packed data
 structures in your own code.
 
@@ -17321,15 +17177,15 @@ File: as.info,  Node: Sparc-Chars,  Next: Sparc-Regs,  Up: Sparc-Syntax
 9.41.3.1 Special Characters
 ...........................
 
-A `!' character appearing anywhere on a line indicates the start of a
+A '!' character appearing 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::).
 
-   `;' can be used instead of a newline to separate statements.
+   ';' can be used instead of a newline to separate statements.
 
 
 File: as.info,  Node: Sparc-Regs,  Next: Sparc-Constants,  Prev: Sparc-Chars,  Up: Sparc-Syntax
@@ -17340,147 +17196,146 @@ File: as.info,  Node: Sparc-Regs,  Next: Sparc-Constants,  Prev: Sparc-Chars,  U
 The Sparc integer register file is broken down into global, outgoing,
 local, and incoming.
 
-   * The 8 global registers are referred to as `%gN'.
+   * The 8 global registers are referred to as '%gN'.
 
-   * The 8 outgoing registers are referred to as `%oN'.
+   * The 8 outgoing registers are referred to as '%oN'.
 
-   * The 8 local registers are referred to as `%lN'.
+   * The 8 local registers are referred to as '%lN'.
 
-   * The 8 incoming registers are referred to as `%iN'.
+   * The 8 incoming registers are referred to as '%iN'.
 
-   * The frame pointer register `%i6' can be referenced using the alias
-     `%fp'.
+   * The frame pointer register '%i6' can be referenced using the alias
+     '%fp'.
 
-   * The stack pointer register `%o6' can be referenced using the alias
-     `%sp'.
+   * The stack pointer register '%o6' can be referenced using the alias
+     '%sp'.
 
-   Floating point registers are simply referred to as `%fN'.  When
+   Floating point registers are simply referred to as '%fN'.  When
 assembling for pre-V9, only 32 floating point registers are available.
 For V9 and later there are 64, but there are restrictions when
-referencing the upper 32 registers.  They can only be accessed as
-double or quad, and thus only even or quad numbered accesses are
-allowed.  For example, `%f34' is a legal floating point register, but
-`%f35' is not.
+referencing the upper 32 registers.  They can only be accessed as double
+or quad, and thus only even or quad numbered accesses are allowed.  For
+example, '%f34' is a legal floating point register, but '%f35' is not.
 
    Certain V9 instructions allow access to ancillary state registers.
-Most simply they can be referred to as `%asrN' where N can be from 16
-to 31.  However, there are some aliases defined to reference ASR
-registers defined for various UltraSPARC processors:
+Most simply they can be referred to as '%asrN' where N can be from 16 to
+31.  However, there are some aliases defined to reference ASR registers
+defined for various UltraSPARC processors:
 
-   * The tick compare register is referred to as `%tick_cmpr'.
+   * The tick compare register is referred to as '%tick_cmpr'.
 
-   * The system tick register is referred to as `%stick'.  An alias,
-     `%sys_tick', exists but is deprecated and should not be used by
-     new software.
+   * The system tick register is referred to as '%stick'.  An alias,
+     '%sys_tick', exists but is deprecated and should not be used by new
+     software.
 
-   * The system tick compare register is referred to as `%stick_cmpr'.
-     An alias, `%sys_tick_cmpr', exists but is deprecated and should
-     not be used by new software.
+   * The system tick compare register is referred to as '%stick_cmpr'.
+     An alias, '%sys_tick_cmpr', exists but is deprecated and should not
+     be used by new software.
 
-   * The software interrupt register is referred to as `%softint'.
+   * The software interrupt register is referred to as '%softint'.
 
    * The set software interrupt register is referred to as
-     `%set_softint'.  The mnemonic `%softint_set' is provided as an
+     '%set_softint'.  The mnemonic '%softint_set' is provided as an
      alias.
 
    * The clear software interrupt register is referred to as
-     `%clear_softint'.  The mnemonic `%softint_clear' is provided as an
+     '%clear_softint'.  The mnemonic '%softint_clear' is provided as an
      alias.
 
    * The performance instrumentation counters register is referred to as
-     `%pic'.
+     '%pic'.
 
-   * The performance control register is referred to as `%pcr'.
+   * The performance control register is referred to as '%pcr'.
 
-   * The graphics status register is referred to as `%gsr'.
+   * The graphics status register is referred to as '%gsr'.
 
-   * The V9 dispatch control register is referred to as `%dcr'.
+   * The V9 dispatch control register is referred to as '%dcr'.
 
    Various V9 branch and conditional move instructions allow
 specification of which set of integer condition codes to test.  These
-are referred to as `%xcc' and `%icc'.
+are referred to as '%xcc' and '%icc'.
 
    In V9, there are 4 sets of floating point condition codes which are
-referred to as `%fccN'.
+referred to as '%fccN'.
 
    Several special privileged and non-privileged registers exist:
 
-   * The V9 address space identifier register is referred to as `%asi'.
+   * The V9 address space identifier register is referred to as '%asi'.
 
-   * The V9 restorable windows register is referred to as `%canrestore'.
+   * The V9 restorable windows register is referred to as '%canrestore'.
 
-   * The V9 savable windows register is referred to as `%cansave'.
+   * The V9 savable windows register is referred to as '%cansave'.
 
-   * The V9 clean windows register is referred to as `%cleanwin'.
+   * The V9 clean windows register is referred to as '%cleanwin'.
 
-   * The V9 current window pointer register is referred to as `%cwp'.
+   * The V9 current window pointer register is referred to as '%cwp'.
 
-   * The floating-point queue register is referred to as `%fq'.
+   * The floating-point queue register is referred to as '%fq'.
 
-   * The V8 co-processor queue register is referred to as `%cq'.
+   * The V8 co-processor queue register is referred to as '%cq'.
 
-   * The floating point status register is referred to as `%fsr'.
+   * The floating point status register is referred to as '%fsr'.
 
-   * The other windows register is referred to as `%otherwin'.
+   * The other windows register is referred to as '%otherwin'.
 
-   * The V9 program counter register is referred to as `%pc'.
+   * The V9 program counter register is referred to as '%pc'.
 
-   * The V9 next program counter register is referred to as `%npc'.
+   * The V9 next program counter register is referred to as '%npc'.
 
-   * The V9 processor interrupt level register is referred to as `%pil'.
+   * The V9 processor interrupt level register is referred to as '%pil'.
 
-   * The V9 processor state register is referred to as `%pstate'.
+   * The V9 processor state register is referred to as '%pstate'.
 
-   * The trap base address register is referred to as `%tba'.
+   * The trap base address register is referred to as '%tba'.
 
-   * The V9 tick register is referred to as `%tick'.
+   * The V9 tick register is referred to as '%tick'.
 
-   * The V9 trap level is referred to as `%tl'.
+   * The V9 trap level is referred to as '%tl'.
 
-   * The V9 trap program counter is referred to as `%tpc'.
+   * The V9 trap program counter is referred to as '%tpc'.
 
-   * The V9 trap next program counter is referred to as `%tnpc'.
+   * The V9 trap next program counter is referred to as '%tnpc'.
 
-   * The V9 trap state is referred to as `%tstate'.
+   * The V9 trap state is referred to as '%tstate'.
 
-   * The V9 trap type is referred to as `%tt'.
+   * The V9 trap type is referred to as '%tt'.
 
-   * The V9 condition codes is referred to as `%ccr'.
+   * The V9 condition codes is referred to as '%ccr'.
 
-   * The V9 floating-point registers state is referred to as `%fprs'.
+   * The V9 floating-point registers state is referred to as '%fprs'.
 
-   * The V9 version register is referred to as `%ver'.
+   * The V9 version register is referred to as '%ver'.
 
-   * The V9 window state register is referred to as `%wstate'.
+   * The V9 window state register is referred to as '%wstate'.
 
-   * The Y register is referred to as `%y'.
+   * The Y register is referred to as '%y'.
 
-   * The V8 window invalid mask register is referred to as `%wim'.
+   * The V8 window invalid mask register is referred to as '%wim'.
 
-   * The V8 processor state register is referred to as `%psr'.
+   * The V8 processor state register is referred to as '%psr'.
 
-   * The V9 global register level register is referred to as `%gl'.
+   * The V9 global register level register is referred to as '%gl'.
 
    Several special register names exist for hypervisor mode code:
 
    * The hyperprivileged processor state register is referred to as
-     `%hpstate'.
+     '%hpstate'.
 
    * The hyperprivileged trap state register is referred to as
-     `%htstate'.
+     '%htstate'.
 
    * The hyperprivileged interrupt pending register is referred to as
-     `%hintp'.
+     '%hintp'.
 
    * The hyperprivileged trap base address register is referred to as
-     `%htba'.
+     '%htba'.
 
    * The hyperprivileged implementation version register is referred to
-     as `%hver'.
+     as '%hver'.
 
    * The hyperprivileged system tick compare register is referred to as
-     `%hstick_cmpr'.  Note that there is no `%hstick' register, the
-     normal `%stick' is used.
+     '%hstick_cmpr'.  Note that there is no '%hstick' register, the
+     normal '%stick' is used.
 
 
 File: as.info,  Node: Sparc-Constants,  Next: Sparc-Relocs,  Prev: Sparc-Regs,  Up: Sparc-Syntax
@@ -17489,93 +17344,92 @@ File: as.info,  Node: Sparc-Constants,  Next: Sparc-Relocs,  Prev: Sparc-Regs,
 ..................
 
 Several Sparc instructions take an immediate operand field for which
-mnemonic names exist.  Two such examples are `membar' and `prefetch'.
+mnemonic names exist.  Two such examples are 'membar' and 'prefetch'.
 Another example are the set of V9 memory access instruction that allow
 specification of an address space identifier.
 
-   The `membar' instruction specifies a memory barrier that is the
-defined by the operand which is a bitmask.  The supported mask
-mnemonics are:
+   The 'membar' instruction specifies a memory barrier that is the
+defined by the operand which is a bitmask.  The supported mask mnemonics
+are:
 
-   * `#Sync' requests that all operations (including nonmemory
-     reference operations) appearing prior to the `membar' must have
-     been performed and the effects of any exceptions become visible
-     before any instructions after the `membar' may be initiated.  This
-     corresponds to `membar' cmask field bit 2.
+   * '#Sync' requests that all operations (including nonmemory reference
+     operations) appearing prior to the 'membar' must have been
+     performed and the effects of any exceptions become visible before
+     any instructions after the 'membar' may be initiated.  This
+     corresponds to 'membar' cmask field bit 2.
 
-   * `#MemIssue' requests that all memory reference operations
-     appearing prior to the `membar' must have been performed before
-     any memory operation after the `membar' may be initiated.  This
-     corresponds to `membar' cmask field bit 1.
+   * '#MemIssue' requests that all memory reference operations appearing
+     prior to the 'membar' must have been performed before any memory
+     operation after the 'membar' may be initiated.  This corresponds to
+     'membar' cmask field bit 1.
 
-   * `#Lookaside' requests that a store appearing prior to the `membar'
-     must complete before any load following the `membar' referencing
-     the same address can be initiated.  This corresponds to `membar'
+   * '#Lookaside' requests that a store appearing prior to the 'membar'
+     must complete before any load following the 'membar' referencing
+     the same address can be initiated.  This corresponds to 'membar'
      cmask field bit 0.
 
-   * `#StoreStore' defines that the effects of all stores appearing
-     prior to the `membar' instruction must be visible to all
-     processors before the effect of any stores following the `membar'.
-     Equivalent to the deprecated `stbar' instruction.  This
-     corresponds to `membar' mmask field bit 3.
+   * '#StoreStore' defines that the effects of all stores appearing
+     prior to the 'membar' instruction must be visible to all processors
+     before the effect of any stores following the 'membar'.  Equivalent
+     to the deprecated 'stbar' instruction.  This corresponds to
+     'membar' mmask field bit 3.
 
-   * `#LoadStore' defines all loads appearing prior to the `membar'
+   * '#LoadStore' defines all loads appearing prior to the 'membar'
      instruction must have been performed before the effect of any
-     stores following the `membar' is visible to any other processor.
-     This corresponds to `membar' mmask field bit 2.
+     stores following the 'membar' is visible to any other processor.
+     This corresponds to 'membar' mmask field bit 2.
 
-   * `#StoreLoad' defines that the effects of all stores appearing
-     prior to the `membar' instruction must be visible to all
-     processors before loads following the `membar' may be performed.
-     This corresponds to `membar' mmask field bit 1.
+   * '#StoreLoad' defines that the effects of all stores appearing prior
+     to the 'membar' instruction must be visible to all processors
+     before loads following the 'membar' may be performed.  This
+     corresponds to 'membar' mmask field bit 1.
 
-   * `#LoadLoad' defines that all loads appearing prior to the `membar'
-     instruction must have been performed before any loads following
-     the `membar' may be performed.  This corresponds to `membar' mmask
+   * '#LoadLoad' defines that all loads appearing prior to the 'membar'
+     instruction must have been performed before any loads following the
+     'membar' may be performed.  This corresponds to 'membar' mmask
      field bit 0.
 
-
    These values can be ored together, for example:
 
      membar #Sync
      membar #StoreLoad | #LoadLoad
      membar #StoreLoad | #StoreStore
 
-   The `prefetch' and `prefetcha' instructions take a prefetch function
+   The 'prefetch' and 'prefetcha' instructions take a prefetch function
 code.  The following prefetch function code constant mnemonics are
 available:
 
-   * `#n_reads' requests a prefetch for several reads, and corresponds
+   * '#n_reads' requests a prefetch for several reads, and corresponds
      to a prefetch function code of 0.
 
-     `#one_read' requests a prefetch for one read, and corresponds to a
+     '#one_read' requests a prefetch for one read, and corresponds to a
      prefetch function code of 1.
 
-     `#n_writes' requests a prefetch for several writes (and possibly
+     '#n_writes' requests a prefetch for several writes (and possibly
      reads), and corresponds to a prefetch function code of 2.
 
-     `#one_write' requests a prefetch for one write, and corresponds to
+     '#one_write' requests a prefetch for one write, and corresponds to
      a prefetch function code of 3.
 
-     `#page' requests a prefetch page, and corresponds to a prefetch
+     '#page' requests a prefetch page, and corresponds to a prefetch
      function code of 4.
 
-     `#invalidate' requests a prefetch invalidate, and corresponds to a
+     '#invalidate' requests a prefetch invalidate, and corresponds to a
      prefetch function code of 16.
 
-     `#unified' requests a prefetch to the nearest unified cache, and
+     '#unified' requests a prefetch to the nearest unified cache, and
      corresponds to a prefetch function code of 17.
 
-     `#n_reads_strong' requests a strong prefetch for several reads,
-     and corresponds to a prefetch function code of 20.
+     '#n_reads_strong' requests a strong prefetch for several reads, and
+     corresponds to a prefetch function code of 20.
 
-     `#one_read_strong' requests a strong prefetch for one read, and
+     '#one_read_strong' requests a strong prefetch for one read, and
      corresponds to a prefetch function code of 21.
 
-     `#n_writes_strong' requests a strong prefetch for several writes,
+     '#n_writes_strong' requests a strong prefetch for several writes,
      and corresponds to a prefetch function code of 22.
 
-     `#one_write_strong' requests a strong prefetch for one write, and
+     '#one_write_strong' requests a strong prefetch for one write, and
      corresponds to a prefetch function code of 23.
 
      Onle one prefetch code may be specified.  Here are some examples:
@@ -17590,11 +17444,10 @@ available:
      function code, it will treat the prefetch instruction as a nop.
 
      For instructions that accept an immediate address space identifier,
-     `as' provides many mnemonics corresponding to V9 defined as well
-     as UltraSPARC and Niagara extended values.  For example, `#ASI_P'
-     and `#ASI_BLK_INIT_QUAD_LDD_AIUS'.  See the V9 and processor
-     specific manuals for details.
-
+     'as' provides many mnemonics corresponding to V9 defined as well as
+     UltraSPARC and Niagara extended values.  For example, '#ASI_P' and
+     '#ASI_BLK_INIT_QUAD_LDD_AIUS'.  See the V9 and processor specific
+     manuals for details.
 
 
 File: as.info,  Node: Sparc-Relocs,  Next: Sparc-Size-Translations,  Prev: Sparc-Constants,  Up: Sparc-Syntax
@@ -17605,9 +17458,9 @@ File: as.info,  Node: Sparc-Relocs,  Next: Sparc-Size-Translations,  Prev: Sparc
 ELF relocations are available as defined in the 32-bit and 64-bit Sparc
 ELF specifications.
 
-   `R_SPARC_HI22' is obtained using `%hi' and `R_SPARC_LO10' is
-obtained using `%lo'.  Likewise `R_SPARC_HIX22' is obtained from `%hix'
-and `R_SPARC_LOX10' is obtained using `%lox'.  For example:
+   'R_SPARC_HI22' is obtained using '%hi' and 'R_SPARC_LO10' is obtained
+using '%lo'.  Likewise 'R_SPARC_HIX22' is obtained from '%hix' and
+'R_SPARC_LOX10' is obtained using '%lox'.  For example:
 
      sethi %hi(symbol), %g1
      or    %g1, %lo(symbol), %g1
@@ -17620,94 +17473,75 @@ and `R_SPARC_LOX10' is obtained using `%lox'.  For example:
 
    V9 code model relocations can be requested as follows:
 
-   * `R_SPARC_HH22' is requested using `%hh'.  It can also be generated
-     using `%uhi'.
-
-   * `R_SPARC_HM10' is requested using `%hm'.  It can also be generated
-     using `%ulo'.
-
-   * `R_SPARC_LM22' is requested using `%lm'.
-
-   * `R_SPARC_H44' is requested using `%h44'.
+   * 'R_SPARC_HH22' is requested using '%hh'.  It can also be generated
+     using '%uhi'.
+   * 'R_SPARC_HM10' is requested using '%hm'.  It can also be generated
+     using '%ulo'.
+   * 'R_SPARC_LM22' is requested using '%lm'.
 
-   * `R_SPARC_M44' is requested using `%m44'.
+   * 'R_SPARC_H44' is requested using '%h44'.
+   * 'R_SPARC_M44' is requested using '%m44'.
+   * 'R_SPARC_L44' is requested using '%l44' or '%l34'.
+   * 'R_SPARC_H34' is requested using '%h34'.
 
-   * `R_SPARC_L44' is requested using `%l44' or `%l34'.
+   The '%l34' generates a 'R_SPARC_L44' relocation because it calculates
+the necessary value, and therefore no explicit 'R_SPARC_L34' relocation
+needed to be created for this purpose.
 
-   * `R_SPARC_H34' is requested using `%h34'.
-
-   The `%l34' generates a `R_SPARC_L44' relocation because it
-calculates the necessary value, and therefore no explicit `R_SPARC_L34'
-relocation needed to be created for this purpose.
-
-   The `%h34' and `%l34' relocations are used for the abs34 code model.
+   The '%h34' and '%l34' relocations are used for the abs34 code model.
 Here is an example abs34 address generation sequence:
 
      sethi %h34(symbol), %g1
      sllx  %g1, 2, %g1
      or    %g1, %l34(symbol), %g1
 
-   The PC relative relocation `R_SPARC_PC22' can be obtained by
-enclosing an operand inside of `%pc22'.  Likewise, the `R_SPARC_PC10'
-relocation can be obtained using `%pc10'.  These are mostly used when
-assembling PIC code.  For example, the standard PIC sequence on Sparc
-to get the base of the global offset table, PC relative, into a
-register, can be performed as:
+   The PC relative relocation 'R_SPARC_PC22' can be obtained by
+enclosing an operand inside of '%pc22'.  Likewise, the 'R_SPARC_PC10'
+relocation can be obtained using '%pc10'.  These are mostly used when
+assembling PIC code.  For example, the standard PIC sequence on Sparc to
+get the base of the global offset table, PC relative, into a register,
+can be performed as:
 
      sethi %pc22(_GLOBAL_OFFSET_TABLE_-4), %l7
      add   %l7, %pc10(_GLOBAL_OFFSET_TABLE_+4), %l7
 
    Several relocations exist to allow the link editor to potentially
-optimize GOT data references.  The `R_SPARC_GOTDATA_OP_HIX22'
-relocation can obtained by enclosing an operand inside of
-`%gdop_hix22'.  The `R_SPARC_GOTDATA_OP_LOX10' relocation can obtained
-by enclosing an operand inside of `%gdop_lox10'.  Likewise,
-`R_SPARC_GOTDATA_OP' can be obtained by enclosing an operand inside of
-`%gdop'.  For example, assuming the GOT base is in register `%l7':
+optimize GOT data references.  The 'R_SPARC_GOTDATA_OP_HIX22' relocation
+can obtained by enclosing an operand inside of '%gdop_hix22'.  The
+'R_SPARC_GOTDATA_OP_LOX10' relocation can obtained by enclosing an
+operand inside of '%gdop_lox10'.  Likewise, 'R_SPARC_GOTDATA_OP' can be
+obtained by enclosing an operand inside of '%gdop'.  For example,
+assuming the GOT base is in register '%l7':
 
      sethi %gdop_hix22(symbol), %l1
      xor   %l1, %gdop_lox10(symbol), %l1
      ld    [%l7 + %l1], %l2, %gdop(symbol)
 
-   There are many relocations that can be requested for access to
-thread local storage variables.  All of the Sparc TLS mnemonics are
-supported:
-
-   * `R_SPARC_TLS_GD_HI22' is requested using `%tgd_hi22'.
-
-   * `R_SPARC_TLS_GD_LO10' is requested using `%tgd_lo10'.
-
-   * `R_SPARC_TLS_GD_ADD' is requested using `%tgd_add'.
-
-   * `R_SPARC_TLS_GD_CALL' is requested using `%tgd_call'.
-
-   * `R_SPARC_TLS_LDM_HI22' is requested using `%tldm_hi22'.
+   There are many relocations that can be requested for access to thread
+local storage variables.  All of the Sparc TLS mnemonics are supported:
 
-   * `R_SPARC_TLS_LDM_LO10' is requested using `%tldm_lo10'.
+   * 'R_SPARC_TLS_GD_HI22' is requested using '%tgd_hi22'.
+   * 'R_SPARC_TLS_GD_LO10' is requested using '%tgd_lo10'.
+   * 'R_SPARC_TLS_GD_ADD' is requested using '%tgd_add'.
+   * 'R_SPARC_TLS_GD_CALL' is requested using '%tgd_call'.
 
-   * `R_SPARC_TLS_LDM_ADD' is requested using `%tldm_add'.
+   * 'R_SPARC_TLS_LDM_HI22' is requested using '%tldm_hi22'.
+   * 'R_SPARC_TLS_LDM_LO10' is requested using '%tldm_lo10'.
+   * 'R_SPARC_TLS_LDM_ADD' is requested using '%tldm_add'.
+   * 'R_SPARC_TLS_LDM_CALL' is requested using '%tldm_call'.
 
-   * `R_SPARC_TLS_LDM_CALL' is requested using `%tldm_call'.
+   * 'R_SPARC_TLS_LDO_HIX22' is requested using '%tldo_hix22'.
+   * 'R_SPARC_TLS_LDO_LOX10' is requested using '%tldo_lox10'.
+   * 'R_SPARC_TLS_LDO_ADD' is requested using '%tldo_add'.
 
-   * `R_SPARC_TLS_LDO_HIX22' is requested using `%tldo_hix22'.
+   * 'R_SPARC_TLS_IE_HI22' is requested using '%tie_hi22'.
+   * 'R_SPARC_TLS_IE_LO10' is requested using '%tie_lo10'.
+   * 'R_SPARC_TLS_IE_LD' is requested using '%tie_ld'.
+   * 'R_SPARC_TLS_IE_LDX' is requested using '%tie_ldx'.
+   * 'R_SPARC_TLS_IE_ADD' is requested using '%tie_add'.
 
-   * `R_SPARC_TLS_LDO_LOX10' is requested using `%tldo_lox10'.
-
-   * `R_SPARC_TLS_LDO_ADD' is requested using `%tldo_add'.
-
-   * `R_SPARC_TLS_IE_HI22' is requested using `%tie_hi22'.
-
-   * `R_SPARC_TLS_IE_LO10' is requested using `%tie_lo10'.
-
-   * `R_SPARC_TLS_IE_LD' is requested using `%tie_ld'.
-
-   * `R_SPARC_TLS_IE_LDX' is requested using `%tie_ldx'.
-
-   * `R_SPARC_TLS_IE_ADD' is requested using `%tie_add'.
-
-   * `R_SPARC_TLS_LE_HIX22' is requested using `%tle_hix22'.
-
-   * `R_SPARC_TLS_LE_LOX10' is requested using `%tle_lox10'.
+   * 'R_SPARC_TLS_LE_HIX22' is requested using '%tle_hix22'.
+   * 'R_SPARC_TLS_LE_LOX10' is requested using '%tle_lox10'.
 
    Here are some example TLS model sequences.
 
@@ -17751,7 +17585,7 @@ supported:
 
    When assembling for 64-bit, and a secondary constant addend is
 specified in an address expression that would normally generate an
-`R_SPARC_LO10' relocation, the assembler will emit an `R_SPARC_OLO10'
+'R_SPARC_LO10' relocation, the assembler will emit an 'R_SPARC_OLO10'
 instead.
 
 
@@ -17761,14 +17595,14 @@ File: as.info,  Node: Sparc-Size-Translations,  Prev: Sparc-Relocs,  Up: Sparc-S
 ..........................
 
 Often it is desirable to write code in an operand size agnostic manner.
-`as' provides support for this via operand size opcode translations.
+'as' provides support for this via operand size opcode translations.
 Translations are supported for loads, stores, shifts, compare-and-swap
-atomics, and the `clr' synthetic instruction.
+atomics, and the 'clr' synthetic instruction.
 
-   If generating 32-bit code, `as' will generate the 32-bit opcode.
+   If generating 32-bit code, 'as' will generate the 32-bit opcode.
 Whereas if 64-bit code is being generated, the 64-bit opcode will be
-emitted.  For example `ldn' will be transformed into `ld' for 32-bit
-code and `ldx' for 64-bit code.
+emitted.  For example 'ldn' will be transformed into 'ld' for 32-bit
+code and 'ldx' for 64-bit code.
 
    Here is an example meant to demonstrate all the supported opcode
 translations:
@@ -17784,7 +17618,7 @@ translations:
      casna [%o0] %asi, %o1, %o2
      clrn  %g1
 
-   In 32-bit mode `as' will emit:
+   In 32-bit mode 'as' will emit:
 
      ld   [%o0], %o1
      lda  [%o0] %asi, %o2
@@ -17797,7 +17631,7 @@ translations:
      casa [%o0] %asi, %o1, %o2
      clr  %g1
 
-   And in 64-bit mode `as' will emit:
+   And in 64-bit mode 'as' will emit:
 
      ldx   [%o0], %o1
      ldxa  [%o0] %asi, %o2
@@ -17810,8 +17644,8 @@ translations:
      casxa [%o0] %asi, %o1, %o2
      clrx  %g1
 
-   Finally, the `.nword' translating directive is supported as well.
-It is documented in the section on Sparc machine directives.
+   Finally, the '.nword' translating directive is supported as well.  It
+is documented in the section on Sparc machine directives.
 
 
 File: as.info,  Node: Sparc-Float,  Next: Sparc-Directives,  Prev: Sparc-Syntax,  Up: Sparc-Dependent
@@ -17827,57 +17661,57 @@ File: as.info,  Node: Sparc-Directives,  Prev: Sparc-Float,  Up: Sparc-Dependent
 9.41.5 Sparc Machine Directives
 -------------------------------
 
-The Sparc version of `as' supports the following additional machine
+The Sparc version of 'as' supports the following additional machine
 directives:
 
-`.align'
+'.align'
      This must be followed by the desired alignment in bytes.
 
-`.common'
+'.common'
      This must be followed by a symbol name, a positive number, and
-     `"bss"'.  This behaves somewhat like `.comm', but the syntax is
+     '"bss"'.  This behaves somewhat like '.comm', but the syntax is
      different.
 
-`.half'
-     This is functionally identical to `.short'.
+'.half'
+     This is functionally identical to '.short'.
 
-`.nword'
-     On the Sparc, the `.nword' directive produces native word sized
-     value, ie. if assembling with -32 it is equivalent to `.word', if
-     assembling with -64 it is equivalent to `.xword'.
+'.nword'
+     On the Sparc, the '.nword' directive produces native word sized
+     value, ie.  if assembling with -32 it is equivalent to '.word', if
+     assembling with -64 it is equivalent to '.xword'.
 
-`.proc'
+'.proc'
      This directive is ignored.  Any text following it on the same line
      is also ignored.
 
-`.register'
+'.register'
      This directive declares use of a global application or system
      register.  It must be followed by a register name %g2, %g3, %g6 or
      %g7, comma and the symbol name for that register.  If symbol name
-     is `#scratch', it is a scratch register, if it is `#ignore', it
+     is '#scratch', it is a scratch register, if it is '#ignore', it
      just suppresses any errors about using undeclared global register,
      but does not emit any information about it into the object file.
-     This can be useful e.g. if you save the register before use and
+     This can be useful e.g.  if you save the register before use and
      restore it after.
 
-`.reserve'
+'.reserve'
      This must be followed by a symbol name, a positive number, and
-     `"bss"'.  This behaves somewhat like `.lcomm', but the syntax is
+     '"bss"'.  This behaves somewhat like '.lcomm', but the syntax is
      different.
 
-`.seg'
-     This must be followed by `"text"', `"data"', or `"data1"'.  It
-     behaves like `.text', `.data', or `.data 1'.
+'.seg'
+     This must be followed by '"text"', '"data"', or '"data1"'.  It
+     behaves like '.text', '.data', or '.data 1'.
 
-`.skip'
-     This is functionally identical to the `.space' directive.
+'.skip'
+     This is functionally identical to the '.space' directive.
 
-`.word'
-     On the Sparc, the `.word' directive produces 32 bit values,
-     instead of the 16 bit values it produces on many other machines.
+'.word'
+     On the Sparc, the '.word' directive produces 32 bit values, instead
+     of the 16 bit values it produces on many other machines.
 
-`.xword'
-     On the Sparc V9 processor, the `.xword' directive produces 64 bit
+'.xword'
+     On the Sparc V9 processor, the '.xword' directive produces 64 bit
      values.
 
 
@@ -17907,24 +17741,24 @@ File: as.info,  Node: TIC54X-Opts,  Next: TIC54X-Block,  Up: TIC54X-Dependent
 9.42.1 Options
 --------------
 
-The TMS320C54X version of `as' has a few machine-dependent options.
+The TMS320C54X version of 'as' has a few machine-dependent options.
 
-   You can use the `-mfar-mode' option to enable extended addressing
+   You can use the '-mfar-mode' option to enable extended addressing
 mode.  All addresses will be assumed to be > 16 bits, and the
-appropriate relocation types will be used.  This option is equivalent
-to using the `.far_mode' directive in the assembly code.  If you do not
-use the `-mfar-mode' option, all references will be assumed to be 16
-bits.  This option may be abbreviated to `-mf'.
-
-   You can use the `-mcpu' option to specify a particular CPU.  This
-option is equivalent to using the `.version' directive in the assembly
-code.  For recognized CPU codes, see *Note `.version':
-TIC54X-Directives.  The default CPU version is `542'.
-
-   You can use the `-merrors-to-file' option to redirect error output
-to a file (this provided for those deficient environments which don't
+appropriate relocation types will be used.  This option is equivalent to
+using the '.far_mode' directive in the assembly code.  If you do not use
+the '-mfar-mode' option, all references will be assumed to be 16 bits.
+This option may be abbreviated to '-mf'.
+
+   You can use the '-mcpu' option to specify a particular CPU. This
+option is equivalent to using the '.version' directive in the assembly
+code.  For recognized CPU codes, see *Note '.version':
+TIC54X-Directives.  The default CPU version is '542'.
+
+   You can use the '-merrors-to-file' option to redirect error output to
+a file (this provided for those deficient environments which don't
 provide adequate output redirection).  This option may be abbreviated to
-`-me'.
+'-me'.
 
 
 File: as.info,  Node: TIC54X-Block,  Next: TIC54X-Env,  Prev: TIC54X-Opts,  Up: TIC54X-Dependent
@@ -17943,9 +17777,9 @@ File: as.info,  Node: TIC54X-Env,  Next: TIC54X-Constants,  Prev: TIC54X-Block,
 9.42.3 Environment Settings
 ---------------------------
 
-`C54XDSP_DIR' and `A_DIR' are semicolon-separated paths which are added
+'C54XDSP_DIR' and 'A_DIR' are semicolon-separated paths which are added
 to the list of directories normally searched for source and include
-files.  `C54XDSP_DIR' will override `A_DIR'.
+files.  'C54XDSP_DIR' will override 'A_DIR'.
 
 
 File: as.info,  Node: TIC54X-Constants,  Next: TIC54X-Subsyms,  Prev: TIC54X-Env,  Up: TIC54X-Dependent
@@ -17953,12 +17787,12 @@ File: as.info,  Node: TIC54X-Constants,  Next: TIC54X-Subsyms,  Prev: TIC54X-Env
 9.42.4 Constants Syntax
 -----------------------
 
-The TIC54X version of `as' allows the following additional constant
+The TIC54X version of 'as' allows the following additional constant
 formats, using a suffix to indicate the radix:
 
-     Binary                  `000000B, 011000b'
-     Octal                   `10Q, 224q'
-     Hexadecimal             `45h, 0FH'
+     Binary                  000000B, 011000b
+     Octal                   10Q, 224q
+     Hexadecimal             45h, 0FH
 
 
 File: as.info,  Node: TIC54X-Subsyms,  Next: TIC54X-Locals,  Prev: TIC54X-Constants,  Up: TIC54X-Dependent
@@ -17968,18 +17802,18 @@ File: as.info,  Node: TIC54X-Subsyms,  Next: TIC54X-Locals,  Prev: TIC54X-Consta
 
 A subset of allowable symbols (which we'll call subsyms) may be assigned
 arbitrary string values.  This is roughly equivalent to C preprocessor
-#define macros.  When `as' encounters one of these symbols, the symbol
+#define macros.  When 'as' encounters one of these symbols, the symbol
 is replaced in the input stream by its string value.  Subsym names
 *must* begin with a letter.
 
-   Subsyms may be defined using the `.asg' and `.eval' directives
-(*Note `.asg': TIC54X-Directives, *Note `.eval': TIC54X-Directives.
+   Subsyms may be defined using the '.asg' and '.eval' directives (*Note
+'.asg': TIC54X-Directives, *Note '.eval': TIC54X-Directives.
 
-   Expansion is recursive until a previously encountered symbol is
-seen, at which point substitution stops.
+   Expansion is recursive until a previously encountered symbol is seen,
+at which point substitution stops.
 
-   In this example, x is replaced with SYM2; SYM2 is replaced with
-SYM1, and SYM1 is replaced with x.  At this point, x has already been
+   In this example, x is replaced with SYM2; SYM2 is replaced with SYM1,
+and SYM1 is replaced with x.  At this point, x has already been
 encountered and the substitution stops.
 
       .asg   "x",SYM1
@@ -17988,10 +17822,10 @@ encountered and the substitution stops.
       add    x,a             ; final code assembled is "add  x, a"
 
    Macro parameters are converted to subsyms; a side effect of this is
-the normal `as' '\ARG' dereferencing syntax is unnecessary.  Subsyms
-defined within a macro will have global scope, unless the `.var'
-directive is used to identify the subsym as a local macro variable
-*note `.var': TIC54X-Directives.
+the normal 'as' '\ARG' dereferencing syntax is unnecessary.  Subsyms
+defined within a macro will have global scope, unless the '.var'
+directive is used to identify the subsym as a local macro variable *note
+'.var': TIC54X-Directives.
 
    Substitution may be forced in situations where replacement might be
 ambiguous by placing colons on either side of the subsym.  The following
@@ -18007,11 +17841,10 @@ code:
    Smaller parts of the string assigned to a subsym may be accessed with
 the following syntax:
 
-``:SYMBOL(CHAR_INDEX):''
+':SYMBOL(CHAR_INDEX):'
      Evaluates to a single-character string, the character at
      CHAR_INDEX.
-
-``:SYMBOL(START,LENGTH):''
+':SYMBOL(START,LENGTH):'
      Evaluates to a substring of SYMBOL beginning at START with length
      LENGTH.
 
@@ -18024,7 +17857,6 @@ File: as.info,  Node: TIC54X-Locals,  Next: TIC54X-Builtins,  Prev: TIC54X-Subsy
 Local labels may be defined in two ways:
 
    * $N, where N is a decimal number between 0 and 9
-
    * LABEL?, where LABEL is any legal symbol name.
 
    Local labels thus defined may be redefined or automatically
@@ -18032,12 +17864,9 @@ generated.  The scope of a local label is based on when it may be
 undefined or reset.  This happens when one of the following situations
 is encountered:
 
-   * .newblock directive *note `.newblock': TIC54X-Directives.
-
+   * .newblock directive *note '.newblock': TIC54X-Directives.
    * The current section is changed (.sect, .text, or .data)
-
    * Entering or leaving an included file
-
    * The macro scope where the label was defined is exited
 
 
@@ -18047,105 +17876,104 @@ File: as.info,  Node: TIC54X-Builtins,  Next: TIC54X-Ext,  Prev: TIC54X-Locals,
 --------------------
 
 The following built-in functions may be used to generate a
-floating-point value.  All return a floating-point value except `$cvi',
-`$int', and `$sgn', which return an integer value.
+floating-point value.  All return a floating-point value except '$cvi',
+'$int', and '$sgn', which return an integer value.
 
-``$acos(EXPR)''
+'$acos(EXPR)'
      Returns the floating point arccosine of EXPR.
 
-``$asin(EXPR)''
+'$asin(EXPR)'
      Returns the floating point arcsine of EXPR.
 
-``$atan(EXPR)''
+'$atan(EXPR)'
      Returns the floating point arctangent of EXPR.
 
-``$atan2(EXPR1,EXPR2)''
+'$atan2(EXPR1,EXPR2)'
      Returns the floating point arctangent of EXPR1 / EXPR2.
 
-``$ceil(EXPR)''
+'$ceil(EXPR)'
      Returns the smallest integer not less than EXPR as floating point.
 
-``$cosh(EXPR)''
+'$cosh(EXPR)'
      Returns the floating point hyperbolic cosine of EXPR.
 
-``$cos(EXPR)''
+'$cos(EXPR)'
      Returns the floating point cosine of EXPR.
 
-``$cvf(EXPR)''
+'$cvf(EXPR)'
      Returns the integer value EXPR converted to floating-point.
 
-``$cvi(EXPR)''
+'$cvi(EXPR)'
      Returns the floating point value EXPR converted to integer.
 
-``$exp(EXPR)''
+'$exp(EXPR)'
      Returns the floating point value e ^ EXPR.
 
-``$fabs(EXPR)''
+'$fabs(EXPR)'
      Returns the floating point absolute value of EXPR.
 
-``$floor(EXPR)''
+'$floor(EXPR)'
      Returns the largest integer that is not greater than EXPR as
      floating point.
 
-``$fmod(EXPR1,EXPR2)''
+'$fmod(EXPR1,EXPR2)'
      Returns the floating point remainder of EXPR1 / EXPR2.
 
-``$int(EXPR)''
+'$int(EXPR)'
      Returns 1 if EXPR evaluates to an integer, zero otherwise.
 
-``$ldexp(EXPR1,EXPR2)''
+'$ldexp(EXPR1,EXPR2)'
      Returns the floating point value EXPR1 * 2 ^ EXPR2.
 
-``$log10(EXPR)''
+'$log10(EXPR)'
      Returns the base 10 logarithm of EXPR.
 
-``$log(EXPR)''
+'$log(EXPR)'
      Returns the natural logarithm of EXPR.
 
-``$max(EXPR1,EXPR2)''
+'$max(EXPR1,EXPR2)'
      Returns the floating point maximum of EXPR1 and EXPR2.
 
-``$min(EXPR1,EXPR2)''
+'$min(EXPR1,EXPR2)'
      Returns the floating point minimum of EXPR1 and EXPR2.
 
-``$pow(EXPR1,EXPR2)''
+'$pow(EXPR1,EXPR2)'
      Returns the floating point value EXPR1 ^ EXPR2.
 
-``$round(EXPR)''
+'$round(EXPR)'
      Returns the nearest integer to EXPR as a floating point number.
 
-``$sgn(EXPR)''
+'$sgn(EXPR)'
      Returns -1, 0, or 1 based on the sign of EXPR.
 
-``$sin(EXPR)''
+'$sin(EXPR)'
      Returns the floating point sine of EXPR.
 
-``$sinh(EXPR)''
+'$sinh(EXPR)'
      Returns the floating point hyperbolic sine of EXPR.
 
-``$sqrt(EXPR)''
+'$sqrt(EXPR)'
      Returns the floating point square root of EXPR.
 
-``$tan(EXPR)''
+'$tan(EXPR)'
      Returns the floating point tangent of EXPR.
 
-``$tanh(EXPR)''
+'$tanh(EXPR)'
      Returns the floating point hyperbolic tangent of EXPR.
 
-``$trunc(EXPR)''
+'$trunc(EXPR)'
      Returns the integer value of EXPR truncated towards zero as
      floating point.
 
-
 
 File: as.info,  Node: TIC54X-Ext,  Next: TIC54X-Directives,  Prev: TIC54X-Builtins,  Up: TIC54X-Dependent
 
 9.42.8 Extended Addressing
 --------------------------
 
-The `LDX' pseudo-op is provided for loading the extended addressing bits
-of a label or address.  For example, if an address `_label' resides in
-extended program memory, the value of `_label' may be loaded as follows:
+The 'LDX' pseudo-op is provided for loading the extended addressing bits
+of a label or address.  For example, if an address '_label' resides in
+extended program memory, the value of '_label' may be loaded as follows:
       ldx     #_label,16,a    ; loads extended bits of _label
       or      #_label,a       ; loads lower 16 bits of _label
       bacc    a               ; full address is in accumulator A
@@ -18156,224 +17984,222 @@ File: as.info,  Node: TIC54X-Directives,  Next: TIC54X-Macros,  Prev: TIC54X-Ext
 9.42.9 Directives
 -----------------
 
-`.align [SIZE]'
-`.even'
+'.align [SIZE]'
+'.even'
      Align the section program counter on the next boundary, based on
-     SIZE.  SIZE may be any power of 2.  `.even' is equivalent to
-     `.align' with a SIZE of 2.
-    `1'
+     SIZE.  SIZE may be any power of 2.  '.even' is equivalent to
+     '.align' with a SIZE of 2.
+     '1'
           Align SPC to word boundary
-
-    `2'
+     '2'
           Align SPC to longword boundary (same as .even)
-
-    `128'
+     '128'
           Align SPC to page boundary
 
-`.asg STRING, NAME'
+'.asg STRING, NAME'
      Assign NAME the string STRING.  String replacement is performed on
      STRING before assignment.
 
-`.eval STRING, NAME'
+'.eval STRING, NAME'
      Evaluate the contents of string STRING and assign the result as a
      string to the subsym NAME.  String replacement is performed on
      STRING before assignment.
 
-`.bss SYMBOL, SIZE [, [BLOCKING_FLAG] [,ALIGNMENT_FLAG]]'
+'.bss SYMBOL, SIZE [, [BLOCKING_FLAG] [,ALIGNMENT_FLAG]]'
      Reserve space for SYMBOL in the .bss section.  SIZE is in words.
      If present, BLOCKING_FLAG indicates the allocated space should be
      aligned on a page boundary if it would otherwise cross a page
      boundary.  If present, ALIGNMENT_FLAG causes the assembler to
      allocate SIZE on a long word boundary.
 
-`.byte VALUE [,...,VALUE_N]'
-`.ubyte VALUE [,...,VALUE_N]'
-`.char VALUE [,...,VALUE_N]'
-`.uchar VALUE [,...,VALUE_N]'
+'.byte VALUE [,...,VALUE_N]'
+'.ubyte VALUE [,...,VALUE_N]'
+'.char VALUE [,...,VALUE_N]'
+'.uchar VALUE [,...,VALUE_N]'
      Place one or more bytes into consecutive words of the current
-     section.  The upper 8 bits of each word is zero-filled.  If a
-     label is used, it points to the word allocated for the first byte
+     section.  The upper 8 bits of each word is zero-filled.  If a label
+     is used, it points to the word allocated for the first byte
      encountered.
 
-`.clink ["SECTION_NAME"]'
-     Set STYP_CLINK flag for this section, which indicates to the
-     linker that if no symbols from this section are referenced, the
-     section should not be included in the link.  If SECTION_NAME is
-     omitted, the current section is used.
+'.clink ["SECTION_NAME"]'
+     Set STYP_CLINK flag for this section, which indicates to the linker
+     that if no symbols from this section are referenced, the section
+     should not be included in the link.  If SECTION_NAME is omitted,
+     the current section is used.
 
-`.c_mode'
+'.c_mode'
      TBD.
 
-`.copy "FILENAME" | FILENAME'
-`.include "FILENAME" | FILENAME'
+'.copy "FILENAME" | FILENAME'
+'.include "FILENAME" | FILENAME'
      Read source statements from FILENAME.  The normal include search
      path is used.  Normally .copy will cause statements from the
      included file to be printed in the assembly listing and .include
      will not, but this distinction is not currently implemented.
 
-`.data'
+'.data'
      Begin assembling code into the .data section.
 
-`.double VALUE [,...,VALUE_N]'
-`.ldouble VALUE [,...,VALUE_N]'
-`.float VALUE [,...,VALUE_N]'
-`.xfloat VALUE [,...,VALUE_N]'
-     Place an IEEE single-precision floating-point representation of
-     one or more floating-point values into the current section.  All
-     but `.xfloat' align the result on a longword boundary.  Values are
+'.double VALUE [,...,VALUE_N]'
+'.ldouble VALUE [,...,VALUE_N]'
+'.float VALUE [,...,VALUE_N]'
+'.xfloat VALUE [,...,VALUE_N]'
+     Place an IEEE single-precision floating-point representation of one
+     or more floating-point values into the current section.  All but
+     '.xfloat' align the result on a longword boundary.  Values are
      stored most-significant word first.
 
-`.drlist'
-`.drnolist'
+'.drlist'
+'.drnolist'
      Control printing of directives to the listing file.  Ignored.
 
-`.emsg STRING'
-`.mmsg STRING'
-`.wmsg STRING'
+'.emsg STRING'
+'.mmsg STRING'
+'.wmsg STRING'
      Emit a user-defined error, message, or warning, respectively.
 
-`.far_mode'
+'.far_mode'
      Use extended addressing when assembling statements.  This should
      appear only once per file, and is equivalent to the -mfar-mode
-     option *note `-mfar-mode': TIC54X-Opts.
+     option *note '-mfar-mode': TIC54X-Opts.
 
-`.fclist'
-`.fcnolist'
+'.fclist'
+'.fcnolist'
      Control printing of false conditional blocks to the listing file.
 
-`.field VALUE [,SIZE]'
+'.field VALUE [,SIZE]'
      Initialize a bitfield of SIZE bits in the current section.  If
      VALUE is relocatable, then SIZE must be 16.  SIZE defaults to 16
      bits.  If VALUE does not fit into SIZE bits, the value will be
-     truncated.  Successive `.field' directives will pack starting at
+     truncated.  Successive '.field' directives will pack starting at
      the current word, filling the most significant bits first, and
      aligning to the start of the next word if the field size does not
-     fit into the space remaining in the current word.  A `.align'
-     directive with an operand of 1 will force the next `.field'
+     fit into the space remaining in the current word.  A '.align'
+     directive with an operand of 1 will force the next '.field'
      directive to begin packing into a new word.  If a label is used, it
      points to the word that contains the specified field.
 
-`.global SYMBOL [,...,SYMBOL_N]'
-`.def SYMBOL [,...,SYMBOL_N]'
-`.ref SYMBOL [,...,SYMBOL_N]'
-     `.def' nominally identifies a symbol defined in the current file
-     and available to other files.  `.ref' identifies a symbol used in
+'.global SYMBOL [,...,SYMBOL_N]'
+'.def SYMBOL [,...,SYMBOL_N]'
+'.ref SYMBOL [,...,SYMBOL_N]'
+     '.def' nominally identifies a symbol defined in the current file
+     and available to other files.  '.ref' identifies a symbol used in
      the current file but defined elsewhere.  Both map to the standard
-     `.global' directive.
-
-`.half VALUE [,...,VALUE_N]'
-`.uhalf VALUE [,...,VALUE_N]'
-`.short VALUE [,...,VALUE_N]'
-`.ushort VALUE [,...,VALUE_N]'
-`.int VALUE [,...,VALUE_N]'
-`.uint VALUE [,...,VALUE_N]'
-`.word VALUE [,...,VALUE_N]'
-`.uword VALUE [,...,VALUE_N]'
+     '.global' directive.
+
+'.half VALUE [,...,VALUE_N]'
+'.uhalf VALUE [,...,VALUE_N]'
+'.short VALUE [,...,VALUE_N]'
+'.ushort VALUE [,...,VALUE_N]'
+'.int VALUE [,...,VALUE_N]'
+'.uint VALUE [,...,VALUE_N]'
+'.word VALUE [,...,VALUE_N]'
+'.uword VALUE [,...,VALUE_N]'
      Place one or more values into consecutive words of the current
      section.  If a label is used, it points to the word allocated for
      the first value encountered.
 
-`.label SYMBOL'
+'.label SYMBOL'
      Define a special SYMBOL to refer to the load time address of the
      current section program counter.
 
-`.length'
-`.width'
+'.length'
+'.width'
      Set the page length and width of the output listing file.  Ignored.
 
-`.list'
-`.nolist'
+'.list'
+'.nolist'
      Control whether the source listing is printed.  Ignored.
 
-`.long VALUE [,...,VALUE_N]'
-`.ulong VALUE [,...,VALUE_N]'
-`.xlong VALUE [,...,VALUE_N]'
+'.long VALUE [,...,VALUE_N]'
+'.ulong VALUE [,...,VALUE_N]'
+'.xlong VALUE [,...,VALUE_N]'
      Place one or more 32-bit values into consecutive words in the
      current section.  The most significant word is stored first.
-     `.long' and `.ulong' align the result on a longword boundary;
-     `xlong' does not.
-
-`.loop [COUNT]'
-`.break [CONDITION]'
-`.endloop'
-     Repeatedly assemble a block of code.  `.loop' begins the block, and
-     `.endloop' marks its termination.  COUNT defaults to 1024, and
+     '.long' and '.ulong' align the result on a longword boundary;
+     'xlong' does not.
+
+'.loop [COUNT]'
+'.break [CONDITION]'
+'.endloop'
+     Repeatedly assemble a block of code.  '.loop' begins the block, and
+     '.endloop' marks its termination.  COUNT defaults to 1024, and
      indicates the number of times the block should be repeated.
-     `.break' terminates the loop so that assembly begins after the
-     `.endloop' directive.  The optional CONDITION will cause the loop
+     '.break' terminates the loop so that assembly begins after the
+     '.endloop' directive.  The optional CONDITION will cause the loop
      to terminate only if it evaluates to zero.
 
-`MACRO_NAME .macro [PARAM1][,...PARAM_N]'
-`[.mexit]'
-`.endm'
+'MACRO_NAME .macro [PARAM1][,...PARAM_N]'
+'[.mexit]'
+'.endm'
      See the section on macros for more explanation (*Note
      TIC54X-Macros::.
 
-`.mlib "FILENAME" | FILENAME'
+'.mlib "FILENAME" | FILENAME'
      Load the macro library FILENAME.  FILENAME must be an archived
-     library (BFD ar-compatible) of text files, expected to contain
-     only macro definitions.   The standard include search path is used.
+     library (BFD ar-compatible) of text files, expected to contain only
+     macro definitions.  The standard include search path is used.
 
-`.mlist'
-`.mnolist'
+'.mlist'
+'.mnolist'
      Control whether to include macro and loop block expansions in the
      listing output.  Ignored.
 
-`.mmregs'
+'.mmregs'
      Define global symbolic names for the 'c54x registers.  Supposedly
-     equivalent to executing `.set' directives for each register with
+     equivalent to executing '.set' directives for each register with
      its memory-mapped value, but in reality is provided only for
      compatibility and does nothing.
 
-`.newblock'
+'.newblock'
      This directive resets any TIC54X local labels currently defined.
-     Normal `as' local labels are unaffected.
+     Normal 'as' local labels are unaffected.
 
-`.option OPTION_LIST'
+'.option OPTION_LIST'
      Set listing options.  Ignored.
 
-`.sblock "SECTION_NAME" | SECTION_NAME [,"NAME_N" | NAME_N]'
+'.sblock "SECTION_NAME" | SECTION_NAME [,"NAME_N" | NAME_N]'
      Designate SECTION_NAME for blocking.  Blocking guarantees that a
      section will start on a page boundary (128 words) if it would
      otherwise cross a page boundary.  Only initialized sections may be
      designated with this directive.  See also *Note TIC54X-Block::.
 
-`.sect "SECTION_NAME"'
+'.sect "SECTION_NAME"'
      Define a named initialized section and make it the current section.
 
-`SYMBOL .set "VALUE"'
-`SYMBOL .equ "VALUE"'
+'SYMBOL .set "VALUE"'
+'SYMBOL .equ "VALUE"'
      Equate a constant VALUE to a SYMBOL, which is placed in the symbol
      table.  SYMBOL may not be previously defined.
 
-`.space SIZE_IN_BITS'
-`.bes SIZE_IN_BITS'
+'.space SIZE_IN_BITS'
+'.bes SIZE_IN_BITS'
      Reserve the given number of bits in the current section and
-     zero-fill them.  If a label is used with `.space', it points to the
-     *first* word reserved.  With `.bes', the label points to the
-     *last* word reserved.
+     zero-fill them.  If a label is used with '.space', it points to the
+     *first* word reserved.  With '.bes', the label points to the *last*
+     word reserved.
 
-`.sslist'
-`.ssnolist'
-     Controls the inclusion of subsym replacement in the listing
-     output.  Ignored.
+'.sslist'
+'.ssnolist'
+     Controls the inclusion of subsym replacement in the listing output.
+     Ignored.
 
-`.string "STRING" [,...,"STRING_N"]'
-`.pstring "STRING" [,...,"STRING_N"]'
+'.string "STRING" [,...,"STRING_N"]'
+'.pstring "STRING" [,...,"STRING_N"]'
      Place 8-bit characters from STRING into the current section.
-     `.string' zero-fills the upper 8 bits of each word, while
-     `.pstring' puts two characters into each word, filling the
+     '.string' zero-fills the upper 8 bits of each word, while
+     '.pstring' puts two characters into each word, filling the
      most-significant bits first.  Unused space is zero-filled.  If a
      label is used, it points to the first word initialized.
 
-`[STAG] .struct [OFFSET]'
-`[NAME_1] element [COUNT_1]'
-`[NAME_2] element [COUNT_2]'
-`[TNAME] .tag STAGX [TCOUNT]'
-`...'
-`[NAME_N] element [COUNT_N]'
-`[SSIZE] .endstruct'
-`LABEL .tag [STAG]'
+'[STAG] .struct [OFFSET]'
+'[NAME_1] element [COUNT_1]'
+'[NAME_2] element [COUNT_2]'
+'[TNAME] .tag STAGX [TCOUNT]'
+'...'
+'[NAME_N] element [COUNT_N]'
+'[SSIZE] .endstruct'
+'LABEL .tag [STAG]'
      Assign symbolic offsets to the elements of a structure.  STAG
      defines a symbol to use to reference the structure.  OFFSET
      indicates a starting value to use for the first element
@@ -18381,62 +18207,62 @@ File: as.info,  Node: TIC54X-Directives,  Next: TIC54X-Macros,  Prev: TIC54X-Ext
      a named offset, NAME, which is a symbol assigned the value of the
      element's offset into the structure.  If STAG is missing, these
      become global symbols.  COUNT adjusts the offset that many times,
-     as if `element' were an array.  `element' may be one of `.byte',
-     `.word', `.long', `.float', or any equivalent of those, and the
-     structure offset is adjusted accordingly.  `.field' and `.string'
-     are also allowed; the size of `.field' is one bit, and `.string'
-     is considered to be one word in size.  Only element descriptors,
-     structure/union tags, `.align' and conditional assembly directives
-     are allowed within `.struct'/`.endstruct'.  `.align' aligns member
+     as if 'element' were an array.  'element' may be one of '.byte',
+     '.word', '.long', '.float', or any equivalent of those, and the
+     structure offset is adjusted accordingly.  '.field' and '.string'
+     are also allowed; the size of '.field' is one bit, and '.string' is
+     considered to be one word in size.  Only element descriptors,
+     structure/union tags, '.align' and conditional assembly directives
+     are allowed within '.struct'/'.endstruct'.  '.align' aligns member
      offsets to word boundaries only.  SSIZE, if provided, will always
      be assigned the size of the structure.
 
-     The `.tag' directive, in addition to being used to define a
+     The '.tag' directive, in addition to being used to define a
      structure/union element within a structure, may be used to apply a
      structure to a symbol.  Once applied to LABEL, the individual
      structure elements may be applied to LABEL to produce the desired
      offsets using LABEL as the structure base.
 
-`.tab'
+'.tab'
      Set the tab size in the output listing.  Ignored.
 
-`[UTAG] .union'
-`[NAME_1] element [COUNT_1]'
-`[NAME_2] element [COUNT_2]'
-`[TNAME] .tag UTAGX[,TCOUNT]'
-`...'
-`[NAME_N] element [COUNT_N]'
-`[USIZE] .endstruct'
-`LABEL .tag [UTAG]'
-     Similar to `.struct', but the offset after each element is reset to
+'[UTAG] .union'
+'[NAME_1] element [COUNT_1]'
+'[NAME_2] element [COUNT_2]'
+'[TNAME] .tag UTAGX[,TCOUNT]'
+'...'
+'[NAME_N] element [COUNT_N]'
+'[USIZE] .endstruct'
+'LABEL .tag [UTAG]'
+     Similar to '.struct', but the offset after each element is reset to
      zero, and the USIZE is set to the maximum of all defined elements.
      Starting offset for the union is always zero.
 
-`[SYMBOL] .usect "SECTION_NAME", SIZE, [,[BLOCKING_FLAG] [,ALIGNMENT_FLAG]]'
+'[SYMBOL] .usect "SECTION_NAME", SIZE, [,[BLOCKING_FLAG] [,ALIGNMENT_FLAG]]'
      Reserve space for variables in a named, uninitialized section
-     (similar to .bss).  `.usect' allows definitions sections
+     (similar to .bss).  '.usect' allows definitions sections
      independent of .bss.  SYMBOL points to the first location reserved
      by this allocation.  The symbol may be used as a variable name.
      SIZE is the allocated size in words.  BLOCKING_FLAG indicates
-     whether to block this section on a page boundary (128 words)
-     (*note TIC54X-Block::).  ALIGNMENT FLAG indicates whether the
-     section should be longword-aligned.
+     whether to block this section on a page boundary (128 words) (*note
+     TIC54X-Block::).  ALIGNMENT FLAG indicates whether the section
+     should be longword-aligned.
 
-`.var SYM[,..., SYM_N]'
+'.var SYM[,..., SYM_N]'
      Define a subsym to be a local variable within a macro.  See *Note
      TIC54X-Macros::.
 
-`.version VERSION'
+'.version VERSION'
      Set which processor to build instructions for.  Though the
      following values are accepted, the op is ignored.
-    `541'
-    `542'
-    `543'
-    `545'
-    `545LP'
-    `546LP'
-    `548'
-    `549'
+     '541'
+     '542'
+     '543'
+     '545'
+     '545LP'
+     '546LP'
+     '548'
+     '549'
 
 
 File: as.info,  Node: TIC54X-Macros,  Next: TIC54X-MMRegs,  Prev: TIC54X-Directives,  Up: TIC54X-Dependent
@@ -18447,58 +18273,57 @@ File: as.info,  Node: TIC54X-Macros,  Next: TIC54X-MMRegs,  Prev: TIC54X-Directi
 Macros do not require explicit dereferencing of arguments (i.e., \ARG).
 
    During macro expansion, the macro parameters are converted to
-subsyms.  If the number of arguments passed the macro invocation
-exceeds the number of parameters defined, the last parameter is
-assigned the string equivalent of all remaining arguments.  If fewer
-arguments are given than parameters, the missing parameters are
-assigned empty strings.  To include a comma in an argument, you must
-enclose the argument in quotes.
+subsyms.  If the number of arguments passed the macro invocation exceeds
+the number of parameters defined, the last parameter is assigned the
+string equivalent of all remaining arguments.  If fewer arguments are
+given than parameters, the missing parameters are assigned empty
+strings.  To include a comma in an argument, you must enclose the
+argument in quotes.
 
    The following built-in subsym functions allow examination of the
 string value of subsyms (or ordinary strings).  The arguments are
 strings unless otherwise indicated (subsyms passed as args will be
 replaced by the strings they represent).
-``$symlen(STR)''
+'$symlen(STR)'
      Returns the length of STR.
 
-``$symcmp(STR1,STR2)''
+'$symcmp(STR1,STR2)'
      Returns 0 if STR1 == STR2, non-zero otherwise.
 
-``$firstch(STR,CH)''
+'$firstch(STR,CH)'
      Returns index of the first occurrence of character constant CH in
      STR.
 
-``$lastch(STR,CH)''
+'$lastch(STR,CH)'
      Returns index of the last occurrence of character constant CH in
      STR.
 
-``$isdefed(SYMBOL)''
+'$isdefed(SYMBOL)'
      Returns zero if the symbol SYMBOL is not in the symbol table,
      non-zero otherwise.
 
-``$ismember(SYMBOL,LIST)''
+'$ismember(SYMBOL,LIST)'
      Assign the first member of comma-separated string LIST to SYMBOL;
-     LIST is reassigned the remainder of the list.  Returns zero if
-     LIST is a null string.  Both arguments must be subsyms.
+     LIST is reassigned the remainder of the list.  Returns zero if LIST
+     is a null string.  Both arguments must be subsyms.
 
-``$iscons(EXPR)''
-     Returns 1 if string EXPR is binary, 2 if octal, 3 if hexadecimal,
-     4 if a character, 5 if decimal, and zero if not an integer.
+'$iscons(EXPR)'
+     Returns 1 if string EXPR is binary, 2 if octal, 3 if hexadecimal, 4
+     if a character, 5 if decimal, and zero if not an integer.
 
-``$isname(NAME)''
+'$isname(NAME)'
      Returns 1 if NAME is a valid symbol name, zero otherwise.
 
-``$isreg(REG)''
+'$isreg(REG)'
      Returns 1 if REG is a valid predefined register name (AR0-AR7
      only).
 
-``$structsz(STAG)''
+'$structsz(STAG)'
      Returns the size of the structure or union represented by STAG.
 
-``$structacc(STAG)''
+'$structacc(STAG)'
      Returns the reference point of the structure or union represented
-     by STAG.   Always returns zero.
-
+     by STAG.  Always returns zero.
 
 
 File: as.info,  Node: TIC54X-MMRegs,  Next: TIC54X-Syntax,  Prev: TIC54X-Macros,  Up: TIC54X-Dependent
@@ -18508,7 +18333,6 @@ File: as.info,  Node: TIC54X-MMRegs,  Next: TIC54X-Syntax,  Prev: TIC54X-Macros,
 
 The following symbols are recognized as memory-mapped registers:
 
-
 
 File: as.info,  Node: TIC54X-Syntax,  Prev: TIC54X-MMRegs,  Up: TIC54X-Dependent
 
@@ -18525,15 +18349,15 @@ File: as.info,  Node: TIC54X-Chars,  Up: TIC54X-Syntax
 9.42.12.1 Special Characters
 ............................
 
-The presence of a `;' appearing anywhere on a line indicates the start
+The presence of a ';' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The presence of an asterisk (`*') at the start of a line also
+   The presence of an asterisk ('*') at the start of a line also
 indicates a comment that extends to the end of that line.
 
    The TIC54X assembler does not currently support a line separator
@@ -18557,71 +18381,70 @@ File: as.info,  Node: TIC6X Options,  Next: TIC6X Syntax,  Up: TIC6X-Dependent
 9.43.1 TIC6X Options
 --------------------
 
-`-march=ARCH'
-     Enable (only) instructions from architecture ARCH.  By default,
-     all instructions are permitted.
+'-march=ARCH'
+     Enable (only) instructions from architecture ARCH.  By default, all
+     instructions are permitted.
 
-     The following values of ARCH are accepted: `c62x', `c64x',
-     `c64x+', `c67x', `c67x+', `c674x'.
+     The following values of ARCH are accepted: 'c62x', 'c64x', 'c64x+',
+     'c67x', 'c67x+', 'c674x'.
 
-`-mdsbt'
-`-mno-dsbt'
-     The `-mdsbt' option causes the assembler to generate the
-     `Tag_ABI_DSBT' attribute with a value of 1, indicating that the
-     code is using DSBT addressing.  The `-mno-dsbt' option, the
+'-mdsbt'
+'-mno-dsbt'
+     The '-mdsbt' option causes the assembler to generate the
+     'Tag_ABI_DSBT' attribute with a value of 1, indicating that the
+     code is using DSBT addressing.  The '-mno-dsbt' option, the
      default, causes the tag to have a value of 0, indicating that the
      code does not use DSBT addressing.  The linker will emit a warning
      if objects of different type (DSBT and non-DSBT) are linked
      together.
 
-`-mpid=no'
-`-mpid=near'
-`-mpid=far'
-     The `-mpid=' option causes the assembler to generate the
-     `Tag_ABI_PID' attribute with a value indicating the form of data
-     addressing used by the code.  `-mpid=no', the default, indicates
-     position-dependent data addressing, `-mpid=near' indicates
+'-mpid=no'
+'-mpid=near'
+'-mpid=far'
+     The '-mpid=' option causes the assembler to generate the
+     'Tag_ABI_PID' attribute with a value indicating the form of data
+     addressing used by the code.  '-mpid=no', the default, indicates
+     position-dependent data addressing, '-mpid=near' indicates
      position-independent addressing with GOT accesses using near DP
-     addressing, and `-mpid=far' indicates position-independent
+     addressing, and '-mpid=far' indicates position-independent
      addressing with GOT accesses using far DP addressing.  The linker
      will emit a warning if objects built with different settings of
      this option are linked together.
 
-`-mpic'
-`-mno-pic'
-     The `-mpic' option causes the assembler to generate the
-     `Tag_ABI_PIC' attribute with a value of 1, indicating that the
-     code is using position-independent code addressing,  The
-     `-mno-pic' option, the default, causes the tag to have a value of
-     0, indicating position-dependent code addressing.  The linker will
+'-mpic'
+'-mno-pic'
+     The '-mpic' option causes the assembler to generate the
+     'Tag_ABI_PIC' attribute with a value of 1, indicating that the code
+     is using position-independent code addressing, The '-mno-pic'
+     option, the default, causes the tag to have a value of 0,
+     indicating position-dependent code addressing.  The linker will
      emit a warning if objects of different type (position-dependent and
      position-independent) are linked together.
 
-`-mbig-endian'
-`-mlittle-endian'
+'-mbig-endian'
+'-mlittle-endian'
      Generate code for the specified endianness.  The default is
      little-endian.
 
-
 
 File: as.info,  Node: TIC6X Syntax,  Next: TIC6X Directives,  Prev: TIC6X Options,  Up: TIC6X-Dependent
 
 9.43.2 TIC6X Syntax
 -------------------
 
-The presence of a `;' on a line indicates the start of a comment that
-extends to the end of the current line.  If a `#' or `*' appears as the
-first character of a line, the whole line is treated as a comment.
-Note that 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::).
+The presence of a ';' on a line indicates the start of a comment that
+extends to the end of the current line.  If a '#' or '*' appears as the
+first character of a line, the whole line is treated as a comment.  Note
+that 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::).
 
-   The `@' character can be used instead of a newline to separate
+   The '@' character can be used instead of a newline to separate
 statements.
 
    Instruction, register and functional unit names are case-insensitive.
-`as' requires fully-specified functional unit names, such as `.S1',
-`.L1X' or `.D1T2', on all instructions using a functional unit.
+'as' requires fully-specified functional unit names, such as '.S1',
+'.L1X' or '.D1T2', on all instructions using a functional unit.
 
    For some instructions, there may be syntactic ambiguity between
 register or functional unit names and the names of labels or other
@@ -18635,63 +18458,62 @@ File: as.info,  Node: TIC6X Directives,  Prev: TIC6X Syntax,  Up: TIC6X-Dependen
 9.43.3 TIC6X Directives
 -----------------------
 
-Directives controlling the set of instructions accepted by the
-assembler have effect for instructions between the directive and any
-subsequent directive overriding it.
+Directives controlling the set of instructions accepted by the assembler
+have effect for instructions between the directive and any subsequent
+directive overriding it.
 
-`.arch ARCH'
-     This has the same effect as `-march=ARCH'.
+'.arch ARCH'
+     This has the same effect as '-march=ARCH'.
 
-`.cantunwind'
+'.cantunwind'
      Prevents unwinding through the current function.  No personality
      routine or exception table data is required or permitted.
 
      If this is not specified then frame unwinding information will be
-     constructed from CFI directives. *note CFI directives::.
+     constructed from CFI directives.  *note CFI directives::.
 
-`.c6xabi_attribute TAG, VALUE'
+'.c6xabi_attribute TAG, VALUE'
      Set the C6000 EABI build attribute TAG to VALUE.
 
-     The TAG is either an attribute number or one of `Tag_ISA',
-     `Tag_ABI_wchar_t', `Tag_ABI_stack_align_needed',
-     `Tag_ABI_stack_align_preserved', `Tag_ABI_DSBT', `Tag_ABI_PID',
-     `Tag_ABI_PIC', `TAG_ABI_array_object_alignment',
-     `TAG_ABI_array_object_align_expected', `Tag_ABI_compatibility' and
-     `Tag_ABI_conformance'.  The VALUE is either a `number',
-     `"string"', or `number, "string"' depending on the tag.
+     The TAG is either an attribute number or one of 'Tag_ISA',
+     'Tag_ABI_wchar_t', 'Tag_ABI_stack_align_needed',
+     'Tag_ABI_stack_align_preserved', 'Tag_ABI_DSBT', 'Tag_ABI_PID',
+     'Tag_ABI_PIC', 'TAG_ABI_array_object_alignment',
+     'TAG_ABI_array_object_align_expected', 'Tag_ABI_compatibility' and
+     'Tag_ABI_conformance'.  The VALUE is either a 'number', '"string"',
+     or 'number, "string"' depending on the tag.
 
-`.ehtype SYMBOL'
+'.ehtype SYMBOL'
      Output an exception type table reference to SYMBOL.
 
-`.endp'
+'.endp'
      Marks the end of and exception table or function.  If preceeded by
-     a `.handlerdata' directive then this also switched back to the
+     a '.handlerdata' directive then this also switched back to the
      previous text section.
 
-`.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 `.endp' directive will be added to the exception
+     directive and the '.endp' directive will be added to the exception
      table entry.
 
-     Must be preceded by a CFI block containing a `.cfi_lsda' directive.
+     Must be preceded by a CFI block containing a '.cfi_lsda' directive.
 
-`.nocmp'
+'.nocmp'
      Disallow use of C64x+ compact instructions in the current text
      section.
 
-`.personalityindex INDEX'
+'.personalityindex INDEX'
      Sets the personality routine for the current function to the ABI
      specified compact routine number INDEX
 
-`.personality NAME'
+'.personality NAME'
      Sets the personality routine for the current function to NAME.
 
-`.scomm SYMBOL, SIZE, ALIGN'
-     Like `.comm', creating a common symbol SYMBOL with size SIZE and
-     alignment ALIGN, but unlike when using `.comm', this symbol will
-     be placed into the small BSS section by the linker.
-
+'.scomm SYMBOL, SIZE, ALIGN'
+     Like '.comm', creating a common symbol SYMBOL with size SIZE and
+     alignment ALIGN, but unlike when using '.comm', this symbol will be
+     placed into the small BSS section by the linker.
 
 
 File: as.info,  Node: TILE-Gx-Dependent,  Next: TILEPro-Dependent,  Prev: TIC6X-Dependent,  Up: Machine Dependencies
@@ -18713,22 +18535,21 @@ File: as.info,  Node: TILE-Gx Options,  Next: TILE-Gx Syntax,  Up: TILE-Gx-Depen
 
 The following table lists all available TILE-Gx specific options:
 
-`-m32 | -m64'
+'-m32 | -m64'
      Select the word size, either 32 bits or 64 bits.
 
-`-EB | -EL'
+'-EB | -EL'
      Select the endianness, either big-endian (-EB) or little-endian
      (-EL).
 
-
 
 File: as.info,  Node: TILE-Gx Syntax,  Next: TILE-Gx Directives,  Prev: TILE-Gx Options,  Up: TILE-Gx-Dependent
 
 9.44.2 Syntax
 -------------
 
-Block comments are delimited by `/*' and `*/'.  End of line comments
-may be introduced by `#'.
+Block comments are delimited by '/*' and '*/'.  End of line comments may
+be introduced by '#'.
 
    Instructions consist of a leading opcode or macro name followed by
 whitespace and an optional comma-separated list of operands:
@@ -18738,26 +18559,26 @@ whitespace and an optional comma-separated list of operands:
    Instructions must be separated by a newline or semicolon.
 
    There are two ways to write code: either write naked instructions,
-which the assembler is free to combine into VLIW bundles, or specify
-the VLIW bundles explicitly.
+which the assembler is free to combine into VLIW bundles, or specify the
+VLIW bundles explicitly.
 
    Bundles are specified using curly braces:
 
      { ADD r3,r4,r5 ; ADD r7,r8,r9 ; LW r10,r11 }
 
-   A bundle can span multiple lines. If you want to put multiple
-instructions on a line, whether in a bundle or not, you need to
-separate them with semicolons as in this example.
+   A bundle can span multiple lines.  If you want to put multiple
+instructions on a line, whether in a bundle or not, you need to separate
+them with semicolons as in this example.
 
    A bundle may contain one or more instructions, up to the limit
-specified by the ISA (currently three). If fewer instructions are
+specified by the ISA (currently three).  If fewer instructions are
 specified than the hardware supports in a bundle, the assembler inserts
-`fnop' instructions automatically.
+'fnop' instructions automatically.
 
    The assembler will prefer to preserve the ordering of instructions
 within the bundle, putting the first instruction in a lower-numbered
 pipeline than the next one, etc.  This fact, combined with the optional
-use of explicit `fnop' or `nop' instructions, allows precise control
+use of explicit 'fnop' or 'nop' instructions, allows precise control
 over which pipeline executes each instruction.
 
    If the instructions cannot be bundled in the listed order, the
@@ -18767,9 +18588,9 @@ reports an error.
 
    The assembler does not yet auto-bundle (automatically combine
 multiple instructions into one bundle), but it reserves the right to do
-so in the future.  If you want to force an instruction to run by
-itself, put it in a bundle explicitly with curly braces and use `nop'
-instructions (not `fnop') to fill the remaining pipeline slots in that
+so in the future.  If you want to force an instruction to run by itself,
+put it in a bundle explicitly with curly braces and use 'nop'
+instructions (not 'fnop') to fill the remaining pipeline slots in that
 bundle.
 
 * Menu:
@@ -18785,7 +18606,7 @@ File: as.info,  Node: TILE-Gx Opcodes,  Next: TILE-Gx Registers,  Up: TILE-Gx Sy
 .....................
 
 For a complete list of opcodes and descriptions of their semantics, see
-`TILE-Gx Instruction Set Architecture', available upon request at
+'TILE-Gx Instruction Set Architecture', available upon request at
 www.tilera.com.
 
 
@@ -18795,44 +18616,43 @@ File: as.info,  Node: TILE-Gx Registers,  Next: TILE-Gx Modifiers,  Prev: TILE-G
 .......................
 
 General-purpose registers are represented by predefined symbols of the
-form `rN', where N represents a number between `0' and `63'.  However,
+form 'rN', where N represents a number between '0' and '63'.  However,
 the following registers have canonical names that must be used instead:
 
-`r54'
+'r54'
      sp
 
-`r55'
+'r55'
      lr
 
-`r56'
+'r56'
      sn
 
-`r57'
+'r57'
      idn0
 
-`r58'
+'r58'
      idn1
 
-`r59'
+'r59'
      udn0
 
-`r60'
+'r60'
      udn1
 
-`r61'
+'r61'
      udn2
 
-`r62'
+'r62'
      udn3
 
-`r63'
+'r63'
      zero
 
-
    The assembler will emit a warning if a numeric name is used instead
-of the non-numeric name.  The `.no_require_canonical_reg_names'
+of the non-numeric name.  The '.no_require_canonical_reg_names'
 assembler pseudo-op turns off this warning.
-`.require_canonical_reg_names' turns it back on.
+'.require_canonical_reg_names' turns it back on.
 
 
 File: as.info,  Node: TILE-Gx Modifiers,  Prev: TILE-Gx Registers,  Up: TILE-Gx Syntax
@@ -18847,28 +18667,35 @@ TILE-Gx instruction operands.  The general syntax is the following:
 
    The following modifiers are supported:
 
-`hw0'
+'hw0'
+
      This modifier is used to load bits 0-15 of the symbol's address.
 
-`hw1'
+'hw1'
+
      This modifier is used to load bits 16-31 of the symbol's address.
 
-`hw2'
+'hw2'
+
      This modifier is used to load bits 32-47 of the symbol's address.
 
-`hw3'
+'hw3'
+
      This modifier is used to load bits 48-63 of the symbol's address.
 
-`hw0_last'
-     This modifier yields the same value as `hw0', but it also checks
+'hw0_last'
+
+     This modifier yields the same value as 'hw0', but it also checks
      that the value does not overflow.
 
-`hw1_last'
-     This modifier yields the same value as `hw1', but it also checks
+'hw1_last'
+
+     This modifier yields the same value as 'hw1', but it also checks
      that the value does not overflow.
 
-`hw2_last'
-     This modifier yields the same value as `hw2', but it also checks
+'hw2_last'
+
+     This modifier yields the same value as 'hw2', but it also checks
      that the value does not overflow.
 
      A 48-bit symbolic value is constructed by using the following
@@ -18878,135 +18705,153 @@ TILE-Gx instruction operands.  The general syntax is the following:
           shl16insli r0, r0, hw1(sym)
           shl16insli r0, r0, hw0(sym)
 
-`hw0_got'
+'hw0_got'
+
      This modifier is used to load bits 0-15 of the symbol's offset in
      the GOT entry corresponding to the symbol.
 
-`hw0_last_got'
-     This modifier yields the same value as `hw0_got', but it also
+'hw0_last_got'
+
+     This modifier yields the same value as 'hw0_got', but it also
      checks that the value does not overflow.
 
-`hw1_last_got'
+'hw1_last_got'
+
      This modifier is used to load bits 16-31 of the symbol's offset in
      the GOT entry corresponding to the symbol, and it also checks that
      the value does not overflow.
 
-`plt'
-     This modifier is used for function symbols.  It causes a
-     _procedure linkage table_, an array of code stubs, to be created
-     at the time the shared object is created or linked against,
-     together with a global offset table entry.  The value is a
-     pc-relative offset to the corresponding stub code in the procedure
-     linkage table.  This arrangement causes the run-time symbol
-     resolver to be called to look up and set the value of the symbol
-     the first time the function is called (at latest; depending
-     environment variables).  It is only safe to leave the symbol
-     unresolved this way if all references are function calls.
-
-`hw0_plt'
+'plt'
+
+     This modifier is used for function symbols.  It causes a _procedure
+     linkage table_, an array of code stubs, to be created at the time
+     the shared object is created or linked against, together with a
+     global offset table entry.  The value is a pc-relative offset to
+     the corresponding stub code in the procedure linkage table.  This
+     arrangement causes the run-time symbol resolver to be called to
+     look up and set the value of the symbol the first time the function
+     is called (at latest; depending environment variables).  It is only
+     safe to leave the symbol unresolved this way if all references are
+     function calls.
+
+'hw0_plt'
+
      This modifier is used to load bits 0-15 of the pc-relative address
      of a plt entry.
 
-`hw1_plt'
-     This modifier is used to load bits 16-31 of the pc-relative
-     address of a plt entry.
+'hw1_plt'
+
+     This modifier is used to load bits 16-31 of the pc-relative address
+     of a plt entry.
+
+'hw1_last_plt'
 
-`hw1_last_plt'
-     This modifier yields the same value as `hw1_plt', but it also
+     This modifier yields the same value as 'hw1_plt', but it also
      checks that the value does not overflow.
 
-`hw2_last_plt'
-     This modifier is used to load bits 32-47 of the pc-relative
-     address of a plt entry, and it also checks that the value does not
+'hw2_last_plt'
+
+     This modifier is used to load bits 32-47 of the pc-relative address
+     of a plt entry, and it also checks that the value does not
      overflow.
 
-`hw0_tls_gd'
+'hw0_tls_gd'
+
      This modifier is used to load bits 0-15 of the offset of the GOT
      entry of the symbol's TLS descriptor, to be used for
      general-dynamic TLS accesses.
 
-`hw0_last_tls_gd'
-     This modifier yields the same value as `hw0_tls_gd', but it also
+'hw0_last_tls_gd'
+
+     This modifier yields the same value as 'hw0_tls_gd', but it also
      checks that the value does not overflow.
 
-`hw1_last_tls_gd'
+'hw1_last_tls_gd'
+
      This modifier is used to load bits 16-31 of the offset of the GOT
      entry of the symbol's TLS descriptor, to be used for
      general-dynamic TLS accesses.  It also checks that the value does
      not overflow.
 
-`hw0_tls_ie'
+'hw0_tls_ie'
+
      This modifier is used to load bits 0-15 of the offset of the GOT
      entry containing the offset of the symbol's address from the TCB,
      to be used for initial-exec TLS accesses.
 
-`hw0_last_tls_ie'
-     This modifier yields the same value as `hw0_tls_ie', but it also
+'hw0_last_tls_ie'
+
+     This modifier yields the same value as 'hw0_tls_ie', but it also
      checks that the value does not overflow.
 
-`hw1_last_tls_ie'
+'hw1_last_tls_ie'
+
      This modifier is used to load bits 16-31 of the offset of the GOT
      entry containing the offset of the symbol's address from the TCB,
      to be used for initial-exec TLS accesses.  It also checks that the
      value does not overflow.
 
-`hw0_tls_le'
+'hw0_tls_le'
+
      This modifier is used to load bits 0-15 of the offset of the
      symbol's address from the TCB, to be used for local-exec TLS
      accesses.
 
-`hw0_last_tls_le'
-     This modifier yields the same value as `hw0_tls_le', but it also
+'hw0_last_tls_le'
+
+     This modifier yields the same value as 'hw0_tls_le', but it also
      checks that the value does not overflow.
 
-`hw1_last_tls_le'
+'hw1_last_tls_le'
+
      This modifier is used to load bits 16-31 of the offset of the
      symbol's address from the TCB, to be used for local-exec TLS
      accesses.  It also checks that the value does not overflow.
 
-`tls_gd_call'
+'tls_gd_call'
+
      This modifier is used to tag an instrution as the "call" part of a
      calling sequence for a TLS GD reference of its operand.
 
-`tls_gd_add'
+'tls_gd_add'
+
      This modifier is used to tag an instruction as the "add" part of a
      calling sequence for a TLS GD reference of its operand.
 
-`tls_ie_load'
+'tls_ie_load'
+
      This modifier is used to tag an instruction as the "load" part of a
      calling sequence for a TLS IE reference of its operand.
 
-
 
 File: as.info,  Node: TILE-Gx Directives,  Prev: TILE-Gx Syntax,  Up: TILE-Gx-Dependent
 
 9.44.3 TILE-Gx Directives
 -------------------------
 
-`.align EXPRESSION [, EXPRESSION]'
+'.align EXPRESSION [, EXPRESSION]'
      This is the generic .ALIGN directive.  The first argument is the
      requested alignment in bytes.
 
-`.allow_suspicious_bundles'
+'.allow_suspicious_bundles'
      Turns on error checking for combinations of instructions in a
      bundle that probably indicate a programming error.  This is on by
      default.
 
-`.no_allow_suspicious_bundles'
+'.no_allow_suspicious_bundles'
      Turns off error checking for combinations of instructions in a
      bundle that probably indicate a programming error.
 
-`.require_canonical_reg_names'
+'.require_canonical_reg_names'
      Require that canonical register names be used, and emit a warning
      if the numeric names are used.  This is on by default.
 
-`.no_require_canonical_reg_names'
+'.no_require_canonical_reg_names'
      Permit the use of numeric names for registers that have canonical
      names.
 
-
 
-File: as.info,  Node: TILEPro-Dependent,  Next: V850-Dependent,  Prev: TILE-Gx-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: TILEPro-Dependent,  Next: Z80-Dependent,  Prev: TILE-Gx-Dependent,  Up: Machine Dependencies
 
 9.45 TILEPro Dependent Features
 ===============================
@@ -19023,7 +18868,7 @@ File: as.info,  Node: TILEPro Options,  Next: TILEPro Syntax,  Up: TILEPro-Depen
 9.45.1 Options
 --------------
 
-`as' has no machine-dependent command-line options for TILEPro.
+'as' has no machine-dependent command-line options for TILEPro.
 
 
 File: as.info,  Node: TILEPro Syntax,  Next: TILEPro Directives,  Prev: TILEPro Options,  Up: TILEPro-Dependent
@@ -19031,8 +18876,8 @@ File: as.info,  Node: TILEPro Syntax,  Next: TILEPro Directives,  Prev: TILEPro
 9.45.2 Syntax
 -------------
 
-Block comments are delimited by `/*' and `*/'.  End of line comments
-may be introduced by `#'.
+Block comments are delimited by '/*' and '*/'.  End of line comments may
+be introduced by '#'.
 
    Instructions consist of a leading opcode or macro name followed by
 whitespace and an optional comma-separated list of operands:
@@ -19042,26 +18887,26 @@ whitespace and an optional comma-separated list of operands:
    Instructions must be separated by a newline or semicolon.
 
    There are two ways to write code: either write naked instructions,
-which the assembler is free to combine into VLIW bundles, or specify
-the VLIW bundles explicitly.
+which the assembler is free to combine into VLIW bundles, or specify the
+VLIW bundles explicitly.
 
    Bundles are specified using curly braces:
 
      { ADD r3,r4,r5 ; ADD r7,r8,r9 ; LW r10,r11 }
 
-   A bundle can span multiple lines. If you want to put multiple
-instructions on a line, whether in a bundle or not, you need to
-separate them with semicolons as in this example.
+   A bundle can span multiple lines.  If you want to put multiple
+instructions on a line, whether in a bundle or not, you need to separate
+them with semicolons as in this example.
 
    A bundle may contain one or more instructions, up to the limit
-specified by the ISA (currently three). If fewer instructions are
+specified by the ISA (currently three).  If fewer instructions are
 specified than the hardware supports in a bundle, the assembler inserts
-`fnop' instructions automatically.
+'fnop' instructions automatically.
 
    The assembler will prefer to preserve the ordering of instructions
 within the bundle, putting the first instruction in a lower-numbered
 pipeline than the next one, etc.  This fact, combined with the optional
-use of explicit `fnop' or `nop' instructions, allows precise control
+use of explicit 'fnop' or 'nop' instructions, allows precise control
 over which pipeline executes each instruction.
 
    If the instructions cannot be bundled in the listed order, the
@@ -19071,9 +18916,9 @@ reports an error.
 
    The assembler does not yet auto-bundle (automatically combine
 multiple instructions into one bundle), but it reserves the right to do
-so in the future.  If you want to force an instruction to run by
-itself, put it in a bundle explicitly with curly braces and use `nop'
-instructions (not `fnop') to fill the remaining pipeline slots in that
+so in the future.  If you want to force an instruction to run by itself,
+put it in a bundle explicitly with curly braces and use 'nop'
+instructions (not 'fnop') to fill the remaining pipeline slots in that
 bundle.
 
 * Menu:
@@ -19089,7 +18934,7 @@ File: as.info,  Node: TILEPro Opcodes,  Next: TILEPro Registers,  Up: TILEPro Sy
 .....................
 
 For a complete list of opcodes and descriptions of their semantics, see
-`TILE Processor User Architecture Manual', available upon request at
+'TILE Processor User Architecture Manual', available upon request at
 www.tilera.com.
 
 
@@ -19099,43 +18944,42 @@ File: as.info,  Node: TILEPro Registers,  Next: TILEPro Modifiers,  Prev: TILEPr
 .......................
 
 General-purpose registers are represented by predefined symbols of the
-form `rN', where N represents a number between `0' and `63'.  However,
+form 'rN', where N represents a number between '0' and '63'.  However,
 the following registers have canonical names that must be used instead:
 
-`r54'
+'r54'
      sp
 
-`r55'
+'r55'
      lr
 
-`r56'
+'r56'
      sn
 
-`r57'
+'r57'
      idn0
 
-`r58'
+'r58'
      idn1
 
-`r59'
+'r59'
      udn0
 
-`r60'
+'r60'
      udn1
 
-`r61'
+'r61'
      udn2
 
-`r62'
+'r62'
      udn3
 
-`r63'
+'r63'
      zero
 
-
    The assembler will emit a warning if a numeric name is used instead
-of the canonical name.  The `.no_require_canonical_reg_names' assembler
-pseudo-op turns off this warning. `.require_canonical_reg_names' turns
+of the canonical name.  The '.no_require_canonical_reg_names' assembler
+pseudo-op turns off this warning.  '.require_canonical_reg_names' turns
 it back on.
 
 
@@ -19151,152 +18995,173 @@ TILEPro instruction operands.  The general syntax is the following:
 
    The following modifiers are supported:
 
-`lo16'
+'lo16'
+
      This modifier is used to load the low 16 bits of the symbol's
      address, sign-extended to a 32-bit value (sign-extension allows it
      to be range-checked against signed 16 bit immediate operands
      without complaint).
 
-`hi16'
+'hi16'
+
      This modifier is used to load the high 16 bits of the symbol's
      address, also sign-extended to a 32-bit value.
 
-`ha16'
-     `ha16(N)' is identical to `hi16(N)', except if `lo16(N)' is
-     negative it adds one to the `hi16(N)' value. This way `lo16' and
-     `ha16' can be added to create any 32-bit value using `auli'.  For
+'ha16'
+
+     'ha16(N)' is identical to 'hi16(N)', except if 'lo16(N)' is
+     negative it adds one to the 'hi16(N)' value.  This way 'lo16' and
+     'ha16' can be added to create any 32-bit value using 'auli'.  For
      example, here is how you move an arbitrary 32-bit address into r3:
 
           moveli r3, lo16(sym)
           auli r3, r3, ha16(sym)
 
-`got'
+'got'
+
      This modifier is used to load the offset of the GOT entry
      corresponding to the symbol.
 
-`got_lo16'
+'got_lo16'
+
      This modifier is used to load the sign-extended low 16 bits of the
      offset of the GOT entry corresponding to the symbol.
 
-`got_hi16'
+'got_hi16'
+
      This modifier is used to load the sign-extended high 16 bits of the
      offset of the GOT entry corresponding to the symbol.
 
-`got_ha16'
-     This modifier is like `got_hi16', but it adds one if `got_lo16' of
+'got_ha16'
+
+     This modifier is like 'got_hi16', but it adds one if 'got_lo16' of
      the input value is negative.
 
-`plt'
-     This modifier is used for function symbols.  It causes a
-     _procedure linkage table_, an array of code stubs, to be created
-     at the time the shared object is created or linked against,
-     together with a global offset table entry.  The value is a
-     pc-relative offset to the corresponding stub code in the procedure
-     linkage table.  This arrangement causes the run-time symbol
-     resolver to be called to look up and set the value of the symbol
-     the first time the function is called (at latest; depending
-     environment variables).  It is only safe to leave the symbol
-     unresolved this way if all references are function calls.
-
-`tls_gd'
+'plt'
+
+     This modifier is used for function symbols.  It causes a _procedure
+     linkage table_, an array of code stubs, to be created at the time
+     the shared object is created or linked against, together with a
+     global offset table entry.  The value is a pc-relative offset to
+     the corresponding stub code in the procedure linkage table.  This
+     arrangement causes the run-time symbol resolver to be called to
+     look up and set the value of the symbol the first time the function
+     is called (at latest; depending environment variables).  It is only
+     safe to leave the symbol unresolved this way if all references are
+     function calls.
+
+'tls_gd'
+
      This modifier is used to load the offset of the GOT entry of the
      symbol's TLS descriptor, to be used for general-dynamic TLS
      accesses.
 
-`tls_gd_lo16'
+'tls_gd_lo16'
+
      This modifier is used to load the sign-extended low 16 bits of the
      offset of the GOT entry of the symbol's TLS descriptor, to be used
      for general dynamic TLS accesses.
 
-`tls_gd_hi16'
+'tls_gd_hi16'
+
      This modifier is used to load the sign-extended high 16 bits of the
      offset of the GOT entry of the symbol's TLS descriptor, to be used
      for general dynamic TLS accesses.
 
-`tls_gd_ha16'
-     This modifier is like `tls_gd_hi16', but it adds one to the value
-     if `tls_gd_lo16' of the input value is negative.
+'tls_gd_ha16'
+
+     This modifier is like 'tls_gd_hi16', but it adds one to the value
+     if 'tls_gd_lo16' of the input value is negative.
+
+'tls_ie'
 
-`tls_ie'
      This modifier is used to load the offset of the GOT entry
      containing the offset of the symbol's address from the TCB, to be
      used for initial-exec TLS accesses.
 
-`tls_ie_lo16'
+'tls_ie_lo16'
+
      This modifier is used to load the low 16 bits of the offset of the
      GOT entry containing the offset of the symbol's address from the
      TCB, to be used for initial-exec TLS accesses.
 
-`tls_ie_hi16'
+'tls_ie_hi16'
+
      This modifier is used to load the high 16 bits of the offset of the
      GOT entry containing the offset of the symbol's address from the
      TCB, to be used for initial-exec TLS accesses.
 
-`tls_ie_ha16'
-     This modifier is like `tls_ie_hi16', but it adds one to the value
-     if `tls_ie_lo16' of the input value is negative.
+'tls_ie_ha16'
+
+     This modifier is like 'tls_ie_hi16', but it adds one to the value
+     if 'tls_ie_lo16' of the input value is negative.
+
+'tls_le'
 
-`tls_le'
      This modifier is used to load the offset of the symbol's address
      from the TCB, to be used for local-exec TLS accesses.
 
-`tls_le_lo16'
+'tls_le_lo16'
+
      This modifier is used to load the low 16 bits of the offset of the
      symbol's address from the TCB, to be used for local-exec TLS
      accesses.
 
-`tls_le_hi16'
+'tls_le_hi16'
+
      This modifier is used to load the high 16 bits of the offset of the
      symbol's address from the TCB, to be used for local-exec TLS
      accesses.
 
-`tls_le_ha16'
-     This modifier is like `tls_le_hi16', but it adds one to the value
-     if `tls_le_lo16' of the input value is negative.
+'tls_le_ha16'
+
+     This modifier is like 'tls_le_hi16', but it adds one to the value
+     if 'tls_le_lo16' of the input value is negative.
+
+'tls_gd_call'
 
-`tls_gd_call'
      This modifier is used to tag an instrution as the "call" part of a
      calling sequence for a TLS GD reference of its operand.
 
-`tls_gd_add'
+'tls_gd_add'
+
      This modifier is used to tag an instruction as the "add" part of a
      calling sequence for a TLS GD reference of its operand.
 
-`tls_ie_load'
+'tls_ie_load'
+
      This modifier is used to tag an instruction as the "load" part of a
      calling sequence for a TLS IE reference of its operand.
 
-
 
 File: as.info,  Node: TILEPro Directives,  Prev: TILEPro Syntax,  Up: TILEPro-Dependent
 
 9.45.3 TILEPro Directives
 -------------------------
 
-`.align EXPRESSION [, EXPRESSION]'
+'.align EXPRESSION [, EXPRESSION]'
      This is the generic .ALIGN directive.  The first argument is the
      requested alignment in bytes.
 
-`.allow_suspicious_bundles'
+'.allow_suspicious_bundles'
      Turns on error checking for combinations of instructions in a
      bundle that probably indicate a programming error.  This is on by
      default.
 
-`.no_allow_suspicious_bundles'
+'.no_allow_suspicious_bundles'
      Turns off error checking for combinations of instructions in a
      bundle that probably indicate a programming error.
 
-`.require_canonical_reg_names'
+'.require_canonical_reg_names'
      Require that canonical register names be used, and emit a warning
      if the numeric names are used.  This is on by default.
 
-`.no_require_canonical_reg_names'
+'.no_require_canonical_reg_names'
      Permit the use of numeric names for registers that have canonical
      names.
 
-
 
-File: as.info,  Node: Z80-Dependent,  Next: Z8000-Dependent,  Prev: Xtensa-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: Z80-Dependent,  Next: Z8000-Dependent,  Prev: TILEPro-Dependent,  Up: Machine Dependencies
 
 9.46 Z80 Dependent Features
 ===========================
@@ -19315,46 +19180,40 @@ File: as.info,  Node: Z80 Options,  Next: Z80 Syntax,  Up: Z80-Dependent
 9.46.1 Options
 --------------
 
-The Zilog Z80 and Ascii R800 version of `as' have a few machine
+The Zilog Z80 and Ascii R800 version of 'as' have a few machine
 dependent options.
-`-z80'
-     Produce code for the Z80 processor. There are additional options to
-     request warnings and error messages for undocumented instructions.
-
-`-ignore-undocumented-instructions'
-`-Wnud'
+'-z80'
+     Produce code for the Z80 processor.  There are additional options
+     to request warnings and error messages for undocumented
+     instructions.
+'-ignore-undocumented-instructions'
+'-Wnud'
      Silently assemble undocumented Z80-instructions that have been
      adopted as documented R800-instructions.
-
-`-ignore-unportable-instructions'
-`-Wnup'
+'-ignore-unportable-instructions'
+'-Wnup'
      Silently assemble all undocumented Z80-instructions.
-
-`-warn-undocumented-instructions'
-`-Wud'
-     Issue warnings for undocumented Z80-instructions that work on
-     R800, do not assemble other undocumented instructions without
-     warning.
-
-`-warn-unportable-instructions'
-`-Wup'
+'-warn-undocumented-instructions'
+'-Wud'
+     Issue warnings for undocumented Z80-instructions that work on R800,
+     do not assemble other undocumented instructions without warning.
+'-warn-unportable-instructions'
+'-Wup'
      Issue warnings for other undocumented Z80-instructions, do not
      treat any undocumented instructions as errors.
-
-`-forbid-undocumented-instructions'
-`-Fud'
+'-forbid-undocumented-instructions'
+'-Fud'
      Treat all undocumented z80-instructions as errors.
-
-`-forbid-unportable-instructions'
-`-Fup'
+'-forbid-unportable-instructions'
+'-Fup'
      Treat undocumented z80-instructions that do not work on R800 as
      errors.
 
-`-r800'
-     Produce code for the R800 processor. The assembler does not support
-     undocumented instructions for the R800.  In line with common
-     practice, `as' uses Z80 instruction names for the R800 processor,
-     as far as they exist.
+'-r800'
+     Produce code for the R800 processor.  The assembler does not
+     support undocumented instructions for the R800.  In line with
+     common practice, 'as' uses Z80 instruction names for the R800
+     processor, as far as they exist.
 
 
 File: as.info,  Node: Z80 Syntax,  Next: Z80 Floating Point,  Prev: Z80 Options,  Up: Z80-Dependent
@@ -19363,14 +19222,14 @@ File: as.info,  Node: Z80 Syntax,  Next: Z80 Floating Point,  Prev: Z80 Options,
 -------------
 
 The assembler syntax closely follows the 'Z80 family CPU User Manual' by
-Zilog.  In expressions a single `=' may be used as "is equal to"
+Zilog.  In expressions a single '=' may be used as "is equal to"
 comparison operator.
 
-   Suffices can be used to indicate the radix of integer constants; `H'
-or `h' for hexadecimal, `D' or `d' for decimal, `Q', `O', `q' or `o'
-for octal, and `B' for binary.
+   Suffices can be used to indicate the radix of integer constants; 'H'
+or 'h' for hexadecimal, 'D' or 'd' for decimal, 'Q', 'O', 'q' or 'o' for
+octal, and 'B' for binary.
 
-   The suffix `b' denotes a backreference to local label.
+   The suffix 'b' denotes a backreference to local label.
 
 * Menu:
 
@@ -19384,21 +19243,21 @@ File: as.info,  Node: Z80-Chars,  Next: Z80-Regs,  Up: Z80 Syntax
 9.46.2.1 Special Characters
 ...........................
 
-The semicolon `;' is the line comment character;
+The semicolon ';' is the line comment character;
 
-   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 Z80 assembler does not support a line separator character.
 
-   The dollar sign `$' can be used as a prefix for hexadecimal numbers
+   The dollar sign '$' can be used as a prefix for hexadecimal numbers
 and as a symbol denoting the current location counter.
 
-   A backslash `\' is an ordinary character for the Z80 assembler.
+   A backslash '\' is an ordinary character for the Z80 assembler.
 
-   The single quote `'' must be followed by a closing quote. If there
+   The single quote ''' must be followed by a closing quote.  If there
 is one character in between, it is a character constant, otherwise it is
 a string constant.
 
@@ -19409,9 +19268,9 @@ File: as.info,  Node: Z80-Regs,  Next: Z80-Case,  Prev: Z80-Chars,  Up: Z80 Synt
 .......................
 
 The registers are referred to with the letters assigned to them by
-Zilog. In addition `as' recognizes `ixl' and `ixh' as the least and
-most significant octet in `ix', and similarly `iyl' and  `iyh' as parts
-of `iy'.
+Zilog.  In addition 'as' recognizes 'ixl' and 'ixh' as the least and
+most significant octet in 'ix', and similarly 'iyl' and 'iyh' as parts
+of 'iy'.
 
 
 File: as.info,  Node: Z80-Case,  Prev: Z80-Regs,  Up: Z80 Syntax
@@ -19420,10 +19279,10 @@ File: as.info,  Node: Z80-Case,  Prev: Z80-Regs,  Up: Z80 Syntax
 .........................
 
 Upper and lower case are equivalent in register names, opcodes,
-condition codes  and assembler directives.  The case of letters is
-significant in labels and symbol names. The case is also important to
-distinguish the suffix `b' for a backward reference to a local label
-from the suffix `B' for a number in binary notation.
+condition codes and assembler directives.  The case of letters is
+significant in labels and symbol names.  The case is also important to
+distinguish the suffix 'b' for a backward reference to a local label
+from the suffix 'B' for a number in binary notation.
 
 
 File: as.info,  Node: Z80 Floating Point,  Next: Z80 Directives,  Prev: Z80 Syntax,  Up: Z80-Dependent
@@ -19439,51 +19298,50 @@ File: as.info,  Node: Z80 Directives,  Next: Z80 Opcodes,  Prev: Z80 Floating Po
 9.46.4 Z80 Assembler Directives
 -------------------------------
 
-`as' for the Z80 supports some additional directives for compatibility
+'as' for the Z80 supports some additional directives for compatibility
 with other assemblers.
 
-   These are the additional directives in `as' for the Z80:
+   These are the additional directives in 'as' for the Z80:
 
-`db EXPRESSION|STRING[,EXPRESSION|STRING...]'
-`defb EXPRESSION|STRING[,EXPRESSION|STRING...]'
+'db EXPRESSION|STRING[,EXPRESSION|STRING...]'
+'defb EXPRESSION|STRING[,EXPRESSION|STRING...]'
      For each STRING the characters are copied to the object file, for
      each other EXPRESSION the value is stored in one byte.  A warning
      is issued in case of an overflow.
 
-`dw EXPRESSION[,EXPRESSION...]'
-`defw EXPRESSION[,EXPRESSION...]'
+'dw EXPRESSION[,EXPRESSION...]'
+'defw EXPRESSION[,EXPRESSION...]'
      For each EXPRESSION the value is stored in two bytes, ignoring
      overflow.
 
-`d24 EXPRESSION[,EXPRESSION...]'
-`def24 EXPRESSION[,EXPRESSION...]'
+'d24 EXPRESSION[,EXPRESSION...]'
+'def24 EXPRESSION[,EXPRESSION...]'
      For each EXPRESSION the value is stored in three bytes, ignoring
      overflow.
 
-`d32 EXPRESSION[,EXPRESSION...]'
-`def32 EXPRESSION[,EXPRESSION...]'
+'d32 EXPRESSION[,EXPRESSION...]'
+'def32 EXPRESSION[,EXPRESSION...]'
      For each EXPRESSION the value is stored in four bytes, ignoring
      overflow.
 
-`ds COUNT[, VALUE]'
-`defs COUNT[, VALUE]'
-     Fill COUNT bytes in the object file with VALUE, if VALUE is
-     omitted it defaults to zero.
+'ds COUNT[, VALUE]'
+'defs COUNT[, VALUE]'
+     Fill COUNT bytes in the object file with VALUE, if VALUE is omitted
+     it defaults to zero.
 
-`SYMBOL equ EXPRESSION'
-`SYMBOL defl EXPRESSION'
-     These directives set the value of SYMBOL to EXPRESSION. If `equ'
+'SYMBOL equ EXPRESSION'
+'SYMBOL defl EXPRESSION'
+     These directives set the value of SYMBOL to EXPRESSION.  If 'equ'
      is used, it is an error if SYMBOL is already defined.  Symbols
-     defined with `equ' are not protected from redefinition.
+     defined with 'equ' are not protected from redefinition.
 
-`set'
+'set'
      This is a normal instruction on Z80, and not an assembler
      directive.
 
-`psect NAME'
+'psect NAME'
      A synonym for *Note Section::, no second argument should be given.
 
-
 
 File: as.info,  Node: Z80 Opcodes,  Prev: Z80 Directives,  Up: Z80-Dependent
 
@@ -19494,36 +19352,36 @@ In line with common practice, Z80 mnemonics are used for both the Z80
 and the R800.
 
    In many instructions it is possible to use one of the half index
-registers (`ixl',`ixh',`iyl',`iyh') in stead of an 8-bit general
-purpose register. This yields instructions that are documented on the
-R800 and undocumented on the Z80.  Similarly `in f,(c)' is documented
-on the R800 and undocumented on the Z80.
+registers ('ixl','ixh','iyl','iyh') in stead of an 8-bit general purpose
+register.  This yields instructions that are documented on the R800 and
+undocumented on the Z80.  Similarly 'in f,(c)' is documented on the R800
+and undocumented on the Z80.
 
    The assembler also supports the following undocumented
 Z80-instructions, that have not been adopted in the R800 instruction
 set:
-`out (c),0'
+'out (c),0'
      Sends zero to the port pointed to by register c.
 
-`sli M'
-     Equivalent to `M = (M<<1)+1', the operand M can be any operand
-     that is valid for `sla'. One can use `sll' as a synonym for `sli'.
+'sli M'
+     Equivalent to 'M = (M<<1)+1', the operand M can be any operand that
+     is valid for 'sla'.  One can use 'sll' as a synonym for 'sli'.
 
-`OP (ix+D), R'
+'OP (ix+D), R'
      This is equivalent to
 
           ld R, (ix+D)
           OPC R
           ld (ix+D), R
 
-     The operation `OPC' may be any of `res B,', `set B,', `rl', `rlc',
-     `rr', `rrc', `sla', `sli', `sra' and `srl', and the register `R'
-     may be any of `a', `b', `c', `d', `e', `h' and `l'.
+     The operation 'OPC' may be any of 'res B,', 'set B,', 'rl', 'rlc',
+     'rr', 'rrc', 'sla', 'sli', 'sra' and 'srl', and the register 'R'
+     may be any of 'a', 'b', 'c', 'd', 'e', 'h' and 'l'.
 
-`OPC (iy+D), R'
-     As above, but with `iy' instead of `ix'.
+'OPC (iy+D), R'
+     As above, but with 'iy' instead of 'ix'.
 
-   The web site at `http://www.z80.info' is a good starting place to
+   The web site at <http://www.z80.info> is a good starting place to
 find more information on programming the Z80.
 
 
@@ -19532,14 +19390,14 @@ File: as.info,  Node: Z8000-Dependent,  Next: Vax-Dependent,  Prev: Z80-Dependen
 9.47 Z8000 Dependent Features
 =============================
 
-   The Z8000 as supports both members of the Z8000 family: the
-unsegmented Z8002, with 16 bit addresses, and the segmented Z8001 with
-24 bit addresses.
+The Z8000 as supports both members of the Z8000 family: the unsegmented
+Z8002, with 16 bit addresses, and the segmented Z8001 with 24 bit
+addresses.
 
    When the assembler is in unsegmented mode (specified with the
-`unsegm' directive), an address takes up one word (16 bit) sized
+'unsegm' directive), an address takes up one word (16 bit) sized
 register.  When the assembler is in segmented mode (specified with the
-`segm' directive), a 24-bit address takes up a long (32 bit) register.
+'segm' directive), a 24-bit address takes up a long (32 bit) register.
 *Note Assembler Directives for the Z8000: Z8000 Directives, for a list
 of other Z8000 specific assembler directives.
 
@@ -19556,10 +19414,10 @@ File: as.info,  Node: Z8000 Options,  Next: Z8000 Syntax,  Up: Z8000-Dependent
 9.47.1 Options
 --------------
 
-`-z8001'
+'-z8001'
      Generate segmented code by default.
 
-`-z8002'
+'-z8002'
      Generate unsegmented code by default.
 
 
@@ -19580,14 +19438,14 @@ File: as.info,  Node: Z8000-Chars,  Next: Z8000-Regs,  Up: Z8000 Syntax
 9.47.2.1 Special Characters
 ...........................
 
-`!' is the line comment character.
+'!' is the line comment character.
 
-   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::).
 
-   You can use `;' instead of a newline to separate statements.
+   You can use ';' instead of a newline to separate statements.
 
 
 File: as.info,  Node: Z8000-Regs,  Next: Z8000-Addressing,  Prev: Z8000-Chars,  Up: Z8000 Syntax
@@ -19597,10 +19455,10 @@ File: as.info,  Node: Z8000-Regs,  Next: Z8000-Addressing,  Prev: Z8000-Chars,
 
 The Z8000 has sixteen 16 bit registers, numbered 0 to 15.  You can refer
 to different sized groups of registers by register number, with the
-prefix `r' for 16 bit registers, `rr' for 32 bit registers and `rq' for
-64 bit registers.  You can also refer to the contents of the first
-eight (of the sixteen 16 bit registers) by bytes.  They are named `rlN'
-and `rhN'.
+prefix 'r' for 16 bit registers, 'rr' for 32 bit registers and 'rq' for
+64 bit registers.  You can also refer to the contents of the first eight
+(of the sixteen 16 bit registers) by bytes.  They are named 'rlN' and
+'rhN'.
 
 _byte registers_
      rl0 rh0 rl1 rh1 rl2 rh2 rl3 rh3
@@ -19623,40 +19481,39 @@ File: as.info,  Node: Z8000-Addressing,  Prev: Z8000-Regs,  Up: Z8000 Syntax
 
 as understands the following addressing modes for the Z8000:
 
-`rlN'
-`rhN'
-`rN'
-`rrN'
-`rqN'
-     Register direct:  8bit, 16bit, 32bit, and 64bit registers.
+'rlN'
+'rhN'
+'rN'
+'rrN'
+'rqN'
+     Register direct: 8bit, 16bit, 32bit, and 64bit registers.
 
-`@rN'
-`@rrN'
-     Indirect register:  @rrN in segmented mode, @rN in unsegmented
-     mode.
+'@rN'
+'@rrN'
+     Indirect register: @rrN in segmented mode, @rN in unsegmented mode.
 
-`ADDR'
+'ADDR'
      Direct: the 16 bit or 24 bit address (depending on whether the
-     assembler is in segmented or unsegmented mode) of the operand is
-     in the instruction.
+     assembler is in segmented or unsegmented mode) of the operand is in
+     the instruction.
 
-`address(rN)'
+'address(rN)'
      Indexed: the 16 or 24 bit address is added to the 16 bit register
      to produce the final address in memory of the operand.
 
-`rN(#IMM)'
-`rrN(#IMM)'
+'rN(#IMM)'
+'rrN(#IMM)'
      Base Address: the 16 or 24 bit register is added to the 16 bit sign
      extended immediate displacement to produce the final address in
      memory of the operand.
 
-`rN(rM)'
-`rrN(rM)'
+'rN(rM)'
+'rrN(rM)'
      Base Index: the 16 or 24 bit register rN or rrN is added to the
-     sign extended 16 bit index register rM to produce the final
-     address in memory of the operand.
+     sign extended 16 bit index register rM to produce the final address
+     in memory of the operand.
 
-`#XX'
+'#XX'
      Immediate data XX.
 
 
@@ -19666,43 +19523,42 @@ File: as.info,  Node: Z8000 Directives,  Next: Z8000 Opcodes,  Prev: Z8000 Synta
 -----------------------------------------
 
 The Z8000 port of as includes additional assembler directives, for
-compatibility with other Z8000 assemblers.  These do not begin with `.'
+compatibility with other Z8000 assemblers.  These do not begin with '.'
 (unlike the ordinary as directives).
 
-`segm'
-`.z8001'
+'segm'
+'.z8001'
      Generate code for the segmented Z8001.
 
-`unsegm'
-`.z8002'
+'unsegm'
+'.z8002'
      Generate code for the unsegmented Z8002.
 
-`name'
-     Synonym for `.file'
+'name'
+     Synonym for '.file'
 
-`global'
-     Synonym for `.global'
+'global'
+     Synonym for '.global'
 
-`wval'
-     Synonym for `.word'
+'wval'
+     Synonym for '.word'
 
-`lval'
-     Synonym for `.long'
+'lval'
+     Synonym for '.long'
 
-`bval'
-     Synonym for `.byte'
+'bval'
+     Synonym for '.byte'
 
-`sval'
-     Assemble a string.  `sval' expects one string literal, delimited by
+'sval'
+     Assemble a string.  'sval' expects one string literal, delimited by
      single quotes.  It assembles each byte of the string into
-     consecutive addresses.  You can use the escape sequence `%XX'
+     consecutive addresses.  You can use the escape sequence '%XX'
      (where XX represents a two-digit hexadecimal number) to represent
      the character whose ASCII value is XX.  Use this feature to
      describe single quote and other characters that may not appear in
-     string literals as themselves.  For example, the C statement
-     `char *a = "he said \"it's 50% off\"";' is represented in Z8000
-     assembly language (shown with the assembler output in hex at the
-     left) as
+     string literals as themselves.  For example, the C statement 'char *a = "he said \"it's 50% off\"";'
+     is represented in Z8000 assembly language (shown with the assembler
+     output in hex at the left) as
 
           68652073    sval    'he said %22it%27s 50%25 off%22%00'
           61696420
@@ -19711,14 +19567,14 @@ compatibility with other Z8000 assemblers.  These do not begin with `.'
           25206F66
           662200
 
-`rsect'
-     synonym for `.section'
+'rsect'
+     synonym for '.section'
 
-`block'
-     synonym for `.space'
+'block'
+     synonym for '.space'
 
-`even'
-     special case of `.align'; aligns output to even byte boundary.
+'even'
+     special case of '.align'; aligns output to even byte boundary.
 
 
 File: as.info,  Node: Z8000 Opcodes,  Prev: Z8000 Directives,  Up: Z8000-Dependent
@@ -19727,7 +19583,7 @@ File: as.info,  Node: Z8000 Opcodes,  Prev: Z8000 Directives,  Up: Z8000-Depende
 --------------
 
 For detailed information on the Z8000 machine instruction set, see
-`Z8000 Technical Manual'.
+'Z8000 Technical Manual'.
 
    The following table summarizes the opcodes and their arguments:
 
@@ -19884,7 +19740,7 @@ For detailed information on the Z8000 machine instruction set, see
      set addr(rd),imm4       subl rrd,addr(rs)
 
 
-File: as.info,  Node: Vax-Dependent,  Prev: Z8000-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: Vax-Dependent,  Next: V850-Dependent,  Prev: Z8000-Dependent,  Up: Machine Dependencies
 
 9.48 VAX Dependent Features
 ===========================
@@ -19906,84 +19762,84 @@ File: as.info,  Node: VAX-Opts,  Next: VAX-float,  Up: Vax-Dependent
 9.48.1 VAX Command-Line Options
 -------------------------------
 
-The Vax version of `as' accepts any of the following options, gives a
-warning message that the option was ignored and proceeds.  These
-options are for compatibility with scripts designed for other people's
+The Vax version of 'as' accepts any of the following options, gives a
+warning message that the option was ignored and proceeds.  These options
+are for compatibility with scripts designed for other people's
 assemblers.
 
-``-D' (Debug)'
-``-S' (Symbol Table)'
-``-T' (Token Trace)'
+'-D (Debug)'
+'-S (Symbol Table)'
+'-T (Token Trace)'
      These are obsolete options used to debug old assemblers.
 
-``-d' (Displacement size for JUMPs)'
-     This option expects a number following the `-d'.  Like options
-     that expect filenames, the number may immediately follow the `-d'
-     (old standard) or constitute the whole of the command line
-     argument that follows `-d' (GNU standard).
+'-d (Displacement size for JUMPs)'
+     This option expects a number following the '-d'.  Like options that
+     expect filenames, the number may immediately follow the '-d' (old
+     standard) or constitute the whole of the command line argument that
+     follows '-d' (GNU standard).
 
-``-V' (Virtualize Interpass Temporary File)'
+'-V (Virtualize Interpass Temporary File)'
      Some other assemblers use a temporary file.  This option commanded
-     them to keep the information in active memory rather than in a
-     disk file.  `as' always does this, so this option is redundant.
-
-``-J' (JUMPify Longer Branches)'
-     Many 32-bit computers permit a variety of branch instructions to
-     do the same job.  Some of these instructions are short (and fast)
-     but have a limited range; others are long (and slow) but can
-     branch anywhere in virtual memory.  Often there are 3 flavors of
-     branch: short, medium and long.  Some other assemblers would emit
-     short and medium branches, unless told by this option to emit
-     short and long branches.
-
-``-t' (Temporary File Directory)'
+     them to keep the information in active memory rather than in a disk
+     file.  'as' always does this, so this option is redundant.
+
+'-J (JUMPify Longer Branches)'
+     Many 32-bit computers permit a variety of branch instructions to do
+     the same job.  Some of these instructions are short (and fast) but
+     have a limited range; others are long (and slow) but can branch
+     anywhere in virtual memory.  Often there are 3 flavors of branch:
+     short, medium and long.  Some other assemblers would emit short and
+     medium branches, unless told by this option to emit short and long
+     branches.
+
+'-t (Temporary File Directory)'
      Some other assemblers may use a temporary file, and this option
      takes a filename being the directory to site the temporary file.
-     Since `as' does not use a temporary disk file, this option makes
-     no difference.  `-t' needs exactly one filename.
+     Since 'as' does not use a temporary disk file, this option makes no
+     difference.  '-t' needs exactly one filename.
 
    The Vax version of the assembler accepts additional options when
 compiled for VMS:
 
-`-h N'
+'-h N'
      External symbol or section (used for global variables) names are
      not case sensitive on VAX/VMS and always mapped to upper case.
      This is contrary to the C language definition which explicitly
      distinguishes upper and lower case.  To implement a standard
      conforming C compiler, names must be changed (mapped) to preserve
      the case information.  The default mapping is to convert all lower
-     case characters to uppercase and adding an underscore followed by
-     a 6 digit hex value, representing a 24 digit binary value.  The
-     one digits in the binary value represent which characters are
-     uppercase in the original symbol name.
-
-     The `-h N' option determines how we map names.  This takes several
-     values.  No `-h' switch at all allows case hacking as described
-     above.  A value of zero (`-h0') implies names should be upper
-     case, and inhibits the case hack.  A value of 2 (`-h2') implies
-     names should be all lower case, with no case hack.  A value of 3
-     (`-h3') implies that case should be preserved.  The value 1 is
-     unused.  The `-H' option directs `as' to display every mapped
-     symbol during assembly.
-
-     Symbols whose names include a dollar sign `$' are exceptions to the
+     case characters to uppercase and adding an underscore followed by a
+     6 digit hex value, representing a 24 digit binary value.  The one
+     digits in the binary value represent which characters are uppercase
+     in the original symbol name.
+
+     The '-h N' option determines how we map names.  This takes several
+     values.  No '-h' switch at all allows case hacking as described
+     above.  A value of zero ('-h0') implies names should be upper case,
+     and inhibits the case hack.  A value of 2 ('-h2') implies names
+     should be all lower case, with no case hack.  A value of 3 ('-h3')
+     implies that case should be preserved.  The value 1 is unused.  The
+     '-H' option directs 'as' to display every mapped symbol during
+     assembly.
+
+     Symbols whose names include a dollar sign '$' are exceptions to the
      general name mapping.  These symbols are normally only used to
      reference VMS library names.  Such symbols are always mapped to
      upper case.
 
-`-+'
-     The `-+' option causes `as' to truncate any symbol name larger
-     than 31 characters.  The `-+' option also prevents some code
-     following the `_main' symbol normally added to make the object
-     file compatible with Vax-11 "C".
+'-+'
+     The '-+' option causes 'as' to truncate any symbol name larger than
+     31 characters.  The '-+' option also prevents some code following
+     the '_main' symbol normally added to make the object file
+     compatible with Vax-11 "C".
 
-`-1'
-     This option is ignored for backward compatibility with `as'
-     version 1.x.
+'-1'
+     This option is ignored for backward compatibility with 'as' version
+     1.x.
 
-`-H'
-     The `-H' option causes `as' to print every symbol which was
-     changed by case mapping.
+'-H'
+     The '-H' option causes 'as' to print every symbol which was changed
+     by case mapping.
 
 
 File: as.info,  Node: VAX-float,  Next: VAX-directives,  Prev: VAX-Opts,  Up: Vax-Dependent
@@ -19995,13 +19851,13 @@ Conversion of flonums to floating point is correct, and compatible with
 previous assemblers.  Rounding is towards zero if the remainder is
 exactly half the least significant bit.
 
-   `D', `F', `G' and `H' floating point formats are understood.
+   'D', 'F', 'G' and 'H' floating point formats are understood.
 
-   Immediate floating literals (_e.g._ `S`$6.9') are rendered
+   Immediate floating literals (_e.g._  'S`$6.9') are rendered
 correctly.  Again, rounding is towards zero in the boundary case.
 
-   The `.float' directive produces `f' format numbers.  The `.double'
-directive produces `d' format numbers.
+   The '.float' directive produces 'f' format numbers.  The '.double'
+directive produces 'd' format numbers.
 
 
 File: as.info,  Node: VAX-directives,  Next: VAX-opcodes,  Prev: VAX-float,  Up: Vax-Dependent
@@ -20009,26 +19865,24 @@ File: as.info,  Node: VAX-directives,  Next: VAX-opcodes,  Prev: VAX-float,  Up:
 9.48.3 Vax Machine Directives
 -----------------------------
 
-The Vax version of the assembler supports four directives for
-generating Vax floating point constants.  They are described in the
-table below.
+The Vax version of the assembler supports four directives for generating
+Vax floating point constants.  They are described in the table below.
 
-`.dfloat'
+'.dfloat'
      This expects zero or more flonums, separated by commas, and
-     assembles Vax `d' format 64-bit floating point constants.
+     assembles Vax 'd' format 64-bit floating point constants.
 
-`.ffloat'
+'.ffloat'
      This expects zero or more flonums, separated by commas, and
-     assembles Vax `f' format 32-bit floating point constants.
+     assembles Vax 'f' format 32-bit floating point constants.
 
-`.gfloat'
+'.gfloat'
      This expects zero or more flonums, separated by commas, and
-     assembles Vax `g' format 64-bit floating point constants.
+     assembles Vax 'g' format 64-bit floating point constants.
 
-`.hfloat'
+'.hfloat'
      This expects zero or more flonums, separated by commas, and
-     assembles Vax `h' format 128-bit floating point constants.
-
+     assembles Vax 'h' format 128-bit floating point constants.
 
 
 File: as.info,  Node: VAX-opcodes,  Next: VAX-branch,  Prev: VAX-directives,  Up: Vax-Dependent
@@ -20036,9 +19890,9 @@ File: as.info,  Node: VAX-opcodes,  Next: VAX-branch,  Prev: VAX-directives,  Up
 9.48.4 VAX Opcodes
 ------------------
 
-All DEC mnemonics are supported.  Beware that `case...' instructions
-have exactly 3 operands.  The dispatch table that follows the `case...'
-instruction should be made with `.word' statements.  This is compatible
+All DEC mnemonics are supported.  Beware that 'case...' instructions
+have exactly 3 operands.  The dispatch table that follows the 'case...'
+instruction should be made with '.word' statements.  This is compatible
 with all unix assemblers we know of.
 
 
@@ -20047,98 +19901,80 @@ File: as.info,  Node: VAX-branch,  Next: VAX-operands,  Prev: VAX-opcodes,  Up:
 9.48.5 VAX Branch Improvement
 -----------------------------
 
-Certain pseudo opcodes are permitted.  They are for branch
-instructions.  They expand to the shortest branch instruction that
-reaches the target.  Generally these mnemonics are made by substituting
-`j' for `b' at the start of a DEC mnemonic.  This feature is included
-both for compatibility and to help compilers.  If you do not need this
-feature, avoid these opcodes.  Here are the mnemonics, and the code
-they can expand into.
-
-`jbsb'
-     `Jsb' is already an instruction mnemonic, so we chose `jbsb'.
-    (byte displacement)
-          `bsbb ...'
-
-    (word displacement)
-          `bsbw ...'
-
-    (long displacement)
-          `jsb ...'
-
-`jbr'
-`jr'
+Certain pseudo opcodes are permitted.  They are for branch instructions.
+They expand to the shortest branch instruction that reaches the target.
+Generally these mnemonics are made by substituting 'j' for 'b' at the
+start of a DEC mnemonic.  This feature is included both for
+compatibility and to help compilers.  If you do not need this feature,
+avoid these opcodes.  Here are the mnemonics, and the code they can
+expand into.
+
+'jbsb'
+     'Jsb' is already an instruction mnemonic, so we chose 'jbsb'.
+     (byte displacement)
+          'bsbb ...'
+     (word displacement)
+          'bsbw ...'
+     (long displacement)
+          'jsb ...'
+'jbr'
+'jr'
      Unconditional branch.
-    (byte displacement)
-          `brb ...'
-
-    (word displacement)
-          `brw ...'
-
-    (long displacement)
-          `jmp ...'
-
-`jCOND'
-     COND may be any one of the conditional branches `neq', `nequ',
-     `eql', `eqlu', `gtr', `geq', `lss', `gtru', `lequ', `vc', `vs',
-     `gequ', `cc', `lssu', `cs'.  COND may also be one of the bit tests
-     `bs', `bc', `bss', `bcs', `bsc', `bcc', `bssi', `bcci', `lbs',
-     `lbc'.  NOTCOND is the opposite condition to COND.
-    (byte displacement)
-          `bCOND ...'
-
-    (word displacement)
-          `bNOTCOND foo ; brw ... ; foo:'
-
-    (long displacement)
-          `bNOTCOND foo ; jmp ... ; foo:'
-
-`jacbX'
-     X may be one of `b d f g h l w'.
-    (word displacement)
-          `OPCODE ...'
-
-    (long displacement)
+     (byte displacement)
+          'brb ...'
+     (word displacement)
+          'brw ...'
+     (long displacement)
+          'jmp ...'
+'jCOND'
+     COND may be any one of the conditional branches 'neq', 'nequ',
+     'eql', 'eqlu', 'gtr', 'geq', 'lss', 'gtru', 'lequ', 'vc', 'vs',
+     'gequ', 'cc', 'lssu', 'cs'.  COND may also be one of the bit tests
+     'bs', 'bc', 'bss', 'bcs', 'bsc', 'bcc', 'bssi', 'bcci', 'lbs',
+     'lbc'.  NOTCOND is the opposite condition to COND.
+     (byte displacement)
+          'bCOND ...'
+     (word displacement)
+          'bNOTCOND foo ; brw ... ; foo:'
+     (long displacement)
+          'bNOTCOND foo ; jmp ... ; foo:'
+'jacbX'
+     X may be one of 'b d f g h l w'.
+     (word displacement)
+          'OPCODE ...'
+     (long displacement)
                OPCODE ..., foo ;
                brb bar ;
                foo: jmp ... ;
                bar:
-
-`jaobYYY'
-     YYY may be one of `lss leq'.
-
-`jsobZZZ'
-     ZZZ may be one of `geq gtr'.
-    (byte displacement)
-          `OPCODE ...'
-
-    (word displacement)
+'jaobYYY'
+     YYY may be one of 'lss leq'.
+'jsobZZZ'
+     ZZZ may be one of 'geq gtr'.
+     (byte displacement)
+          'OPCODE ...'
+     (word displacement)
                OPCODE ..., foo ;
                brb bar ;
                foo: brw DESTINATION ;
                bar:
-
-    (long displacement)
+     (long displacement)
                OPCODE ..., foo ;
                brb bar ;
                foo: jmp DESTINATION ;
                bar:
-
-`aobleq'
-`aoblss'
-`sobgeq'
-`sobgtr'
-
-    (byte displacement)
-          `OPCODE ...'
-
-    (word displacement)
+'aobleq'
+'aoblss'
+'sobgeq'
+'sobgtr'
+     (byte displacement)
+          'OPCODE ...'
+     (word displacement)
                OPCODE ..., foo ;
                brb bar ;
                foo: brw DESTINATION ;
                bar:
-
-    (long displacement)
+     (long displacement)
                OPCODE ..., foo ;
                brb bar ;
                foo: jmp DESTINATION ;
@@ -20150,18 +19986,18 @@ File: as.info,  Node: VAX-operands,  Next: VAX-no,  Prev: VAX-branch,  Up: Vax-D
 9.48.6 VAX Operands
 -------------------
 
-The immediate character is `$' for Unix compatibility, not `#' as DEC
+The immediate character is '$' for Unix compatibility, not '#' as DEC
 writes it.
 
-   The indirect character is `*' for Unix compatibility, not `@' as DEC
+   The indirect character is '*' for Unix compatibility, not '@' as DEC
 writes it.
 
-   The displacement sizing character is ``' (an accent grave) for Unix
-compatibility, not `^' as DEC writes it.  The letter preceding ``' may
-have either case.  `G' is not understood, but all other letters (`b i l
+   The displacement sizing character is '`' (an accent grave) for Unix
+compatibility, not '^' as DEC writes it.  The letter preceding '`' may
+have either case.  'G' is not understood, but all other letters ('b i l
 s w') are understood.
 
-   Register names understood are `r0 r1 r2 ... r15 ap fp sp pc'.  Upper
+   Register names understood are 'r0 r1 r2 ... r15 ap fp sp pc'.  Upper
 and lower case letters are equivalent.
 
    For instance
@@ -20176,7 +20012,7 @@ File: as.info,  Node: VAX-no,  Next: VAX-Syntax,  Prev: VAX-operands,  Up: Vax-D
 9.48.7 Not Supported on VAX
 ---------------------------
 
-Vax bit fields can not be assembled with `as'.  Someone can add the
+Vax bit fields can not be assembled with 'as'.  Someone can add the
 required code if they really need it.
 
 
@@ -20195,19 +20031,19 @@ File: as.info,  Node: VAX-Chars,  Up: VAX-Syntax
 9.48.8.1 Special Characters
 ...........................
 
-The presence of a `#' appearing anywhere on a line indicates the start
+The presence of a '#' appearing 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 can also be a
-logical line number directive (*note Comments::) or a preprocessor
-control command (*note Preprocessing::).
+   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 can also be a logical
+line number directive (*note Comments::) or a preprocessor control
+command (*note Preprocessing::).
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
-File: as.info,  Node: V850-Dependent,  Next: XGATE-Dependent,  Prev: TILEPro-Dependent,  Up: Machine Dependencies
+File: as.info,  Node: V850-Dependent,  Next: XGATE-Dependent,  Prev: Vax-Dependent,  Up: Machine Dependencies
 
 9.49 v850 Dependent Features
 ============================
@@ -20226,96 +20062,95 @@ File: as.info,  Node: V850 Options,  Next: V850 Syntax,  Up: V850-Dependent
 9.49.1 Options
 --------------
 
-`as' supports the following additional command-line options for the
-V850 processor family:
+'as' supports the following additional command-line options for the V850
+processor family:
 
-`-wsigned_overflow'
+'-wsigned_overflow'
      Causes warnings to be produced when signed immediate values
      overflow the space available for then within their opcodes.  By
      default this option is disabled as it is possible to receive
      spurious warnings due to using exact bit patterns as immediate
      constants.
 
-`-wunsigned_overflow'
+'-wunsigned_overflow'
      Causes warnings to be produced when unsigned immediate values
      overflow the space available for then within their opcodes.  By
      default this option is disabled as it is possible to receive
      spurious warnings due to using exact bit patterns as immediate
      constants.
 
-`-mv850'
+'-mv850'
      Specifies that the assembled code should be marked as being
      targeted at the V850 processor.  This allows the linker to detect
      attempts to link such code with code assembled for other
      processors.
 
-`-mv850e'
+'-mv850e'
      Specifies that the assembled code should be marked as being
      targeted at the V850E processor.  This allows the linker to detect
      attempts to link such code with code assembled for other
      processors.
 
-`-mv850e1'
+'-mv850e1'
      Specifies that the assembled code should be marked as being
-     targeted at the V850E1 processor.  This allows the linker to
-     detect attempts to link such code with code assembled for other
+     targeted at the V850E1 processor.  This allows the linker to detect
+     attempts to link such code with code assembled for other
      processors.
 
-`-mv850any'
+'-mv850any'
      Specifies that the assembled code should be marked as being
      targeted at the V850 processor but support instructions that are
      specific to the extended variants of the process.  This allows the
-     production of binaries that contain target specific code, but
-     which are also intended to be used in a generic fashion.  For
-     example libgcc.a contains generic routines used by the code
-     produced by GCC for all versions of the v850 architecture,
-     together with support routines only used by the V850E architecture.
+     production of binaries that contain target specific code, but which
+     are also intended to be used in a generic fashion.  For example
+     libgcc.a contains generic routines used by the code produced by GCC
+     for all versions of the v850 architecture, together with support
+     routines only used by the V850E architecture.
 
-`-mv850e2'
+'-mv850e2'
      Specifies that the assembled code should be marked as being
-     targeted at the V850E2 processor.  This allows the linker to
-     detect attempts to link such code with code assembled for other
+     targeted at the V850E2 processor.  This allows the linker to detect
+     attempts to link such code with code assembled for other
      processors.
 
-`-mv850e2v3'
+'-mv850e2v3'
      Specifies that the assembled code should be marked as being
      targeted at the V850E2V3 processor.  This allows the linker to
      detect attempts to link such code with code assembled for other
      processors.
 
-`-mv850e2v4'
-     This is an alias for `-mv850e3v5'.
+'-mv850e2v4'
+     This is an alias for '-mv850e3v5'.
 
-`-mv850e3v5'
+'-mv850e3v5'
      Specifies that the assembled code should be marked as being
      targeted at the V850E3V5 processor.  This allows the linker to
      detect attempts to link such code with code assembled for other
      processors.
 
-`-mrelax'
+'-mrelax'
      Enables relaxation.  This allows the .longcall and .longjump pseudo
      ops to be used in the assembler source code.  These ops label
      sections of code which are either a long function call or a long
      branch.  The assembler will then flag these sections of code and
      the linker will attempt to relax them.
 
-`-mgcc-abi'
+'-mgcc-abi'
      Marks the generated objecy file as supporting the old GCC ABI.
 
-`-mrh850-abi'
-     Marks the generated objecy file as supporting the RH850 ABI.  This
+'-mrh850-abi'
+     Marks the generated objecy file as supporting the RH850 ABI. This
      is the default.
 
-`-m8byte-align'
+'-m8byte-align'
      Marks the generated objecy file as supporting a maximum 64-bits of
      alignment for variables defined in the source code.
 
-`-m4byte-align'
+'-m4byte-align'
      Marks the generated objecy file as supporting a maximum 32-bits of
      alignment for variables defined in the source code.  This is the
      default.
 
-
 
 File: as.info,  Node: V850 Syntax,  Next: V850 Floating Point,  Prev: V850 Options,  Up: V850-Dependent
 
@@ -20333,14 +20168,14 @@ File: as.info,  Node: V850-Chars,  Next: V850-Regs,  Up: V850 Syntax
 9.49.2.1 Special Characters
 ...........................
 
-`#' is the line comment character.  If a `#' appears as the first
-character of a line, the whole line is treated as a comment, but in
-this case the line can also be a logical line number directive (*note
+'#' is the line comment character.  If a '#' appears as the first
+character of a line, the whole line is treated as a comment, but in this
+case the line can also be a logical line number directive (*note
 Comments::) or a preprocessor control command (*note Preprocessing::).
 
-   Two dashes (`--') can also be used to start a line comment.
+   Two dashes ('--') can also be used to start a line comment.
 
-   The `;' character can be used to separate statements on the same
+   The ';' character can be used to separate statements on the same
 line.
 
 
@@ -20349,134 +20184,92 @@ File: as.info,  Node: V850-Regs,  Prev: V850-Chars,  Up: V850 Syntax
 9.49.2.2 Register Names
 .......................
 
-`as' supports the following names for registers:
-`general register 0'
+'as' supports the following names for registers:
+'general register 0'
      r0, zero
-
-`general register 1'
+'general register 1'
      r1
-
-`general register 2'
-     r2, hp 
-
-`general register 3'
-     r3, sp 
-
-`general register 4'
-     r4, gp 
-
-`general register 5'
+'general register 2'
+     r2, hp
+'general register 3'
+     r3, sp
+'general register 4'
+     r4, gp
+'general register 5'
      r5, tp
-
-`general register 6'
+'general register 6'
      r6
-
-`general register 7'
+'general register 7'
      r7
-
-`general register 8'
+'general register 8'
      r8
-
-`general register 9'
+'general register 9'
      r9
-
-`general register 10'
+'general register 10'
      r10
-
-`general register 11'
+'general register 11'
      r11
-
-`general register 12'
+'general register 12'
      r12
-
-`general register 13'
+'general register 13'
      r13
-
-`general register 14'
+'general register 14'
      r14
-
-`general register 15'
+'general register 15'
      r15
-
-`general register 16'
+'general register 16'
      r16
-
-`general register 17'
+'general register 17'
      r17
-
-`general register 18'
+'general register 18'
      r18
-
-`general register 19'
+'general register 19'
      r19
-
-`general register 20'
+'general register 20'
      r20
-
-`general register 21'
+'general register 21'
      r21
-
-`general register 22'
+'general register 22'
      r22
-
-`general register 23'
+'general register 23'
      r23
-
-`general register 24'
+'general register 24'
      r24
-
-`general register 25'
+'general register 25'
      r25
-
-`general register 26'
+'general register 26'
      r26
-
-`general register 27'
+'general register 27'
      r27
-
-`general register 28'
+'general register 28'
      r28
-
-`general register 29'
-     r29 
-
-`general register 30'
-     r30, ep 
-
-`general register 31'
-     r31, lp 
-
-`system register 0'
-     eipc 
-
-`system register 1'
-     eipsw 
-
-`system register 2'
-     fepc 
-
-`system register 3'
-     fepsw 
-
-`system register 4'
-     ecr 
-
-`system register 5'
-     psw 
-
-`system register 16'
-     ctpc 
-
-`system register 17'
-     ctpsw 
-
-`system register 18'
-     dbpc 
-
-`system register 19'
-     dbpsw 
-
-`system register 20'
+'general register 29'
+     r29
+'general register 30'
+     r30, ep
+'general register 31'
+     r31, lp
+'system register 0'
+     eipc
+'system register 1'
+     eipsw
+'system register 2'
+     fepc
+'system register 3'
+     fepsw
+'system register 4'
+     ecr
+'system register 5'
+     psw
+'system register 16'
+     ctpc
+'system register 17'
+     ctpsw
+'system register 18'
+     dbpc
+'system register 19'
+     dbpsw
+'system register 20'
      ctbp
 
 
@@ -20493,91 +20286,90 @@ File: as.info,  Node: V850 Directives,  Next: V850 Opcodes,  Prev: V850 Floating
 9.49.4 V850 Machine Directives
 ------------------------------
 
-`.offset <EXPRESSION>'
+'.offset <EXPRESSION>'
      Moves the offset into the current section to the specified amount.
 
-`.section "name", <type>'
+'.section "name", <type>'
      This is an extension to the standard .section directive.  It sets
      the current section to be <type> and creates an alias for this
      section called "name".
 
-`.v850'
+'.v850'
      Specifies that the assembled code should be marked as being
      targeted at the V850 processor.  This allows the linker to detect
      attempts to link such code with code assembled for other
      processors.
 
-`.v850e'
+'.v850e'
      Specifies that the assembled code should be marked as being
      targeted at the V850E processor.  This allows the linker to detect
      attempts to link such code with code assembled for other
      processors.
 
-`.v850e1'
+'.v850e1'
      Specifies that the assembled code should be marked as being
-     targeted at the V850E1 processor.  This allows the linker to
-     detect attempts to link such code with code assembled for other
+     targeted at the V850E1 processor.  This allows the linker to detect
+     attempts to link such code with code assembled for other
      processors.
 
-`.v850e2'
+'.v850e2'
      Specifies that the assembled code should be marked as being
-     targeted at the V850E2 processor.  This allows the linker to
-     detect attempts to link such code with code assembled for other
+     targeted at the V850E2 processor.  This allows the linker to detect
+     attempts to link such code with code assembled for other
      processors.
 
-`.v850e2v3'
+'.v850e2v3'
      Specifies that the assembled code should be marked as being
      targeted at the V850E2V3 processor.  This allows the linker to
      detect attempts to link such code with code assembled for other
      processors.
 
-`.v850e2v4'
+'.v850e2v4'
      Specifies that the assembled code should be marked as being
      targeted at the V850E3V5 processor.  This allows the linker to
      detect attempts to link such code with code assembled for other
      processors.
 
-`.v850e3v5'
+'.v850e3v5'
      Specifies that the assembled code should be marked as being
      targeted at the V850E3V5 processor.  This allows the linker to
      detect attempts to link such code with code assembled for other
      processors.
 
-
 
 File: as.info,  Node: V850 Opcodes,  Prev: V850 Directives,  Up: V850-Dependent
 
 9.49.5 Opcodes
 --------------
 
-`as' implements all the standard V850 opcodes.
+'as' implements all the standard V850 opcodes.
 
-   `as' also implements the following pseudo ops:
+   'as' also implements the following pseudo ops:
 
-`hi0()'
+'hi0()'
      Computes the higher 16 bits of the given expression and stores it
      into the immediate operand field of the given instruction.  For
      example:
 
-     `mulhi hi0(here - there), r5, r6'
+     'mulhi hi0(here - there), r5, r6'
 
      computes the difference between the address of labels 'here' and
-     'there', takes the upper 16 bits of this difference, shifts it
-     down 16 bits and then multiplies it by the lower 16 bits in
-     register 5, putting the result into register 6.
+     'there', takes the upper 16 bits of this difference, shifts it down
+     16 bits and then multiplies it by the lower 16 bits in register 5,
+     putting the result into register 6.
 
-`lo()'
+'lo()'
      Computes the lower 16 bits of the given expression and stores it
      into the immediate operand field of the given instruction.  For
      example:
 
-     `addi lo(here - there), r5, r6'
+     'addi lo(here - there), r5, r6'
 
      computes the difference between the address of labels 'here' and
      'there', takes the lower 16 bits of this difference and adds it to
      register 5, putting the result into register 6.
 
-`hi()'
+'hi()'
      Computes the higher 16 bits of the given expression and then adds
      the value of the most significant bit of the lower 16 bits of the
      expression and stores the result into the immediate operand field
@@ -20585,37 +20377,37 @@ File: as.info,  Node: V850 Opcodes,  Prev: V850 Directives,  Up: V850-Dependent
      used to compute the address of the label 'here' and store it into
      register 6:
 
-     `movhi hi(here), r0, r6'     `movea lo(here), r6, r6'
+     'movhi hi(here), r0, r6' 'movea lo(here), r6, r6'
 
      The reason for this special behaviour is that movea performs a sign
      extension on its immediate operand.  So for example if the address
      of 'here' was 0xFFFFFFFF then without the special behaviour of the
      hi() pseudo-op the movhi instruction would put 0xFFFF0000 into r6,
      then the movea instruction would takes its immediate operand,
-     0xFFFF, sign extend it to 32 bits, 0xFFFFFFFF, and then add it
-     into r6 giving 0xFFFEFFFF which is wrong (the fifth nibble is E).
-     With the hi() pseudo op adding in the top bit of the lo() pseudo
-     op, the movhi instruction actually stores 0 into r6 (0xFFFF + 1 =
-     0x0000), so that the movea instruction stores 0xFFFFFFFF into r6 -
-     the right value.
-
-`hilo()'
+     0xFFFF, sign extend it to 32 bits, 0xFFFFFFFF, and then add it into
+     r6 giving 0xFFFEFFFF which is wrong (the fifth nibble is E). With
+     the hi() pseudo op adding in the top bit of the lo() pseudo op, the
+     movhi instruction actually stores 0 into r6 (0xFFFF + 1 = 0x0000),
+     so that the movea instruction stores 0xFFFFFFFF into r6 - the right
+     value.
+
+'hilo()'
      Computes the 32 bit value of the given expression and stores it
      into the immediate operand field of the given instruction (which
      must be a mov instruction).  For example:
 
-     `mov hilo(here), r6'
+     'mov hilo(here), r6'
 
      computes the absolute address of label 'here' and puts the result
      into register 6.
 
-`sdaoff()'
+'sdaoff()'
      Computes the offset of the named variable from the start of the
      Small Data Area (whoes address is held in register 4, the GP
      register) and stores the result as a 16 bit signed value in the
      immediate operand field of the given instruction.  For example:
 
-     `ld.w sdaoff(_a_variable)[gp],r6'
+     'ld.w sdaoff(_a_variable)[gp],r6'
 
      loads the contents of the location pointed to by the label
      '_a_variable' into register 6, provided that the label is located
@@ -20623,64 +20415,62 @@ File: as.info,  Node: V850 Opcodes,  Prev: V850 Directives,  Up: V850-Dependent
      [Note the linker assumes that the GP register contains a fixed
      address set to the address of the label called '__gp'.  This can
      either be set up automatically by the linker, or specifically set
-     by using the `--defsym __gp=<value>' command line option].
+     by using the '--defsym __gp=<value>' command line option].
 
-`tdaoff()'
+'tdaoff()'
      Computes the offset of the named variable from the start of the
      Tiny Data Area (whoes address is held in register 30, the EP
-     register) and stores the result as a 4,5, 7 or 8 bit unsigned
-     value in the immediate operand field of the given instruction.
-     For example:
+     register) and stores the result as a 4,5, 7 or 8 bit unsigned value
+     in the immediate operand field of the given instruction.  For
+     example:
 
-     `sld.w tdaoff(_a_variable)[ep],r6'
+     'sld.w tdaoff(_a_variable)[ep],r6'
 
      loads the contents of the location pointed to by the label
      '_a_variable' into register 6, provided that the label is located
-     somewhere within +256 bytes of the address held in the EP
-     register.  [Note the linker assumes that the EP register contains
-     a fixed address set to the address of the label called '__ep'.
-     This can either be set up automatically by the linker, or
-     specifically set by using the `--defsym __ep=<value>' command line
-     option].
+     somewhere within +256 bytes of the address held in the EP register.
+     [Note the linker assumes that the EP register contains a fixed
+     address set to the address of the label called '__ep'.  This can
+     either be set up automatically by the linker, or specifically set
+     by using the '--defsym __ep=<value>' command line option].
 
-`zdaoff()'
-     Computes the offset of the named variable from address 0 and
-     stores the result as a 16 bit signed value in the immediate
-     operand field of the given instruction.  For example:
+'zdaoff()'
+     Computes the offset of the named variable from address 0 and stores
+     the result as a 16 bit signed value in the immediate operand field
+     of the given instruction.  For example:
 
-     `movea zdaoff(_a_variable),zero,r6'
+     'movea zdaoff(_a_variable),zero,r6'
 
      puts the address of the label '_a_variable' into register 6,
      assuming that the label is somewhere within the first 32K of
-     memory.  (Strictly speaking it also possible to access the last
-     32K of memory as well, as the offsets are signed).
+     memory.  (Strictly speaking it also possible to access the last 32K
+     of memory as well, as the offsets are signed).
 
-`ctoff()'
+'ctoff()'
      Computes the offset of the named variable from the start of the
      Call Table Area (whoes address is helg in system register 20, the
      CTBP register) and stores the result a 6 or 16 bit unsigned value
      in the immediate field of then given instruction or piece of data.
      For example:
 
-     `callt ctoff(table_func1)'
+     'callt ctoff(table_func1)'
 
      will put the call the function whoes address is held in the call
      table at the location labeled 'table_func1'.
 
-`.longcall `name''
+'.longcall name'
      Indicates that the following sequence of instructions is a long
-     call to function `name'.  The linker will attempt to shorten this
-     call sequence if `name' is within a 22bit offset of the call.  Only
-     valid if the `-mrelax' command line switch has been enabled.
+     call to function 'name'.  The linker will attempt to shorten this
+     call sequence if 'name' is within a 22bit offset of the call.  Only
+     valid if the '-mrelax' command line switch has been enabled.
 
-`.longjump `name''
+'.longjump name'
      Indicates that the following sequence of instructions is a long
-     jump to label `name'.  The linker will attempt to shorten this code
-     sequence if `name' is within a 22bit offset of the jump.  Only
-     valid if the `-mrelax' command line switch has been enabled.
-
+     jump to label 'name'.  The linker will attempt to shorten this code
+     sequence if 'name' is within a 22bit offset of the jump.  Only
+     valid if the '-mrelax' command line switch has been enabled.
 
-   For information on the V850 instruction set, see `V850 Family
+   For information on the V850 instruction set, see 'V850 Family
 32-/16-Bit single-Chip Microcontroller Architecture Manual' from NEC.
 Ltd.
 
@@ -20704,35 +20494,34 @@ File: as.info,  Node: XGATE-Opts,  Next: XGATE-Syntax,  Up: XGATE-Dependent
 9.50.1 XGATE Options
 --------------------
 
-The Freescale XGATE version of `as' has a few machine dependent options.
+The Freescale XGATE version of 'as' has a few machine dependent options.
 
-`-mshort'
+'-mshort'
      This option controls the ABI and indicates to use a 16-bit integer
-     ABI.  It has no effect on the assembled instructions.  This is the
+     ABI. It has no effect on the assembled instructions.  This is the
      default.
 
-`-mlong'
+'-mlong'
      This option controls the ABI and indicates to use a 32-bit integer
      ABI.
 
-`-mshort-double'
+'-mshort-double'
      This option controls the ABI and indicates to use a 32-bit float
-     ABI.  This is the default.
+     ABI. This is the default.
 
-`-mlong-double'
+'-mlong-double'
      This option controls the ABI and indicates to use a 64-bit float
      ABI.
 
-`--print-insn-syntax'
-     You can use the `--print-insn-syntax' option to obtain the syntax
+'--print-insn-syntax'
+     You can use the '--print-insn-syntax' option to obtain the syntax
      description of the instruction when an error is detected.
 
-`--print-opcodes'
-     The `--print-opcodes' option prints the list of all the
-     instructions with their syntax. Once the list is printed `as'
+'--print-opcodes'
+     The '--print-opcodes' option prints the list of all the
+     instructions with their syntax.  Once the list is printed 'as'
      exits.
 
-
 
 File: as.info,  Node: XGATE-Syntax,  Next: XGATE-Directives,  Prev: XGATE-Opts,  Up: XGATE-Dependent
 
@@ -20740,22 +20529,21 @@ File: as.info,  Node: XGATE-Syntax,  Next: XGATE-Directives,  Prev: XGATE-Opts,
 -------------
 
 In XGATE RISC syntax, the instruction name comes first and it may be
-followed by up to three operands. Operands are separated by commas
-(`,'). `as' will complain if too many operands are specified for a
-given instruction. The same will happen if you specified too few
+followed by up to three operands.  Operands are separated by commas
+(',').  'as' will complain if too many operands are specified for a
+given instruction.  The same will happen if you specified too few
 operands.
 
      nop
      ldl  #23
      CMP  R1, R2
 
-   The presence of a `;' character or a `!' character anywhere on a
-line indicates the start of a comment that extends to the end of that
-line.
+   The presence of a ';' character or a '!' character anywhere on a line
+indicates the start of a comment that extends to the end of that line.
 
-   A `*' or a `#' character at the start of a line also introduces a
+   A '*' or a '#' character at the start of a line also introduces a
 line comment, but these characters do not work elsewhere on the line.
-If the first character of the line is a `#' then as well as starting a
+If the first character of the line is a '#' then as well as starting a
 comment, the line could also be logical line number directive (*note
 Comments::) or a preprocessor control command (*note Preprocessing::).
 
@@ -20764,52 +20552,51 @@ character.
 
    The following addressing modes are understood for XGATE:
 "Inherent"
-     `'
+     ''
 
 "Immediate 3 Bit Wide"
-     `#NUMBER'
+     '#NUMBER'
 
 "Immediate 4 Bit Wide"
-     `#NUMBER'
+     '#NUMBER'
 
 "Immediate 8 Bit Wide"
-     `#NUMBER'
+     '#NUMBER'
 
 "Monadic Addressing"
-     `REG'
+     'REG'
 
 "Dyadic Addressing"
-     `REG, REG'
+     'REG, REG'
 
 "Triadic Addressing"
-     `REG, REG, REG'
+     'REG, REG, REG'
 
 "Relative Addressing 9 Bit Wide"
-     `*SYMBOL'
+     '*SYMBOL'
 
 "Relative Addressing 10 Bit Wide"
-     `*SYMBOL'
+     '*SYMBOL'
 
 "Index Register plus Immediate Offset"
-     `REG, (REG, #NUMBER)'
+     'REG, (REG, #NUMBER)'
 
 "Index Register plus Register Offset"
-     `REG, REG, REG'
+     'REG, REG, REG'
 
 "Index Register plus Register Offset with Post-increment"
-     `REG, REG, REG+'
+     'REG, REG, REG+'
 
 "Index Register plus Register Offset with Pre-decrement"
-     `REG, REG, -REG'
-
-     The register can be either `R0', `R1', `R2', `R3', `R4', `R5',
-     `R6' or `R7'.
+     'REG, REG, -REG'
 
+     The register can be either 'R0', 'R1', 'R2', 'R3', 'R4', 'R5', 'R6'
+     or 'R7'.
 
    Convience macro opcodes to deal with 16-bit values have been added.
 
 "Immediate 16 Bit Wide"
-     `#NUMBER', or `*SYMBOL'
+     '#NUMBER', or '*SYMBOL'
 
      For example:
 
@@ -20825,7 +20612,7 @@ File: as.info,  Node: XGATE-Directives,  Next: XGATE-Float,  Prev: XGATE-Syntax,
 9.50.3 Assembler Directives
 ---------------------------
 
-The XGATE version of `as' have the following specific assembler
+The XGATE version of 'as' have the following specific assembler
 directives:
 
 
@@ -20838,15 +20625,15 @@ Packed decimal (P) format floating literals are not supported(yet).
 
    The floating point formats generated by directives are these.
 
-`.float'
-     `Single' precision floating point constants.
+'.float'
+     'Single' precision floating point constants.
 
-`.double'
-     `Double' precision floating point constants.
+'.double'
+     'Double' precision floating point constants.
 
-`.extend'
-`.ldouble'
-     `Extended' precision (`long double') floating point constants.
+'.extend'
+'.ldouble'
+     'Extended' precision ('long double') floating point constants.
 
 
 File: as.info,  Node: XGATE-opcodes,  Prev: XGATE-Float,  Up: XGATE-Dependent
@@ -20882,15 +20669,15 @@ File: as.info,  Node: XStormy16-Chars,  Up: XStormy16 Syntax
 9.51.1.1 Special Characters
 ...........................
 
-`#' is the line comment character.  If a `#' appears as the first
-character of a line, the whole line is treated as a comment, but in
-this case the line can also be a logical line number directive (*note
+'#' is the line comment character.  If a '#' appears as the first
+character of a line, the whole line is treated as a comment, but in this
+case the line can also be a logical line number directive (*note
 Comments::) or a preprocessor control command (*note Preprocessing::).
 
-   A semicolon (`;') can be used to start a comment that extends from
+   A semicolon (';') can be used to start a comment that extends from
 wherever the character appears on the line up to the end of the line.
 
-   The `|' character can be used to separate statements on the same
+   The '|' character can be used to separate statements on the same
 line.
 
 
@@ -20899,52 +20686,50 @@ File: as.info,  Node: XStormy16 Directives,  Next: XStormy16 Opcodes,  Prev: XSt
 9.51.2 XStormy16 Machine Directives
 -----------------------------------
 
-`.16bit_pointers'
-     Like the `--16bit-pointers' command line option this directive
+'.16bit_pointers'
+     Like the '--16bit-pointers' command line option this directive
      indicates that the assembly code makes use of 16-bit pointers.
 
-`.32bit_pointers'
-     Like the `--32bit-pointers' command line option this directive
+'.32bit_pointers'
+     Like the '--32bit-pointers' command line option this directive
      indicates that the assembly code makes use of 32-bit pointers.
 
-`.no_pointers'
-     Like the `--no-pointers' command line option this directive
+'.no_pointers'
+     Like the '--no-pointers' command line option this directive
      indicates that the assembly code does not makes use pointers.
 
-
 
 File: as.info,  Node: XStormy16 Opcodes,  Prev: XStormy16 Directives,  Up: XSTORMY16-Dependent
 
 9.51.3 XStormy16 Pseudo-Opcodes
 -------------------------------
 
-`as' implements all the standard XStormy16 opcodes.
+'as' implements all the standard XStormy16 opcodes.
 
-   `as' also implements the following pseudo ops:
+   'as' also implements the following pseudo ops:
 
-`@lo()'
+'@lo()'
      Computes the lower 16 bits of the given expression and stores it
      into the immediate operand field of the given instruction.  For
      example:
 
-     `add r6, @lo(here - there)'
+     'add r6, @lo(here - there)'
 
      computes the difference between the address of labels 'here' and
      'there', takes the lower 16 bits of this difference and adds it to
      register 6.
 
-`@hi()'
+'@hi()'
      Computes the higher 16 bits of the given expression and stores it
      into the immediate operand field of the given instruction.  For
      example:
 
-     `addc r7, @hi(here - there)'
+     'addc r7, @hi(here - there)'
 
      computes the difference between the address of labels 'here' and
-     'there', takes the upper 16 bits of this difference, shifts it
-     down 16 bits and then adds it, along with the carry bit, to the
-     value in register 7.
-
+     'there', takes the upper 16 bits of this difference, shifts it down
+     16 bits and then adds it, along with the carry bit, to the value in
+     register 7.
 
 
 File: as.info,  Node: Xtensa-Dependent,  Next: Z80-Dependent,  Prev: XSTORMY16-Dependent,  Up: Machine Dependencies
@@ -20952,10 +20737,10 @@ File: as.info,  Node: Xtensa-Dependent,  Next: Z80-Dependent,  Prev: XSTORMY16-D
 9.52 Xtensa Dependent Features
 ==============================
 
-   This chapter covers features of the GNU assembler that are specific
-to the Xtensa architecture.  For details about the Xtensa instruction
-set, please consult the `Xtensa Instruction Set Architecture (ISA)
-Reference Manual'.
+This chapter covers features of the GNU assembler that are specific to
+the Xtensa architecture.  For details about the Xtensa instruction set,
+please consult the 'Xtensa Instruction Set Architecture (ISA) Reference
+Manual'.
 
 * Menu:
 
@@ -20971,52 +20756,51 @@ File: as.info,  Node: Xtensa Options,  Next: Xtensa Syntax,  Up: Xtensa-Dependen
 9.52.1 Command Line Options
 ---------------------------
 
-`--text-section-literals | --no-text-section-literals'
+'--text-section-literals | --no-text-section-literals'
      Control the treatment of literal pools.  The default is
-     `--no-text-section-literals', which places literals in separate
+     '--no-text-section-literals', which places literals in separate
      sections in the output file.  This allows the literal pool to be
-     placed in a data RAM/ROM.  With `--text-section-literals', the
-     literals are interspersed in the text section in order to keep
-     them as close as possible to their references.  This may be
-     necessary for large assembly files, where the literals would
-     otherwise be out of range of the `L32R' instructions in the text
-     section.  These options only affect literals referenced via
-     PC-relative `L32R' instructions; literals for absolute mode `L32R'
-     instructions are handled separately.  *Note literal: Literal
-     Directive.
-
-`--absolute-literals | --no-absolute-literals'
-     Indicate to the assembler whether `L32R' instructions use absolute
+     placed in a data RAM/ROM. With '--text-section-literals', the
+     literals are interspersed in the text section in order to keep them
+     as close as possible to their references.  This may be necessary
+     for large assembly files, where the literals would otherwise be out
+     of range of the 'L32R' instructions in the text section.  These
+     options only affect literals referenced via PC-relative 'L32R'
+     instructions; literals for absolute mode 'L32R' instructions are
+     handled separately.  *Note literal: Literal Directive.
+
+'--absolute-literals | --no-absolute-literals'
+     Indicate to the assembler whether 'L32R' instructions use absolute
      or PC-relative addressing.  If the processor includes the absolute
-     addressing option, the default is to use absolute `L32R'
-     relocations.  Otherwise, only the PC-relative `L32R' relocations
+     addressing option, the default is to use absolute 'L32R'
+     relocations.  Otherwise, only the PC-relative 'L32R' relocations
      can be used.
 
-`--target-align | --no-target-align'
-     Enable or disable automatic alignment to reduce branch penalties
-     at some expense in code size.  *Note Automatic Instruction
-     Alignment: Xtensa Automatic Alignment.  This optimization is
-     enabled by default.  Note that the assembler will always align
-     instructions like `LOOP' that have fixed alignment requirements.
+'--target-align | --no-target-align'
+     Enable or disable automatic alignment to reduce branch penalties at
+     some expense in code size.  *Note Automatic Instruction Alignment:
+     Xtensa Automatic Alignment.  This optimization is enabled by
+     default.  Note that the assembler will always align instructions
+     like 'LOOP' that have fixed alignment requirements.
 
-`--longcalls | --no-longcalls'
+'--longcalls | --no-longcalls'
      Enable or disable transformation of call instructions to allow
      calls across a greater range of addresses.  *Note Function Call
      Relaxation: Xtensa Call Relaxation.  This option should be used
      when call targets can potentially be out of range.  It may degrade
      both code size and performance, but the linker can generally
      optimize away the unnecessary overhead when a call ends up within
-     range.  The default is `--no-longcalls'.
+     range.  The default is '--no-longcalls'.
 
-`--transform | --no-transform'
+'--transform | --no-transform'
      Enable or disable all assembler transformations of Xtensa
      instructions, including both relaxation and optimization.  The
-     default is `--transform'; `--no-transform' should only be used in
+     default is '--transform'; '--no-transform' should only be used in
      the rare cases when the instructions must be exactly as specified
-     in the assembly source.  Using `--no-transform' causes out of range
+     in the assembly source.  Using '--no-transform' causes out of range
      instruction operands to be errors.
 
-`--rename-section OLDNAME=NEWNAME'
+'--rename-section OLDNAME=NEWNAME'
      Rename the OLDNAME section to NEWNAME.  This option can be used
      multiple times to rename multiple sections.
 
@@ -21026,11 +20810,11 @@ File: as.info,  Node: Xtensa Syntax,  Next: Xtensa Optimizations,  Prev: Xtensa
 9.52.2 Assembler Syntax
 -----------------------
 
-Block comments are delimited by `/*' and `*/'.  End of line comments
-may be introduced with either `#' or `//'.
+Block comments are delimited by '/*' and '*/'.  End of line comments may
+be introduced with either '#' or '//'.
 
-   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::).
 
@@ -21039,7 +20823,7 @@ whitespace and an optional comma-separated list of operands:
 
      OPCODE [OPERAND, ...]
 
-   Instructions must be separated by a newline or semicolon (`;').
+   Instructions must be separated by a newline or semicolon (';').
 
    FLIX instructions, which bundle multiple opcodes together in a single
 instruction, are specified by enclosing the bundled opcodes inside
@@ -21082,11 +20866,11 @@ File: as.info,  Node: Xtensa Opcodes,  Next: Xtensa Registers,  Up: Xtensa Synta
 9.52.2.1 Opcode Names
 .....................
 
-See the `Xtensa Instruction Set Architecture (ISA) Reference Manual'
-for a complete list of opcodes and descriptions of their semantics.
+See the 'Xtensa Instruction Set Architecture (ISA) Reference Manual' for
+a complete list of opcodes and descriptions of their semantics.
 
-   If an opcode name is prefixed with an underscore character (`_'),
-`as' will not transform that instruction in any way.  The underscore
+   If an opcode name is prefixed with an underscore character ('_'),
+'as' will not transform that instruction in any way.  The underscore
 prefix disables both optimization (*note Xtensa Optimizations: Xtensa
 Optimizations.) and relaxation (*note Xtensa Relaxation: Xtensa
 Relaxation.) for that particular instruction.  Only use the underscore
@@ -21097,19 +20881,19 @@ disabling relaxation.
 
    Note that this special handling of underscore prefixes only applies
 to Xtensa opcodes, not to either built-in macros or user-defined macros.
-When an underscore prefix is used with a macro (e.g., `_MOV'), it
-refers to a different macro.  The assembler generally provides built-in
-macros both with and without the underscore prefix, where the underscore
+When an underscore prefix is used with a macro (e.g., '_MOV'), it refers
+to a different macro.  The assembler generally provides built-in macros
+both with and without the underscore prefix, where the underscore
 versions behave as if the underscore carries through to the instructions
-in the macros.  For example, `_MOV' may expand to `_MOV.N'.
+in the macros.  For example, '_MOV' may expand to '_MOV.N'.
 
    The underscore prefix only applies to individual instructions, not to
 series of instructions.  For example, if a series of instructions have
 underscore prefixes, the assembler will not transform the individual
 instructions, but it may insert other instructions between them (e.g.,
-to align a `LOOP' instruction).  To prevent the assembler from
-modifying a series of instructions as a whole, use the `no-transform'
-directive.  *Note transform: Transform Directive.
+to align a 'LOOP' instruction).  To prevent the assembler from modifying
+a series of instructions as a whole, use the 'no-transform' directive.
+*Note transform: Transform Directive.
 
 
 File: as.info,  Node: Xtensa Registers,  Prev: Xtensa Opcodes,  Up: Xtensa Syntax
@@ -21119,11 +20903,11 @@ File: as.info,  Node: Xtensa Registers,  Prev: Xtensa Opcodes,  Up: Xtensa Synta
 
 The assembly syntax for a register file entry is the "short" name for a
 TIE register file followed by the index into that register file.  For
-example, the general-purpose `AR' register file has a short name of
-`a', so these registers are named `a0'...`a15'.  As a special feature,
-`sp' is also supported as a synonym for `a1'.  Additional registers may
-be added by processor configuration options and by designer-defined TIE
-extensions.  An initial `$' character is optional in all register names.
+example, the general-purpose 'AR' register file has a short name of 'a',
+so these registers are named 'a0'...'a15'.  As a special feature, 'sp'
+is also supported as a synonym for 'a1'.  Additional registers may be
+added by processor configuration options and by designer-defined TIE
+extensions.  An initial '$' character is optional in all register names.
 
 
 File: as.info,  Node: Xtensa Optimizations,  Next: Xtensa Relaxation,  Prev: Xtensa Syntax,  Up: Xtensa-Dependent
@@ -21131,7 +20915,7 @@ File: as.info,  Node: Xtensa Optimizations,  Next: Xtensa Relaxation,  Prev: Xte
 9.52.3 Xtensa Optimizations
 ---------------------------
 
-The optimizations currently supported by `as' are generation of density
+The optimizations currently supported by 'as' are generation of density
 instructions where appropriate and automatic branch target alignment.
 
 * Menu:
@@ -21152,9 +20936,9 @@ assembler automatically translates instructions from the core Xtensa
 instruction set into equivalent instructions from the Xtensa code
 density option.  This translation can be disabled by using underscore
 prefixes (*note Opcode Names: Xtensa Opcodes.), by using the
-`--no-transform' command-line option (*note Command Line Options:
-Xtensa Options.), or by using the `no-transform' directive (*note
-transform: Transform Directive.).
+'--no-transform' command-line option (*note Command Line Options: Xtensa
+Options.), or by using the 'no-transform' directive (*note transform:
+Transform Directive.).
 
    It is a good idea _not_ to use the density instructions directly.
 The assembler will automatically select dense instructions where
@@ -21177,10 +20961,9 @@ align branch targets so they do not cross instruction fetch boundaries.
 instruction fetch widths.)  An instruction immediately following a call
 is treated as a branch target in this context, because it will be the
 target of a return from the call.  This alignment has the potential to
-reduce branch penalties at some expense in code size.  This
-optimization is enabled by default.  You can disable it with the
-`--no-target-align' command-line option (*note Command Line Options:
-Xtensa Options.).
+reduce branch penalties at some expense in code size.  This optimization
+is enabled by default.  You can disable it with the '--no-target-align'
+command-line option (*note Command Line Options: Xtensa Options.).
 
    The target alignment optimization is done without adding instructions
 that could increase the execution time of the program.  If there are
@@ -21188,23 +20971,23 @@ density instructions in the code preceding a target, the assembler can
 change the target alignment by widening some of those instructions to
 the equivalent 24-bit instructions.  Extra bytes of padding can be
 inserted immediately following unconditional jump and return
-instructions.  This approach is usually successful in aligning many,
-but not all, branch targets.
-
-   The `LOOP' family of instructions must be aligned such that the
-first instruction in the loop body does not cross an instruction fetch
-boundary (e.g., with a 32-bit fetch width, a `LOOP' instruction must be
-on either a 1 or 2 mod 4 byte boundary).  The assembler knows about
-this restriction and inserts the minimal number of 2 or 3 byte no-op
+instructions.  This approach is usually successful in aligning many, but
+not all, branch targets.
+
+   The 'LOOP' family of instructions must be aligned such that the first
+instruction in the loop body does not cross an instruction fetch
+boundary (e.g., with a 32-bit fetch width, a 'LOOP' instruction must be
+on either a 1 or 2 mod 4 byte boundary).  The assembler knows about this
+restriction and inserts the minimal number of 2 or 3 byte no-op
 instructions to satisfy it.  When no-op instructions are added, any
 label immediately preceding the original loop will be moved in order to
 refer to the loop instruction, not the newly generated no-op
 instruction.  To preserve binary compatibility across processors with
 different fetch widths, the assembler conservatively assumes a 32-bit
-fetch width when aligning `LOOP' instructions (except if the first
+fetch width when aligning 'LOOP' instructions (except if the first
 instruction in the loop is a 64-bit instruction).
 
-   Previous versions of the assembler automatically aligned `ENTRY'
+   Previous versions of the assembler automatically aligned 'ENTRY'
 instructions to 4-byte boundaries, but that alignment is now the
 programmer's responsibility.
 
@@ -21215,12 +20998,12 @@ File: as.info,  Node: Xtensa Relaxation,  Next: Xtensa Directives,  Prev: Xtensa
 ------------------------
 
 When an instruction operand is outside the range allowed for that
-particular instruction field, `as' can transform the code to use a
+particular instruction field, 'as' can transform the code to use a
 functionally-equivalent instruction or sequence of instructions.  This
 process is known as "relaxation".  This is typically done for branch
 instructions because the distance of the branch targets is not known
 until assembly-time.  The Xtensa assembler offers branch relaxation and
-also extends this concept to function calls, `MOVI' instructions and
+also extends this concept to function calls, 'MOVI' instructions and
 other instructions with immediate fields.
 
 * Menu:
@@ -21248,21 +21031,21 @@ replace the branch with a branch around a jump.  For example,
          j L
      M:
 
-   (The `BNEZ.N' instruction would be used in this example only if the
-density option is available.  Otherwise, `BNEZ' would be used.)
+   (The 'BNEZ.N' instruction would be used in this example only if the
+density option is available.  Otherwise, 'BNEZ' would be used.)
 
    This relaxation works well because the unconditional jump instruction
 has a much larger offset range than the various conditional branches.
 However, an error will occur if a branch target is beyond the range of a
-jump instruction.  `as' cannot relax unconditional jumps.  Similarly,
-an error will occur if the original input contains an unconditional
-jump to a target that is out of range.
+jump instruction.  'as' cannot relax unconditional jumps.  Similarly, an
+error will occur if the original input contains an unconditional jump to
+a target that is out of range.
 
    Branch relaxation is enabled by default.  It can be disabled by using
 underscore prefixes (*note Opcode Names: Xtensa Opcodes.), the
-`--no-transform' command-line option (*note Command Line Options:
-Xtensa Options.), or the `no-transform' directive (*note transform:
-Transform Directive.).
+'--no-transform' command-line option (*note Command Line Options: Xtensa
+Options.), or the 'no-transform' directive (*note transform: Transform
+Directive.).
 
 
 File: as.info,  Node: Xtensa Call Relaxation,  Next: Xtensa Immediate Relaxation,  Prev: Xtensa Branch Relaxation,  Up: Xtensa Relaxation
@@ -21271,15 +21054,14 @@ File: as.info,  Node: Xtensa Call Relaxation,  Next: Xtensa Immediate Relaxation
 .................................
 
 Function calls may require relaxation because the Xtensa immediate call
-instructions (`CALL0', `CALL4', `CALL8' and `CALL12') provide a
+instructions ('CALL0', 'CALL4', 'CALL8' and 'CALL12') provide a
 PC-relative offset of only 512 Kbytes in either direction.  For larger
-programs, it may be necessary to use indirect calls (`CALLX0',
-`CALLX4', `CALLX8' and `CALLX12') where the target address is specified
-in a register.  The Xtensa assembler can automatically relax immediate
-call instructions into indirect call instructions.  This relaxation is
-done by loading the address of the called function into the callee's
-return address register and then using a `CALLX' instruction.  So, for
-example:
+programs, it may be necessary to use indirect calls ('CALLX0', 'CALLX4',
+'CALLX8' and 'CALLX12') where the target address is specified in a
+register.  The Xtensa assembler can automatically relax immediate call
+instructions into indirect call instructions.  This relaxation is done
+by loading the address of the called function into the callee's return
+address register and then using a 'CALLX' instruction.  So, for example:
 
          call8 func
 
@@ -21300,7 +21082,7 @@ assembler for those cases where direct calls are sufficient.
 effect on both code size and performance, although the linker can
 usually eliminate the unnecessary overhead.  If a program is too large
 and some of the calls are out of range, function call relaxation can be
-enabled using the `--longcalls' command-line option or the `longcalls'
+enabled using the '--longcalls' command-line option or the 'longcalls'
 directive (*note longcalls: Longcalls Directive.).
 
 
@@ -21310,14 +21092,14 @@ File: as.info,  Node: Xtensa Immediate Relaxation,  Prev: Xtensa Call Relaxation
 .........................................
 
 The assembler normally performs the following other relaxations.  They
-can be disabled by using underscore prefixes (*note Opcode Names:
-Xtensa Opcodes.), the `--no-transform' command-line option (*note
-Command Line Options: Xtensa Options.), or the `no-transform' directive
-(*note transform: Transform Directive.).
+can be disabled by using underscore prefixes (*note Opcode Names: Xtensa
+Opcodes.), the '--no-transform' command-line option (*note Command Line
+Options: Xtensa Options.), or the 'no-transform' directive (*note
+transform: Transform Directive.).
 
-   The `MOVI' machine instruction can only materialize values in the
+   The 'MOVI' machine instruction can only materialize values in the
 range from -2048 to 2047.  Values outside this range are best
-materialized with `L32R' instructions.  Thus:
+materialized with 'L32R' instructions.  Thus:
 
          movi a0, 100000
 
@@ -21326,11 +21108,11 @@ materialized with `L32R' instructions.  Thus:
          .literal .L1, 100000
          l32r a0, .L1
 
-   The `L8UI' machine instruction can only be used with immediate
-offsets in the range from 0 to 255. The `L16SI' and `L16UI' machine
-instructions can only be used with offsets from 0 to 510.  The `L32I'
+   The 'L8UI' machine instruction can only be used with immediate
+offsets in the range from 0 to 255.  The 'L16SI' and 'L16UI' machine
+instructions can only be used with offsets from 0 to 510.  The 'L32I'
 machine instruction can only be used with offsets from 0 to 1020.  A
-load offset outside these ranges can be materialized with an `L32R'
+load offset outside these ranges can be materialized with an 'L32R'
 instruction if the destination register of the load is different than
 the source address register.  For example:
 
@@ -21346,16 +21128,16 @@ the source address register.  For example:
 If the load destination and source address register are the same, an
 out-of-range offset causes an error.
 
-   The Xtensa `ADDI' instruction only allows immediate operands in the
+   The Xtensa 'ADDI' instruction only allows immediate operands in the
 range from -128 to 127.  There are a number of alternate instruction
-sequences for the `ADDI' operation.  First, if the immediate is 0, the
-`ADDI' will be turned into a `MOV.N' instruction (or the equivalent
-`OR' instruction if the code density option is not available).  If the
-`ADDI' immediate is outside of the range -128 to 127, but inside the
-range -32896 to 32639, an `ADDMI' instruction or `ADDMI'/`ADDI'
-sequence will be used.  Finally, if the immediate is outside of this
-range and a free register is available, an `L32R'/`ADD' sequence will
-be used with a literal allocated from the literal pool.
+sequences for the 'ADDI' operation.  First, if the immediate is 0, the
+'ADDI' will be turned into a 'MOV.N' instruction (or the equivalent 'OR'
+instruction if the code density option is not available).  If the 'ADDI'
+immediate is outside of the range -128 to 127, but inside the range
+-32896 to 32639, an 'ADDMI' instruction or 'ADDMI'/'ADDI' sequence will
+be used.  Finally, if the immediate is outside of this range and a free
+register is available, an 'L32R'/'ADD' sequence will be used with a
+literal allocated from the literal pool.
 
    For example:
 
@@ -21389,9 +21171,9 @@ The Xtensa assembler supports a region-based directive syntax:
    All the Xtensa-specific directives that apply to a region of code use
 this syntax.
 
-   The directive applies to code between the `.begin' and the `.end'.
-The state of the option after the `.end' reverts to what it was before
-the `.begin'.  A nested `.begin'/`.end' region can further change the
+   The directive applies to code between the '.begin' and the '.end'.
+The state of the option after the '.end' reverts to what it was before
+the '.begin'.  A nested '.begin'/'.end' region can further change the
 state of the directive without having to be aware of its outer state.
 For example, consider:
 
@@ -21403,16 +21185,15 @@ For example, consider:
      N:  add a0, a1, a2
          .end no-transform
 
-   The `ADD' opcodes at `L' and `N' in the outer `no-transform' region
-both result in `ADD' machine instructions, but the assembler selects an
-`ADD.N' instruction for the `ADD' at `M' in the inner `transform'
+   The 'ADD' opcodes at 'L' and 'N' in the outer 'no-transform' region
+both result in 'ADD' machine instructions, but the assembler selects an
+'ADD.N' instruction for the 'ADD' at 'M' in the inner 'transform'
 region.
 
-   The advantage of this style is that it works well inside macros
-which can preserve the context of their callers.
+   The advantage of this style is that it works well inside macros which
+can preserve the context of their callers.
 
    The following directives are available:
-
 * Menu:
 
 * Schedule Directive::         Enable instruction scheduling.
@@ -21429,13 +21210,13 @@ File: as.info,  Node: Schedule Directive,  Next: Longcalls Directive,  Up: Xtens
 9.52.5.1 schedule
 .................
 
-The `schedule' directive is recognized only for compatibility with
+The 'schedule' directive is recognized only for compatibility with
 Tensilica's assembler.
 
          .begin [no-]schedule
          .end [no-]schedule
 
-   This directive is ignored and has no effect on `as'.
+   This directive is ignored and has no effect on 'as'.
 
 
 File: as.info,  Node: Longcalls Directive,  Next: Transform Directive,  Prev: Schedule Directive,  Up: Xtensa Directives
@@ -21443,14 +21224,14 @@ File: as.info,  Node: Longcalls Directive,  Next: Transform Directive,  Prev: Sc
 9.52.5.2 longcalls
 ..................
 
-The `longcalls' directive enables or disables function call relaxation.
+The 'longcalls' directive enables or disables function call relaxation.
 *Note Function Call Relaxation: Xtensa Call Relaxation.
 
          .begin [no-]longcalls
          .end [no-]longcalls
 
-   Call relaxation is disabled by default unless the `--longcalls'
-command-line option is specified.  The `longcalls' directive overrides
+   Call relaxation is disabled by default unless the '--longcalls'
+command-line option is specified.  The 'longcalls' directive overrides
 the default determined by the command-line options.
 
 
@@ -21466,8 +21247,8 @@ optimization (*note Xtensa Optimizations: Xtensa Optimizations.).
          .begin [no-]transform
          .end [no-]transform
 
-   Transformations are enabled by default unless the `--no-transform'
-option is used.  The `transform' directive overrides the default
+   Transformations are enabled by default unless the '--no-transform'
+option is used.  The 'transform' directive overrides the default
 determined by the command-line options.  An underscore opcode prefix,
 disabling transformation of that opcode, always takes precedence over
 both directives and command-line flags.
@@ -21478,14 +21259,14 @@ File: as.info,  Node: Literal Directive,  Next: Literal Position Directive,  Pre
 9.52.5.4 literal
 ................
 
-The `.literal' directive is used to define literal pool data, i.e.,
-read-only 32-bit data accessed via `L32R' instructions.
+The '.literal' directive is used to define literal pool data, i.e.,
+read-only 32-bit data accessed via 'L32R' instructions.
 
          .literal LABEL, VALUE[, VALUE...]
 
-   This directive is similar to the standard `.word' directive, except
+   This directive is similar to the standard '.word' directive, except
 that the actual location of the literal data is determined by the
-assembler and linker, not by the position of the `.literal' directive.
+assembler and linker, not by the position of the '.literal' directive.
 Using this directive gives the assembler freedom to locate the literal
 data in the most appropriate place and possibly to combine identical
 literals.  For example, the code:
@@ -21494,59 +21275,58 @@ literals.  For example, the code:
          .literal .L1, sym
          l32r    a4, .L1
 
-   can be used to load a pointer to the symbol `sym' into register
-`a4'.  The value of `sym' will not be placed between the `ENTRY' and
-`L32R' instructions; instead, the assembler puts the data in a literal
-pool.
+   can be used to load a pointer to the symbol 'sym' into register 'a4'.
+The value of 'sym' will not be placed between the 'ENTRY' and 'L32R'
+instructions; instead, the assembler puts the data in a literal pool.
 
    Literal pools are placed by default in separate literal sections;
-however, when using the `--text-section-literals' option (*note Command
+however, when using the '--text-section-literals' option (*note Command
 Line Options: Xtensa Options.), the literal pools for PC-relative mode
-`L32R' instructions are placed in the current section.(1) These text
-section literal pools are created automatically before `ENTRY'
-instructions and manually after `.literal_position' directives (*note
+'L32R' instructions are placed in the current section.(1)  These text
+section literal pools are created automatically before 'ENTRY'
+instructions and manually after '.literal_position' directives (*note
 literal_position: Literal Position Directive.).  If there are no
-preceding `ENTRY' instructions, explicit `.literal_position' directives
-must be used to place the text section literal pools; otherwise, `as'
+preceding 'ENTRY' instructions, explicit '.literal_position' directives
+must be used to place the text section literal pools; otherwise, 'as'
 will report an error.
 
    When literals are placed in separate sections, the literal section
 names are derived from the names of the sections where the literals are
-defined.  The base literal section names are `.literal' for PC-relative
-mode `L32R' instructions and `.lit4' for absolute mode `L32R'
+defined.  The base literal section names are '.literal' for PC-relative
+mode 'L32R' instructions and '.lit4' for absolute mode 'L32R'
 instructions (*note absolute-literals: Absolute Literals Directive.).
-These base names are used for literals defined in the default `.text'
+These base names are used for literals defined in the default '.text'
 section.  For literals defined in other sections or within the scope of
-a `literal_prefix' directive (*note literal_prefix: Literal Prefix
+a 'literal_prefix' directive (*note literal_prefix: Literal Prefix
 Directive.), the following rules determine the literal section name:
 
   1. If the current section is a member of a section group, the literal
      section name includes the group name as a suffix to the base
-     `.literal' or `.lit4' name, with a period to separate the base
-     name and group name.  The literal section is also made a member of
-     the group.
+     '.literal' or '.lit4' name, with a period to separate the base name
+     and group name.  The literal section is also made a member of the
+     group.
 
-  2. If the current section name (or `literal_prefix' value) begins with
-     "`.gnu.linkonce.KIND.'", the literal section name is formed by
-     replacing "`.KIND'" with the base `.literal' or `.lit4' name.  For
+  2. If the current section name (or 'literal_prefix' value) begins with
+     "'.gnu.linkonce.KIND.'", the literal section name is formed by
+     replacing "'.KIND'" with the base '.literal' or '.lit4' name.  For
      example, for literals defined in a section named
-     `.gnu.linkonce.t.func', the literal section will be
-     `.gnu.linkonce.literal.func' or `.gnu.linkonce.lit4.func'.
+     '.gnu.linkonce.t.func', the literal section will be
+     '.gnu.linkonce.literal.func' or '.gnu.linkonce.lit4.func'.
 
-  3. If the current section name (or `literal_prefix' value) ends with
-     `.text', the literal section name is formed by replacing that
-     suffix with the base `.literal' or `.lit4' name.  For example, for
-     literals defined in a section named `.iram0.text', the literal
-     section will be `.iram0.literal' or `.iram0.lit4'.
+  3. If the current section name (or 'literal_prefix' value) ends with
+     '.text', the literal section name is formed by replacing that
+     suffix with the base '.literal' or '.lit4' name.  For example, for
+     literals defined in a section named '.iram0.text', the literal
+     section will be '.iram0.literal' or '.iram0.lit4'.
 
-  4. If none of the preceding conditions apply, the literal section
-     name is formed by adding the base `.literal' or `.lit4' name as a
-     suffix to the current section name (or `literal_prefix' value).
+  4. If none of the preceding conditions apply, the literal section name
+     is formed by adding the base '.literal' or '.lit4' name as a suffix
+     to the current section name (or 'literal_prefix' value).
 
    ---------- Footnotes ----------
 
-   (1) Literals for the `.init' and `.fini' sections are always placed
-in separate sections, even when `--text-section-literals' is enabled.
+   (1) Literals for the '.init' and '.fini' sections are always placed
+in separate sections, even when '--text-section-literals' is enabled.
 
 
 File: as.info,  Node: Literal Position Directive,  Next: Literal Prefix Directive,  Prev: Literal Directive,  Up: Xtensa Directives
@@ -21554,33 +21334,33 @@ File: as.info,  Node: Literal Position Directive,  Next: Literal Prefix Directiv
 9.52.5.5 literal_position
 .........................
 
-When using `--text-section-literals' to place literals inline in the
-section being assembled, the `.literal_position' directive can be used
+When using '--text-section-literals' to place literals inline in the
+section being assembled, the '.literal_position' directive can be used
 to mark a potential location for a literal pool.
 
          .literal_position
 
-   The `.literal_position' directive is ignored when the
-`--text-section-literals' option is not used or when `L32R'
-instructions use the absolute addressing mode.
+   The '.literal_position' directive is ignored when the
+'--text-section-literals' option is not used or when 'L32R' instructions
+use the absolute addressing mode.
 
    The assembler will automatically place text section literal pools
-before `ENTRY' instructions, so the `.literal_position' directive is
+before 'ENTRY' instructions, so the '.literal_position' directive is
 only needed to specify some other location for a literal pool.  You may
 need to add an explicit jump instruction to skip over an inline literal
 pool.
 
-   For example, an interrupt vector does not begin with an `ENTRY'
+   For example, an interrupt vector does not begin with an 'ENTRY'
 instruction so the assembler will be unable to automatically find a good
 place to put a literal pool.  Moreover, the code for the interrupt
 vector must be at a specific starting address, so the literal pool
 cannot come before the start of the code.  The literal pool for the
 vector must be explicitly positioned in the middle of the vector (before
 any uses of the literals, due to the negative offsets used by
-PC-relative `L32R' instructions).  The `.literal_position' directive
-can be used to do this.  In the following code, the literal for `M'
-will automatically be aligned correctly and is placed after the
-unconditional jump.
+PC-relative 'L32R' instructions).  The '.literal_position' directive can
+be used to do this.  In the following code, the literal for 'M' will
+automatically be aligned correctly and is placed after the unconditional
+jump.
 
          .global M
      code_start:
@@ -21596,7 +21376,7 @@ File: as.info,  Node: Literal Prefix Directive,  Next: Absolute Literals Directi
 9.52.5.6 literal_prefix
 .......................
 
-The `literal_prefix' directive allows you to override the default
+The 'literal_prefix' directive allows you to override the default
 literal section names, which are derived from the names of the sections
 where the literals are defined.
 
@@ -21608,7 +21388,7 @@ names are derived from the NAME argument instead of the name of the
 current section.  The rules used to derive the literal section names do
 not change.  *Note literal: Literal Directive.  If the NAME argument is
 omitted, the literal sections revert to the defaults.  This directive
-has no effect when using the `--text-section-literals' option (*note
+has no effect when using the '--text-section-literals' option (*note
 Command Line Options: Xtensa Options.).
 
 
@@ -21617,27 +21397,27 @@ File: as.info,  Node: Absolute Literals Directive,  Prev: Literal Prefix Directi
 9.52.5.7 absolute-literals
 ..........................
 
-The `absolute-literals' and `no-absolute-literals' directives control
-the absolute vs. PC-relative mode for `L32R' instructions.  These are
+The 'absolute-literals' and 'no-absolute-literals' directives control
+the absolute vs. PC-relative mode for 'L32R' instructions.  These are
 relevant only for Xtensa configurations that include the absolute
-addressing option for `L32R' instructions.
+addressing option for 'L32R' instructions.
 
          .begin [no-]absolute-literals
          .end [no-]absolute-literals
 
-   These directives do not change the `L32R' mode--they only cause the
-assembler to emit the appropriate kind of relocation for `L32R'
+   These directives do not change the 'L32R' mode--they only cause the
+assembler to emit the appropriate kind of relocation for 'L32R'
 instructions and to place the literal values in the appropriate section.
-To change the `L32R' mode, the program must write the `LITBASE' special
+To change the 'L32R' mode, the program must write the 'LITBASE' special
 register.  It is the programmer's responsibility to keep track of the
 mode and indicate to the assembler which mode is used in each region of
 code.
 
-   If the Xtensa configuration includes the absolute `L32R' addressing
-option, the default is to assume absolute `L32R' addressing unless the
-`--no-absolute-literals' command-line option is specified.  Otherwise,
-the default is to assume PC-relative `L32R' addressing.  The
-`absolute-literals' directive can then be used to override the default
+   If the Xtensa configuration includes the absolute 'L32R' addressing
+option, the default is to assume absolute 'L32R' addressing unless the
+'--no-absolute-literals' command-line option is specified.  Otherwise,
+the default is to assume PC-relative 'L32R' addressing.  The
+'absolute-literals' directive can then be used to override the default
 determined by the command-line options.
 
 
@@ -21646,12 +21426,12 @@ File: as.info,  Node: Reporting Bugs,  Next: Acknowledgements,  Prev: Machine De
 10 Reporting Bugs
 *****************
 
-Your bug reports play an essential role in making `as' reliable.
+Your bug reports play an essential role in making 'as' reliable.
 
    Reporting a bug may help you by bringing a solution to your problem,
 or it may not.  But in any case the principal function of a bug report
-is to help the entire community by making the next version of `as' work
-better.  Bug reports are your contribution to the maintenance of `as'.
+is to help the entire community by making the next version of 'as' work
+better.  Bug reports are your contribution to the maintenance of 'as'.
 
    In order for a bug report to serve its purpose, you must include the
 information that enables us to fix the bug.
@@ -21671,17 +21451,17 @@ If you are not sure whether you have found a bug, here are some
 guidelines:
 
    * If the assembler gets a fatal signal, for any input whatever, that
-     is a `as' bug.  Reliable assemblers never crash.
+     is a 'as' bug.  Reliable assemblers never crash.
 
-   * If `as' produces an error message for valid input, that is a bug.
+   * If 'as' produces an error message for valid input, that is a bug.
 
-   * If `as' does not produce an error message for invalid input, that
+   * If 'as' does not produce an error message for invalid input, that
      is a bug.  However, you should note that your idea of "invalid
      input" might be our idea of "an extension" or "support for
      traditional practice".
 
    * If you are an experienced user of assemblers, your suggestions for
-     improvement of `as' are welcome in any case.
+     improvement of 'as' are welcome in any case.
 
 
 File: as.info,  Node: Bug Reporting,  Prev: Bug Criteria,  Up: Reporting Bugs
@@ -21690,18 +21470,18 @@ File: as.info,  Node: Bug Reporting,  Prev: Bug Criteria,  Up: Reporting Bugs
 =======================
 
 A number of companies and individuals offer support for GNU products.
-If you obtained `as' from a support organization, we recommend you
+If you obtained 'as' from a support organization, we recommend you
 contact that organization first.
 
    You can find contact information for many support companies and
-individuals in the file `etc/SERVICE' in the GNU Emacs distribution.
+individuals in the file 'etc/SERVICE' in the GNU Emacs distribution.
 
-   In any event, we also recommend that you send bug reports for `as'
-to `http://www.sourceware.org/bugzilla/ and mailto:hjl.tools@gmail.com'.
+   In any event, we also recommend that you send bug reports for 'as' to
+<http://www.sourceware.org/bugzilla/>.
 
-   The fundamental principle of reporting bugs usefully is this:
-*report all the facts*.  If you are not sure whether to state a fact or
-leave it out, state it!
+   The fundamental principle of reporting bugs usefully is this: *report
+all the facts*.  If you are not sure whether to state a fact or leave it
+out, state it!
 
    Often people omit facts because they think they know what causes the
 problem and assume that some details do not matter.  Thus, you might
@@ -21714,8 +21494,8 @@ thing despite the bug.  Play it safe and give a specific, complete
 example.  That is the easiest thing for you to do, and the most helpful.
 
    Keep in mind that the purpose of a bug report is to enable us to fix
-the bug if it is new to us.  Therefore, always write your bug reports
-on the assumption that the bug has not been reported previously.
+the bug if it is new to us.  Therefore, always write your bug reports on
+the assumption that the bug has not been reported previously.
 
    Sometimes people give a few sketchy facts and ask, "Does this ring a
 bell?"  This cannot help us fix a bug, so it is basically useless.  We
@@ -21724,24 +21504,24 @@ might as well expedite matters by sending them to begin with.
 
    To enable us to fix the bug, you should include all these things:
 
-   * The version of `as'.  `as' announces it if you start it with the
-     `--version' argument.
+   * The version of 'as'.  'as' announces it if you start it with the
+     '--version' argument.
 
      Without this, we will not know whether there is any point in
-     looking for the bug in the current version of `as'.
+     looking for the bug in the current version of 'as'.
 
-   * Any patches you may have applied to the `as' source.
+   * Any patches you may have applied to the 'as' source.
 
    * The type of machine you are using, and the operating system name
      and version number.
 
-   * What compiler (and its version) was used to compile `as'--e.g.
-     "`gcc-2.7'".
+   * What compiler (and its version) was used to compile 'as'--e.g.
+     "'gcc-2.7'".
 
    * The command arguments you gave the assembler to assemble your
      example and observe the bug.  To guarantee you will not omit
-     something important, list them all.  A copy of the Makefile (or
-     the output from make) is sufficient.
+     something important, list them all.  A copy of the Makefile (or the
+     output from make) is sufficient.
 
      If we were to try to guess the arguments, we would probably guess
      wrong and then we might not encounter the bug.
@@ -21749,23 +21529,22 @@ might as well expedite matters by sending them to begin with.
    * A complete input file that will reproduce the bug.  If the bug is
      observed when the assembler is invoked via a compiler, send the
      assembler source, not the high level language source.  Most
-     compilers will produce the assembler source when run with the `-S'
-     option.  If you are using `gcc', use the options `-v
-     --save-temps'; this will save the assembler source in a file with
-     an extension of `.s', and also show you exactly how `as' is being
-     run.
+     compilers will produce the assembler source when run with the '-S'
+     option.  If you are using 'gcc', use the options '-v --save-temps';
+     this will save the assembler source in a file with an extension of
+     '.s', and also show you exactly how 'as' is being run.
 
    * A description of what behavior you observe that you believe is
      incorrect.  For example, "It gets a fatal signal."
 
-     Of course, if the bug is that `as' gets a fatal signal, then we
+     Of course, if the bug is that 'as' gets a fatal signal, then we
      will certainly notice it.  But if the bug is incorrect output, we
      might not notice unless it is glaringly wrong.  You might as well
      not give us a chance to make a mistake.
 
      Even if the problem you experience is a fatal signal, you should
      still say so explicitly.  Suppose something strange is going on,
-     such as, your copy of `as' is out of sync, or you have encountered
+     such as, your copy of 'as' is out of sync, or you have encountered
      a bug in the C library on your system.  (This has happened!)  Your
      copy might crash and ours would not.  If you told us to expect a
      crash, then when ours fails to crash, we would know that the bug
@@ -21773,15 +21552,15 @@ might as well expedite matters by sending them to begin with.
      crash, then we would not be able to draw any conclusion from our
      observations.
 
-   * If you wish to suggest changes to the `as' source, send us context
-     diffs, as generated by `diff' with the `-u', `-c', or `-p' option.
+   * If you wish to suggest changes to the 'as' source, send us context
+     diffs, as generated by 'diff' with the '-u', '-c', or '-p' option.
      Always send diffs from the old file to the new file.  If you even
-     discuss something in the `as' source, refer to it by context, not
+     discuss something in the 'as' source, refer to it by context, not
      by line number.
 
-     The line numbers in our development sources will not match those
-     in your sources.  Your line numbers would convey no useful
-     information to us.
+     The line numbers in our development sources will not match those in
+     your sources.  Your line numbers would convey no useful information
+     to us.
 
    Here are some things that are not necessary:
 
@@ -21796,8 +21575,8 @@ might as well expedite matters by sending them to begin with.
      debugger with breakpoints, not by pure deduction from a series of
      examples.  We recommend that you save your time for something else.
 
-     Of course, if you can find a simpler example to report _instead_
-     of the original one, that is a convenience for us.  Errors in the
+     Of course, if you can find a simpler example to report _instead_ of
+     the original one, that is a convenience for us.  Errors in the
      output will be easier to spot, running under the debugger will take
      less time, and so on.
 
@@ -21809,15 +21588,15 @@ might as well expedite matters by sending them to begin with.
 
      A patch for the bug does help us if it is a good one.  But do not
      omit the necessary information, such as the test case, on the
-     assumption that a patch is all we need.  We might see problems
-     with your patch and decide to fix the problem another way, or we
-     might not understand it at all.
+     assumption that a patch is all we need.  We might see problems with
+     your patch and decide to fix the problem another way, or we might
+     not understand it at all.
 
-     Sometimes with a program as complicated as `as' it is very hard to
+     Sometimes with a program as complicated as 'as' it is very hard to
      construct an example that will make the program follow a certain
      path through the code.  If you do not send us the example, we will
-     not be able to construct one, so we will not be able to verify
-     that the bug is fixed.
+     not be able to construct one, so we will not be able to verify that
+     the bug is fixed.
 
      And if we cannot understand what bug you are trying to fix, or why
      your patch should be an improvement, we will not install it.  A
@@ -21837,27 +21616,27 @@ File: as.info,  Node: Acknowledgements,  Next: GNU Free Documentation License,
 If you have contributed to GAS and your name isn't listed here, it is
 not meant as a slight.  We just don't know about it.  Send mail to the
 maintainer, and we'll correct the situation.  Currently the maintainer
-is Nick Clifton (email address `nickc@redhat.com').
+is Nick Clifton (email address 'nickc@redhat.com').
 
    Dean Elsner wrote the original GNU assembler for the VAX.(1)
 
    Jay Fenlason maintained GAS for a while, adding support for
 GDB-specific debug information and the 68k series machines, most of the
-preprocessing pass, and extensive changes in `messages.c',
-`input-file.c', `write.c'.
+preprocessing pass, and extensive changes in 'messages.c',
+'input-file.c', 'write.c'.
 
    K. Richard Pixley maintained GAS for a while, adding various
 enhancements and many bug fixes, including merging support for several
 processors, breaking GAS up to handle multiple object file format back
 ends (including heavy rewrite, testing, an integration of the coff and
 b.out back ends), adding configuration including heavy testing and
-verification of cross assemblers and file splits and renaming,
-converted GAS to strictly ANSI C including full prototypes, added
-support for m680[34]0 and cpu32, did considerable work on i960
-including a COFF port (including considerable amounts of reverse
-engineering), a SPARC opcode file rewrite, DECstation, rs6000, and
-hp300hpux host ports, updated "know" assertions and made them work,
-much other reorganization, cleanup, and lint.
+verification of cross assemblers and file splits and renaming, converted
+GAS to strictly ANSI C including full prototypes, added support for
+m680[34]0 and cpu32, did considerable work on i960 including a COFF port
+(including considerable amounts of reverse engineering), a SPARC opcode
+file rewrite, DECstation, rs6000, and hp300hpux host ports, updated
+"know" assertions and made them work, much other reorganization,
+cleanup, and lint.
 
    Ken Raeburn wrote the high-level BFD interface code to replace most
 of the code in format-specific I/O modules.
@@ -21873,10 +21652,10 @@ Youngdale has done much work with it since.
 of Buffalo University and Torbjorn Granlund of the Swedish Institute of
 Computer Science.
 
-   Keith Knowles at the Open Software Foundation wrote the original
-MIPS back end (`tc-mips.c', `tc-mips.h'), and contributed Rose format
-support (which hasn't been merged in yet).  Ralph Campbell worked with
-the MIPS code to support a.out format.
+   Keith Knowles at the Open Software Foundation wrote the original MIPS
+back end ('tc-mips.c', 'tc-mips.h'), and contributed Rose format support
+(which hasn't been merged in yet).  Ralph Campbell worked with the MIPS
+code to support a.out format.
 
    Support for the Zilog Z8k and Renesas H8/300 processors (tc-z8k,
 tc-h8300), and IEEE 695 object file format (obj-ieee), was written by
@@ -21884,39 +21663,39 @@ Steve Chamberlain of Cygnus Support.  Steve also modified the COFF back
 end to use BFD for some low-level operations, for use with the H8/300
 and AMD 29k targets.
 
-   John Gilmore built the AMD 29000 support, added `.include' support,
+   John Gilmore built the AMD 29000 support, added '.include' support,
 and simplified the configuration of which versions accept which
 directives.  He updated the 68k machine description so that Motorola's
-opcodes always produced fixed-size instructions (e.g., `jsr'), while
-synthetic instructions remained shrinkable (`jbsr').  John fixed many
+opcodes always produced fixed-size instructions (e.g., 'jsr'), while
+synthetic instructions remained shrinkable ('jbsr').  John fixed many
 bugs, including true tested cross-compilation support, and one bug in
 relaxation that took a week and required the proverbial one-bit fix.
 
-   Ian Lance Taylor of Cygnus Support merged the Motorola and MIT
-syntax for the 68k, completed support for some COFF targets (68k, i386
-SVR3, and SCO Unix), added support for MIPS ECOFF and ELF targets,
-wrote the initial RS/6000 and PowerPC assembler, and made a few other
-minor patches.
+   Ian Lance Taylor of Cygnus Support merged the Motorola and MIT syntax
+for the 68k, completed support for some COFF targets (68k, i386 SVR3,
+and SCO Unix), added support for MIPS ECOFF and ELF targets, wrote the
+initial RS/6000 and PowerPC assembler, and made a few other minor
+patches.
 
    Steve Chamberlain made GAS able to generate listings.
 
    Hewlett-Packard contributed support for the HP9000/300.
 
    Jeff Law wrote GAS and BFD support for the native HPPA object format
-(SOM) along with a fairly extensive HPPA testsuite (for both SOM and
-ELF object formats).  This work was supported by both the Center for
+(SOM) along with a fairly extensive HPPA testsuite (for both SOM and ELF
+object formats).  This work was supported by both the Center for
 Software Science at the University of Utah and Cygnus Support.
 
    Support for ELF format files has been worked on by Mark Eichin of
 Cygnus Support (original, incomplete implementation for SPARC), Pete
-Hoogenboom and Jeff Law at the University of Utah (HPPA mainly),
-Michael Meissner of the Open Software Foundation (i386 mainly), and Ken
-Raeburn of Cygnus Support (sparc, and some initial 64-bit support).
+Hoogenboom and Jeff Law at the University of Utah (HPPA mainly), Michael
+Meissner of the Open Software Foundation (i386 mainly), and Ken Raeburn
+of Cygnus Support (sparc, and some initial 64-bit support).
 
    Linas Vepstas added GAS support for the ESA/390 "IBM 370"
 architecture.
 
-   Richard Henderson rewrote the Alpha assembler. Klaus Kaempf wrote
+   Richard Henderson rewrote the Alpha assembler.  Klaus Kaempf wrote
 GAS and BFD support for openVMS/Alpha.
 
    Timothy Wall, Michael Hayes, and Greg Smart contributed to the
@@ -21925,8 +21704,8 @@ various tic* flavors.
    David Heine, Sterling Augustine, Bob Wilson and John Ruttenberg from
 Tensilica, Inc. added support for Xtensa processors.
 
-   Several engineers at Cygnus Support have also provided many small
-bug fixes and configuration enhancements.
+   Several engineers at Cygnus Support have also provided many small bug
+fixes and configuration enhancements.
 
    Jon Beniston added support for the Lattice Mico32 architecture.
 
@@ -21948,7 +21727,7 @@ Appendix A GNU Free Documentation License
                      Version 1.3, 3 November 2008
 
      Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-     `http://fsf.org/'
+     <http://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.
@@ -21973,21 +21752,21 @@ Appendix A GNU Free Documentation License
      free program should come with manuals providing the same freedoms
      that the software does.  But this License is not limited to
      software manuals; it can be used for any textual work, regardless
-     of subject matter or whether it is published as a printed book.
-     We recommend this License principally for works whose purpose is
+     of subject matter or whether it is published as a printed book.  We
+     recommend this License principally for works whose purpose is
      instruction or reference.
 
   1. APPLICABILITY AND DEFINITIONS
 
      This License applies to any manual or other work, in any medium,
-     that contains a notice placed by the copyright holder saying it
-     can be distributed under the terms of this License.  Such a notice
+     that contains a notice placed by the copyright holder saying it can
+     be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
      "Document", below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as "you".  You
-     accept the license if you copy, modify or distribute the work in a
-     way requiring permission under copyright law.
+     of the public is a licensee, and is addressed as "you".  You accept
+     the license if you copy, modify or distribute the work in a way
+     requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
@@ -22005,12 +21784,12 @@ Appendix A GNU Free Documentation License
      regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
-     titles are designated, as being those of Invariant Sections, in
-     the notice that says that the Document is released under this
-     License.  If a section does not fit the above definition of
-     Secondary then it is not allowed to be designated as Invariant.
-     The Document may contain zero Invariant Sections.  If the Document
-     does not identify any Invariant Sections then there are none.
+     titles are designated, as being those of Invariant Sections, in the
+     notice that says that the Document is released under this License.
+     If a section does not fit the above definition of Secondary then it
+     is not allowed to be designated as Invariant.  The Document may
+     contain zero Invariant Sections.  If the Document does not identify
+     any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -22021,27 +21800,27 @@ Appendix A GNU Free Documentation License
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
-     straightforwardly with generic text editors or (for images
-     composed of pixels) generic paint programs or (for drawings) some
-     widely available drawing editor, and that is suitable for input to
-     text formatters or for automatic translation to a variety of
-     formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup, or absence of
-     markup, has been arranged to thwart or discourage subsequent
-     modification by readers is not Transparent.  An image format is
-     not Transparent if used for any substantial amount of text.  A
-     copy that is not "Transparent" is called "Opaque".
+     straightforwardly with generic text editors or (for images composed
+     of pixels) generic paint programs or (for drawings) some widely
+     available drawing editor, and that is suitable for input to text
+     formatters or for automatic translation to a variety of formats
+     suitable for input to text formatters.  A copy made in an otherwise
+     Transparent file format whose markup, or absence of markup, has
+     been arranged to thwart or discourage subsequent modification by
+     readers is not Transparent.  An image format is not Transparent if
+     used for any substantial amount of text.  A copy that is not
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
-     SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML, PostScript or PDF designed for
-     human modification.  Examples of transparent image formats include
-     PNG, XCF and JPG.  Opaque formats include proprietary formats that
-     can be read and edited only by proprietary word processors, SGML or
-     XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML, PostScript or PDF
-     produced by some word processors for output purposes only.
+     SGML or XML using a publicly available DTD, and standard-conforming
+     simple HTML, PostScript or PDF designed for human modification.
+     Examples of transparent image formats include PNG, XCF and JPG.
+     Opaque formats include proprietary formats that can be read and
+     edited only by proprietary word processors, SGML or XML for which
+     the DTD and/or processing tools are not generally available, and
+     the machine-generated HTML, PostScript or PDF produced by some word
+     processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
@@ -22079,8 +21858,8 @@ Appendix A GNU Free Documentation License
      may not use technical measures to obstruct or control the reading
      or further copying of the copies you make or distribute.  However,
      you may accept compensation in exchange for copies.  If you
-     distribute a large enough number of copies you must also follow
-     the conditions in section 3.
+     distribute a large enough number of copies you must also follow the
+     conditions in section 3.
 
      You may also lend copies, under the same conditions stated above,
      and you may publicly display copies.
@@ -22094,12 +21873,11 @@ Appendix A GNU Free Documentation License
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
-     front cover must present the full title with all words of the
-     title equally prominent and visible.  You may add other material
-     on the covers in addition.  Copying with changes limited to the
-     covers, as long as they preserve the title of the Document and
-     satisfy these conditions, can be treated as verbatim copying in
-     other respects.
+     front cover must present the full title with all words of the title
+     equally prominent and visible.  You may add other material on the
+     covers in addition.  Copying with changes limited to the covers, as
+     long as they preserve the title of the Document and satisfy these
+     conditions, can be treated as verbatim copying in other respects.
 
      If the required texts for either cover are too voluminous to fit
      legibly, you should put the first ones listed (as many as fit
@@ -22107,40 +21885,39 @@ Appendix A GNU Free Documentation License
      adjacent pages.
 
      If you publish or distribute Opaque copies of the Document
-     numbering more than 100, you must either include a
-     machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a computer-network location from
-     which the general network-using public has access to download
-     using public-standard network protocols a complete Transparent
-     copy of the Document, free of added material.  If you use the
-     latter option, you must take reasonably prudent steps, when you
-     begin distribution of Opaque copies in quantity, to ensure that
-     this Transparent copy will remain thus accessible at the stated
-     location until at least one year after the last time you
-     distribute an Opaque copy (directly or through your agents or
-     retailers) of that edition to the public.
+     numbering more than 100, you must either include a machine-readable
+     Transparent copy along with each Opaque copy, or state in or with
+     each Opaque copy a computer-network location from which the general
+     network-using public has access to download using public-standard
+     network protocols a complete Transparent copy of the Document, free
+     of added material.  If you use the latter option, you must take
+     reasonably prudent steps, when you begin distribution of Opaque
+     copies in quantity, to ensure that this Transparent copy will
+     remain thus accessible at the stated location until at least one
+     year after the last time you distribute an Opaque copy (directly or
+     through your agents or retailers) of that edition to the public.
 
      It is requested, but not required, that you contact the authors of
-     the Document well before redistributing any large number of
-     copies, to give them a chance to provide you with an updated
-     version of the Document.
+     the Document well before redistributing any large number of copies,
+     to give them a chance to provide you with an updated version of the
+     Document.
 
   4. MODIFICATIONS
 
      You may copy and distribute a Modified Version of the Document
      under the conditions of sections 2 and 3 above, provided that you
-     release the Modified Version under precisely this License, with
-     the Modified Version filling the role of the Document, thus
-     licensing distribution and modification of the Modified Version to
-     whoever possesses a copy of it.  In addition, you must do these
-     things in the Modified Version:
+     release the Modified Version under precisely this License, with the
+     Modified Version filling the role of the Document, thus licensing
+     distribution and modification of the Modified Version to whoever
+     possesses a copy of it.  In addition, you must do these things in
+     the Modified Version:
 
        A. Use in the Title Page (and on the covers, if any) a title
-          distinct from that of the Document, and from those of
-          previous versions (which should, if there were any, be listed
-          in the History section of the Document).  You may use the
-          same title as a previous version if the original publisher of
-          that version gives permission.
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
 
        B. List on the Title Page, as authors, one or more persons or
           entities responsible for authorship of the modifications in
@@ -22170,31 +21947,30 @@ Appendix A GNU Free Documentation License
 
        I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
-          authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section Entitled "History" in
-          the Document, create one stating the title, year, authors,
-          and publisher of the Document as given on its Title Page,
-          then add an item describing the Modified Version as stated in
-          the previous sentence.
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled "History" in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
 
        J. Preserve the network location, if any, given in the Document
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
-          previous versions it was based on.  These may be placed in
-          the "History" section.  You may omit a network location for a
-          work that was published at least four years before the
-          Document itself, or if the original publisher of the version
-          it refers to gives permission.
+          previous versions it was based on.  These may be placed in the
+          "History" section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
 
        K. For any section Entitled "Acknowledgements" or "Dedications",
-          Preserve the Title of the section, and preserve in the
-          section all the substance and tone of each of the contributor
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
 
-       L. Preserve all the Invariant Sections of the Document,
-          unaltered in their text and in their titles.  Section numbers
-          or the equivalent are not considered part of the section
-          titles.
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
 
        M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
@@ -22207,11 +21983,11 @@ Appendix A GNU Free Documentation License
 
      If the Modified Version includes new front-matter sections or
      appendices that qualify as Secondary Sections and contain no
-     material copied from the Document, you may at your option
-     designate some or all of these sections as invariant.  To do this,
-     add their titles to the list of Invariant Sections in the Modified
-     Version's license notice.  These titles must be distinct from any
-     other section titles.
+     material copied from the Document, you may at your option designate
+     some or all of these sections as invariant.  To do this, add their
+     titles to the list of Invariant Sections in the Modified Version's
+     license notice.  These titles must be distinct from any other
+     section titles.
 
      You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
@@ -22220,15 +21996,15 @@ Appendix A GNU Free Documentation License
      definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
-     and a passage of up to 25 words as a Back-Cover Text, to the end
-     of the list of Cover Texts in the Modified Version.  Only one
-     passage of Front-Cover Text and one of Back-Cover Text may be
-     added by (or through arrangements made by) any one entity.  If the
-     Document already includes a cover text for the same cover,
-     previously added by you or by arrangement made by the same entity
-     you are acting on behalf of, you may not add another; but you may
-     replace the old one, on explicit permission from the previous
-     publisher that added the old one.
+     and a passage of up to 25 words as a Back-Cover Text, to the end of
+     the list of Cover Texts in the Modified Version.  Only one passage
+     of Front-Cover Text and one of Back-Cover Text may be added by (or
+     through arrangements made by) any one entity.  If the Document
+     already includes a cover text for the same cover, previously added
+     by you or by arrangement made by the same entity you are acting on
+     behalf of, you may not add another; but you may replace the old
+     one, on explicit permission from the previous publisher that added
+     the old one.
 
      The author(s) and publisher(s) of the Document do not by this
      License give permission to use their names for publicity for or to
@@ -22238,8 +22014,8 @@ Appendix A GNU Free Documentation License
 
      You may combine the Document with other documents released under
      this License, under the terms defined in section 4 above for
-     modified versions, provided that you include in the combination
-     all of the Invariant Sections of all of the original documents,
+     modified versions, provided that you include in the combination all
+     of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
      combined work in its license notice, and that you preserve all
      their Warranty Disclaimers.
@@ -22266,20 +22042,20 @@ Appendix A GNU Free Documentation License
      documents released under this License, and replace the individual
      copies of this License in the various documents with a single copy
      that is included in the collection, provided that you follow the
-     rules of this License for verbatim copying of each of the
-     documents in all other respects.
+     rules of this License for verbatim copying of each of the documents
+     in all other respects.
 
      You may extract a single document from such a collection, and
      distribute it individually under this License, provided you insert
-     a copy of this License into the extracted document, and follow
-     this License in all other respects regarding verbatim copying of
-     that document.
+     a copy of this License into the extracted document, and follow this
+     License in all other respects regarding verbatim copying of that
+     document.
 
   7. AGGREGATION WITH INDEPENDENT WORKS
 
      A compilation of the Document or its derivatives with other
-     separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, is called an "aggregate" if the
+     separate and independent documents or works, in or on a volume of a
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
      legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
@@ -22324,8 +22100,8 @@ Appendix A GNU Free Documentation License
 
      However, if you cease all violation of this License, then your
      license from a particular copyright holder is reinstated (a)
-     provisionally, unless and until the copyright holder explicitly
-     and finally terminates your license, and (b) permanently, if the
+     provisionally, unless and until the copyright holder explicitly and
+     finally terminates your license, and (b) permanently, if the
      copyright holder fails to notify you of the violation by some
      reasonable means prior to 60 days after the cessation.
 
@@ -22337,33 +22113,33 @@ Appendix A GNU Free Documentation License
      after your receipt of the notice.
 
      Termination of your rights under this section does not terminate
-     the licenses of parties who have received copies or rights from
-     you under this License.  If your rights have been terminated and
-     not permanently reinstated, receipt of a copy of some or all of
-     the same material does not give you any rights to use it.
+     the licenses of parties who have received copies or rights from you
+     under this License.  If your rights have been terminated and not
+     permanently reinstated, receipt of a copy of some or all of the
+     same material does not give you any rights to use it.
 
- 10. FUTURE REVISIONS OF THIS LICENSE
+  10. FUTURE REVISIONS OF THIS LICENSE
 
      The Free Software Foundation may publish new, revised versions of
      the GNU Free Documentation License from time to time.  Such new
      versions will be similar in spirit to the present version, but may
      differ in detail to address new problems or concerns.  See
-     `http://www.gnu.org/copyleft/'.
+     <http://www.gnu.org/copyleft/>.
 
      Each version of the License is given a distinguishing version
      number.  If the Document specifies that a particular numbered
      version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
-     published (not as a draft) by the Free Software Foundation.  If
-     the Document does not specify a version number of this License,
-     you may choose any version ever published (not as a draft) by the
-     Free Software Foundation.  If the Document specifies that a proxy
-     can decide which future versions of this License can be used, that
+     published (not as a draft) by the Free Software Foundation.  If the
+     Document does not specify a version number of this License, you may
+     choose any version ever published (not as a draft) by the Free
+     Software Foundation.  If the Document specifies that a proxy can
+     decide which future versions of this License can be used, that
      proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
- 11. RELICENSING
+  11. RELICENSING
 
      "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
      World Wide Web server that publishes copyrightable works and also
@@ -22393,7 +22169,6 @@ Appendix A GNU Free Documentation License
      site under CC-BY-SA on the same site at any time before August 1,
      2009, provided the MMC is eligible for relicensing.
 
-
 ADDENDUM: How to use this License for your documents
 ====================================================
 
@@ -22410,7 +22185,7 @@ notices just after the title page:
        Free Documentation License''.
 
    If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts."  line with this:
 
          with the Invariant Sections being LIST THEIR TITLES, with
          the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -22421,9 +22196,9 @@ combination of the three, merge those two alternatives to suit the
 situation.
 
    If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
 
 
 File: as.info,  Node: AS Index,  Prev: GNU Free Documentation License,  Up: Top
@@ -22437,147 +22212,151 @@ AS Index
 * #:                                     Comments.            (line  33)
 * #APP:                                  Preprocessing.       (line  26)
 * #NO_APP:                               Preprocessing.       (line  26)
-* $ in symbol names <1>:                 SH64-Chars.          (line  15)
-* $ in symbol names <2>:                 SH-Chars.            (line  15)
-* $ in symbol names <3>:                 Meta-Chars.          (line  10)
-* $ in symbol names <4>:                 D30V-Chars.          (line  70)
-* $ in symbol names:                     D10V-Chars.          (line  53)
-* $a:                                    ARM Mapping Symbols. (line   9)
-* $acos math builtin, TIC54X:            TIC54X-Builtins.     (line  10)
-* $asin math builtin, TIC54X:            TIC54X-Builtins.     (line  13)
-* $atan math builtin, TIC54X:            TIC54X-Builtins.     (line  16)
-* $atan2 math builtin, TIC54X:           TIC54X-Builtins.     (line  19)
-* $ceil math builtin, TIC54X:            TIC54X-Builtins.     (line  22)
-* $cos math builtin, TIC54X:             TIC54X-Builtins.     (line  28)
-* $cosh math builtin, TIC54X:            TIC54X-Builtins.     (line  25)
-* $cvf math builtin, TIC54X:             TIC54X-Builtins.     (line  31)
-* $cvi math builtin, TIC54X:             TIC54X-Builtins.     (line  34)
-* $d <1>:                                ARM Mapping Symbols. (line  15)
-* $d:                                    AArch64 Mapping Symbols.
+* '$' in symbol names:                   D10V-Chars.          (line  46)
+* '$' in symbol names <1>:               D30V-Chars.          (line  70)
+* '$' in symbol names <2>:               Meta-Chars.          (line  10)
+* '$' in symbol names <3>:               SH-Chars.            (line  15)
+* '$' in symbol names <4>:               SH64-Chars.          (line  15)
+* '$a':                                  ARM Mapping Symbols. (line   9)
+* '$acos' math builtin, TIC54X:          TIC54X-Builtins.     (line  10)
+* '$asin' math builtin, TIC54X:          TIC54X-Builtins.     (line  13)
+* '$atan' math builtin, TIC54X:          TIC54X-Builtins.     (line  16)
+* '$atan2' math builtin, TIC54X:         TIC54X-Builtins.     (line  19)
+* '$ceil' math builtin, TIC54X:          TIC54X-Builtins.     (line  22)
+* '$cos' math builtin, TIC54X:           TIC54X-Builtins.     (line  28)
+* '$cosh' math builtin, TIC54X:          TIC54X-Builtins.     (line  25)
+* '$cvf' math builtin, TIC54X:           TIC54X-Builtins.     (line  31)
+* '$cvi' math builtin, TIC54X:           TIC54X-Builtins.     (line  34)
+* '$d':                                  AArch64 Mapping Symbols.
                                                               (line  12)
-* $exp math builtin, TIC54X:             TIC54X-Builtins.     (line  37)
-* $fabs math builtin, TIC54X:            TIC54X-Builtins.     (line  40)
-* $firstch subsym builtin, TIC54X:       TIC54X-Macros.       (line  26)
-* $floor math builtin, TIC54X:           TIC54X-Builtins.     (line  43)
-* $fmod math builtin, TIC54X:            TIC54X-Builtins.     (line  47)
-* $int math builtin, TIC54X:             TIC54X-Builtins.     (line  50)
-* $iscons subsym builtin, TIC54X:        TIC54X-Macros.       (line  43)
-* $isdefed subsym builtin, TIC54X:       TIC54X-Macros.       (line  34)
-* $ismember subsym builtin, TIC54X:      TIC54X-Macros.       (line  38)
-* $isname subsym builtin, TIC54X:        TIC54X-Macros.       (line  47)
-* $isreg subsym builtin, TIC54X:         TIC54X-Macros.       (line  50)
-* $lastch subsym builtin, TIC54X:        TIC54X-Macros.       (line  30)
-* $ldexp math builtin, TIC54X:           TIC54X-Builtins.     (line  53)
-* $log math builtin, TIC54X:             TIC54X-Builtins.     (line  59)
-* $log10 math builtin, TIC54X:           TIC54X-Builtins.     (line  56)
-* $max math builtin, TIC54X:             TIC54X-Builtins.     (line  62)
-* $min math builtin, TIC54X:             TIC54X-Builtins.     (line  65)
-* $pow math builtin, TIC54X:             TIC54X-Builtins.     (line  68)
-* $round math builtin, TIC54X:           TIC54X-Builtins.     (line  71)
-* $sgn math builtin, TIC54X:             TIC54X-Builtins.     (line  74)
-* $sin math builtin, TIC54X:             TIC54X-Builtins.     (line  77)
-* $sinh math builtin, TIC54X:            TIC54X-Builtins.     (line  80)
-* $sqrt math builtin, TIC54X:            TIC54X-Builtins.     (line  83)
-* $structacc subsym builtin, TIC54X:     TIC54X-Macros.       (line  57)
-* $structsz subsym builtin, TIC54X:      TIC54X-Macros.       (line  54)
-* $symcmp subsym builtin, TIC54X:        TIC54X-Macros.       (line  23)
-* $symlen subsym builtin, TIC54X:        TIC54X-Macros.       (line  20)
-* $t:                                    ARM Mapping Symbols. (line  12)
-* $tan math builtin, TIC54X:             TIC54X-Builtins.     (line  86)
-* $tanh math builtin, TIC54X:            TIC54X-Builtins.     (line  89)
-* $trunc math builtin, TIC54X:           TIC54X-Builtins.     (line  92)
-* $x:                                    AArch64 Mapping Symbols.
+* '$d' <1>:                              ARM Mapping Symbols. (line  15)
+* '$exp' math builtin, TIC54X:           TIC54X-Builtins.     (line  37)
+* '$fabs' math builtin, TIC54X:          TIC54X-Builtins.     (line  40)
+* '$firstch' subsym builtin, TIC54X:     TIC54X-Macros.       (line  26)
+* '$floor' math builtin, TIC54X:         TIC54X-Builtins.     (line  43)
+* '$fmod' math builtin, TIC54X:          TIC54X-Builtins.     (line  47)
+* '$int' math builtin, TIC54X:           TIC54X-Builtins.     (line  50)
+* '$iscons' subsym builtin, TIC54X:      TIC54X-Macros.       (line  43)
+* '$isdefed' subsym builtin, TIC54X:     TIC54X-Macros.       (line  34)
+* '$ismember' subsym builtin, TIC54X:    TIC54X-Macros.       (line  38)
+* '$isname' subsym builtin, TIC54X:      TIC54X-Macros.       (line  47)
+* '$isreg' subsym builtin, TIC54X:       TIC54X-Macros.       (line  50)
+* '$lastch' subsym builtin, TIC54X:      TIC54X-Macros.       (line  30)
+* '$ldexp' math builtin, TIC54X:         TIC54X-Builtins.     (line  53)
+* '$log' math builtin, TIC54X:           TIC54X-Builtins.     (line  59)
+* '$log10' math builtin, TIC54X:         TIC54X-Builtins.     (line  56)
+* '$max' math builtin, TIC54X:           TIC54X-Builtins.     (line  62)
+* '$min' math builtin, TIC54X:           TIC54X-Builtins.     (line  65)
+* '$pow' math builtin, TIC54X:           TIC54X-Builtins.     (line  68)
+* '$round' math builtin, TIC54X:         TIC54X-Builtins.     (line  71)
+* '$sgn' math builtin, TIC54X:           TIC54X-Builtins.     (line  74)
+* '$sin' math builtin, TIC54X:           TIC54X-Builtins.     (line  77)
+* '$sinh' math builtin, TIC54X:          TIC54X-Builtins.     (line  80)
+* '$sqrt' math builtin, TIC54X:          TIC54X-Builtins.     (line  83)
+* '$structacc' subsym builtin, TIC54X:   TIC54X-Macros.       (line  57)
+* '$structsz' subsym builtin, TIC54X:    TIC54X-Macros.       (line  54)
+* '$symcmp' subsym builtin, TIC54X:      TIC54X-Macros.       (line  23)
+* '$symlen' subsym builtin, TIC54X:      TIC54X-Macros.       (line  20)
+* '$t':                                  ARM Mapping Symbols. (line  12)
+* '$tan' math builtin, TIC54X:           TIC54X-Builtins.     (line  86)
+* '$tanh' math builtin, TIC54X:          TIC54X-Builtins.     (line  89)
+* '$trunc' math builtin, TIC54X:         TIC54X-Builtins.     (line  92)
+* '$x':                                  AArch64 Mapping Symbols.
                                                               (line   9)
 * %gp:                                   RX-Modifiers.        (line   6)
-* %gpreg:                                RX-Modifiers.        (line  22)
-* %pidreg:                               RX-Modifiers.        (line  25)
-* -+ option, VAX/VMS:                    VAX-Opts.            (line  71)
+* '%gpreg':                              RX-Modifiers.        (line  22)
+* '%pidreg':                             RX-Modifiers.        (line  25)
+* '-+' option, VAX/VMS:                  VAX-Opts.            (line  71)
 * --:                                    Command Line.        (line  10)
-* --32 option, i386:                     i386-Options.        (line   8)
-* --32 option, x86-64:                   i386-Options.        (line   8)
-* --64 option, i386:                     i386-Options.        (line   8)
-* --64 option, x86-64:                   i386-Options.        (line   8)
-* --absolute-literals:                   Xtensa Options.      (line  21)
+* '--32' option, i386:                   i386-Options.        (line   8)
+* '--32' option, x86-64:                 i386-Options.        (line   8)
+* '--64' option, i386:                   i386-Options.        (line   8)
+* '--64' option, x86-64:                 i386-Options.        (line   8)
+* --absolute-literals:                   Xtensa Options.      (line  20)
 * --allow-reg-prefix:                    SH Options.          (line   9)
 * --alternate:                           alternate.           (line   6)
-* --base-size-default-16:                M68K-Opts.           (line  65)
-* --base-size-default-32:                M68K-Opts.           (line  65)
+* '--base-size-default-16':              M68K-Opts.           (line  66)
+* '--base-size-default-32':              M68K-Opts.           (line  66)
 * --big:                                 SH Options.          (line   9)
-* --bitwise-or option, M680x0:           M68K-Opts.           (line  58)
-* --disp-size-default-16:                M68K-Opts.           (line  74)
-* --disp-size-default-32:                M68K-Opts.           (line  74)
-* --divide option, i386:                 i386-Options.        (line  24)
+* '--bitwise-or' option, M680x0:         M68K-Opts.           (line  59)
+* '--disp-size-default-16':              M68K-Opts.           (line  75)
+* '--disp-size-default-32':              M68K-Opts.           (line  75)
+* '--divide' option, i386:               i386-Options.        (line  24)
 * --dsp:                                 SH Options.          (line   9)
-* --emulation=crisaout command line option, CRIS: CRIS-Opts.  (line   9)
-* --emulation=criself command line option, CRIS: CRIS-Opts.   (line   9)
+* '--emulation=crisaout' command line option, CRIS: CRIS-Opts.
+                                                              (line   9)
+* '--emulation=criself' command line option, CRIS: CRIS-Opts. (line   9)
 * --enforce-aligned-data:                Sparc-Aligned-Data.  (line  11)
 * --fatal-warnings:                      W.                   (line  16)
 * --fdpic:                               SH Options.          (line  31)
-* --fix-v4bx command line option, ARM:   ARM Options.         (line 173)
-* --fixed-special-register-names command line option, MMIX: MMIX-Opts.
+* '--fix-v4bx' command line option, ARM: ARM Options.         (line 174)
+* '--fixed-special-register-names' command line option, MMIX: MMIX-Opts.
                                                               (line   8)
-* --force-long-branches:                 M68HC11-Opts.        (line  82)
-* --generate-example:                    M68HC11-Opts.        (line  99)
-* --globalize-symbols command line option, MMIX: MMIX-Opts.   (line  12)
-* --gnu-syntax command line option, MMIX: MMIX-Opts.          (line  16)
-* --hash-size=NUMBER:                    Overview.            (line 387)
-* --linker-allocated-gregs command line option, MMIX: MMIX-Opts.
+* '--force-long-branches':               M68HC11-Opts.        (line  81)
+* '--generate-example':                  M68HC11-Opts.        (line  98)
+* '--globalize-symbols' command line option, MMIX: MMIX-Opts. (line  12)
+* '--gnu-syntax' command line option, MMIX: MMIX-Opts.        (line  16)
+* --hash-size=NUMBER:                    Overview.            (line 400)
+* '--linker-allocated-gregs' command line option, MMIX: MMIX-Opts.
                                                               (line  67)
 * --listing-cont-lines:                  listing.             (line  34)
 * --listing-lhs-width:                   listing.             (line  16)
 * --listing-lhs-width2:                  listing.             (line  21)
 * --listing-rhs-width:                   listing.             (line  28)
 * --little:                              SH Options.          (line   9)
-* --longcalls:                           Xtensa Options.      (line  35)
-* --march=ARCHITECTURE command line option, CRIS: CRIS-Opts.  (line  34)
+* --longcalls:                           Xtensa Options.      (line  34)
+* '--march=ARCHITECTURE' command line option, CRIS: CRIS-Opts.
+                                                              (line  34)
 * --MD:                                  MD.                  (line   6)
-* --mul-bug-abort command line option, CRIS: CRIS-Opts.       (line  62)
-* --no-absolute-literals:                Xtensa Options.      (line  21)
-* --no-expand command line option, MMIX: MMIX-Opts.           (line  31)
-* --no-longcalls:                        Xtensa Options.      (line  35)
-* --no-merge-gregs command line option, MMIX: MMIX-Opts.      (line  36)
-* --no-mul-bug-abort command line option, CRIS: CRIS-Opts.    (line  62)
-* --no-predefined-syms command line option, MMIX: MMIX-Opts.  (line  22)
-* --no-pushj-stubs command line option, MMIX: MMIX-Opts.      (line  54)
-* --no-stubs command line option, MMIX:  MMIX-Opts.           (line  54)
-* --no-target-align:                     Xtensa Options.      (line  28)
+* '--mul-bug-abort' command line option, CRIS: CRIS-Opts.     (line  63)
+* --no-absolute-literals:                Xtensa Options.      (line  20)
+* '--no-expand' command line option, MMIX: MMIX-Opts.         (line  31)
+* --no-longcalls:                        Xtensa Options.      (line  34)
+* '--no-merge-gregs' command line option, MMIX: MMIX-Opts.    (line  36)
+* '--no-mul-bug-abort' command line option, CRIS: CRIS-Opts.  (line  63)
+* '--no-predefined-syms' command line option, MMIX: MMIX-Opts.
+                                                              (line  22)
+* '--no-pushj-stubs' command line option, MMIX: MMIX-Opts.    (line  54)
+* '--no-stubs' command line option, MMIX: MMIX-Opts.          (line  54)
+* --no-target-align:                     Xtensa Options.      (line  27)
 * --no-text-section-literals:            Xtensa Options.      (line   7)
-* --no-transform:                        Xtensa Options.      (line  44)
-* --no-underscore command line option, CRIS: CRIS-Opts.       (line  15)
+* --no-transform:                        Xtensa Options.      (line  43)
+* '--no-underscore' command line option, CRIS: CRIS-Opts.     (line  15)
 * --no-warn:                             W.                   (line  11)
-* --pcrel:                               M68K-Opts.           (line  86)
-* --pic command line option, CRIS:       CRIS-Opts.           (line  27)
-* --print-insn-syntax <1>:               XGATE-Opts.          (line  25)
-* --print-insn-syntax:                   M68HC11-Opts.        (line  88)
-* --print-opcodes <1>:                   XGATE-Opts.          (line  29)
-* --print-opcodes:                       M68HC11-Opts.        (line  92)
-* --register-prefix-optional option, M680x0: M68K-Opts.       (line  45)
+* '--pcrel':                             M68K-Opts.           (line  87)
+* '--pic' command line option, CRIS:     CRIS-Opts.           (line  27)
+* '--print-insn-syntax':                 M68HC11-Opts.        (line  87)
+* '--print-insn-syntax' <1>:             XGATE-Opts.          (line  25)
+* '--print-opcodes':                     M68HC11-Opts.        (line  91)
+* '--print-opcodes' <1>:                 XGATE-Opts.          (line  29)
+* '--register-prefix-optional' option, M680x0: M68K-Opts.     (line  46)
 * --relax:                               SH Options.          (line   9)
-* --relax command line option, MMIX:     MMIX-Opts.           (line  19)
-* --rename-section:                      Xtensa Options.      (line  52)
+* '--relax' command line option, MMIX:   MMIX-Opts.           (line  19)
+* --rename-section:                      Xtensa Options.      (line  51)
 * --renesas:                             SH Options.          (line   9)
-* --short-branches:                      M68HC11-Opts.        (line  67)
+* '--short-branches':                    M68HC11-Opts.        (line  67)
 * --small:                               SH Options.          (line   9)
 * --statistics:                          statistics.          (line   6)
-* --strict-direct-mode:                  M68HC11-Opts.        (line  57)
-* --target-align:                        Xtensa Options.      (line  28)
+* '--strict-direct-mode':                M68HC11-Opts.        (line  57)
+* --target-align:                        Xtensa Options.      (line  27)
 * --text-section-literals:               Xtensa Options.      (line   7)
 * --traditional-format:                  traditional-format.  (line   6)
-* --transform:                           Xtensa Options.      (line  44)
-* --underscore command line option, CRIS: CRIS-Opts.          (line  15)
+* --transform:                           Xtensa Options.      (line  43)
+* '--underscore' command line option, CRIS: CRIS-Opts.        (line  15)
 * --warn:                                W.                   (line  19)
-* --x32 option, i386:                    i386-Options.        (line   8)
-* --x32 option, x86-64:                  i386-Options.        (line   8)
-* --xgate-ramoffset:                     M68HC11-Opts.        (line  36)
-* -1 option, VAX/VMS:                    VAX-Opts.            (line  77)
-* -32addr command line option, Alpha:    Alpha Options.       (line  57)
+* '--x32' option, i386:                  i386-Options.        (line   8)
+* '--x32' option, x86-64:                i386-Options.        (line   8)
+* '--xgate-ramoffset':                   M68HC11-Opts.        (line  36)
+* '-1' option, VAX/VMS:                  VAX-Opts.            (line  77)
+* '-32addr' command line option, Alpha:  Alpha Options.       (line  57)
 * -a:                                    a.                   (line   6)
-* -A options, i960:                      Options-i960.        (line   6)
+* '-A' options, i960:                    Options-i960.        (line   6)
 * -ac:                                   a.                   (line   6)
 * -ad:                                   a.                   (line   6)
 * -ag:                                   a.                   (line   6)
 * -ah:                                   a.                   (line   6)
 * -al:                                   a.                   (line   6)
+* -Aleon:                                Sparc-Opts.          (line  25)
 * -an:                                   a.                   (line   6)
 * -as:                                   a.                   (line   6)
 * -Asparc:                               Sparc-Opts.          (line  25)
@@ -22598,42 +22377,42 @@ AS Index
 * -Av9c:                                 Sparc-Opts.          (line  25)
 * -Av9d:                                 Sparc-Opts.          (line  25)
 * -Av9v:                                 Sparc-Opts.          (line  25)
-* -b option, i960:                       Options-i960.        (line  22)
-* -big option, M32R:                     M32R-Opts.           (line  35)
+* '-b' option, i960:                     Options-i960.        (line  22)
+* '-big' option, M32R:                   M32R-Opts.           (line  35)
 * -D:                                    D.                   (line   6)
-* -D, ignored on VAX:                    VAX-Opts.            (line  11)
-* -d, VAX option:                        VAX-Opts.            (line  16)
-* -eabi= command line option, ARM:       ARM Options.         (line 156)
-* -EB command line option, AArch64:      AArch64 Options.     (line   6)
-* -EB command line option, ARC:          ARC Options.         (line  31)
-* -EB command line option, ARM:          ARM Options.         (line 161)
-* -EB option (MIPS):                     MIPS Opts.           (line  13)
-* -EB option, M32R:                      M32R-Opts.           (line  39)
-* -EB option, TILE-Gx:                   TILE-Gx Options.     (line  11)
-* -EL command line option, AArch64:      AArch64 Options.     (line  10)
-* -EL command line option, ARC:          ARC Options.         (line  35)
-* -EL command line option, ARM:          ARM Options.         (line 165)
-* -EL option (MIPS):                     MIPS Opts.           (line  13)
-* -EL option, M32R:                      M32R-Opts.           (line  32)
-* -EL option, TILE-Gx:                   TILE-Gx Options.     (line  11)
+* '-D', ignored on VAX:                  VAX-Opts.            (line  11)
+* '-d', VAX option:                      VAX-Opts.            (line  16)
+* '-eabi=' command line option, ARM:     ARM Options.         (line 157)
+* '-EB' command line option, AArch64:    AArch64 Options.     (line   6)
+* '-EB' command line option, ARC:        ARC Options.         (line  30)
+* '-EB' command line option, ARM:        ARM Options.         (line 162)
+* '-EB' option (MIPS):                   MIPS Options.        (line  13)
+* '-EB' option, M32R:                    M32R-Opts.           (line  39)
+* '-EB' option, TILE-Gx:                 TILE-Gx Options.     (line  11)
+* '-EL' command line option, AArch64:    AArch64 Options.     (line  10)
+* '-EL' command line option, ARC:        ARC Options.         (line  34)
+* '-EL' command line option, ARM:        ARM Options.         (line 166)
+* '-EL' option (MIPS):                   MIPS Options.        (line  13)
+* '-EL' option, M32R:                    M32R-Opts.           (line  32)
+* '-EL' option, TILE-Gx:                 TILE-Gx Options.     (line  11)
 * -f:                                    f.                   (line   6)
-* -F command line option, Alpha:         Alpha Options.       (line  57)
-* -G command line option, Alpha:         Alpha Options.       (line  53)
-* -g command line option, Alpha:         Alpha Options.       (line  47)
-* -G option (MIPS):                      MIPS Opts.           (line   8)
-* -H option, VAX/VMS:                    VAX-Opts.            (line  81)
-* -h option, VAX/VMS:                    VAX-Opts.            (line  45)
+* '-F' command line option, Alpha:       Alpha Options.       (line  57)
+* '-g' command line option, Alpha:       Alpha Options.       (line  47)
+* '-G' command line option, Alpha:       Alpha Options.       (line  53)
+* '-G' option (MIPS):                    MIPS Options.        (line   8)
+* '-h' option, VAX/VMS:                  VAX-Opts.            (line  45)
+* '-H' option, VAX/VMS:                  VAX-Opts.            (line  81)
 * -I PATH:                               I.                   (line   6)
-* -ignore-parallel-conflicts option, M32RX: M32R-Opts.        (line  87)
-* -Ip option, M32RX:                     M32R-Opts.           (line  97)
-* -J, ignored on VAX:                    VAX-Opts.            (line  27)
+* '-ignore-parallel-conflicts' option, M32RX: M32R-Opts.      (line  87)
+* '-Ip' option, M32RX:                   M32R-Opts.           (line  97)
+* '-J', ignored on VAX:                  VAX-Opts.            (line  27)
 * -K:                                    K.                   (line   6)
-* -k command line option, ARM:           ARM Options.         (line 169)
-* -KPIC option, M32R:                    M32R-Opts.           (line  42)
-* -KPIC option, MIPS:                    MIPS Opts.           (line  21)
+* '-k' command line option, ARM:         ARM Options.         (line 170)
+* '-KPIC' option, M32R:                  M32R-Opts.           (line  42)
+* '-KPIC' option, MIPS:                  MIPS Options.        (line  21)
 * -L:                                    L.                   (line   6)
-* -l option, M680x0:                     M68K-Opts.           (line  33)
-* -little option, M32R:                  M32R-Opts.           (line  27)
+* '-l' option, M680x0:                   M68K-Opts.           (line  34)
+* '-little' option, M32R:                M32R-Opts.           (line  27)
 * -M:                                    M.                   (line   6)
 * -m11/03:                               PDP-11-Options.      (line 140)
 * -m11/04:                               PDP-11-Options.      (line 143)
@@ -22660,88 +22439,90 @@ AS Index
 * -m11/84:                               PDP-11-Options.      (line 173)
 * -m11/93:                               PDP-11-Options.      (line 173)
 * -m11/94:                               PDP-11-Options.      (line 173)
-* -m16c option, M16C:                    M32C-Opts.           (line  12)
-* -m31 option, s390:                     s390 Options.        (line   8)
-* -m32 option, TILE-Gx:                  TILE-Gx Options.     (line   8)
-* -m32bit-doubles:                       RX-Opts.             (line   9)
-* -m32c option, M32C:                    M32C-Opts.           (line   9)
-* -m32r option, M32R:                    M32R-Opts.           (line  21)
-* -m32rx option, M32R2:                  M32R-Opts.           (line  17)
-* -m32rx option, M32RX:                  M32R-Opts.           (line   9)
-* -m4byte-align command line option, V850: V850 Options.      (line  90)
-* -m64 option, s390:                     s390 Options.        (line   8)
-* -m64 option, TILE-Gx:                  TILE-Gx Options.     (line   8)
-* -m64bit-doubles:                       RX-Opts.             (line  15)
-* -m68000 and related options:           M68K-Opts.           (line  98)
-* -m68hc11:                              M68HC11-Opts.        (line   9)
-* -m68hc12:                              M68HC11-Opts.        (line  14)
-* -m68hcs12:                             M68HC11-Opts.        (line  21)
-* -m8byte-align command line option, V850: V850 Options.      (line  86)
-* -m[no-]68851 command line option, M680x0: M68K-Opts.        (line  21)
-* -m[no-]68881 command line option, M680x0: M68K-Opts.        (line  21)
-* -m[no-]div command line option, M680x0: M68K-Opts.          (line  21)
-* -m[no-]emac command line option, M680x0: M68K-Opts.         (line  21)
-* -m[no-]float command line option, M680x0: M68K-Opts.        (line  21)
-* -m[no-]mac command line option, M680x0: M68K-Opts.          (line  21)
-* -m[no-]usp command line option, M680x0: M68K-Opts.          (line  21)
+* '-m16c' option, M16C:                  M32C-Opts.           (line  12)
+* '-m31' option, s390:                   s390 Options.        (line   8)
+* '-m32' option, TILE-Gx:                TILE-Gx Options.     (line   8)
+* '-m32bit-doubles':                     RX-Opts.             (line   9)
+* '-m32c' option, M32C:                  M32C-Opts.           (line   9)
+* '-m32r' option, M32R:                  M32R-Opts.           (line  21)
+* '-m32rx' option, M32R2:                M32R-Opts.           (line  17)
+* '-m32rx' option, M32RX:                M32R-Opts.           (line   9)
+* '-m4byte-align' command line option, V850: V850 Options.    (line  90)
+* '-m64' option, s390:                   s390 Options.        (line   8)
+* '-m64' option, TILE-Gx:                TILE-Gx Options.     (line   8)
+* '-m64bit-doubles':                     RX-Opts.             (line  15)
+* '-m68000' and related options:         M68K-Opts.           (line  99)
+* '-m68hc11':                            M68HC11-Opts.        (line   9)
+* '-m68hc12':                            M68HC11-Opts.        (line  14)
+* '-m68hcs12':                           M68HC11-Opts.        (line  21)
+* '-m8byte-align' command line option, V850: V850 Options.    (line  86)
+* '-mabi=' command line option, AArch64: AArch64 Options.     (line  14)
+* '-madd-bnd-prefix' option, i386:       i386-Options.        (line 124)
+* '-madd-bnd-prefix' option, x86-64:     i386-Options.        (line 124)
 * -mall:                                 PDP-11-Options.      (line  26)
-* -mall-enabled command line option, LM32: LM32 Options.      (line  30)
+* '-mall-enabled' command line option, LM32: LM32 Options.    (line  30)
 * -mall-extensions:                      PDP-11-Options.      (line  26)
-* -mall-opcodes command line option, AVR: AVR Options.        (line  97)
-* -mapcs-26 command line option, ARM:    ARM Options.         (line 128)
-* -mapcs-32 command line option, ARM:    ARM Options.         (line 128)
-* -mapcs-float command line option, ARM: ARM Options.         (line 142)
-* -mapcs-reentrant command line option, ARM: ARM Options.     (line 147)
-* -marc[5|6|7|8] command line option, ARC: ARC Options.       (line   6)
-* -march= command line option, ARM:      ARM Options.         (line  65)
-* -march= command line option, M680x0:   M68K-Opts.           (line   8)
-* -march= command line option, TIC6X:    TIC6X Options.       (line   6)
-* -march= option, i386:                  i386-Options.        (line  31)
-* -march= option, s390:                  s390 Options.        (line  25)
-* -march= option, x86-64:                i386-Options.        (line  31)
-* -matpcs command line option, ARM:      ARM Options.         (line 134)
-* -mavxscalar= option, i386:             i386-Options.        (line  81)
-* -mavxscalar= option, x86-64:           i386-Options.        (line  81)
-* -mbarrel-shift-enabled command line option, LM32: LM32 Options.
+* '-mall-opcodes' command line option, AVR: AVR Options.      (line  97)
+* '-mapcs-26' command line option, ARM:  ARM Options.         (line 129)
+* '-mapcs-32' command line option, ARM:  ARM Options.         (line 129)
+* '-mapcs-float' command line option, ARM: ARM Options.       (line 143)
+* '-mapcs-reentrant' command line option, ARM: ARM Options.   (line 148)
+* '-march=' command line option, ARM:    ARM Options.         (line  65)
+* '-march=' command line option, M680x0: M68K-Opts.           (line   8)
+* '-march=' command line option, TIC6X:  TIC6X Options.       (line   6)
+* '-march=' option, i386:                i386-Options.        (line  31)
+* '-march=' option, s390:                s390 Options.        (line  25)
+* '-march=' option, x86-64:              i386-Options.        (line  31)
+* '-marc[5|6|7|8]' command line option, ARC: ARC Options.     (line   6)
+* '-matpcs' command line option, ARM:    ARM Options.         (line 135)
+* '-mavxscalar=' option, i386:           i386-Options.        (line  82)
+* '-mavxscalar=' option, x86-64:         i386-Options.        (line  82)
+* '-mbarrel-shift-enabled' command line option, LM32: LM32 Options.
                                                               (line  12)
-* -mbig-endian:                          RX-Opts.             (line  20)
-* -mbreak-enabled command line option, LM32: LM32 Options.    (line  27)
+* '-mbig-endian':                        RX-Opts.             (line  20)
+* '-mbreak-enabled' command line option, LM32: LM32 Options.  (line  27)
 * -mcis:                                 PDP-11-Options.      (line  32)
-* -mconstant-gp command line option, IA-64: IA-64 Options.    (line   6)
-* -mCPU command line option, Alpha:      Alpha Options.       (line   6)
-* -mcpu option, cpu:                     TIC54X-Opts.         (line  15)
-* -mcpu= command line option, ARM:       ARM Options.         (line   6)
-* -mcpu= command line option, Blackfin:  Blackfin Options.    (line   6)
-* -mcpu= command line option, M680x0:    M68K-Opts.           (line  14)
+* '-mconstant-gp' command line option, IA-64: IA-64 Options.  (line   6)
+* '-mCPU' command line option, Alpha:    Alpha Options.       (line   6)
+* '-mcpu' option, cpu:                   TIC54X-Opts.         (line  15)
+* '-mcpu=':                              RX-Opts.             (line  75)
+* '-mcpu=' command line option, ARM:     ARM Options.         (line   6)
+* '-mcpu=' command line option, Blackfin: Blackfin Options.   (line   6)
+* '-mcpu=' command line option, M680x0:  M68K-Opts.           (line  14)
 * -mcsm:                                 PDP-11-Options.      (line  43)
-* -mdcache-enabled command line option, LM32: LM32 Options.   (line  24)
-* -mdebug command line option, Alpha:    Alpha Options.       (line  25)
-* -mdivide-enabled command line option, LM32: LM32 Options.   (line   9)
-* -mdsbt command line option, TIC6X:     TIC6X Options.       (line  13)
-* -me option, stderr redirect:           TIC54X-Opts.         (line  20)
+* '-mdcache-enabled' command line option, LM32: LM32 Options. (line  24)
+* '-mdebug' command line option, Alpha:  Alpha Options.       (line  25)
+* '-mdivide-enabled' command line option, LM32: LM32 Options. (line   9)
+* '-mdsbt' command line option, TIC6X:   TIC6X Options.       (line  13)
+* '-me' option, stderr redirect:         TIC54X-Opts.         (line  20)
 * -meis:                                 PDP-11-Options.      (line  46)
-* -mepiphany command line option, Epiphany: Epiphany Options. (line   9)
-* -mepiphany16 command line option, Epiphany: Epiphany Options.
+* '-mepiphany' command line option, Epiphany: Epiphany Options.
+                                                              (line   9)
+* '-mepiphany16' command line option, Epiphany: Epiphany Options.
                                                               (line  13)
-* -merrors-to-file option, stderr redirect: TIC54X-Opts.      (line  20)
-* -mesa option, s390:                    s390 Options.        (line  17)
-* -mf option, far-mode:                  TIC54X-Opts.         (line   8)
+* '-merrors-to-file' option, stderr redirect: TIC54X-Opts.    (line  20)
+* '-mesa' option, s390:                  s390 Options.        (line  17)
+* '-mevexlig=' option, i386:             i386-Options.        (line  90)
+* '-mevexlig=' option, x86-64:           i386-Options.        (line  90)
+* '-mevexwig=' option, i386:             i386-Options.        (line 100)
+* '-mevexwig=' option, x86-64:           i386-Options.        (line 100)
+* '-mf' option, far-mode:                TIC54X-Opts.         (line   8)
 * -mf11:                                 PDP-11-Options.      (line 122)
-* -mfar-mode option, far-mode:           TIC54X-Opts.         (line   8)
-* -mfdpic command line option, Blackfin: Blackfin Options.    (line  19)
+* '-mfar-mode' option, far-mode:         TIC54X-Opts.         (line   8)
+* '-mfdpic' command line option, Blackfin: Blackfin Options.  (line  19)
 * -mfis:                                 PDP-11-Options.      (line  51)
-* -mfloat-abi= command line option, ARM: ARM Options.         (line 151)
+* '-mfloat-abi=' command line option, ARM: ARM Options.       (line 152)
 * -mfp-11:                               PDP-11-Options.      (line  56)
 * -mfpp:                                 PDP-11-Options.      (line  56)
 * -mfpu:                                 PDP-11-Options.      (line  56)
-* -mfpu= command line option, ARM:       ARM Options.         (line  81)
-* -mgcc-abi:                             RX-Opts.             (line  63)
-* -mgcc-abi command line option, V850:   V850 Options.        (line  79)
-* -micache-enabled command line option, LM32: LM32 Options.   (line  21)
-* -mimplicit-it command line option, ARM: ARM Options.        (line 112)
-* -mint-register:                        RX-Opts.             (line  57)
-* -mip2022 option, IP2K:                 IP2K-Opts.           (line  14)
-* -mip2022ext option, IP2022:            IP2K-Opts.           (line   9)
+* '-mfpu=' command line option, ARM:     ARM Options.         (line  81)
+* '-mgcc-abi':                           RX-Opts.             (line  63)
+* '-mgcc-abi' command line option, V850: V850 Options.        (line  79)
+* '-micache-enabled' command line option, LM32: LM32 Options. (line  21)
+* '-mimplicit-it' command line option, ARM: ARM Options.      (line 113)
+* '-mint-register':                      RX-Opts.             (line  57)
+* '-mip2022' option, IP2K:               IP2K-Opts.           (line  14)
+* '-mip2022ext' option, IP2022:          IP2K-Opts.           (line   9)
 * -mj11:                                 PDP-11-Options.      (line 126)
 * -mka11:                                PDP-11-Options.      (line  92)
 * -mkb11:                                PDP-11-Options.      (line  95)
@@ -22755,30 +22536,34 @@ AS Index
 * -mkd11q:                               PDP-11-Options.      (line 110)
 * -mkd11z:                               PDP-11-Options.      (line 118)
 * -mkev11:                               PDP-11-Options.      (line  51)
+* -mkev11 <1>:                           PDP-11-Options.      (line  51)
 * -mlimited-eis:                         PDP-11-Options.      (line  64)
-* -mlittle-endian:                       RX-Opts.             (line  26)
-* -mlong <1>:                            XGATE-Opts.          (line  13)
-* -mlong:                                M68HC11-Opts.        (line  45)
-* -mlong-double <1>:                     XGATE-Opts.          (line  21)
-* -mlong-double:                         M68HC11-Opts.        (line  53)
-* -mm9s12x:                              M68HC11-Opts.        (line  27)
-* -mm9s12xg:                             M68HC11-Opts.        (line  32)
-* -mmcu= command line option, AVR:       AVR Options.         (line   6)
+* '-mlittle-endian':                     RX-Opts.             (line  26)
+* '-mlong':                              M68HC11-Opts.        (line  45)
+* '-mlong' <1>:                          XGATE-Opts.          (line  13)
+* '-mlong-double':                       M68HC11-Opts.        (line  53)
+* '-mlong-double' <1>:                   XGATE-Opts.          (line  21)
+* '-mm9s12x':                            M68HC11-Opts.        (line  27)
+* '-mm9s12xg':                           M68HC11-Opts.        (line  32)
+* '-mmcu=' command line option, AVR:     AVR Options.         (line   6)
 * -mmfpt:                                PDP-11-Options.      (line  70)
 * -mmicrocode:                           PDP-11-Options.      (line  83)
-* -mmnemonic= option, i386:              i386-Options.        (line  89)
-* -mmnemonic= option, x86-64:            i386-Options.        (line  89)
-* -mmultiply-enabled command line option, LM32: LM32 Options. (line   6)
+* '-mmnemonic=' option, i386:            i386-Options.        (line 107)
+* '-mmnemonic=' option, x86-64:          i386-Options.        (line 107)
+* '-mmultiply-enabled' command line option, LM32: LM32 Options.
+                                                              (line   6)
 * -mmutiproc:                            PDP-11-Options.      (line  73)
 * -mmxps:                                PDP-11-Options.      (line  77)
-* -mnaked-reg option, i386:              i386-Options.        (line 101)
-* -mnaked-reg option, x86-64:            i386-Options.        (line 101)
+* '-mnaked-reg' option, i386:            i386-Options.        (line 119)
+* '-mnaked-reg' option, x86-64:          i386-Options.        (line 119)
+* '-mnan=' command line option, MIPS:    MIPS Options.        (line 296)
 * -mno-cis:                              PDP-11-Options.      (line  32)
 * -mno-csm:                              PDP-11-Options.      (line  43)
-* -mno-dsbt command line option, TIC6X:  TIC6X Options.       (line  13)
+* '-mno-dsbt' command line option, TIC6X: TIC6X Options.      (line  13)
 * -mno-eis:                              PDP-11-Options.      (line  46)
 * -mno-extensions:                       PDP-11-Options.      (line  29)
-* -mno-fdpic command line option, Blackfin: Blackfin Options. (line  22)
+* '-mno-fdpic' command line option, Blackfin: Blackfin Options.
+                                                              (line  22)
 * -mno-fis:                              PDP-11-Options.      (line  51)
 * -mno-fp-11:                            PDP-11-Options.      (line  56)
 * -mno-fpp:                              PDP-11-Options.      (line  56)
@@ -22790,262 +22575,285 @@ AS Index
 * -mno-mutiproc:                         PDP-11-Options.      (line  73)
 * -mno-mxps:                             PDP-11-Options.      (line  77)
 * -mno-pic:                              PDP-11-Options.      (line  11)
-* -mno-pic command line option, TIC6X:   TIC6X Options.       (line  36)
-* -mno-regnames option, s390:            s390 Options.        (line  35)
-* -mno-skip-bug command line option, AVR: AVR Options.        (line 100)
+* '-mno-pic' command line option, TIC6X: TIC6X Options.       (line  36)
+* '-mno-regnames' option, s390:          s390 Options.        (line  35)
+* '-mno-skip-bug' command line option, AVR: AVR Options.      (line 100)
 * -mno-spl:                              PDP-11-Options.      (line  80)
-* -mno-sym32:                            MIPS Opts.           (line 222)
-* -mno-wrap command line option, AVR:    AVR Options.         (line 103)
-* -mnopic command line option, Blackfin: Blackfin Options.    (line  22)
+* -mno-sym32:                            MIPS Options.        (line 238)
+* '-mno-wrap' command line option, AVR:  AVR Options.         (line 103)
+* '-mnopic' command line option, Blackfin: Blackfin Options.  (line  22)
 * -mpic:                                 PDP-11-Options.      (line  11)
-* -mpic command line option, TIC6X:      TIC6X Options.       (line  36)
-* -mpid:                                 RX-Opts.             (line  50)
-* -mpid= command line option, TIC6X:     TIC6X Options.       (line  23)
-* -mregnames option, s390:               s390 Options.        (line  32)
-* -mrelax command line option, V850:     V850 Options.        (line  72)
-* -mrh850-abi command line option, V850: V850 Options.        (line  82)
-* -mrx-abi:                              RX-Opts.             (line  69)
-* -mshort <1>:                           XGATE-Opts.          (line   8)
-* -mshort:                               M68HC11-Opts.        (line  40)
-* -mshort-double <1>:                    XGATE-Opts.          (line  17)
-* -mshort-double:                        M68HC11-Opts.        (line  49)
-* -msign-extend-enabled command line option, LM32: LM32 Options.
+* '-mpic' command line option, TIC6X:    TIC6X Options.       (line  36)
+* '-mpid':                               RX-Opts.             (line  50)
+* '-mpid=' command line option, TIC6X:   TIC6X Options.       (line  23)
+* '-mregnames' option, s390:             s390 Options.        (line  32)
+* '-mrelax' command line option, V850:   V850 Options.        (line  72)
+* '-mrh850-abi' command line option, V850: V850 Options.      (line  82)
+* '-mrx-abi':                            RX-Opts.             (line  69)
+* '-mshort':                             M68HC11-Opts.        (line  40)
+* '-mshort' <1>:                         XGATE-Opts.          (line   8)
+* '-mshort-double':                      M68HC11-Opts.        (line  49)
+* '-mshort-double' <1>:                  XGATE-Opts.          (line  17)
+* '-msign-extend-enabled' command line option, LM32: LM32 Options.
                                                               (line  15)
-* -msmall-data-limit:                    RX-Opts.             (line  42)
+* '-msmall-data-limit':                  RX-Opts.             (line  42)
 * -mspl:                                 PDP-11-Options.      (line  80)
-* -msse-check= option, i386:             i386-Options.        (line  71)
-* -msse-check= option, x86-64:           i386-Options.        (line  71)
-* -msse2avx option, i386:                i386-Options.        (line  67)
-* -msse2avx option, x86-64:              i386-Options.        (line  67)
-* -msym32:                               MIPS Opts.           (line 222)
-* -msyntax= option, i386:                i386-Options.        (line  95)
-* -msyntax= option, x86-64:              i386-Options.        (line  95)
+* '-msse-check=' option, i386:           i386-Options.        (line  72)
+* '-msse-check=' option, x86-64:         i386-Options.        (line  72)
+* '-msse2avx' option, i386:              i386-Options.        (line  68)
+* '-msse2avx' option, x86-64:            i386-Options.        (line  68)
+* -msym32:                               MIPS Options.        (line 238)
+* '-msyntax=' option, i386:              i386-Options.        (line 113)
+* '-msyntax=' option, x86-64:            i386-Options.        (line 113)
 * -mt11:                                 PDP-11-Options.      (line 130)
-* -mthumb command line option, ARM:      ARM Options.         (line 103)
-* -mthumb-interwork command line option, ARM: ARM Options.    (line 108)
-* -mtune= option, i386:                  i386-Options.        (line  59)
-* -mtune= option, x86-64:                i386-Options.        (line  59)
-* -muse-conventional-section-names:      RX-Opts.             (line  33)
-* -muse-renesas-section-names:           RX-Opts.             (line  37)
-* -muser-enabled command line option, LM32: LM32 Options.     (line  18)
-* -mv850 command line option, V850:      V850 Options.        (line  23)
-* -mv850any command line option, V850:   V850 Options.        (line  41)
-* -mv850e command line option, V850:     V850 Options.        (line  29)
-* -mv850e1 command line option, V850:    V850 Options.        (line  35)
-* -mv850e2 command line option, V850:    V850 Options.        (line  51)
-* -mv850e2v3 command line option, V850:  V850 Options.        (line  57)
-* -mv850e2v4 command line option, V850:  V850 Options.        (line  63)
-* -mv850e3v5 command line option, V850:  V850 Options.        (line  66)
-* -mvxworks-pic option, MIPS:            MIPS Opts.           (line  26)
-* -mwarn-areg-zero option, s390:         s390 Options.        (line  38)
-* -mwarn-deprecated command line option, ARM: ARM Options.    (line 177)
-* -mzarch option, s390:                  s390 Options.        (line  17)
-* -N command line option, CRIS:          CRIS-Opts.           (line  58)
-* -nIp option, M32RX:                    M32R-Opts.           (line 101)
-* -no-bitinst, M32R2:                    M32R-Opts.           (line  54)
-* -no-ignore-parallel-conflicts option, M32RX: M32R-Opts.     (line  93)
-* -no-mdebug command line option, Alpha: Alpha Options.       (line  25)
-* -no-parallel option, M32RX:            M32R-Opts.           (line  51)
-* -no-relax option, i960:                Options-i960.        (line  66)
-* -no-warn-explicit-parallel-conflicts option, M32RX: M32R-Opts.
+* '-mthumb' command line option, ARM:    ARM Options.         (line 104)
+* '-mthumb-interwork' command line option, ARM: ARM Options.  (line 109)
+* '-mtune=' option, i386:                i386-Options.        (line  60)
+* '-mtune=' option, x86-64:              i386-Options.        (line  60)
+* '-muse-conventional-section-names':    RX-Opts.             (line  33)
+* '-muse-renesas-section-names':         RX-Opts.             (line  37)
+* '-muser-enabled' command line option, LM32: LM32 Options.   (line  18)
+* '-mv850' command line option, V850:    V850 Options.        (line  23)
+* '-mv850any' command line option, V850: V850 Options.        (line  41)
+* '-mv850e' command line option, V850:   V850 Options.        (line  29)
+* '-mv850e1' command line option, V850:  V850 Options.        (line  35)
+* '-mv850e2' command line option, V850:  V850 Options.        (line  51)
+* '-mv850e2v3' command line option, V850: V850 Options.       (line  57)
+* '-mv850e2v4' command line option, V850: V850 Options.       (line  63)
+* '-mv850e3v5' command line option, V850: V850 Options.       (line  66)
+* '-mvxworks-pic' option, MIPS:          MIPS Options.        (line  26)
+* '-mwarn-areg-zero' option, s390:       s390 Options.        (line  38)
+* '-mwarn-deprecated' command line option, ARM: ARM Options.  (line 178)
+* '-mzarch' option, s390:                s390 Options.        (line  17)
+* '-m[no-]68851' command line option, M680x0: M68K-Opts.      (line  21)
+* '-m[no-]68881' command line option, M680x0: M68K-Opts.      (line  21)
+* '-m[no-]div' command line option, M680x0: M68K-Opts.        (line  21)
+* '-m[no-]emac' command line option, M680x0: M68K-Opts.       (line  21)
+* '-m[no-]float' command line option, M680x0: M68K-Opts.      (line  21)
+* '-m[no-]mac' command line option, M680x0: M68K-Opts.        (line  21)
+* '-m[no-]usp' command line option, M680x0: M68K-Opts.        (line  21)
+* '-N' command line option, CRIS:        CRIS-Opts.           (line  59)
+* '-nIp' option, M32RX:                  M32R-Opts.           (line 101)
+* '-no-bitinst', M32R2:                  M32R-Opts.           (line  54)
+* '-no-ignore-parallel-conflicts' option, M32RX: M32R-Opts.   (line  93)
+* '-no-mdebug' command line option, Alpha: Alpha Options.     (line  25)
+* '-no-parallel' option, M32RX:          M32R-Opts.           (line  51)
+* '-no-relax' option, i960:              Options-i960.        (line  66)
+* '-no-warn-explicit-parallel-conflicts' option, M32RX: M32R-Opts.
                                                               (line  79)
-* -no-warn-unmatched-high option, M32R:  M32R-Opts.           (line 111)
-* -nocpp ignored (MIPS):                 MIPS Opts.           (line 225)
-* -noreplace command line option, Alpha: Alpha Options.       (line  40)
+* '-no-warn-unmatched-high' option, M32R: M32R-Opts.          (line 111)
+* '-nocpp' ignored (MIPS):               MIPS Options.        (line 241)
+* '-noreplace' command line option, Alpha: Alpha Options.     (line  40)
 * -o:                                    o.                   (line   6)
-* -O option, M32RX:                      M32R-Opts.           (line  59)
-* -parallel option, M32RX:               M32R-Opts.           (line  46)
+* '-O' option, M32RX:                    M32R-Opts.           (line  59)
+* '-parallel' option, M32RX:             M32R-Opts.           (line  46)
 * -R:                                    R.                   (line   6)
-* -r800 command line option, Z80:        Z80 Options.         (line  41)
-* -relax command line option, Alpha:     Alpha Options.       (line  32)
-* -replace command line option, Alpha:   Alpha Options.       (line  40)
-* -S, ignored on VAX:                    VAX-Opts.            (line  11)
-* -t, ignored on VAX:                    VAX-Opts.            (line  36)
-* -T, ignored on VAX:                    VAX-Opts.            (line  11)
+* '-r800' command line option, Z80:      Z80 Options.         (line  35)
+* '-relax' command line option, Alpha:   Alpha Options.       (line  32)
+* '-replace' command line option, Alpha: Alpha Options.       (line  40)
+* '-S', ignored on VAX:                  VAX-Opts.            (line  11)
+* '-T', ignored on VAX:                  VAX-Opts.            (line  11)
+* '-t', ignored on VAX:                  VAX-Opts.            (line  36)
 * -v:                                    v.                   (line   6)
-* -V, redundant on VAX:                  VAX-Opts.            (line  22)
+* '-V', redundant on VAX:                VAX-Opts.            (line  22)
 * -version:                              v.                   (line   6)
 * -W:                                    W.                   (line  11)
-* -warn-explicit-parallel-conflicts option, M32RX: M32R-Opts. (line  65)
-* -warn-unmatched-high option, M32R:     M32R-Opts.           (line 105)
-* -Wnp option, M32RX:                    M32R-Opts.           (line  83)
-* -Wnuh option, M32RX:                   M32R-Opts.           (line 117)
-* -Wp option, M32RX:                     M32R-Opts.           (line  75)
-* -wsigned_overflow command line option, V850: V850 Options.  (line   9)
-* -Wuh option, M32RX:                    M32R-Opts.           (line 114)
-* -wunsigned_overflow command line option, V850: V850 Options.
+* '-warn-explicit-parallel-conflicts' option, M32RX: M32R-Opts.
+                                                              (line  65)
+* '-warn-unmatched-high' option, M32R:   M32R-Opts.           (line 105)
+* '-Wnp' option, M32RX:                  M32R-Opts.           (line  83)
+* '-Wnuh' option, M32RX:                 M32R-Opts.           (line 117)
+* '-Wp' option, M32RX:                   M32R-Opts.           (line  75)
+* '-wsigned_overflow' command line option, V850: V850 Options.
+                                                              (line   9)
+* '-Wuh' option, M32RX:                  M32R-Opts.           (line 114)
+* '-wunsigned_overflow' command line option, V850: V850 Options.
                                                               (line  16)
-* -x command line option, MMIX:          MMIX-Opts.           (line  44)
-* -z80 command line option, Z80:         Z80 Options.         (line   8)
-* -z8001 command line option, Z8000:     Z8000 Options.       (line   6)
-* -z8002 command line option, Z8000:     Z8000 Options.       (line   9)
-* . (symbol):                            Dot.                 (line   6)
-* .2byte directive, ARM:                 ARM Directives.      (line   6)
-* .4byte directive, ARM:                 ARM Directives.      (line   6)
-* .8byte directive, ARM:                 ARM Directives.      (line   6)
-* .align directive, ARM:                 ARM Directives.      (line  11)
-* .align directive, TILE-Gx:             TILE-Gx Directives.  (line   6)
-* .align directive, TILEPro:             TILEPro Directives.  (line   6)
-* .allow_suspicious_bundles directive, TILE-Gx: TILE-Gx Directives.
+* '-x' command line option, MMIX:        MMIX-Opts.           (line  44)
+* '-z80' command line option, Z80:       Z80 Options.         (line   8)
+* '-z8001' command line option, Z8000:   Z8000 Options.       (line   6)
+* '-z8002' command line option, Z8000:   Z8000 Options.       (line   9)
+* '.' (symbol):                          Dot.                 (line   6)
+* '.2byte' directive, ARM:               ARM Directives.      (line   6)
+* '.4byte' directive, ARM:               ARM Directives.      (line   6)
+* '.8byte' directive, ARM:               ARM Directives.      (line   6)
+* '.align' directive, ARM:               ARM Directives.      (line  11)
+* '.align' directive, TILE-Gx:           TILE-Gx Directives.  (line   6)
+* '.align' directive, TILEPro:           TILEPro Directives.  (line   6)
+* '.allow_suspicious_bundles' directive, TILE-Gx: TILE-Gx Directives.
                                                               (line  10)
-* .allow_suspicious_bundles directive, TILEPro: TILEPro Directives.
+* '.allow_suspicious_bundles' directive, TILEPro: TILEPro Directives.
                                                               (line  10)
-* .arch directive, ARM:                  ARM Directives.      (line  18)
-* .arch directive, TIC6X:                TIC6X Directives.    (line  10)
-* .arch_extension directive, ARM:        ARM Directives.      (line  25)
-* .arm directive, ARM:                   ARM Directives.      (line  34)
-* .big directive, M32RX:                 M32R-Directives.     (line  88)
-* .bss directive, AArch64:               AArch64 Directives.  (line   6)
-* .bss directive, ARM:                   ARM Directives.      (line  42)
-* .c6xabi_attribute directive, TIC6X:    TIC6X Directives.    (line  20)
-* .cantunwind directive, ARM:            ARM Directives.      (line  45)
-* .cantunwind directive, TIC6X:          TIC6X Directives.    (line  13)
-* .code directive, ARM:                  ARM Directives.      (line  49)
-* .cpu directive, ARM:                   ARM Directives.      (line  53)
-* .dn and .qn directives, ARM:           ARM Directives.      (line  60)
-* .eabi_attribute directive, ARM:        ARM Directives.      (line  83)
-* .ehtype directive, TIC6X:              TIC6X Directives.    (line  31)
-* .endp directive, TIC6X:                TIC6X Directives.    (line  34)
-* .even directive, ARM:                  ARM Directives.      (line 111)
-* .extend directive, ARM:                ARM Directives.      (line 114)
-* .fnend directive, ARM:                 ARM Directives.      (line 120)
-* .fnstart directive, ARM:               ARM Directives.      (line 129)
-* .force_thumb directive, ARM:           ARM Directives.      (line 132)
-* .fpu directive, ARM:                   ARM Directives.      (line 136)
-* .global:                               MIPS insn.           (line  12)
-* .handlerdata directive, ARM:           ARM Directives.      (line 140)
-* .handlerdata directive, TIC6X:         TIC6X Directives.    (line  39)
-* .insn:                                 MIPS insn.           (line   6)
-* .insn directive, s390:                 s390 Directives.     (line  11)
-* .inst directive, ARM:                  ARM Directives.      (line 149)
-* .ldouble directive, ARM:               ARM Directives.      (line 114)
-* .little directive, M32RX:              M32R-Directives.     (line  82)
-* .long directive, s390:                 s390 Directives.     (line  16)
-* .ltorg directive, AArch64:             AArch64 Directives.  (line   9)
-* .ltorg directive, ARM:                 ARM Directives.      (line 159)
-* .ltorg directive, s390:                s390 Directives.     (line  88)
-* .m32r directive, M32R:                 M32R-Directives.     (line  66)
-* .m32r2 directive, M32R2:               M32R-Directives.     (line  77)
-* .m32rx directive, M32RX:               M32R-Directives.     (line  72)
-* .machine directive, s390:              s390 Directives.     (line  93)
-* .machinemode directive, s390:          s390 Directives.     (line 103)
-* .movsp directive, ARM:                 ARM Directives.      (line 173)
-* .no_pointers directive, XStormy16:     XStormy16 Directives.
+* '.arch' directive, ARM:                ARM Directives.      (line  18)
+* '.arch' directive, TIC6X:              TIC6X Directives.    (line  10)
+* '.arch_extension' directive, ARM:      ARM Directives.      (line  25)
+* '.arm' directive, ARM:                 ARM Directives.      (line  33)
+* '.big' directive, M32RX:               M32R-Directives.     (line  88)
+* '.bss' directive, AArch64:             AArch64 Directives.  (line   6)
+* '.bss' directive, ARM:                 ARM Directives.      (line  41)
+* '.c6xabi_attribute' directive, TIC6X:  TIC6X Directives.    (line  20)
+* '.cantunwind' directive, ARM:          ARM Directives.      (line  44)
+* '.cantunwind' directive, TIC6X:        TIC6X Directives.    (line  13)
+* '.code' directive, ARM:                ARM Directives.      (line  48)
+* '.cpu' directive, ARM:                 ARM Directives.      (line  52)
+* '.dn' and '.qn' directives, ARM:       ARM Directives.      (line  59)
+* '.eabi_attribute' directive, ARM:      ARM Directives.      (line  83)
+* '.ehtype' directive, TIC6X:            TIC6X Directives.    (line  31)
+* '.endp' directive, TIC6X:              TIC6X Directives.    (line  34)
+* '.even' directive, ARM:                ARM Directives.      (line 111)
+* '.extend' directive, ARM:              ARM Directives.      (line 114)
+* '.fnend' directive, ARM:               ARM Directives.      (line 120)
+* '.fnstart' directive, ARM:             ARM Directives.      (line 128)
+* '.force_thumb' directive, ARM:         ARM Directives.      (line 131)
+* '.fpu' directive, ARM:                 ARM Directives.      (line 135)
+* '.global':                             MIPS insn.           (line  12)
+* '.handlerdata' directive, ARM:         ARM Directives.      (line 139)
+* '.handlerdata' directive, TIC6X:       TIC6X Directives.    (line  39)
+* '.insn':                               MIPS insn.           (line   6)
+* '.insn' directive, s390:               s390 Directives.     (line  11)
+* '.inst' directive, ARM:                ARM Directives.      (line 148)
+* '.ldouble' directive, ARM:             ARM Directives.      (line 114)
+* '.little' directive, M32RX:            M32R-Directives.     (line  82)
+* '.long' directive, s390:               s390 Directives.     (line  16)
+* '.ltorg' directive, AArch64:           AArch64 Directives.  (line   9)
+* '.ltorg' directive, ARM:               ARM Directives.      (line 158)
+* '.ltorg' directive, s390:              s390 Directives.     (line  79)
+* '.m32r' directive, M32R:               M32R-Directives.     (line  66)
+* '.m32r2' directive, M32R2:             M32R-Directives.     (line  77)
+* '.m32rx' directive, M32RX:             M32R-Directives.     (line  72)
+* '.machine' directive, s390:            s390 Directives.     (line  84)
+* '.machinemode' directive, s390:        s390 Directives.     (line  93)
+* '.movsp' directive, ARM:               ARM Directives.      (line 172)
+* '.nan' directive, MIPS:                MIPS NaN Encodings.  (line   6)
+* '.nocmp' directive, TIC6X:             TIC6X Directives.    (line  47)
+* '.no_pointers' directive, XStormy16:   XStormy16 Directives.
                                                               (line  14)
-* .nocmp directive, TIC6X:               TIC6X Directives.    (line  47)
 * .o:                                    Object.              (line   6)
-* .object_arch directive, ARM:           ARM Directives.      (line 178)
-* .packed directive, ARM:                ARM Directives.      (line 184)
-* .pad directive, ARM:                   ARM Directives.      (line  37)
-* .param on HPPA:                        HPPA Directives.     (line  19)
-* .personality directive, ARM:           ARM Directives.      (line 194)
-* .personality directive, TIC6X:         TIC6X Directives.    (line  55)
-* .personalityindex directive, ARM:      ARM Directives.      (line 197)
-* .personalityindex directive, TIC6X:    TIC6X Directives.    (line  51)
-* .pool directive, AArch64:              AArch64 Directives.  (line  23)
-* .pool directive, ARM:                  ARM Directives.      (line 201)
-* .quad directive, s390:                 s390 Directives.     (line  16)
-* .req directive, AArch64:               AArch64 Directives.  (line  26)
-* .req directive, ARM:                   ARM Directives.      (line 204)
-* .require_canonical_reg_names directive, TILE-Gx: TILE-Gx Directives.
+* '.object_arch' directive, ARM:         ARM Directives.      (line 177)
+* '.packed' directive, ARM:              ARM Directives.      (line 183)
+* '.pad' directive, ARM:                 ARM Directives.      (line  36)
+* '.pad' directive, ARM <1>:             ARM Directives.      (line 188)
+* '.param' on HPPA:                      HPPA Directives.     (line  19)
+* '.personality' directive, ARM:         ARM Directives.      (line 193)
+* '.personality' directive, TIC6X:       TIC6X Directives.    (line  55)
+* '.personalityindex' directive, ARM:    ARM Directives.      (line 196)
+* '.personalityindex' directive, TIC6X:  TIC6X Directives.    (line  51)
+* '.pool' directive, AArch64:            AArch64 Directives.  (line  23)
+* '.pool' directive, ARM:                ARM Directives.      (line 200)
+* '.quad' directive, s390:               s390 Directives.     (line  16)
+* '.req' directive, AArch64:             AArch64 Directives.  (line  26)
+* '.req' directive, ARM:                 ARM Directives.      (line 203)
+* '.require_canonical_reg_names' directive, TILE-Gx: TILE-Gx Directives.
                                                               (line  19)
-* .require_canonical_reg_names directive, TILEPro: TILEPro Directives.
+* '.require_canonical_reg_names' directive, TILEPro: TILEPro Directives.
                                                               (line  19)
-* .save directive, ARM:                  ARM Directives.      (line 209)
-* .scomm directive, TIC6X:               TIC6X Directives.    (line  58)
-* .secrel32 directive, ARM:              ARM Directives.      (line 247)
-* .set arch=CPU:                         MIPS ISA.            (line  18)
-* .set autoextend:                       MIPS autoextend.     (line   6)
-* .set doublefloat:                      MIPS floating-point. (line  12)
-* .set dsp:                              MIPS ASE instruction generation overrides.
+* '.save' directive, ARM:                ARM Directives.      (line 208)
+* '.scomm' directive, TIC6X:             TIC6X Directives.    (line  58)
+* '.secrel32' directive, ARM:            ARM Directives.      (line 246)
+* '.set arch=CPU':                       MIPS ISA.            (line  18)
+* '.set at':                             MIPS Macros.         (line  41)
+* '.set at=REG':                         MIPS Macros.         (line  35)
+* '.set autoextend':                     MIPS autoextend.     (line   6)
+* '.set doublefloat':                    MIPS Floating-Point. (line  12)
+* '.set dsp':                            MIPS ASE Instruction Generation Overrides.
                                                               (line  21)
-* .set dspr2:                            MIPS ASE instruction generation overrides.
+* '.set dspr2':                          MIPS ASE Instruction Generation Overrides.
                                                               (line  26)
-* .set hardfloat:                        MIPS floating-point. (line   6)
-* .set mcu:                              MIPS ASE instruction generation overrides.
-                                                              (line  37)
-* .set mdmx:                             MIPS ASE instruction generation overrides.
+* '.set hardfloat':                      MIPS Floating-Point. (line   6)
+* '.set insn32':                         MIPS assembly options.
+                                                              (line   6)
+* '.set macro':                          MIPS Macros.         (line  30)
+* '.set mcu':                            MIPS ASE Instruction Generation Overrides.
+                                                              (line  36)
+* '.set mdmx':                           MIPS ASE Instruction Generation Overrides.
                                                               (line  16)
-* .set mips3d:                           MIPS ASE instruction generation overrides.
+* '.set mips3d':                         MIPS ASE Instruction Generation Overrides.
                                                               (line   6)
-* .set mipsN:                            MIPS ISA.            (line   6)
-* .set mt:                               MIPS ASE instruction generation overrides.
-                                                              (line  32)
-* .set noautoextend:                     MIPS autoextend.     (line   6)
-* .set nodsp:                            MIPS ASE instruction generation overrides.
+* '.set mipsN':                          MIPS ISA.            (line   6)
+* '.set mt':                             MIPS ASE Instruction Generation Overrides.
+                                                              (line  31)
+* '.set noat':                           MIPS Macros.         (line  41)
+* '.set noautoextend':                   MIPS autoextend.     (line   6)
+* '.set nodsp':                          MIPS ASE Instruction Generation Overrides.
                                                               (line  21)
-* .set nodspr2:                          MIPS ASE instruction generation overrides.
+* '.set nodspr2':                        MIPS ASE Instruction Generation Overrides.
                                                               (line  26)
-* .set nomcu:                            MIPS ASE instruction generation overrides.
-                                                              (line  37)
-* .set nomdmx:                           MIPS ASE instruction generation overrides.
+* '.set noinsn32':                       MIPS assembly options.
+                                                              (line   6)
+* '.set nomacro':                        MIPS Macros.         (line  30)
+* '.set nomcu':                          MIPS ASE Instruction Generation Overrides.
+                                                              (line  36)
+* '.set nomdmx':                         MIPS ASE Instruction Generation Overrides.
                                                               (line  16)
-* .set nomips3d:                         MIPS ASE instruction generation overrides.
+* '.set nomips3d':                       MIPS ASE Instruction Generation Overrides.
                                                               (line   6)
-* .set nomt:                             MIPS ASE instruction generation overrides.
-                                                              (line  32)
-* .set nosmartmips:                      MIPS ASE instruction generation overrides.
+* '.set nomt':                           MIPS ASE Instruction Generation Overrides.
+                                                              (line  31)
+* '.set nosmartmips':                    MIPS ASE Instruction Generation Overrides.
                                                               (line  11)
-* .set nosym32:                          MIPS symbol sizes.   (line   6)
-* .set pop:                              MIPS option stack.   (line   6)
-* .set push:                             MIPS option stack.   (line   6)
-* .set singlefloat:                      MIPS floating-point. (line  12)
-* .set smartmips:                        MIPS ASE instruction generation overrides.
+* '.set nosym32':                        MIPS Symbol Sizes.   (line   6)
+* '.set novirt':                         MIPS ASE Instruction Generation Overrides.
+                                                              (line  41)
+* '.set pop':                            MIPS Option Stack.   (line   6)
+* '.set push':                           MIPS Option Stack.   (line   6)
+* '.set singlefloat':                    MIPS Floating-Point. (line  12)
+* '.set smartmips':                      MIPS ASE Instruction Generation Overrides.
                                                               (line  11)
-* .set softfloat:                        MIPS floating-point. (line   6)
-* .set sym32:                            MIPS symbol sizes.   (line   6)
-* .setfp directive, ARM:                 ARM Directives.      (line 233)
-* .short directive, s390:                s390 Directives.     (line  16)
-* .syntax directive, ARM:                ARM Directives.      (line 252)
-* .thumb directive, ARM:                 ARM Directives.      (line 256)
-* .thumb_func directive, ARM:            ARM Directives.      (line 259)
-* .thumb_set directive, ARM:             ARM Directives.      (line 270)
-* .tlsdescseq directive, ARM:            ARM Directives.      (line 277)
-* .unreq directive, AArch64:             AArch64 Directives.  (line  31)
-* .unreq directive, ARM:                 ARM Directives.      (line 282)
-* .unwind_raw directive, ARM:            ARM Directives.      (line 293)
-* .v850 directive, V850:                 V850 Directives.     (line  14)
-* .v850e directive, V850:                V850 Directives.     (line  20)
-* .v850e1 directive, V850:               V850 Directives.     (line  26)
-* .v850e2 directive, V850:               V850 Directives.     (line  32)
-* .v850e2v3 directive, V850:             V850 Directives.     (line  38)
-* .v850e2v4 directive, V850:             V850 Directives.     (line  44)
-* .v850e3v5 directive, V850:             V850 Directives.     (line  50)
-* .vsave directive, ARM:                 ARM Directives.      (line 300)
+* '.set softfloat':                      MIPS Floating-Point. (line   6)
+* '.set sym32':                          MIPS Symbol Sizes.   (line   6)
+* '.set virt':                           MIPS ASE Instruction Generation Overrides.
+                                                              (line  41)
+* '.setfp' directive, ARM:               ARM Directives.      (line 232)
+* '.short' directive, s390:              s390 Directives.     (line  16)
+* '.syntax' directive, ARM:              ARM Directives.      (line 251)
+* '.thumb' directive, ARM:               ARM Directives.      (line 255)
+* '.thumb_func' directive, ARM:          ARM Directives.      (line 258)
+* '.thumb_set' directive, ARM:           ARM Directives.      (line 269)
+* '.tlsdescseq' directive, ARM:          ARM Directives.      (line 276)
+* '.unreq' directive, AArch64:           AArch64 Directives.  (line  31)
+* '.unreq' directive, ARM:               ARM Directives.      (line 281)
+* '.unwind_raw' directive, ARM:          ARM Directives.      (line 292)
+* '.v850' directive, V850:               V850 Directives.     (line  14)
+* '.v850e' directive, V850:              V850 Directives.     (line  20)
+* '.v850e1' directive, V850:             V850 Directives.     (line  26)
+* '.v850e2' directive, V850:             V850 Directives.     (line  32)
+* '.v850e2v3' directive, V850:           V850 Directives.     (line  38)
+* '.v850e2v4' directive, V850:           V850 Directives.     (line  44)
+* '.v850e3v5' directive, V850:           V850 Directives.     (line  50)
+* '.vsave' directive, ARM:               ARM Directives.      (line 299)
 * .z8001:                                Z8000 Directives.    (line  11)
 * .z8002:                                Z8000 Directives.    (line  15)
 * 16-bit code, i386:                     i386-16bit.          (line   6)
-* 16bit_pointers directive, XStormy16:   XStormy16 Directives.
+* '16bit_pointers' directive, XStormy16: XStormy16 Directives.
                                                               (line   6)
-* 16byte directive, Nios II:             Nios II Directives.  (line  28)
-* 2byte directive, ARC:                  ARC Directives.      (line   9)
-* 2byte directive, Nios II:              Nios II Directives.  (line  19)
-* 32bit_pointers directive, XStormy16:   XStormy16 Directives.
+* '16byte' directive, Nios II:           Nios II Directives.  (line  28)
+* '2byte' directive, ARC:                ARC Directives.      (line   9)
+* '2byte' directive, Nios II:            Nios II Directives.  (line  19)
+* '32bit_pointers' directive, XStormy16: XStormy16 Directives.
                                                               (line  10)
-* 3byte directive, ARC:                  ARC Directives.      (line  12)
+* '3byte' directive, ARC:                ARC Directives.      (line  12)
 * 3DNow!, i386:                          i386-SIMD.           (line   6)
 * 3DNow!, x86-64:                        i386-SIMD.           (line   6)
 * 430 support:                           MSP430-Dependent.    (line   6)
-* 4byte directive, ARC:                  ARC Directives.      (line  15)
-* 4byte directive, Nios II:              Nios II Directives.  (line  22)
-* 8byte directive, Nios II:              Nios II Directives.  (line  25)
-* : (label):                             Statements.          (line  31)
-* @hi pseudo-op, XStormy16:              XStormy16 Opcodes.   (line  21)
-* @lo pseudo-op, XStormy16:              XStormy16 Opcodes.   (line  10)
+* '4byte' directive, ARC:                ARC Directives.      (line  15)
+* '4byte' directive, Nios II:            Nios II Directives.  (line  22)
+* '8byte' directive, Nios II:            Nios II Directives.  (line  25)
+* ':' (label):                           Statements.          (line  31)
+* '@hi' pseudo-op, XStormy16:            XStormy16 Opcodes.   (line  21)
+* '@lo' pseudo-op, XStormy16:            XStormy16 Opcodes.   (line  10)
 * @word modifier, D10V:                  D10V-Word.           (line   6)
-* \" (doublequote character):            Strings.             (line  43)
-* \\ (\ character):                      Strings.             (line  40)
-* \b (backspace character):              Strings.             (line  15)
-* \DDD (octal character code):           Strings.             (line  30)
-* \f (formfeed character):               Strings.             (line  18)
-* \n (newline character):                Strings.             (line  21)
-* \r (carriage return character):        Strings.             (line  24)
-* \t (tab):                              Strings.             (line  27)
-* \XD... (hex character code):           Strings.             (line  36)
+* '\"' (doublequote character):          Strings.             (line  43)
+* '\b' (backspace character):            Strings.             (line  15)
+* '\DDD' (octal character code):         Strings.             (line  30)
+* '\f' (formfeed character):             Strings.             (line  18)
+* '\n' (newline character):              Strings.             (line  21)
+* '\r' (carriage return character):      Strings.             (line  24)
+* '\t' (tab):                            Strings.             (line  27)
+* '\XD...' (hex character code):         Strings.             (line  36)
+* '\\' ('\' character):                  Strings.             (line  40)
 * _ opcode prefix:                       Xtensa Opcodes.      (line   9)
 * a.out:                                 Object.              (line   6)
-* a.out symbol attributes:               a.out Symbols.       (line   6)
-* A_DIR environment variable, TIC54X:    TIC54X-Env.          (line   6)
+* 'a.out' symbol attributes:             a.out Symbols.       (line   6)
 * AArch64 floating point (IEEE):         AArch64 Floating Point.
                                                               (line   6)
 * AArch64 immediate character:           AArch64-Chars.       (line  13)
@@ -23057,40 +22865,40 @@ AS Index
 * AArch64 register names:                AArch64-Regs.        (line   6)
 * AArch64 relocations:                   AArch64-Relocations. (line   6)
 * AArch64 support:                       AArch64-Dependent.   (line   6)
-* ABI options, SH64:                     SH64 Options.        (line  29)
-* ABORT directive:                       ABORT (COFF).        (line   6)
-* abort directive:                       Abort.               (line   6)
+* ABI options, SH64:                     SH64 Options.        (line  25)
+* 'abort' directive:                     Abort.               (line   6)
+* 'ABORT' directive:                     ABORT (COFF).        (line   6)
 * absolute section:                      Ld Sections.         (line  29)
-* absolute-literals directive:           Absolute Literals Directive.
+* 'absolute-literals' directive:         Absolute Literals Directive.
                                                               (line   6)
-* ADDI instructions, relaxation:         Xtensa Immediate Relaxation.
+* 'ADDI' instructions, relaxation:       Xtensa Immediate Relaxation.
                                                               (line  43)
-* addition, permitted arguments:         Infix Ops.           (line  44)
+* addition, permitted arguments:         Infix Ops.           (line  45)
 * addresses:                             Expressions.         (line   6)
-* addresses, format of:                  Secs Background.     (line  68)
+* addresses, format of:                  Secs Background.     (line  65)
 * addressing modes, D10V:                D10V-Addressing.     (line   6)
 * addressing modes, D30V:                D30V-Addressing.     (line   6)
 * addressing modes, H8/300:              H8/300-Addressing.   (line   6)
 * addressing modes, M680x0:              M68K-Syntax.         (line  21)
-* addressing modes, M68HC11:             M68HC11-Syntax.      (line  30)
+* addressing modes, M68HC11:             M68HC11-Syntax.      (line  29)
 * addressing modes, SH:                  SH-Addressing.       (line   6)
 * addressing modes, SH64:                SH64-Addressing.     (line   6)
-* addressing modes, XGATE:               XGATE-Syntax.        (line  29)
+* addressing modes, XGATE:               XGATE-Syntax.        (line  28)
 * addressing modes, Z8000:               Z8000-Addressing.    (line   6)
-* ADR reg,<label> pseudo op, ARM:        ARM Opcodes.         (line  25)
-* ADRL reg,<label> pseudo op, ARM:       ARM Opcodes.         (line  35)
+* 'ADR reg,<label>' pseudo op, ARM:      ARM Opcodes.         (line  25)
+* 'ADRL reg,<label>' pseudo op, ARM:     ARM Opcodes.         (line  35)
 * ADRP, ADD, LDR/STR group relocations, AArch64: AArch64-Relocations.
                                                               (line  14)
 * advancing location counter:            Org.                 (line   6)
-* align directive:                       Align.               (line   6)
-* align directive, Nios II:              Nios II Directives.  (line   6)
-* align directive, SPARC:                Sparc-Directives.    (line   9)
-* align directive, TIC54X:               TIC54X-Directives.   (line   6)
+* 'align' directive:                     Align.               (line   6)
+* 'align' directive, Nios II:            Nios II Directives.  (line   6)
+* 'align' directive, SPARC:              Sparc-Directives.    (line   9)
+* 'align' directive, TIC54X:             TIC54X-Directives.   (line   6)
 * aligned instruction bundle:            Bundle directives.   (line   6)
 * alignment for NEON instructions:       ARM-Neon-Alignment.  (line   6)
 * alignment of branch targets:           Xtensa Automatic Alignment.
                                                               (line   6)
-* alignment of LOOP instructions:        Xtensa Automatic Alignment.
+* alignment of 'LOOP' instructions:      Xtensa Automatic Alignment.
                                                               (line   6)
 * Alpha floating point (IEEE):           Alpha Floating Point.
                                                               (line   6)
@@ -23101,8 +22909,8 @@ AS Index
 * Alpha registers:                       Alpha-Regs.          (line   6)
 * Alpha relocations:                     Alpha-Relocs.        (line   6)
 * Alpha support:                         Alpha-Dependent.     (line   6)
-* Alpha Syntax:                          Alpha Options.       (line  61)
-* Alpha-only directives:                 Alpha Directives.    (line  10)
+* Alpha Syntax:                          Alpha Options.       (line  60)
+* Alpha-only directives:                 Alpha Directives.    (line   9)
 * Altera Nios II support:                NiosII-Dependent.    (line   6)
 * altered difference tables:             Word.                (line  12)
 * alternate syntax for the 680x0:        M68K-Moto-Syntax.    (line   6)
@@ -23114,12 +22922,13 @@ AS Index
 * ARC options (none):                    ARC Options.         (line   6)
 * ARC register names:                    ARC-Regs.            (line   6)
 * ARC support:                           ARC-Dependent.       (line   6)
-* arc5 arc5, ARC:                        ARC Options.         (line  10)
-* arc6 arc6, ARC:                        ARC Options.         (line  13)
-* arc7 arc7, ARC:                        ARC Options.         (line  21)
-* arc8 arc8, ARC:                        ARC Options.         (line  24)
+* 'arc5' arc5, ARC:                      ARC Options.         (line  10)
+* 'arc6' arc6, ARC:                      ARC Options.         (line  13)
+* 'arc7' arc7, ARC:                      ARC Options.         (line  21)
+* 'arc8' arc8, ARC:                      ARC Options.         (line  24)
 * arch directive, i386:                  i386-Arch.           (line   6)
-* arch directive, M680x0:                M68K-Directives.     (line  22)
+* 'arch' directive, M680x0:              M68K-Directives.     (line  22)
+* 'arch' directive, MSP 430:             MSP430 Directives.   (line  18)
 * arch directive, x86-64:                i386-Arch.           (line   6)
 * architecture options, i960:            Options-i960.        (line   6)
 * architecture options, IP2022:          IP2K-Opts.           (line   9)
@@ -23129,14 +22938,14 @@ AS Index
 * architecture options, M32R:            M32R-Opts.           (line  21)
 * architecture options, M32R2:           M32R-Opts.           (line  17)
 * architecture options, M32RX:           M32R-Opts.           (line   9)
-* architecture options, M680x0:          M68K-Opts.           (line  98)
+* architecture options, M680x0:          M68K-Opts.           (line  99)
 * Architecture variant option, CRIS:     CRIS-Opts.           (line  34)
 * architectures, Meta:                   Meta Options.        (line   6)
 * architectures, PowerPC:                PowerPC-Opts.        (line   6)
 * architectures, SCORE:                  SCORE-Opts.          (line   6)
 * architectures, SPARC:                  Sparc-Opts.          (line   6)
-* arguments for addition:                Infix Ops.           (line  44)
-* arguments for subtraction:             Infix Ops.           (line  49)
+* arguments for addition:                Infix Ops.           (line  45)
+* arguments for subtraction:             Infix Ops.           (line  50)
 * arguments in expressions:              Arguments.           (line   6)
 * arithmetic functions:                  Operators.           (line   6)
 * arithmetic operands:                   Arguments.           (line   6)
@@ -23151,13 +22960,13 @@ AS Index
 * ARM options (none):                    ARM Options.         (line   6)
 * ARM register names:                    ARM-Regs.            (line   6)
 * ARM support:                           ARM-Dependent.       (line   6)
-* ascii directive:                       Ascii.               (line   6)
-* asciz directive:                       Asciz.               (line   6)
-* asg directive, TIC54X:                 TIC54X-Directives.   (line  20)
+* 'ascii' directive:                     Ascii.               (line   6)
+* 'asciz' directive:                     Asciz.               (line   6)
+* 'asg' directive, TIC54X:               TIC54X-Directives.   (line  18)
 * assembler bugs, reporting:             Bug Reporting.       (line   6)
 * assembler crash:                       Bug Criteria.        (line   9)
 * assembler directive .3byte, RX:        RX-Directives.       (line   9)
-* assembler directive .arch, CRIS:       CRIS-Pseudos.        (line  45)
+* assembler directive .arch, CRIS:       CRIS-Pseudos.        (line  50)
 * assembler directive .dword, CRIS:      CRIS-Pseudos.        (line  12)
 * assembler directive .far, M68HC11:     M68HC11-Directives.  (line  20)
 * assembler directive .fetchalign, RX:   RX-Directives.       (line  13)
@@ -23165,19 +22974,19 @@ AS Index
                                                               (line  26)
 * assembler directive .mode, M68HC11:    M68HC11-Directives.  (line  16)
 * assembler directive .relax, M68HC11:   M68HC11-Directives.  (line  10)
-* assembler directive .syntax, CRIS:     CRIS-Pseudos.        (line  17)
+* assembler directive .syntax, CRIS:     CRIS-Pseudos.        (line  18)
 * assembler directive .xrefb, M68HC11:   M68HC11-Directives.  (line  31)
-* assembler directive BSPEC, MMIX:       MMIX-Pseudos.        (line 131)
-* assembler directive BYTE, MMIX:        MMIX-Pseudos.        (line  97)
-* assembler directive ESPEC, MMIX:       MMIX-Pseudos.        (line 131)
-* assembler directive GREG, MMIX:        MMIX-Pseudos.        (line  50)
-* assembler directive IS, MMIX:          MMIX-Pseudos.        (line  42)
+* assembler directive BSPEC, MMIX:       MMIX-Pseudos.        (line 137)
+* assembler directive BYTE, MMIX:        MMIX-Pseudos.        (line 101)
+* assembler directive ESPEC, MMIX:       MMIX-Pseudos.        (line 137)
+* assembler directive GREG, MMIX:        MMIX-Pseudos.        (line  53)
+* assembler directive IS, MMIX:          MMIX-Pseudos.        (line  44)
 * assembler directive LOC, MMIX:         MMIX-Pseudos.        (line   7)
-* assembler directive LOCAL, MMIX:       MMIX-Pseudos.        (line  28)
-* assembler directive OCTA, MMIX:        MMIX-Pseudos.        (line 108)
-* assembler directive PREFIX, MMIX:      MMIX-Pseudos.        (line 120)
-* assembler directive TETRA, MMIX:       MMIX-Pseudos.        (line 108)
-* assembler directive WYDE, MMIX:        MMIX-Pseudos.        (line 108)
+* assembler directive LOCAL, MMIX:       MMIX-Pseudos.        (line  29)
+* assembler directive OCTA, MMIX:        MMIX-Pseudos.        (line 113)
+* assembler directive PREFIX, MMIX:      MMIX-Pseudos.        (line 125)
+* assembler directive TETRA, MMIX:       MMIX-Pseudos.        (line 113)
+* assembler directive WYDE, MMIX:        MMIX-Pseudos.        (line 113)
 * assembler directives, CRIS:            CRIS-Pseudos.        (line   6)
 * assembler directives, M68HC11:         M68HC11-Directives.  (line   6)
 * assembler directives, M68HC12:         M68HC11-Directives.  (line   6)
@@ -23189,12 +22998,13 @@ AS Index
 * assembler version:                     v.                   (line   6)
 * assembler, and linker:                 Secs Background.     (line  10)
 * assembly listings, enabling:           a.                   (line   6)
-* assigning values to symbols <1>:       Equ.                 (line   6)
 * assigning values to symbols:           Setting Symbols.     (line   6)
-* atmp directive, i860:                  Directives-i860.     (line  16)
+* assigning values to symbols <1>:       Equ.                 (line   6)
+* 'at' register, MIPS:                   MIPS Macros.         (line  35)
+* 'atmp' directive, i860:                Directives-i860.     (line  16)
+* attributes, symbol:                    Symbol Attributes.   (line   6)
 * att_syntax pseudo op, i386:            i386-Variations.     (line   6)
 * att_syntax pseudo op, x86-64:          i386-Variations.     (line   6)
-* attributes, symbol:                    Symbol Attributes.   (line   6)
 * auxiliary attributes, COFF symbols:    COFF Symbols.        (line  19)
 * auxiliary symbol information, COFF:    Dim.                 (line   6)
 * AVR line comment character:            AVR-Chars.           (line   6)
@@ -23204,15 +23014,16 @@ AS Index
 * AVR options (none):                    AVR Options.         (line   6)
 * AVR register names:                    AVR-Regs.            (line   6)
 * AVR support:                           AVR-Dependent.       (line   6)
-* backslash (\\):                        Strings.             (line  40)
-* backspace (\b):                        Strings.             (line  15)
-* balign directive:                      Balign.              (line   6)
-* balignl directive:                     Balign.              (line  27)
-* balignw directive:                     Balign.              (line  27)
-* bes directive, TIC54X:                 TIC54X-Directives.   (line 196)
-* big endian output, MIPS:               Overview.            (line 727)
-* big endian output, PJ:                 Overview.            (line 630)
-* big-endian output, MIPS:               MIPS Opts.           (line  13)
+* 'A_DIR' environment variable, TIC54X:  TIC54X-Env.          (line   6)
+* backslash ('\\'):                      Strings.             (line  40)
+* backspace ('\b'):                      Strings.             (line  15)
+* 'balign' directive:                    Balign.              (line   6)
+* 'balignl' directive:                   Balign.              (line  27)
+* 'balignw' directive:                   Balign.              (line  27)
+* 'bes' directive, TIC54X:               TIC54X-Directives.   (line 194)
+* big endian output, MIPS:               Overview.            (line 720)
+* big endian output, PJ:                 Overview.            (line 627)
+* big-endian output, MIPS:               MIPS Options.        (line  13)
 * big-endian output, TIC6X:              TIC6X Options.       (line  46)
 * bignums:                               Bignums.             (line   6)
 * binary constants, TIC54X:              TIC54X-Constants.    (line   8)
@@ -23224,7 +23035,7 @@ AS Index
 * Blackfin options (none):               Blackfin Options.    (line   6)
 * Blackfin support:                      Blackfin-Dependent.  (line   6)
 * Blackfin syntax:                       Blackfin Syntax.     (line   6)
-* block:                                 Z8000 Directives.    (line  55)
+* block:                                 Z8000 Directives.    (line  54)
 * BMI, i386:                             i386-BMI.            (line   6)
 * BMI, x86-64:                           i386-BMI.            (line   6)
 * branch improvement, M680x0:            M68K-Branch.         (line   6)
@@ -23236,12 +23047,12 @@ AS Index
 * branch statistics table, i960:         Options-i960.        (line  40)
 * branch target alignment:               Xtensa Automatic Alignment.
                                                               (line   6)
-* break directive, TIC54X:               TIC54X-Directives.   (line 143)
+* 'break' directive, TIC54X:             TIC54X-Directives.   (line 141)
 * BSD syntax:                            PDP-11-Syntax.       (line   6)
-* bss directive, i960:                   Directives-i960.     (line   6)
-* bss directive, TIC54X:                 TIC54X-Directives.   (line  29)
-* bss section <1>:                       bss.                 (line   6)
+* 'bss' directive, i960:                 Directives-i960.     (line   6)
+* 'bss' directive, TIC54X:               TIC54X-Directives.   (line  27)
 * bss section:                           Ld Sections.         (line  20)
+* bss section <1>:                       bss.                 (line   6)
 * bug criteria:                          Bug Criteria.        (line   6)
 * bug reports:                           Bug Reporting.       (line   6)
 * bugs in assembler:                     Reporting Bugs.      (line   6)
@@ -23249,40 +23060,39 @@ AS Index
 * builtin math functions, TIC54X:        TIC54X-Builtins.     (line   6)
 * builtin subsym functions, TIC54X:      TIC54X-Macros.       (line  16)
 * bundle:                                Bundle directives.   (line   6)
-* bundle-locked:                         Bundle directives.   (line  35)
-* bundle_align_mode directive:           Bundle directives.   (line   6)
-* bundle_lock directive:                 Bundle directives.   (line  28)
-* bundle_unlock directive:               Bundle directives.   (line  28)
+* bundle-locked:                         Bundle directives.   (line  36)
+* 'bundle_align_mode' directive:         Bundle directives.   (line   6)
+* 'bundle_lock' directive:               Bundle directives.   (line  28)
+* 'bundle_unlock' directive:             Bundle directives.   (line  28)
 * bus lock prefixes, i386:               i386-Prefixes.       (line  36)
 * bval:                                  Z8000 Directives.    (line  30)
-* byte directive:                        Byte.                (line   6)
-* byte directive, TIC54X:                TIC54X-Directives.   (line  36)
-* C54XDSP_DIR environment variable, TIC54X: TIC54X-Env.       (line   6)
-* c_mode directive, TIC54X:              TIC54X-Directives.   (line  51)
-* call directive, Nios II:               Nios II Relocations. (line  38)
-* call instructions, i386:               i386-Mnemonics.      (line  56)
+* 'byte' directive:                      Byte.                (line   6)
+* 'byte' directive, TIC54X:              TIC54X-Directives.   (line  34)
+* 'C54XDSP_DIR' environment variable, TIC54X: TIC54X-Env.     (line   6)
+* 'call' directive, Nios II:             Nios II Relocations. (line  38)
+* call instructions, i386:               i386-Mnemonics.      (line  55)
 * call instructions, relaxation:         Xtensa Call Relaxation.
                                                               (line   6)
-* call instructions, x86-64:             i386-Mnemonics.      (line  56)
-* callj, i960 pseudo-opcode:             callj-i960.          (line   6)
-* carriage return (\r):                  Strings.             (line  24)
+* call instructions, x86-64:             i386-Mnemonics.      (line  55)
+* 'callj', i960 pseudo-opcode:           callj-i960.          (line   6)
+* carriage return ('\r'):                Strings.             (line  24)
 * case sensitivity, Z80:                 Z80-Case.            (line   6)
-* cfi_endproc directive:                 CFI directives.      (line  26)
-* cfi_sections directive:                CFI directives.      (line   6)
-* cfi_startproc directive:               CFI directives.      (line  16)
-* char directive, TIC54X:                TIC54X-Directives.   (line  36)
+* 'cfi_endproc' directive:               CFI directives.      (line  26)
+* 'cfi_sections' directive:              CFI directives.      (line   6)
+* 'cfi_startproc' directive:             CFI directives.      (line  16)
+* 'char' directive, TIC54X:              TIC54X-Directives.   (line  34)
 * character constant, Z80:               Z80-Chars.           (line  20)
 * character constants:                   Characters.          (line   6)
 * character escape codes:                Strings.             (line  15)
 * character escapes, Z80:                Z80-Chars.           (line  18)
 * character, single:                     Chars.               (line   6)
 * characters used in symbols:            Symbol Intro.        (line   6)
-* clink directive, TIC54X:               TIC54X-Directives.   (line  45)
-* code16 directive, i386:                i386-16bit.          (line   6)
-* code16gcc directive, i386:             i386-16bit.          (line   6)
-* code32 directive, i386:                i386-16bit.          (line   6)
-* code64 directive, i386:                i386-16bit.          (line   6)
-* code64 directive, x86-64:              i386-16bit.          (line   6)
+* 'clink' directive, TIC54X:             TIC54X-Directives.   (line  43)
+* 'code16' directive, i386:              i386-16bit.          (line   6)
+* 'code16gcc' directive, i386:           i386-16bit.          (line   6)
+* 'code32' directive, i386:              i386-16bit.          (line   6)
+* 'code64' directive, i386:              i386-16bit.          (line   6)
+* 'code64' directive, x86-64:            i386-16bit.          (line   6)
 * COFF auxiliary symbol information:     Dim.                 (line   6)
 * COFF structure debugging:              Tag.                 (line   6)
 * COFF symbol attributes:                COFF Symbols.        (line   6)
@@ -23292,7 +23102,7 @@ AS Index
 * COFF symbols, debugging:               Def.                 (line   6)
 * COFF value attribute:                  Val.                 (line   6)
 * COMDAT:                                Linkonce.            (line   6)
-* comm directive:                        Comm.                (line   6)
+* 'comm' directive:                      Comm.                (line   6)
 * command line conventions:              Command Line.        (line   6)
 * command line options, V850:            V850 Options.        (line   9)
 * command-line options ignored, VAX:     VAX-Opts.            (line   6)
@@ -23300,14 +23110,14 @@ AS Index
 * comments:                              Comments.            (line   6)
 * comments, M680x0:                      M68K-Chars.          (line   6)
 * comments, removed by preprocessor:     Preprocessing.       (line  11)
-* common directive, SPARC:               Sparc-Directives.    (line  12)
+* 'common' directive, SPARC:             Sparc-Directives.    (line  12)
 * common sections:                       Linkonce.            (line   6)
 * common variable storage:               bss.                 (line   6)
 * compare and jump expansions, i960:     Compare-and-branch-i960.
                                                               (line  13)
 * compare/branch instructions, i960:     Compare-and-branch-i960.
                                                               (line   6)
-* comparison expressions:                Infix Ops.           (line  55)
+* comparison expressions:                Infix Ops.           (line  56)
 * conditional assembly:                  If.                  (line   6)
 * constant, single character:            Chars.               (line   6)
 * constants:                             Constants.           (line   6)
@@ -23320,55 +23130,57 @@ AS Index
 * constants, Sparc:                      Sparc-Constants.     (line   6)
 * constants, string:                     Strings.             (line   6)
 * constants, TIC54X:                     TIC54X-Constants.    (line   6)
-* conversion instructions, i386:         i386-Mnemonics.      (line  37)
-* conversion instructions, x86-64:       i386-Mnemonics.      (line  37)
+* conversion instructions, i386:         i386-Mnemonics.      (line  36)
+* conversion instructions, x86-64:       i386-Mnemonics.      (line  36)
 * coprocessor wait, i386:                i386-Prefixes.       (line  40)
-* copy directive, TIC54X:                TIC54X-Directives.   (line  54)
-* cpu directive, M680x0:                 M68K-Directives.     (line  30)
+* 'copy' directive, TIC54X:              TIC54X-Directives.   (line  52)
+* 'cpu' directive, M680x0:               M68K-Directives.     (line  30)
+* 'cpu' directive, MSP 430:              MSP430 Directives.   (line  22)
 * CR16 line comment character:           CR16-Chars.          (line   6)
-* CR16 line separator:                   CR16-Chars.          (line  13)
+* CR16 line separator:                   CR16-Chars.          (line  12)
 * CR16 Operand Qualifiers:               CR16 Operand Qualifiers.
                                                               (line   6)
 * CR16 support:                          CR16-Dependent.      (line   6)
 * crash of assembler:                    Bug Criteria.        (line   9)
-* CRIS --emulation=crisaout command line option: CRIS-Opts.   (line   9)
-* CRIS --emulation=criself command line option: CRIS-Opts.    (line   9)
-* CRIS --march=ARCHITECTURE command line option: CRIS-Opts.   (line  34)
-* CRIS --mul-bug-abort command line option: CRIS-Opts.        (line  62)
-* CRIS --no-mul-bug-abort command line option: CRIS-Opts.     (line  62)
-* CRIS --no-underscore command line option: CRIS-Opts.        (line  15)
-* CRIS --pic command line option:        CRIS-Opts.           (line  27)
-* CRIS --underscore command line option: CRIS-Opts.           (line  15)
-* CRIS -N command line option:           CRIS-Opts.           (line  58)
+* CRIS '--emulation=crisaout' command line option: CRIS-Opts. (line   9)
+* CRIS '--emulation=criself' command line option: CRIS-Opts.  (line   9)
+* CRIS '--march=ARCHITECTURE' command line option: CRIS-Opts. (line  34)
+* CRIS '--mul-bug-abort' command line option: CRIS-Opts.      (line  63)
+* CRIS '--no-mul-bug-abort' command line option: CRIS-Opts.   (line  63)
+* CRIS '--no-underscore' command line option: CRIS-Opts.      (line  15)
+* CRIS '--pic' command line option:      CRIS-Opts.           (line  27)
+* CRIS '--underscore' command line option: CRIS-Opts.         (line  15)
+* CRIS '-N' command line option:         CRIS-Opts.           (line  59)
 * CRIS architecture variant option:      CRIS-Opts.           (line  34)
-* CRIS assembler directive .arch:        CRIS-Pseudos.        (line  45)
+* CRIS assembler directive .arch:        CRIS-Pseudos.        (line  50)
 * CRIS assembler directive .dword:       CRIS-Pseudos.        (line  12)
-* CRIS assembler directive .syntax:      CRIS-Pseudos.        (line  17)
+* CRIS assembler directive .syntax:      CRIS-Pseudos.        (line  18)
 * CRIS assembler directives:             CRIS-Pseudos.        (line   6)
 * CRIS built-in symbols:                 CRIS-Symbols.        (line   6)
 * CRIS instruction expansion:            CRIS-Expand.         (line   6)
 * CRIS line comment characters:          CRIS-Chars.          (line   6)
 * CRIS options:                          CRIS-Opts.           (line   6)
 * CRIS position-independent code:        CRIS-Opts.           (line  27)
-* CRIS pseudo-op .arch:                  CRIS-Pseudos.        (line  45)
+* CRIS pseudo-op .arch:                  CRIS-Pseudos.        (line  50)
 * CRIS pseudo-op .dword:                 CRIS-Pseudos.        (line  12)
-* CRIS pseudo-op .syntax:                CRIS-Pseudos.        (line  17)
+* CRIS pseudo-op .syntax:                CRIS-Pseudos.        (line  18)
 * CRIS pseudo-ops:                       CRIS-Pseudos.        (line   6)
 * CRIS register names:                   CRIS-Regs.           (line   6)
 * CRIS support:                          CRIS-Dependent.      (line   6)
 * CRIS symbols in position-independent code: CRIS-Pic.        (line   6)
-* ctbp register, V850:                   V850-Regs.           (line 131)
-* ctoff pseudo-op, V850:                 V850 Opcodes.        (line 111)
-* ctpc register, V850:                   V850-Regs.           (line 119)
-* ctpsw register, V850:                  V850-Regs.           (line 122)
+* 'ctbp' register, V850:                 V850-Regs.           (line  90)
+* 'ctoff' pseudo-op, V850:               V850 Opcodes.        (line 110)
+* 'ctpc' register, V850:                 V850-Regs.           (line  82)
+* 'ctpsw' register, V850:                V850-Regs.           (line  84)
 * current address:                       Dot.                 (line   6)
 * current address, advancing:            Org.                 (line   6)
+* 'c_mode' directive, TIC54X:            TIC54X-Directives.   (line  49)
 * D10V @word modifier:                   D10V-Word.           (line   6)
 * D10V addressing modes:                 D10V-Addressing.     (line   6)
 * D10V floating point:                   D10V-Float.          (line   6)
 * D10V line comment character:           D10V-Chars.          (line   6)
 * D10V opcode summary:                   D10V-Opcodes.        (line   6)
-* D10V optimization:                     Overview.            (line 490)
+* D10V optimization:                     Overview.            (line 493)
 * D10V options:                          D10V-Opts.           (line   6)
 * D10V registers:                        D10V-Regs.           (line   6)
 * D10V size modifiers:                   D10V-Size.           (line   6)
@@ -23380,10 +23192,10 @@ AS Index
 * D30V floating point:                   D30V-Float.          (line   6)
 * D30V Guarded Execution:                D30V-Guarded.        (line   6)
 * D30V line comment character:           D30V-Chars.          (line   6)
-* D30V nops:                             Overview.            (line 498)
-* D30V nops after 32-bit multiply:       Overview.            (line 501)
+* D30V nops:                             Overview.            (line 501)
+* D30V nops after 32-bit multiply:       Overview.            (line 504)
 * D30V opcode summary:                   D30V-Opcodes.        (line   6)
-* D30V optimization:                     Overview.            (line 495)
+* D30V optimization:                     Overview.            (line 498)
 * D30V options:                          D30V-Opts.           (line   6)
 * D30V registers:                        D30V-Regs.           (line   6)
 * D30V size modifiers:                   D30V-Size.           (line   6)
@@ -23393,32 +23205,32 @@ AS Index
 * D30V syntax:                           D30V-Syntax.         (line   6)
 * data alignment on SPARC:               Sparc-Aligned-Data.  (line   6)
 * data and text sections, joining:       R.                   (line   6)
-* data directive:                        Data.                (line   6)
-* data directive, TIC54X:                TIC54X-Directives.   (line  61)
+* 'data' directive:                      Data.                (line   6)
+* 'data' directive, TIC54X:              TIC54X-Directives.   (line  59)
 * data relocations, ARM:                 ARM-Relocations.     (line   6)
 * data section:                          Ld Sections.         (line   9)
-* data1 directive, M680x0:               M68K-Directives.     (line   9)
-* data2 directive, M680x0:               M68K-Directives.     (line  12)
+* 'data1' directive, M680x0:             M68K-Directives.     (line   9)
+* 'data2' directive, M680x0:             M68K-Directives.     (line  12)
 * datalabel, SH64:                       SH64-Addressing.     (line  16)
-* dbpc register, V850:                   V850-Regs.           (line 125)
-* dbpsw register, V850:                  V850-Regs.           (line 128)
+* 'dbpc' register, V850:                 V850-Regs.           (line  86)
+* 'dbpsw' register, V850:                V850-Regs.           (line  88)
 * debuggers, and symbol order:           Symbols.             (line  10)
 * debugging COFF symbols:                Def.                 (line   6)
 * DEC syntax:                            PDP-11-Syntax.       (line   6)
 * decimal integers:                      Integers.            (line  12)
-* def directive:                         Def.                 (line   6)
-* def directive, TIC54X:                 TIC54X-Directives.   (line 103)
+* 'def' directive:                       Def.                 (line   6)
+* 'def' directive, TIC54X:               TIC54X-Directives.   (line 101)
 * density instructions:                  Density Instructions.
                                                               (line   6)
 * dependency tracking:                   MD.                  (line   6)
 * deprecated directives:                 Deprecated.          (line   6)
-* desc directive:                        Desc.                (line   6)
-* descriptor, of a.out symbol:           Symbol Desc.         (line   6)
-* dfloat directive, VAX:                 VAX-directives.      (line  10)
+* 'desc' directive:                      Desc.                (line   6)
+* descriptor, of 'a.out' symbol:         Symbol Desc.         (line   6)
+* 'dfloat' directive, VAX:               VAX-directives.      (line   9)
 * difference tables altered:             Word.                (line  12)
 * difference tables, warning:            K.                   (line   6)
 * differences, mmixal:                   MMIX-mmixal.         (line   6)
-* dim directive:                         Dim.                 (line   6)
+* 'dim' directive:                       Dim.                 (line   6)
 * directives and instructions:           Statements.          (line  20)
 * directives for PowerPC:                PowerPC-Pseudo.      (line   6)
 * directives for SCORE:                  SCORE-Pseudo.        (line   6)
@@ -23428,66 +23240,65 @@ AS Index
 * directives, machine independent:       Pseudo Ops.          (line   6)
 * directives, Xtensa:                    Xtensa Directives.   (line   6)
 * directives, Z8000:                     Z8000 Directives.    (line   6)
-* Disable floating-point instructions:   MIPS floating-point. (line   6)
-* Disable single-precision floating-point operations: MIPS floating-point.
+* Disable floating-point instructions:   MIPS Floating-Point. (line   6)
+* Disable single-precision floating-point operations: MIPS Floating-Point.
                                                               (line  12)
 * displacement sizing character, VAX:    VAX-operands.        (line  12)
-* dollar local symbols:                  Symbol Names.        (line 110)
+* dollar local symbols:                  Symbol Names.        (line 109)
 * dot (symbol):                          Dot.                 (line   6)
-* double directive:                      Double.              (line   6)
-* double directive, i386:                i386-Float.          (line  14)
-* double directive, M680x0:              M68K-Float.          (line  14)
-* double directive, M68HC11:             M68HC11-Float.       (line  14)
-* double directive, RX:                  RX-Float.            (line  11)
-* double directive, TIC54X:              TIC54X-Directives.   (line  64)
-* double directive, VAX:                 VAX-float.           (line  15)
-* double directive, x86-64:              i386-Float.          (line  14)
-* double directive, XGATE:               XGATE-Float.         (line  13)
-* doublequote (\"):                      Strings.             (line  43)
-* drlist directive, TIC54X:              TIC54X-Directives.   (line  73)
-* drnolist directive, TIC54X:            TIC54X-Directives.   (line  73)
-* dual directive, i860:                  Directives-i860.     (line   6)
-* dword directive, Nios II:              Nios II Directives.  (line  16)
-* EB command line option, Nios II:       Nios II Options.     (line  23)
-* ECOFF sections:                        MIPS Object.         (line   6)
-* ecr register, V850:                    V850-Regs.           (line 113)
+* 'double' directive:                    Double.              (line   6)
+* 'double' directive, i386:              i386-Float.          (line  14)
+* 'double' directive, M680x0:            M68K-Float.          (line  14)
+* 'double' directive, M68HC11:           M68HC11-Float.       (line  14)
+* 'double' directive, RX:                RX-Float.            (line  11)
+* 'double' directive, TIC54X:            TIC54X-Directives.   (line  62)
+* 'double' directive, VAX:               VAX-float.           (line  15)
+* 'double' directive, x86-64:            i386-Float.          (line  14)
+* 'double' directive, XGATE:             XGATE-Float.         (line  13)
+* doublequote ('\"'):                    Strings.             (line  43)
+* 'drlist' directive, TIC54X:            TIC54X-Directives.   (line  71)
+* 'drnolist' directive, TIC54X:          TIC54X-Directives.   (line  71)
+* 'dual' directive, i860:                Directives-i860.     (line   6)
+* 'dword' directive, Nios II:            Nios II Directives.  (line  16)
+* 'EB' command line option, Nios II:     Nios II Options.     (line  22)
+* 'ecr' register, V850:                  V850-Regs.           (line  78)
 * eight-byte integer:                    Quad.                (line   9)
-* eipc register, V850:                   V850-Regs.           (line 101)
-* eipsw register, V850:                  V850-Regs.           (line 104)
-* eject directive:                       Eject.               (line   6)
-* EL command line option, Nios II:       Nios II Options.     (line  26)
+* 'eipc' register, V850:                 V850-Regs.           (line  70)
+* 'eipsw' register, V850:                V850-Regs.           (line  72)
+* 'eject' directive:                     Eject.               (line   6)
+* 'EL' command line option, Nios II:     Nios II Options.     (line  25)
 * ELF symbol type:                       Type.                (line  22)
-* else directive:                        Else.                (line   6)
-* elseif directive:                      Elseif.              (line   6)
+* 'else' directive:                      Else.                (line   6)
+* 'elseif' directive:                    Elseif.              (line   6)
 * empty expressions:                     Empty Exprs.         (line   6)
-* emsg directive, TIC54X:                TIC54X-Directives.   (line  77)
-* emulation:                             Overview.            (line 843)
-* encoding options, i386:                i386-Mnemonics.      (line  32)
-* encoding options, x86-64:              i386-Mnemonics.      (line  32)
-* end directive:                         End.                 (line   6)
-* enddual directive, i860:               Directives-i860.     (line  11)
-* endef directive:                       Endef.               (line   6)
-* endfunc directive:                     Endfunc.             (line   6)
-* endianness, MIPS:                      Overview.            (line 727)
-* endianness, PJ:                        Overview.            (line 630)
-* endif directive:                       Endif.               (line   6)
-* endloop directive, TIC54X:             TIC54X-Directives.   (line 143)
-* endm directive:                        Macro.               (line 138)
-* endm directive, TIC54X:                TIC54X-Directives.   (line 153)
-* endstruct directive, TIC54X:           TIC54X-Directives.   (line 216)
-* endunion directive, TIC54X:            TIC54X-Directives.   (line 250)
+* 'emsg' directive, TIC54X:              TIC54X-Directives.   (line  75)
+* emulation:                             Overview.            (line 856)
+* encoding options, i386:                i386-Mnemonics.      (line  31)
+* encoding options, x86-64:              i386-Mnemonics.      (line  31)
+* 'end' directive:                       End.                 (line   6)
+* 'enddual' directive, i860:             Directives-i860.     (line  11)
+* 'endef' directive:                     Endef.               (line   6)
+* 'endfunc' directive:                   Endfunc.             (line   6)
+* endianness, MIPS:                      Overview.            (line 720)
+* endianness, PJ:                        Overview.            (line 627)
+* 'endif' directive:                     Endif.               (line   6)
+* 'endloop' directive, TIC54X:           TIC54X-Directives.   (line 141)
+* 'endm' directive:                      Macro.               (line 137)
+* 'endm' directive, TIC54X:              TIC54X-Directives.   (line 151)
+* 'endstruct' directive, TIC54X:         TIC54X-Directives.   (line 214)
+* 'endunion' directive, TIC54X:          TIC54X-Directives.   (line 248)
 * environment settings, TIC54X:          TIC54X-Env.          (line   6)
 * EOF, newline must precede:             Statements.          (line  14)
-* ep register, V850:                     V850-Regs.           (line  95)
+* 'ep' register, V850:                   V850-Regs.           (line  66)
 * Epiphany line comment character:       Epiphany-Chars.      (line   6)
 * Epiphany line separator:               Epiphany-Chars.      (line  14)
 * Epiphany options:                      Epiphany Options.    (line   6)
 * Epiphany support:                      Epiphany-Dependent.  (line   6)
-* equ directive:                         Equ.                 (line   6)
-* equ directive, TIC54X:                 TIC54X-Directives.   (line 191)
-* equiv directive:                       Equiv.               (line   6)
-* eqv directive:                         Eqv.                 (line   6)
-* err directive:                         Err.                 (line   6)
+* 'equ' directive:                       Equ.                 (line   6)
+* 'equ' directive, TIC54X:               TIC54X-Directives.   (line 189)
+* 'equiv' directive:                     Equiv.               (line   6)
+* 'eqv' directive:                       Eqv.                 (line   6)
+* 'err' directive:                       Err.                 (line   6)
 * error directive:                       Error.               (line   6)
 * error messages:                        Errors.              (line   6)
 * error on valid input:                  Bug Criteria.        (line  12)
@@ -23496,61 +23307,61 @@ AS Index
 * ESA/390 floating point (IEEE):         ESA/390 Floating Point.
                                                               (line   6)
 * ESA/390 support:                       ESA/390-Dependent.   (line   6)
-* ESA/390 Syntax:                        ESA/390 Options.     (line   8)
+* ESA/390 Syntax:                        ESA/390 Options.     (line   7)
 * ESA/390-only directives:               ESA/390 Directives.  (line  12)
 * escape codes, character:               Strings.             (line  15)
-* eval directive, TIC54X:                TIC54X-Directives.   (line  24)
-* even:                                  Z8000 Directives.    (line  58)
-* even directive, M680x0:                M68K-Directives.     (line  15)
-* even directive, TIC54X:                TIC54X-Directives.   (line   6)
-* exitm directive:                       Macro.               (line 141)
+* 'eval' directive, TIC54X:              TIC54X-Directives.   (line  22)
+* even:                                  Z8000 Directives.    (line  57)
+* 'even' directive, M680x0:              M68K-Directives.     (line  15)
+* 'even' directive, TIC54X:              TIC54X-Directives.   (line   6)
+* 'exitm' directive:                     Macro.               (line 140)
 * expr (internal section):               As Sections.         (line  17)
 * expression arguments:                  Arguments.           (line   6)
 * expressions:                           Expressions.         (line   6)
-* expressions, comparison:               Infix Ops.           (line  55)
+* expressions, comparison:               Infix Ops.           (line  56)
 * expressions, empty:                    Empty Exprs.         (line   6)
 * expressions, integer:                  Integer Exprs.       (line   6)
-* extAuxRegister directive, ARC:         ARC Directives.      (line  18)
-* extCondCode directive, ARC:            ARC Directives.      (line  41)
-* extCoreRegister directive, ARC:        ARC Directives.      (line  53)
-* extend directive M680x0:               M68K-Float.          (line  17)
-* extend directive M68HC11:              M68HC11-Float.       (line  17)
-* extend directive XGATE:                XGATE-Float.         (line  16)
-* extended directive, i960:              Directives-i960.     (line  13)
-* extern directive:                      Extern.              (line   6)
-* extInstruction directive, ARC:         ARC Directives.      (line  78)
-* fail directive:                        Fail.                (line   6)
-* far_mode directive, TIC54X:            TIC54X-Directives.   (line  82)
-* faster processing (-f):                f.                   (line   6)
+* 'extAuxRegister' directive, ARC:       ARC Directives.      (line  18)
+* 'extCondCode' directive, ARC:          ARC Directives.      (line  38)
+* 'extCoreRegister' directive, ARC:      ARC Directives.      (line  50)
+* 'extend' directive M680x0:             M68K-Float.          (line  17)
+* 'extend' directive M68HC11:            M68HC11-Float.       (line  17)
+* 'extend' directive XGATE:              XGATE-Float.         (line  16)
+* 'extended' directive, i960:            Directives-i960.     (line  13)
+* 'extern' directive:                    Extern.              (line   6)
+* 'extInstruction' directive, ARC:       ARC Directives.      (line  72)
+* 'fail' directive:                      Fail.                (line   6)
+* 'far_mode' directive, TIC54X:          TIC54X-Directives.   (line  80)
+* faster processing ('-f'):              f.                   (line   6)
 * fatal signal:                          Bug Criteria.        (line   9)
-* fclist directive, TIC54X:              TIC54X-Directives.   (line  87)
-* fcnolist directive, TIC54X:            TIC54X-Directives.   (line  87)
-* fepc register, V850:                   V850-Regs.           (line 107)
-* fepsw register, V850:                  V850-Regs.           (line 110)
-* ffloat directive, VAX:                 VAX-directives.      (line  14)
-* field directive, TIC54X:               TIC54X-Directives.   (line  91)
-* file directive:                        File.                (line   6)
-* file directive, MSP 430:               MSP430 Directives.   (line   6)
+* 'fclist' directive, TIC54X:            TIC54X-Directives.   (line  85)
+* 'fcnolist' directive, TIC54X:          TIC54X-Directives.   (line  85)
+* 'fepc' register, V850:                 V850-Regs.           (line  74)
+* 'fepsw' register, V850:                V850-Regs.           (line  76)
+* 'ffloat' directive, VAX:               VAX-directives.      (line  13)
+* 'field' directive, TIC54X:             TIC54X-Directives.   (line  89)
+* 'file' directive:                      File.                (line   6)
+* 'file' directive, MSP 430:             MSP430 Directives.   (line   6)
 * file name, logical:                    File.                (line  13)
 * files, including:                      Include.             (line   6)
 * files, input:                          Input Files.         (line   6)
-* fill directive:                        Fill.                (line   6)
-* filling memory <1>:                    Space.               (line   6)
+* 'fill' directive:                      Fill.                (line   6)
 * filling memory:                        Skip.                (line   6)
+* filling memory <1>:                    Space.               (line   6)
 * FLIX syntax:                           Xtensa Syntax.       (line   6)
-* float directive:                       Float.               (line   6)
-* float directive, i386:                 i386-Float.          (line  14)
-* float directive, M680x0:               M68K-Float.          (line  11)
-* float directive, M68HC11:              M68HC11-Float.       (line  11)
-* float directive, RX:                   RX-Float.            (line   8)
-* float directive, TIC54X:               TIC54X-Directives.   (line  64)
-* float directive, VAX:                  VAX-float.           (line  15)
-* float directive, x86-64:               i386-Float.          (line  14)
-* float directive, XGATE:                XGATE-Float.         (line  10)
+* 'float' directive:                     Float.               (line   6)
+* 'float' directive, i386:               i386-Float.          (line  14)
+* 'float' directive, M680x0:             M68K-Float.          (line  11)
+* 'float' directive, M68HC11:            M68HC11-Float.       (line  11)
+* 'float' directive, RX:                 RX-Float.            (line   8)
+* 'float' directive, TIC54X:             TIC54X-Directives.   (line  62)
+* 'float' directive, VAX:                VAX-float.           (line  15)
+* 'float' directive, x86-64:             i386-Float.          (line  14)
+* 'float' directive, XGATE:              XGATE-Float.         (line  10)
 * floating point numbers:                Flonums.             (line   6)
 * floating point numbers (double):       Double.              (line   6)
-* floating point numbers (single) <1>:   Single.              (line   6)
 * floating point numbers (single):       Float.               (line   6)
+* floating point numbers (single) <1>:   Single.              (line   6)
 * floating point, AArch64 (IEEE):        AArch64 Floating Point.
                                                               (line   6)
 * floating point, Alpha (IEEE):          Alpha Floating Point.
@@ -23582,21 +23393,21 @@ AS Index
 * flonums:                               Flonums.             (line   6)
 * format of error messages:              Errors.              (line  24)
 * format of warning messages:            Errors.              (line  12)
-* formfeed (\f):                         Strings.             (line  18)
-* func directive:                        Func.                (line   6)
+* formfeed ('\f'):                       Strings.             (line  18)
+* 'func' directive:                      Func.                (line   6)
 * functions, in expressions:             Operators.           (line   6)
-* gbr960, i960 postprocessor:            Options-i960.        (line  40)
-* gfloat directive, VAX:                 VAX-directives.      (line  18)
+* 'gbr960', i960 postprocessor:          Options-i960.        (line  40)
+* 'gfloat' directive, VAX:               VAX-directives.      (line  17)
 * global:                                Z8000 Directives.    (line  21)
-* global directive:                      Global.              (line   6)
-* global directive, TIC54X:              TIC54X-Directives.   (line 103)
-* got directive, Nios II:                Nios II Relocations. (line  38)
-* gotoff directive, Nios II:             Nios II Relocations. (line  38)
-* gotoff_hiadj directive, Nios II:       Nios II Relocations. (line  38)
-* gotoff_lo directive, Nios II:          Nios II Relocations. (line  38)
-* gp register, MIPS:                     MIPS Object.         (line  11)
-* gp register, V850:                     V850-Regs.           (line  17)
-* gprel directive, Nios II:              Nios II Relocations. (line  26)
+* 'global' directive:                    Global.              (line   6)
+* 'global' directive, TIC54X:            TIC54X-Directives.   (line 101)
+* 'got' directive, Nios II:              Nios II Relocations. (line  38)
+* 'gotoff' directive, Nios II:           Nios II Relocations. (line  38)
+* 'gotoff_hiadj' directive, Nios II:     Nios II Relocations. (line  38)
+* 'gotoff_lo' directive, Nios II:        Nios II Relocations. (line  38)
+* 'gp' register, MIPS:                   MIPS Small Data.     (line   6)
+* 'gp' register, V850:                   V850-Regs.           (line  14)
+* 'gprel' directive, Nios II:            Nios II Relocations. (line  26)
 * grouping data:                         Sub-Sections.        (line   6)
 * H8/300 addressing modes:               H8/300-Addressing.   (line   6)
 * H8/300 floating point (IEEE):          H8/300 Floating Point.
@@ -23607,53 +23418,53 @@ AS Index
 * H8/300 opcode summary:                 H8/300 Opcodes.      (line   6)
 * H8/300 options:                        H8/300 Options.      (line   6)
 * H8/300 registers:                      H8/300-Regs.         (line   6)
-* H8/300 size suffixes:                  H8/300 Opcodes.      (line 163)
+* H8/300 size suffixes:                  H8/300 Opcodes.      (line 160)
 * H8/300 support:                        H8/300-Dependent.    (line   6)
 * H8/300H, assembling for:               H8/300 Directives.   (line   8)
-* half directive, ARC:                   ARC Directives.      (line 153)
-* half directive, Nios II:               Nios II Directives.  (line  10)
-* half directive, SPARC:                 Sparc-Directives.    (line  17)
-* half directive, TIC54X:                TIC54X-Directives.   (line 111)
-* hex character code (\XD...):           Strings.             (line  36)
+* 'half' directive, ARC:                 ARC Directives.      (line 144)
+* 'half' directive, Nios II:             Nios II Directives.  (line  10)
+* 'half' directive, SPARC:               Sparc-Directives.    (line  17)
+* 'half' directive, TIC54X:              TIC54X-Directives.   (line 109)
+* hex character code ('\XD...'):         Strings.             (line  36)
 * hexadecimal integers:                  Integers.            (line  15)
 * hexadecimal prefix, Z80:               Z80-Chars.           (line  15)
-* hfloat directive, VAX:                 VAX-directives.      (line  22)
-* hi directive, Nios II:                 Nios II Relocations. (line  20)
-* hi pseudo-op, V850:                    V850 Opcodes.        (line  33)
-* hi0 pseudo-op, V850:                   V850 Opcodes.        (line  10)
-* hiadj directive, Nios II:              Nios II Relocations. (line   6)
-* hidden directive:                      Hidden.              (line   6)
-* high directive, M32R:                  M32R-Directives.     (line  18)
-* hilo pseudo-op, V850:                  V850 Opcodes.        (line  55)
+* 'hfloat' directive, VAX:               VAX-directives.      (line  21)
+* 'hi' directive, Nios II:               Nios II Relocations. (line  20)
+* 'hi' pseudo-op, V850:                  V850 Opcodes.        (line  33)
+* 'hi0' pseudo-op, V850:                 V850 Opcodes.        (line  10)
+* 'hiadj' directive, Nios II:            Nios II Relocations. (line   6)
+* 'hidden' directive:                    Hidden.              (line   6)
+* 'high' directive, M32R:                M32R-Directives.     (line  18)
+* 'hilo' pseudo-op, V850:                V850 Opcodes.        (line  55)
 * HPPA directives not supported:         HPPA Directives.     (line  11)
 * HPPA floating point (IEEE):            HPPA Floating Point. (line   6)
-* HPPA Syntax:                           HPPA Options.        (line   8)
+* HPPA Syntax:                           HPPA Options.        (line   7)
 * HPPA-only directives:                  HPPA Directives.     (line  24)
-* hword directive:                       hword.               (line   6)
+* 'hword' directive:                     hword.               (line   6)
 * i370 support:                          ESA/390-Dependent.   (line   6)
 * i386 16-bit code:                      i386-16bit.          (line   6)
 * i386 arch directive:                   i386-Arch.           (line   6)
 * i386 att_syntax pseudo op:             i386-Variations.     (line   6)
-* i386 conversion instructions:          i386-Mnemonics.      (line  37)
+* i386 conversion instructions:          i386-Mnemonics.      (line  36)
 * i386 floating point:                   i386-Float.          (line   6)
 * i386 immediate operands:               i386-Variations.     (line  15)
 * i386 instruction naming:               i386-Mnemonics.      (line   6)
 * i386 instruction prefixes:             i386-Prefixes.       (line   6)
 * i386 intel_syntax pseudo op:           i386-Variations.     (line   6)
 * i386 jump optimization:                i386-Jumps.          (line   6)
-* i386 jump, call, return:               i386-Variations.     (line  41)
+* i386 jump, call, return:               i386-Variations.     (line  40)
 * i386 jump/call operands:               i386-Variations.     (line  15)
 * i386 line comment character:           i386-Chars.          (line   6)
 * i386 line separator:                   i386-Chars.          (line  18)
 * i386 memory references:                i386-Memory.         (line   6)
-* i386 mnemonic compatibility:           i386-Mnemonics.      (line  62)
-* i386 mul, imul instructions:           i386-Notes.          (line   6)
+* i386 mnemonic compatibility:           i386-Mnemonics.      (line  61)
+* i386 'mul', 'imul' instructions:       i386-Notes.          (line   6)
 * i386 options:                          i386-Options.        (line   6)
 * i386 register operands:                i386-Variations.     (line  15)
 * i386 registers:                        i386-Regs.           (line   6)
-* i386 sections:                         i386-Variations.     (line  47)
-* i386 size suffixes:                    i386-Variations.     (line  29)
-* i386 source, destination operands:     i386-Variations.     (line  22)
+* i386 sections:                         i386-Variations.     (line  46)
+* i386 size suffixes:                    i386-Variations.     (line  28)
+* i386 source, destination operands:     i386-Variations.     (line  21)
 * i386 support:                          i386-Dependent.      (line   6)
 * i386 syntax compatibility:             i386-Variations.     (line   6)
 * i80386 support:                        i386-Dependent.      (line   6)
@@ -23664,7 +23475,7 @@ AS Index
 * i860 support:                          i860-Dependent.      (line   6)
 * i960 architecture options:             Options-i960.        (line   6)
 * i960 branch recording:                 Options-i960.        (line  22)
-* i960 callj pseudo-opcode:              callj-i960.          (line   6)
+* i960 'callj' pseudo-opcode:            callj-i960.          (line   6)
 * i960 compare and jump expansions:      Compare-and-branch-i960.
                                                               (line  13)
 * i960 compare/branch instructions:      Compare-and-branch-i960.
@@ -23683,26 +23494,26 @@ AS Index
 * IA-64 registers:                       IA-64-Regs.          (line   6)
 * IA-64 relocations:                     IA-64-Relocs.        (line   6)
 * IA-64 support:                         IA-64-Dependent.     (line   6)
-* IA-64 Syntax:                          IA-64 Options.       (line  87)
-* ident directive:                       Ident.               (line   6)
+* IA-64 Syntax:                          IA-64 Options.       (line  85)
+* 'ident' directive:                     Ident.               (line   6)
 * identifiers, ARM:                      ARM-Chars.           (line  19)
 * identifiers, MSP 430:                  MSP430-Chars.        (line  17)
-* if directive:                          If.                  (line   6)
-* ifb directive:                         If.                  (line  21)
-* ifc directive:                         If.                  (line  25)
-* ifdef directive:                       If.                  (line  16)
-* ifeq directive:                        If.                  (line  33)
-* ifeqs directive:                       If.                  (line  36)
-* ifge directive:                        If.                  (line  40)
-* ifgt directive:                        If.                  (line  44)
-* ifle directive:                        If.                  (line  48)
-* iflt directive:                        If.                  (line  52)
-* ifnb directive:                        If.                  (line  56)
-* ifnc directive:                        If.                  (line  61)
-* ifndef directive:                      If.                  (line  65)
-* ifne directive:                        If.                  (line  72)
-* ifnes directive:                       If.                  (line  76)
-* ifnotdef directive:                    If.                  (line  65)
+* 'if' directive:                        If.                  (line   6)
+* 'ifb' directive:                       If.                  (line  21)
+* 'ifc' directive:                       If.                  (line  25)
+* 'ifdef' directive:                     If.                  (line  16)
+* 'ifeq' directive:                      If.                  (line  33)
+* 'ifeqs' directive:                     If.                  (line  36)
+* 'ifge' directive:                      If.                  (line  40)
+* 'ifgt' directive:                      If.                  (line  44)
+* 'ifle' directive:                      If.                  (line  48)
+* 'iflt' directive:                      If.                  (line  52)
+* 'ifnb' directive:                      If.                  (line  56)
+* 'ifnc' directive:                      If.                  (line  61)
+* 'ifndef' directive:                    If.                  (line  65)
+* 'ifne' directive:                      If.                  (line  72)
+* 'ifnes' directive:                     If.                  (line  76)
+* 'ifnotdef' directive:                  If.                  (line  65)
 * immediate character, AArch64:          AArch64-Chars.       (line  13)
 * immediate character, ARM:              ARM-Chars.           (line  17)
 * immediate character, M680x0:           M68K-Chars.          (line  13)
@@ -23711,11 +23522,11 @@ AS Index
                                                               (line   6)
 * immediate operands, i386:              i386-Variations.     (line  15)
 * immediate operands, x86-64:            i386-Variations.     (line  15)
-* imul instruction, i386:                i386-Notes.          (line   6)
-* imul instruction, x86-64:              i386-Notes.          (line   6)
-* incbin directive:                      Incbin.              (line   6)
-* include directive:                     Include.             (line   6)
-* include directive search path:         I.                   (line   6)
+* 'imul' instruction, i386:              i386-Notes.          (line   6)
+* 'imul' instruction, x86-64:            i386-Notes.          (line   6)
+* 'incbin' directive:                    Incbin.              (line   6)
+* 'include' directive:                   Include.             (line   6)
+* 'include' directive search path:       I.                   (line   6)
 * indirect character, VAX:               VAX-operands.        (line   9)
 * infix operators:                       Infix Ops.           (line   6)
 * inhibiting interrupts, i386:           i386-Prefixes.       (line  36)
@@ -23737,7 +23548,7 @@ AS Index
 * instruction prefixes, i386:            i386-Prefixes.       (line   6)
 * instruction set, M680x0:               M68K-opcodes.        (line   6)
 * instruction set, M68HC11:              M68HC11-opcodes.     (line   6)
-* instruction set, XGATE:                XGATE-opcodes.       (line   6)
+* instruction set, XGATE:                XGATE-opcodes.       (line   5)
 * instruction summary, AVR:              AVR Opcodes.         (line   6)
 * instruction summary, D10V:             D10V-Opcodes.        (line   6)
 * instruction summary, D30V:             D30V-Opcodes.        (line   6)
@@ -23748,11 +23559,11 @@ AS Index
 * instruction summary, Z8000:            Z8000 Opcodes.       (line   6)
 * instruction syntax, s390:              s390 Syntax.         (line   6)
 * instructions and directives:           Statements.          (line  20)
-* int directive:                         Int.                 (line   6)
-* int directive, H8/300:                 H8/300 Directives.   (line   6)
-* int directive, i386:                   i386-Float.          (line  21)
-* int directive, TIC54X:                 TIC54X-Directives.   (line 111)
-* int directive, x86-64:                 i386-Float.          (line  21)
+* 'int' directive:                       Int.                 (line   6)
+* 'int' directive, H8/300:               H8/300 Directives.   (line   6)
+* 'int' directive, i386:                 i386-Float.          (line  21)
+* 'int' directive, TIC54X:               TIC54X-Directives.   (line 109)
+* 'int' directive, x86-64:               i386-Float.          (line  21)
 * integer expressions:                   Integer Exprs.       (line   6)
 * integer, 16-byte:                      Octa.                (line   6)
 * integer, 8-byte:                       Quad.                (line   9)
@@ -23767,48 +23578,49 @@ AS Index
 * intel_syntax pseudo op, i386:          i386-Variations.     (line   6)
 * intel_syntax pseudo op, x86-64:        i386-Variations.     (line   6)
 * internal assembler sections:           As Sections.         (line   6)
-* internal directive:                    Internal.            (line   6)
+* 'internal' directive:                  Internal.            (line   6)
 * invalid input:                         Bug Criteria.        (line  14)
 * invocation summary:                    Overview.            (line   6)
 * IP2K architecture options:             IP2K-Opts.           (line   9)
+* IP2K architecture options <1>:         IP2K-Opts.           (line  14)
 * IP2K line comment character:           IP2K-Chars.          (line   6)
 * IP2K line separator:                   IP2K-Chars.          (line  14)
 * IP2K options:                          IP2K-Opts.           (line   6)
 * IP2K support:                          IP2K-Dependent.      (line   6)
-* irp directive:                         Irp.                 (line   6)
-* irpc directive:                        Irpc.                (line   6)
+* 'irp' directive:                       Irp.                 (line   6)
+* 'irpc' directive:                      Irpc.                (line   6)
 * ISA options, SH64:                     SH64 Options.        (line   6)
 * joining text and data sections:        R.                   (line   6)
-* jump instructions, i386:               i386-Mnemonics.      (line  56)
-* jump instructions, x86-64:             i386-Mnemonics.      (line  56)
+* jump instructions, i386:               i386-Mnemonics.      (line  55)
+* jump instructions, x86-64:             i386-Mnemonics.      (line  55)
 * jump optimization, i386:               i386-Jumps.          (line   6)
 * jump optimization, x86-64:             i386-Jumps.          (line   6)
 * jump/call operands, i386:              i386-Variations.     (line  15)
 * jump/call operands, x86-64:            i386-Variations.     (line  15)
-* L16SI instructions, relaxation:        Xtensa Immediate Relaxation.
+* 'L16SI' instructions, relaxation:      Xtensa Immediate Relaxation.
                                                               (line  23)
-* L16UI instructions, relaxation:        Xtensa Immediate Relaxation.
+* 'L16UI' instructions, relaxation:      Xtensa Immediate Relaxation.
                                                               (line  23)
-* L32I instructions, relaxation:         Xtensa Immediate Relaxation.
+* 'L32I' instructions, relaxation:       Xtensa Immediate Relaxation.
                                                               (line  23)
-* L8UI instructions, relaxation:         Xtensa Immediate Relaxation.
+* 'L8UI' instructions, relaxation:       Xtensa Immediate Relaxation.
                                                               (line  23)
-* label (:):                             Statements.          (line  31)
-* label directive, TIC54X:               TIC54X-Directives.   (line 123)
+* label (':'):                           Statements.          (line  31)
+* 'label' directive, TIC54X:             TIC54X-Directives.   (line 121)
 * labels:                                Labels.              (line   6)
-* lcomm directive:                       Lcomm.               (line   6)
-* lcomm directive, COFF:                 i386-Directives.     (line   6)
+* 'lcomm' directive:                     Lcomm.               (line   6)
+* 'lcomm' directive, COFF:               i386-Directives.     (line   6)
 * ld:                                    Object.              (line  15)
-* ldouble directive M680x0:              M68K-Float.          (line  17)
-* ldouble directive M68HC11:             M68HC11-Float.       (line  17)
-* ldouble directive XGATE:               XGATE-Float.         (line  16)
-* ldouble directive, TIC54X:             TIC54X-Directives.   (line  64)
-* LDR reg,=<expr> pseudo op, AArch64:    AArch64 Opcodes.     (line   9)
-* LDR reg,=<label> pseudo op, ARM:       ARM Opcodes.         (line  15)
-* leafproc directive, i960:              Directives-i960.     (line  18)
-* length directive, TIC54X:              TIC54X-Directives.   (line 127)
+* 'ldouble' directive M680x0:            M68K-Float.          (line  17)
+* 'ldouble' directive M68HC11:           M68HC11-Float.       (line  17)
+* 'ldouble' directive XGATE:             XGATE-Float.         (line  16)
+* 'ldouble' directive, TIC54X:           TIC54X-Directives.   (line  62)
+* 'LDR reg,=<expr>' pseudo op, AArch64:  AArch64 Opcodes.     (line   9)
+* 'LDR reg,=<label>' pseudo op, ARM:     ARM Opcodes.         (line  15)
+* 'leafproc' directive, i960:            Directives-i960.     (line  18)
+* 'length' directive, TIC54X:            TIC54X-Directives.   (line 125)
 * length of symbols:                     Symbol Intro.        (line  14)
-* lflags directive (ignored):            Lflags.              (line   6)
+* 'lflags' directive (ignored):          Lflags.              (line   6)
 * line comment character:                Comments.            (line  19)
 * line comment character, AArch64:       AArch64-Chars.       (line   6)
 * line comment character, Alpha:         Alpha-Chars.         (line   6)
@@ -23854,8 +23666,8 @@ AS Index
 * line comment character, Z8000:         Z8000-Chars.         (line   6)
 * line comment characters, CRIS:         CRIS-Chars.          (line   6)
 * line comment characters, MMIX:         MMIX-Chars.          (line   6)
-* line directive:                        Line.                (line   6)
-* line directive, MSP 430:               MSP430 Directives.   (line  14)
+* 'line' directive:                      Line.                (line   6)
+* 'line' directive, MSP 430:             MSP430 Directives.   (line  14)
 * line numbers, in input files:          Input Files.         (line  35)
 * line numbers, in warnings/errors:      Errors.              (line  16)
 * line separator character:              Statements.          (line   6)
@@ -23865,7 +23677,7 @@ AS Index
 * line separator, ARC:                   ARC-Chars.           (line  12)
 * line separator, ARM:                   ARM-Chars.           (line  14)
 * line separator, AVR:                   AVR-Chars.           (line  14)
-* line separator, CR16:                  CR16-Chars.          (line  13)
+* line separator, CR16:                  CR16-Chars.          (line  12)
 * line separator, Epiphany:              Epiphany-Chars.      (line  14)
 * line separator, H8/300:                H8/300-Chars.        (line   8)
 * line separator, i386:                  i386-Chars.          (line  18)
@@ -23876,7 +23688,7 @@ AS Index
 * line separator, LM32:                  LM32-Chars.          (line  12)
 * line separator, M32C:                  M32C-Chars.          (line  14)
 * line separator, M680x0:                M68K-Chars.          (line  20)
-* line separator, M68HC11:               M68HC11-Syntax.      (line  27)
+* line separator, M68HC11:               M68HC11-Syntax.      (line  26)
 * line separator, Meta:                  Meta-Chars.          (line   8)
 * line separator, MicroBlaze:            MicroBlaze-Chars.    (line  14)
 * line separator, MIPS:                  MIPS-Chars.          (line  14)
@@ -23895,16 +23707,16 @@ AS Index
 * line separator, TIC6X:                 TIC6X Syntax.        (line  13)
 * line separator, V850:                  V850-Chars.          (line  13)
 * line separator, VAX:                   VAX-Chars.           (line  14)
-* line separator, XGATE:                 XGATE-Syntax.        (line  26)
+* line separator, XGATE:                 XGATE-Syntax.        (line  25)
 * line separator, XStormy16:             XStormy16-Chars.     (line  14)
 * line separator, Z80:                   Z80-Chars.           (line  13)
 * line separator, Z8000:                 Z8000-Chars.         (line  13)
-* lines starting with #:                 Comments.            (line  33)
+* lines starting with '#':               Comments.            (line  33)
 * linker:                                Object.              (line  15)
 * linker, and assembler:                 Secs Background.     (line  10)
-* linkonce directive:                    Linkonce.            (line   6)
-* list directive:                        List.                (line   6)
-* list directive, TIC54X:                TIC54X-Directives.   (line 131)
+* 'linkonce' directive:                  Linkonce.            (line   6)
+* 'list' directive:                      List.                (line   6)
+* 'list' directive, TIC54X:              TIC54X-Directives.   (line 129)
 * listing control, turning off:          Nolist.              (line   6)
 * listing control, turning on:           List.                (line   6)
 * listing control: new page:             Eject.               (line   6)
@@ -23912,16 +23724,16 @@ AS Index
 * listing control: subtitle:             Sbttl.               (line   6)
 * listing control: title line:           Title.               (line   6)
 * listings, enabling:                    a.                   (line   6)
-* literal directive:                     Literal Directive.   (line   6)
+* 'literal' directive:                   Literal Directive.   (line   6)
 * literal pool entries, s390:            s390 Literal Pool Entries.
                                                               (line   6)
-* literal_position directive:            Literal Position Directive.
+* 'literal_position' directive:          Literal Position Directive.
                                                               (line   6)
-* literal_prefix directive:              Literal Prefix Directive.
+* 'literal_prefix' directive:            Literal Prefix Directive.
                                                               (line   6)
-* little endian output, MIPS:            Overview.            (line 730)
-* little endian output, PJ:              Overview.            (line 633)
-* little-endian output, MIPS:            MIPS Opts.           (line  13)
+* little endian output, MIPS:            Overview.            (line 723)
+* little endian output, PJ:              Overview.            (line 630)
+* little-endian output, MIPS:            MIPS Options.        (line  13)
 * little-endian output, TIC6X:           TIC6X Options.       (line  46)
 * LM32 line comment character:           LM32-Chars.          (line   6)
 * LM32 line separator:                   LM32-Chars.          (line  12)
@@ -23930,35 +23742,35 @@ AS Index
 * LM32 options (none):                   LM32 Options.        (line   6)
 * LM32 register names:                   LM32-Regs.           (line   6)
 * LM32 support:                          LM32-Dependent.      (line   6)
-* ln directive:                          Ln.                  (line   6)
-* lo directive, Nios II:                 Nios II Relocations. (line  23)
-* lo pseudo-op, V850:                    V850 Opcodes.        (line  22)
-* loc directive:                         Loc.                 (line   6)
-* loc_mark_labels directive:             Loc_mark_labels.     (line   6)
+* 'ln' directive:                        Ln.                  (line   6)
+* 'lo' directive, Nios II:               Nios II Relocations. (line  23)
+* 'lo' pseudo-op, V850:                  V850 Opcodes.        (line  22)
+* 'loc' directive:                       Loc.                 (line   6)
 * local common symbols:                  Lcomm.               (line   6)
-* local directive:                       Local.               (line   6)
+* 'local' directive:                     Local.               (line   6)
 * local labels:                          Symbol Names.        (line  40)
 * local symbol names:                    Symbol Names.        (line  27)
 * local symbols, retaining in output:    L.                   (line   6)
 * location counter:                      Dot.                 (line   6)
 * location counter, advancing:           Org.                 (line   6)
 * location counter, Z80:                 Z80-Chars.           (line  15)
+* 'loc_mark_labels' directive:           Loc_mark_labels.     (line   6)
 * logical file name:                     File.                (line  13)
 * logical line number:                   Line.                (line   6)
 * logical line numbers:                  Comments.            (line  33)
-* long directive:                        Long.                (line   6)
-* long directive, ARC:                   ARC Directives.      (line 156)
-* long directive, i386:                  i386-Float.          (line  21)
-* long directive, TIC54X:                TIC54X-Directives.   (line 135)
-* long directive, x86-64:                i386-Float.          (line  21)
-* longcall pseudo-op, V850:              V850 Opcodes.        (line 123)
-* longcalls directive:                   Longcalls Directive. (line   6)
-* longjump pseudo-op, V850:              V850 Opcodes.        (line 129)
-* loop directive, TIC54X:                TIC54X-Directives.   (line 143)
-* LOOP instructions, alignment:          Xtensa Automatic Alignment.
+* 'long' directive:                      Long.                (line   6)
+* 'long' directive, ARC:                 ARC Directives.      (line 147)
+* 'long' directive, i386:                i386-Float.          (line  21)
+* 'long' directive, TIC54X:              TIC54X-Directives.   (line 133)
+* 'long' directive, x86-64:              i386-Float.          (line  21)
+* 'longcall' pseudo-op, V850:            V850 Opcodes.        (line 122)
+* 'longcalls' directive:                 Longcalls Directive. (line   6)
+* 'longjump' pseudo-op, V850:            V850 Opcodes.        (line 128)
+* 'loop' directive, TIC54X:              TIC54X-Directives.   (line 141)
+* 'LOOP' instructions, alignment:        Xtensa Automatic Alignment.
                                                               (line   6)
-* low directive, M32R:                   M32R-Directives.     (line   9)
-* lp register, V850:                     V850-Regs.           (line  98)
+* 'low' directive, M32R:                 M32R-Directives.     (line   9)
+* 'lp' register, V850:                   V850-Regs.           (line  68)
 * lval:                                  Z8000 Directives.    (line  27)
 * LWP, i386:                             i386-LWP.            (line   6)
 * LWP, x86-64:                           i386-LWP.            (line   6)
@@ -23970,12 +23782,14 @@ AS Index
 * M32C options:                          M32C-Opts.           (line   6)
 * M32C support:                          M32C-Dependent.      (line   6)
 * M32R architecture options:             M32R-Opts.           (line   9)
+* M32R architecture options <1>:         M32R-Opts.           (line  17)
+* M32R architecture options <2>:         M32R-Opts.           (line  21)
 * M32R directives:                       M32R-Directives.     (line   6)
 * M32R options:                          M32R-Opts.           (line   6)
 * M32R support:                          M32R-Dependent.      (line   6)
 * M32R warnings:                         M32R-Warnings.       (line   6)
 * M680x0 addressing modes:               M68K-Syntax.         (line  21)
-* M680x0 architecture options:           M68K-Opts.           (line  98)
+* M680x0 architecture options:           M68K-Opts.           (line  99)
 * M680x0 branch improvement:             M68K-Branch.         (line   6)
 * M680x0 directives:                     M68K-Directives.     (line   6)
 * M680x0 floating point:                 M68K-Float.          (line   6)
@@ -23988,7 +23802,7 @@ AS Index
 * M680x0 size modifiers:                 M68K-Syntax.         (line   8)
 * M680x0 support:                        M68K-Dependent.      (line   6)
 * M680x0 syntax:                         M68K-Syntax.         (line   8)
-* M68HC11 addressing modes:              M68HC11-Syntax.      (line  30)
+* M68HC11 addressing modes:              M68HC11-Syntax.      (line  29)
 * M68HC11 and M68HC12 support:           M68HC11-Dependent.   (line   6)
 * M68HC11 assembler directive .far:      M68HC11-Directives.  (line  20)
 * M68HC11 assembler directive .interrupt: M68HC11-Directives. (line  26)
@@ -23999,7 +23813,7 @@ AS Index
 * M68HC11 branch improvement:            M68HC11-Branch.      (line   6)
 * M68HC11 floating point:                M68HC11-Float.       (line   6)
 * M68HC11 line comment character:        M68HC11-Syntax.      (line  17)
-* M68HC11 line separator:                M68HC11-Syntax.      (line  27)
+* M68HC11 line separator:                M68HC11-Syntax.      (line  26)
 * M68HC11 modifiers:                     M68HC11-Modifiers.   (line   6)
 * M68HC11 opcodes:                       M68HC11-opcodes.     (line   6)
 * M68HC11 options:                       M68HC11-Opts.        (line   6)
@@ -24032,10 +23846,10 @@ AS Index
 * machine instructions (not covered):    Manual.              (line  14)
 * machine relocations, Nios II:          Nios II Relocations. (line   6)
 * machine-independent syntax:            Syntax.              (line   6)
-* macro directive:                       Macro.               (line  28)
-* macro directive, TIC54X:               TIC54X-Directives.   (line 153)
+* 'macro' directive:                     Macro.               (line  28)
+* 'macro' directive, TIC54X:             TIC54X-Directives.   (line 151)
 * macros:                                Macro.               (line   6)
-* macros, count executed:                Macro.               (line 143)
+* macros, count executed:                Macro.               (line 142)
 * Macros, MSP 430:                       MSP430-Macros.       (line   6)
 * macros, TIC54X:                        TIC54X-Macros.       (line   6)
 * make rules:                            MD.                  (line   6)
@@ -24060,72 +23874,74 @@ AS Index
 * MicroBlaze line comment character:     MicroBlaze-Chars.    (line   6)
 * MicroBlaze line separator:             MicroBlaze-Chars.    (line  14)
 * MicroBlaze support:                    MicroBlaze-Dependent.
-                                                              (line  13)
-* minus, permitted arguments:            Infix Ops.           (line  49)
-* MIPS architecture options:             MIPS Opts.           (line  29)
-* MIPS big-endian output:                MIPS Opts.           (line  13)
+                                                              (line  12)
+* minus, permitted arguments:            Infix Ops.           (line  50)
+* MIPS 32-bit microMIPS instruction generation override: MIPS assembly options.
+                                                              (line   6)
+* MIPS architecture options:             MIPS Options.        (line  29)
+* MIPS big-endian output:                MIPS Options.        (line  13)
 * MIPS CPU override:                     MIPS ISA.            (line  18)
-* MIPS debugging directives:             MIPS Stabs.          (line   6)
-* MIPS DSP Release 1 instruction generation override: MIPS ASE instruction generation overrides.
+* MIPS DSP Release 1 instruction generation override: MIPS ASE Instruction Generation Overrides.
                                                               (line  21)
-* MIPS DSP Release 2 instruction generation override: MIPS ASE instruction generation overrides.
+* MIPS DSP Release 2 instruction generation override: MIPS ASE Instruction Generation Overrides.
                                                               (line  26)
-* MIPS ECOFF sections:                   MIPS Object.         (line   6)
-* MIPS endianness:                       Overview.            (line 727)
-* MIPS ISA:                              Overview.            (line 733)
+* MIPS endianness:                       Overview.            (line 720)
+* MIPS IEEE 754 NaN data encoding selection: MIPS NaN Encodings.
+                                                              (line   6)
+* MIPS ISA:                              Overview.            (line 726)
 * MIPS ISA override:                     MIPS ISA.            (line   6)
 * MIPS line comment character:           MIPS-Chars.          (line   6)
 * MIPS line separator:                   MIPS-Chars.          (line  14)
-* MIPS little-endian output:             MIPS Opts.           (line  13)
-* MIPS MCU instruction generation override: MIPS ASE instruction generation overrides.
-                                                              (line  37)
-* MIPS MDMX instruction generation override: MIPS ASE instruction generation overrides.
+* MIPS little-endian output:             MIPS Options.        (line  13)
+* MIPS MCU instruction generation override: MIPS ASE Instruction Generation Overrides.
+                                                              (line  36)
+* MIPS MDMX instruction generation override: MIPS ASE Instruction Generation Overrides.
                                                               (line  16)
-* MIPS MIPS-3D instruction generation override: MIPS ASE instruction generation overrides.
+* MIPS MIPS-3D instruction generation override: MIPS ASE Instruction Generation Overrides.
                                                               (line   6)
-* MIPS MT instruction generation override: MIPS ASE instruction generation overrides.
-                                                              (line  32)
-* MIPS option stack:                     MIPS option stack.   (line   6)
+* MIPS MT instruction generation override: MIPS ASE Instruction Generation Overrides.
+                                                              (line  31)
+* MIPS option stack:                     MIPS Option Stack.   (line   6)
 * MIPS processor:                        MIPS-Dependent.      (line   6)
 * MIT:                                   M68K-Syntax.         (line   6)
-* mlib directive, TIC54X:                TIC54X-Directives.   (line 159)
-* mlist directive, TIC54X:               TIC54X-Directives.   (line 164)
-* MMIX assembler directive BSPEC:        MMIX-Pseudos.        (line 131)
-* MMIX assembler directive BYTE:         MMIX-Pseudos.        (line  97)
-* MMIX assembler directive ESPEC:        MMIX-Pseudos.        (line 131)
-* MMIX assembler directive GREG:         MMIX-Pseudos.        (line  50)
-* MMIX assembler directive IS:           MMIX-Pseudos.        (line  42)
+* 'mlib' directive, TIC54X:              TIC54X-Directives.   (line 157)
+* 'mlist' directive, TIC54X:             TIC54X-Directives.   (line 162)
+* MMIX assembler directive BSPEC:        MMIX-Pseudos.        (line 137)
+* MMIX assembler directive BYTE:         MMIX-Pseudos.        (line 101)
+* MMIX assembler directive ESPEC:        MMIX-Pseudos.        (line 137)
+* MMIX assembler directive GREG:         MMIX-Pseudos.        (line  53)
+* MMIX assembler directive IS:           MMIX-Pseudos.        (line  44)
 * MMIX assembler directive LOC:          MMIX-Pseudos.        (line   7)
-* MMIX assembler directive LOCAL:        MMIX-Pseudos.        (line  28)
-* MMIX assembler directive OCTA:         MMIX-Pseudos.        (line 108)
-* MMIX assembler directive PREFIX:       MMIX-Pseudos.        (line 120)
-* MMIX assembler directive TETRA:        MMIX-Pseudos.        (line 108)
-* MMIX assembler directive WYDE:         MMIX-Pseudos.        (line 108)
+* MMIX assembler directive LOCAL:        MMIX-Pseudos.        (line  29)
+* MMIX assembler directive OCTA:         MMIX-Pseudos.        (line 113)
+* MMIX assembler directive PREFIX:       MMIX-Pseudos.        (line 125)
+* MMIX assembler directive TETRA:        MMIX-Pseudos.        (line 113)
+* MMIX assembler directive WYDE:         MMIX-Pseudos.        (line 113)
 * MMIX assembler directives:             MMIX-Pseudos.        (line   6)
 * MMIX line comment characters:          MMIX-Chars.          (line   6)
 * MMIX options:                          MMIX-Opts.           (line   6)
-* MMIX pseudo-op BSPEC:                  MMIX-Pseudos.        (line 131)
-* MMIX pseudo-op BYTE:                   MMIX-Pseudos.        (line  97)
-* MMIX pseudo-op ESPEC:                  MMIX-Pseudos.        (line 131)
-* MMIX pseudo-op GREG:                   MMIX-Pseudos.        (line  50)
-* MMIX pseudo-op IS:                     MMIX-Pseudos.        (line  42)
+* MMIX pseudo-op BSPEC:                  MMIX-Pseudos.        (line 137)
+* MMIX pseudo-op BYTE:                   MMIX-Pseudos.        (line 101)
+* MMIX pseudo-op ESPEC:                  MMIX-Pseudos.        (line 137)
+* MMIX pseudo-op GREG:                   MMIX-Pseudos.        (line  53)
+* MMIX pseudo-op IS:                     MMIX-Pseudos.        (line  44)
 * MMIX pseudo-op LOC:                    MMIX-Pseudos.        (line   7)
-* MMIX pseudo-op LOCAL:                  MMIX-Pseudos.        (line  28)
-* MMIX pseudo-op OCTA:                   MMIX-Pseudos.        (line 108)
-* MMIX pseudo-op PREFIX:                 MMIX-Pseudos.        (line 120)
-* MMIX pseudo-op TETRA:                  MMIX-Pseudos.        (line 108)
-* MMIX pseudo-op WYDE:                   MMIX-Pseudos.        (line 108)
+* MMIX pseudo-op LOCAL:                  MMIX-Pseudos.        (line  29)
+* MMIX pseudo-op OCTA:                   MMIX-Pseudos.        (line 113)
+* MMIX pseudo-op PREFIX:                 MMIX-Pseudos.        (line 125)
+* MMIX pseudo-op TETRA:                  MMIX-Pseudos.        (line 113)
+* MMIX pseudo-op WYDE:                   MMIX-Pseudos.        (line 113)
 * MMIX pseudo-ops:                       MMIX-Pseudos.        (line   6)
 * MMIX register names:                   MMIX-Regs.           (line   6)
 * MMIX support:                          MMIX-Dependent.      (line   6)
 * mmixal differences:                    MMIX-mmixal.         (line   6)
-* mmregs directive, TIC54X:              TIC54X-Directives.   (line 169)
-* mmsg directive, TIC54X:                TIC54X-Directives.   (line  77)
+* 'mmregs' directive, TIC54X:            TIC54X-Directives.   (line 167)
+* 'mmsg' directive, TIC54X:              TIC54X-Directives.   (line  75)
 * MMX, i386:                             i386-SIMD.           (line   6)
 * MMX, x86-64:                           i386-SIMD.           (line   6)
-* mnemonic compatibility, i386:          i386-Mnemonics.      (line  62)
-* mnemonic suffixes, i386:               i386-Variations.     (line  29)
-* mnemonic suffixes, x86-64:             i386-Variations.     (line  29)
+* mnemonic compatibility, i386:          i386-Mnemonics.      (line  61)
+* mnemonic suffixes, i386:               i386-Variations.     (line  28)
+* mnemonic suffixes, x86-64:             i386-Variations.     (line  28)
 * mnemonics for opcodes, VAX:            VAX-opcodes.         (line   6)
 * mnemonics, AVR:                        AVR Opcodes.         (line   6)
 * mnemonics, D10V:                       D10V-Opcodes.        (line   6)
@@ -24135,16 +23951,16 @@ AS Index
 * mnemonics, SH:                         SH Opcodes.          (line   6)
 * mnemonics, SH64:                       SH64 Opcodes.        (line   6)
 * mnemonics, Z8000:                      Z8000 Opcodes.       (line   6)
-* mnolist directive, TIC54X:             TIC54X-Directives.   (line 164)
+* 'mnolist' directive, TIC54X:           TIC54X-Directives.   (line 162)
 * modifiers, M32C:                       M32C-Modifiers.      (line   6)
 * Motorola syntax for the 680x0:         M68K-Moto-Syntax.    (line   6)
-* MOVI instructions, relaxation:         Xtensa Immediate Relaxation.
+* 'MOVI' instructions, relaxation:       Xtensa Immediate Relaxation.
                                                               (line  12)
 * MOVN, MOVZ and MOVK group relocations, AArch64: AArch64-Relocations.
                                                               (line   6)
 * MOVW and MOVT relocations, ARM:        ARM-Relocations.     (line  21)
 * MRI compatibility mode:                M.                   (line   6)
-* mri directive:                         MRI.                 (line   6)
+* 'mri' directive:                       MRI.                 (line   6)
 * MRI mode, temporarily:                 MRI.                 (line   6)
 * MSP 430 floating point (IEEE):         MSP430 Floating Point.
                                                               (line   6)
@@ -24160,8 +23976,8 @@ AS Index
 * MSP 430 register names:                MSP430-Regs.         (line   6)
 * MSP 430 support:                       MSP430-Dependent.    (line   6)
 * MSP430 Assembler Extensions:           MSP430-Ext.          (line   6)
-* mul instruction, i386:                 i386-Notes.          (line   6)
-* mul instruction, x86-64:               i386-Notes.          (line   6)
+* 'mul' instruction, i386:               i386-Notes.          (line   6)
+* 'mul' instruction, x86-64:             i386-Notes.          (line   6)
 * N32K support:                          NS32K-Dependent.     (line   6)
 * name:                                  Z8000 Directives.    (line  18)
 * named section:                         Section.             (line   6)
@@ -24169,8 +23985,8 @@ AS Index
 * names, symbol:                         Symbol Names.        (line   6)
 * naming object file:                    o.                   (line   6)
 * new page, in listings:                 Eject.               (line   6)
-* newblock directive, TIC54X:            TIC54X-Directives.   (line 175)
-* newline (\n):                          Strings.             (line  21)
+* 'newblock' directive, TIC54X:          TIC54X-Directives.   (line 173)
+* newline ('\n'):                        Strings.             (line  21)
 * newline, required at file end:         Statements.          (line  14)
 * Nios II line comment character:        Nios II Chars.       (line   6)
 * Nios II line separator character:      Nios II Chars.       (line   6)
@@ -24180,36 +23996,36 @@ AS Index
 * Nios II options:                       Nios II Options.     (line   6)
 * Nios II support:                       NiosII-Dependent.    (line   6)
 * Nios support:                          NiosII-Dependent.    (line   6)
-* no-absolute-literals directive:        Absolute Literals Directive.
+* 'no-absolute-literals' directive:      Absolute Literals Directive.
                                                               (line   6)
-* no-longcalls directive:                Longcalls Directive. (line   6)
-* no-relax command line option, Nios II: Nios II Options.     (line  20)
-* no-schedule directive:                 Schedule Directive.  (line   6)
-* no-transform directive:                Transform Directive. (line   6)
-* nolist directive:                      Nolist.              (line   6)
-* nolist directive, TIC54X:              TIC54X-Directives.   (line 131)
-* NOP pseudo op, ARM:                    ARM Opcodes.         (line   9)
+* 'no-longcalls' directive:              Longcalls Directive. (line   6)
+* 'no-relax' command line option, Nios II: Nios II Options.   (line  19)
+* 'no-schedule' directive:               Schedule Directive.  (line   6)
+* 'no-transform' directive:              Transform Directive. (line   6)
+* 'nolist' directive:                    Nolist.              (line   6)
+* 'nolist' directive, TIC54X:            TIC54X-Directives.   (line 129)
+* 'NOP' pseudo op, ARM:                  ARM Opcodes.         (line   9)
 * notes for Alpha:                       Alpha Notes.         (line   6)
 * NS32K line comment character:          NS32K-Chars.         (line   6)
 * NS32K line separator:                  NS32K-Chars.         (line  18)
 * null-terminated strings:               Asciz.               (line   6)
 * number constants:                      Numbers.             (line   6)
-* number of macros executed:             Macro.               (line 143)
+* number of macros executed:             Macro.               (line 142)
 * numbered subsections:                  Sub-Sections.        (line   6)
 * numbers, 16-bit:                       hword.               (line   6)
 * numeric values:                        Expressions.         (line   6)
-* nword directive, SPARC:                Sparc-Directives.    (line  20)
+* 'nword' directive, SPARC:              Sparc-Directives.    (line  20)
 * object attributes:                     Object Attributes.   (line   6)
 * object file:                           Object.              (line   6)
 * object file format:                    Object Formats.      (line   6)
 * object file name:                      o.                   (line   6)
 * object file, after errors:             Z.                   (line   6)
 * obsolescent directives:                Deprecated.          (line   6)
-* octa directive:                        Octa.                (line   6)
-* octal character code (\DDD):           Strings.             (line  30)
+* 'octa' directive:                      Octa.                (line   6)
+* octal character code ('\DDD'):         Strings.             (line  30)
 * octal integers:                        Integers.            (line   9)
-* offset directive:                      Offset.              (line   6)
-* offset directive, V850:                V850 Directives.     (line   6)
+* 'offset' directive:                    Offset.              (line   6)
+* 'offset' directive, V850:              V850 Directives.     (line   6)
 * opcode mnemonics, VAX:                 VAX-opcodes.         (line   6)
 * opcode names, TILE-Gx:                 TILE-Gx Opcodes.     (line   6)
 * opcode names, TILEPro:                 TILEPro Opcodes.     (line   6)
@@ -24239,12 +24055,12 @@ AS Index
 * operator precedence:                   Infix Ops.           (line  11)
 * operators, in expressions:             Operators.           (line   6)
 * operators, permitted arguments:        Infix Ops.           (line   6)
-* optimization, D10V:                    Overview.            (line 490)
-* optimization, D30V:                    Overview.            (line 495)
+* optimization, D10V:                    Overview.            (line 493)
+* optimization, D30V:                    Overview.            (line 498)
 * optimizations:                         Xtensa Optimizations.
                                                               (line   6)
-* option directive, ARC:                 ARC Directives.      (line 159)
-* option directive, TIC54X:              TIC54X-Directives.   (line 179)
+* 'option' directive, ARC:               ARC Directives.      (line 150)
+* 'option' directive, TIC54X:            TIC54X-Directives.   (line 177)
 * option summary:                        Overview.            (line   6)
 * options for AArch64 (none):            AArch64 Options.     (line   6)
 * options for Alpha:                     Alpha Options.       (line   6)
@@ -24290,18 +24106,18 @@ AS Index
 * options, TIC54X:                       TIC54X-Opts.         (line   6)
 * options, XGATE:                        XGATE-Opts.          (line   6)
 * options, Z8000:                        Z8000 Options.       (line   6)
-* org directive:                         Org.                 (line   6)
-* other attribute, of a.out symbol:      Symbol Other.        (line   6)
+* 'org' directive:                       Org.                 (line   6)
+* other attribute, of 'a.out' symbol:    Symbol Other.        (line   6)
 * output file:                           Object.              (line   6)
-* p2align directive:                     P2align.             (line   6)
-* p2alignl directive:                    P2align.             (line  28)
-* p2alignw directive:                    P2align.             (line  28)
+* 'p2align' directive:                   P2align.             (line   6)
+* 'p2alignl' directive:                  P2align.             (line  28)
+* 'p2alignw' directive:                  P2align.             (line  28)
 * padding the location counter:          Align.               (line   6)
 * padding the location counter given a power of two: P2align. (line   6)
 * padding the location counter given number of bytes: Balign. (line   6)
 * page, in listings:                     Eject.               (line   6)
 * paper size, for listings:              Psize.               (line   6)
-* paths for .include:                    I.                   (line   6)
+* paths for '.include':                  I.                   (line   6)
 * patterns, writing in memory:           Fill.                (line   6)
 * PDP-11 comments:                       PDP-11-Syntax.       (line  16)
 * PDP-11 floating-point register syntax: PDP-11-Syntax.       (line  13)
@@ -24310,16 +24126,16 @@ AS Index
 * PDP-11 line separator:                 PDP-11-Syntax.       (line  19)
 * PDP-11 support:                        PDP-11-Dependent.    (line   6)
 * PDP-11 syntax:                         PDP-11-Syntax.       (line   6)
-* PIC code generation for ARM:           ARM Options.         (line 169)
+* PIC code generation for ARM:           ARM Options.         (line 170)
 * PIC code generation for M32R:          M32R-Opts.           (line  42)
-* PIC selection, MIPS:                   MIPS Opts.           (line  21)
-* PJ endianness:                         Overview.            (line 630)
+* PIC selection, MIPS:                   MIPS Options.        (line  21)
+* PJ endianness:                         Overview.            (line 627)
 * PJ line comment character:             PJ-Chars.            (line   6)
 * PJ line separator:                     PJ-Chars.            (line  14)
 * PJ options:                            PJ Options.          (line   6)
 * PJ support:                            PJ-Dependent.        (line   6)
-* plus, permitted arguments:             Infix Ops.           (line  44)
-* popsection directive:                  PopSection.          (line   6)
+* plus, permitted arguments:             Infix Ops.           (line  45)
+* 'popsection' directive:                PopSection.          (line   6)
 * Position-independent code, CRIS:       CRIS-Opts.           (line  27)
 * Position-independent code, symbols in, CRIS: CRIS-Pic.      (line   6)
 * PowerPC architectures:                 PowerPC-Opts.        (line   6)
@@ -24334,28 +24150,28 @@ AS Index
 * prefixes, i386:                        i386-Prefixes.       (line   6)
 * preprocessing:                         Preprocessing.       (line   6)
 * preprocessing, turning on and off:     Preprocessing.       (line  26)
-* previous directive:                    Previous.            (line   6)
+* 'previous' directive:                  Previous.            (line   6)
 * primary attributes, COFF symbols:      COFF Symbols.        (line  13)
-* print directive:                       Print.               (line   6)
-* proc directive, SPARC:                 Sparc-Directives.    (line  25)
-* profiler directive, MSP 430:           MSP430 Directives.   (line  22)
+* 'print' directive:                     Print.               (line   6)
+* 'proc' directive, SPARC:               Sparc-Directives.    (line  25)
+* 'profiler' directive, MSP 430:         MSP430 Directives.   (line  26)
 * profiling capability for MSP 430:      MSP430 Profiling Capability.
                                                               (line   6)
-* protected directive:                   Protected.           (line   6)
-* pseudo-op .arch, CRIS:                 CRIS-Pseudos.        (line  45)
+* 'protected' directive:                 Protected.           (line   6)
+* pseudo-op .arch, CRIS:                 CRIS-Pseudos.        (line  50)
 * pseudo-op .dword, CRIS:                CRIS-Pseudos.        (line  12)
-* pseudo-op .syntax, CRIS:               CRIS-Pseudos.        (line  17)
-* pseudo-op BSPEC, MMIX:                 MMIX-Pseudos.        (line 131)
-* pseudo-op BYTE, MMIX:                  MMIX-Pseudos.        (line  97)
-* pseudo-op ESPEC, MMIX:                 MMIX-Pseudos.        (line 131)
-* pseudo-op GREG, MMIX:                  MMIX-Pseudos.        (line  50)
-* pseudo-op IS, MMIX:                    MMIX-Pseudos.        (line  42)
+* pseudo-op .syntax, CRIS:               CRIS-Pseudos.        (line  18)
+* pseudo-op BSPEC, MMIX:                 MMIX-Pseudos.        (line 137)
+* pseudo-op BYTE, MMIX:                  MMIX-Pseudos.        (line 101)
+* pseudo-op ESPEC, MMIX:                 MMIX-Pseudos.        (line 137)
+* pseudo-op GREG, MMIX:                  MMIX-Pseudos.        (line  53)
+* pseudo-op IS, MMIX:                    MMIX-Pseudos.        (line  44)
 * pseudo-op LOC, MMIX:                   MMIX-Pseudos.        (line   7)
-* pseudo-op LOCAL, MMIX:                 MMIX-Pseudos.        (line  28)
-* pseudo-op OCTA, MMIX:                  MMIX-Pseudos.        (line 108)
-* pseudo-op PREFIX, MMIX:                MMIX-Pseudos.        (line 120)
-* pseudo-op TETRA, MMIX:                 MMIX-Pseudos.        (line 108)
-* pseudo-op WYDE, MMIX:                  MMIX-Pseudos.        (line 108)
+* pseudo-op LOCAL, MMIX:                 MMIX-Pseudos.        (line  29)
+* pseudo-op OCTA, MMIX:                  MMIX-Pseudos.        (line 113)
+* pseudo-op PREFIX, MMIX:                MMIX-Pseudos.        (line 125)
+* pseudo-op TETRA, MMIX:                 MMIX-Pseudos.        (line 113)
+* pseudo-op WYDE, MMIX:                  MMIX-Pseudos.        (line 113)
 * pseudo-opcodes for XStormy16:          XStormy16 Opcodes.   (line   6)
 * pseudo-opcodes, M680x0:                M68K-Branch.         (line   6)
 * pseudo-opcodes, M68HC11:               M68HC11-Branch.      (line   6)
@@ -24363,19 +24179,19 @@ AS Index
 * pseudo-ops, CRIS:                      CRIS-Pseudos.        (line   6)
 * pseudo-ops, machine independent:       Pseudo Ops.          (line   6)
 * pseudo-ops, MMIX:                      MMIX-Pseudos.        (line   6)
-* psize directive:                       Psize.               (line   6)
+* 'psize' directive:                     Psize.               (line   6)
 * PSR bits:                              IA-64-Bits.          (line   6)
-* pstring directive, TIC54X:             TIC54X-Directives.   (line 208)
-* psw register, V850:                    V850-Regs.           (line 116)
-* purgem directive:                      Purgem.              (line   6)
+* 'pstring' directive, TIC54X:           TIC54X-Directives.   (line 206)
+* 'psw' register, V850:                  V850-Regs.           (line  80)
+* 'purgem' directive:                    Purgem.              (line   6)
 * purpose of GNU assembler:              GNU Assembler.       (line  12)
-* pushsection directive:                 PushSection.         (line   6)
-* quad directive:                        Quad.                (line   6)
-* quad directive, i386:                  i386-Float.          (line  21)
-* quad directive, x86-64:                i386-Float.          (line  21)
+* 'pushsection' directive:               PushSection.         (line   6)
+* 'quad' directive:                      Quad.                (line   6)
+* 'quad' directive, i386:                i386-Float.          (line  21)
+* 'quad' directive, x86-64:              i386-Float.          (line  21)
 * real-mode code, i386:                  i386-16bit.          (line   6)
-* ref directive, TIC54X:                 TIC54X-Directives.   (line 103)
-* register directive, SPARC:             Sparc-Directives.    (line  29)
+* 'ref' directive, TIC54X:               TIC54X-Directives.   (line 101)
+* 'register' directive, SPARC:           Sparc-Directives.    (line  29)
 * register names, AArch64:               AArch64-Regs.        (line   6)
 * register names, Alpha:                 Alpha-Regs.          (line   6)
 * register names, ARC:                   ARC-Regs.            (line   6)
@@ -24406,11 +24222,11 @@ AS Index
 * registers, TIC54X memory-mapped:       TIC54X-MMRegs.       (line   6)
 * registers, x86-64:                     i386-Regs.           (line   6)
 * registers, Z8000:                      Z8000-Regs.          (line   6)
-* relax-all command line option, Nios II: Nios II Options.    (line  13)
-* relax-section command line option, Nios II: Nios II Options.
+* 'relax-all' command line option, Nios II: Nios II Options.  (line  13)
+* 'relax-section' command line option, Nios II: Nios II Options.
                                                               (line   6)
 * relaxation:                            Xtensa Relaxation.   (line   6)
-* relaxation of ADDI instructions:       Xtensa Immediate Relaxation.
+* relaxation of 'ADDI' instructions:     Xtensa Immediate Relaxation.
                                                               (line  43)
 * relaxation of branch instructions:     Xtensa Branch Relaxation.
                                                               (line   6)
@@ -24418,17 +24234,17 @@ AS Index
                                                               (line   6)
 * relaxation of immediate fields:        Xtensa Immediate Relaxation.
                                                               (line   6)
-* relaxation of L16SI instructions:      Xtensa Immediate Relaxation.
+* relaxation of 'L16SI' instructions:    Xtensa Immediate Relaxation.
                                                               (line  23)
-* relaxation of L16UI instructions:      Xtensa Immediate Relaxation.
+* relaxation of 'L16UI' instructions:    Xtensa Immediate Relaxation.
                                                               (line  23)
-* relaxation of L32I instructions:       Xtensa Immediate Relaxation.
+* relaxation of 'L32I' instructions:     Xtensa Immediate Relaxation.
                                                               (line  23)
-* relaxation of L8UI instructions:       Xtensa Immediate Relaxation.
+* relaxation of 'L8UI' instructions:     Xtensa Immediate Relaxation.
                                                               (line  23)
-* relaxation of MOVI instructions:       Xtensa Immediate Relaxation.
+* relaxation of 'MOVI' instructions:     Xtensa Immediate Relaxation.
                                                               (line  12)
-* reloc directive:                       Reloc.               (line   6)
+* 'reloc' directive:                     Reloc.               (line   6)
 * relocation:                            Sections.            (line   6)
 * relocation example:                    Ld Sections.         (line  40)
 * relocations, AArch64:                  AArch64-Relocations. (line   6)
@@ -24436,10 +24252,10 @@ AS Index
 * relocations, Sparc:                    Sparc-Relocs.        (line   6)
 * repeat prefixes, i386:                 i386-Prefixes.       (line  44)
 * reporting bugs in assembler:           Reporting Bugs.      (line   6)
-* rept directive:                        Rept.                (line   6)
-* reserve directive, SPARC:              Sparc-Directives.    (line  39)
-* return instructions, i386:             i386-Variations.     (line  41)
-* return instructions, x86-64:           i386-Variations.     (line  41)
+* 'rept' directive:                      Rept.                (line   6)
+* 'reserve' directive, SPARC:            Sparc-Directives.    (line  39)
+* return instructions, i386:             i386-Variations.     (line  40)
+* return instructions, x86-64:           i386-Variations.     (line  40)
 * REX prefixes, i386:                    i386-Prefixes.       (line  46)
 * RL78 assembler directives:             RL78-Directives.     (line   6)
 * RL78 line comment character:           RL78-Chars.          (line   6)
@@ -24447,7 +24263,7 @@ AS Index
 * RL78 modifiers:                        RL78-Modifiers.      (line   6)
 * RL78 options:                          RL78-Opts.           (line   6)
 * RL78 support:                          RL78-Dependent.      (line   6)
-* rsect:                                 Z8000 Directives.    (line  52)
+* rsect:                                 Z8000 Directives.    (line  51)
 * RX assembler directive .3byte:         RX-Directives.       (line   9)
 * RX assembler directive .fetchalign:    RX-Directives.       (line  13)
 * RX assembler directives:               RX-Directives.       (line   6)
@@ -24474,48 +24290,46 @@ AS Index
 * s390 options:                          s390 Options.        (line   6)
 * s390 register naming:                  s390 Register.       (line   6)
 * s390 support:                          S/390-Dependent.     (line   6)
-* sblock directive, TIC54X:              TIC54X-Directives.   (line 182)
-* sbttl directive:                       Sbttl.               (line   6)
-* schedule directive:                    Schedule Directive.  (line   6)
-* scl directive:                         Scl.                 (line   6)
+* 'sblock' directive, TIC54X:            TIC54X-Directives.   (line 180)
+* 'sbttl' directive:                     Sbttl.               (line   6)
+* 'schedule' directive:                  Schedule Directive.  (line   6)
+* 'scl' directive:                       Scl.                 (line   6)
 * SCORE architectures:                   SCORE-Opts.          (line   6)
 * SCORE directives:                      SCORE-Pseudo.        (line   6)
 * SCORE line comment character:          SCORE-Chars.         (line   6)
 * SCORE line separator:                  SCORE-Chars.         (line  14)
 * SCORE options:                         SCORE-Opts.          (line   6)
 * SCORE processor:                       SCORE-Dependent.     (line   6)
-* sdaoff pseudo-op, V850:                V850 Opcodes.        (line  65)
-* search path for .include:              I.                   (line   6)
-* secondary directive:                   Secondary.           (line   6)
-* sect directive, MSP 430:               MSP430 Directives.   (line  18)
-* sect directive, TIC54X:                TIC54X-Directives.   (line 188)
-* section directive (COFF version):      Section.             (line  16)
-* section directive (ELF version):       Section.             (line  76)
-* section directive, V850:               V850 Directives.     (line   9)
+* 'sdaoff' pseudo-op, V850:              V850 Opcodes.        (line  65)
+* search path for '.include':            I.                   (line   6)
+* 'sect' directive, TIC54X:              TIC54X-Directives.   (line 186)
+* 'section' directive (COFF version):    Section.             (line  16)
+* 'section' directive (ELF version):     Section.             (line  66)
+* 'section' directive, V850:             V850 Directives.     (line   9)
 * section override prefixes, i386:       i386-Prefixes.       (line  23)
-* Section Stack <1>:                     SubSection.          (line   6)
-* Section Stack <2>:                     Section.             (line  71)
-* Section Stack <3>:                     PushSection.         (line   6)
-* Section Stack <4>:                     Previous.            (line   6)
 * Section Stack:                         PopSection.          (line   6)
-* section-relative addressing:           Secs Background.     (line  68)
+* Section Stack <1>:                     Previous.            (line   6)
+* Section Stack <2>:                     PushSection.         (line   6)
+* Section Stack <3>:                     Section.             (line  61)
+* Section Stack <4>:                     SubSection.          (line   6)
+* section-relative addressing:           Secs Background.     (line  65)
 * sections:                              Sections.            (line   6)
 * sections in messages, internal:        As Sections.         (line   6)
-* sections, i386:                        i386-Variations.     (line  47)
+* sections, i386:                        i386-Variations.     (line  46)
 * sections, named:                       Ld Sections.         (line   8)
-* sections, x86-64:                      i386-Variations.     (line  47)
-* seg directive, SPARC:                  Sparc-Directives.    (line  44)
+* sections, x86-64:                      i386-Variations.     (line  46)
+* 'seg' directive, SPARC:                Sparc-Directives.    (line  44)
 * segm:                                  Z8000 Directives.    (line  10)
-* set at directive, Nios II:             Nios II Directives.  (line  35)
-* set break directive, Nios II:          Nios II Directives.  (line  43)
-* set directive:                         Set.                 (line   6)
-* set directive, Nios II:                Nios II Directives.  (line  57)
-* set directive, TIC54X:                 TIC54X-Directives.   (line 191)
-* set noat directive, Nios II:           Nios II Directives.  (line  31)
-* set nobreak directive, Nios II:        Nios II Directives.  (line  39)
-* set norelax directive, Nios II:        Nios II Directives.  (line  46)
-* set relaxall directive, Nios II:       Nios II Directives.  (line  53)
-* set relaxsection directive, Nios II:   Nios II Directives.  (line  49)
+* 'set at' directive, Nios II:           Nios II Directives.  (line  35)
+* 'set break' directive, Nios II:        Nios II Directives.  (line  43)
+* 'set' directive:                       Set.                 (line   6)
+* 'set' directive, Nios II:              Nios II Directives.  (line  57)
+* 'set' directive, TIC54X:               TIC54X-Directives.   (line 189)
+* 'set noat' directive, Nios II:         Nios II Directives.  (line  31)
+* 'set nobreak' directive, Nios II:      Nios II Directives.  (line  39)
+* 'set norelax' directive, Nios II:      Nios II Directives.  (line  46)
+* 'set relaxall' directive, Nios II:     Nios II Directives.  (line  53)
+* 'set relaxsection' directive, Nios II: Nios II Directives.  (line  49)
 * SH addressing modes:                   SH-Addressing.       (line   6)
 * SH floating point (IEEE):              SH Floating Point.   (line   6)
 * SH line comment character:             SH-Chars.            (line   6)
@@ -24525,7 +24339,7 @@ AS Index
 * SH options:                            SH Options.          (line   6)
 * SH registers:                          SH-Regs.             (line   6)
 * SH support:                            SH-Dependent.        (line   6)
-* SH64 ABI options:                      SH64 Options.        (line  29)
+* SH64 ABI options:                      SH64 Options.        (line  25)
 * SH64 addressing modes:                 SH64-Addressing.     (line   6)
 * SH64 ISA options:                      SH64 Options.        (line   6)
 * SH64 line comment character:           SH64-Chars.          (line   6)
@@ -24535,45 +24349,45 @@ AS Index
 * SH64 options:                          SH64 Options.        (line   6)
 * SH64 registers:                        SH64-Regs.           (line   6)
 * SH64 support:                          SH64-Dependent.      (line   6)
-* shigh directive, M32R:                 M32R-Directives.     (line  26)
-* short directive:                       Short.               (line   6)
-* short directive, ARC:                  ARC Directives.      (line 168)
-* short directive, TIC54X:               TIC54X-Directives.   (line 111)
+* 'shigh' directive, M32R:               M32R-Directives.     (line  26)
+* 'short' directive:                     Short.               (line   6)
+* 'short' directive, ARC:                ARC Directives.      (line 159)
+* 'short' directive, TIC54X:             TIC54X-Directives.   (line 109)
 * SIMD, i386:                            i386-SIMD.           (line   6)
 * SIMD, x86-64:                          i386-SIMD.           (line   6)
 * single character constant:             Chars.               (line   6)
-* single directive:                      Single.              (line   6)
-* single directive, i386:                i386-Float.          (line  14)
-* single directive, x86-64:              i386-Float.          (line  14)
+* 'single' directive:                    Single.              (line   6)
+* 'single' directive, i386:              i386-Float.          (line  14)
+* 'single' directive, x86-64:            i386-Float.          (line  14)
 * single quote, Z80:                     Z80-Chars.           (line  20)
 * sixteen bit integers:                  hword.               (line   6)
 * sixteen byte integer:                  Octa.                (line   6)
-* size directive (COFF version):         Size.                (line  11)
-* size directive (ELF version):          Size.                (line  19)
+* 'size' directive (COFF version):       Size.                (line  11)
+* 'size' directive (ELF version):        Size.                (line  19)
 * size modifiers, D10V:                  D10V-Size.           (line   6)
 * size modifiers, D30V:                  D30V-Size.           (line   6)
 * size modifiers, M680x0:                M68K-Syntax.         (line   8)
 * size prefixes, i386:                   i386-Prefixes.       (line  27)
-* size suffixes, H8/300:                 H8/300 Opcodes.      (line 163)
+* size suffixes, H8/300:                 H8/300 Opcodes.      (line 160)
 * size, translations, Sparc:             Sparc-Size-Translations.
                                                               (line   6)
-* sizes operands, i386:                  i386-Variations.     (line  29)
-* sizes operands, x86-64:                i386-Variations.     (line  29)
-* skip directive:                        Skip.                (line   6)
-* skip directive, M680x0:                M68K-Directives.     (line  19)
-* skip directive, SPARC:                 Sparc-Directives.    (line  48)
-* sleb128 directive:                     Sleb128.             (line   6)
-* small objects, MIPS ECOFF:             MIPS Object.         (line  11)
-* SmartMIPS instruction generation override: MIPS ASE instruction generation overrides.
+* sizes operands, i386:                  i386-Variations.     (line  28)
+* sizes operands, x86-64:                i386-Variations.     (line  28)
+* 'skip' directive:                      Skip.                (line   6)
+* 'skip' directive, M680x0:              M68K-Directives.     (line  19)
+* 'skip' directive, SPARC:               Sparc-Directives.    (line  48)
+* 'sleb128' directive:                   Sleb128.             (line   6)
+* small data, MIPS:                      MIPS Small Data.     (line   6)
+* SmartMIPS instruction generation override: MIPS ASE Instruction Generation Overrides.
                                                               (line  11)
 * SOM symbol attributes:                 SOM Symbols.         (line   6)
 * source program:                        Input Files.         (line   6)
-* source, destination operands; i386:    i386-Variations.     (line  22)
-* source, destination operands; x86-64:  i386-Variations.     (line  22)
+* source, destination operands; i386:    i386-Variations.     (line  21)
+* source, destination operands; x86-64:  i386-Variations.     (line  21)
 * sp register:                           Xtensa Registers.    (line   6)
-* sp register, V850:                     V850-Regs.           (line  14)
-* space directive:                       Space.               (line   6)
-* space directive, TIC54X:               TIC54X-Directives.   (line 196)
+* 'sp' register, V850:                   V850-Regs.           (line  12)
+* 'space' directive:                     Space.               (line   6)
+* 'space' directive, TIC54X:             TIC54X-Directives.   (line 194)
 * space used, maximum for assembly:      statistics.          (line   6)
 * SPARC architectures:                   Sparc-Opts.          (line   6)
 * Sparc constants:                       Sparc-Constants.     (line   6)
@@ -24591,12 +24405,12 @@ AS Index
 * SPARC syntax:                          Sparc-Aligned-Data.  (line  21)
 * special characters, M680x0:            M68K-Chars.          (line   6)
 * special purpose registers, MSP 430:    MSP430-Regs.         (line  11)
-* sslist directive, TIC54X:              TIC54X-Directives.   (line 203)
-* ssnolist directive, TIC54X:            TIC54X-Directives.   (line 203)
-* stabd directive:                       Stab.                (line  38)
-* stabn directive:                       Stab.                (line  48)
-* stabs directive:                       Stab.                (line  51)
-* stabX directives:                      Stab.                (line   6)
+* 'sslist' directive, TIC54X:            TIC54X-Directives.   (line 201)
+* 'ssnolist' directive, TIC54X:          TIC54X-Directives.   (line 201)
+* 'stabd' directive:                     Stab.                (line  38)
+* 'stabn' directive:                     Stab.                (line  49)
+* 'stabs' directive:                     Stab.                (line  52)
+* 'stabX' directives:                    Stab.                (line   6)
 * standard assembler sections:           Secs Background.     (line  27)
 * standard input, as input file:         Command Line.        (line  10)
 * statement separator character:         Statements.          (line   6)
@@ -24605,7 +24419,7 @@ AS Index
 * statement separator, ARC:              ARC-Chars.           (line  12)
 * statement separator, ARM:              ARM-Chars.           (line  14)
 * statement separator, AVR:              AVR-Chars.           (line  14)
-* statement separator, CR16:             CR16-Chars.          (line  13)
+* statement separator, CR16:             CR16-Chars.          (line  12)
 * statement separator, Epiphany:         Epiphany-Chars.      (line  14)
 * statement separator, H8/300:           H8/300-Chars.        (line   8)
 * statement separator, i386:             i386-Chars.          (line  18)
@@ -24615,7 +24429,7 @@ AS Index
 * statement separator, IP2K:             IP2K-Chars.          (line  14)
 * statement separator, LM32:             LM32-Chars.          (line  12)
 * statement separator, M32C:             M32C-Chars.          (line  14)
-* statement separator, M68HC11:          M68HC11-Syntax.      (line  27)
+* statement separator, M68HC11:          M68HC11-Syntax.      (line  26)
 * statement separator, Meta:             Meta-Chars.          (line   8)
 * statement separator, MicroBlaze:       MicroBlaze-Chars.    (line  14)
 * statement separator, MIPS:             MIPS-Chars.          (line  14)
@@ -24634,7 +24448,7 @@ AS Index
 * statement separator, TIC6X:            TIC6X Syntax.        (line  13)
 * statement separator, V850:             V850-Chars.          (line  13)
 * statement separator, VAX:              VAX-Chars.           (line  14)
-* statement separator, XGATE:            XGATE-Syntax.        (line  26)
+* statement separator, XGATE:            XGATE-Syntax.        (line  25)
 * statement separator, XStormy16:        XStormy16-Chars.     (line  14)
 * statement separator, Z80:              Z80-Chars.           (line  13)
 * statement separator, Z8000:            Z8000-Chars.         (line  13)
@@ -24642,53 +24456,53 @@ AS Index
 * statistics, about assembly:            statistics.          (line   6)
 * stopping the assembly:                 Abort.               (line   6)
 * string constants:                      Strings.             (line   6)
-* string directive:                      String.              (line   8)
-* string directive on HPPA:              HPPA Directives.     (line 137)
-* string directive, TIC54X:              TIC54X-Directives.   (line 208)
+* 'string' directive:                    String.              (line   8)
+* 'string' directive on HPPA:            HPPA Directives.     (line 137)
+* 'string' directive, TIC54X:            TIC54X-Directives.   (line 206)
 * string literals:                       Ascii.               (line   6)
 * string, copying to object file:        String.              (line   8)
-* string16 directive:                    String.              (line   8)
+* 'string16' directive:                  String.              (line   8)
 * string16, copying to object file:      String.              (line   8)
-* string32 directive:                    String.              (line   8)
+* 'string32' directive:                  String.              (line   8)
 * string32, copying to object file:      String.              (line   8)
-* string64 directive:                    String.              (line   8)
+* 'string64' directive:                  String.              (line   8)
 * string64, copying to object file:      String.              (line   8)
-* string8 directive:                     String.              (line   8)
+* 'string8' directive:                   String.              (line   8)
 * string8, copying to object file:       String.              (line   8)
-* struct directive:                      Struct.              (line   6)
-* struct directive, TIC54X:              TIC54X-Directives.   (line 216)
+* 'struct' directive:                    Struct.              (line   6)
+* 'struct' directive, TIC54X:            TIC54X-Directives.   (line 214)
 * structure debugging, COFF:             Tag.                 (line   6)
 * sub-instruction ordering, D10V:        D10V-Chars.          (line  14)
 * sub-instruction ordering, D30V:        D30V-Chars.          (line  14)
 * sub-instructions, D10V:                D10V-Subs.           (line   6)
 * sub-instructions, D30V:                D30V-Subs.           (line   6)
 * subexpressions:                        Arguments.           (line  24)
-* subsection directive:                  SubSection.          (line   6)
+* 'subsection' directive:                SubSection.          (line   6)
 * subsym builtins, TIC54X:               TIC54X-Macros.       (line  16)
 * subtitles for listings:                Sbttl.               (line   6)
-* subtraction, permitted arguments:      Infix Ops.           (line  49)
+* subtraction, permitted arguments:      Infix Ops.           (line  50)
 * summary of options:                    Overview.            (line   6)
 * support:                               HPPA-Dependent.      (line   6)
 * supporting files, including:           Include.             (line   6)
 * suppressing warnings:                  W.                   (line  11)
 * sval:                                  Z8000 Directives.    (line  33)
 * symbol attributes:                     Symbol Attributes.   (line   6)
-* symbol attributes, a.out:              a.out Symbols.       (line   6)
+* symbol attributes, 'a.out':            a.out Symbols.       (line   6)
 * symbol attributes, COFF:               COFF Symbols.        (line   6)
 * symbol attributes, SOM:                SOM Symbols.         (line   6)
 * symbol descriptor, COFF:               Desc.                (line   6)
-* symbol modifiers <1>:                  M68HC11-Modifiers.   (line  12)
-* symbol modifiers <2>:                  M32C-Modifiers.      (line  11)
-* symbol modifiers <3>:                  LM32-Modifiers.      (line  12)
 * symbol modifiers:                      AVR-Modifiers.       (line  12)
+* symbol modifiers <1>:                  LM32-Modifiers.      (line  12)
+* symbol modifiers <2>:                  M32C-Modifiers.      (line  11)
+* symbol modifiers <3>:                  M68HC11-Modifiers.   (line  12)
 * symbol modifiers, TILE-Gx:             TILE-Gx Modifiers.   (line   6)
 * symbol modifiers, TILEPro:             TILEPro Modifiers.   (line   6)
 * symbol names:                          Symbol Names.        (line   6)
-* symbol names, $ in <1>:                SH64-Chars.          (line  15)
-* symbol names, $ in <2>:                SH-Chars.            (line  15)
-* symbol names, $ in <3>:                Meta-Chars.          (line  10)
-* symbol names, $ in <4>:                D30V-Chars.          (line  70)
-* symbol names, $ in:                    D10V-Chars.          (line  53)
+* symbol names, '$' in:                  D10V-Chars.          (line  46)
+* symbol names, '$' in <1>:              D30V-Chars.          (line  70)
+* symbol names, '$' in <2>:              Meta-Chars.          (line  10)
+* symbol names, '$' in <3>:              SH-Chars.            (line  15)
+* symbol names, '$' in <4>:              SH64-Chars.          (line  15)
 * symbol names, local:                   Symbol Names.        (line  27)
 * symbol names, temporary:               Symbol Names.        (line  40)
 * symbol storage class (COFF):           Scl.                 (line   6)
@@ -24709,7 +24523,7 @@ AS Index
 * Symbols, built-in, CRIS:               CRIS-Symbols.        (line   6)
 * Symbols, CRIS, built-in:               CRIS-Symbols.        (line   6)
 * symbols, local common:                 Lcomm.               (line   6)
-* symver directive:                      Symver.              (line   6)
+* 'symver' directive:                    Symver.              (line   6)
 * syntax compatibility, i386:            i386-Variations.     (line   6)
 * syntax compatibility, x86-64:          i386-Variations.     (line   6)
 * syntax, AVR:                           AVR-Modifiers.       (line   6)
@@ -24718,32 +24532,33 @@ AS Index
 * syntax, D30V:                          D30V-Syntax.         (line   6)
 * syntax, LM32:                          LM32-Modifiers.      (line   6)
 * syntax, M680x0:                        M68K-Syntax.         (line   8)
-* syntax, M68HC11 <1>:                   M68HC11-Modifiers.   (line   6)
 * syntax, M68HC11:                       M68HC11-Syntax.      (line   6)
+* syntax, M68HC11 <1>:                   M68HC11-Modifiers.   (line   6)
 * syntax, machine-independent:           Syntax.              (line   6)
 * syntax, RL78:                          RL78-Modifiers.      (line   6)
 * syntax, RX:                            RX-Modifiers.        (line   6)
-* syntax, SPARC:                         Sparc-Aligned-Data.  (line  21)
+* syntax, SPARC:                         Sparc-Aligned-Data.  (line  20)
 * syntax, TILE-Gx:                       TILE-Gx Syntax.      (line   6)
 * syntax, TILEPro:                       TILEPro Syntax.      (line   6)
 * syntax, XGATE:                         XGATE-Syntax.        (line   6)
 * syntax, Xtensa assembler:              Xtensa Syntax.       (line   6)
-* sysproc directive, i960:               Directives-i960.     (line  37)
-* tab (\t):                              Strings.             (line  27)
-* tab directive, TIC54X:                 TIC54X-Directives.   (line 247)
-* tag directive:                         Tag.                 (line   6)
-* tag directive, TIC54X:                 TIC54X-Directives.   (line 216)
+* 'sysproc' directive, i960:             Directives-i960.     (line  37)
+* tab ('\t'):                            Strings.             (line  27)
+* 'tab' directive, TIC54X:               TIC54X-Directives.   (line 245)
+* 'tag' directive:                       Tag.                 (line   6)
+* 'tag' directive, TIC54X:               TIC54X-Directives.   (line 214)
+* 'tag' directive, TIC54X <1>:           TIC54X-Directives.   (line 248)
 * TBM, i386:                             i386-TBM.            (line   6)
 * TBM, x86-64:                           i386-TBM.            (line   6)
-* tdaoff pseudo-op, V850:                V850 Opcodes.        (line  81)
+* 'tdaoff' pseudo-op, V850:              V850 Opcodes.        (line  81)
 * temporary symbol names:                Symbol Names.        (line  40)
 * text and data sections, joining:       R.                   (line   6)
-* text directive:                        Text.                (line   6)
+* 'text' directive:                      Text.                (line   6)
 * text section:                          Ld Sections.         (line   9)
-* tfloat directive, i386:                i386-Float.          (line  14)
-* tfloat directive, x86-64:              i386-Float.          (line  14)
-* Thumb support <1>:                     ARM-Dependent.       (line   6)
+* 'tfloat' directive, i386:              i386-Float.          (line  14)
+* 'tfloat' directive, x86-64:            i386-Float.          (line  14)
 * Thumb support:                         AArch64-Dependent.   (line   6)
+* Thumb support <1>:                     ARM-Dependent.       (line   6)
 * TIC54X builtin math functions:         TIC54X-Builtins.     (line   6)
 * TIC54X line comment character:         TIC54X-Chars.        (line   6)
 * TIC54X line separator:                 TIC54X-Chars.        (line  17)
@@ -24773,35 +24588,35 @@ AS Index
 * TILEPro support:                       TILEPro-Dependent.   (line   6)
 * TILEPro syntax:                        TILEPro Syntax.      (line   6)
 * time, total for assembly:              statistics.          (line   6)
-* title directive:                       Title.               (line   6)
-* tls_gd directive, Nios II:             Nios II Relocations. (line  38)
-* tls_ie directive, Nios II:             Nios II Relocations. (line  38)
-* tls_ldm directive, Nios II:            Nios II Relocations. (line  38)
-* tls_ldo directive, Nios II:            Nios II Relocations. (line  38)
-* tls_le directive, Nios II:             Nios II Relocations. (line  38)
+* 'title' directive:                     Title.               (line   6)
+* 'tls_gd' directive, Nios II:           Nios II Relocations. (line  38)
+* 'tls_ie' directive, Nios II:           Nios II Relocations. (line  38)
+* 'tls_ldm' directive, Nios II:          Nios II Relocations. (line  38)
+* 'tls_ldo' directive, Nios II:          Nios II Relocations. (line  38)
+* 'tls_le' directive, Nios II:           Nios II Relocations. (line  38)
 * TMS320C6X support:                     TIC6X-Dependent.     (line   6)
-* tp register, V850:                     V850-Regs.           (line  20)
-* transform directive:                   Transform Directive. (line   6)
+* 'tp' register, V850:                   V850-Regs.           (line  16)
+* 'transform' directive:                 Transform Directive. (line   6)
 * trusted compiler:                      f.                   (line   6)
 * turning preprocessing on and off:      Preprocessing.       (line  26)
-* type directive (COFF version):         Type.                (line  11)
-* type directive (ELF version):          Type.                (line  22)
+* 'type' directive (COFF version):       Type.                (line  11)
+* 'type' directive (ELF version):        Type.                (line  22)
 * type of a symbol:                      Symbol Type.         (line   6)
-* ualong directive, SH:                  SH Directives.       (line   6)
-* uaquad directive, SH:                  SH Directives.       (line   6)
-* uaword directive, SH:                  SH Directives.       (line   6)
-* ubyte directive, TIC54X:               TIC54X-Directives.   (line  36)
-* uchar directive, TIC54X:               TIC54X-Directives.   (line  36)
-* uhalf directive, TIC54X:               TIC54X-Directives.   (line 111)
-* uint directive, TIC54X:                TIC54X-Directives.   (line 111)
-* uleb128 directive:                     Uleb128.             (line   6)
-* ulong directive, TIC54X:               TIC54X-Directives.   (line 135)
+* 'ualong' directive, SH:                SH Directives.       (line   6)
+* 'uaquad' directive, SH:                SH Directives.       (line   6)
+* 'uaword' directive, SH:                SH Directives.       (line   6)
+* 'ubyte' directive, TIC54X:             TIC54X-Directives.   (line  34)
+* 'uchar' directive, TIC54X:             TIC54X-Directives.   (line  34)
+* 'uhalf' directive, TIC54X:             TIC54X-Directives.   (line 109)
+* 'uint' directive, TIC54X:              TIC54X-Directives.   (line 109)
+* 'uleb128' directive:                   Uleb128.             (line   6)
+* 'ulong' directive, TIC54X:             TIC54X-Directives.   (line 133)
 * undefined section:                     Ld Sections.         (line  36)
-* union directive, TIC54X:               TIC54X-Directives.   (line 250)
+* 'union' directive, TIC54X:             TIC54X-Directives.   (line 248)
 * unsegm:                                Z8000 Directives.    (line  14)
-* usect directive, TIC54X:               TIC54X-Directives.   (line 262)
-* ushort directive, TIC54X:              TIC54X-Directives.   (line 111)
-* uword directive, TIC54X:               TIC54X-Directives.   (line 111)
+* 'usect' directive, TIC54X:             TIC54X-Directives.   (line 260)
+* 'ushort' directive, TIC54X:            TIC54X-Directives.   (line 109)
+* 'uword' directive, TIC54X:             TIC54X-Directives.   (line 109)
 * V850 command line options:             V850 Options.        (line   9)
 * V850 floating point (IEEE):            V850 Floating Point. (line   6)
 * V850 line comment character:           V850-Chars.          (line   6)
@@ -24811,10 +24626,10 @@ AS Index
 * V850 options (none):                   V850 Options.        (line   6)
 * V850 register names:                   V850-Regs.           (line   6)
 * V850 support:                          V850-Dependent.      (line   6)
-* val directive:                         Val.                 (line   6)
+* 'val' directive:                       Val.                 (line   6)
 * value attribute, COFF:                 Val.                 (line   6)
 * value of a symbol:                     Symbol Value.        (line   6)
-* var directive, TIC54X:                 TIC54X-Directives.   (line 272)
+* 'var' directive, TIC54X:               TIC54X-Directives.   (line 270)
 * VAX bitfields not supported:           VAX-no.              (line   6)
 * VAX branch improvement:                VAX-branch.          (line   6)
 * VAX command-line options ignored:      VAX-Opts.            (line   6)
@@ -24831,16 +24646,18 @@ AS Index
 * VAX support:                           Vax-Dependent.       (line   6)
 * Vax-11 C compatibility:                VAX-Opts.            (line  42)
 * VAX/VMS options:                       VAX-Opts.            (line  42)
-* version directive:                     Version.             (line   6)
-* version directive, TIC54X:             TIC54X-Directives.   (line 276)
+* 'version' directive:                   Version.             (line   6)
+* 'version' directive, TIC54X:           TIC54X-Directives.   (line 274)
 * version of assembler:                  v.                   (line   6)
 * versions of symbols:                   Symver.              (line   6)
-* visibility <1>:                        Protected.           (line   6)
-* visibility <2>:                        Internal.            (line   6)
+* Virtualization instruction generation override: MIPS ASE Instruction Generation Overrides.
+                                                              (line  41)
 * visibility:                            Hidden.              (line   6)
+* visibility <1>:                        Internal.            (line   6)
+* visibility <2>:                        Protected.           (line   6)
 * VMS (VAX) options:                     VAX-Opts.            (line  42)
-* vtable_entry directive:                VTableEntry.         (line   6)
-* vtable_inherit directive:              VTableInherit.       (line   6)
+* 'vtable_entry' directive:              VTableEntry.         (line   6)
+* 'vtable_inherit' directive:            VTableInherit.       (line   6)
 * warning directive:                     Warning.             (line   6)
 * warning for altered difference tables: K.                   (line   6)
 * warning messages:                      Errors.              (line   6)
@@ -24848,57 +24665,57 @@ AS Index
 * warnings, M32R:                        M32R-Warnings.       (line   6)
 * warnings, suppressing:                 W.                   (line  11)
 * warnings, switching on:                W.                   (line  19)
-* weak directive:                        Weak.                (line   6)
-* weakref directive:                     Weakref.             (line   6)
+* 'weak' directive:                      Weak.                (line   6)
+* 'weakref' directive:                   Weakref.             (line   6)
 * whitespace:                            Whitespace.          (line   6)
 * whitespace, removed by preprocessor:   Preprocessing.       (line   7)
-* wide floating point directives, VAX:   VAX-directives.      (line  10)
-* width directive, TIC54X:               TIC54X-Directives.   (line 127)
+* wide floating point directives, VAX:   VAX-directives.      (line   9)
+* 'width' directive, TIC54X:             TIC54X-Directives.   (line 125)
 * Width of continuation lines of disassembly output: listing. (line  21)
 * Width of first line disassembly output: listing.            (line  16)
 * Width of source line output:           listing.             (line  28)
-* wmsg directive, TIC54X:                TIC54X-Directives.   (line  77)
-* word directive:                        Word.                (line   6)
-* word directive, ARC:                   ARC Directives.      (line 171)
-* word directive, H8/300:                H8/300 Directives.   (line   6)
-* word directive, i386:                  i386-Float.          (line  21)
-* word directive, Nios II:               Nios II Directives.  (line  13)
-* word directive, SPARC:                 Sparc-Directives.    (line  51)
-* word directive, TIC54X:                TIC54X-Directives.   (line 111)
-* word directive, x86-64:                i386-Float.          (line  21)
+* 'wmsg' directive, TIC54X:              TIC54X-Directives.   (line  75)
+* 'word' directive:                      Word.                (line   6)
+* 'word' directive, ARC:                 ARC Directives.      (line 162)
+* 'word' directive, H8/300:              H8/300 Directives.   (line   6)
+* 'word' directive, i386:                i386-Float.          (line  21)
+* 'word' directive, Nios II:             Nios II Directives.  (line  13)
+* 'word' directive, SPARC:               Sparc-Directives.    (line  51)
+* 'word' directive, TIC54X:              TIC54X-Directives.   (line 109)
+* 'word' directive, x86-64:              i386-Float.          (line  21)
 * writing patterns in memory:            Fill.                (line   6)
 * wval:                                  Z8000 Directives.    (line  24)
 * x86 machine directives:                i386-Directives.     (line   6)
 * x86-64 arch directive:                 i386-Arch.           (line   6)
 * x86-64 att_syntax pseudo op:           i386-Variations.     (line   6)
-* x86-64 conversion instructions:        i386-Mnemonics.      (line  37)
+* x86-64 conversion instructions:        i386-Mnemonics.      (line  36)
 * x86-64 floating point:                 i386-Float.          (line   6)
 * x86-64 immediate operands:             i386-Variations.     (line  15)
 * x86-64 instruction naming:             i386-Mnemonics.      (line   6)
 * x86-64 intel_syntax pseudo op:         i386-Variations.     (line   6)
 * x86-64 jump optimization:              i386-Jumps.          (line   6)
-* x86-64 jump, call, return:             i386-Variations.     (line  41)
+* x86-64 jump, call, return:             i386-Variations.     (line  40)
 * x86-64 jump/call operands:             i386-Variations.     (line  15)
 * x86-64 memory references:              i386-Memory.         (line   6)
 * x86-64 options:                        i386-Options.        (line   6)
 * x86-64 register operands:              i386-Variations.     (line  15)
 * x86-64 registers:                      i386-Regs.           (line   6)
-* x86-64 sections:                       i386-Variations.     (line  47)
-* x86-64 size suffixes:                  i386-Variations.     (line  29)
-* x86-64 source, destination operands:   i386-Variations.     (line  22)
+* x86-64 sections:                       i386-Variations.     (line  46)
+* x86-64 size suffixes:                  i386-Variations.     (line  28)
+* x86-64 source, destination operands:   i386-Variations.     (line  21)
 * x86-64 support:                        i386-Dependent.      (line   6)
 * x86-64 syntax compatibility:           i386-Variations.     (line   6)
-* xfloat directive, TIC54X:              TIC54X-Directives.   (line  64)
-* XGATE addressing modes:                XGATE-Syntax.        (line  29)
+* 'xfloat' directive, TIC54X:            TIC54X-Directives.   (line  62)
+* XGATE addressing modes:                XGATE-Syntax.        (line  28)
 * XGATE assembler directives:            XGATE-Directives.    (line   6)
 * XGATE floating point:                  XGATE-Float.         (line   6)
 * XGATE line comment character:          XGATE-Syntax.        (line  16)
-* XGATE line separator:                  XGATE-Syntax.        (line  26)
+* XGATE line separator:                  XGATE-Syntax.        (line  25)
 * XGATE opcodes:                         XGATE-opcodes.       (line   6)
 * XGATE options:                         XGATE-Opts.          (line   6)
 * XGATE support:                         XGATE-Dependent.     (line   6)
 * XGATE syntax:                          XGATE-Syntax.        (line   6)
-* xlong directive, TIC54X:               TIC54X-Directives.   (line 135)
+* 'xlong' directive, TIC54X:             TIC54X-Directives.   (line 133)
 * XStormy16 comment character:           XStormy16-Chars.     (line  11)
 * XStormy16 line comment character:      XStormy16-Chars.     (line   6)
 * XStormy16 line separator:              XStormy16-Chars.     (line  14)
@@ -24911,7 +24728,7 @@ AS Index
 * Xtensa directives:                     Xtensa Directives.   (line   6)
 * Xtensa opcode names:                   Xtensa Opcodes.      (line   6)
 * Xtensa register names:                 Xtensa Registers.    (line   6)
-* xword directive, SPARC:                Sparc-Directives.    (line  55)
+* 'xword' directive, SPARC:              Sparc-Directives.    (line  55)
 * Z80 $:                                 Z80-Chars.           (line  15)
 * Z80 ':                                 Z80-Chars.           (line  20)
 * Z80 floating point:                    Z80 Floating Point.  (line   6)
@@ -24920,9 +24737,9 @@ AS Index
 * Z80 options:                           Z80 Options.         (line   6)
 * Z80 registers:                         Z80-Regs.            (line   6)
 * Z80 support:                           Z80-Dependent.       (line   6)
-* Z80 Syntax:                            Z80 Options.         (line  47)
-* Z80, \:                                Z80-Chars.           (line  18)
+* Z80 Syntax:                            Z80 Options.         (line  40)
 * Z80, case sensitivity:                 Z80-Case.            (line   6)
+* Z80, \:                                Z80-Chars.           (line  18)
 * Z80-only directives:                   Z80 Directives.      (line   9)
 * Z800 addressing modes:                 Z8000-Addressing.    (line   6)
 * Z8000 directives:                      Z8000 Directives.    (line   6)
@@ -24932,636 +24749,638 @@ AS Index
 * Z8000 options:                         Z8000 Options.       (line   6)
 * Z8000 registers:                       Z8000-Regs.          (line   6)
 * Z8000 support:                         Z8000-Dependent.     (line   6)
-* zdaoff pseudo-op, V850:                V850 Opcodes.        (line  99)
-* zero register, V850:                   V850-Regs.           (line   7)
+* 'zdaoff' pseudo-op, V850:              V850 Opcodes.        (line  98)
+* 'zero' register, V850:                 V850-Regs.           (line   7)
 * zero-terminated strings:               Asciz.               (line   6)
 
 
 
 Tag Table:
-Node: Top958
-Node: Overview1957
-Node: Manual33174
-Node: GNU Assembler34118
-Node: Object Formats35289
-Node: Command Line35741
-Node: Input Files36828
-Node: Object38809
-Node: Errors39705
-Node: Invoking40900
-Node: a42855
-Node: alternate44766
-Node: D44938
-Node: f45171
-Node: I45679
-Node: K46223
-Node: L46527
-Node: listing47266
-Node: M48925
-Node: MD53326
-Node: o53752
-Node: R54207
-Node: statistics55237
-Node: traditional-format55644
-Node: v56117
-Node: W56392
-Node: Z57299
-Node: Syntax57821
-Node: Preprocessing58413
-Node: Whitespace59976
-Node: Comments60372
-Node: Symbol Intro62383
-Node: Statements63110
-Node: Constants65099
-Node: Characters65730
-Node: Strings66232
-Node: Chars68398
-Node: Numbers69152
-Node: Integers69692
-Node: Bignums70348
-Node: Flonums70704
-Node: Sections72451
-Node: Secs Background72829
-Node: Ld Sections77868
-Node: As Sections80252
-Node: Sub-Sections81162
-Node: bss84307
-Node: Symbols85257
-Node: Labels85905
-Node: Setting Symbols86636
-Node: Symbol Names87190
-Node: Dot92481
-Node: Symbol Attributes92928
-Node: Symbol Value93665
-Node: Symbol Type94710
-Node: a.out Symbols95098
-Node: Symbol Desc95360
-Node: Symbol Other95655
-Node: COFF Symbols95824
-Node: SOM Symbols96497
-Node: Expressions96939
-Node: Empty Exprs97688
-Node: Integer Exprs98035
-Node: Arguments98430
-Node: Operators99536
-Node: Prefix Ops99871
-Node: Infix Ops100199
-Node: Pseudo Ops102589
-Node: Abort108264
-Node: ABORT (COFF)108676
-Node: Align108884
-Node: Altmacro111166
-Node: Ascii112495
-Node: Asciz112804
-Node: Balign113049
-Node: Bundle directives114925
-Node: Byte117854
-Node: CFI directives118115
-Node: Comm123744
-Ref: Comm-Footnote-1125345
-Node: Data125707
-Node: Def126024
-Node: Desc126256
-Node: Dim126756
-Node: Double127013
-Node: Eject127351
-Node: Else127526
-Node: Elseif127826
-Node: End128120
-Node: Endef128335
-Node: Endfunc128512
-Node: Endif128687
-Node: Equ128948
-Node: Equiv129462
-Node: Eqv130018
-Node: Err130382
-Node: Error130693
-Node: Exitm131138
-Node: Extern131307
-Node: Fail131568
-Node: File132013
-Node: Fill133342
-Node: Float134306
-Node: Func134648
-Node: Global135238
-Node: Gnu_attribute135995
-Node: Hidden136220
-Node: hword136806
-Node: Ident137134
-Node: If137708
-Node: Incbin140767
-Node: Include141462
-Node: Int142013
-Node: Internal142394
-Node: Irp143042
-Node: Irpc143921
-Node: Lcomm144838
-Node: Lflags145586
-Node: Line145780
-Node: Linkonce146693
-Node: List147922
-Node: Ln148530
-Node: Loc148680
-Node: Loc_mark_labels150066
-Node: Local150550
-Node: Long151162
-Node: Macro151340
-Node: MRI157262
-Node: Noaltmacro157600
-Node: Nolist157769
-Node: Octa158199
-Node: Offset158536
-Node: Org158863
-Node: P2align160148
-Node: PopSection162076
-Node: Previous162584
-Node: Print163997
-Node: Protected164226
-Node: Secondary164877
-Node: Psize165162
-Node: Purgem165846
-Node: PushSection166067
-Node: Quad166810
-Node: Reloc167266
-Node: Rept168027
-Node: Sbttl168441
-Node: Scl168806
-Node: Section169147
-Node: Set175303
-Node: Short175876
-Node: Single176199
-Node: Size176546
-Node: Skip177220
-Node: Sleb128177544
-Node: Space177868
-Node: Stab178509
-Node: String180513
-Node: Struct181507
-Node: SubSection182232
-Node: Symver182795
-Node: Tag185188
-Node: Text185570
-Node: Title185891
-Node: Type186272
-Node: Uleb128188585
-Node: Val188909
-Node: Version189159
-Node: VTableEntry189434
-Node: VTableInherit189724
-Node: Warning190174
-Node: Weak190408
-Node: Weakref191077
-Node: Word192042
-Node: Deprecated193888
-Node: Object Attributes194123
-Node: GNU Object Attributes195843
-Node: Defining New Object Attributes198396
-Node: Machine Dependencies199193
-Node: AArch64-Dependent203022
-Node: AArch64 Options203468
-Node: AArch64 Syntax203877
-Node: AArch64-Chars204174
-Node: AArch64-Regs204660
-Node: AArch64-Relocations204954
-Node: AArch64 Floating Point206033
-Node: AArch64 Directives206258
-Node: AArch64 Opcodes207806
-Node: AArch64 Mapping Symbols208485
-Node: Alpha-Dependent208867
-Node: Alpha Notes209307
-Node: Alpha Options209588
-Node: Alpha Syntax212063
-Node: Alpha-Chars212532
-Node: Alpha-Regs212944
-Node: Alpha-Relocs213331
-Node: Alpha Floating Point219589
-Node: Alpha Directives219811
-Node: Alpha Opcodes225334
-Node: ARC-Dependent225629
-Node: ARC Options226012
-Node: ARC Syntax227081
-Node: ARC-Chars227313
-Node: ARC-Regs227794
-Node: ARC Floating Point227918
-Node: ARC Directives228229
-Node: ARC Opcodes234194
-Node: ARM-Dependent234420
-Node: ARM Options234885
-Node: ARM Syntax243719
-Node: ARM-Instruction-Set244087
-Node: ARM-Chars245307
-Node: ARM-Regs246018
-Node: ARM-Relocations246227
-Node: ARM-Neon-Alignment247361
-Node: ARM Floating Point247825
-Node: ARM Directives248024
-Ref: arm_pad249341
-Ref: arm_fnend252678
-Ref: arm_fnstart253002
-Ref: arm_save256012
-Ref: arm_setfp256713
-Node: ARM Opcodes260005
-Node: ARM Mapping Symbols262093
-Node: ARM Unwinding Tutorial262903
-Node: AVR-Dependent269103
-Node: AVR Options269393
-Node: AVR Syntax274281
-Node: AVR-Chars274568
-Node: AVR-Regs275127
-Node: AVR-Modifiers275706
-Node: AVR Opcodes277766
-Node: Blackfin-Dependent283012
-Node: Blackfin Options283324
-Node: Blackfin Syntax284298
-Node: Blackfin Directives290505
-Node: CR16-Dependent291251
-Node: CR16 Operand Qualifiers291551
-Node: CR16 Syntax294280
-Node: CR16-Chars294466
-Node: CRIS-Dependent295003
-Node: CRIS-Opts295349
-Ref: march-option297035
-Node: CRIS-Expand298852
-Node: CRIS-Symbols300035
-Node: CRIS-Syntax301204
-Node: CRIS-Chars301540
-Node: CRIS-Pic302091
-Ref: crispic302287
-Node: CRIS-Regs305827
-Node: CRIS-Pseudos306244
-Ref: crisnous307020
-Node: D10V-Dependent308302
-Node: D10V-Opts308653
-Node: D10V-Syntax309615
-Node: D10V-Size310144
-Node: D10V-Subs311117
-Node: D10V-Chars312152
-Node: D10V-Regs314064
-Node: D10V-Addressing315109
-Node: D10V-Word315795
-Node: D10V-Float316310
-Node: D10V-Opcodes316621
-Node: D30V-Dependent317014
-Node: D30V-Opts317371
-Node: D30V-Syntax318048
-Node: D30V-Size318582
-Node: D30V-Subs319555
-Node: D30V-Chars320592
-Node: D30V-Guarded323200
-Node: D30V-Regs323882
-Node: D30V-Addressing325023
-Node: D30V-Float325693
-Node: D30V-Opcodes326006
-Node: Epiphany-Dependent326401
-Node: Epiphany Options326689
-Node: Epiphany Syntax327088
-Node: Epiphany-Chars327289
-Node: H8/300-Dependent327843
-Node: H8/300 Options328259
-Node: H8/300 Syntax328526
-Node: H8/300-Chars328827
-Node: H8/300-Regs329126
-Node: H8/300-Addressing330045
-Node: H8/300 Floating Point331086
-Node: H8/300 Directives331413
-Node: H8/300 Opcodes332541
-Node: HPPA-Dependent340863
-Node: HPPA Notes341298
-Node: HPPA Options342056
-Node: HPPA Syntax342251
-Node: HPPA Floating Point343521
-Node: HPPA Directives343727
-Node: HPPA Opcodes352413
-Node: ESA/390-Dependent352672
-Node: ESA/390 Notes353132
-Node: ESA/390 Options353923
-Node: ESA/390 Syntax354133
-Node: ESA/390 Floating Point356306
-Node: ESA/390 Directives356585
-Node: ESA/390 Opcodes359874
-Node: i386-Dependent360136
-Node: i386-Options361466
-Node: i386-Directives366048
-Node: i386-Syntax366786
-Node: i386-Variations367091
-Node: i386-Chars369632
-Node: i386-Mnemonics370361
-Node: i386-Regs373672
-Node: i386-Prefixes375717
-Node: i386-Memory378477
-Node: i386-Jumps381414
-Node: i386-Float382535
-Node: i386-SIMD384366
-Node: i386-LWP385475
-Node: i386-BMI386309
-Node: i386-TBM386687
-Node: i386-16bit387217
-Node: i386-Bugs389288
-Node: i386-Arch390042
-Node: i386-Notes392924
-Node: i860-Dependent393782
-Node: Notes-i860394222
-Node: Options-i860395127
-Node: Directives-i860396490
-Node: Opcodes for i860397559
-Node: Syntax of i860399749
-Node: i860-Chars399933
-Node: i960-Dependent400492
-Node: Options-i960400939
-Node: Floating Point-i960404824
-Node: Directives-i960405092
-Node: Opcodes for i960407126
-Node: callj-i960407766
-Node: Compare-and-branch-i960408255
-Node: Syntax of i960410159
-Node: i960-Chars410359
-Node: IA-64-Dependent410902
-Node: IA-64 Options411203
-Node: IA-64 Syntax414354
-Node: IA-64-Chars414760
-Node: IA-64-Regs414990
-Node: IA-64-Bits415916
-Node: IA-64-Relocs416446
-Node: IA-64 Opcodes416918
-Node: IP2K-Dependent417190
-Node: IP2K-Opts417462
-Node: IP2K-Syntax417962
-Node: IP2K-Chars418136
-Node: LM32-Dependent418679
-Node: LM32 Options418974
-Node: LM32 Syntax419608
-Node: LM32-Regs419904
-Node: LM32-Modifiers420863
-Node: LM32-Chars422238
-Node: LM32 Opcodes422746
-Node: M32C-Dependent423050
-Node: M32C-Opts423559
-Node: M32C-Syntax423979
-Node: M32C-Modifiers424214
-Node: M32C-Chars426003
-Node: M32R-Dependent426569
-Node: M32R-Opts426890
-Node: M32R-Directives431057
-Node: M32R-Warnings435032
-Node: M68K-Dependent438038
-Node: M68K-Opts438505
-Node: M68K-Syntax445878
-Node: M68K-Moto-Syntax447718
-Node: M68K-Float450308
-Node: M68K-Directives450828
-Node: M68K-opcodes452156
-Node: M68K-Branch452382
-Node: M68K-Chars456580
-Node: M68HC11-Dependent457443
-Node: M68HC11-Opts457974
-Node: M68HC11-Syntax462279
-Node: M68HC11-Modifiers465070
-Node: M68HC11-Directives466898
-Node: M68HC11-Float468274
-Node: M68HC11-opcodes468802
-Node: M68HC11-Branch468984
-Node: Meta-Dependent471433
-Node: Meta Options471718
-Node: Meta Syntax472380
-Node: Meta-Chars472592
-Node: Meta-Regs472892
-Node: MicroBlaze-Dependent473168
-Node: MicroBlaze Directives473857
-Node: MicroBlaze Syntax475240
-Node: MicroBlaze-Chars475472
-Node: MIPS-Dependent476024
-Node: MIPS Opts477252
-Node: MIPS Object488326
-Node: MIPS Stabs489892
-Node: MIPS symbol sizes490614
-Node: MIPS ISA492283
-Node: MIPS autoextend494020
-Node: MIPS insn494750
-Node: MIPS option stack496035
-Node: MIPS ASE instruction generation overrides496809
-Node: MIPS floating-point498847
-Node: MIPS Syntax499753
-Node: MIPS-Chars500015
-Node: MMIX-Dependent500557
-Node: MMIX-Opts500937
-Node: MMIX-Expand504541
-Node: MMIX-Syntax505856
-Ref: mmixsite506213
-Node: MMIX-Chars507054
-Node: MMIX-Symbols507928
-Node: MMIX-Regs509996
-Node: MMIX-Pseudos511021
-Ref: MMIX-loc511162
-Ref: MMIX-local512242
-Ref: MMIX-is512774
-Ref: MMIX-greg513045
-Ref: GREG-base513964
-Ref: MMIX-byte515281
-Ref: MMIX-constants515752
-Ref: MMIX-prefix516398
-Ref: MMIX-spec516772
-Node: MMIX-mmixal517106
-Node: MSP430-Dependent520604
-Node: MSP430 Options521074
-Node: MSP430 Syntax521360
-Node: MSP430-Macros521676
-Node: MSP430-Chars522407
-Node: MSP430-Regs523122
-Node: MSP430-Ext523682
-Node: MSP430 Floating Point525503
-Node: MSP430 Directives525727
-Node: MSP430 Opcodes526518
-Node: MSP430 Profiling Capability526913
-Node: NiosII-Dependent529242
-Node: Nios II Options529662
-Node: Nios II Syntax530583
-Node: Nios II Chars530789
-Node: Nios II Relocations530980
-Node: Nios II Directives532454
-Node: Nios II Opcodes534017
-Node: NS32K-Dependent534292
-Node: NS32K Syntax534515
-Node: NS32K-Chars534664
-Node: PDP-11-Dependent535404
-Node: PDP-11-Options535793
-Node: PDP-11-Pseudos540864
-Node: PDP-11-Syntax541209
-Node: PDP-11-Mnemonics542041
-Node: PDP-11-Synthetic542343
-Node: PJ-Dependent542561
-Node: PJ Options542824
-Node: PJ Syntax543119
-Node: PJ-Chars543284
-Node: PPC-Dependent543833
-Node: PowerPC-Opts544166
-Node: PowerPC-Pseudo547662
-Node: PowerPC-Syntax548284
-Node: PowerPC-Chars548474
-Node: RL78-Dependent549225
-Node: RL78-Opts549623
-Node: RL78-Modifiers549806
-Node: RL78-Directives550582
-Node: RL78-Syntax551080
-Node: RL78-Chars551276
-Node: RX-Dependent551832
-Node: RX-Opts552263
-Node: RX-Modifiers555377
-Node: RX-Directives556481
-Node: RX-Float557221
-Node: RX-Syntax557862
-Node: RX-Chars558041
-Node: S/390-Dependent558593
-Node: s390 Options559309
-Node: s390 Characters560855
-Node: s390 Syntax561376
-Node: s390 Register562277
-Node: s390 Mnemonics563090
-Node: s390 Operands566110
-Node: s390 Formats568729
-Node: s390 Aliases576575
-Node: s390 Operand Modifier580472
-Node: s390 Instruction Marker584273
-Node: s390 Literal Pool Entries585289
-Node: s390 Directives587212
-Node: s390 Floating Point592268
-Node: SCORE-Dependent592714
-Node: SCORE-Opts593019
-Node: SCORE-Pseudo594307
-Node: SCORE-Syntax596384
-Node: SCORE-Chars596566
-Node: SH-Dependent597124
-Node: SH Options597535
-Node: SH Syntax598590
-Node: SH-Chars598863
-Node: SH-Regs599406
-Node: SH-Addressing600020
-Node: SH Floating Point600929
-Node: SH Directives602023
-Node: SH Opcodes602424
-Node: SH64-Dependent606746
-Node: SH64 Options607109
-Node: SH64 Syntax608906
-Node: SH64-Chars609189
-Node: SH64-Regs609738
-Node: SH64-Addressing610834
-Node: SH64 Directives612017
-Node: SH64 Opcodes613002
-Node: Sparc-Dependent613718
-Node: Sparc-Opts614130
-Node: Sparc-Aligned-Data618788
-Node: Sparc-Syntax619620
-Node: Sparc-Chars620194
-Node: Sparc-Regs620757
-Node: Sparc-Constants625868
-Node: Sparc-Relocs630628
-Node: Sparc-Size-Translations635764
-Node: Sparc-Float637413
-Node: Sparc-Directives637608
-Node: TIC54X-Dependent639568
-Node: TIC54X-Opts640331
-Node: TIC54X-Block641374
-Node: TIC54X-Env641734
-Node: TIC54X-Constants642082
-Node: TIC54X-Subsyms642484
-Node: TIC54X-Locals644393
-Node: TIC54X-Builtins645137
-Node: TIC54X-Ext647608
-Node: TIC54X-Directives648179
-Node: TIC54X-Macros659080
-Node: TIC54X-MMRegs661191
-Node: TIC54X-Syntax661429
-Node: TIC54X-Chars661619
-Node: TIC6X-Dependent662310
-Node: TIC6X Options662613
-Node: TIC6X Syntax664614
-Node: TIC6X Directives665716
-Node: TILE-Gx-Dependent668001
-Node: TILE-Gx Options668311
-Node: TILE-Gx Syntax668661
-Node: TILE-Gx Opcodes670895
-Node: TILE-Gx Registers671183
-Node: TILE-Gx Modifiers671955
-Node: TILE-Gx Directives676927
-Node: TILEPro-Dependent677831
-Node: TILEPro Options678140
-Node: TILEPro Syntax678324
-Node: TILEPro Opcodes680558
-Node: TILEPro Registers680849
-Node: TILEPro Modifiers681619
-Node: TILEPro Directives686384
-Node: Z80-Dependent687288
-Node: Z80 Options687676
-Node: Z80 Syntax689099
-Node: Z80-Chars689771
-Node: Z80-Regs690621
-Node: Z80-Case690973
-Node: Z80 Floating Point691418
-Node: Z80 Directives691612
-Node: Z80 Opcodes693237
-Node: Z8000-Dependent694581
-Node: Z8000 Options695542
-Node: Z8000 Syntax695759
-Node: Z8000-Chars696049
-Node: Z8000-Regs696531
-Node: Z8000-Addressing697321
-Node: Z8000 Directives698438
-Node: Z8000 Opcodes700047
-Node: Vax-Dependent709989
-Node: VAX-Opts710549
-Node: VAX-float714284
-Node: VAX-directives714916
-Node: VAX-opcodes715777
-Node: VAX-branch716166
-Node: VAX-operands718673
-Node: VAX-no719436
-Node: VAX-Syntax719692
-Node: VAX-Chars719858
-Node: V850-Dependent720412
-Node: V850 Options720810
-Node: V850 Syntax724456
-Node: V850-Chars724696
-Node: V850-Regs725240
-Node: V850 Floating Point726808
-Node: V850 Directives727014
-Node: V850 Opcodes729081
-Node: XGATE-Dependent734973
-Node: XGATE-Opts735393
-Node: XGATE-Syntax736384
-Node: XGATE-Directives738463
-Node: XGATE-Float738702
-Node: XGATE-opcodes739199
-Node: XSTORMY16-Dependent739311
-Node: XStormy16 Syntax739657
-Node: XStormy16-Chars739847
-Node: XStormy16 Directives740460
-Node: XStormy16 Opcodes741115
-Node: Xtensa-Dependent742171
-Node: Xtensa Options742905
-Node: Xtensa Syntax745642
-Node: Xtensa Opcodes747786
-Node: Xtensa Registers749580
-Node: Xtensa Optimizations750213
-Node: Density Instructions750665
-Node: Xtensa Automatic Alignment751767
-Node: Xtensa Relaxation754214
-Node: Xtensa Branch Relaxation755122
-Node: Xtensa Call Relaxation756494
-Node: Xtensa Immediate Relaxation758280
-Node: Xtensa Directives760854
-Node: Schedule Directive762563
-Node: Longcalls Directive762903
-Node: Transform Directive763447
-Node: Literal Directive764189
-Ref: Literal Directive-Footnote-1767728
-Node: Literal Position Directive767870
-Node: Literal Prefix Directive769569
-Node: Absolute Literals Directive770467
-Node: Reporting Bugs771774
-Node: Bug Criteria772500
-Node: Bug Reporting773267
-Node: Acknowledgements779947
-Ref: Acknowledgements-Footnote-1784912
-Node: GNU Free Documentation License784938
-Node: AS Index810107
+Node: Top736
+Node: Overview1723
+Node: Manual33597
+Node: GNU Assembler34541
+Node: Object Formats35712
+Node: Command Line36164
+Node: Input Files37250
+Node: Object39231
+Node: Errors40127
+Node: Invoking41320
+Node: a43265
+Node: alternate45176
+Node: D45348
+Node: f45581
+Node: I46090
+Node: K46634
+Node: L46938
+Node: listing47677
+Node: M49336
+Node: MD53735
+Node: o54161
+Node: R54616
+Node: statistics55646
+Node: traditional-format56053
+Node: v56526
+Node: W56801
+Node: Z57708
+Node: Syntax58230
+Node: Preprocessing58822
+Node: Whitespace60386
+Node: Comments60782
+Node: Symbol Intro62793
+Node: Statements63518
+Node: Constants65506
+Node: Characters66137
+Node: Strings66639
+Node: Chars68803
+Node: Numbers69556
+Node: Integers70096
+Node: Bignums70752
+Node: Flonums71108
+Node: Sections72852
+Node: Secs Background73230
+Node: Ld Sections78263
+Node: As Sections80647
+Node: Sub-Sections81557
+Node: bss84705
+Node: Symbols85655
+Node: Labels86303
+Node: Setting Symbols87034
+Node: Symbol Names87588
+Node: Dot92883
+Node: Symbol Attributes93330
+Node: Symbol Value94063
+Node: Symbol Type95108
+Node: a.out Symbols95496
+Node: Symbol Desc95758
+Node: Symbol Other96054
+Node: COFF Symbols96223
+Node: SOM Symbols96896
+Node: Expressions97338
+Node: Empty Exprs98087
+Node: Integer Exprs98434
+Node: Arguments98829
+Node: Operators99935
+Node: Prefix Ops100270
+Node: Infix Ops100597
+Node: Pseudo Ops102991
+Node: Abort108593
+Node: ABORT (COFF)109006
+Node: Align109214
+Node: Altmacro111496
+Node: Ascii112827
+Node: Asciz113136
+Node: Balign113381
+Node: Bundle directives115257
+Node: Byte118185
+Node: CFI directives118446
+Node: Comm124079
+Ref: Comm-Footnote-1125679
+Node: Data126041
+Node: Def126358
+Node: Desc126590
+Node: Dim127090
+Node: Double127347
+Node: Eject127685
+Node: Else127860
+Node: Elseif128160
+Node: End128454
+Node: Endef128669
+Node: Endfunc128846
+Node: Endif129021
+Node: Equ129282
+Node: Equiv129796
+Node: Eqv130352
+Node: Err130716
+Node: Error131027
+Node: Exitm131472
+Node: Extern131641
+Node: Fail131902
+Node: File132347
+Node: Fill133676
+Node: Float134640
+Node: Func134982
+Node: Global135572
+Node: Gnu_attribute136329
+Node: Hidden136554
+Node: hword137140
+Node: Ident137468
+Node: If138042
+Node: Incbin141103
+Node: Include141797
+Node: Int142348
+Node: Internal142729
+Node: Irp143376
+Node: Irpc144255
+Node: Lcomm145171
+Node: Lflags145918
+Node: Line146112
+Node: Linkonce147028
+Node: List148257
+Node: Ln148864
+Node: Loc149014
+Node: Loc_mark_labels150399
+Node: Local150883
+Node: Long151495
+Node: Macro151673
+Node: MRI157604
+Node: Noaltmacro157942
+Node: Nolist158111
+Node: Octa158540
+Node: Offset158877
+Node: Org159204
+Node: P2align160489
+Node: PopSection162417
+Node: Previous162925
+Node: Print164337
+Node: Protected164566
+Node: Psize165213
+Node: Purgem165897
+Node: PushSection166118
+Node: Quad166862
+Node: Reloc167316
+Node: Rept168077
+Node: Sbttl168491
+Node: Scl168856
+Node: Section169197
+Node: Set175318
+Node: Short175891
+Node: Single176214
+Node: Size176561
+Node: Skip177229
+Node: Sleb128177553
+Node: Space177877
+Node: Stab178518
+Node: String180523
+Node: Struct181517
+Node: SubSection182242
+Node: Symver182805
+Node: Tag185201
+Node: Text185583
+Node: Title185905
+Node: Type186286
+Node: Uleb128188592
+Node: Val188916
+Node: Version189166
+Node: VTableEntry189440
+Node: VTableInherit189730
+Node: Warning190180
+Node: Weak190414
+Node: Weakref191083
+Node: Word192048
+Node: Deprecated193894
+Node: Object Attributes194128
+Node: GNU Object Attributes195848
+Node: Defining New Object Attributes198391
+Node: Machine Dependencies199183
+Node: AArch64-Dependent202961
+Node: AArch64 Options203407
+Node: AArch64 Syntax204038
+Node: AArch64-Chars204335
+Node: AArch64-Regs204821
+Node: AArch64-Relocations205115
+Node: AArch64 Floating Point206194
+Node: AArch64 Directives206419
+Node: AArch64 Opcodes207967
+Node: AArch64 Mapping Symbols208645
+Node: Alpha-Dependent209026
+Node: Alpha Notes209466
+Node: Alpha Options209747
+Node: Alpha Syntax212222
+Node: Alpha-Chars212691
+Node: Alpha-Regs213103
+Node: Alpha-Relocs213490
+Node: Alpha Floating Point219736
+Node: Alpha Directives219958
+Node: Alpha Opcodes225485
+Node: ARC-Dependent225780
+Node: ARC Options226163
+Node: ARC Syntax227234
+Node: ARC-Chars227466
+Node: ARC-Regs227947
+Node: ARC Floating Point228071
+Node: ARC Directives228382
+Node: ARC Opcodes234302
+Node: ARM-Dependent234528
+Node: ARM Options234993
+Node: ARM Syntax243839
+Node: ARM-Instruction-Set244207
+Node: ARM-Chars245422
+Node: ARM-Regs246133
+Node: ARM-Relocations246342
+Node: ARM-Neon-Alignment247477
+Node: ARM Floating Point247942
+Node: ARM Directives248141
+Ref: arm_pad249452
+Ref: arm_fnend252787
+Ref: arm_fnstart253106
+Ref: arm_save256115
+Ref: arm_setfp256816
+Node: ARM Opcodes260102
+Node: ARM Mapping Symbols262189
+Node: ARM Unwinding Tutorial262998
+Node: AVR-Dependent269198
+Node: AVR Options269488
+Node: AVR Syntax274375
+Node: AVR-Chars274662
+Node: AVR-Regs275221
+Node: AVR-Modifiers275802
+Node: AVR Opcodes277866
+Node: Blackfin-Dependent283112
+Node: Blackfin Options283424
+Node: Blackfin Syntax284398
+Node: Blackfin Directives290607
+Node: CR16-Dependent291348
+Node: CR16 Operand Qualifiers291648
+Node: CR16 Syntax294357
+Node: CR16-Chars294543
+Node: CRIS-Dependent295080
+Node: CRIS-Opts295426
+Ref: march-option297111
+Node: CRIS-Expand298930
+Node: CRIS-Symbols300113
+Node: CRIS-Syntax301284
+Node: CRIS-Chars301620
+Node: CRIS-Pic302171
+Ref: crispic302366
+Node: CRIS-Regs305915
+Node: CRIS-Pseudos306332
+Ref: crisnous307109
+Node: D10V-Dependent308397
+Node: D10V-Opts308748
+Node: D10V-Syntax309717
+Node: D10V-Size310246
+Node: D10V-Subs311217
+Node: D10V-Chars312252
+Node: D10V-Regs314063
+Node: D10V-Addressing315090
+Node: D10V-Word315768
+Node: D10V-Float316283
+Node: D10V-Opcodes316594
+Node: D30V-Dependent316987
+Node: D30V-Opts317344
+Node: D30V-Syntax318022
+Node: D30V-Size318556
+Node: D30V-Subs319529
+Node: D30V-Chars320566
+Node: D30V-Guarded323176
+Node: D30V-Regs323853
+Node: D30V-Addressing324972
+Node: D30V-Float325634
+Node: D30V-Opcodes325947
+Node: Epiphany-Dependent326342
+Node: Epiphany Options326630
+Node: Epiphany Syntax327029
+Node: Epiphany-Chars327230
+Node: H8/300-Dependent327784
+Node: H8/300 Options328200
+Node: H8/300 Syntax328466
+Node: H8/300-Chars328767
+Node: H8/300-Regs329066
+Node: H8/300-Addressing329985
+Node: H8/300 Floating Point331009
+Node: H8/300 Directives331336
+Node: H8/300 Opcodes332464
+Node: HPPA-Dependent340783
+Node: HPPA Notes341218
+Node: HPPA Options341976
+Node: HPPA Syntax342171
+Node: HPPA Floating Point343441
+Node: HPPA Directives343647
+Node: HPPA Opcodes352329
+Node: ESA/390-Dependent352588
+Node: ESA/390 Notes353048
+Node: ESA/390 Options353839
+Node: ESA/390 Syntax354049
+Node: ESA/390 Floating Point356222
+Node: ESA/390 Directives356501
+Node: ESA/390 Opcodes359791
+Node: i386-Dependent360053
+Node: i386-Options361380
+Node: i386-Directives366890
+Node: i386-Syntax367627
+Node: i386-Variations367932
+Node: i386-Chars370469
+Node: i386-Mnemonics371198
+Node: i386-Regs374508
+Node: i386-Prefixes376548
+Node: i386-Memory379308
+Node: i386-Jumps382247
+Node: i386-Float383370
+Node: i386-SIMD385202
+Node: i386-LWP386311
+Node: i386-BMI387145
+Node: i386-TBM387523
+Node: i386-16bit388053
+Node: i386-Bugs390124
+Node: i386-Arch390875
+Node: i386-Notes393995
+Node: i860-Dependent394854
+Node: Notes-i860395294
+Node: Options-i860396201
+Node: Directives-i860397561
+Node: Opcodes for i860398633
+Node: Syntax of i860400822
+Node: i860-Chars401006
+Node: i960-Dependent401565
+Node: Options-i960402012
+Node: Floating Point-i960405898
+Node: Directives-i960406166
+Node: Opcodes for i960408200
+Node: callj-i960408840
+Node: Compare-and-branch-i960409330
+Node: Syntax of i960411234
+Node: i960-Chars411434
+Node: IA-64-Dependent411977
+Node: IA-64 Options412278
+Node: IA-64 Syntax415429
+Node: IA-64-Chars415835
+Node: IA-64-Regs416065
+Node: IA-64-Bits416991
+Node: IA-64-Relocs417521
+Node: IA-64 Opcodes417992
+Node: IP2K-Dependent418264
+Node: IP2K-Opts418536
+Node: IP2K-Syntax419035
+Node: IP2K-Chars419209
+Node: LM32-Dependent419752
+Node: LM32 Options420047
+Node: LM32 Syntax420680
+Node: LM32-Regs420976
+Node: LM32-Modifiers421917
+Node: LM32-Chars423297
+Node: LM32 Opcodes423805
+Node: M32C-Dependent424109
+Node: M32C-Opts424615
+Node: M32C-Syntax425034
+Node: M32C-Modifiers425269
+Node: M32C-Chars427061
+Node: M32R-Dependent427627
+Node: M32R-Opts427948
+Node: M32R-Directives432110
+Node: M32R-Warnings436084
+Node: M68K-Dependent439089
+Node: M68K-Opts439556
+Node: M68K-Syntax446978
+Node: M68K-Moto-Syntax448818
+Node: M68K-Float451402
+Node: M68K-Directives451922
+Node: M68K-opcodes453249
+Node: M68K-Branch453475
+Node: M68K-Chars457668
+Node: M68HC11-Dependent458531
+Node: M68HC11-Opts459062
+Node: M68HC11-Syntax463374
+Node: M68HC11-Modifiers466168
+Node: M68HC11-Directives467995
+Node: M68HC11-Float469369
+Node: M68HC11-opcodes469897
+Node: M68HC11-Branch470079
+Node: Meta-Dependent472528
+Node: Meta Options472813
+Node: Meta Syntax473475
+Node: Meta-Chars473687
+Node: Meta-Regs473987
+Node: MicroBlaze-Dependent474263
+Node: MicroBlaze Directives474950
+Node: MicroBlaze Syntax476341
+Node: MicroBlaze-Chars476573
+Node: MIPS-Dependent477125
+Node: MIPS Options478511
+Node: MIPS Macros491670
+Ref: MIPS Macros-Footnote-1494384
+Node: MIPS Symbol Sizes494527
+Node: MIPS Small Data496199
+Node: MIPS ISA498363
+Node: MIPS assembly options500111
+Node: MIPS autoextend500680
+Node: MIPS insn501414
+Node: MIPS NaN Encodings502700
+Node: MIPS Option Stack504658
+Node: MIPS ASE Instruction Generation Overrides505443
+Node: MIPS Floating-Point507731
+Node: MIPS Syntax508637
+Node: MIPS-Chars508899
+Node: MMIX-Dependent509441
+Node: MMIX-Opts509821
+Node: MMIX-Expand513426
+Node: MMIX-Syntax514738
+Ref: mmixsite515094
+Node: MMIX-Chars515936
+Node: MMIX-Symbols516809
+Node: MMIX-Regs518880
+Node: MMIX-Pseudos519905
+Ref: MMIX-loc520047
+Ref: MMIX-local521128
+Ref: MMIX-is521661
+Ref: MMIX-greg521933
+Ref: GREG-base522851
+Ref: MMIX-byte524170
+Ref: MMIX-constants524642
+Ref: MMIX-prefix525284
+Ref: MMIX-spec525659
+Node: MMIX-mmixal525993
+Node: MSP430-Dependent529488
+Node: MSP430 Options529958
+Node: MSP430 Syntax531292
+Node: MSP430-Macros531608
+Node: MSP430-Chars532338
+Node: MSP430-Regs533053
+Node: MSP430-Ext533614
+Node: MSP430 Floating Point535433
+Node: MSP430 Directives535657
+Node: MSP430 Opcodes536529
+Node: MSP430 Profiling Capability536924
+Node: NiosII-Dependent539252
+Node: Nios II Options539672
+Node: Nios II Syntax540586
+Node: Nios II Chars540792
+Node: Nios II Relocations540983
+Node: Nios II Directives542458
+Node: Nios II Opcodes544020
+Node: NS32K-Dependent544295
+Node: NS32K Syntax544522
+Node: NS32K-Chars544671
+Node: PDP-11-Dependent545411
+Node: PDP-11-Options545801
+Node: PDP-11-Pseudos550860
+Node: PDP-11-Syntax551205
+Node: PDP-11-Mnemonics552037
+Node: PDP-11-Synthetic552339
+Node: PJ-Dependent552557
+Node: PJ Options552820
+Node: PJ Syntax553115
+Node: PJ-Chars553280
+Node: PPC-Dependent553829
+Node: PowerPC-Opts554162
+Node: PowerPC-Pseudo557657
+Node: PowerPC-Syntax558278
+Node: PowerPC-Chars558468
+Node: RL78-Dependent559219
+Node: RL78-Opts559617
+Node: RL78-Modifiers559891
+Node: RL78-Directives560670
+Node: RL78-Syntax561167
+Node: RL78-Chars561363
+Node: RX-Dependent561919
+Node: RX-Opts562350
+Node: RX-Modifiers565751
+Node: RX-Directives566854
+Node: RX-Float567593
+Node: RX-Syntax568228
+Node: RX-Chars568407
+Node: S/390-Dependent568959
+Node: s390 Options569674
+Node: s390 Characters571222
+Node: s390 Syntax571743
+Node: s390 Register572645
+Node: s390 Mnemonics573461
+Node: s390 Operands576483
+Node: s390 Formats579113
+Node: s390 Aliases586960
+Node: s390 Operand Modifier590925
+Node: s390 Instruction Marker594728
+Node: s390 Literal Pool Entries595742
+Node: s390 Directives597675
+Node: s390 Floating Point602733
+Node: SCORE-Dependent603181
+Node: SCORE-Opts603483
+Node: SCORE-Pseudo604770
+Node: SCORE-Syntax606852
+Node: SCORE-Chars607034
+Node: SH-Dependent607592
+Node: SH Options608003
+Node: SH Syntax609054
+Node: SH-Chars609327
+Node: SH-Regs609870
+Node: SH-Addressing610484
+Node: SH Floating Point611392
+Node: SH Directives612489
+Node: SH Opcodes612890
+Node: SH64-Dependent617211
+Node: SH64 Options617573
+Node: SH64 Syntax619364
+Node: SH64-Chars619647
+Node: SH64-Regs620196
+Node: SH64-Addressing621292
+Node: SH64 Directives622477
+Node: SH64 Opcodes623461
+Node: Sparc-Dependent624176
+Node: Sparc-Opts624587
+Node: Sparc-Aligned-Data629254
+Node: Sparc-Syntax630086
+Node: Sparc-Chars630660
+Node: Sparc-Regs631223
+Node: Sparc-Constants636334
+Node: Sparc-Relocs641094
+Node: Sparc-Size-Translations646212
+Node: Sparc-Float647862
+Node: Sparc-Directives648057
+Node: TIC54X-Dependent650019
+Node: TIC54X-Opts650782
+Node: TIC54X-Block651823
+Node: TIC54X-Env652183
+Node: TIC54X-Constants652531
+Node: TIC54X-Subsyms652927
+Node: TIC54X-Locals654831
+Node: TIC54X-Builtins655571
+Node: TIC54X-Ext657985
+Node: TIC54X-Directives658556
+Node: TIC54X-Macros669464
+Node: TIC54X-MMRegs671551
+Node: TIC54X-Syntax671788
+Node: TIC54X-Chars671978
+Node: TIC6X-Dependent672669
+Node: TIC6X Options672972
+Node: TIC6X Syntax674971
+Node: TIC6X Directives676074
+Node: TILE-Gx-Dependent678359
+Node: TILE-Gx Options678669
+Node: TILE-Gx Syntax679018
+Node: TILE-Gx Opcodes681254
+Node: TILE-Gx Registers681542
+Node: TILE-Gx Modifiers682313
+Node: TILE-Gx Directives687311
+Node: TILEPro-Dependent688214
+Node: TILEPro Options688522
+Node: TILEPro Syntax688706
+Node: TILEPro Opcodes690942
+Node: TILEPro Registers691233
+Node: TILEPro Modifiers692003
+Node: TILEPro Directives696791
+Node: Z80-Dependent697694
+Node: Z80 Options698083
+Node: Z80 Syntax699502
+Node: Z80-Chars700174
+Node: Z80-Regs701025
+Node: Z80-Case701377
+Node: Z80 Floating Point701822
+Node: Z80 Directives702016
+Node: Z80 Opcodes703641
+Node: Z8000-Dependent704987
+Node: Z8000 Options705945
+Node: Z8000 Syntax706162
+Node: Z8000-Chars706452
+Node: Z8000-Regs706934
+Node: Z8000-Addressing707724
+Node: Z8000 Directives708834
+Node: Z8000 Opcodes710438
+Node: Vax-Dependent720380
+Node: VAX-Opts720963
+Node: VAX-float724684
+Node: VAX-directives725317
+Node: VAX-opcodes726177
+Node: VAX-branch726566
+Node: VAX-operands729070
+Node: VAX-no729833
+Node: VAX-Syntax730089
+Node: VAX-Chars730255
+Node: V850-Dependent730809
+Node: V850 Options731203
+Node: V850 Syntax734847
+Node: V850-Chars735087
+Node: V850-Regs735631
+Node: V850 Floating Point737141
+Node: V850 Directives737347
+Node: V850 Opcodes739413
+Node: XGATE-Dependent745292
+Node: XGATE-Opts745712
+Node: XGATE-Syntax746701
+Node: XGATE-Directives748782
+Node: XGATE-Float749021
+Node: XGATE-opcodes749518
+Node: XSTORMY16-Dependent749630
+Node: XStormy16 Syntax749976
+Node: XStormy16-Chars750166
+Node: XStormy16 Directives750779
+Node: XStormy16 Opcodes751433
+Node: Xtensa-Dependent752488
+Node: Xtensa Options753219
+Node: Xtensa Syntax755950
+Node: Xtensa Opcodes758094
+Node: Xtensa Registers759887
+Node: Xtensa Optimizations760520
+Node: Density Instructions760972
+Node: Xtensa Automatic Alignment762074
+Node: Xtensa Relaxation764521
+Node: Xtensa Branch Relaxation765429
+Node: Xtensa Call Relaxation766801
+Node: Xtensa Immediate Relaxation768587
+Node: Xtensa Directives771162
+Node: Schedule Directive772870
+Node: Longcalls Directive773210
+Node: Transform Directive773754
+Node: Literal Directive774496
+Ref: Literal Directive-Footnote-1778035
+Node: Literal Position Directive778177
+Node: Literal Prefix Directive779876
+Node: Absolute Literals Directive780774
+Node: Reporting Bugs782081
+Node: Bug Criteria782807
+Node: Bug Reporting783574
+Node: Acknowledgements790218
+Ref: Acknowledgements-Footnote-1795184
+Node: GNU Free Documentation License795210
+Node: AS Index820359
 
 End Tag Table
diff --git a/share/info/bfd.info b/share/info/bfd.info
index 4cf2e73..e4532fe 100644
--- a/share/info/bfd.info
+++ b/share/info/bfd.info
@@ -1,12 +1,6 @@
-This is bfd.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/bfd/doc/bfd.texinfo.
+This is bfd.info, produced by makeinfo version 5.1 from bfd.texinfo.
 
-INFO-DIR-SECTION Software development
-START-INFO-DIR-ENTRY
-* Bfd: (bfd).                   The Binary File Descriptor library.
-END-INFO-DIR-ENTRY
-
-   This file documents the BFD library.
+This file documents the BFD library.
 
    Copyright (C) 1991 - 2013 Free Software Foundation, Inc.
 
@@ -25,13 +19,17 @@ included in the section entitled "GNU Free Documentation License".
    (b) The FSF's Back-Cover Text is:
 
    You have freedom to copy and modify this GNU Manual, like GNU
-software.  Copies published by the Free Software Foundation raise
-funds for GNU development.
+software.  Copies published by the Free Software Foundation raise funds
+for GNU development.
+INFO-DIR-SECTION Software development
+START-INFO-DIR-ENTRY
+* Bfd: (bfd).                   The Binary File Descriptor library.
+END-INFO-DIR-ENTRY
 
 
 File: bfd.info,  Node: Top,  Next: Overview,  Prev: (dir),  Up: (dir)
 
-   This file documents the binary file descriptor library libbfd.
+This file documents the binary file descriptor library libbfd.
 
 * Menu:
 
@@ -54,15 +52,14 @@ adding it to the library.
 
    BFD is split into two parts: the front end, and the back ends (one
 for each object file format).
-   * The front end of BFD provides the interface to the user. It manages
-     memory and various canonical data structures. The front end also
-     decides which back end to use and when to call back end routines.
-
-   * The back ends provide BFD its view of the real world. Each back
+   * The front end of BFD provides the interface to the user.  It
+     manages memory and various canonical data structures.  The front
+     end also decides which back end to use and when to call back end
+     routines.
+   * The back ends provide BFD its view of the real world.  Each back
      end provides a set of calls which the BFD front end can use to
-     maintain its canonical form. The back ends also may keep around
+     maintain its canonical form.  The back ends also may keep around
      information for their own use, for greater efficiency.
-
 * Menu:
 
 * History::			History
@@ -82,16 +79,16 @@ was contracted to provide the required functionality.
 
    The name came from a conversation David Wallace was having with
 Richard Stallman about the library: RMS said that it would be quite
-hard--David said "BFD".  Stallman was right, but the name stuck.
+hard--David said "BFD". Stallman was right, but the name stuck.
 
    At the same time, Ready Systems wanted much the same thing, but for
 different object file formats: IEEE-695, Oasys, Srecords, a.out and 68k
 coff.
 
    BFD was first implemented by members of Cygnus Support; Steve
-Chamberlain (`sac@cygnus.com'), John Gilmore (`gnu@cygnus.com'), K.
-Richard Pixley (`rich@cygnus.com') and David Henkel-Wallace
-(`gumby@cygnus.com').
+Chamberlain ('sac@cygnus.com'), John Gilmore ('gnu@cygnus.com'), K.
+Richard Pixley ('rich@cygnus.com') and David Henkel-Wallace
+('gumby@cygnus.com').
 
 
 File: bfd.info,  Node: How It Works,  Next: What BFD Version 2 Can Do,  Prev: History,  Up: Overview
@@ -99,23 +96,22 @@ File: bfd.info,  Node: How It Works,  Next: What BFD Version 2 Can Do,  Prev: Hi
 1.2 How To Use BFD
 ==================
 
-To use the library, include `bfd.h' and link with `libbfd.a'.
+To use the library, include 'bfd.h' and link with 'libbfd.a'.
 
    BFD provides a common interface to the parts of an object file for a
 calling application.
 
    When an application successfully opens a target file (object,
 archive, or whatever), a pointer to an internal structure is returned.
-This pointer points to a structure called `bfd', described in `bfd.h'.
-Our convention is to call this pointer a BFD, and instances of it
-within code `abfd'.  All operations on the target object file are
-applied as methods to the BFD.  The mapping is defined within `bfd.h'
-in a set of macros, all beginning with `bfd_' to reduce namespace
-pollution.
+This pointer points to a structure called 'bfd', described in 'bfd.h'.
+Our convention is to call this pointer a BFD, and instances of it within
+code 'abfd'.  All operations on the target object file are applied as
+methods to the BFD. The mapping is defined within 'bfd.h' in a set of
+macros, all beginning with 'bfd_' to reduce namespace pollution.
 
    For example, this sequence does what you would probably expect:
 return the number of sections in an object file attached to a BFD
-`abfd'.
+'abfd'.
 
      #include "bfd.h"
 
@@ -128,15 +124,12 @@ return the number of sections in an object file attached to a BFD
    The abstraction used within BFD is that an object file has:
 
    * a header,
-
    * a number of sections containing raw data (*note Sections::),
-
    * a set of relocations (*note Relocations::), and
-
    * some symbol information (*note Symbols::).
-   Also, BFDs opened for archives have the additional attribute of an
-index and contain subordinate BFDs. This approach is fine for a.out and
-coff, but loses efficiency when applied to formats such as S-records and
+Also, BFDs opened for archives have the additional attribute of an index
+and contain subordinate BFDs.  This approach is fine for a.out and coff,
+but loses efficiency when applied to formats such as S-records and
 IEEE-695.
 
 
@@ -150,18 +143,18 @@ the format of the input object file.  They then build a descriptor in
 memory with pointers to routines that will be used to access elements of
 the object file's data structures.
 
-   As different information from the object files is required, BFD
-reads from different sections of the file and processes them.  For
-example, a very common operation for the linker is processing symbol
-tables.  Each BFD back end provides a routine for converting between
-the object file's representation of symbols and an internal canonical
-format. When the linker asks for the symbol table of an object file, it
-calls through a memory pointer to the routine from the relevant BFD
-back end which reads and converts the table into a canonical form.  The
-linker then operates upon the canonical form. When the link is finished
-and the linker writes the output file's symbol table, another BFD back
-end routine is called to take the newly created symbol table and
-convert it into the chosen output format.
+   As different information from the object files is required, BFD reads
+from different sections of the file and processes them.  For example, a
+very common operation for the linker is processing symbol tables.  Each
+BFD back end provides a routine for converting between the object file's
+representation of symbols and an internal canonical format.  When the
+linker asks for the symbol table of an object file, it calls through a
+memory pointer to the routine from the relevant BFD back end which reads
+and converts the table into a canonical form.  The linker then operates
+upon the canonical form.  When the link is finished and the linker
+writes the output file's symbol table, another BFD back end routine is
+called to take the newly created symbol table and convert it into the
+chosen output format.
 
 * Menu:
 
@@ -174,25 +167,25 @@ File: bfd.info,  Node: BFD information loss,  Next: Canonical format,  Up: What
 1.3.1 Information Loss
 ----------------------
 
-_Information can be lost during output._ The output formats supported
-by BFD do not provide identical facilities, and information which can
-be described in one form has nowhere to go in another format. One
-example of this is alignment information in `b.out'. There is nowhere
-in an `a.out' format file to store alignment information on the
-contained data, so when a file is linked from `b.out' and an `a.out'
-image is produced, alignment information will not propagate to the
-output file. (The linker will still use the alignment information
-internally, so the link is performed correctly).
-
-   Another example is COFF section names. COFF files may contain an
-unlimited number of sections, each one with a textual section name. If
+_Information can be lost during output._  The output formats supported
+by BFD do not provide identical facilities, and information which can be
+described in one form has nowhere to go in another format.  One example
+of this is alignment information in 'b.out'.  There is nowhere in an
+'a.out' format file to store alignment information on the contained
+data, so when a file is linked from 'b.out' and an 'a.out' image is
+produced, alignment information will not propagate to the output file.
+(The linker will still use the alignment information internally, so the
+link is performed correctly).
+
+   Another example is COFF section names.  COFF files may contain an
+unlimited number of sections, each one with a textual section name.  If
 the target of the link is a format which does not have many sections
-(e.g., `a.out') or has sections without names (e.g., the Oasys format),
-the link cannot be done simply. You can circumvent this problem by
+(e.g., 'a.out') or has sections without names (e.g., the Oasys format),
+the link cannot be done simply.  You can circumvent this problem by
 describing the desired input-to-output section mapping with the linker
 command language.
 
-   _Information can be lost during canonicalization._ The BFD internal
+   _Information can be lost during canonicalization._  The BFD internal
 canonical form of the external formats is not exhaustive; there are
 structures in input formats for which there is no direct representation
 internally.  This means that the BFD back ends cannot maintain all
@@ -203,16 +196,16 @@ internal and back to external formats.
 format and writes another.  Each BFD back end is responsible for
 maintaining as much data as possible, and the internal BFD canonical
 form has structures which are opaque to the BFD core, and exported only
-to the back ends. When a file is read in one format, the canonical form
-is generated for BFD and the application. At the same time, the back
-end saves away any information which may otherwise be lost. If the data
+to the back ends.  When a file is read in one format, the canonical form
+is generated for BFD and the application.  At the same time, the back
+end saves away any information which may otherwise be lost.  If the data
 is then written back in the same format, the back end routine will be
 able to use the canonical form provided by the BFD core as well as the
 information it prepared earlier.  Since there is a great deal of
-commonality between back ends, there is no information lost when
-linking or copying big endian COFF to little endian COFF, or `a.out' to
-`b.out'.  When a mixture of formats is linked, the information is only
-lost from the files whose format differs from the destination.
+commonality between back ends, there is no information lost when linking
+or copying big endian COFF to little endian COFF, or 'a.out' to 'b.out'.
+When a mixture of formats is linked, the information is only lost from
+the files whose format differs from the destination.
 
 
 File: bfd.info,  Node: Canonical format,  Prev: BFD information loss,  Up: What BFD Version 2 Can Do
@@ -223,16 +216,16 @@ File: bfd.info,  Node: Canonical format,  Prev: BFD information loss,  Up: What
 The greatest potential for loss of information occurs when there is the
 least overlap between the information provided by the source format,
 that stored by the canonical format, and that needed by the destination
-format. A brief description of the canonical form may help you
+format.  A brief description of the canonical form may help you
 understand which kinds of data you can count on preserving across
-conversions.  
+conversions.
 
 _files_
      Information stored on a per-file basis includes target machine
      architecture, particular implementation format type, a demand
      pageable bit, and a write protected bit.  Information like Unix
      magic numbers is not stored here--only the magic numbers' meaning,
-     so a `ZMAGIC' file would have both the demand pageable bit and the
+     so a 'ZMAGIC' file would have both the demand pageable bit and the
      write protected text bit set.  The byte order of the target is
      stored on a per-file basis, so that big- and little-endian object
      files may be used with one another.
@@ -251,14 +244,14 @@ _symbols_
      section where they were defined.  Doing this ensures that each
      symbol points to its containing section.  Each symbol also has a
      varying amount of hidden private data for the BFD back end.  Since
-     the symbol points to the original file, the private data format
-     for that symbol is accessible.  `ld' can operate on a collection
-     of symbols of wildly different formats without problems.
-
-     Normal global and simple local symbols are maintained on output,
-     so an output file (no matter its format) will retain symbols
-     pointing to functions and to global, static, and common variables.
-     Some symbol information is not worth retaining; in `a.out', type
+     the symbol points to the original file, the private data format for
+     that symbol is accessible.  'ld' can operate on a collection of
+     symbols of wildly different formats without problems.
+
+     Normal global and simple local symbols are maintained on output, so
+     an output file (no matter its format) will retain symbols pointing
+     to functions and to global, static, and common variables.  Some
+     symbol information is not worth retaining; in 'a.out', type
      information is stored in the symbol table as long symbol names.
      This information would be useless to most COFF debuggers; the
      linker has command line switches to allow users to throw it away.
@@ -266,17 +259,17 @@ _symbols_
      There is one word of type information within the symbol, so if the
      format supports symbol type information within symbols (for
      example, COFF, IEEE, Oasys) and the type is simple enough to fit
-     within one word (nearly everything but aggregates), the
-     information will be preserved.
+     within one word (nearly everything but aggregates), the information
+     will be preserved.
 
 _relocation level_
      Each canonical BFD relocation record contains a pointer to the
      symbol to relocate to, the offset of the data to relocate, the
      section the data is in, and a pointer to a relocation type
-     descriptor. Relocation is performed by passing messages through
-     the relocation type descriptor and the symbol pointer. Therefore,
+     descriptor.  Relocation is performed by passing messages through
+     the relocation type descriptor and the symbol pointer.  Therefore,
      relocations can be performed on output data using a relocation
-     method that is only available in one of the input formats. For
+     method that is only available in one of the input formats.  For
      instance, Oasys provides a byte relocation format.  A relocation
      record requesting this relocation type would point indirectly to a
      routine to perform this, so the relocation may be performed on a
@@ -288,13 +281,13 @@ _line numbers_
      mapping between symbols, source line numbers, and addresses in the
      output file.  These addresses have to be relocated along with the
      symbol information.  Each symbol with an associated list of line
-     number records points to the first record of the list.  The head
-     of a line number list consists of a pointer to the symbol, which
-     allows finding out the address of the function whose line number
-     is being described. The rest of the list is made up of pairs:
-     offsets into the section and line numbers. Any format which can
-     simply derive this information can pass it successfully between
-     formats (COFF, IEEE and Oasys).
+     number records points to the first record of the list.  The head of
+     a line number list consists of a pointer to the symbol, which
+     allows finding out the address of the function whose line number is
+     being described.  The rest of the list is made up of pairs: offsets
+     into the section and line numbers.  Any format which can simply
+     derive this information can pass it successfully between formats
+     (COFF, IEEE and Oasys).
 
 
 File: bfd.info,  Node: BFD front end,  Next: BFD back ends,  Prev: Overview,  Up: Top
@@ -326,14 +319,14 @@ File: bfd.info,  Node: BFD front end,  Next: BFD back ends,  Prev: Overview,  Up
 
 File: bfd.info,  Node: typedef bfd,  Next: Error reporting,  Prev: BFD front end,  Up: BFD front end
 
-2.1 `typedef bfd'
+2.1 'typedef bfd'
 =================
 
-A BFD has type `bfd'; objects of this type are the cornerstone of any
+A BFD has type 'bfd'; objects of this type are the cornerstone of any
 application using BFD. Using BFD consists of making references though
 the BFD and to data in the BFD.
 
-   Here is the structure that defines the type `bfd'.  It contains the
+   Here is the structure that defines the type 'bfd'.  It contains the
 major data about the file and pointers to the rest of the data.
 
 
@@ -345,14 +338,6 @@ major data about the file and pointers to the rest of the data.
          both_direction = 3
        };
 
-     enum bfd_lto_object_type
-       {
-         lto_non_object,
-         lto_non_ir_object,
-         lto_ir_object,
-         lto_mixed_object
-       };
-
      struct bfd
      {
        /* A unique identifier of the BFD  */
@@ -500,9 +485,6 @@ major data about the file and pointers to the rest of the data.
        /* The last section on the section list.  */
        struct bfd_section *section_last;
 
-       /* The object-only section on the section list.  */
-       struct bfd_section *object_only_section;
-
        /* The number of sections.  */
        unsigned int section_count;
 
@@ -621,11 +603,16 @@ major data about the file and pointers to the rest of the data.
        /* Set if only required symbols should be added in the link hash table for
           this object.  Used by VMS linkers.  */
        unsigned int selective_search : 1;
-
-       /* LTO object type.  */
-       unsigned int lto_type : 2;
      };
 
+     /* See note beside bfd_set_section_userdata.  */
+     static inline bfd_boolean
+     bfd_set_cacheable (bfd * abfd, bfd_boolean val)
+     {
+       abfd->cacheable = val;
+       return TRUE;
+     }
+
 
 File: bfd.info,  Node: Error reporting,  Next: Miscellaneous,  Prev: typedef bfd,  Up: BFD front end
 
@@ -634,18 +621,18 @@ File: bfd.info,  Node: Error reporting,  Next: Miscellaneous,  Prev: typedef bfd
 
 Most BFD functions return nonzero on success (check their individual
 documentation for precise semantics).  On an error, they call
-`bfd_set_error' to set an error condition that callers can check by
-calling `bfd_get_error'.  If that returns `bfd_error_system_call', then
-check `errno'.
+'bfd_set_error' to set an error condition that callers can check by
+calling 'bfd_get_error'.  If that returns 'bfd_error_system_call', then
+check 'errno'.
 
    The easiest way to report a BFD error to the user is to use
-`bfd_perror'.
+'bfd_perror'.
 
-2.2.1 Type `bfd_error_type'
+2.2.1 Type 'bfd_error_type'
 ---------------------------
 
-The values returned by `bfd_get_error' are defined by the enumerated
-type `bfd_error_type'.
+The values returned by 'bfd_get_error' are defined by the enumerated
+type 'bfd_error_type'.
 
 
      typedef enum bfd_error
@@ -674,8 +661,8 @@ type `bfd_error_type'.
        bfd_error_invalid_error_code
      }
      bfd_error_type;
-   
-2.2.1.1 `bfd_get_error'
+
+2.2.1.1 'bfd_get_error'
 .......................
 
 *Synopsis*
@@ -683,7 +670,7 @@ type `bfd_error_type'.
    *Description*
 Return the current BFD error condition.
 
-2.2.1.2 `bfd_set_error'
+2.2.1.2 'bfd_set_error'
 .......................
 
 *Synopsis*
@@ -693,16 +680,16 @@ Set the BFD error condition to be ERROR_TAG.  If ERROR_TAG is
 bfd_error_on_input, then this function takes two more parameters, the
 input bfd where the error occurred, and the bfd_error_type error.
 
-2.2.1.3 `bfd_errmsg'
+2.2.1.3 'bfd_errmsg'
 ....................
 
 *Synopsis*
      const char *bfd_errmsg (bfd_error_type error_tag);
    *Description*
 Return a string describing the error ERROR_TAG, or the system error if
-ERROR_TAG is `bfd_error_system_call'.
+ERROR_TAG is 'bfd_error_system_call'.
 
-2.2.1.4 `bfd_perror'
+2.2.1.4 'bfd_perror'
 ....................
 
 *Synopsis*
@@ -725,8 +712,8 @@ the program.
 
 
      typedef void (*bfd_error_handler_type) (const char *, ...);
-   
-2.2.2.1 `bfd_set_error_handler'
+
+2.2.2.1 'bfd_set_error_handler'
 ...............................
 
 *Synopsis*
@@ -734,17 +721,17 @@ the program.
    *Description*
 Set the BFD error handler function.  Returns the previous function.
 
-2.2.2.2 `bfd_set_error_program_name'
+2.2.2.2 'bfd_set_error_program_name'
 ....................................
 
 *Synopsis*
      void bfd_set_error_program_name (const char *);
    *Description*
 Set the program name to use when printing a BFD error.  This is printed
-before the error message followed by a colon and space.  The string
-must not be changed after it is passed to this function.
+before the error message followed by a colon and space.  The string must
+not be changed after it is passed to this function.
 
-2.2.2.3 `bfd_get_error_handler'
+2.2.2.3 'bfd_get_error_handler'
 ...............................
 
 *Synopsis*
@@ -755,11 +742,11 @@ Return the BFD error handler function.
 2.2.3 BFD assert handler
 ------------------------
 
-If BFD finds an internal inconsistency, the bfd assert handler is
-called with information on the BFD version, BFD source file and line.
-If this happens, most programs linked against BFD are expected to want
-to exit with an error, or mark the current BFD operation as failed, so
-it is recommended to override the default handler, which just calls
+If BFD finds an internal inconsistency, the bfd assert handler is called
+with information on the BFD version, BFD source file and line.  If this
+happens, most programs linked against BFD are expected to want to exit
+with an error, or mark the current BFD operation as failed, so it is
+recommended to override the default handler, which just calls
 _bfd_error_handler and continues.
 
 
@@ -767,8 +754,8 @@ _bfd_error_handler and continues.
                                               const char *bfd_version,
                                               const char *bfd_file,
                                               int bfd_line);
-   
-2.2.3.1 `bfd_set_assert_handler'
+
+2.2.3.1 'bfd_set_assert_handler'
 ................................
 
 *Synopsis*
@@ -776,7 +763,7 @@ _bfd_error_handler and continues.
    *Description*
 Set the BFD assert handler function.  Returns the previous function.
 
-2.2.3.2 `bfd_get_assert_handler'
+2.2.3.2 'bfd_get_assert_handler'
 ................................
 
 *Synopsis*
@@ -793,7 +780,7 @@ File: bfd.info,  Node: Miscellaneous,  Next: Memory Usage,  Prev: Error reportin
 2.3.1 Miscellaneous functions
 -----------------------------
 
-2.3.1.1 `bfd_get_reloc_upper_bound'
+2.3.1.1 'bfd_get_reloc_upper_bound'
 ...................................
 
 *Synopsis*
@@ -803,7 +790,7 @@ Return the number of bytes required to store the relocation information
 associated with section SECT attached to bfd ABFD.  If an error occurs,
 return -1.
 
-2.3.1.2 `bfd_canonicalize_reloc'
+2.3.1.2 'bfd_canonicalize_reloc'
 ................................
 
 *Synopsis*
@@ -813,12 +800,12 @@ return -1.
 Call the back end associated with the open BFD ABFD and translate the
 external form of the relocation information attached to SEC into the
 internal canonical form.  Place the table into memory at LOC, which has
-been preallocated, usually by a call to `bfd_get_reloc_upper_bound'.
+been preallocated, usually by a call to 'bfd_get_reloc_upper_bound'.
 Returns the number of relocs, or -1 on error.
 
    The SYMS table is also needed for horrible internal magic reasons.
 
-2.3.1.3 `bfd_set_reloc'
+2.3.1.3 'bfd_set_reloc'
 .......................
 
 *Synopsis*
@@ -828,7 +815,7 @@ Returns the number of relocs, or -1 on error.
 Set the relocation pointer and count within section SEC to the values
 REL and COUNT.  The argument ABFD is ignored.
 
-2.3.1.4 `bfd_set_file_flags'
+2.3.1.4 'bfd_set_file_flags'
 ............................
 
 *Synopsis*
@@ -837,17 +824,16 @@ REL and COUNT.  The argument ABFD is ignored.
 Set the flag word in the BFD ABFD to the value FLAGS.
 
    Possible errors are:
-   * `bfd_error_wrong_format' - The target bfd was not of object format.
 
-   * `bfd_error_invalid_operation' - The target bfd was open for
+   * 'bfd_error_wrong_format' - The target bfd was not of object format.
+   * 'bfd_error_invalid_operation' - The target bfd was open for
      reading.
+   * 'bfd_error_invalid_operation' - The flag word contained a bit which
+     was not applicable to the type of file.  E.g., an attempt was made
+     to set the 'D_PAGED' bit on a BFD format which does not support
+     demand paging.
 
-   * `bfd_error_invalid_operation' - The flag word contained a bit
-     which was not applicable to the type of file.  E.g., an attempt
-     was made to set the `D_PAGED' bit on a BFD format which does not
-     support demand paging.
-
-2.3.1.5 `bfd_get_arch_size'
+2.3.1.5 'bfd_get_arch_size'
 ...........................
 
 *Synopsis*
@@ -858,9 +844,9 @@ object file's format.  For ELF, this information is included in the
 header.
 
    *Returns*
-Returns the arch size in bits if known, `-1' otherwise.
+Returns the arch size in bits if known, '-1' otherwise.
 
-2.3.1.6 `bfd_get_sign_extend_vma'
+2.3.1.6 'bfd_get_sign_extend_vma'
 .................................
 
 *Synopsis*
@@ -873,11 +859,11 @@ instance, bfd_get_start_address() will return an address sign extended
 to fill a bfd_vma when this is the case.
 
    *Returns*
-Returns `1' if the target architecture is known to sign extend
-addresses, `0' if the target architecture is known to not sign extend
-addresses, and `-1' otherwise.
+Returns '1' if the target architecture is known to sign extend
+addresses, '0' if the target architecture is known to not sign extend
+addresses, and '-1' otherwise.
 
-2.3.1.7 `bfd_set_start_address'
+2.3.1.7 'bfd_set_start_address'
 ...............................
 
 *Synopsis*
@@ -886,45 +872,45 @@ addresses, and `-1' otherwise.
 Make VMA the entry point of output BFD ABFD.
 
    *Returns*
-Returns `TRUE' on success, `FALSE' otherwise.
+Returns 'TRUE' on success, 'FALSE' otherwise.
 
-2.3.1.8 `bfd_get_gp_size'
+2.3.1.8 'bfd_get_gp_size'
 .........................
 
 *Synopsis*
      unsigned int bfd_get_gp_size (bfd *abfd);
    *Description*
-Return the maximum size of objects to be optimized using the GP
-register under MIPS ECOFF.  This is typically set by the `-G' argument
-to the compiler, assembler or linker.
+Return the maximum size of objects to be optimized using the GP register
+under MIPS ECOFF. This is typically set by the '-G' argument to the
+compiler, assembler or linker.
 
-2.3.1.9 `bfd_set_gp_size'
+2.3.1.9 'bfd_set_gp_size'
 .........................
 
 *Synopsis*
      void bfd_set_gp_size (bfd *abfd, unsigned int i);
    *Description*
 Set the maximum size of objects to be optimized using the GP register
-under ECOFF or MIPS ELF.  This is typically set by the `-G' argument to
+under ECOFF or MIPS ELF. This is typically set by the '-G' argument to
 the compiler, assembler or linker.
 
-2.3.1.10 `bfd_scan_vma'
+2.3.1.10 'bfd_scan_vma'
 .......................
 
 *Synopsis*
      bfd_vma bfd_scan_vma (const char *string, const char **end, int base);
    *Description*
-Convert, like `strtoul', a numerical expression STRING into a `bfd_vma'
+Convert, like 'strtoul', a numerical expression STRING into a 'bfd_vma'
 integer, and return that integer.  (Though without as many bells and
-whistles as `strtoul'.)  The expression is assumed to be unsigned
-(i.e., positive).  If given a BASE, it is used as the base for
-conversion.  A base of 0 causes the function to interpret the string in
-hex if a leading "0x" or "0X" is found, otherwise in octal if a leading
-zero is found, otherwise in decimal.
+whistles as 'strtoul'.)  The expression is assumed to be unsigned (i.e.,
+positive).  If given a BASE, it is used as the base for conversion.  A
+base of 0 causes the function to interpret the string in hex if a
+leading "0x" or "0X" is found, otherwise in octal if a leading zero is
+found, otherwise in decimal.
 
-   If the value would overflow, the maximum `bfd_vma' value is returned.
+   If the value would overflow, the maximum 'bfd_vma' value is returned.
 
-2.3.1.11 `bfd_copy_private_header_data'
+2.3.1.11 'bfd_copy_private_header_data'
 .......................................
 
 *Synopsis*
@@ -932,65 +918,61 @@ zero is found, otherwise in decimal.
    *Description*
 Copy private BFD header information from the BFD IBFD to the the BFD
 OBFD.  This copies information that may require sections to exist, but
-does not require symbol tables.  Return `true' on success, `false' on
+does not require symbol tables.  Return 'true' on success, 'false' on
 error.  Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OBFD.
-
      #define bfd_copy_private_header_data(ibfd, obfd) \
           BFD_SEND (obfd, _bfd_copy_private_header_data, \
                     (ibfd, obfd))
 
-2.3.1.12 `bfd_copy_private_bfd_data'
+2.3.1.12 'bfd_copy_private_bfd_data'
 ....................................
 
 *Synopsis*
      bfd_boolean bfd_copy_private_bfd_data (bfd *ibfd, bfd *obfd);
    *Description*
 Copy private BFD information from the BFD IBFD to the the BFD OBFD.
-Return `TRUE' on success, `FALSE' on error.  Possible error returns are:
+Return 'TRUE' on success, 'FALSE' on error.  Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OBFD.
-
      #define bfd_copy_private_bfd_data(ibfd, obfd) \
           BFD_SEND (obfd, _bfd_copy_private_bfd_data, \
                     (ibfd, obfd))
 
-2.3.1.13 `bfd_merge_private_bfd_data'
+2.3.1.13 'bfd_merge_private_bfd_data'
 .....................................
 
 *Synopsis*
      bfd_boolean bfd_merge_private_bfd_data (bfd *ibfd, bfd *obfd);
    *Description*
 Merge private BFD information from the BFD IBFD to the the output file
-BFD OBFD when linking.  Return `TRUE' on success, `FALSE' on error.
+BFD OBFD when linking.  Return 'TRUE' on success, 'FALSE' on error.
 Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OBFD.
-
      #define bfd_merge_private_bfd_data(ibfd, obfd) \
           BFD_SEND (obfd, _bfd_merge_private_bfd_data, \
                     (ibfd, obfd))
 
-2.3.1.14 `bfd_set_private_flags'
+2.3.1.14 'bfd_set_private_flags'
 ................................
 
 *Synopsis*
      bfd_boolean bfd_set_private_flags (bfd *abfd, flagword flags);
    *Description*
-Set private BFD flag information in the BFD ABFD.  Return `TRUE' on
-success, `FALSE' on error.  Possible error returns are:
+Set private BFD flag information in the BFD ABFD.  Return 'TRUE' on
+success, 'FALSE' on error.  Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OBFD.
-
      #define bfd_set_private_flags(abfd, flags) \
           BFD_SEND (abfd, _bfd_set_private_flags, (abfd, flags))
 
-2.3.1.15 `Other functions'
+2.3.1.15 'Other functions'
 ..........................
 
 *Description*
@@ -1092,18 +1074,18 @@ The following functions exist but have not yet been documented.
        (bfd *, struct bfd_link_info *, struct bfd_link_order *, bfd_byte *,
         bfd_boolean, asymbol **);
 
-2.3.1.16 `bfd_alt_mach_code'
+2.3.1.16 'bfd_alt_mach_code'
 ............................
 
 *Synopsis*
      bfd_boolean bfd_alt_mach_code (bfd *abfd, int alternative);
    *Description*
-When more than one machine code number is available for the same
-machine type, this function can be used to switch between the preferred
-one (alternative == 0) and any others.  Currently, only ELF supports
-this feature, with up to two alternate machine codes.
+When more than one machine code number is available for the same machine
+type, this function can be used to switch between the preferred one
+(alternative == 0) and any others.  Currently, only ELF supports this
+feature, with up to two alternate machine codes.
 
-2.3.1.17 `bfd_emul_get_maxpagesize'
+2.3.1.17 'bfd_emul_get_maxpagesize'
 ...................................
 
 *Synopsis*
@@ -1114,16 +1096,16 @@ Returns the maximum page size, in bytes, as determined by emulation.
    *Returns*
 Returns the maximum page size in bytes for ELF, 0 otherwise.
 
-2.3.1.18 `bfd_emul_set_maxpagesize'
+2.3.1.18 'bfd_emul_set_maxpagesize'
 ...................................
 
 *Synopsis*
      void bfd_emul_set_maxpagesize (const char *, bfd_vma);
    *Description*
-For ELF, set the maximum page size for the emulation.  It is a no-op
-for other formats.
+For ELF, set the maximum page size for the emulation.  It is a no-op for
+other formats.
 
-2.3.1.19 `bfd_emul_get_commonpagesize'
+2.3.1.19 'bfd_emul_get_commonpagesize'
 ......................................
 
 *Synopsis*
@@ -1134,7 +1116,7 @@ Returns the common page size, in bytes, as determined by emulation.
    *Returns*
 Returns the common page size in bytes for ELF, 0 otherwise.
 
-2.3.1.20 `bfd_emul_set_commonpagesize'
+2.3.1.20 'bfd_emul_set_commonpagesize'
 ......................................
 
 *Synopsis*
@@ -1143,7 +1125,7 @@ Returns the common page size in bytes for ELF, 0 otherwise.
 For ELF, set the common page size for the emulation.  It is a no-op for
 other formats.
 
-2.3.1.21 `bfd_demangle'
+2.3.1.21 'bfd_demangle'
 .......................
 
 *Synopsis*
@@ -1154,22 +1136,13 @@ such chars that would otherwise confuse the demangler.  If passed a g++
 v3 ABI mangled name, returns a buffer allocated with malloc holding the
 demangled name.  Returns NULL otherwise and on memory alloc failure.
 
-2.3.1.22 `bfd_group_signature'
-..............................
-
-*Synopsis*
-     asymbol *bfd_group_signature (asection *group, asymbol **isympp);
-   *Description*
-Return a pointer to the symbol used as a signature for GROUP.
-
-2.3.1.23 `struct bfd_iovec'
+2.3.1.22 'struct bfd_iovec'
 ...........................
 
 *Description*
-The `struct bfd_iovec' contains the internal file I/O class.  Each
-`BFD' has an instance of this class and all file I/O is routed through
-it (it is assumed that the instance implements all methods listed
-below).
+The 'struct bfd_iovec' contains the internal file I/O class.  Each 'BFD'
+has an instance of this class and all file I/O is routed through it (it
+is assumed that the instance implements all methods listed below).
      struct bfd_iovec
      {
        /* To avoid problems with macros, a "b" rather than "f"
@@ -1177,15 +1150,15 @@ below).
        /* Attempt to read/write NBYTES on ABFD's IOSTREAM storing/fetching
           bytes starting at PTR.  Return the number of bytes actually
           transfered (a read past end-of-file returns less than NBYTES),
-          or -1 (setting `bfd_error') if an error occurs.  */
+          or -1 (setting bfd_error) if an error occurs.  */
        file_ptr (*bread) (struct bfd *abfd, void *ptr, file_ptr nbytes);
        file_ptr (*bwrite) (struct bfd *abfd, const void *ptr,
                            file_ptr nbytes);
-       /* Return the current IOSTREAM file offset, or -1 (setting `bfd_error'
+       /* Return the current IOSTREAM file offset, or -1 (setting bfd_error
           if an error occurs.  */
        file_ptr (*btell) (struct bfd *abfd);
        /* For the following, on successful completion a value of 0 is returned.
-          Otherwise, a value of -1 is returned (and  `bfd_error' is set).  */
+          Otherwise, a value of -1 is returned (and  bfd_error is set).  */
        int (*bseek) (struct bfd *abfd, file_ptr offset, int whence);
        int (*bclose) (struct bfd *abfd);
        int (*bflush) (struct bfd *abfd);
@@ -1202,16 +1175,16 @@ below).
      };
      extern const struct bfd_iovec _bfd_memory_iovec;
 
-2.3.1.24 `bfd_get_mtime'
+2.3.1.23 'bfd_get_mtime'
 ........................
 
 *Synopsis*
      long bfd_get_mtime (bfd *abfd);
    *Description*
-Return the file modification time (as read from the file system, or
-from the archive header for archive members).
+Return the file modification time (as read from the file system, or from
+the archive header for archive members).
 
-2.3.1.25 `bfd_get_size'
+2.3.1.24 'bfd_get_size'
 .......................
 
 *Synopsis*
@@ -1220,27 +1193,26 @@ from the archive header for archive members).
 Return the file size (as read from file system) for the file associated
 with BFD ABFD.
 
-   The initial motivation for, and use of, this routine is not so we
-can get the exact size of the object the BFD applies to, since that
-might not be generally possible (archive members for example).  It
-would be ideal if someone could eventually modify it so that such
-results were guaranteed.
-
-   Instead, we want to ask questions like "is this NNN byte sized
-object I'm about to try read from file offset YYY reasonable?"  As as
-example of where we might do this, some object formats use string
-tables for which the first `sizeof (long)' bytes of the table contain
-the size of the table itself, including the size bytes.  If an
-application tries to read what it thinks is one of these string tables,
-without some way to validate the size, and for some reason the size is
-wrong (byte swapping error, wrong location for the string table, etc.),
-the only clue is likely to be a read error when it tries to read the
-table, or a "virtual memory exhausted" error when it tries to allocate
-15 bazillon bytes of space for the 15 bazillon byte table it is about
-to read.  This function at least allows us to answer the question, "is
-the size reasonable?".
-
-2.3.1.26 `bfd_mmap'
+   The initial motivation for, and use of, this routine is not so we can
+get the exact size of the object the BFD applies to, since that might
+not be generally possible (archive members for example).  It would be
+ideal if someone could eventually modify it so that such results were
+guaranteed.
+
+   Instead, we want to ask questions like "is this NNN byte sized object
+I'm about to try read from file offset YYY reasonable?"  As as example
+of where we might do this, some object formats use string tables for
+which the first 'sizeof (long)' bytes of the table contain the size of
+the table itself, including the size bytes.  If an application tries to
+read what it thinks is one of these string tables, without some way to
+validate the size, and for some reason the size is wrong (byte swapping
+error, wrong location for the string table, etc.), the only clue is
+likely to be a read error when it tries to read the table, or a "virtual
+memory exhausted" error when it tries to allocate 15 bazillon bytes of
+space for the 15 bazillon byte table it is about to read.  This function
+at least allows us to answer the question, "is the size reasonable?".
+
+2.3.1.25 'bfd_mmap'
 ...................
 
 *Synopsis*
@@ -1249,8 +1221,8 @@ the size reasonable?".
          void **map_addr, bfd_size_type *map_len);
    *Description*
 Return mmap()ed region of the file, if possible and implemented.  LEN
-and OFFSET do not need to be page aligned.  The page aligned address
-and length are written to MAP_ADDR and MAP_LEN.
+and OFFSET do not need to be page aligned.  The page aligned address and
+length are written to MAP_ADDR and MAP_LEN.
 
 
 File: bfd.info,  Node: Memory Usage,  Next: Initialization,  Prev: Miscellaneous,  Up: BFD front end
@@ -1258,21 +1230,21 @@ File: bfd.info,  Node: Memory Usage,  Next: Initialization,  Prev: Miscellaneous
 2.4 Memory Usage
 ================
 
-BFD keeps all of its internal structures in obstacks. There is one
-obstack per open BFD file, into which the current state is stored. When
+BFD keeps all of its internal structures in obstacks.  There is one
+obstack per open BFD file, into which the current state is stored.  When
 a BFD is closed, the obstack is deleted, and so everything which has
 been allocated by BFD for the closing file is thrown away.
 
    BFD does not free anything created by an application, but pointers
-into `bfd' structures become invalid on a `bfd_close'; for example,
-after a `bfd_close' the vector passed to `bfd_canonicalize_symtab' is
+into 'bfd' structures become invalid on a 'bfd_close'; for example,
+after a 'bfd_close' the vector passed to 'bfd_canonicalize_symtab' is
 still around, since it has been allocated by the application, but the
 data that it pointed to are lost.
 
    The general rule is to not close a BFD until all operations dependent
 upon data from the BFD have been completed, or all the data from within
-the file has been copied. To help with the management of memory, there
-is a function (`bfd_alloc_size') which returns the number of bytes in
+the file has been copied.  To help with the management of memory, there
+is a function ('bfd_alloc_size') which returns the number of bytes in
 obstacks associated with the supplied BFD. This could be used to select
 the greediest open BFD, close it to reclaim the memory, perform some
 operation and reopen the BFD again, to get a fresh copy of the data
@@ -1289,7 +1261,7 @@ File: bfd.info,  Node: Initialization,  Next: Sections,  Prev: Memory Usage,  Up
 
 These are the functions that handle initializing a BFD.
 
-2.5.1.1 `bfd_init'
+2.5.1.1 'bfd_init'
 ..................
 
 *Synopsis*
@@ -1309,7 +1281,7 @@ abstraction.  A single BFD may have any number of sections.  It keeps
 hold of them by pointing to the first; each one points to the next in
 the list.
 
-   Sections are supported in BFD in `section.c'.
+   Sections are supported in BFD in 'section.c'.
 
 * Menu:
 
@@ -1324,31 +1296,30 @@ File: bfd.info,  Node: Section Input,  Next: Section Output,  Prev: Sections,  U
 2.6.1 Section input
 -------------------
 
-When a BFD is opened for reading, the section structures are created
-and attached to the BFD.
+When a BFD is opened for reading, the section structures are created and
+attached to the BFD.
 
    Each section has a name which describes the section in the outside
-world--for example, `a.out' would contain at least three sections,
-called `.text', `.data' and `.bss'.
+world--for example, 'a.out' would contain at least three sections,
+called '.text', '.data' and '.bss'.
 
    Names need not be unique; for example a COFF file may have several
-sections named `.data'.
+sections named '.data'.
 
    Sometimes a BFD will contain more than the "natural" number of
-sections. A back end may attach other sections containing constructor
-data, or an application may add a section (using `bfd_make_section') to
+sections.  A back end may attach other sections containing constructor
+data, or an application may add a section (using 'bfd_make_section') to
 the sections attached to an already open BFD. For example, the linker
-creates an extra section `COMMON' for each input file's BFD to hold
+creates an extra section 'COMMON' for each input file's BFD to hold
 information about common storage.
 
    The raw data is not necessarily read in when the section descriptor
-is created. Some targets may leave the data in place until a
-`bfd_get_section_contents' call is made. Other back ends may read in
-all the data at once.  For example, an S-record file has to be read
-once to determine the size of the data. An IEEE-695 file doesn't
-contain raw data in sections, but data and relocation expressions
-intermixed, so the data area has to be parsed to get out the data and
-relocations.
+is created.  Some targets may leave the data in place until a
+'bfd_get_section_contents' call is made.  Other back ends may read in
+all the data at once.  For example, an S-record file has to be read once
+to determine the size of the data.  An IEEE-695 file doesn't contain raw
+data in sections, but data and relocation expressions intermixed, so the
+data area has to be parsed to get out the data and relocations.
 
 
 File: bfd.info,  Node: Section Output,  Next: typedef asection,  Prev: Section Input,  Up: Sections
@@ -1356,20 +1327,20 @@ File: bfd.info,  Node: Section Output,  Next: typedef asection,  Prev: Section I
 2.6.2 Section output
 --------------------
 
-To write a new object style BFD, the various sections to be written
-have to be created. They are attached to the BFD in the same way as
-input sections; data is written to the sections using
-`bfd_set_section_contents'.
+To write a new object style BFD, the various sections to be written have
+to be created.  They are attached to the BFD in the same way as input
+sections; data is written to the sections using
+'bfd_set_section_contents'.
 
    Any program that creates or combines sections (e.g., the assembler
-and linker) must use the `asection' fields `output_section' and
-`output_offset' to indicate the file sections to which each section
-must be written.  (If the section is being created from scratch,
-`output_section' should probably point to the section itself and
-`output_offset' should probably be zero.)
+and linker) must use the 'asection' fields 'output_section' and
+'output_offset' to indicate the file sections to which each section must
+be written.  (If the section is being created from scratch,
+'output_section' should probably point to the section itself and
+'output_offset' should probably be zero.)
 
    The data to be written comes from input sections attached (via
-`output_section' pointers) to the output sections.  The output section
+'output_section' pointers) to the output sections.  The output section
 structure can be considered a filter for the input section: the output
 section determines the vma of the output data and the name, but the
 input section determines the offset into the output section of the data
@@ -1377,7 +1348,7 @@ to be written.
 
    E.g., to create a section "O", starting at 0x100, 0x123 long,
 containing two subsections, "A" at offset 0x0 (i.e., at vma 0x100) and
-"B" at offset 0x20 (i.e., at vma 0x120) the `asection' structures would
+"B" at offset 0x20 (i.e., at vma 0x120) the 'asection' structures would
 look like:
 
         section name          "A"
@@ -1394,7 +1365,7 @@ look like:
 -----------------
 
 The data within a section is stored in a "link_order".  These are much
-like the fixups in `gas'.  The link_order abstraction allows a section
+like the fixups in 'gas'.  The link_order abstraction allows a section
 to grow and shrink within itself.
 
    A link_order knows how big it is, and which is the next link_order
@@ -1402,8 +1373,8 @@ and where the raw data for it is; it also points to a list of
 relocations which apply to it.
 
    The link_order is used by the linker to perform relaxing on final
-code.  The compiler creates code which is as big as necessary to make
-it work without relaxing, and the user can select whether to relax.
+code.  The compiler creates code which is as big as necessary to make it
+work without relaxing, and the user can select whether to relax.
 Sometimes relaxing takes a lot of time.  The linker runs around the
 relocations to see if any are attached to data which can be shrunk, if
 so it does it on a link_order by link_order basis.
@@ -1468,19 +1439,19 @@ Here is the section structure:
 
        /* The section contains constructor information. This section
           type is used by the linker to create lists of constructors and
-          destructors used by `g++'. When a back end sees a symbol
+          destructors used by g++. When a back end sees a symbol
           which should be used in a constructor list, it creates a new
-          section for the type of name (e.g., `__CTOR_LIST__'), attaches
+          section for the type of name (e.g., __CTOR_LIST__), attaches
           the symbol to it, and builds a relocation. To build the lists
           of constructors, all the linker has to do is catenate all the
-          sections called `__CTOR_LIST__' and relocate the data
+          sections called __CTOR_LIST__ and relocate the data
           contained within - exactly the operations it would peform on
           standard data.  */
      #define SEC_CONSTRUCTOR 0x080
 
        /* The section has contents - a data section could be
-          `SEC_ALLOC' | `SEC_HAS_CONTENTS'; a debug section could be
-          `SEC_HAS_CONTENTS'  */
+          SEC_ALLOC | SEC_HAS_CONTENTS; a debug section could be
+          SEC_HAS_CONTENTS  */
      #define SEC_HAS_CONTENTS 0x100
 
        /* An instruction to the linker to not output the section
@@ -1654,6 +1625,7 @@ Here is the section structure:
      #define SEC_INFO_TYPE_MERGE     2
      #define SEC_INFO_TYPE_EH_FRAME  3
      #define SEC_INFO_TYPE_JUST_SYMS 4
+     #define SEC_INFO_TYPE_TARGET    5
 
        /* Nonzero if this section uses RELA relocations, rather than REL.  */
        unsigned int use_rela_p:1;
@@ -1673,8 +1645,8 @@ Here is the section structure:
        /*  The virtual memory address of the section - where it will be
            at run time.  The symbols are relocated against this.  The
            user_set_vma flag is maintained by bfd; if it's not set, the
-           backend can assign addresses (for example, in `a.out', where
-           the default address for `.data' is dependent on the specific
+           backend can assign addresses (for example, in a.out, where
+           the default address for .data is dependent on the specific
            target and various flags).  */
        bfd_vma vma;
 
@@ -1685,7 +1657,7 @@ Here is the section structure:
 
        /* The size of the section in octets, as it will be output.
           Contains a value even if the section has no contents (e.g., the
-          size of `.bss').  */
+          size of .bss).  */
        bfd_size_type size;
 
        /* For input sections, the original size on disk of the section, in
@@ -1808,6 +1780,32 @@ Here is the section structure:
        int size;
      };
 
+     /* Note: the following are provided as inline functions rather than macros
+        because not all callers use the return value.  A macro implementation
+        would use a comma expression, eg: "((ptr)->foo = val, TRUE)" and some
+        compilers will complain about comma expressions that have no effect.  */
+     static inline bfd_boolean
+     bfd_set_section_userdata (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, void * val)
+     {
+       ptr->userdata = val;
+       return TRUE;
+     }
+
+     static inline bfd_boolean
+     bfd_set_section_vma (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, bfd_vma val)
+     {
+       ptr->vma = ptr->lma = val;
+       ptr->user_set_vma = TRUE;
+       return TRUE;
+     }
+
+     static inline bfd_boolean
+     bfd_set_section_alignment (bfd * abfd ATTRIBUTE_UNUSED, asection * ptr, unsigned int val)
+     {
+       ptr->alignment_power = val;
+       return TRUE;
+     }
+
      /* These sections are global, and are managed by BFD.  The application
         and target back end are not permitted to change the values in
         these sections.  */
@@ -1818,9 +1816,6 @@ Here is the section structure:
      #define BFD_COM_SECTION_NAME "*COM*"
      #define BFD_IND_SECTION_NAME "*IND*"
 
-     /* GNU object-only section name.  */
-     #define GNU_OBJECT_ONLY_SECTION_NAME ".gnu_object_only"
-
      /* Pointer to the common section.  */
      #define bfd_com_section_ptr (&_bfd_std_section[0])
      /* Pointer to the undefined section.  */
@@ -1976,7 +1971,7 @@ File: bfd.info,  Node: section prototypes,  Prev: typedef asection,  Up: Section
 
 These are the functions exported by the section handling part of BFD.
 
-2.6.5.1 `bfd_section_list_clear'
+2.6.5.1 'bfd_section_list_clear'
 ................................
 
 *Synopsis*
@@ -1985,7 +1980,7 @@ These are the functions exported by the section handling part of BFD.
 Clears the section list, and also resets the section count and hash
 table entries.
 
-2.6.5.2 `bfd_get_section_by_name'
+2.6.5.2 'bfd_get_section_by_name'
 .................................
 
 *Synopsis*
@@ -1994,17 +1989,17 @@ table entries.
 Return the most recently created section attached to ABFD named NAME.
 Return NULL if no such section exists.
 
-2.6.5.3 `bfd_get_next_section_by_name'
+2.6.5.3 'bfd_get_next_section_by_name'
 ......................................
 
 *Synopsis*
      asection *bfd_get_next_section_by_name (asection *sec);
    *Description*
-Given SEC is a section returned by `bfd_get_section_by_name', return
-the next most recently created section attached to the same BFD with
-the same name.  Return NULL if no such section exists.
+Given SEC is a section returned by 'bfd_get_section_by_name', return the
+next most recently created section attached to the same BFD with the
+same name.  Return NULL if no such section exists.
 
-2.6.5.4 `bfd_get_linker_section'
+2.6.5.4 'bfd_get_linker_section'
 ................................
 
 *Synopsis*
@@ -2013,7 +2008,7 @@ the same name.  Return NULL if no such section exists.
 Return the linker created section attached to ABFD named NAME.  Return
 NULL if no such section exists.
 
-2.6.5.5 `bfd_get_section_by_name_if'
+2.6.5.5 'bfd_get_section_by_name_if'
 ....................................
 
 *Synopsis*
@@ -2024,15 +2019,15 @@ NULL if no such section exists.
          void *obj);
    *Description*
 Call the provided function FUNC for each section attached to the BFD
-ABFD whose name matches NAME, passing OBJ as an argument. The function
+ABFD whose name matches NAME, passing OBJ as an argument.  The function
 will be called as if by
 
             func (abfd, the_section, obj);
 
    It returns the first section for which FUNC returns true, otherwise
-`NULL'.
+'NULL'.
 
-2.6.5.6 `bfd_get_unique_section_name'
+2.6.5.6 'bfd_get_unique_section_name'
 .....................................
 
 *Synopsis*
@@ -2044,14 +2039,14 @@ digit suffix onto the original TEMPLAT.  If COUNT is non-NULL, then it
 specifies the first number tried as a suffix to generate a unique name.
 The value pointed to by COUNT will be incremented in this case.
 
-2.6.5.7 `bfd_make_section_old_way'
+2.6.5.7 'bfd_make_section_old_way'
 ..................................
 
 *Synopsis*
      asection *bfd_make_section_old_way (bfd *abfd, const char *name);
    *Description*
 Create a new empty section called NAME and attach it to the end of the
-chain of sections for the BFD ABFD. An attempt to create a section with
+chain of sections for the BFD ABFD.  An attempt to create a section with
 a name which is already in use returns its pointer without changing the
 section chain.
 
@@ -2059,12 +2054,12 @@ section chain.
 was rewritten....
 
    Possible errors are:
-   * `bfd_error_invalid_operation' - If output has already started for
-     this BFD.
 
-   * `bfd_error_no_memory' - If memory allocation fails.
+   * 'bfd_error_invalid_operation' - If output has already started for
+     this BFD.
+   * 'bfd_error_no_memory' - If memory allocation fails.
 
-2.6.5.8 `bfd_make_section_anyway_with_flags'
+2.6.5.8 'bfd_make_section_anyway_with_flags'
 ............................................
 
 *Synopsis*
@@ -2076,13 +2071,13 @@ chain of sections for ABFD.  Create a new section even if there is
 already a section with that name.  Also set the attributes of the new
 section to the value FLAGS.
 
-   Return `NULL' and set `bfd_error' on error; possible errors are:
-   * `bfd_error_invalid_operation' - If output has already started for
-     ABFD.
+   Return 'NULL' and set 'bfd_error' on error; possible errors are:
 
-   * `bfd_error_no_memory' - If memory allocation fails.
+   * 'bfd_error_invalid_operation' - If output has already started for
+     ABFD.
+   * 'bfd_error_no_memory' - If memory allocation fails.
 
-2.6.5.9 `bfd_make_section_anyway'
+2.6.5.9 'bfd_make_section_anyway'
 .................................
 
 *Synopsis*
@@ -2092,37 +2087,36 @@ Create a new empty section called NAME and attach it to the end of the
 chain of sections for ABFD.  Create a new section even if there is
 already a section with that name.
 
-   Return `NULL' and set `bfd_error' on error; possible errors are:
-   * `bfd_error_invalid_operation' - If output has already started for
-     ABFD.
+   Return 'NULL' and set 'bfd_error' on error; possible errors are:
 
-   * `bfd_error_no_memory' - If memory allocation fails.
+   * 'bfd_error_invalid_operation' - If output has already started for
+     ABFD.
+   * 'bfd_error_no_memory' - If memory allocation fails.
 
-2.6.5.10 `bfd_make_section_with_flags'
+2.6.5.10 'bfd_make_section_with_flags'
 ......................................
 
 *Synopsis*
      asection *bfd_make_section_with_flags
         (bfd *, const char *name, flagword flags);
    *Description*
-Like `bfd_make_section_anyway', but return `NULL' (without calling
-bfd_set_error ()) without changing the section chain if there is
-already a section named NAME.  Also set the attributes of the new
-section to the value FLAGS.  If there is an error, return `NULL' and set
-`bfd_error'.
+Like 'bfd_make_section_anyway', but return 'NULL' (without calling
+bfd_set_error ()) without changing the section chain if there is already
+a section named NAME.  Also set the attributes of the new section to the
+value FLAGS.  If there is an error, return 'NULL' and set 'bfd_error'.
 
-2.6.5.11 `bfd_make_section'
+2.6.5.11 'bfd_make_section'
 ...........................
 
 *Synopsis*
      asection *bfd_make_section (bfd *, const char *name);
    *Description*
-Like `bfd_make_section_anyway', but return `NULL' (without calling
-bfd_set_error ()) without changing the section chain if there is
-already a section named NAME.  If there is an error, return `NULL' and
-set `bfd_error'.
+Like 'bfd_make_section_anyway', but return 'NULL' (without calling
+bfd_set_error ()) without changing the section chain if there is already
+a section named NAME.  If there is an error, return 'NULL' and set
+'bfd_error'.
 
-2.6.5.12 `bfd_set_section_flags'
+2.6.5.12 'bfd_set_section_flags'
 ................................
 
 *Synopsis*
@@ -2130,14 +2124,14 @@ set `bfd_error'.
         (bfd *abfd, asection *sec, flagword flags);
    *Description*
 Set the attributes of the section SEC in the BFD ABFD to the value
-FLAGS. Return `TRUE' on success, `FALSE' on error. Possible error
+FLAGS.  Return 'TRUE' on success, 'FALSE' on error.  Possible error
 returns are:
 
-   * `bfd_error_invalid_operation' - The section cannot have one or
-     more of the attributes requested. For example, a .bss section in
-     `a.out' may not have the `SEC_HAS_CONTENTS' field set.
+   * 'bfd_error_invalid_operation' - The section cannot have one or more
+     of the attributes requested.  For example, a .bss section in
+     'a.out' may not have the 'SEC_HAS_CONTENTS' field set.
 
-2.6.5.13 `bfd_rename_section'
+2.6.5.13 'bfd_rename_section'
 .............................
 
 *Synopsis*
@@ -2146,7 +2140,7 @@ returns are:
    *Description*
 Rename section SEC in ABFD to NEWNAME.
 
-2.6.5.14 `bfd_map_over_sections'
+2.6.5.14 'bfd_map_over_sections'
 ................................
 
 *Synopsis*
@@ -2156,7 +2150,7 @@ Rename section SEC in ABFD to NEWNAME.
          void *obj);
    *Description*
 Call the provided function FUNC for each section attached to the BFD
-ABFD, passing OBJ as an argument. The function will be called as if by
+ABFD, passing OBJ as an argument.  The function will be called as if by
 
             func (abfd, the_section, obj);
 
@@ -2167,7 +2161,7 @@ alternative would be to use a loop:
                for (p = abfd->sections; p != NULL; p = p->next)
                   func (abfd, p, ...)
 
-2.6.5.15 `bfd_sections_find_if'
+2.6.5.15 'bfd_sections_find_if'
 ...............................
 
 *Synopsis*
@@ -2177,28 +2171,29 @@ alternative would be to use a loop:
          void *obj);
    *Description*
 Call the provided function OPERATION for each section attached to the
-BFD ABFD, passing OBJ as an argument. The function will be called as if
+BFD ABFD, passing OBJ as an argument.  The function will be called as if
 by
 
             operation (abfd, the_section, obj);
 
    It returns the first section for which OPERATION returns true.
 
-2.6.5.16 `bfd_set_section_size'
+2.6.5.16 'bfd_set_section_size'
 ...............................
 
 *Synopsis*
      bfd_boolean bfd_set_section_size
         (bfd *abfd, asection *sec, bfd_size_type val);
    *Description*
-Set SEC to the size VAL. If the operation is ok, then `TRUE' is
-returned, else `FALSE'.
+Set SEC to the size VAL.  If the operation is ok, then 'TRUE' is
+returned, else 'FALSE'.
 
    Possible error returns:
-   * `bfd_error_invalid_operation' - Writing has started to the BFD, so
+
+   * 'bfd_error_invalid_operation' - Writing has started to the BFD, so
      setting the size is invalid.
 
-2.6.5.17 `bfd_set_section_contents'
+2.6.5.17 'bfd_set_section_contents'
 ...................................
 
 *Synopsis*
@@ -2207,19 +2202,19 @@ returned, else `FALSE'.
          file_ptr offset, bfd_size_type count);
    *Description*
 Sets the contents of the section SECTION in BFD ABFD to the data
-starting in memory at DATA. The data is written to the output section
+starting in memory at DATA.  The data is written to the output section
 starting at offset OFFSET for COUNT octets.
 
-   Normally `TRUE' is returned, else `FALSE'. Possible error returns
+   Normally 'TRUE' is returned, else 'FALSE'.  Possible error returns
 are:
-   * `bfd_error_no_contents' - The output section does not have the
-     `SEC_HAS_CONTENTS' attribute, so nothing can be written to it.
 
+   * 'bfd_error_no_contents' - The output section does not have the
+     'SEC_HAS_CONTENTS' attribute, so nothing can be written to it.
    * and some more too
    This routine is front end to the back end function
-`_bfd_set_section_contents'.
+'_bfd_set_section_contents'.
 
-2.6.5.18 `bfd_get_section_contents'
+2.6.5.18 'bfd_get_section_contents'
 ...................................
 
 *Synopsis*
@@ -2231,12 +2226,12 @@ Read data from SECTION in BFD ABFD into memory starting at LOCATION.
 The data is read at an offset of OFFSET from the start of the input
 section, and is read for COUNT bytes.
 
-   If the contents of a constructor with the `SEC_CONSTRUCTOR' flag set
-are requested or if the section does not have the `SEC_HAS_CONTENTS'
-flag set, then the LOCATION is filled with zeroes. If no errors occur,
-`TRUE' is returned, else `FALSE'.
+   If the contents of a constructor with the 'SEC_CONSTRUCTOR' flag set
+are requested or if the section does not have the 'SEC_HAS_CONTENTS'
+flag set, then the LOCATION is filled with zeroes.  If no errors occur,
+'TRUE' is returned, else 'FALSE'.
 
-2.6.5.19 `bfd_malloc_and_get_section'
+2.6.5.19 'bfd_malloc_and_get_section'
 .....................................
 
 *Synopsis*
@@ -2246,7 +2241,7 @@ flag set, then the LOCATION is filled with zeroes. If no errors occur,
 Read all data from SECTION in BFD ABFD into a buffer, *BUF, malloc'd by
 this function.
 
-2.6.5.20 `bfd_copy_private_section_data'
+2.6.5.20 'bfd_copy_private_section_data'
 ........................................
 
 *Synopsis*
@@ -2254,17 +2249,16 @@ this function.
         (bfd *ibfd, asection *isec, bfd *obfd, asection *osec);
    *Description*
 Copy private section information from ISEC in the BFD IBFD to the
-section OSEC in the BFD OBFD.  Return `TRUE' on success, `FALSE' on
+section OSEC in the BFD OBFD.  Return 'TRUE' on success, 'FALSE' on
 error.  Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OSEC.
-
      #define bfd_copy_private_section_data(ibfd, isection, obfd, osection) \
           BFD_SEND (obfd, _bfd_copy_private_section_data, \
                     (ibfd, isection, obfd, osection))
 
-2.6.5.21 `bfd_generic_is_group_section'
+2.6.5.21 'bfd_generic_is_group_section'
 .......................................
 
 *Synopsis*
@@ -2272,7 +2266,7 @@ error.  Possible error returns are:
    *Description*
 Returns TRUE if SEC is a member of a group.
 
-2.6.5.22 `bfd_generic_discard_group'
+2.6.5.22 'bfd_generic_discard_group'
 ....................................
 
 *Synopsis*
@@ -2286,27 +2280,26 @@ File: bfd.info,  Node: Symbols,  Next: Archives,  Prev: Sections,  Up: BFD front
 2.7 Symbols
 ===========
 
-BFD tries to maintain as much symbol information as it can when it
-moves information from file to file. BFD passes information to
-applications though the `asymbol' structure. When the application
-requests the symbol table, BFD reads the table in the native form and
-translates parts of it into the internal format. To maintain more than
-the information passed to applications, some targets keep some
-information "behind the scenes" in a structure only the particular back
-end knows about. For example, the coff back end keeps the original
-symbol table structure as well as the canonical structure when a BFD is
-read in. On output, the coff back end can reconstruct the output symbol
-table so that no information is lost, even information unique to coff
-which BFD doesn't know or understand. If a coff symbol table were read,
-but were written through an a.out back end, all the coff specific
-information would be lost. The symbol table of a BFD is not necessarily
-read in until a canonicalize request is made. Then the BFD back end
-fills in a table provided by the application with pointers to the
-canonical information.  To output symbols, the application provides BFD
-with a table of pointers to pointers to `asymbol's. This allows
-applications like the linker to output a symbol as it was read, since
-the "behind the scenes" information will be still available.
-
+BFD tries to maintain as much symbol information as it can when it moves
+information from file to file.  BFD passes information to applications
+though the 'asymbol' structure.  When the application requests the
+symbol table, BFD reads the table in the native form and translates
+parts of it into the internal format.  To maintain more than the
+information passed to applications, some targets keep some information
+"behind the scenes" in a structure only the particular back end knows
+about.  For example, the coff back end keeps the original symbol table
+structure as well as the canonical structure when a BFD is read in.  On
+output, the coff back end can reconstruct the output symbol table so
+that no information is lost, even information unique to coff which BFD
+doesn't know or understand.  If a coff symbol table were read, but were
+written through an a.out back end, all the coff specific information
+would be lost.  The symbol table of a BFD is not necessarily read in
+until a canonicalize request is made.  Then the BFD back end fills in a
+table provided by the application with pointers to the canonical
+information.  To output symbols, the application provides BFD with a
+table of pointers to pointers to 'asymbol's.  This allows applications
+like the linker to output a symbol as it was read, since the "behind the
+scenes" information will be still available.
 * Menu:
 
 * Reading Symbols::
@@ -2322,7 +2315,7 @@ File: bfd.info,  Node: Reading Symbols,  Next: Writing Symbols,  Prev: Symbols,
 ---------------------
 
 There are two stages to reading a symbol table from a BFD: allocating
-storage, and the actual reading process. This is an excerpt from an
+storage, and the actual reading process.  This is an excerpt from an
 application which reads the symbol table:
 
               long storage_needed;
@@ -2349,8 +2342,8 @@ application which reads the symbol table:
               for (i = 0; i < number_of_symbols; i++)
                 process_symbol (symbol_table[i]);
 
-   All storage for the symbols themselves is in an objalloc connected
-to the BFD; it is freed when the BFD is closed.
+   All storage for the symbols themselves is in an objalloc connected to
+the BFD; it is freed when the BFD is closed.
 
 
 File: bfd.info,  Node: Writing Symbols,  Next: Mini Symbols,  Prev: Reading Symbols,  Up: Symbols
@@ -2359,12 +2352,12 @@ File: bfd.info,  Node: Writing Symbols,  Next: Mini Symbols,  Prev: Reading Symb
 ---------------------
 
 Writing of a symbol table is automatic when a BFD open for writing is
-closed. The application attaches a vector of pointers to pointers to
-symbols to the BFD being written, and fills in the symbol count. The
-close and cleanup code reads through the table provided and performs
-all the necessary operations. The BFD output code must always be
-provided with an "owned" symbol: one which has come from another BFD,
-or one which has been created using `bfd_make_empty_symbol'.  Here is an
+closed.  The application attaches a vector of pointers to pointers to
+symbols to the BFD being written, and fills in the symbol count.  The
+close and cleanup code reads through the table provided and performs all
+the necessary operations.  The BFD output code must always be provided
+with an "owned" symbol: one which has come from another BFD, or one
+which has been created using 'bfd_make_empty_symbol'.  Here is an
 example showing the creation of a symbol table with only one element:
 
             #include "sysdep.h"
@@ -2396,9 +2389,9 @@ example showing the creation of a symbol table with only one element:
             00012345 A dummy_symbol
 
    Many formats cannot represent arbitrary symbol information; for
-instance, the `a.out' object format does not allow an arbitrary number
-of sections. A symbol pointing to a section which is not one  of
-`.text', `.data' or `.bss' cannot be described.
+instance, the 'a.out' object format does not allow an arbitrary number
+of sections.  A symbol pointing to a section which is not one of
+'.text', '.data' or '.bss' cannot be described.
 
 
 File: bfd.info,  Node: Mini Symbols,  Next: typedef asymbol,  Prev: Writing Symbols,  Up: Symbols
@@ -2411,17 +2404,17 @@ less memory space, but require more time to access.  They can be useful
 for tools like nm or objdump, which may have to handle symbol tables of
 extremely large executables.
 
-   The `bfd_read_minisymbols' function will read the symbols into
-memory in an internal form.  It will return a `void *' pointer to a
-block of memory, a symbol count, and the size of each symbol.  The
-pointer is allocated using `malloc', and should be freed by the caller
-when it is no longer needed.
+   The 'bfd_read_minisymbols' function will read the symbols into memory
+in an internal form.  It will return a 'void *' pointer to a block of
+memory, a symbol count, and the size of each symbol.  The pointer is
+allocated using 'malloc', and should be freed by the caller when it is
+no longer needed.
 
-   The function `bfd_minisymbol_to_symbol' will take a pointer to a
+   The function 'bfd_minisymbol_to_symbol' will take a pointer to a
 minisymbol, and a pointer to a structure returned by
-`bfd_make_empty_symbol', and return a `asymbol' structure.  The return
+'bfd_make_empty_symbol', and return a 'asymbol' structure.  The return
 value may or may not be the same as the value from
-`bfd_make_empty_symbol' which was passed in.
+'bfd_make_empty_symbol' which was passed in.
 
 
 File: bfd.info,  Node: typedef asymbol,  Next: symbol handling functions,  Prev: Mini Symbols,  Up: Symbols
@@ -2429,7 +2422,7 @@ File: bfd.info,  Node: typedef asymbol,  Next: symbol handling functions,  Prev:
 2.7.4 typedef asymbol
 ---------------------
 
-An `asymbol' has the form:
+An 'asymbol' has the form:
 
 
      typedef struct bfd_symbol
@@ -2457,11 +2450,11 @@ An `asymbol' has the form:
        /* Attributes of a symbol.  */
      #define BSF_NO_FLAGS           0x00
 
-       /* The symbol has local scope; `static' in `C'. The value
+       /* The symbol has local scope; static in C. The value
           is the offset into the section of the data.  */
      #define BSF_LOCAL              (1 << 0)
 
-       /* The symbol has global scope; initialized data in `C'. The
+       /* The symbol has global scope; initialized data in C. The
           value is the offset into the section of the data.  */
      #define BSF_GLOBAL             (1 << 1)
 
@@ -2470,8 +2463,8 @@ An `asymbol' has the form:
      #define BSF_EXPORT     BSF_GLOBAL /* No real difference.  */
 
        /* A normal C symbol would be one of:
-          `BSF_LOCAL', `BSF_COMMON',  `BSF_UNDEFINED' or
-          `BSF_GLOBAL'.  */
+          BSF_LOCAL, BSF_COMMON,  BSF_UNDEFINED or
+          BSF_GLOBAL.  */
 
        /* The symbol is a debugging record. The value has an arbitrary
           meaning, unless BSF_DEBUGGING_RELOC is also set.  */
@@ -2498,8 +2491,8 @@ An `asymbol' has the form:
      #define BSF_OLD_COMMON         (1 << 9)
 
        /* In some files the type of a symbol sometimes alters its
-          location in an output file - ie in coff a `ISFCN' symbol
-          which is also `C_EXT' symbol appears where it was
+          location in an output file - ie in coff a ISFCN symbol
+          which is also C_EXT symbol appears where it was
           declared and not at the end of a section.  This bit is set
           by the target BFD part to convey this information.  */
      #define BSF_NOT_AT_END         (1 << 10)
@@ -2557,10 +2550,6 @@ An `asymbol' has the form:
           with this name and type in use.  BSF_OBJECT must also be set.  */
      #define BSF_GNU_UNIQUE         (1 << 23)
 
-       /* A secondary global symbol, overridable without warnings by
-          a regular or weak global symbol of the same name.  */
-     #define BSF_SECONDARY          (1 << 24)
-
        flagword flags;
 
        /* A pointer to the section to which this symbol is
@@ -2584,18 +2573,18 @@ File: bfd.info,  Node: symbol handling functions,  Prev: typedef asymbol,  Up: S
 2.7.5 Symbol handling functions
 -------------------------------
 
-2.7.5.1 `bfd_get_symtab_upper_bound'
+2.7.5.1 'bfd_get_symtab_upper_bound'
 ....................................
 
 *Description*
 Return the number of bytes required to store a vector of pointers to
-`asymbols' for all the symbols in the BFD ABFD, including a terminal
-NULL pointer. If there are no symbols in the BFD, then return 0.  If an
+'asymbols' for all the symbols in the BFD ABFD, including a terminal
+NULL pointer.  If there are no symbols in the BFD, then return 0.  If an
 error occurs, return -1.
      #define bfd_get_symtab_upper_bound(abfd) \
           BFD_SEND (abfd, _bfd_get_symtab_upper_bound, (abfd))
 
-2.7.5.2 `bfd_is_local_label'
+2.7.5.2 'bfd_is_local_label'
 ............................
 
 *Synopsis*
@@ -2604,41 +2593,41 @@ error occurs, return -1.
 Return TRUE if the given symbol SYM in the BFD ABFD is a compiler
 generated local label, else return FALSE.
 
-2.7.5.3 `bfd_is_local_label_name'
+2.7.5.3 'bfd_is_local_label_name'
 .................................
 
 *Synopsis*
      bfd_boolean bfd_is_local_label_name (bfd *abfd, const char *name);
    *Description*
-Return TRUE if a symbol with the name NAME in the BFD ABFD is a
-compiler generated local label, else return FALSE.  This just checks
-whether the name has the form of a local label.
+Return TRUE if a symbol with the name NAME in the BFD ABFD is a compiler
+generated local label, else return FALSE. This just checks whether the
+name has the form of a local label.
      #define bfd_is_local_label_name(abfd, name) \
        BFD_SEND (abfd, _bfd_is_local_label_name, (abfd, name))
 
-2.7.5.4 `bfd_is_target_special_symbol'
+2.7.5.4 'bfd_is_target_special_symbol'
 ......................................
 
 *Synopsis*
      bfd_boolean bfd_is_target_special_symbol (bfd *abfd, asymbol *sym);
    *Description*
-Return TRUE iff a symbol SYM in the BFD ABFD is something special to
-the particular target represented by the BFD.  Such symbols should
-normally not be mentioned to the user.
+Return TRUE iff a symbol SYM in the BFD ABFD is something special to the
+particular target represented by the BFD. Such symbols should normally
+not be mentioned to the user.
      #define bfd_is_target_special_symbol(abfd, sym) \
        BFD_SEND (abfd, _bfd_is_target_special_symbol, (abfd, sym))
 
-2.7.5.5 `bfd_canonicalize_symtab'
+2.7.5.5 'bfd_canonicalize_symtab'
 .................................
 
 *Description*
 Read the symbols from the BFD ABFD, and fills in the vector LOCATION
-with pointers to the symbols and a trailing NULL.  Return the actual
+with pointers to the symbols and a trailing NULL. Return the actual
 number of symbol pointers, not including the NULL.
      #define bfd_canonicalize_symtab(abfd, location) \
        BFD_SEND (abfd, _bfd_canonicalize_symtab, (abfd, location))
 
-2.7.5.6 `bfd_set_symtab'
+2.7.5.6 'bfd_set_symtab'
 ........................
 
 *Synopsis*
@@ -2648,7 +2637,7 @@ number of symbol pointers, not including the NULL.
 Arrange that when the output BFD ABFD is closed, the table LOCATION of
 COUNT pointers to symbols will be written.
 
-2.7.5.7 `bfd_print_symbol_vandf'
+2.7.5.7 'bfd_print_symbol_vandf'
 ................................
 
 *Synopsis*
@@ -2656,40 +2645,40 @@ COUNT pointers to symbols will be written.
    *Description*
 Print the value and flags of the SYMBOL supplied to the stream FILE.
 
-2.7.5.8 `bfd_make_empty_symbol'
+2.7.5.8 'bfd_make_empty_symbol'
 ...............................
 
 *Description*
-Create a new `asymbol' structure for the BFD ABFD and return a pointer
+Create a new 'asymbol' structure for the BFD ABFD and return a pointer
 to it.
 
    This routine is necessary because each back end has private
-information surrounding the `asymbol'. Building your own `asymbol' and
+information surrounding the 'asymbol'.  Building your own 'asymbol' and
 pointing to it will not create the private information, and will cause
 problems later on.
      #define bfd_make_empty_symbol(abfd) \
        BFD_SEND (abfd, _bfd_make_empty_symbol, (abfd))
 
-2.7.5.9 `_bfd_generic_make_empty_symbol'
+2.7.5.9 '_bfd_generic_make_empty_symbol'
 ........................................
 
 *Synopsis*
      asymbol *_bfd_generic_make_empty_symbol (bfd *);
    *Description*
-Create a new `asymbol' structure for the BFD ABFD and return a pointer
+Create a new 'asymbol' structure for the BFD ABFD and return a pointer
 to it.  Used by core file routines, binary back-end and anywhere else
 where no private info is needed.
 
-2.7.5.10 `bfd_make_debug_symbol'
+2.7.5.10 'bfd_make_debug_symbol'
 ................................
 
 *Description*
-Create a new `asymbol' structure for the BFD ABFD, to be used as a
+Create a new 'asymbol' structure for the BFD ABFD, to be used as a
 debugging symbol.  Further details of its use have yet to be worked out.
      #define bfd_make_debug_symbol(abfd,ptr,size) \
        BFD_SEND (abfd, _bfd_make_debug_symbol, (abfd, ptr, size))
 
-2.7.5.11 `bfd_decode_symclass'
+2.7.5.11 'bfd_decode_symclass'
 ..............................
 
 *Description*
@@ -2698,8 +2687,8 @@ for an unknown class.
 
    *Synopsis*
      int bfd_decode_symclass (asymbol *symbol);
-   
-2.7.5.12 `bfd_is_undefined_symclass'
+
+2.7.5.12 'bfd_is_undefined_symclass'
 ....................................
 
 *Description*
@@ -2708,8 +2697,8 @@ represents an undefined symbol.  Returns zero otherwise.
 
    *Synopsis*
      bfd_boolean bfd_is_undefined_symclass (int symclass);
-   
-2.7.5.13 `bfd_symbol_info'
+
+2.7.5.13 'bfd_symbol_info'
 ..........................
 
 *Description*
@@ -2718,8 +2707,8 @@ be added by the back-ends after calling this function.
 
    *Synopsis*
      void bfd_symbol_info (asymbol *symbol, symbol_info *ret);
-   
-2.7.5.14 `bfd_copy_private_symbol_data'
+
+2.7.5.14 'bfd_copy_private_symbol_data'
 .......................................
 
 *Synopsis*
@@ -2727,12 +2716,11 @@ be added by the back-ends after calling this function.
         (bfd *ibfd, asymbol *isym, bfd *obfd, asymbol *osym);
    *Description*
 Copy private symbol information from ISYM in the BFD IBFD to the symbol
-OSYM in the BFD OBFD.  Return `TRUE' on success, `FALSE' on error.
+OSYM in the BFD OBFD.  Return 'TRUE' on success, 'FALSE' on error.
 Possible error returns are:
 
-   * `bfd_error_no_memory' - Not enough memory exists to create private
+   * 'bfd_error_no_memory' - Not enough memory exists to create private
      data for OSEC.
-
      #define bfd_copy_private_symbol_data(ibfd, isymbol, obfd, osymbol) \
        BFD_SEND (obfd, _bfd_copy_private_symbol_data, \
                  (ibfd, isymbol, obfd, osymbol))
@@ -2744,30 +2732,30 @@ File: bfd.info,  Node: Archives,  Next: Formats,  Prev: Symbols,  Up: BFD front
 ============
 
 *Description*
-An archive (or library) is just another BFD.  It has a symbol table,
+An archive (or library) is just another BFD. It has a symbol table,
 although there's not much a user program will do with it.
 
-   The big difference between an archive BFD and an ordinary BFD is
-that the archive doesn't have sections.  Instead it has a chain of BFDs
-that are considered its contents.  These BFDs can be manipulated like
-any other.  The BFDs contained in an archive opened for reading will
-all be opened for reading.  You may put either input or output BFDs
-into an archive opened for output; they will be handled correctly when
-the archive is closed.
+   The big difference between an archive BFD and an ordinary BFD is that
+the archive doesn't have sections.  Instead it has a chain of BFDs that
+are considered its contents.  These BFDs can be manipulated like any
+other.  The BFDs contained in an archive opened for reading will all be
+opened for reading.  You may put either input or output BFDs into an
+archive opened for output; they will be handled correctly when the
+archive is closed.
 
-   Use `bfd_openr_next_archived_file' to step through the contents of
-an archive opened for input.  You don't have to read the entire archive
-if you don't want to!  Read it until you find what you want.
+   Use 'bfd_openr_next_archived_file' to step through the contents of an
+archive opened for input.  You don't have to read the entire archive if
+you don't want to!  Read it until you find what you want.
 
-   A BFD returned by `bfd_openr_next_archived_file' can be closed
-manually with `bfd_close'.  If you do not close it, then a second
-iteration through the members of an archive may return the same BFD.
-If you close the archive BFD, then all the member BFDs will
-automatically be closed as well.
+   A BFD returned by 'bfd_openr_next_archived_file' can be closed
+manually with 'bfd_close'.  If you do not close it, then a second
+iteration through the members of an archive may return the same BFD. If
+you close the archive BFD, then all the member BFDs will automatically
+be closed as well.
 
    Archive contents of output BFDs are chained through the
-`archive_next' pointer in a BFD.  The first one is findable through the
-`archive_head' slot of the archive.  Set it with `bfd_set_archive_head'
+'archive_next' pointer in a BFD. The first one is findable through the
+'archive_head' slot of the archive.  Set it with 'bfd_set_archive_head'
 (q.v.).  A given BFD may be in only one open output archive at a time.
 
    As expected, the BFD archive code is more general than the archive
@@ -2790,12 +2778,12 @@ this case due to restrictions in the format of archives.  Many Unix
 utilities are braindead in regards to spaces and such in filenames
 anyway, so this shouldn't be much of a restriction.
 
-   Archives are supported in BFD in `archive.c'.
+   Archives are supported in BFD in 'archive.c'.
 
 2.8.1 Archive functions
 -----------------------
 
-2.8.1.1 `bfd_get_next_mapent'
+2.8.1.1 'bfd_get_next_mapent'
 .............................
 
 *Synopsis*
@@ -2806,13 +2794,13 @@ Step through archive ABFD's symbol table (if it has one).  Successively
 update SYM with the next symbol's information, returning that symbol's
 (internal) index into the symbol table.
 
-   Supply `BFD_NO_MORE_SYMBOLS' as the PREVIOUS entry to get the first
-one; returns `BFD_NO_MORE_SYMBOLS' when you've already got the last one.
+   Supply 'BFD_NO_MORE_SYMBOLS' as the PREVIOUS entry to get the first
+one; returns 'BFD_NO_MORE_SYMBOLS' when you've already got the last one.
 
-   A `carsym' is a canonical archive symbol.  The only user-visible
+   A 'carsym' is a canonical archive symbol.  The only user-visible
 element is its name, a null-terminated string.
 
-2.8.1.2 `bfd_set_archive_head'
+2.8.1.2 'bfd_set_archive_head'
 ..............................
 
 *Synopsis*
@@ -2821,7 +2809,7 @@ element is its name, a null-terminated string.
 Set the head of the chain of BFDs contained in the archive OUTPUT to
 NEW_HEAD.
 
-2.8.1.3 `bfd_openr_next_archived_file'
+2.8.1.3 'bfd_openr_next_archived_file'
 ......................................
 
 *Synopsis*
@@ -2830,7 +2818,7 @@ NEW_HEAD.
 Provided a BFD, ARCHIVE, containing an archive and NULL, open an input
 BFD on the first contained element and returns that.  Subsequent calls
 should pass the archive and the previous return value to return a
-created BFD to the next contained element. NULL is returned when there
+created BFD to the next contained element.  NULL is returned when there
 are no more.
 
 
@@ -2839,87 +2827,87 @@ File: bfd.info,  Node: Formats,  Next: Relocations,  Prev: Archives,  Up: BFD fr
 2.9 File formats
 ================
 
-A format is a BFD concept of high level file contents type. The formats
+A format is a BFD concept of high level file contents type.  The formats
 supported by BFD are:
 
-   * `bfd_object'
+   * 'bfd_object'
    The BFD may contain data, symbols, relocations and debug info.
 
-   * `bfd_archive'
+   * 'bfd_archive'
    The BFD contains other BFDs and an optional index.
 
-   * `bfd_core'
+   * 'bfd_core'
    The BFD contains the result of an executable core dump.
 
 2.9.1 File format functions
 ---------------------------
 
-2.9.1.1 `bfd_check_format'
+2.9.1.1 'bfd_check_format'
 ..........................
 
 *Synopsis*
      bfd_boolean bfd_check_format (bfd *abfd, bfd_format format);
    *Description*
 Verify if the file attached to the BFD ABFD is compatible with the
-format FORMAT (i.e., one of `bfd_object', `bfd_archive' or `bfd_core').
+format FORMAT (i.e., one of 'bfd_object', 'bfd_archive' or 'bfd_core').
 
    If the BFD has been set to a specific target before the call, only
-the named target and format combination is checked. If the target has
-not been set, or has been set to `default', then all the known target
+the named target and format combination is checked.  If the target has
+not been set, or has been set to 'default', then all the known target
 backends is interrogated to determine a match.  If the default target
 matches, it is used.  If not, exactly one target must recognize the
 file, or an error results.
 
-   The function returns `TRUE' on success, otherwise `FALSE' with one
-of the following error codes:
+   The function returns 'TRUE' on success, otherwise 'FALSE' with one of
+the following error codes:
 
-   * `bfd_error_invalid_operation' - if `format' is not one of
-     `bfd_object', `bfd_archive' or `bfd_core'.
+   * 'bfd_error_invalid_operation' - if 'format' is not one of
+     'bfd_object', 'bfd_archive' or 'bfd_core'.
 
-   * `bfd_error_system_call' - if an error occured during a read - even
+   * 'bfd_error_system_call' - if an error occured during a read - even
      some file mismatches can cause bfd_error_system_calls.
 
-   * `file_not_recognised' - none of the backends recognised the file
+   * 'file_not_recognised' - none of the backends recognised the file
      format.
 
-   * `bfd_error_file_ambiguously_recognized' - more than one backend
+   * 'bfd_error_file_ambiguously_recognized' - more than one backend
      recognised the file format.
 
-2.9.1.2 `bfd_check_format_matches'
+2.9.1.2 'bfd_check_format_matches'
 ..................................
 
 *Synopsis*
      bfd_boolean bfd_check_format_matches
         (bfd *abfd, bfd_format format, char ***matching);
    *Description*
-Like `bfd_check_format', except when it returns FALSE with `bfd_errno'
-set to `bfd_error_file_ambiguously_recognized'.  In that case, if
+Like 'bfd_check_format', except when it returns FALSE with 'bfd_errno'
+set to 'bfd_error_file_ambiguously_recognized'.  In that case, if
 MATCHING is not NULL, it will be filled in with a NULL-terminated list
-of the names of the formats that matched, allocated with `malloc'.
-Then the user may choose a format and try again.
+of the names of the formats that matched, allocated with 'malloc'.  Then
+the user may choose a format and try again.
 
    When done with the list that MATCHING points to, the caller should
 free it.
 
-2.9.1.3 `bfd_set_format'
+2.9.1.3 'bfd_set_format'
 ........................
 
 *Synopsis*
      bfd_boolean bfd_set_format (bfd *abfd, bfd_format format);
    *Description*
-This function sets the file format of the BFD ABFD to the format
-FORMAT. If the target set in the BFD does not support the format
-requested, the format is invalid, or the BFD is not open for writing,
-then an error occurs.
+This function sets the file format of the BFD ABFD to the format FORMAT.
+If the target set in the BFD does not support the format requested, the
+format is invalid, or the BFD is not open for writing, then an error
+occurs.
 
-2.9.1.4 `bfd_format_string'
+2.9.1.4 'bfd_format_string'
 ...........................
 
 *Synopsis*
      const char *bfd_format_string (bfd_format format);
    *Description*
-Return a pointer to a const string `invalid', `object', `archive',
-`core', or `unknown', depending upon the value of FORMAT.
+Return a pointer to a const string 'invalid', 'object', 'archive',
+'core', or 'unknown', depending upon the value of FORMAT.
 
 
 File: bfd.info,  Node: Relocations,  Next: Core Files,  Prev: Formats,  Up: BFD front end
@@ -2928,16 +2916,16 @@ File: bfd.info,  Node: Relocations,  Next: Core Files,  Prev: Formats,  Up: BFD
 ================
 
 BFD maintains relocations in much the same way it maintains symbols:
-they are left alone until required, then read in en-masse and
-translated into an internal form.  A common routine
-`bfd_perform_relocation' acts upon the canonical form to do the fixup.
+they are left alone until required, then read in en-masse and translated
+into an internal form.  A common routine 'bfd_perform_relocation' acts
+upon the canonical form to do the fixup.
 
    Relocations are maintained on a per section basis, while symbols are
 maintained on a per BFD basis.
 
-   All that a back end has to do to fit the BFD interface is to create
-a `struct reloc_cache_entry' for each relocation in a particular
-section, and fill in the right bits of the structures.
+   All that a back end has to do to fit the BFD interface is to create a
+'struct reloc_cache_entry' for each relocation in a particular section,
+and fill in the right bits of the structures.
 
 * Menu:
 
@@ -3001,31 +2989,32 @@ This is the structure of a relocation entry:
 
      }
      arelent;
+
    *Description*
-Here is a description of each of the fields within an `arelent':
-
-   * `sym_ptr_ptr'
-   The symbol table pointer points to a pointer to the symbol
-associated with the relocation request.  It is the pointer into the
-table returned by the back end's `canonicalize_symtab' action. *Note
-Symbols::. The symbol is referenced through a pointer to a pointer so
-that tools like the linker can fix up all the symbols of the same name
-by modifying only one pointer. The relocation routine looks in the
-symbol and uses the base of the section the symbol is attached to and
-the value of the symbol as the initial relocation offset. If the symbol
-pointer is zero, then the section provided is looked up.
-
-   * `address'
-   The `address' field gives the offset in bytes from the base of the
+Here is a description of each of the fields within an 'arelent':
+
+   * 'sym_ptr_ptr'
+   The symbol table pointer points to a pointer to the symbol associated
+with the relocation request.  It is the pointer into the table returned
+by the back end's 'canonicalize_symtab' action.  *Note Symbols::.  The
+symbol is referenced through a pointer to a pointer so that tools like
+the linker can fix up all the symbols of the same name by modifying only
+one pointer.  The relocation routine looks in the symbol and uses the
+base of the section the symbol is attached to and the value of the
+symbol as the initial relocation offset.  If the symbol pointer is zero,
+then the section provided is looked up.
+
+   * 'address'
+   The 'address' field gives the offset in bytes from the base of the
 section data which owns the relocation record to the first byte of
-relocatable information. The actual data relocated will be relative to
-this point; for example, a relocation type which modifies the bottom
-two bytes of a four byte word would not touch the first byte pointed to
-in a big endian world.
-
-   * `addend'
-   The `addend' is a value provided by the back end to be added (!)  to
-the relocation offset. Its interpretation is dependent upon the howto.
+relocatable information.  The actual data relocated will be relative to
+this point; for example, a relocation type which modifies the bottom two
+bytes of a four byte word would not touch the first byte pointed to in a
+big endian world.
+
+   * 'addend'
+   The 'addend' is a value provided by the back end to be added (!)  to
+the relocation offset.  Its interpretation is dependent upon the howto.
 For example, on the 68k the code:
 
              char foo[];
@@ -3042,7 +3031,7 @@ For example, on the 68k the code:
              unlk fp
              rts
 
-   This could create a reloc pointing to `foo', but leave the offset in
+   This could create a reloc pointing to 'foo', but leave the offset in
 the data, something like:
 
      RELOCATION RECORDS FOR [.text]:
@@ -3056,15 +3045,15 @@ the data, something like:
      0000000e 4e75               ; rts
 
    Using coff and an 88k, some instructions don't have enough space in
-them to represent the full address range, and pointers have to be
-loaded in two parts. So you'd get something like:
+them to represent the full address range, and pointers have to be loaded
+in two parts.  So you'd get something like:
 
              or.u     r13,r0,hi16(_foo+0x12345678)
              ld.b     r2,r13,lo16(_foo+0x12345678)
              jmp      r1
 
-   This should create two relocs, both pointing to `_foo', and with
-0x12340000 in their addend field. The data would consist of:
+   This should create two relocs, both pointing to '_foo', and with
+0x12340000 in their addend field.  The data would consist of:
 
      RELOCATION RECORDS FOR [.text]:
      offset   type      value
@@ -3077,15 +3066,15 @@ loaded in two parts. So you'd get something like:
 
    The relocation routine digs out the value from the data, adds it to
 the addend to get the original offset, and then adds the value of
-`_foo'. Note that all 32 bits have to be kept around somewhere, to cope
+'_foo'.  Note that all 32 bits have to be kept around somewhere, to cope
 with carry from bit 15 to bit 16.
 
-   One further example is the sparc and the a.out format. The sparc has
+   One further example is the sparc and the a.out format.  The sparc has
 a similar problem to the 88k, in that some instructions don't have room
 for an entire offset, but on the sparc the parts are created in odd
-sized lumps. The designers of the a.out format chose to not use the
+sized lumps.  The designers of the a.out format chose to not use the
 data within the section for storing part of the offset; all the offset
-is kept within the reloc. Anything in the data should be ignored.
+is kept within the reloc.  Anything in the data should be ignored.
 
              save %sp,-112,%sp
              sethi %hi(_foo+0x12345678),%g2
@@ -3093,7 +3082,7 @@ is kept within the reloc. Anything in the data should be ignored.
              ret
              restore
 
-   Both relocs contain a pointer to `foo', and the offsets contain junk.
+   Both relocs contain a pointer to 'foo', and the offsets contain junk.
 
      RELOCATION RECORDS FOR [.text]:
      offset   type      value
@@ -3106,15 +3095,15 @@ is kept within the reloc. Anything in the data should be ignored.
      0000000c 81c7e008     ; ret
      00000010 81e80000     ; restore
 
-   * `howto'
-   The `howto' field can be imagined as a relocation instruction. It is
+   * 'howto'
+   The 'howto' field can be imagined as a relocation instruction.  It is
 a pointer to a structure which contains information on what to do with
-all of the other information in the reloc record and data section. A
+all of the other information in the reloc record and data section.  A
 back end would normally have a relocation instruction set and turn
 relocations into pointers to the correct structure on input - but it
 would be possible to create each howto field on demand.
 
-2.10.1.1 `enum complain_overflow'
+2.10.1.1 'enum complain_overflow'
 .................................
 
 Indicates what sort of overflow checking should be done when performing
@@ -3140,11 +3129,11 @@ a relocation.
        complain_overflow_unsigned
      };
 
-2.10.1.2 `reloc_howto_type'
+2.10.1.2 'reloc_howto_type'
 ...........................
 
-The `reloc_howto_type' is a structure which contains all the
-information that libbfd needs to know to tie up a back end's data.
+The 'reloc_howto_type' is a structure which contains all the information
+that libbfd needs to know to tie up a back end's data.
 
      struct bfd_symbol;             /* Forward declaration.  */
 
@@ -3232,8 +3221,8 @@ information that libbfd needs to know to tie up a back end's data.
           empty (e.g., m88k bcs); this flag signals the fact.  */
        bfd_boolean pcrel_offset;
      };
-   
-2.10.1.3 `The HOWTO Macro'
+
+2.10.1.3 'The HOWTO Macro'
 ..........................
 
 *Description*
@@ -3242,7 +3231,7 @@ The HOWTO define is horrible and will go away.
        { (unsigned) C, R, S, B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC }
 
    *Description*
-And will be replaced with the totally magic way. But for the moment, we
+And will be replaced with the totally magic way.  But for the moment, we
 are compatible, so do it this way.
      #define NEWHOWTO(FUNCTION, NAME, SIZE, REL, IN) \
        HOWTO (0, 0, SIZE, 0, REL, 0, complain_overflow_dont, FUNCTION, \
@@ -3271,7 +3260,7 @@ Helper routine to turn a symbol into a relocation value.
            }                                                 \
        }
 
-2.10.1.4 `bfd_get_reloc_size'
+2.10.1.4 'bfd_get_reloc_size'
 .............................
 
 *Synopsis*
@@ -3280,11 +3269,11 @@ Helper routine to turn a symbol into a relocation value.
 For a reloc_howto_type that operates on a fixed number of bytes, this
 returns the number of bytes operated on.
 
-2.10.1.5 `arelent_chain'
+2.10.1.5 'arelent_chain'
 ........................
 
 *Description*
-How relocs are tied together in an `asection':
+How relocs are tied together in an 'asection':
      typedef struct relent_chain
      {
        arelent relent;
@@ -3292,7 +3281,7 @@ How relocs are tied together in an `asection':
      }
      arelent_chain;
 
-2.10.1.6 `bfd_check_overflow'
+2.10.1.6 'bfd_check_overflow'
 .............................
 
 *Synopsis*
@@ -3306,9 +3295,9 @@ How relocs are tied together in an `asection':
 Perform overflow checking on RELOCATION which has BITSIZE significant
 bits and will be shifted right by RIGHTSHIFT bits, on a machine with
 addresses containing ADDRSIZE significant bits.  The result is either of
-`bfd_reloc_ok' or `bfd_reloc_overflow'.
+'bfd_reloc_ok' or 'bfd_reloc_overflow'.
 
-2.10.1.7 `bfd_perform_relocation'
+2.10.1.7 'bfd_perform_relocation'
 .................................
 
 *Synopsis*
@@ -3322,18 +3311,18 @@ addresses containing ADDRSIZE significant bits.  The result is either of
    *Description*
 If OUTPUT_BFD is supplied to this function, the generated image will be
 relocatable; the relocations are copied to the output file after they
-have been changed to reflect the new state of the world. There are two
+have been changed to reflect the new state of the world.  There are two
 ways of reflecting the results of partial linkage in an output file: by
 modifying the output data in place, and by modifying the relocation
 record.  Some native formats (e.g., basic a.out and basic coff) have no
-way of specifying an addend in the relocation type, so the addend has
-to go in the output data.  This is no big deal since in these formats
-the output data slot will always be big enough for the addend. Complex
+way of specifying an addend in the relocation type, so the addend has to
+go in the output data.  This is no big deal since in these formats the
+output data slot will always be big enough for the addend.  Complex
 reloc types with addends were invented to solve just this problem.  The
 ERROR_MESSAGE argument is set to an error message if this return
-`bfd_reloc_dangerous'.
+'bfd_reloc_dangerous'.
 
-2.10.1.8 `bfd_install_relocation'
+2.10.1.8 'bfd_install_relocation'
 .................................
 
 *Synopsis*
@@ -3344,7 +3333,7 @@ ERROR_MESSAGE argument is set to an error message if this return
          asection *input_section,
          char **error_message);
    *Description*
-This looks remarkably like `bfd_perform_relocation', except it does not
+This looks remarkably like 'bfd_perform_relocation', except it does not
 expect that the section contents have been filled in.  I.e., it's
 suitable for use when creating, rather than applying a relocation.
 
@@ -3361,20 +3350,20 @@ When an application wants to create a relocation, but doesn't know what
 the target machine might call it, it can find out by using this bit of
 code.
 
-2.10.2.1 `bfd_reloc_code_type'
+2.10.2.1 'bfd_reloc_code_type'
 ..............................
 
 *Description*
 The insides of a reloc code.  The idea is that, eventually, there will
 be one enumerator for every type of relocation we ever do.  Pass one of
-these values to `bfd_reloc_type_lookup', and it'll return a howto
+these values to 'bfd_reloc_type_lookup', and it'll return a howto
 pointer.
 
    This does mean that the application must determine the correct
 enumerator value; you can't get a howto pointer from a random set of
 attributes.
 
-   Here are the possible values for `enum bfd_reloc_code_real':
+   Here are the possible values for 'enum bfd_reloc_code_real':
 
  -- : BFD_RELOC_64
  -- : BFD_RELOC_32
@@ -3384,7 +3373,6 @@ attributes.
  -- : BFD_RELOC_14
  -- : BFD_RELOC_8
      Basic absolute relocations of N bits.
-
  -- : BFD_RELOC_64_PCREL
  -- : BFD_RELOC_32_PCREL
  -- : BFD_RELOC_24_PCREL
@@ -3397,10 +3385,8 @@ attributes.
      the specific target.
 
      The 24-bit relocation is used in some Intel 960 configurations.
-
  -- : BFD_RELOC_32_SECREL
      Section relative relocations.  Some targets need this for DWARF2.
-
  -- : BFD_RELOC_32_GOT_PCREL
  -- : BFD_RELOC_16_GOT_PCREL
  -- : BFD_RELOC_8_GOT_PCREL
@@ -3423,11 +3409,9 @@ attributes.
  -- : BFD_RELOC_HI16_S_PLTOFF
  -- : BFD_RELOC_8_PLTOFF
      For ELF.
-
  -- : BFD_RELOC_SIZE32
  -- : BFD_RELOC_SIZE64
      Size relocations.
-
  -- : BFD_RELOC_68K_GLOB_DAT
  -- : BFD_RELOC_68K_JMP_SLOT
  -- : BFD_RELOC_68K_RELATIVE
@@ -3447,7 +3431,6 @@ attributes.
  -- : BFD_RELOC_68K_TLS_LE16
  -- : BFD_RELOC_68K_TLS_LE8
      Relocations used by 68K ELF.
-
  -- : BFD_RELOC_32_BASEREL
  -- : BFD_RELOC_16_BASEREL
  -- : BFD_RELOC_LO16_BASEREL
@@ -3456,35 +3439,29 @@ attributes.
  -- : BFD_RELOC_8_BASEREL
  -- : BFD_RELOC_RVA
      Linkage-table relative.
-
  -- : BFD_RELOC_8_FFnn
      Absolute 8-bit relocation, but used to form an address like 0xFFnn.
-
  -- : BFD_RELOC_32_PCREL_S2
  -- : BFD_RELOC_16_PCREL_S2
  -- : BFD_RELOC_23_PCREL_S2
      These PC-relative relocations are stored as word displacements -
      i.e., byte displacements shifted right two bits.  The 30-bit word
      displacement (<<32_PCREL_S2>> - 32 bits, shifted 2) is used on the
-     SPARC.  (SPARC tools generally refer to this as <<WDISP30>>.)  The
+     SPARC. (SPARC tools generally refer to this as <<WDISP30>>.)  The
      signed 16-bit displacement is used on the MIPS, and the 23-bit
      displacement is used on the Alpha.
-
  -- : BFD_RELOC_HI22
  -- : BFD_RELOC_LO10
      High 22 bits and low 10 bits of 32-bit value, placed into lower
      bits of the target word.  These are used on the SPARC.
-
  -- : BFD_RELOC_GPREL16
  -- : BFD_RELOC_GPREL32
      For systems that allocate a Global Pointer register, these are
      displacements off that register.  These relocation types are
      handled specially, because the value the register will have is
      decided relatively late.
-
  -- : BFD_RELOC_I960_CALLJ
      Reloc types used for i960/b.out.
-
  -- : BFD_RELOC_NONE
  -- : BFD_RELOC_SPARC_WDISP22
  -- : BFD_RELOC_SPARC22
@@ -3511,11 +3488,9 @@ attributes.
  -- : BFD_RELOC_SPARC_IRELATIVE
      SPARC ELF relocations.  There is probably some overlap with other
      relocation types already defined.
-
  -- : BFD_RELOC_SPARC_BASE13
  -- : BFD_RELOC_SPARC_BASE22
      I think these are specific to SPARC a.out (e.g., Sun 4).
-
  -- : BFD_RELOC_SPARC_64
  -- : BFD_RELOC_SPARC_10
  -- : BFD_RELOC_SPARC_11
@@ -3545,10 +3520,8 @@ attributes.
  -- : BFD_RELOC_SPARC_SIZE64
  -- : BFD_RELOC_SPARC_WDISP10
      SPARC64 relocations
-
  -- : BFD_RELOC_SPARC_REV32
      SPARC little endian relocation
-
  -- : BFD_RELOC_SPARC_TLS_GD_HI22
  -- : BFD_RELOC_SPARC_TLS_GD_LO10
  -- : BFD_RELOC_SPARC_TLS_GD_ADD
@@ -3574,7 +3547,6 @@ attributes.
  -- : BFD_RELOC_SPARC_TLS_TPOFF32
  -- : BFD_RELOC_SPARC_TLS_TPOFF64
      SPARC TLS relocations
-
  -- : BFD_RELOC_SPU_IMM7
  -- : BFD_RELOC_SPU_IMM8
  -- : BFD_RELOC_SPU_IMM10
@@ -3591,7 +3563,6 @@ attributes.
  -- : BFD_RELOC_SPU_PPU64
  -- : BFD_RELOC_SPU_ADD_PIC
      SPU Relocations.
-
  -- : BFD_RELOC_ALPHA_GPDISP_HI16
      Alpha ECOFF and ELF relocations.  Some of these treat the symbol or
      "addend" in some special way.  For GPDISP_HI16 ("gpdisp")
@@ -3599,18 +3570,15 @@ attributes.
      will be the absolute section symbol.  The addend is the
      displacement in bytes of the "lda" instruction from the "ldah"
      instruction (which is at the address of this reloc).
-
  -- : BFD_RELOC_ALPHA_GPDISP_LO16
      For GPDISP_LO16 ("ignore") relocations, the symbol is handled as
      with GPDISP_HI16 relocs.  The addend is ignored when writing the
      relocations out, and is filled in with the file's GP value on
      reading, for convenience.
-
  -- : BFD_RELOC_ALPHA_GPDISP
      The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
      relocation except that there is no accompanying GPDISP_LO16
      relocation.
-
  -- : BFD_RELOC_ALPHA_LITERAL
  -- : BFD_RELOC_ALPHA_ELF_LITERAL
  -- : BFD_RELOC_ALPHA_LITUSE
@@ -3635,48 +3603,38 @@ attributes.
      optimize away some literal section references.  The symbol is
      ignored (read as the absolute section symbol), and the "addend"
      indicates the type of instruction using the register: 1 - "memory"
-     fmt insn 2 - byte-manipulation (byte offset reg) 3 - jsr (target
-     of branch)
-
+     fmt insn 2 - byte-manipulation (byte offset reg) 3 - jsr (target of
+     branch)
  -- : BFD_RELOC_ALPHA_HINT
      The HINT relocation indicates a value that should be filled into
      the "hint" field of a jmp/jsr/ret instruction, for possible branch-
      prediction logic which may be provided on some processors.
-
  -- : BFD_RELOC_ALPHA_LINKAGE
      The LINKAGE relocation outputs a linkage pair in the object file,
      which is filled by the linker.
-
  -- : BFD_RELOC_ALPHA_CODEADDR
      The CODEADDR relocation outputs a STO_CA in the object file, which
      is filled by the linker.
-
  -- : BFD_RELOC_ALPHA_GPREL_HI16
  -- : BFD_RELOC_ALPHA_GPREL_LO16
      The GPREL_HI/LO relocations together form a 32-bit offset from the
      GP register.
-
  -- : BFD_RELOC_ALPHA_BRSGP
      Like BFD_RELOC_23_PCREL_S2, except that the source and target must
      share a common GP, and the target address is adjusted for
      STO_ALPHA_STD_GPLOAD.
-
  -- : BFD_RELOC_ALPHA_NOP
      The NOP relocation outputs a NOP if the longword displacement
      between two procedure entry points is < 2^21.
-
  -- : BFD_RELOC_ALPHA_BSR
      The BSR relocation outputs a BSR if the longword displacement
      between two procedure entry points is < 2^21.
-
  -- : BFD_RELOC_ALPHA_LDA
      The LDA relocation outputs a LDA if the longword displacement
      between two procedure entry points is < 2^16.
-
  -- : BFD_RELOC_ALPHA_BOH
      The BOH relocation outputs a BSR if the longword displacement
      between two procedure entry points is < 2^21, or else a hint.
-
  -- : BFD_RELOC_ALPHA_TLSGD
  -- : BFD_RELOC_ALPHA_TLSLDM
  -- : BFD_RELOC_ALPHA_DTPMOD64
@@ -3691,55 +3649,41 @@ attributes.
  -- : BFD_RELOC_ALPHA_TPREL_LO16
  -- : BFD_RELOC_ALPHA_TPREL16
      Alpha thread-local storage relocations.
-
  -- : BFD_RELOC_MIPS_JMP
  -- : BFD_RELOC_MICROMIPS_JMP
      The MIPS jump instruction.
-
  -- : BFD_RELOC_MIPS16_JMP
      The MIPS16 jump instruction.
-
  -- : BFD_RELOC_MIPS16_GPREL
      MIPS16 GP relative reloc.
-
  -- : BFD_RELOC_HI16
      High 16 bits of 32-bit value; simple reloc.
-
  -- : BFD_RELOC_HI16_S
      High 16 bits of 32-bit value but the low 16 bits will be sign
      extended and added to form the final result.  If the low 16 bits
      form a negative number, we need to add one to the high value to
      compensate for the borrow when the low bits are added.
-
  -- : BFD_RELOC_LO16
      Low 16 bits.
-
  -- : BFD_RELOC_HI16_PCREL
      High 16 bits of 32-bit pc-relative value
-
  -- : BFD_RELOC_HI16_S_PCREL
      High 16 bits of 32-bit pc-relative value, adjusted
-
  -- : BFD_RELOC_LO16_PCREL
      Low 16 bits of pc-relative value
-
  -- : BFD_RELOC_MIPS16_GOT16
  -- : BFD_RELOC_MIPS16_CALL16
      Equivalent of BFD_RELOC_MIPS_*, but with the MIPS16 layout of
      16-bit immediate fields
-
  -- : BFD_RELOC_MIPS16_HI16
      MIPS16 high 16 bits of 32-bit value.
-
  -- : BFD_RELOC_MIPS16_HI16_S
      MIPS16 high 16 bits of 32-bit value but the low 16 bits will be
      sign extended and added to form the final result.  If the low 16
      bits form a negative number, we need to add one to the high value
      to compensate for the borrow when the low bits are added.
-
  -- : BFD_RELOC_MIPS16_LO16
      MIPS16 low 16 bits.
-
  -- : BFD_RELOC_MIPS16_TLS_GD
  -- : BFD_RELOC_MIPS16_TLS_LDM
  -- : BFD_RELOC_MIPS16_TLS_DTPREL_HI16
@@ -3748,22 +3692,18 @@ attributes.
  -- : BFD_RELOC_MIPS16_TLS_TPREL_HI16
  -- : BFD_RELOC_MIPS16_TLS_TPREL_LO16
      MIPS16 TLS relocations
-
  -- : BFD_RELOC_MIPS_LITERAL
  -- : BFD_RELOC_MICROMIPS_LITERAL
      Relocation against a MIPS literal section.
-
  -- : BFD_RELOC_MICROMIPS_7_PCREL_S1
  -- : BFD_RELOC_MICROMIPS_10_PCREL_S1
  -- : BFD_RELOC_MICROMIPS_16_PCREL_S1
      microMIPS PC-relative relocations.
-
  -- : BFD_RELOC_MICROMIPS_GPREL16
  -- : BFD_RELOC_MICROMIPS_HI16
  -- : BFD_RELOC_MICROMIPS_HI16_S
  -- : BFD_RELOC_MICROMIPS_LO16
      microMIPS versions of generic BFD relocs.
-
  -- : BFD_RELOC_MIPS_GOT16
  -- : BFD_RELOC_MICROMIPS_GOT16
  -- : BFD_RELOC_MIPS_CALL16
@@ -3819,15 +3759,13 @@ attributes.
  -- : BFD_RELOC_MICROMIPS_TLS_TPREL_HI16
  -- : BFD_RELOC_MIPS_TLS_TPREL_LO16
  -- : BFD_RELOC_MICROMIPS_TLS_TPREL_LO16
+ -- : BFD_RELOC_MIPS_EH
      MIPS ELF relocations.
-
  -- : BFD_RELOC_MIPS_COPY
  -- : BFD_RELOC_MIPS_JUMP_SLOT
      MIPS ELF relocations (VxWorks and PLT extensions).
-
  -- : BFD_RELOC_MOXIE_10_PCREL
      Moxie ELF relocations.
-
  -- : BFD_RELOC_FRV_LABEL16
  -- : BFD_RELOC_FRV_LABEL24
  -- : BFD_RELOC_FRV_LO16
@@ -3868,43 +3806,32 @@ attributes.
  -- : BFD_RELOC_FRV_TLSOFF_RELAX
  -- : BFD_RELOC_FRV_TLSMOFF
      Fujitsu Frv Relocations.
-
  -- : BFD_RELOC_MN10300_GOTOFF24
      This is a 24bit GOT-relative reloc for the mn10300.
-
  -- : BFD_RELOC_MN10300_GOT32
      This is a 32bit GOT-relative reloc for the mn10300, offset by two
      bytes in the instruction.
-
  -- : BFD_RELOC_MN10300_GOT24
      This is a 24bit GOT-relative reloc for the mn10300, offset by two
      bytes in the instruction.
-
  -- : BFD_RELOC_MN10300_GOT16
      This is a 16bit GOT-relative reloc for the mn10300, offset by two
      bytes in the instruction.
-
  -- : BFD_RELOC_MN10300_COPY
      Copy symbol at runtime.
-
  -- : BFD_RELOC_MN10300_GLOB_DAT
      Create GOT entry.
-
  -- : BFD_RELOC_MN10300_JMP_SLOT
      Create PLT entry.
-
  -- : BFD_RELOC_MN10300_RELATIVE
      Adjust by program base.
-
  -- : BFD_RELOC_MN10300_SYM_DIFF
      Together with another reloc targeted at the same location, allows
      for a value that is the difference of two symbols in the same
      section.
-
  -- : BFD_RELOC_MN10300_ALIGN
      The addend of this reloc is an alignment power that must be
      honoured at the offset's location, regardless of linker relaxation.
-
  -- : BFD_RELOC_MN10300_TLS_GD
  -- : BFD_RELOC_MN10300_TLS_LD
  -- : BFD_RELOC_MN10300_TLS_LDO
@@ -3915,15 +3842,12 @@ attributes.
  -- : BFD_RELOC_MN10300_TLS_DTPOFF
  -- : BFD_RELOC_MN10300_TLS_TPOFF
      Various TLS-related relocations.
-
  -- : BFD_RELOC_MN10300_32_PCREL
-     This is a 32bit pcrel reloc for the mn10300, offset by two bytes
-     in the instruction.
-
+     This is a 32bit pcrel reloc for the mn10300, offset by two bytes in
+     the instruction.
  -- : BFD_RELOC_MN10300_16_PCREL
-     This is a 16bit pcrel reloc for the mn10300, offset by two bytes
-     in the instruction.
-
+     This is a 16bit pcrel reloc for the mn10300, offset by two bytes in
+     the instruction.
  -- : BFD_RELOC_386_GOT32
  -- : BFD_RELOC_386_PLT32
  -- : BFD_RELOC_386_COPY
@@ -3949,7 +3873,6 @@ attributes.
  -- : BFD_RELOC_386_TLS_DESC
  -- : BFD_RELOC_386_IRELATIVE
      i386/elf relocations
-
  -- : BFD_RELOC_X86_64_GOT32
  -- : BFD_RELOC_X86_64_PLT32
  -- : BFD_RELOC_X86_64_COPY
@@ -3977,8 +3900,9 @@ attributes.
  -- : BFD_RELOC_X86_64_TLSDESC_CALL
  -- : BFD_RELOC_X86_64_TLSDESC
  -- : BFD_RELOC_X86_64_IRELATIVE
+ -- : BFD_RELOC_X86_64_PC32_BND
+ -- : BFD_RELOC_X86_64_PLT32_BND
      x86-64/elf relocations
-
  -- : BFD_RELOC_NS32K_IMM_8
  -- : BFD_RELOC_NS32K_IMM_16
  -- : BFD_RELOC_NS32K_IMM_32
@@ -3992,11 +3916,9 @@ attributes.
  -- : BFD_RELOC_NS32K_DISP_16_PCREL
  -- : BFD_RELOC_NS32K_DISP_32_PCREL
      ns32k relocations
-
  -- : BFD_RELOC_PDP11_DISP_8_PCREL
  -- : BFD_RELOC_PDP11_DISP_6_PCREL
      PDP11 relocations
-
  -- : BFD_RELOC_PJ_CODE_HI16
  -- : BFD_RELOC_PJ_CODE_LO16
  -- : BFD_RELOC_PJ_CODE_DIR16
@@ -4004,7 +3926,6 @@ attributes.
  -- : BFD_RELOC_PJ_CODE_REL16
  -- : BFD_RELOC_PJ_CODE_REL32
      Picojava relocs.  Not all of these appear in object files.
-
  -- : BFD_RELOC_PPC_B26
  -- : BFD_RELOC_PPC_BA26
  -- : BFD_RELOC_PPC_TOC16
@@ -4075,8 +3996,9 @@ attributes.
  -- : BFD_RELOC_PPC64_TOC16_LO_DS
  -- : BFD_RELOC_PPC64_PLTGOT16_DS
  -- : BFD_RELOC_PPC64_PLTGOT16_LO_DS
+ -- : BFD_RELOC_PPC64_ADDR16_HIGH
+ -- : BFD_RELOC_PPC64_ADDR16_HIGHA
      Power(rs6000) and PowerPC relocations.
-
  -- : BFD_RELOC_PPC_TLS
  -- : BFD_RELOC_PPC_TLSGD
  -- : BFD_RELOC_PPC_TLSLD
@@ -4119,38 +4041,34 @@ attributes.
  -- : BFD_RELOC_PPC64_DTPREL16_HIGHERA
  -- : BFD_RELOC_PPC64_DTPREL16_HIGHEST
  -- : BFD_RELOC_PPC64_DTPREL16_HIGHESTA
+ -- : BFD_RELOC_PPC64_TPREL16_HIGH
+ -- : BFD_RELOC_PPC64_TPREL16_HIGHA
+ -- : BFD_RELOC_PPC64_DTPREL16_HIGH
+ -- : BFD_RELOC_PPC64_DTPREL16_HIGHA
      PowerPC and PowerPC64 thread-local storage relocations.
-
  -- : BFD_RELOC_I370_D12
      IBM 370/390 relocations
-
  -- : BFD_RELOC_CTOR
      The type of reloc used to build a constructor table - at the moment
      probably a 32 bit wide absolute relocation, but the target can
      choose.  It generally does map to one of the other relocation
      types.
-
  -- : BFD_RELOC_ARM_PCREL_BRANCH
      ARM 26 bit pc-relative branch.  The lowest two bits must be zero
      and are not stored in the instruction.
-
  -- : BFD_RELOC_ARM_PCREL_BLX
      ARM 26 bit pc-relative branch.  The lowest bit must be zero and is
      not stored in the instruction.  The 2nd lowest bit comes from a 1
      bit field in the instruction.
-
  -- : BFD_RELOC_THUMB_PCREL_BLX
      Thumb 22 bit pc-relative branch.  The lowest bit must be zero and
      is not stored in the instruction.  The 2nd lowest bit comes from a
      1 bit field in the instruction.
-
  -- : BFD_RELOC_ARM_PCREL_CALL
      ARM 26-bit pc-relative branch for an unconditional BL or BLX
      instruction.
-
  -- : BFD_RELOC_ARM_PCREL_JUMP
      ARM 26-bit pc-relative branch for B or conditional BL instruction.
-
  -- : BFD_RELOC_THUMB_PCREL_BRANCH7
  -- : BFD_RELOC_THUMB_PCREL_BRANCH9
  -- : BFD_RELOC_THUMB_PCREL_BRANCH12
@@ -4158,37 +4076,29 @@ attributes.
  -- : BFD_RELOC_THUMB_PCREL_BRANCH23
  -- : BFD_RELOC_THUMB_PCREL_BRANCH25
      Thumb 7-, 9-, 12-, 20-, 23-, and 25-bit pc-relative branches.  The
-     lowest bit must be zero and is not stored in the instruction.
-     Note that the corresponding ELF R_ARM_THM_JUMPnn constant has an
-     "nn" one smaller in all cases.  Note further that BRANCH23
-     corresponds to R_ARM_THM_CALL.
-
+     lowest bit must be zero and is not stored in the instruction.  Note
+     that the corresponding ELF R_ARM_THM_JUMPnn constant has an "nn"
+     one smaller in all cases.  Note further that BRANCH23 corresponds
+     to R_ARM_THM_CALL.
  -- : BFD_RELOC_ARM_OFFSET_IMM
      12-bit immediate offset, used in ARM-format ldr and str
      instructions.
-
  -- : BFD_RELOC_ARM_THUMB_OFFSET
      5-bit immediate offset, used in Thumb-format ldr and str
      instructions.
-
  -- : BFD_RELOC_ARM_TARGET1
      Pc-relative or absolute relocation depending on target.  Used for
      entries in .init_array sections.
-
  -- : BFD_RELOC_ARM_ROSEGREL32
      Read-only segment base relative address.
-
  -- : BFD_RELOC_ARM_SBREL32
      Data segment base relative address.
-
  -- : BFD_RELOC_ARM_TARGET2
      This reloc is used for references to RTTI data from exception
      handling tables.  The actual definition depends on the target.  It
      may be a pc-relative or some form of GOT-indirect relocation.
-
  -- : BFD_RELOC_ARM_PREL31
      31-bit PC relative address.
-
  -- : BFD_RELOC_ARM_MOVW
  -- : BFD_RELOC_ARM_MOVT
  -- : BFD_RELOC_ARM_MOVW_PCREL
@@ -4198,7 +4108,6 @@ attributes.
  -- : BFD_RELOC_ARM_THUMB_MOVW_PCREL
  -- : BFD_RELOC_ARM_THUMB_MOVT_PCREL
      Low and High halfword relocations for MOVW and MOVT instructions.
-
  -- : BFD_RELOC_ARM_JUMP_SLOT
  -- : BFD_RELOC_ARM_GLOB_DAT
  -- : BFD_RELOC_ARM_GOT32
@@ -4208,7 +4117,6 @@ attributes.
  -- : BFD_RELOC_ARM_GOTPC
  -- : BFD_RELOC_ARM_GOT_PREL
      Relocations for setting up GOTs and PLTs for shared libraries.
-
  -- : BFD_RELOC_ARM_TLS_GD32
  -- : BFD_RELOC_ARM_TLS_LDO32
  -- : BFD_RELOC_ARM_TLS_LDM32
@@ -4224,7 +4132,6 @@ attributes.
  -- : BFD_RELOC_ARM_THM_TLS_DESCSEQ
  -- : BFD_RELOC_ARM_TLS_DESC
      ARM thread-local storage relocations.
-
  -- : BFD_RELOC_ARM_ALU_PC_G0_NC
  -- : BFD_RELOC_ARM_ALU_PC_G0
  -- : BFD_RELOC_ARM_ALU_PC_G1_NC
@@ -4254,13 +4161,10 @@ attributes.
  -- : BFD_RELOC_ARM_LDC_SB_G1
  -- : BFD_RELOC_ARM_LDC_SB_G2
      ARM group relocations.
-
  -- : BFD_RELOC_ARM_V4BX
      Annotation of BX instructions.
-
  -- : BFD_RELOC_ARM_IRELATIVE
      ARM support for STT_GNU_IFUNC.
-
  -- : BFD_RELOC_ARM_IMMEDIATE
  -- : BFD_RELOC_ARM_ADRL_IMMEDIATE
  -- : BFD_RELOC_ARM_T32_IMMEDIATE
@@ -4289,7 +4193,6 @@ attributes.
  -- : BFD_RELOC_ARM_THUMB_SHIFT
      These relocs are only used within the ARM assembler.  They are not
      (at present) written to any object files.
-
  -- : BFD_RELOC_SH_PCDISP8BY2
  -- : BFD_RELOC_SH_PCDISP12BY2
  -- : BFD_RELOC_SH_IMM3
@@ -4389,50 +4292,36 @@ attributes.
  -- : BFD_RELOC_SH_FUNCDESC
      Renesas / SuperH SH relocs.  Not all of these appear in object
      files.
-
  -- : BFD_RELOC_ARC_B22_PCREL
      ARC Cores relocs.  ARC 22 bit pc-relative branch.  The lowest two
      bits must be zero and are not stored in the instruction.  The high
      20 bits are installed in bits 26 through 7 of the instruction.
-
  -- : BFD_RELOC_ARC_B26
      ARC 26 bit absolute branch.  The lowest two bits must be zero and
      are not stored in the instruction.  The high 24 bits are installed
      in bits 23 through 0.
-
  -- : BFD_RELOC_BFIN_16_IMM
      ADI Blackfin 16 bit immediate absolute reloc.
-
  -- : BFD_RELOC_BFIN_16_HIGH
      ADI Blackfin 16 bit immediate absolute reloc higher 16 bits.
-
  -- : BFD_RELOC_BFIN_4_PCREL
      ADI Blackfin 'a' part of LSETUP.
-
  -- : BFD_RELOC_BFIN_5_PCREL
      ADI Blackfin.
-
  -- : BFD_RELOC_BFIN_16_LOW
      ADI Blackfin 16 bit immediate absolute reloc lower 16 bits.
-
  -- : BFD_RELOC_BFIN_10_PCREL
      ADI Blackfin.
-
  -- : BFD_RELOC_BFIN_11_PCREL
      ADI Blackfin 'b' part of LSETUP.
-
  -- : BFD_RELOC_BFIN_12_PCREL_JUMP
      ADI Blackfin.
-
  -- : BFD_RELOC_BFIN_12_PCREL_JUMP_S
      ADI Blackfin Short jump, pcrel.
-
  -- : BFD_RELOC_BFIN_24_PCREL_CALL_X
      ADI Blackfin Call.x not implemented.
-
  -- : BFD_RELOC_BFIN_24_PCREL_JUMP_L
      ADI Blackfin Long Jump pcrel.
-
  -- : BFD_RELOC_BFIN_GOT17M4
  -- : BFD_RELOC_BFIN_GOTHI
  -- : BFD_RELOC_BFIN_GOTLO
@@ -4448,176 +4337,126 @@ attributes.
  -- : BFD_RELOC_BFIN_GOTOFFHI
  -- : BFD_RELOC_BFIN_GOTOFFLO
      ADI Blackfin FD-PIC relocations.
-
  -- : BFD_RELOC_BFIN_GOT
      ADI Blackfin GOT relocation.
-
  -- : BFD_RELOC_BFIN_PLTPC
      ADI Blackfin PLTPC relocation.
-
  -- : BFD_ARELOC_BFIN_PUSH
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_CONST
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_ADD
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_SUB
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_MULT
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_DIV
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_MOD
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_LSHIFT
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_RSHIFT
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_AND
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_OR
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_XOR
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_LAND
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_LOR
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_LEN
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_NEG
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_COMP
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_PAGE
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_HWPAGE
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_ARELOC_BFIN_ADDR
      ADI Blackfin arithmetic relocation.
-
  -- : BFD_RELOC_D10V_10_PCREL_R
      Mitsubishi D10V relocs.  This is a 10-bit reloc with the right 2
      bits assumed to be 0.
-
  -- : BFD_RELOC_D10V_10_PCREL_L
      Mitsubishi D10V relocs.  This is a 10-bit reloc with the right 2
      bits assumed to be 0.  This is the same as the previous reloc
      except it is in the left container, i.e., shifted left 15 bits.
-
  -- : BFD_RELOC_D10V_18
      This is an 18-bit reloc with the right 2 bits assumed to be 0.
-
  -- : BFD_RELOC_D10V_18_PCREL
      This is an 18-bit reloc with the right 2 bits assumed to be 0.
-
  -- : BFD_RELOC_D30V_6
      Mitsubishi D30V relocs.  This is a 6-bit absolute reloc.
-
  -- : BFD_RELOC_D30V_9_PCREL
      This is a 6-bit pc-relative reloc with the right 3 bits assumed to
      be 0.
-
  -- : BFD_RELOC_D30V_9_PCREL_R
      This is a 6-bit pc-relative reloc with the right 3 bits assumed to
-     be 0. Same as the previous reloc but on the right side of the
+     be 0.  Same as the previous reloc but on the right side of the
      container.
-
  -- : BFD_RELOC_D30V_15
      This is a 12-bit absolute reloc with the right 3 bitsassumed to be
      0.
-
  -- : BFD_RELOC_D30V_15_PCREL
-     This is a 12-bit pc-relative reloc with the right 3 bits assumed
-     to be 0.
-
+     This is a 12-bit pc-relative reloc with the right 3 bits assumed to
+     be 0.
  -- : BFD_RELOC_D30V_15_PCREL_R
-     This is a 12-bit pc-relative reloc with the right 3 bits assumed
-     to be 0. Same as the previous reloc but on the right side of the
+     This is a 12-bit pc-relative reloc with the right 3 bits assumed to
+     be 0.  Same as the previous reloc but on the right side of the
      container.
-
  -- : BFD_RELOC_D30V_21
      This is an 18-bit absolute reloc with the right 3 bits assumed to
      be 0.
-
  -- : BFD_RELOC_D30V_21_PCREL
      This is an 18-bit pc-relative reloc with the right 3 bits assumed
      to be 0.
-
  -- : BFD_RELOC_D30V_21_PCREL_R
      This is an 18-bit pc-relative reloc with the right 3 bits assumed
-     to be 0. Same as the previous reloc but on the right side of the
+     to be 0.  Same as the previous reloc but on the right side of the
      container.
-
  -- : BFD_RELOC_D30V_32
      This is a 32-bit absolute reloc.
-
  -- : BFD_RELOC_D30V_32_PCREL
      This is a 32-bit pc-relative reloc.
-
  -- : BFD_RELOC_DLX_HI16_S
      DLX relocs
-
  -- : BFD_RELOC_DLX_LO16
      DLX relocs
-
  -- : BFD_RELOC_DLX_JMP26
      DLX relocs
-
  -- : BFD_RELOC_M32C_HI8
  -- : BFD_RELOC_M32C_RL_JUMP
  -- : BFD_RELOC_M32C_RL_1ADDR
  -- : BFD_RELOC_M32C_RL_2ADDR
      Renesas M16C/M32C Relocations.
-
  -- : BFD_RELOC_M32R_24
      Renesas M32R (formerly Mitsubishi M32R) relocs.  This is a 24 bit
      absolute address.
-
  -- : BFD_RELOC_M32R_10_PCREL
-     This is a 10-bit pc-relative reloc with the right 2 bits assumed
-     to be 0.
-
+     This is a 10-bit pc-relative reloc with the right 2 bits assumed to
+     be 0.
  -- : BFD_RELOC_M32R_18_PCREL
      This is an 18-bit reloc with the right 2 bits assumed to be 0.
-
  -- : BFD_RELOC_M32R_26_PCREL
      This is a 26-bit reloc with the right 2 bits assumed to be 0.
-
  -- : BFD_RELOC_M32R_HI16_ULO
      This is a 16-bit reloc containing the high 16 bits of an address
      used when the lower 16 bits are treated as unsigned.
-
  -- : BFD_RELOC_M32R_HI16_SLO
      This is a 16-bit reloc containing the high 16 bits of an address
      used when the lower 16 bits are treated as signed.
-
  -- : BFD_RELOC_M32R_LO16
      This is a 16-bit reloc containing the lower 16 bits of an address.
-
  -- : BFD_RELOC_M32R_SDA16
      This is a 16-bit reloc containing the small data area offset for
      use in add3, load, and store instructions.
-
  -- : BFD_RELOC_M32R_GOT24
  -- : BFD_RELOC_M32R_26_PLTREL
  -- : BFD_RELOC_M32R_COPY
@@ -4636,168 +4475,119 @@ attributes.
  -- : BFD_RELOC_M32R_GOTPC_HI_SLO
  -- : BFD_RELOC_M32R_GOTPC_LO
      For PIC.
-
  -- : BFD_RELOC_V850_9_PCREL
      This is a 9-bit reloc
-
  -- : BFD_RELOC_V850_22_PCREL
      This is a 22-bit reloc
-
  -- : BFD_RELOC_V850_SDA_16_16_OFFSET
      This is a 16 bit offset from the short data area pointer.
-
  -- : BFD_RELOC_V850_SDA_15_16_OFFSET
      This is a 16 bit offset (of which only 15 bits are used) from the
      short data area pointer.
-
  -- : BFD_RELOC_V850_ZDA_16_16_OFFSET
      This is a 16 bit offset from the zero data area pointer.
-
  -- : BFD_RELOC_V850_ZDA_15_16_OFFSET
      This is a 16 bit offset (of which only 15 bits are used) from the
      zero data area pointer.
-
  -- : BFD_RELOC_V850_TDA_6_8_OFFSET
      This is an 8 bit offset (of which only 6 bits are used) from the
      tiny data area pointer.
-
  -- : BFD_RELOC_V850_TDA_7_8_OFFSET
      This is an 8bit offset (of which only 7 bits are used) from the
      tiny data area pointer.
-
  -- : BFD_RELOC_V850_TDA_7_7_OFFSET
      This is a 7 bit offset from the tiny data area pointer.
-
  -- : BFD_RELOC_V850_TDA_16_16_OFFSET
      This is a 16 bit offset from the tiny data area pointer.
-
  -- : BFD_RELOC_V850_TDA_4_5_OFFSET
      This is a 5 bit offset (of which only 4 bits are used) from the
      tiny data area pointer.
-
  -- : BFD_RELOC_V850_TDA_4_4_OFFSET
      This is a 4 bit offset from the tiny data area pointer.
-
  -- : BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET
      This is a 16 bit offset from the short data area pointer, with the
      bits placed non-contiguously in the instruction.
-
  -- : BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET
      This is a 16 bit offset from the zero data area pointer, with the
      bits placed non-contiguously in the instruction.
-
  -- : BFD_RELOC_V850_CALLT_6_7_OFFSET
      This is a 6 bit offset from the call table base pointer.
-
  -- : BFD_RELOC_V850_CALLT_16_16_OFFSET
      This is a 16 bit offset from the call table base pointer.
-
  -- : BFD_RELOC_V850_LONGCALL
      Used for relaxing indirect function calls.
-
  -- : BFD_RELOC_V850_LONGJUMP
      Used for relaxing indirect jumps.
-
  -- : BFD_RELOC_V850_ALIGN
      Used to maintain alignment whilst relaxing.
-
  -- : BFD_RELOC_V850_LO16_SPLIT_OFFSET
      This is a variation of BFD_RELOC_LO16 that can be used in v850e
      ld.bu instructions.
-
  -- : BFD_RELOC_V850_16_PCREL
      This is a 16-bit reloc.
-
  -- : BFD_RELOC_V850_17_PCREL
      This is a 17-bit reloc.
-
  -- : BFD_RELOC_V850_23
      This is a 23-bit reloc.
-
  -- : BFD_RELOC_V850_32_PCREL
      This is a 32-bit reloc.
-
  -- : BFD_RELOC_V850_32_ABS
      This is a 32-bit reloc.
-
  -- : BFD_RELOC_V850_16_SPLIT_OFFSET
      This is a 16-bit reloc.
-
  -- : BFD_RELOC_V850_16_S1
      This is a 16-bit reloc.
-
  -- : BFD_RELOC_V850_LO16_S1
-     Low 16 bits. 16 bit shifted by 1.
-
+     Low 16 bits.  16 bit shifted by 1.
  -- : BFD_RELOC_V850_CALLT_15_16_OFFSET
      This is a 16 bit offset from the call table base pointer.
-
  -- : BFD_RELOC_V850_32_GOTPCREL
      DSO relocations.
-
  -- : BFD_RELOC_V850_16_GOT
      DSO relocations.
-
  -- : BFD_RELOC_V850_32_GOT
      DSO relocations.
-
  -- : BFD_RELOC_V850_22_PLT_PCREL
      DSO relocations.
-
  -- : BFD_RELOC_V850_32_PLT_PCREL
      DSO relocations.
-
  -- : BFD_RELOC_V850_COPY
      DSO relocations.
-
  -- : BFD_RELOC_V850_GLOB_DAT
      DSO relocations.
-
  -- : BFD_RELOC_V850_JMP_SLOT
      DSO relocations.
-
  -- : BFD_RELOC_V850_RELATIVE
      DSO relocations.
-
  -- : BFD_RELOC_V850_16_GOTOFF
      DSO relocations.
-
  -- : BFD_RELOC_V850_32_GOTOFF
      DSO relocations.
-
  -- : BFD_RELOC_V850_CODE
      start code.
-
  -- : BFD_RELOC_V850_DATA
      start data in text.
-
  -- : BFD_RELOC_TIC30_LDP
      This is a 8bit DP reloc for the tms320c30, where the most
      significant 8 bits of a 24 bit word are placed into the least
      significant 8 bits of the opcode.
-
  -- : BFD_RELOC_TIC54X_PARTLS7
      This is a 7bit reloc for the tms320c54x, where the least
      significant 7 bits of a 16 bit word are placed into the least
      significant 7 bits of the opcode.
-
  -- : BFD_RELOC_TIC54X_PARTMS9
      This is a 9bit DP reloc for the tms320c54x, where the most
      significant 9 bits of a 16 bit word are placed into the least
      significant 9 bits of the opcode.
-
  -- : BFD_RELOC_TIC54X_23
      This is an extended address 23-bit reloc for the tms320c54x.
-
  -- : BFD_RELOC_TIC54X_16_OF_23
      This is a 16-bit reloc for the tms320c54x, where the least
      significant 16 bits of a 23-bit extended address are placed into
      the opcode.
-
  -- : BFD_RELOC_TIC54X_MS7_OF_23
      This is a reloc for the tms320c54x, where the most significant 7
      bits of a 23-bit extended address are placed into the opcode.
-
  -- : BFD_RELOC_C6000_PCR_S21
  -- : BFD_RELOC_C6000_PCR_S12
  -- : BFD_RELOC_C6000_PCR_S10
@@ -4829,38 +4619,29 @@ attributes.
  -- : BFD_RELOC_C6000_FPHEAD
  -- : BFD_RELOC_C6000_NOCMP
      TMS320C6000 relocations.
-
  -- : BFD_RELOC_FR30_48
      This is a 48 bit reloc for the FR30 that stores 32 bits.
-
  -- : BFD_RELOC_FR30_20
      This is a 32 bit reloc for the FR30 that stores 20 bits split up
      into two sections.
-
  -- : BFD_RELOC_FR30_6_IN_4
-     This is a 16 bit reloc for the FR30 that stores a 6 bit word
-     offset in 4 bits.
-
+     This is a 16 bit reloc for the FR30 that stores a 6 bit word offset
+     in 4 bits.
  -- : BFD_RELOC_FR30_8_IN_8
      This is a 16 bit reloc for the FR30 that stores an 8 bit byte
      offset into 8 bits.
-
  -- : BFD_RELOC_FR30_9_IN_8
      This is a 16 bit reloc for the FR30 that stores a 9 bit short
      offset into 8 bits.
-
  -- : BFD_RELOC_FR30_10_IN_8
      This is a 16 bit reloc for the FR30 that stores a 10 bit word
      offset into 8 bits.
-
  -- : BFD_RELOC_FR30_9_PCREL
      This is a 16 bit reloc for the FR30 that stores a 9 bit pc relative
      short offset into 8 bits.
-
  -- : BFD_RELOC_FR30_12_PCREL
      This is a 16 bit reloc for the FR30 that stores a 12 bit pc
      relative short offset into 11 bits.
-
  -- : BFD_RELOC_MCORE_PCREL_IMM8BY4
  -- : BFD_RELOC_MCORE_PCREL_IMM11BY2
  -- : BFD_RELOC_MCORE_PCREL_IMM4BY2
@@ -4868,7 +4649,6 @@ attributes.
  -- : BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2
  -- : BFD_RELOC_MCORE_RVA
      Motorola Mcore relocations.
-
  -- : BFD_RELOC_MEP_8
  -- : BFD_RELOC_MEP_16
  -- : BFD_RELOC_MEP_32
@@ -4890,7 +4670,6 @@ attributes.
  -- : BFD_RELOC_MEP_GNU_VTINHERIT
  -- : BFD_RELOC_MEP_GNU_VTENTRY
      Toshiba Media Processor Relocations.
-
  -- : BFD_RELOC_METAG_HIADDR16
  -- : BFD_RELOC_METAG_LOADDR16
  -- : BFD_RELOC_METAG_RELBRANCH
@@ -4930,172 +4709,135 @@ attributes.
  -- : BFD_RELOC_METAG_TLS_LE_HI16
  -- : BFD_RELOC_METAG_TLS_LE_LO16
      Imagination Technologies Meta relocations.
-
  -- : BFD_RELOC_MMIX_GETA
  -- : BFD_RELOC_MMIX_GETA_1
  -- : BFD_RELOC_MMIX_GETA_2
  -- : BFD_RELOC_MMIX_GETA_3
      These are relocations for the GETA instruction.
-
  -- : BFD_RELOC_MMIX_CBRANCH
  -- : BFD_RELOC_MMIX_CBRANCH_J
  -- : BFD_RELOC_MMIX_CBRANCH_1
  -- : BFD_RELOC_MMIX_CBRANCH_2
  -- : BFD_RELOC_MMIX_CBRANCH_3
      These are relocations for a conditional branch instruction.
-
  -- : BFD_RELOC_MMIX_PUSHJ
  -- : BFD_RELOC_MMIX_PUSHJ_1
  -- : BFD_RELOC_MMIX_PUSHJ_2
  -- : BFD_RELOC_MMIX_PUSHJ_3
  -- : BFD_RELOC_MMIX_PUSHJ_STUBBABLE
      These are relocations for the PUSHJ instruction.
-
  -- : BFD_RELOC_MMIX_JMP
  -- : BFD_RELOC_MMIX_JMP_1
  -- : BFD_RELOC_MMIX_JMP_2
  -- : BFD_RELOC_MMIX_JMP_3
      These are relocations for the JMP instruction.
-
  -- : BFD_RELOC_MMIX_ADDR19
      This is a relocation for a relative address as in a GETA
      instruction or a branch.
-
  -- : BFD_RELOC_MMIX_ADDR27
      This is a relocation for a relative address as in a JMP
      instruction.
-
  -- : BFD_RELOC_MMIX_REG_OR_BYTE
      This is a relocation for an instruction field that may be a general
      register or a value 0..255.
-
  -- : BFD_RELOC_MMIX_REG
      This is a relocation for an instruction field that may be a general
      register.
-
  -- : BFD_RELOC_MMIX_BASE_PLUS_OFFSET
      This is a relocation for two instruction fields holding a register
      and an offset, the equivalent of the relocation.
-
  -- : BFD_RELOC_MMIX_LOCAL
      This relocation is an assertion that the expression is not
      allocated as a global register.  It does not modify contents.
-
  -- : BFD_RELOC_AVR_7_PCREL
      This is a 16 bit reloc for the AVR that stores 8 bit pc relative
      short offset into 7 bits.
-
  -- : BFD_RELOC_AVR_13_PCREL
      This is a 16 bit reloc for the AVR that stores 13 bit pc relative
      short offset into 12 bits.
-
  -- : BFD_RELOC_AVR_16_PM
      This is a 16 bit reloc for the AVR that stores 17 bit value
      (usually program memory address) into 16 bits.
-
  -- : BFD_RELOC_AVR_LO8_LDI
      This is a 16 bit reloc for the AVR that stores 8 bit value (usually
      data memory address) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_HI8_LDI
      This is a 16 bit reloc for the AVR that stores 8 bit value (high 8
      bit of data memory address) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_HH8_LDI
      This is a 16 bit reloc for the AVR that stores 8 bit value (most
-     high 8 bit of program memory address) into 8 bit immediate value
-     of LDI insn.
-
+     high 8 bit of program memory address) into 8 bit immediate value of
+     LDI insn.
  -- : BFD_RELOC_AVR_MS8_LDI
      This is a 16 bit reloc for the AVR that stores 8 bit value (most
      high 8 bit of 32 bit value) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_LO8_LDI_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (usually data memory address) into 8 bit immediate value of SUBI
      insn.
-
  -- : BFD_RELOC_AVR_HI8_LDI_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (high 8 bit of data memory address) into 8 bit immediate value of
      SUBI insn.
-
  -- : BFD_RELOC_AVR_HH8_LDI_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (most high 8 bit of program memory address) into 8 bit immediate
      value of LDI or SUBI insn.
-
  -- : BFD_RELOC_AVR_MS8_LDI_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (msb of 32 bit value) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_LO8_LDI_PM
      This is a 16 bit reloc for the AVR that stores 8 bit value (usually
      command address) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_LO8_LDI_GS
-     This is a 16 bit reloc for the AVR that stores 8 bit value
-     (command address) into 8 bit immediate value of LDI insn. If the
-     address is beyond the 128k boundary, the linker inserts a jump
-     stub for this reloc in the lower 128k.
-
+     This is a 16 bit reloc for the AVR that stores 8 bit value (command
+     address) into 8 bit immediate value of LDI insn.  If the address is
+     beyond the 128k boundary, the linker inserts a jump stub for this
+     reloc in the lower 128k.
  -- : BFD_RELOC_AVR_HI8_LDI_PM
      This is a 16 bit reloc for the AVR that stores 8 bit value (high 8
      bit of command address) into 8 bit immediate value of LDI insn.
-
  -- : BFD_RELOC_AVR_HI8_LDI_GS
      This is a 16 bit reloc for the AVR that stores 8 bit value (high 8
-     bit of command address) into 8 bit immediate value of LDI insn.
-     If the address is beyond the 128k boundary, the linker inserts a
-     jump stub for this reloc below 128k.
-
+     bit of command address) into 8 bit immediate value of LDI insn.  If
+     the address is beyond the 128k boundary, the linker inserts a jump
+     stub for this reloc below 128k.
  -- : BFD_RELOC_AVR_HH8_LDI_PM
      This is a 16 bit reloc for the AVR that stores 8 bit value (most
      high 8 bit of command address) into 8 bit immediate value of LDI
      insn.
-
  -- : BFD_RELOC_AVR_LO8_LDI_PM_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (usually command address) into 8 bit immediate value of SUBI insn.
-
  -- : BFD_RELOC_AVR_HI8_LDI_PM_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (high 8 bit of 16 bit command address) into 8 bit immediate value
      of SUBI insn.
-
  -- : BFD_RELOC_AVR_HH8_LDI_PM_NEG
      This is a 16 bit reloc for the AVR that stores negated 8 bit value
      (high 6 bit of 22 bit command address) into 8 bit immediate value
      of SUBI insn.
-
  -- : BFD_RELOC_AVR_CALL
-     This is a 32 bit reloc for the AVR that stores 23 bit value into
-     22 bits.
-
+     This is a 32 bit reloc for the AVR that stores 23 bit value into 22
+     bits.
  -- : BFD_RELOC_AVR_LDI
      This is a 16 bit reloc for the AVR that stores all needed bits for
      absolute addressing with ldi with overflow check to linktime
-
  -- : BFD_RELOC_AVR_6
      This is a 6 bit reloc for the AVR that stores offset for ldd/std
      instructions
-
  -- : BFD_RELOC_AVR_6_ADIW
      This is a 6 bit reloc for the AVR that stores offset for adiw/sbiw
      instructions
-
  -- : BFD_RELOC_AVR_8_LO
      This is a 8 bit reloc for the AVR that stores bits 0..7 of a symbol
      in .byte lo8(symbol)
-
  -- : BFD_RELOC_AVR_8_HI
      This is a 8 bit reloc for the AVR that stores bits 8..15 of a
      symbol in .byte hi8(symbol)
-
  -- : BFD_RELOC_AVR_8_HLO
      This is a 8 bit reloc for the AVR that stores bits 16..23 of a
      symbol in .byte hlo8(symbol)
-
  -- : BFD_RELOC_RL78_NEG8
  -- : BFD_RELOC_RL78_NEG16
  -- : BFD_RELOC_RL78_NEG24
@@ -5130,7 +4872,6 @@ attributes.
  -- : BFD_RELOC_RL78_LO16
  -- : BFD_RELOC_RL78_CODE
      Renesas RL78 Relocations.
-
  -- : BFD_RELOC_RX_NEG8
  -- : BFD_RELOC_RX_NEG16
  -- : BFD_RELOC_RX_NEG24
@@ -5159,85 +4900,66 @@ attributes.
  -- : BFD_RELOC_RX_ABS16UL
  -- : BFD_RELOC_RX_RELAX
      Renesas RX Relocations.
-
  -- : BFD_RELOC_390_12
      Direct 12 bit.
-
  -- : BFD_RELOC_390_GOT12
      12 bit GOT offset.
-
  -- : BFD_RELOC_390_PLT32
      32 bit PC relative PLT address.
-
  -- : BFD_RELOC_390_COPY
      Copy symbol at runtime.
-
  -- : BFD_RELOC_390_GLOB_DAT
      Create GOT entry.
-
  -- : BFD_RELOC_390_JMP_SLOT
      Create PLT entry.
-
  -- : BFD_RELOC_390_RELATIVE
      Adjust by program base.
-
  -- : BFD_RELOC_390_GOTPC
      32 bit PC relative offset to GOT.
-
  -- : BFD_RELOC_390_GOT16
      16 bit GOT offset.
-
+ -- : BFD_RELOC_390_PC12DBL
+     PC relative 12 bit shifted by 1.
+ -- : BFD_RELOC_390_PLT12DBL
+     12 bit PC rel.  PLT shifted by 1.
  -- : BFD_RELOC_390_PC16DBL
      PC relative 16 bit shifted by 1.
-
  -- : BFD_RELOC_390_PLT16DBL
-     16 bit PC rel. PLT shifted by 1.
-
+     16 bit PC rel.  PLT shifted by 1.
+ -- : BFD_RELOC_390_PC24DBL
+     PC relative 24 bit shifted by 1.
+ -- : BFD_RELOC_390_PLT24DBL
+     24 bit PC rel.  PLT shifted by 1.
  -- : BFD_RELOC_390_PC32DBL
      PC relative 32 bit shifted by 1.
-
  -- : BFD_RELOC_390_PLT32DBL
-     32 bit PC rel. PLT shifted by 1.
-
+     32 bit PC rel.  PLT shifted by 1.
  -- : BFD_RELOC_390_GOTPCDBL
-     32 bit PC rel. GOT shifted by 1.
-
+     32 bit PC rel.  GOT shifted by 1.
  -- : BFD_RELOC_390_GOT64
      64 bit GOT offset.
-
  -- : BFD_RELOC_390_PLT64
      64 bit PC relative PLT address.
-
  -- : BFD_RELOC_390_GOTENT
-     32 bit rel. offset to GOT entry.
-
+     32 bit rel.  offset to GOT entry.
  -- : BFD_RELOC_390_GOTOFF64
      64 bit offset to GOT.
-
  -- : BFD_RELOC_390_GOTPLT12
      12-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_390_GOTPLT16
      16-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_390_GOTPLT32
      32-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_390_GOTPLT64
      64-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_390_GOTPLTENT
-     32-bit rel. offset to symbol-entry within GOT, with PLT handling.
-
+     32-bit rel.  offset to symbol-entry within GOT, with PLT handling.
  -- : BFD_RELOC_390_PLTOFF16
-     16-bit rel. offset from the GOT to a PLT entry.
-
+     16-bit rel.  offset from the GOT to a PLT entry.
  -- : BFD_RELOC_390_PLTOFF32
-     32-bit rel. offset from the GOT to a PLT entry.
-
+     32-bit rel.  offset from the GOT to a PLT entry.
  -- : BFD_RELOC_390_PLTOFF64
-     64-bit rel. offset from the GOT to a PLT entry.
-
+     64-bit rel.  offset from the GOT to a PLT entry.
  -- : BFD_RELOC_390_TLS_LOAD
  -- : BFD_RELOC_390_TLS_GDCALL
  -- : BFD_RELOC_390_TLS_LDCALL
@@ -5259,88 +4981,66 @@ attributes.
  -- : BFD_RELOC_390_TLS_DTPOFF
  -- : BFD_RELOC_390_TLS_TPOFF
      s390 tls relocations.
-
  -- : BFD_RELOC_390_20
  -- : BFD_RELOC_390_GOT20
  -- : BFD_RELOC_390_GOTPLT20
  -- : BFD_RELOC_390_TLS_GOTIE20
      Long displacement extension.
-
  -- : BFD_RELOC_390_IRELATIVE
      STT_GNU_IFUNC relocation.
-
  -- : BFD_RELOC_SCORE_GPREL15
      Score relocations Low 16 bit for load/store
-
  -- : BFD_RELOC_SCORE_DUMMY2
  -- : BFD_RELOC_SCORE_JMP
      This is a 24-bit reloc with the right 1 bit assumed to be 0
-
  -- : BFD_RELOC_SCORE_BRANCH
      This is a 19-bit reloc with the right 1 bit assumed to be 0
-
  -- : BFD_RELOC_SCORE_IMM30
      This is a 32-bit reloc for 48-bit instructions.
-
  -- : BFD_RELOC_SCORE_IMM32
      This is a 32-bit reloc for 48-bit instructions.
-
  -- : BFD_RELOC_SCORE16_JMP
      This is a 11-bit reloc with the right 1 bit assumed to be 0
-
  -- : BFD_RELOC_SCORE16_BRANCH
      This is a 8-bit reloc with the right 1 bit assumed to be 0
-
  -- : BFD_RELOC_SCORE_BCMP
      This is a 9-bit reloc with the right 1 bit assumed to be 0
-
  -- : BFD_RELOC_SCORE_GOT15
  -- : BFD_RELOC_SCORE_GOT_LO16
  -- : BFD_RELOC_SCORE_CALL15
  -- : BFD_RELOC_SCORE_DUMMY_HI16
      Undocumented Score relocs
-
  -- : BFD_RELOC_IP2K_FR9
      Scenix IP2K - 9-bit register number / data address
-
  -- : BFD_RELOC_IP2K_BANK
      Scenix IP2K - 4-bit register/data bank number
-
  -- : BFD_RELOC_IP2K_ADDR16CJP
      Scenix IP2K - low 13 bits of instruction word address
-
  -- : BFD_RELOC_IP2K_PAGE3
      Scenix IP2K - high 3 bits of instruction word address
-
  -- : BFD_RELOC_IP2K_LO8DATA
  -- : BFD_RELOC_IP2K_HI8DATA
  -- : BFD_RELOC_IP2K_EX8DATA
      Scenix IP2K - ext/low/high 8 bits of data address
-
  -- : BFD_RELOC_IP2K_LO8INSN
  -- : BFD_RELOC_IP2K_HI8INSN
      Scenix IP2K - low/high 8 bits of instruction word address
-
  -- : BFD_RELOC_IP2K_PC_SKIP
      Scenix IP2K - even/odd PC modifier to modify snb pcl.0
-
  -- : BFD_RELOC_IP2K_TEXT
      Scenix IP2K - 16 bit word address in text section.
-
  -- : BFD_RELOC_IP2K_FR_OFFSET
      Scenix IP2K - 7-bit sp or dp offset
-
  -- : BFD_RELOC_VPE4KMATH_DATA
  -- : BFD_RELOC_VPE4KMATH_INSN
      Scenix VPE4K coprocessor - data/insn-space addressing
-
  -- : BFD_RELOC_VTABLE_INHERIT
  -- : BFD_RELOC_VTABLE_ENTRY
      These two relocations are used by the linker to determine which of
      the entries in a C++ virtual function table are actually used.
-     When the -gc-sections option is given, the linker will zero out
-     the entries that are not used, so that the code for those
-     functions need not be included in the output.
+     When the -gc-sections option is given, the linker will zero out the
+     entries that are not used, so that the code for those functions
+     need not be included in the output.
 
      VTABLE_INHERIT is a zero-space relocation used to describe to the
      linker the inheritance tree of a C++ virtual function table.  The
@@ -5349,11 +5049,10 @@ attributes.
 
      VTABLE_ENTRY is a zero-space relocation that describes the use of a
      virtual function table entry.  The reloc's symbol should refer to
-     the table of the class mentioned in the code.  Off of that base,
-     an offset describes the entry that is being used.  For Rela hosts,
-     this offset is stored in the reloc's addend.  For Rel hosts, we
-     are forced to put this offset in the reloc's section offset.
-
+     the table of the class mentioned in the code.  Off of that base, an
+     offset describes the entry that is being used.  For Rela hosts,
+     this offset is stored in the reloc's addend.  For Rel hosts, we are
+     forced to put this offset in the reloc's section offset.
  -- : BFD_RELOC_IA64_IMM14
  -- : BFD_RELOC_IA64_IMM22
  -- : BFD_RELOC_IA64_IMM64
@@ -5434,111 +5133,83 @@ attributes.
  -- : BFD_RELOC_IA64_DTPREL64LSB
  -- : BFD_RELOC_IA64_LTOFF_DTPREL22
      Intel IA64 Relocations.
-
  -- : BFD_RELOC_M68HC11_HI8
      Motorola 68HC11 reloc.  This is the 8 bit high part of an absolute
      address.
-
  -- : BFD_RELOC_M68HC11_LO8
      Motorola 68HC11 reloc.  This is the 8 bit low part of an absolute
      address.
-
  -- : BFD_RELOC_M68HC11_3B
      Motorola 68HC11 reloc.  This is the 3 bit of a value.
-
  -- : BFD_RELOC_M68HC11_RL_JUMP
      Motorola 68HC11 reloc.  This reloc marks the beginning of a
      jump/call instruction.  It is used for linker relaxation to
      correctly identify beginning of instruction and change some
      branches to use PC-relative addressing mode.
-
  -- : BFD_RELOC_M68HC11_RL_GROUP
      Motorola 68HC11 reloc.  This reloc marks a group of several
-     instructions that gcc generates and for which the linker
-     relaxation pass can modify and/or remove some of them.
-
+     instructions that gcc generates and for which the linker relaxation
+     pass can modify and/or remove some of them.
  -- : BFD_RELOC_M68HC11_LO16
      Motorola 68HC11 reloc.  This is the 16-bit lower part of an
      address.  It is used for 'call' instruction to specify the symbol
      address without any special transformation (due to memory bank
      window).
-
  -- : BFD_RELOC_M68HC11_PAGE
      Motorola 68HC11 reloc.  This is a 8-bit reloc that specifies the
      page number of an address.  It is used by 'call' instruction to
      specify the page number of the symbol.
-
  -- : BFD_RELOC_M68HC11_24
      Motorola 68HC11 reloc.  This is a 24-bit reloc that represents the
      address with a 16-bit value and a 8-bit page number.  The symbol
      address is transformed to follow the 16K memory bank of 68HC12
      (seen as mapped in the window).
-
  -- : BFD_RELOC_M68HC12_5B
      Motorola 68HC12 reloc.  This is the 5 bits of a value.
-
  -- : BFD_RELOC_XGATE_RL_JUMP
-     Freescale XGATE reloc.  This reloc marks the beginning of a
-     bra/jal instruction.
-
+     Freescale XGATE reloc.  This reloc marks the beginning of a bra/jal
+     instruction.
  -- : BFD_RELOC_XGATE_RL_GROUP
      Freescale XGATE reloc.  This reloc marks a group of several
-     instructions that gcc generates and for which the linker
-     relaxation pass can modify and/or remove some of them.
-
+     instructions that gcc generates and for which the linker relaxation
+     pass can modify and/or remove some of them.
  -- : BFD_RELOC_XGATE_LO16
      Freescale XGATE reloc.  This is the 16-bit lower part of an
      address.  It is used for the '16-bit' instructions.
-
  -- : BFD_RELOC_XGATE_GPAGE
      Freescale XGATE reloc.
-
  -- : BFD_RELOC_XGATE_24
      Freescale XGATE reloc.
-
  -- : BFD_RELOC_XGATE_PCREL_9
      Freescale XGATE reloc.  This is a 9-bit pc-relative reloc.
-
  -- : BFD_RELOC_XGATE_PCREL_10
      Freescale XGATE reloc.  This is a 10-bit pc-relative reloc.
-
  -- : BFD_RELOC_XGATE_IMM8_LO
      Freescale XGATE reloc.  This is the 16-bit lower part of an
      address.  It is used for the '16-bit' instructions.
-
  -- : BFD_RELOC_XGATE_IMM8_HI
      Freescale XGATE reloc.  This is the 16-bit higher part of an
      address.  It is used for the '16-bit' instructions.
-
  -- : BFD_RELOC_XGATE_IMM3
      Freescale XGATE reloc.  This is a 3-bit pc-relative reloc.
-
  -- : BFD_RELOC_XGATE_IMM4
      Freescale XGATE reloc.  This is a 4-bit pc-relative reloc.
-
  -- : BFD_RELOC_XGATE_IMM5
      Freescale XGATE reloc.  This is a 5-bit pc-relative reloc.
-
  -- : BFD_RELOC_M68HC12_9B
      Motorola 68HC12 reloc.  This is the 9 bits of a value.
-
  -- : BFD_RELOC_M68HC12_16B
      Motorola 68HC12 reloc.  This is the 16 bits of a value.
-
  -- : BFD_RELOC_M68HC12_9_PCREL
      Motorola 68HC12/XGATE reloc.  This is a PCREL9 branch.
-
  -- : BFD_RELOC_M68HC12_10_PCREL
      Motorola 68HC12/XGATE reloc.  This is a PCREL10 branch.
-
  -- : BFD_RELOC_M68HC12_LO8XG
      Motorola 68HC12/XGATE reloc.  This is the 8 bit low part of an
      absolute address and immediately precedes a matching HI8XG part.
-
  -- : BFD_RELOC_M68HC12_HI8XG
      Motorola 68HC12/XGATE reloc.  This is the 8 bit high part of an
      absolute address and immediately follows a matching LO8XG part.
-
  -- : BFD_RELOC_16C_NUM08
  -- : BFD_RELOC_16C_NUM08_C
  -- : BFD_RELOC_16C_NUM16
@@ -5580,7 +5251,6 @@ attributes.
  -- : BFD_RELOC_16C_IMM32
  -- : BFD_RELOC_16C_IMM32_C
      NS CR16C Relocations.
-
  -- : BFD_RELOC_CR16_NUM8
  -- : BFD_RELOC_CR16_NUM16
  -- : BFD_RELOC_CR16_NUM32
@@ -5615,7 +5285,6 @@ attributes.
  -- : BFD_RELOC_CR16_GOTC_REGREL20
  -- : BFD_RELOC_CR16_GLOB_DAT
      NS CR16 Relocations.
-
  -- : BFD_RELOC_CRX_REL4
  -- : BFD_RELOC_CRX_REL8
  -- : BFD_RELOC_CRX_REL8_CMP
@@ -5637,7 +5306,6 @@ attributes.
  -- : BFD_RELOC_CRX_SWITCH16
  -- : BFD_RELOC_CRX_SWITCH32
      NS CRX Relocations.
-
  -- : BFD_RELOC_CRIS_BDISP8
  -- : BFD_RELOC_CRIS_UNSIGNED_5
  -- : BFD_RELOC_CRIS_SIGNED_6
@@ -5650,35 +5318,26 @@ attributes.
  -- : BFD_RELOC_CRIS_UNSIGNED_4
      These relocs are only used within the CRIS assembler.  They are not
      (at present) written to any object files.
-
  -- : BFD_RELOC_CRIS_COPY
  -- : BFD_RELOC_CRIS_GLOB_DAT
  -- : BFD_RELOC_CRIS_JUMP_SLOT
  -- : BFD_RELOC_CRIS_RELATIVE
      Relocs used in ELF shared libraries for CRIS.
-
  -- : BFD_RELOC_CRIS_32_GOT
      32-bit offset to symbol-entry within GOT.
-
  -- : BFD_RELOC_CRIS_16_GOT
      16-bit offset to symbol-entry within GOT.
-
  -- : BFD_RELOC_CRIS_32_GOTPLT
      32-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_CRIS_16_GOTPLT
      16-bit offset to symbol-entry within GOT, with PLT handling.
-
  -- : BFD_RELOC_CRIS_32_GOTREL
      32-bit offset to symbol, relative to GOT.
-
  -- : BFD_RELOC_CRIS_32_PLT_GOTREL
      32-bit offset to symbol with PLT entry, relative to GOT.
-
  -- : BFD_RELOC_CRIS_32_PLT_PCREL
      32-bit offset to symbol with PLT entry, relative to this
      relocation.
-
  -- : BFD_RELOC_CRIS_32_GOT_GD
  -- : BFD_RELOC_CRIS_16_GOT_GD
  -- : BFD_RELOC_CRIS_32_GD
@@ -5692,7 +5351,6 @@ attributes.
  -- : BFD_RELOC_CRIS_DTPMOD
  -- : BFD_RELOC_CRIS_32_IE
      Relocs used in TLS code for CRIS.
-
  -- : BFD_RELOC_860_COPY
  -- : BFD_RELOC_860_GLOB_DAT
  -- : BFD_RELOC_860_JUMP_SLOT
@@ -5726,11 +5384,9 @@ attributes.
  -- : BFD_RELOC_860_HIGOT
  -- : BFD_RELOC_860_HIGOTOFF
      Intel i860 Relocations.
-
  -- : BFD_RELOC_OPENRISC_ABS_26
  -- : BFD_RELOC_OPENRISC_REL_26
      OpenRISC Relocations.
-
  -- : BFD_RELOC_H8_DIR16A8
  -- : BFD_RELOC_H8_DIR16R8
  -- : BFD_RELOC_H8_DIR24A8
@@ -5738,45 +5394,34 @@ attributes.
  -- : BFD_RELOC_H8_DIR32A16
  -- : BFD_RELOC_H8_DISP32A16
      H8 elf Relocations.
-
  -- : BFD_RELOC_XSTORMY16_REL_12
  -- : BFD_RELOC_XSTORMY16_12
  -- : BFD_RELOC_XSTORMY16_24
  -- : BFD_RELOC_XSTORMY16_FPTR16
      Sony Xstormy16 Relocations.
-
  -- : BFD_RELOC_RELC
      Self-describing complex relocations.
-
  -- : BFD_RELOC_XC16X_PAG
  -- : BFD_RELOC_XC16X_POF
  -- : BFD_RELOC_XC16X_SEG
  -- : BFD_RELOC_XC16X_SOF
      Infineon Relocations.
-
  -- : BFD_RELOC_VAX_GLOB_DAT
  -- : BFD_RELOC_VAX_JMP_SLOT
  -- : BFD_RELOC_VAX_RELATIVE
      Relocations used by VAX ELF.
-
  -- : BFD_RELOC_MT_PC16
      Morpho MT - 16 bit immediate relocation.
-
  -- : BFD_RELOC_MT_HI16
      Morpho MT - Hi 16 bits of an address.
-
  -- : BFD_RELOC_MT_LO16
      Morpho MT - Low 16 bits of an address.
-
  -- : BFD_RELOC_MT_GNU_VTINHERIT
      Morpho MT - Used to tell the linker which vtable entries are used.
-
  -- : BFD_RELOC_MT_GNU_VTENTRY
      Morpho MT - Used to tell the linker which vtable entries are used.
-
  -- : BFD_RELOC_MT_PCINSN8
      Morpho MT - 8 bit immediate relocation.
-
  -- : BFD_RELOC_MSP430_10_PCREL
  -- : BFD_RELOC_MSP430_16_PCREL
  -- : BFD_RELOC_MSP430_16
@@ -5784,8 +5429,22 @@ attributes.
  -- : BFD_RELOC_MSP430_16_BYTE
  -- : BFD_RELOC_MSP430_2X_PCREL
  -- : BFD_RELOC_MSP430_RL_PCREL
+ -- : BFD_RELOC_MSP430_ABS8
+ -- : BFD_RELOC_MSP430X_PCR20_EXT_SRC
+ -- : BFD_RELOC_MSP430X_PCR20_EXT_DST
+ -- : BFD_RELOC_MSP430X_PCR20_EXT_ODST
+ -- : BFD_RELOC_MSP430X_ABS20_EXT_SRC
+ -- : BFD_RELOC_MSP430X_ABS20_EXT_DST
+ -- : BFD_RELOC_MSP430X_ABS20_EXT_ODST
+ -- : BFD_RELOC_MSP430X_ABS20_ADR_SRC
+ -- : BFD_RELOC_MSP430X_ABS20_ADR_DST
+ -- : BFD_RELOC_MSP430X_PCR16
+ -- : BFD_RELOC_MSP430X_PCR20_CALL
+ -- : BFD_RELOC_MSP430X_ABS16
+ -- : BFD_RELOC_MSP430_ABS_HI16
+ -- : BFD_RELOC_MSP430_PREL31
+ -- : BFD_RELOC_MSP430_SYM_DIFF
      msp430 specific relocation codes
-
  -- : BFD_RELOC_NIOS2_S16
  -- : BFD_RELOC_NIOS2_U16
  -- : BFD_RELOC_NIOS2_CALL26
@@ -5821,27 +5480,22 @@ attributes.
  -- : BFD_RELOC_NIOS2_RELATIVE
  -- : BFD_RELOC_NIOS2_GOTOFF
      Relocations used by the Altera Nios II core.
-
  -- : BFD_RELOC_IQ2000_OFFSET_16
  -- : BFD_RELOC_IQ2000_OFFSET_21
  -- : BFD_RELOC_IQ2000_UHI16
      IQ2000 Relocations.
-
  -- : BFD_RELOC_XTENSA_RTLD
      Special Xtensa relocation used only by PLT entries in ELF shared
-     objects to indicate that the runtime linker should set the value
-     to one of its own internal functions or data structures.
-
+     objects to indicate that the runtime linker should set the value to
+     one of its own internal functions or data structures.
  -- : BFD_RELOC_XTENSA_GLOB_DAT
  -- : BFD_RELOC_XTENSA_JMP_SLOT
  -- : BFD_RELOC_XTENSA_RELATIVE
      Xtensa relocations for ELF shared objects.
-
  -- : BFD_RELOC_XTENSA_PLT
      Xtensa relocation used in ELF object files for symbols that may
      require PLT entries.  Otherwise, this is just a generic 32-bit
      relocation.
-
  -- : BFD_RELOC_XTENSA_DIFF8
  -- : BFD_RELOC_XTENSA_DIFF16
  -- : BFD_RELOC_XTENSA_DIFF32
@@ -5849,9 +5503,8 @@ attributes.
      These are only needed to support linker relaxation and can be
      ignored when not relaxing.  The field is set to the value of the
      difference assuming no relaxation.  The relocation encodes the
-     position of the first symbol so the linker can determine whether
-     to adjust the field value.
-
+     position of the first symbol so the linker can determine whether to
+     adjust the field value.
  -- : BFD_RELOC_XTENSA_SLOT0_OP
  -- : BFD_RELOC_XTENSA_SLOT1_OP
  -- : BFD_RELOC_XTENSA_SLOT2_OP
@@ -5871,7 +5524,6 @@ attributes.
      number is encoded in the relocation.  The relocation applies to the
      last PC-relative immediate operand, or if there are no PC-relative
      immediates, to the last immediate operand.
-
  -- : BFD_RELOC_XTENSA_SLOT0_ALT
  -- : BFD_RELOC_XTENSA_SLOT1_ALT
  -- : BFD_RELOC_XTENSA_SLOT2_ALT
@@ -5889,23 +5541,19 @@ attributes.
  -- : BFD_RELOC_XTENSA_SLOT14_ALT
      Alternate Xtensa relocations.  Only the slot is encoded in the
      relocation.  The meaning of these relocations is opcode-specific.
-
  -- : BFD_RELOC_XTENSA_OP0
  -- : BFD_RELOC_XTENSA_OP1
  -- : BFD_RELOC_XTENSA_OP2
      Xtensa relocations for backward compatibility.  These have all been
      replaced by BFD_RELOC_XTENSA_SLOT0_OP.
-
  -- : BFD_RELOC_XTENSA_ASM_EXPAND
      Xtensa relocation to mark that the assembler expanded the
      instructions from an original target.  The expansion size is
      encoded in the reloc size.
-
  -- : BFD_RELOC_XTENSA_ASM_SIMPLIFY
      Xtensa relocation to mark that the linker should simplify
      assembler-expanded instructions.  This is commonly used internally
      by the linker after analysis of a BFD_RELOC_XTENSA_ASM_EXPAND.
-
  -- : BFD_RELOC_XTENSA_TLSDESC_FN
  -- : BFD_RELOC_XTENSA_TLSDESC_ARG
  -- : BFD_RELOC_XTENSA_TLS_DTPOFF
@@ -5914,19 +5562,14 @@ attributes.
  -- : BFD_RELOC_XTENSA_TLS_ARG
  -- : BFD_RELOC_XTENSA_TLS_CALL
      Xtensa TLS relocations.
-
  -- : BFD_RELOC_Z80_DISP8
      8 bit signed offset in (ix+d) or (iy+d).
-
  -- : BFD_RELOC_Z8K_DISP7
      DJNZ offset.
-
  -- : BFD_RELOC_Z8K_CALLR
      CALR offset.
-
  -- : BFD_RELOC_Z8K_IMM4L
      4 bit value.
-
  -- : BFD_RELOC_LM32_CALL
  -- : BFD_RELOC_LM32_BRANCH
  -- : BFD_RELOC_LM32_16_GOT
@@ -5937,356 +5580,317 @@ attributes.
  -- : BFD_RELOC_LM32_JMP_SLOT
  -- : BFD_RELOC_LM32_RELATIVE
      Lattice Mico32 relocations.
-
  -- : BFD_RELOC_MACH_O_SECTDIFF
      Difference between two section addreses.  Must be followed by a
      BFD_RELOC_MACH_O_PAIR.
-
  -- : BFD_RELOC_MACH_O_LOCAL_SECTDIFF
      Like BFD_RELOC_MACH_O_SECTDIFF but with a local symbol.
-
  -- : BFD_RELOC_MACH_O_PAIR
      Pair of relocation.  Contains the first symbol.
-
  -- : BFD_RELOC_MACH_O_X86_64_BRANCH32
  -- : BFD_RELOC_MACH_O_X86_64_BRANCH8
      PCREL relocations.  They are marked as branch to create PLT entry
      if required.
-
  -- : BFD_RELOC_MACH_O_X86_64_GOT
      Used when referencing a GOT entry.
-
  -- : BFD_RELOC_MACH_O_X86_64_GOT_LOAD
-     Used when loading a GOT entry with movq.  It is specially marked
-     so that the linker could optimize the movq to a leaq if possible.
-
+     Used when loading a GOT entry with movq.  It is specially marked so
+     that the linker could optimize the movq to a leaq if possible.
  -- : BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32
      Symbol will be substracted.  Must be followed by a BFD_RELOC_64.
-
  -- : BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64
      Symbol will be substracted.  Must be followed by a BFD_RELOC_64.
-
  -- : BFD_RELOC_MACH_O_X86_64_PCREL32_1
      Same as BFD_RELOC_32_PCREL but with an implicit -1 addend.
-
  -- : BFD_RELOC_MACH_O_X86_64_PCREL32_2
      Same as BFD_RELOC_32_PCREL but with an implicit -2 addend.
-
  -- : BFD_RELOC_MACH_O_X86_64_PCREL32_4
      Same as BFD_RELOC_32_PCREL but with an implicit -4 addend.
-
  -- : BFD_RELOC_MICROBLAZE_32_LO
      This is a 32 bit reloc for the microblaze that stores the low 16
      bits of a value
-
  -- : BFD_RELOC_MICROBLAZE_32_LO_PCREL
      This is a 32 bit pc-relative reloc for the microblaze that stores
      the low 16 bits of a value
-
  -- : BFD_RELOC_MICROBLAZE_32_ROSDA
      This is a 32 bit reloc for the microblaze that stores a value
      relative to the read-only small data area anchor
-
  -- : BFD_RELOC_MICROBLAZE_32_RWSDA
      This is a 32 bit reloc for the microblaze that stores a value
      relative to the read-write small data area anchor
-
  -- : BFD_RELOC_MICROBLAZE_32_SYM_OP_SYM
      This is a 32 bit reloc for the microblaze to handle expressions of
      the form "Symbol Op Symbol"
-
  -- : BFD_RELOC_MICROBLAZE_64_NONE
      This is a 64 bit reloc that stores the 32 bit pc relative value in
      two words (with an imm instruction).  No relocation is done here -
      only used for relaxing
-
  -- : BFD_RELOC_MICROBLAZE_64_GOTPC
      This is a 64 bit reloc that stores the 32 bit pc relative value in
-     two words (with an imm instruction).  The relocation is
-     PC-relative GOT offset
-
+     two words (with an imm instruction).  The relocation is PC-relative
+     GOT offset
  -- : BFD_RELOC_MICROBLAZE_64_GOT
      This is a 64 bit reloc that stores the 32 bit pc relative value in
      two words (with an imm instruction).  The relocation is GOT offset
-
  -- : BFD_RELOC_MICROBLAZE_64_PLT
      This is a 64 bit reloc that stores the 32 bit pc relative value in
-     two words (with an imm instruction).  The relocation is
-     PC-relative offset into PLT
-
+     two words (with an imm instruction).  The relocation is PC-relative
+     offset into PLT
  -- : BFD_RELOC_MICROBLAZE_64_GOTOFF
-     This is a 64 bit reloc that stores the 32 bit GOT relative value
-     in two words (with an imm instruction).  The relocation is
-     relative offset from _GLOBAL_OFFSET_TABLE_
-
+     This is a 64 bit reloc that stores the 32 bit GOT relative value in
+     two words (with an imm instruction).  The relocation is relative
+     offset from _GLOBAL_OFFSET_TABLE_
  -- : BFD_RELOC_MICROBLAZE_32_GOTOFF
-     This is a 32 bit reloc that stores the 32 bit GOT relative value
-     in a word.  The relocation is relative offset from
-
+     This is a 32 bit reloc that stores the 32 bit GOT relative value in
+     a word.  The relocation is relative offset from
  -- : BFD_RELOC_MICROBLAZE_COPY
      This is used to tell the dynamic linker to copy the value out of
      the dynamic object into the runtime process image.
-
  -- : BFD_RELOC_MICROBLAZE_64_TLS
      Unused Reloc
-
  -- : BFD_RELOC_MICROBLAZE_64_TLSGD
-     This is a 64 bit reloc that stores the 32 bit GOT relative value
-     of the GOT TLS GD info entry in two words (with an imm
-     instruction). The relocation is GOT offset.
-
+     This is a 64 bit reloc that stores the 32 bit GOT relative value of
+     the GOT TLS GD info entry in two words (with an imm instruction).
+     The relocation is GOT offset.
  -- : BFD_RELOC_MICROBLAZE_64_TLSLD
-     This is a 64 bit reloc that stores the 32 bit GOT relative value
-     of the GOT TLS LD info entry in two words (with an imm
-     instruction). The relocation is GOT offset.
-
+     This is a 64 bit reloc that stores the 32 bit GOT relative value of
+     the GOT TLS LD info entry in two words (with an imm instruction).
+     The relocation is GOT offset.
  -- : BFD_RELOC_MICROBLAZE_32_TLSDTPMOD
      This is a 32 bit reloc that stores the Module ID to GOT(n).
-
  -- : BFD_RELOC_MICROBLAZE_32_TLSDTPREL
      This is a 32 bit reloc that stores TLS offset to GOT(n+1).
-
  -- : BFD_RELOC_MICROBLAZE_64_TLSDTPREL
      This is a 32 bit reloc for storing TLS offset to two words (uses
      imm instruction)
-
  -- : BFD_RELOC_MICROBLAZE_64_TLSGOTTPREL
      This is a 64 bit reloc that stores 32-bit thread pointer relative
      offset to two words (uses imm instruction).
-
  -- : BFD_RELOC_MICROBLAZE_64_TLSTPREL
      This is a 64 bit reloc that stores 32-bit thread pointer relative
      offset to two words (uses imm instruction).
-
- -- : BFD_RELOC_AARCH64_ADD_LO12
-     AArch64 ADD immediate instruction, holding bits 0 to 11 of the
-     address.  Used in conjunction with
-     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
- -- : BFD_RELOC_AARCH64_GOT_LD_PREL19
-     AArch64 Load Literal instruction, holding a 19 bit PC relative word
-     offset of the global offset table entry for a symbol.  The lowest
-     two bits must be zero and are not stored in the instruction,
-     giving a 21 bit signed byte offset.  This relocation type requires
-     signed overflow checking.
-
- -- : BFD_RELOC_AARCH64_ADR_GOT_PAGE
-     Get to the page base of the global offset table entry for a symbol
-     as part of an ADRP instruction using a 21 bit PC relative
-     value.Used in conjunction with BFD_RELOC_AARCH64_LD64_GOT_LO12_NC.
-
+ -- : BFD_RELOC_AARCH64_RELOC_START
+     AArch64 pseudo relocation code to mark the start of the AArch64
+     relocation enumerators.  N.B. the order of the enumerators is
+     important as several tables in the AArch64 bfd backend are indexed
+     by these enumerators; make sure they are all synced.
+ -- : BFD_RELOC_AARCH64_NONE
+     AArch64 null relocation code.
+ -- : BFD_RELOC_AARCH64_64
+ -- : BFD_RELOC_AARCH64_32
+ -- : BFD_RELOC_AARCH64_16
+     Basic absolute relocations of N bits.  These are equivalent to
+     BFD_RELOC_N and they were added to assist the indexing of the howto
+     table.
+ -- : BFD_RELOC_AARCH64_64_PCREL
+ -- : BFD_RELOC_AARCH64_32_PCREL
+ -- : BFD_RELOC_AARCH64_16_PCREL
+     PC-relative relocations.  These are equivalent to BFD_RELOC_N_PCREL
+     and they were added to assist the indexing of the howto table.
+ -- : BFD_RELOC_AARCH64_MOVW_G0
+     AArch64 MOV[NZK] instruction with most significant bits 0 to 15 of
+     an unsigned address/value.
+ -- : BFD_RELOC_AARCH64_MOVW_G0_NC
+     AArch64 MOV[NZK] instruction with less significant bits 0 to 15 of
+     an address/value.  No overflow checking.
+ -- : BFD_RELOC_AARCH64_MOVW_G1
+     AArch64 MOV[NZK] instruction with most significant bits 16 to 31 of
+     an unsigned address/value.
+ -- : BFD_RELOC_AARCH64_MOVW_G1_NC
+     AArch64 MOV[NZK] instruction with less significant bits 16 to 31 of
+     an address/value.  No overflow checking.
+ -- : BFD_RELOC_AARCH64_MOVW_G2
+     AArch64 MOV[NZK] instruction with most significant bits 32 to 47 of
+     an unsigned address/value.
+ -- : BFD_RELOC_AARCH64_MOVW_G2_NC
+     AArch64 MOV[NZK] instruction with less significant bits 32 to 47 of
+     an address/value.  No overflow checking.
+ -- : BFD_RELOC_AARCH64_MOVW_G3
+     AArch64 MOV[NZK] instruction with most signficant bits 48 to 64 of
+     a signed or unsigned address/value.
+ -- : BFD_RELOC_AARCH64_MOVW_G0_S
+     AArch64 MOV[NZ] instruction with most significant bits 0 to 15 of a
+     signed value.  Changes instruction to MOVZ or MOVN depending on the
+     value's sign.
+ -- : BFD_RELOC_AARCH64_MOVW_G1_S
+     AArch64 MOV[NZ] instruction with most significant bits 16 to 31 of
+     a signed value.  Changes instruction to MOVZ or MOVN depending on
+     the value's sign.
+ -- : BFD_RELOC_AARCH64_MOVW_G2_S
+     AArch64 MOV[NZ] instruction with most significant bits 32 to 47 of
+     a signed value.  Changes instruction to MOVZ or MOVN depending on
+     the value's sign.
+ -- : BFD_RELOC_AARCH64_LD_LO19_PCREL
+     AArch64 Load Literal instruction, holding a 19 bit pc-relative word
+     offset.  The lowest two bits must be zero and are not stored in the
+     instruction, giving a 21 bit signed byte offset.
+ -- : BFD_RELOC_AARCH64_ADR_LO21_PCREL
+     AArch64 ADR instruction, holding a simple 21 bit pc-relative byte
+     offset.
  -- : BFD_RELOC_AARCH64_ADR_HI21_PCREL
      AArch64 ADRP instruction, with bits 12 to 32 of a pc-relative page
      offset, giving a 4KB aligned page base address.
-
  -- : BFD_RELOC_AARCH64_ADR_HI21_NC_PCREL
      AArch64 ADRP instruction, with bits 12 to 32 of a pc-relative page
      offset, giving a 4KB aligned page base address, but with no
      overflow checking.
-
- -- : BFD_RELOC_AARCH64_ADR_LO21_PCREL
-     AArch64 ADR instruction, holding a simple 21 bit pc-relative byte
-     offset.
-
+ -- : BFD_RELOC_AARCH64_ADD_LO12
+     AArch64 ADD immediate instruction, holding bits 0 to 11 of the
+     address.  Used in conjunction with
+     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
+ -- : BFD_RELOC_AARCH64_LDST8_LO12
+     AArch64 8-bit load/store instruction, holding bits 0 to 11 of the
+     address.  Used in conjunction with
+     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
+ -- : BFD_RELOC_AARCH64_TSTBR14
+     AArch64 14 bit pc-relative test bit and branch.  The lowest two
+     bits must be zero and are not stored in the instruction, giving a
+     16 bit signed byte offset.
  -- : BFD_RELOC_AARCH64_BRANCH19
      AArch64 19 bit pc-relative conditional branch and compare & branch.
      The lowest two bits must be zero and are not stored in the
      instruction, giving a 21 bit signed byte offset.
-
- -- : BFD_RELOC_AARCH64_CALL26
-     AArch64 26 bit pc-relative unconditional branch and link.  The
-     lowest two bits must be zero and are not stored in the instruction,
-     giving a 28 bit signed byte offset.
-
- -- : BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP
-     AArch64 pseudo relocation code to be used internally by the AArch64
-     assembler and not (currently) written to any object files.
-
  -- : BFD_RELOC_AARCH64_JUMP26
      AArch64 26 bit pc-relative unconditional branch.  The lowest two
      bits must be zero and are not stored in the instruction, giving a
      28 bit signed byte offset.
-
- -- : BFD_RELOC_AARCH64_LD_LO19_PCREL
-     AArch64 Load Literal instruction, holding a 19 bit pc-relative word
-     offset.  The lowest two bits must be zero and are not stored in the
-     instruction, giving a 21 bit signed byte offset.
-
- -- : BFD_RELOC_AARCH64_LD64_GOT_LO12_NC
-     Unsigned 12 bit byte offset for 64 bit load/store from the page of
-     the GOT entry for this symbol.  Used in conjunction with
-     BFD_RELOC_AARCH64_ADR_GOTPAGE.
-
- -- : BFD_RELOC_AARCH64_LDST_LO12
-     AArch64 unspecified load/store instruction, holding bits 0 to 11
-     of the address.  Used in conjunction with
-     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
- -- : BFD_RELOC_AARCH64_LDST8_LO12
-     AArch64 8-bit load/store instruction, holding bits 0 to 11 of the
-     address.  Used in conjunction with
-     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
+ -- : BFD_RELOC_AARCH64_CALL26
+     AArch64 26 bit pc-relative unconditional branch and link.  The
+     lowest two bits must be zero and are not stored in the instruction,
+     giving a 28 bit signed byte offset.
  -- : BFD_RELOC_AARCH64_LDST16_LO12
      AArch64 16-bit load/store instruction, holding bits 0 to 11 of the
      address.  Used in conjunction with
      BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
  -- : BFD_RELOC_AARCH64_LDST32_LO12
      AArch64 32-bit load/store instruction, holding bits 0 to 11 of the
      address.  Used in conjunction with
      BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
  -- : BFD_RELOC_AARCH64_LDST64_LO12
      AArch64 64-bit load/store instruction, holding bits 0 to 11 of the
      address.  Used in conjunction with
      BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
  -- : BFD_RELOC_AARCH64_LDST128_LO12
      AArch64 128-bit load/store instruction, holding bits 0 to 11 of the
      address.  Used in conjunction with
      BFD_RELOC_AARCH64_ADR_HI21_PCREL.
-
- -- : BFD_RELOC_AARCH64_MOVW_G0
-     AArch64 MOV[NZK] instruction with most significant bits 0 to 15 of
-     an unsigned address/value.
-
- -- : BFD_RELOC_AARCH64_MOVW_G0_S
-     AArch64 MOV[NZ] instruction with most significant bits 0 to 15 of
-     a signed value.  Changes instruction to MOVZ or MOVN depending on
-     the value's sign.
-
- -- : BFD_RELOC_AARCH64_MOVW_G0_NC
-     AArch64 MOV[NZK] instruction with less significant bits 0 to 15 of
-     an address/value.  No overflow checking.
-
- -- : BFD_RELOC_AARCH64_MOVW_G1
-     AArch64 MOV[NZK] instruction with most significant bits 16 to 31
-     of an unsigned address/value.
-
- -- : BFD_RELOC_AARCH64_MOVW_G1_NC
-     AArch64 MOV[NZK] instruction with less significant bits 16 to 31
-     of an address/value.  No overflow checking.
-
- -- : BFD_RELOC_AARCH64_MOVW_G1_S
-     AArch64 MOV[NZ] instruction with most significant bits 16 to 31 of
-     a signed value.  Changes instruction to MOVZ or MOVN depending on
-     the value's sign.
-
- -- : BFD_RELOC_AARCH64_MOVW_G2
-     AArch64 MOV[NZK] instruction with most significant bits 32 to 47
-     of an unsigned address/value.
-
- -- : BFD_RELOC_AARCH64_MOVW_G2_NC
-     AArch64 MOV[NZK] instruction with less significant bits 32 to 47
-     of an address/value.  No overflow checking.
-
- -- : BFD_RELOC_AARCH64_MOVW_G2_S
-     AArch64 MOV[NZ] instruction with most significant bits 32 to 47 of
-     a signed value.  Changes instruction to MOVZ or MOVN depending on
-     the value's sign.
-
- -- : BFD_RELOC_AARCH64_MOVW_G3
-     AArch64 MOV[NZK] instruction with most signficant bits 48 to 64 of
-     a signed or unsigned address/value.
-
- -- : BFD_RELOC_AARCH64_TLSDESC
-     AArch64 TLS relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_ADD
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_CALL
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_LD64_PREL19
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_LDR
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G1
-     AArch64 TLS DESC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC
-     Unsigned 12 bit byte offset to global offset table entry for a
-     symbols tls_index structure.  Used in conjunction with
-     BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21.
-
+ -- : BFD_RELOC_AARCH64_GOT_LD_PREL19
+     AArch64 Load Literal instruction, holding a 19 bit PC relative word
+     offset of the global offset table entry for a symbol.  The lowest
+     two bits must be zero and are not stored in the instruction, giving
+     a 21 bit signed byte offset.  This relocation type requires signed
+     overflow checking.
+ -- : BFD_RELOC_AARCH64_ADR_GOT_PAGE
+     Get to the page base of the global offset table entry for a symbol
+     as part of an ADRP instruction using a 21 bit PC relative
+     value.Used in conjunction with BFD_RELOC_AARCH64_LD64_GOT_LO12_NC.
+ -- : BFD_RELOC_AARCH64_LD64_GOT_LO12_NC
+     Unsigned 12 bit byte offset for 64 bit load/store from the page of
+     the GOT entry for this symbol.  Used in conjunction with
+     BFD_RELOC_AARCH64_ADR_GOTPAGE. Valid in LP64 ABI only.
+ -- : BFD_RELOC_AARCH64_LD32_GOT_LO12_NC
+     Unsigned 12 bit byte offset for 32 bit load/store from the page of
+     the GOT entry for this symbol.  Used in conjunction with
+     BFD_RELOC_AARCH64_ADR_GOTPAGE. Valid in ILP32 ABI only.
  -- : BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21
      Get to the page base of the global offset table entry for a symbols
      tls_index structure as part of an adrp instruction using a 21 bit
      PC relative value.  Used in conjunction with
      BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC.
-
- -- : BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21
+ -- : BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC
+     Unsigned 12 bit byte offset to global offset table entry for a
+     symbols tls_index structure.  Used in conjunction with
+     BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21.
+ -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1
      AArch64 TLS INITIAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19
+ -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC
+     AArch64 TLS INITIAL EXEC relocation.
+ -- : BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21
      AArch64 TLS INITIAL EXEC relocation.
-
  -- : BFD_RELOC_AARCH64_TLSIE_LD64_GOTTPREL_LO12_NC
      AArch64 TLS INITIAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC
+ -- : BFD_RELOC_AARCH64_TLSIE_LD32_GOTTPREL_LO12_NC
      AArch64 TLS INITIAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1
+ -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19
      AArch64 TLS INITIAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12
+ -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12
+ -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC
+ -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC
      AArch64 TLS LOCAL EXEC relocation.
-
  -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0
      AArch64 TLS LOCAL EXEC relocation.
-
  -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1
+ -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC
+ -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2
+ -- : BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC
      AArch64 TLS LOCAL EXEC relocation.
-
- -- : BFD_RELOC_AARCH64_TLS_DTPMOD64
+ -- : BFD_RELOC_AARCH64_TLSDESC_LD_PREL19
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE21
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_LD32_LO12_NC
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G1
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_LDR
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_ADD
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC_CALL
+     AArch64 TLS DESC relocation.
+ -- : BFD_RELOC_AARCH64_COPY
      AArch64 TLS relocation.
-
- -- : BFD_RELOC_AARCH64_TLS_DTPREL64
+ -- : BFD_RELOC_AARCH64_GLOB_DAT
      AArch64 TLS relocation.
-
- -- : BFD_RELOC_AARCH64_TLS_TPREL64
+ -- : BFD_RELOC_AARCH64_JUMP_SLOT
      AArch64 TLS relocation.
-
- -- : BFD_RELOC_AARCH64_TSTBR14
-     AArch64 14 bit pc-relative test bit and branch.  The lowest two
-     bits must be zero and are not stored in the instruction, giving a
-     16 bit signed byte offset.
-
+ -- : BFD_RELOC_AARCH64_RELATIVE
+     AArch64 TLS relocation.
+ -- : BFD_RELOC_AARCH64_TLS_DTPMOD
+     AArch64 TLS relocation.
+ -- : BFD_RELOC_AARCH64_TLS_DTPREL
+     AArch64 TLS relocation.
+ -- : BFD_RELOC_AARCH64_TLS_TPREL
+     AArch64 TLS relocation.
+ -- : BFD_RELOC_AARCH64_TLSDESC
+     AArch64 TLS relocation.
+ -- : BFD_RELOC_AARCH64_IRELATIVE
+     AArch64 support for STT_GNU_IFUNC.
+ -- : BFD_RELOC_AARCH64_RELOC_END
+     AArch64 pseudo relocation code to mark the end of the AArch64
+     relocation enumerators that have direct mapping to ELF reloc codes.
+     There are a few more enumerators after this one; those are mainly
+     used by the AArch64 assembler for the internal fixup or to select
+     one of the above enumerators.
+ -- : BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP
+     AArch64 pseudo relocation code to be used internally by the AArch64
+     assembler and not (currently) written to any object files.
+ -- : BFD_RELOC_AARCH64_LDST_LO12
+     AArch64 unspecified load/store instruction, holding bits 0 to 11 of
+     the address.  Used in conjunction with
+     BFD_RELOC_AARCH64_ADR_HI21_PCREL.
+ -- : BFD_RELOC_AARCH64_LD_GOT_LO12_NC
+     AArch64 pseudo relocation code to be used internally by the AArch64
+     assembler and not (currently) written to any object files.
+ -- : BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_LO12_NC
+     AArch64 pseudo relocation code to be used internally by the AArch64
+     assembler and not (currently) written to any object files.
+ -- : BFD_RELOC_AARCH64_TLSDESC_LD_LO12_NC
+     AArch64 pseudo relocation code to be used internally by the AArch64
+     assembler and not (currently) written to any object files.
  -- : BFD_RELOC_TILEPRO_COPY
  -- : BFD_RELOC_TILEPRO_GLOB_DAT
  -- : BFD_RELOC_TILEPRO_JMP_SLOT
@@ -6367,7 +5971,6 @@ attributes.
  -- : BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HA
  -- : BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HA
      Tilera TILEPro Relocations.
-
  -- : BFD_RELOC_TILEGX_HW0
  -- : BFD_RELOC_TILEGX_HW1
  -- : BFD_RELOC_TILEGX_HW2
@@ -6478,33 +6081,26 @@ attributes.
  -- : BFD_RELOC_TILEGX_IMM8_Y0_TLS_ADD
  -- : BFD_RELOC_TILEGX_IMM8_Y1_TLS_ADD
      Tilera TILE-Gx Relocations.
-
  -- : BFD_RELOC_EPIPHANY_SIMM8
      Adapteva EPIPHANY - 8 bit signed pc-relative displacement
-
  -- : BFD_RELOC_EPIPHANY_SIMM24
      Adapteva EPIPHANY - 24 bit signed pc-relative displacement
-
  -- : BFD_RELOC_EPIPHANY_HIGH
      Adapteva EPIPHANY - 16 most-significant bits of absolute address
-
  -- : BFD_RELOC_EPIPHANY_LOW
      Adapteva EPIPHANY - 16 least-significant bits of absolute address
-
  -- : BFD_RELOC_EPIPHANY_SIMM11
      Adapteva EPIPHANY - 11 bit signed number - add/sub immediate
-
  -- : BFD_RELOC_EPIPHANY_IMM11
      Adapteva EPIPHANY - 11 bit sign-magnitude number (ld/st
      displacement)
-
  -- : BFD_RELOC_EPIPHANY_IMM8
      Adapteva EPIPHANY - 8 bit immediate for 16 bit mov instruction.
 
 
      typedef enum bfd_reloc_code_real bfd_reloc_code_real_type;
-   
-2.10.2.2 `bfd_reloc_type_lookup'
+
+2.10.2.2 'bfd_reloc_type_lookup'
 ................................
 
 *Synopsis*
@@ -6516,7 +6112,7 @@ attributes.
 Return a pointer to a howto structure which, when invoked, will perform
 the relocation CODE on data from the architecture noted.
 
-2.10.2.3 `bfd_default_reloc_type_lookup'
+2.10.2.3 'bfd_default_reloc_type_lookup'
 ........................................
 
 *Synopsis*
@@ -6525,7 +6121,7 @@ the relocation CODE on data from the architecture noted.
    *Description*
 Provides a default relocation lookup routine for any architecture.
 
-2.10.2.4 `bfd_get_reloc_code_name'
+2.10.2.4 'bfd_get_reloc_code_name'
 ..................................
 
 *Synopsis*
@@ -6534,7 +6130,7 @@ Provides a default relocation lookup routine for any architecture.
 Provides a printable name for the supplied relocation code.  Useful
 mainly for printing error messages.
 
-2.10.2.5 `bfd_generic_relax_section'
+2.10.2.5 'bfd_generic_relax_section'
 ....................................
 
 *Synopsis*
@@ -6547,7 +6143,7 @@ mainly for printing error messages.
 Provides default handling for relaxing for back ends which don't do
 relaxing.
 
-2.10.2.6 `bfd_generic_gc_sections'
+2.10.2.6 'bfd_generic_gc_sections'
 ..................................
 
 *Synopsis*
@@ -6557,7 +6153,7 @@ relaxing.
 Provides default handling for relaxing for back ends which don't do
 section gc - i.e., does nothing.
 
-2.10.2.7 `bfd_generic_lookup_section_flags'
+2.10.2.7 'bfd_generic_lookup_section_flags'
 ...........................................
 
 *Synopsis*
@@ -6567,7 +6163,7 @@ section gc - i.e., does nothing.
 Provides default handling for section flags lookup - i.e., does nothing.
 Returns FALSE if the section should be omitted, otherwise TRUE.
 
-2.10.2.8 `bfd_generic_merge_sections'
+2.10.2.8 'bfd_generic_merge_sections'
 .....................................
 
 *Synopsis*
@@ -6577,7 +6173,7 @@ Returns FALSE if the section should be omitted, otherwise TRUE.
 Provides default handling for SEC_MERGE section merging for back ends
 which don't have SEC_MERGE support - i.e., does nothing.
 
-2.10.2.9 `bfd_generic_get_relocated_section_contents'
+2.10.2.9 'bfd_generic_get_relocated_section_contents'
 .....................................................
 
 *Synopsis*
@@ -6589,8 +6185,8 @@ which don't have SEC_MERGE support - i.e., does nothing.
          bfd_boolean relocatable,
          asymbol **symbols);
    *Description*
-Provides default handling of relocation effort for back ends which
-can't be bothered to do it efficiently.
+Provides default handling of relocation effort for back ends which can't
+be bothered to do it efficiently.
 
 
 File: bfd.info,  Node: Core Files,  Next: Targets,  Prev: Relocations,  Up: BFD front end
@@ -6604,7 +6200,7 @@ File: bfd.info,  Node: Core Files,  Next: Targets,  Prev: Relocations,  Up: BFD
 *Description*
 These are functions pertaining to core files.
 
-2.11.1.1 `bfd_core_file_failing_command'
+2.11.1.1 'bfd_core_file_failing_command'
 ........................................
 
 *Synopsis*
@@ -6613,50 +6209,50 @@ These are functions pertaining to core files.
 Return a read-only string explaining which program was running when it
 failed and produced the core file ABFD.
 
-2.11.1.2 `bfd_core_file_failing_signal'
+2.11.1.2 'bfd_core_file_failing_signal'
 .......................................
 
 *Synopsis*
      int bfd_core_file_failing_signal (bfd *abfd);
    *Description*
-Returns the signal number which caused the core dump which generated
-the file the BFD ABFD is attached to.
+Returns the signal number which caused the core dump which generated the
+file the BFD ABFD is attached to.
 
-2.11.1.3 `bfd_core_file_pid'
+2.11.1.3 'bfd_core_file_pid'
 ............................
 
 *Synopsis*
      int bfd_core_file_pid (bfd *abfd);
    *Description*
-Returns the PID of the process the core dump the BFD ABFD is attached
-to was generated from.
+Returns the PID of the process the core dump the BFD ABFD is attached to
+was generated from.
 
-2.11.1.4 `core_file_matches_executable_p'
+2.11.1.4 'core_file_matches_executable_p'
 .........................................
 
 *Synopsis*
      bfd_boolean core_file_matches_executable_p
         (bfd *core_bfd, bfd *exec_bfd);
    *Description*
-Return `TRUE' if the core file attached to CORE_BFD was generated by a
-run of the executable file attached to EXEC_BFD, `FALSE' otherwise.
+Return 'TRUE' if the core file attached to CORE_BFD was generated by a
+run of the executable file attached to EXEC_BFD, 'FALSE' otherwise.
 
-2.11.1.5 `generic_core_file_matches_executable_p'
+2.11.1.5 'generic_core_file_matches_executable_p'
 .................................................
 
 *Synopsis*
      bfd_boolean generic_core_file_matches_executable_p
         (bfd *core_bfd, bfd *exec_bfd);
    *Description*
-Return TRUE if the core file attached to CORE_BFD was generated by a
-run of the executable file attached to EXEC_BFD.  The match is based on
+Return TRUE if the core file attached to CORE_BFD was generated by a run
+of the executable file attached to EXEC_BFD.  The match is based on
 executable basenames only.
 
-   Note: When not able to determine the core file failing command or
-the executable name, we still return TRUE even though we're not sure
-that core file and executable match.  This is to avoid generating a
-false warning in situations where we really don't know whether they
-match or not.
+   Note: When not able to determine the core file failing command or the
+executable name, we still return TRUE even though we're not sure that
+core file and executable match.  This is to avoid generating a false
+warning in situations where we really don't know whether they match or
+not.
 
 
 File: bfd.info,  Node: Targets,  Next: Architectures,  Prev: Core Files,  Up: BFD front end
@@ -6666,44 +6262,43 @@ File: bfd.info,  Node: Targets,  Next: Architectures,  Prev: Core Files,  Up: BF
 
 *Description*
 Each port of BFD to a different machine requires the creation of a
-target back end. All the back end provides to the root part of BFD is a
+target back end.  All the back end provides to the root part of BFD is a
 structure containing pointers to functions which perform certain low
-level operations on files. BFD translates the applications's requests
+level operations on files.  BFD translates the applications's requests
 through a pointer into calls to the back end routines.
 
-   When a file is opened with `bfd_openr', its format and target are
-unknown. BFD uses various mechanisms to determine how to interpret the
-file. The operations performed are:
+   When a file is opened with 'bfd_openr', its format and target are
+unknown.  BFD uses various mechanisms to determine how to interpret the
+file.  The operations performed are:
 
-   * Create a BFD by calling the internal routine `_bfd_new_bfd', then
-     call `bfd_find_target' with the target string supplied to
-     `bfd_openr' and the new BFD pointer.
+   * Create a BFD by calling the internal routine '_bfd_new_bfd', then
+     call 'bfd_find_target' with the target string supplied to
+     'bfd_openr' and the new BFD pointer.
 
-   * If a null target string was provided to `bfd_find_target', look up
-     the environment variable `GNUTARGET' and use that as the target
+   * If a null target string was provided to 'bfd_find_target', look up
+     the environment variable 'GNUTARGET' and use that as the target
      string.
 
-   * If the target string is still `NULL', or the target string is
-     `default', then use the first item in the target vector as the
-     target type, and set `target_defaulted' in the BFD to cause
-     `bfd_check_format' to loop through all the targets.  *Note
+   * If the target string is still 'NULL', or the target string is
+     'default', then use the first item in the target vector as the
+     target type, and set 'target_defaulted' in the BFD to cause
+     'bfd_check_format' to loop through all the targets.  *Note
      bfd_target::.  *Note Formats::.
 
    * Otherwise, inspect the elements in the target vector one by one,
-     until a match on target name is found. When found, use it.
+     until a match on target name is found.  When found, use it.
 
-   * Otherwise return the error `bfd_error_invalid_target' to
-     `bfd_openr'.
+   * Otherwise return the error 'bfd_error_invalid_target' to
+     'bfd_openr'.
 
-   * `bfd_openr' attempts to open the file using `bfd_open_file', and
+   * 'bfd_openr' attempts to open the file using 'bfd_open_file', and
      returns the BFD.
-   Once the BFD has been opened and the target selected, the file
-format may be determined. This is done by calling `bfd_check_format' on
-the BFD with a suggested format.  If `target_defaulted' has been set,
-each possible target type is tried to see if it recognizes the
-specified format.  `bfd_check_format' returns `TRUE' when the caller
-guesses right.
-
+   Once the BFD has been opened and the target selected, the file format
+may be determined.  This is done by calling 'bfd_check_format' on the
+BFD with a suggested format.  If 'target_defaulted' has been set, each
+possible target type is tried to see if it recognizes the specified
+format.  'bfd_check_format' returns 'TRUE' when the caller guesses
+right.
 * Menu:
 
 * bfd_target::
@@ -6715,15 +6310,15 @@ File: bfd.info,  Node: bfd_target,  Prev: Targets,  Up: Targets
 -----------------
 
 *Description*
-This structure contains everything that BFD knows about a target. It
-includes things like its byte order, name, and which routines to call
-to do various operations.
+This structure contains everything that BFD knows about a target.  It
+includes things like its byte order, name, and which routines to call to
+do various operations.
 
-   Every BFD points to a target structure with its `xvec' member.
+   Every BFD points to a target structure with its 'xvec' member.
 
    The macros below are used to dispatch to functions through the
-`bfd_target' vector. They are used in a number of macros further down
-in `bfd.h', and are also used when calling various routines by hand
+'bfd_target' vector.  They are used in a number of macros further down
+in 'bfd.h', and are also used when calling various routines by hand
 inside the BFD implementation.  The ARGLIST argument must be
 parenthesized; it contains all the arguments to the called function.
 
@@ -6750,13 +6345,14 @@ wants to fix this and not break the above, please do.
         (((bfd)->xvec->message[(int) ((bfd)->format)]) arglist) : \
         (bfd_assert (__FILE__,__LINE__), NULL))
      #endif
+
    This is the structure which defines the type of BFD this is.  The
-`xvec' member of the struct `bfd' itself points here.  Each module that
+'xvec' member of the struct 'bfd' itself points here.  Each module that
 implements access to a different target under BFD, defines one of these.
 
-   FIXME, these names should be rationalised with the names of the
-entry points which call them. Too bad we can't have one macro to define
-them both!
+   FIXME, these names should be rationalised with the names of the entry
+points which call them.  Too bad we can't have one macro to define them
+both!
      enum bfd_flavour
      {
        bfd_target_unknown_flavour,
@@ -6809,11 +6405,11 @@ them both!
        enum bfd_endian header_byteorder;
 
        /* A mask of all the flags which an executable may have set -
-          from the set `BFD_NO_FLAGS', `HAS_RELOC', ...`D_PAGED'.  */
+          from the set BFD_NO_FLAGS, HAS_RELOC, ...D_PAGED.  */
        flagword object_flags;
 
       /* A mask of all the flags which a section may have set - from
-         the set `SEC_NO_FLAGS', `SEC_ALLOC', ...`SET_NEVER_LOAD'.  */
+         the set SEC_NO_FLAGS, SEC_ALLOC, ...SET_NEVER_LOAD.  */
        flagword section_flags;
 
       /* The character normally found at the front of a symbol.
@@ -6857,14 +6453,15 @@ them both!
        /* Format dependent routines: these are vectors of entry points
           within the target vector structure, one for each format to check.  */
 
-       /* Check the format of a file being read.  Return a `bfd_target *' or zero.  */
+       /* Check the format of a file being read.  Return a bfd_target * or zero.  */
        const struct bfd_target *(*_bfd_check_format[bfd_type_end]) (bfd *);
 
        /* Set the format of a file being written.  */
        bfd_boolean (*_bfd_set_format[bfd_type_end]) (bfd *);
 
-       /* Write cached information into a file being written, at `bfd_close'.  */
+       /* Write cached information into a file being written, at bfd_close.  */
        bfd_boolean (*_bfd_write_contents[bfd_type_end]) (bfd *);
+
    The general target vector.  These vectors are initialized using the
 BFD_JUMP_TABLE macros.
 
@@ -7157,9 +6754,10 @@ BFD_JUMP_TABLE macros.
        /* Read in the dynamic relocs.  */
        long        (*_bfd_canonicalize_dynamic_reloc)
          (bfd *, arelent **, struct bfd_symbol **);
+
    A pointer to an alternative bfd_target in case the current one is not
-satisfactory.  This can happen when the target cpu supports both big
-and little endian code, and target chosen by the linker has the wrong
+satisfactory.  This can happen when the target cpu supports both big and
+little endian code, and target chosen by the linker has the wrong
 endianness.  The function open_output() in ld/ldlang.c uses this field
 to find an alternative output format that is suitable.
        /* Opposite endian version of this target.  */
@@ -7171,33 +6769,33 @@ to find an alternative output format that is suitable.
 
      } bfd_target;
 
-2.12.1.1 `bfd_set_default_target'
+2.12.1.1 'bfd_set_default_target'
 .................................
 
 *Synopsis*
      bfd_boolean bfd_set_default_target (const char *name);
    *Description*
-Set the default target vector to use when recognizing a BFD.  This
-takes the name of the target, which may be a BFD target name or a
+Set the default target vector to use when recognizing a BFD. This takes
+the name of the target, which may be a BFD target name or a
 configuration triplet.
 
-2.12.1.2 `bfd_find_target'
+2.12.1.2 'bfd_find_target'
 ..........................
 
 *Synopsis*
      const bfd_target *bfd_find_target (const char *target_name, bfd *abfd);
    *Description*
 Return a pointer to the transfer vector for the object target named
-TARGET_NAME.  If TARGET_NAME is `NULL', choose the one in the
-environment variable `GNUTARGET'; if that is null or not defined, then
+TARGET_NAME.  If TARGET_NAME is 'NULL', choose the one in the
+environment variable 'GNUTARGET'; if that is null or not defined, then
 choose the first entry in the target list.  Passing in the string
 "default" or setting the environment variable to "default" will cause
 the first entry in the target list to be returned, and
-"target_defaulted" will be set in the BFD if ABFD isn't `NULL'.  This
-causes `bfd_check_format' to loop over all the targets to find the one
+"target_defaulted" will be set in the BFD if ABFD isn't 'NULL'.  This
+causes 'bfd_check_format' to loop over all the targets to find the one
 that matches the file being read.
 
-2.12.1.3 `bfd_get_target_info'
+2.12.1.3 'bfd_get_target_info'
 ..............................
 
 *Synopsis*
@@ -7208,31 +6806,31 @@ that matches the file being read.
          const char **def_target_arch);
    *Description*
 Return a pointer to the transfer vector for the object target named
-TARGET_NAME.  If TARGET_NAME is `NULL', choose the one in the
-environment variable `GNUTARGET'; if that is null or not defined, then
+TARGET_NAME.  If TARGET_NAME is 'NULL', choose the one in the
+environment variable 'GNUTARGET'; if that is null or not defined, then
 choose the first entry in the target list.  Passing in the string
 "default" or setting the environment variable to "default" will cause
 the first entry in the target list to be returned, and
-"target_defaulted" will be set in the BFD if ABFD isn't `NULL'.  This
-causes `bfd_check_format' to loop over all the targets to find the one
-that matches the file being read.  If IS_BIGENDIAN is not `NULL', then
-set this value to target's endian mode. True for big-endian, FALSE for
-little-endian or for invalid target.  If UNDERSCORING is not `NULL',
-then set this value to target's underscoring mode. Zero for
+"target_defaulted" will be set in the BFD if ABFD isn't 'NULL'.  This
+causes 'bfd_check_format' to loop over all the targets to find the one
+that matches the file being read.  If IS_BIGENDIAN is not 'NULL', then
+set this value to target's endian mode.  True for big-endian, FALSE for
+little-endian or for invalid target.  If UNDERSCORING is not 'NULL',
+then set this value to target's underscoring mode.  Zero for
 none-underscoring, -1 for invalid target, else the value of target
-vector's symbol underscoring.  If DEF_TARGET_ARCH is not `NULL', then
+vector's symbol underscoring.  If DEF_TARGET_ARCH is not 'NULL', then
 set it to the architecture string specified by the target_name.
 
-2.12.1.4 `bfd_target_list'
+2.12.1.4 'bfd_target_list'
 ..........................
 
 *Synopsis*
      const char ** bfd_target_list (void);
    *Description*
-Return a freshly malloced NULL-terminated vector of the names of all
-the valid BFD targets. Do not modify the names.
+Return a freshly malloced NULL-terminated vector of the names of all the
+valid BFD targets.  Do not modify the names.
 
-2.12.1.5 `bfd_seach_for_target'
+2.12.1.5 'bfd_seach_for_target'
 ...............................
 
 *Synopsis*
@@ -7241,9 +6839,9 @@ the valid BFD targets. Do not modify the names.
          void *);
    *Description*
 Return a pointer to the first transfer vector in the list of transfer
-vectors maintained by BFD that produces a non-zero result when passed
-to the function SEARCH_FUNC.  The parameter DATA is passed, unexamined,
-to the search function.
+vectors maintained by BFD that produces a non-zero result when passed to
+the function SEARCH_FUNC.  The parameter DATA is passed, unexamined, to
+the search function.
 
 
 File: bfd.info,  Node: Architectures,  Next: Opening and Closing,  Prev: Targets,  Up: BFD front end
@@ -7252,25 +6850,25 @@ File: bfd.info,  Node: Architectures,  Next: Opening and Closing,  Prev: Targets
 ==================
 
 BFD keeps one atom in a BFD describing the architecture of the data
-attached to the BFD: a pointer to a `bfd_arch_info_type'.
+attached to the BFD: a pointer to a 'bfd_arch_info_type'.
 
    Pointers to structures can be requested independently of a BFD so
-that an architecture's information can be interrogated without access
-to an open BFD.
+that an architecture's information can be interrogated without access to
+an open BFD.
 
    The architecture information is provided by each architecture
 package.  The set of default architectures is selected by the macro
-`SELECT_ARCHITECTURES'.  This is normally set up in the
-`config/TARGET.mt' file of your choice.  If the name is not defined,
+'SELECT_ARCHITECTURES'.  This is normally set up in the
+'config/TARGET.mt' file of your choice.  If the name is not defined,
 then all the architectures supported are included.
 
    When BFD starts up, all the architectures are called with an
 initialize method.  It is up to the architecture back end to insert as
-many items into the list of architectures as it wants to; generally
-this would be one for each machine and one for the default case (an
-item with a machine field of 0).
+many items into the list of architectures as it wants to; generally this
+would be one for each machine and one for the default case (an item with
+a machine field of 0).
 
-   BFD's idea of an architecture is implemented in `archures.c'.
+   BFD's idea of an architecture is implemented in 'archures.c'.
 
 2.13.1 bfd_architecture
 -----------------------
@@ -7414,6 +7012,10 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030.
        bfd_arch_k1om,   /* Intel K1OM */
      #define bfd_mach_k1om                  (1 << 6)
      #define bfd_mach_k1om_intel_syntax     (bfd_mach_k1om | bfd_mach_i386_intel_syntax)
+     #define bfd_mach_i386_nacl             (1 << 7)
+     #define bfd_mach_i386_i386_nacl        (bfd_mach_i386_i386 | bfd_mach_i386_nacl)
+     #define bfd_mach_x86_64_nacl           (bfd_mach_x86_64 | bfd_mach_i386_nacl)
+     #define bfd_mach_x64_32_nacl           (bfd_mach_x64_32 | bfd_mach_i386_nacl)
        bfd_arch_we32k,     /* AT&T WE32xxx */
        bfd_arch_tahoe,     /* CCI/Harris Tahoe */
        bfd_arch_i860,      /* Intel 860 */
@@ -7651,7 +7253,12 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030.
      #define bfd_mach_msp14          14
      #define bfd_mach_msp15          15
      #define bfd_mach_msp16          16
+     #define bfd_mach_msp20          20
      #define bfd_mach_msp21          21
+     #define bfd_mach_msp22          22
+     #define bfd_mach_msp23          23
+     #define bfd_mach_msp24          24
+     #define bfd_mach_msp26          26
      #define bfd_mach_msp31          31
      #define bfd_mach_msp32          32
      #define bfd_mach_msp33          33
@@ -7659,6 +7266,10 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030.
      #define bfd_mach_msp42          42
      #define bfd_mach_msp43          43
      #define bfd_mach_msp44          44
+     #define bfd_mach_msp430x        45
+     #define bfd_mach_msp46          46
+     #define bfd_mach_msp47          47
+     #define bfd_mach_msp54          54
        bfd_arch_xc16x,     /* Infineon's XC16X Series.               */
      #define bfd_mach_xc16x         1
      #define bfd_mach_xc16xl        2
@@ -7682,6 +7293,7 @@ i960 KB, and 68020 and 68030 for Motorola 68020 and 68030.
      #define bfd_mach_tilegx32  2
        bfd_arch_aarch64,   /* AArch64  */
      #define bfd_mach_aarch64 0
+     #define bfd_mach_aarch64_ilp32 32
        bfd_arch_nios2,
      #define bfd_mach_nios2 0
        bfd_arch_last
@@ -7705,7 +7317,7 @@ This structure contains information on architectures for use within BFD.
        unsigned int section_align_power;
        /* TRUE if this is the default machine for the architecture.
           The default arch should be the first entry for an arch so that
-          all the entries for that arch can be accessed via `next'.  */
+          all the entries for that arch can be accessed via next.  */
        bfd_boolean the_default;
        const struct bfd_arch_info * (*compatible)
          (const struct bfd_arch_info *a, const struct bfd_arch_info *b);
@@ -7722,35 +7334,35 @@ This structure contains information on architectures for use within BFD.
      }
      bfd_arch_info_type;
 
-2.13.2.1 `bfd_printable_name'
+2.13.2.1 'bfd_printable_name'
 .............................
 
 *Synopsis*
      const char *bfd_printable_name (bfd *abfd);
    *Description*
-Return a printable string representing the architecture and machine
-from the pointer to the architecture info structure.
+Return a printable string representing the architecture and machine from
+the pointer to the architecture info structure.
 
-2.13.2.2 `bfd_scan_arch'
+2.13.2.2 'bfd_scan_arch'
 ........................
 
 *Synopsis*
      const bfd_arch_info_type *bfd_scan_arch (const char *string);
    *Description*
 Figure out if BFD supports any cpu which could be described with the
-name STRING.  Return a pointer to an `arch_info' structure if a machine
+name STRING.  Return a pointer to an 'arch_info' structure if a machine
 is found, otherwise NULL.
 
-2.13.2.3 `bfd_arch_list'
+2.13.2.3 'bfd_arch_list'
 ........................
 
 *Synopsis*
      const char **bfd_arch_list (void);
    *Description*
-Return a freshly malloced NULL-terminated vector of the names of all
-the valid BFD architectures.  Do not modify the names.
+Return a freshly malloced NULL-terminated vector of the names of all the
+valid BFD architectures.  Do not modify the names.
 
-2.13.2.4 `bfd_arch_get_compatible'
+2.13.2.4 'bfd_arch_get_compatible'
 ..................................
 
 *Synopsis*
@@ -7760,19 +7372,19 @@ the valid BFD architectures.  Do not modify the names.
 Determine whether two BFDs' architectures and machine types are
 compatible.  Calculates the lowest common denominator between the two
 architectures and machine types implied by the BFDs and returns a
-pointer to an `arch_info' structure describing the compatible machine.
+pointer to an 'arch_info' structure describing the compatible machine.
 
-2.13.2.5 `bfd_default_arch_struct'
+2.13.2.5 'bfd_default_arch_struct'
 ..................................
 
 *Description*
-The `bfd_default_arch_struct' is an item of `bfd_arch_info_type' which
+The 'bfd_default_arch_struct' is an item of 'bfd_arch_info_type' which
 has been initialized to a fairly generic state.  A BFD starts life by
 pointing to this structure, until the correct back end has determined
 the real architecture of the file.
      extern const bfd_arch_info_type bfd_default_arch_struct;
 
-2.13.2.6 `bfd_set_arch_info'
+2.13.2.6 'bfd_set_arch_info'
 ............................
 
 *Synopsis*
@@ -7780,7 +7392,7 @@ the real architecture of the file.
    *Description*
 Set the architecture info of ABFD to ARG.
 
-2.13.2.7 `bfd_default_set_arch_mach'
+2.13.2.7 'bfd_default_set_arch_mach'
 ....................................
 
 *Synopsis*
@@ -7789,9 +7401,9 @@ Set the architecture info of ABFD to ARG.
    *Description*
 Set the architecture and machine type in BFD ABFD to ARCH and MACH.
 Find the correct pointer to a structure and insert it into the
-`arch_info' pointer.
+'arch_info' pointer.
 
-2.13.2.8 `bfd_get_arch'
+2.13.2.8 'bfd_get_arch'
 .......................
 
 *Synopsis*
@@ -7799,7 +7411,7 @@ Find the correct pointer to a structure and insert it into the
    *Description*
 Return the enumerated type which describes the BFD ABFD's architecture.
 
-2.13.2.9 `bfd_get_mach'
+2.13.2.9 'bfd_get_mach'
 .......................
 
 *Synopsis*
@@ -7807,7 +7419,7 @@ Return the enumerated type which describes the BFD ABFD's architecture.
    *Description*
 Return the long type which describes the BFD ABFD's machine.
 
-2.13.2.10 `bfd_arch_bits_per_byte'
+2.13.2.10 'bfd_arch_bits_per_byte'
 ..................................
 
 *Synopsis*
@@ -7815,7 +7427,7 @@ Return the long type which describes the BFD ABFD's machine.
    *Description*
 Return the number of bits in one of the BFD ABFD's architecture's bytes.
 
-2.13.2.11 `bfd_arch_bits_per_address'
+2.13.2.11 'bfd_arch_bits_per_address'
 .....................................
 
 *Synopsis*
@@ -7824,7 +7436,7 @@ Return the number of bits in one of the BFD ABFD's architecture's bytes.
 Return the number of bits in one of the BFD ABFD's architecture's
 addresses.
 
-2.13.2.12 `bfd_default_compatible'
+2.13.2.12 'bfd_default_compatible'
 ..................................
 
 *Synopsis*
@@ -7833,17 +7445,17 @@ addresses.
    *Description*
 The default function for testing for compatibility.
 
-2.13.2.13 `bfd_default_scan'
+2.13.2.13 'bfd_default_scan'
 ............................
 
 *Synopsis*
      bfd_boolean bfd_default_scan
         (const struct bfd_arch_info *info, const char *string);
    *Description*
-The default function for working out whether this is an architecture
-hit and a machine hit.
+The default function for working out whether this is an architecture hit
+and a machine hit.
 
-2.13.2.14 `bfd_get_arch_info'
+2.13.2.14 'bfd_get_arch_info'
 .............................
 
 *Synopsis*
@@ -7851,7 +7463,7 @@ hit and a machine hit.
    *Description*
 Return the architecture info struct in ABFD.
 
-2.13.2.15 `bfd_lookup_arch'
+2.13.2.15 'bfd_lookup_arch'
 ...........................
 
 *Synopsis*
@@ -7859,10 +7471,10 @@ Return the architecture info struct in ABFD.
         (enum bfd_architecture arch, unsigned long machine);
    *Description*
 Look for the architecture info structure which matches the arguments
-ARCH and MACHINE. A machine of 0 matches the machine/architecture
+ARCH and MACHINE.  A machine of 0 matches the machine/architecture
 structure which marks itself as the default.
 
-2.13.2.16 `bfd_printable_arch_mach'
+2.13.2.16 'bfd_printable_arch_mach'
 ...................................
 
 *Synopsis*
@@ -7874,7 +7486,7 @@ type.
 
    This routine is depreciated.
 
-2.13.2.17 `bfd_octets_per_byte'
+2.13.2.17 'bfd_octets_per_byte'
 ...............................
 
 *Synopsis*
@@ -7884,7 +7496,7 @@ Return the number of octets (8-bit quantities) per target byte (minimum
 addressable unit).  In most cases, this will be one, but some DSP
 targets have 16, 32, or even 48 bits per byte.
 
-2.13.2.18 `bfd_arch_mach_octets_per_byte'
+2.13.2.18 'bfd_arch_mach_octets_per_byte'
 .........................................
 
 *Synopsis*
@@ -7896,7 +7508,7 @@ See bfd_octets_per_byte.
    This routine is provided for those cases where a bfd * is not
 available
 
-2.13.2.19 `bfd_arch_default_fill'
+2.13.2.19 'bfd_arch_default_fill'
 .................................
 
 *Synopsis*
@@ -7904,7 +7516,7 @@ available
          bfd_boolean is_bigendian,
          bfd_boolean code);
    *Description*
-Allocate via bfd_malloc and return a fill buffer of size COUNT.  If
+Allocate via bfd_malloc and return a fill buffer of size COUNT. If
 IS_BIGENDIAN is TRUE, the order of bytes is big endian.  If CODE is
 TRUE, the buffer contains code.
 
@@ -7920,7 +7532,7 @@ File: bfd.info,  Node: Opening and Closing,  Next: Internal,  Prev: Architecture
 2.14.1 Functions for opening and closing
 ----------------------------------------
 
-2.14.1.1 `bfd_fopen'
+2.14.1.1 'bfd_fopen'
 ....................
 
 *Synopsis*
@@ -7928,70 +7540,70 @@ File: bfd.info,  Node: Opening and Closing,  Next: Internal,  Prev: Architecture
          const char *mode, int fd);
    *Description*
 Open the file FILENAME with the target TARGET.  Return a pointer to the
-created BFD.  If FD is not -1, then `fdopen' is used to open the file;
-otherwise, `fopen' is used.  MODE is passed directly to `fopen' or
-`fdopen'.
+created BFD. If FD is not -1, then 'fdopen' is used to open the file;
+otherwise, 'fopen' is used.  MODE is passed directly to 'fopen' or
+'fdopen'.
 
-   Calls `bfd_find_target', so TARGET is interpreted as by that
+   Calls 'bfd_find_target', so TARGET is interpreted as by that
 function.
 
    The new BFD is marked as cacheable iff FD is -1.
 
-   If `NULL' is returned then an error has occured.   Possible errors
-are `bfd_error_no_memory', `bfd_error_invalid_target' or `system_call'
+   If 'NULL' is returned then an error has occured.  Possible errors are
+'bfd_error_no_memory', 'bfd_error_invalid_target' or 'system_call'
 error.
 
    On error, FD is always closed.
 
-2.14.1.2 `bfd_openr'
+2.14.1.2 'bfd_openr'
 ....................
 
 *Synopsis*
      bfd *bfd_openr (const char *filename, const char *target);
    *Description*
-Open the file FILENAME (using `fopen') with the target TARGET.  Return
-a pointer to the created BFD.
+Open the file FILENAME (using 'fopen') with the target TARGET.  Return a
+pointer to the created BFD.
 
-   Calls `bfd_find_target', so TARGET is interpreted as by that
+   Calls 'bfd_find_target', so TARGET is interpreted as by that
 function.
 
-   If `NULL' is returned then an error has occured.   Possible errors
-are `bfd_error_no_memory', `bfd_error_invalid_target' or `system_call'
+   If 'NULL' is returned then an error has occured.  Possible errors are
+'bfd_error_no_memory', 'bfd_error_invalid_target' or 'system_call'
 error.
 
-2.14.1.3 `bfd_fdopenr'
+2.14.1.3 'bfd_fdopenr'
 ......................
 
 *Synopsis*
      bfd *bfd_fdopenr (const char *filename, const char *target, int fd);
    *Description*
-`bfd_fdopenr' is to `bfd_fopenr' much like `fdopen' is to `fopen'.  It
+'bfd_fdopenr' is to 'bfd_fopenr' much like 'fdopen' is to 'fopen'.  It
 opens a BFD on a file already described by the FD supplied.
 
-   When the file is later `bfd_close'd, the file descriptor will be
+   When the file is later 'bfd_close'd, the file descriptor will be
 closed.  If the caller desires that this file descriptor be cached by
 BFD (opened as needed, closed as needed to free descriptors for other
 opens), with the supplied FD used as an initial file descriptor (but
 subject to closure at any time), call bfd_set_cacheable(bfd, 1) on the
-returned BFD.  The default is to assume no caching; the file descriptor
-will remain open until `bfd_close', and will not be affected by BFD
+returned BFD. The default is to assume no caching; the file descriptor
+will remain open until 'bfd_close', and will not be affected by BFD
 operations on other files.
 
-   Possible errors are `bfd_error_no_memory',
-`bfd_error_invalid_target' and `bfd_error_system_call'.
+   Possible errors are 'bfd_error_no_memory', 'bfd_error_invalid_target'
+and 'bfd_error_system_call'.
 
    On error, FD is closed.
 
-2.14.1.4 `bfd_openstreamr'
+2.14.1.4 'bfd_openstreamr'
 ..........................
 
 *Synopsis*
      bfd *bfd_openstreamr (const char *, const char *, void *);
    *Description*
-Open a BFD for read access on an existing stdio stream.  When the BFD
-is passed to `bfd_close', the stream will be closed.
+Open a BFD for read access on an existing stdio stream.  When the BFD is
+passed to 'bfd_close', the stream will be closed.
 
-2.14.1.5 `bfd_openr_iovec'
+2.14.1.5 'bfd_openr_iovec'
 ..........................
 
 *Synopsis*
@@ -8014,32 +7626,32 @@ Create and return a BFD backed by a read-only STREAM.  The STREAM is
 created using OPEN_FUNC, accessed using PREAD_FUNC and destroyed using
 CLOSE_FUNC.
 
-   Calls `bfd_find_target', so TARGET is interpreted as by that
+   Calls 'bfd_find_target', so TARGET is interpreted as by that
 function.
 
-   Calls OPEN_FUNC (which can call `bfd_zalloc' and `bfd_get_filename')
-to obtain the read-only stream backing the BFD.  OPEN_FUNC either
-succeeds returning the non-`NULL' STREAM, or fails returning `NULL'
-(setting `bfd_error').
+   Calls OPEN_FUNC (which can call 'bfd_zalloc' and 'bfd_get_filename')
+to obtain the read-only stream backing the BFD. OPEN_FUNC either
+succeeds returning the non-'NULL' STREAM, or fails returning 'NULL'
+(setting 'bfd_error').
 
    Calls PREAD_FUNC to request NBYTES of data from STREAM starting at
-OFFSET (e.g., via a call to `bfd_read').  PREAD_FUNC either succeeds
+OFFSET (e.g., via a call to 'bfd_read').  PREAD_FUNC either succeeds
 returning the number of bytes read (which can be less than NBYTES when
-end-of-file), or fails returning -1 (setting `bfd_error').
+end-of-file), or fails returning -1 (setting 'bfd_error').
 
-   Calls CLOSE_FUNC when the BFD is later closed using `bfd_close'.
+   Calls CLOSE_FUNC when the BFD is later closed using 'bfd_close'.
 CLOSE_FUNC either succeeds returning 0, or fails returning -1 (setting
-`bfd_error').
+'bfd_error').
 
    Calls STAT_FUNC to fill in a stat structure for bfd_stat,
 bfd_get_size, and bfd_get_mtime calls.  STAT_FUNC returns 0 on success,
-or returns -1 on failure (setting `bfd_error').
+or returns -1 on failure (setting 'bfd_error').
 
-   If `bfd_openr_iovec' returns `NULL' then an error has occurred.
-Possible errors are `bfd_error_no_memory', `bfd_error_invalid_target'
-and `bfd_error_system_call'.
+   If 'bfd_openr_iovec' returns 'NULL' then an error has occurred.
+Possible errors are 'bfd_error_no_memory', 'bfd_error_invalid_target'
+and 'bfd_error_system_call'.
 
-2.14.1.6 `bfd_openw'
+2.14.1.6 'bfd_openw'
 ....................
 
 *Synopsis*
@@ -8048,10 +7660,10 @@ and `bfd_error_system_call'.
 Create a BFD, associated with file FILENAME, using the file format
 TARGET, and return a pointer to it.
 
-   Possible errors are `bfd_error_system_call', `bfd_error_no_memory',
-`bfd_error_invalid_target'.
+   Possible errors are 'bfd_error_system_call', 'bfd_error_no_memory',
+'bfd_error_invalid_target'.
 
-2.14.1.7 `bfd_close'
+2.14.1.7 'bfd_close'
 ....................
 
 *Synopsis*
@@ -8059,110 +7671,110 @@ TARGET, and return a pointer to it.
    *Description*
 Close a BFD. If the BFD was open for writing, then pending operations
 are completed and the file written out and closed.  If the created file
-is executable, then `chmod' is called to mark it as such.
+is executable, then 'chmod' is called to mark it as such.
 
    All memory attached to the BFD is released.
 
-   The file descriptor associated with the BFD is closed (even if it
-was passed in to BFD by `bfd_fdopenr').
+   The file descriptor associated with the BFD is closed (even if it was
+passed in to BFD by 'bfd_fdopenr').
 
    *Returns*
-`TRUE' is returned if all is ok, otherwise `FALSE'.
+'TRUE' is returned if all is ok, otherwise 'FALSE'.
 
-2.14.1.8 `bfd_close_all_done'
+2.14.1.8 'bfd_close_all_done'
 .............................
 
 *Synopsis*
      bfd_boolean bfd_close_all_done (bfd *);
    *Description*
-Close a BFD.  Differs from `bfd_close' since it does not complete any
+Close a BFD. Differs from 'bfd_close' since it does not complete any
 pending operations.  This routine would be used if the application had
 just used BFD for swapping and didn't want to use any of the writing
 code.
 
-   If the created file is executable, then `chmod' is called to mark it
+   If the created file is executable, then 'chmod' is called to mark it
 as such.
 
    All memory attached to the BFD is released.
 
    *Returns*
-`TRUE' is returned if all is ok, otherwise `FALSE'.
+'TRUE' is returned if all is ok, otherwise 'FALSE'.
 
-2.14.1.9 `bfd_create'
+2.14.1.9 'bfd_create'
 .....................
 
 *Synopsis*
      bfd *bfd_create (const char *filename, bfd *templ);
    *Description*
-Create a new BFD in the manner of `bfd_openw', but without opening a
-file. The new BFD takes the target from the target used by TEMPL. The
-format is always set to `bfd_object'.
+Create a new BFD in the manner of 'bfd_openw', but without opening a
+file.  The new BFD takes the target from the target used by TEMPL.  The
+format is always set to 'bfd_object'.
 
-2.14.1.10 `bfd_make_writable'
+2.14.1.10 'bfd_make_writable'
 .............................
 
 *Synopsis*
      bfd_boolean bfd_make_writable (bfd *abfd);
    *Description*
-Takes a BFD as created by `bfd_create' and converts it into one like as
-returned by `bfd_openw'.  It does this by converting the BFD to
-BFD_IN_MEMORY.  It's assumed that you will call `bfd_make_readable' on
+Takes a BFD as created by 'bfd_create' and converts it into one like as
+returned by 'bfd_openw'.  It does this by converting the BFD to
+BFD_IN_MEMORY. It's assumed that you will call 'bfd_make_readable' on
 this bfd later.
 
    *Returns*
-`TRUE' is returned if all is ok, otherwise `FALSE'.
+'TRUE' is returned if all is ok, otherwise 'FALSE'.
 
-2.14.1.11 `bfd_make_readable'
+2.14.1.11 'bfd_make_readable'
 .............................
 
 *Synopsis*
      bfd_boolean bfd_make_readable (bfd *abfd);
    *Description*
-Takes a BFD as created by `bfd_create' and `bfd_make_writable' and
-converts it into one like as returned by `bfd_openr'.  It does this by
+Takes a BFD as created by 'bfd_create' and 'bfd_make_writable' and
+converts it into one like as returned by 'bfd_openr'.  It does this by
 writing the contents out to the memory buffer, then reversing the
 direction.
 
    *Returns*
-`TRUE' is returned if all is ok, otherwise `FALSE'.
+'TRUE' is returned if all is ok, otherwise 'FALSE'.
 
-2.14.1.12 `bfd_alloc'
+2.14.1.12 'bfd_alloc'
 .....................
 
 *Synopsis*
      void *bfd_alloc (bfd *abfd, bfd_size_type wanted);
    *Description*
-Allocate a block of WANTED bytes of memory attached to `abfd' and
-return a pointer to it.
+Allocate a block of WANTED bytes of memory attached to 'abfd' and return
+a pointer to it.
 
-2.14.1.13 `bfd_alloc2'
+2.14.1.13 'bfd_alloc2'
 ......................
 
 *Synopsis*
      void *bfd_alloc2 (bfd *abfd, bfd_size_type nmemb, bfd_size_type size);
    *Description*
-Allocate a block of NMEMB elements of SIZE bytes each of memory
-attached to `abfd' and return a pointer to it.
+Allocate a block of NMEMB elements of SIZE bytes each of memory attached
+to 'abfd' and return a pointer to it.
 
-2.14.1.14 `bfd_zalloc'
+2.14.1.14 'bfd_zalloc'
 ......................
 
 *Synopsis*
      void *bfd_zalloc (bfd *abfd, bfd_size_type wanted);
    *Description*
-Allocate a block of WANTED bytes of zeroed memory attached to `abfd'
-and return a pointer to it.
+Allocate a block of WANTED bytes of zeroed memory attached to 'abfd' and
+return a pointer to it.
 
-2.14.1.15 `bfd_zalloc2'
+2.14.1.15 'bfd_zalloc2'
 .......................
 
 *Synopsis*
      void *bfd_zalloc2 (bfd *abfd, bfd_size_type nmemb, bfd_size_type size);
    *Description*
 Allocate a block of NMEMB elements of SIZE bytes each of zeroed memory
-attached to `abfd' and return a pointer to it.
+attached to 'abfd' and return a pointer to it.
 
-2.14.1.16 `bfd_calc_gnu_debuglink_crc32'
+2.14.1.16 'bfd_calc_gnu_debuglink_crc32'
 ........................................
 
 *Synopsis*
@@ -8176,18 +7788,29 @@ for LEN bytes of BUF.
    *Returns*
 Return the updated CRC32 value.
 
-2.14.1.17 `bfd_get_debug_link_info'
+2.14.1.17 'bfd_get_debug_link_info'
 ...................................
 
 *Synopsis*
      char *bfd_get_debug_link_info (bfd *abfd, unsigned long *crc32_out);
    *Description*
-fetch the filename and CRC32 value for any separate debuginfo
-associated with ABFD. Return NULL if no such info found, otherwise
-return filename and update CRC32_OUT.  The returned filename is
-allocated with `malloc'; freeing it is the responsibility of the caller.
+fetch the filename and CRC32 value for any separate debuginfo associated
+with ABFD.  Return NULL if no such info found, otherwise return filename
+and update CRC32_OUT.  The returned filename is allocated with 'malloc';
+freeing it is the responsibility of the caller.
+
+2.14.1.18 'bfd_get_alt_debug_link_info'
+.......................................
 
-2.14.1.18 `separate_debug_file_exists'
+*Synopsis*
+     char *bfd_get_alt_debug_link_info (bfd *abfd, unsigned long *crc32_out);
+   *Description*
+Fetch the filename and BuildID value for any alternate debuginfo
+associated with ABFD.  Return NULL if no such info found, otherwise
+return filename and update BUILDID_OUT.  The returned filename is
+allocated with 'malloc'; freeing it is the responsibility of the caller.
+
+2.14.1.19 'separate_debug_file_exists'
 ......................................
 
 *Synopsis*
@@ -8196,40 +7819,71 @@ allocated with `malloc'; freeing it is the responsibility of the caller.
    *Description*
 Checks to see if NAME is a file and if its contents match CRC32.
 
-2.14.1.19 `find_separate_debug_file'
+2.14.1.20 'separate_alt_debug_file_exists'
+..........................................
+
+*Synopsis*
+     bfd_boolean separate_alt_debug_file_exists
+        (char *name, unsigned long crc32);
+   *Description*
+Checks to see if NAME is a file and if its BuildID matches BUILDID.
+
+2.14.1.21 'find_separate_debug_file'
 ....................................
 
 *Synopsis*
      char *find_separate_debug_file (bfd *abfd);
    *Description*
-Searches ABFD for a reference to separate debugging information, scans
-various locations in the filesystem, including the file tree rooted at
-DEBUG_FILE_DIRECTORY, and returns a filename of such debugging
-information if the file is found and has matching CRC32.  Returns NULL
-if no reference to debugging file exists, or file cannot be found.
+Searches ABFD for a section called SECTION_NAME which is expected to
+contain a reference to a file containing separate debugging information.
+The function scans various locations in the filesystem, including the
+file tree rooted at DEBUG_FILE_DIRECTORY, and returns the first matching
+filename that it finds.  If CHECK_CRC is TRUE then the contents of the
+file must also match the CRC value contained in SECTION_NAME.  Returns
+NULL if no valid file could be found.
 
-2.14.1.20 `bfd_follow_gnu_debuglink'
+2.14.1.22 'bfd_follow_gnu_debuglink'
 ....................................
 
 *Synopsis*
      char *bfd_follow_gnu_debuglink (bfd *abfd, const char *dir);
    *Description*
 Takes a BFD and searches it for a .gnu_debuglink section.  If this
-section is found, it examines the section for the name and checksum of
-a '.debug' file containing auxiliary debugging information.  It then
-searches the filesystem for this .debug file in some standard
-locations, including the directory tree rooted at DIR, and if found
-returns the full filename.
+section is found, it examines the section for the name and checksum of a
+'.debug' file containing auxiliary debugging information.  It then
+searches the filesystem for this .debug file in some standard locations,
+including the directory tree rooted at DIR, and if found returns the
+full filename.
 
    If DIR is NULL, it will search a default path configured into libbfd
 at build time.  [XXX this feature is not currently implemented].
 
    *Returns*
-`NULL' on any errors or failure to locate the .debug file, otherwise a
+'NULL' on any errors or failure to locate the .debug file, otherwise a
 pointer to a heap-allocated string containing the filename.  The caller
 is responsible for freeing this string.
 
-2.14.1.21 `bfd_create_gnu_debuglink_section'
+2.14.1.23 'bfd_follow_gnu_debugaltlink'
+.......................................
+
+*Synopsis*
+     char *bfd_follow_gnu_debugaltlink (bfd *abfd, const char *dir);
+   *Description*
+Takes a BFD and searches it for a .gnu_debugaltlink section.  If this
+section is found, it examines the section for the name of a file
+containing auxiliary debugging information.  It then searches the
+filesystem for this file in a set of standard locations, including the
+directory tree rooted at DIR, and if found returns the full filename.
+
+   If DIR is NULL, it will search a default path configured into libbfd
+at build time.  [FIXME: This feature is not currently implemented].
+
+   *Returns*
+'NULL' on any errors or failure to locate the debug file, otherwise a
+pointer to a heap-allocated string containing the filename.  The caller
+is responsible for freeing this string.
+
+2.14.1.24 'bfd_create_gnu_debuglink_section'
 ............................................
 
 *Synopsis*
@@ -8240,10 +7894,10 @@ Takes a BFD and adds a .gnu_debuglink section to it.  The section is
 sized to be big enough to contain a link to the specified FILENAME.
 
    *Returns*
-A pointer to the new section is returned if all is ok.  Otherwise
-`NULL' is returned and bfd_error is set.
+A pointer to the new section is returned if all is ok.  Otherwise 'NULL'
+is returned and bfd_error is set.
 
-2.14.1.22 `bfd_fill_in_gnu_debuglink_section'
+2.14.1.25 'bfd_fill_in_gnu_debuglink_section'
 .............................................
 
 *Synopsis*
@@ -8251,27 +7905,13 @@ A pointer to the new section is returned if all is ok.  Otherwise
         (bfd *abfd, struct bfd_section *sect, const char *filename);
    *Description*
 Takes a BFD and containing a .gnu_debuglink section SECT and fills in
-the contents of the section to contain a link to the specified
-FILENAME.  The filename should be relative to the current directory.
+the contents of the section to contain a link to the specified FILENAME.
+The filename should be relative to the current directory.
 
    *Returns*
-`TRUE' is returned if all is ok.  Otherwise `FALSE' is returned and
+'TRUE' is returned if all is ok.  Otherwise 'FALSE' is returned and
 bfd_error is set.
 
-2.14.1.23 `bfd_extract_object_only_section'
-...........................................
-
-*Synopsis*
-     const char *bfd_extract_object_only_section
-        (bfd *abfd);
-   *Description*
-Takes a ABFD and extract the .gnu_object_only section into a temporary
-file.
-
-   *Returns*
-The name of the temporary file is returned if all is ok.  Otherwise
-`NULL' is returned and bfd_error is set.
-
 
 File: bfd.info,  Node: Internal,  Next: File Caching,  Prev: Opening and Closing,  Up: BFD front end
 
@@ -8282,10 +7922,10 @@ File: bfd.info,  Node: Internal,  Next: File Caching,  Prev: Opening and Closing
 -------------------------
 
 *Description*
-These routines are used within BFD.  They are not intended for export,
+These routines are used within BFD. They are not intended for export,
 but are documented here for completeness.
 
-2.15.1.1 `bfd_write_bigendian_4byte_int'
+2.15.1.1 'bfd_write_bigendian_4byte_int'
 ........................................
 
 *Synopsis*
@@ -8294,28 +7934,28 @@ but are documented here for completeness.
 Write a 4 byte integer I to the output BFD ABFD, in big endian order
 regardless of what else is going on.  This is useful in archives.
 
-2.15.1.2 `bfd_put_size'
+2.15.1.2 'bfd_put_size'
 .......................
 
-2.15.1.3 `bfd_get_size'
+2.15.1.3 'bfd_get_size'
 .......................
 
 *Description*
 These macros as used for reading and writing raw data in sections; each
 access (except for bytes) is vectored through the target format of the
-BFD and mangled accordingly. The mangling performs any necessary endian
+BFD and mangled accordingly.  The mangling performs any necessary endian
 translations and removes alignment restrictions.  Note that types
 accepted and returned by these macros are identical so they can be
-swapped around in macros--for example, `libaout.h' defines `GET_WORD'
-to either `bfd_get_32' or `bfd_get_64'.
+swapped around in macros--for example, 'libaout.h' defines 'GET_WORD' to
+either 'bfd_get_32' or 'bfd_get_64'.
 
-   In the put routines, VAL must be a `bfd_vma'.  If we are on a system
+   In the put routines, VAL must be a 'bfd_vma'.  If we are on a system
 without prototypes, the caller is responsible for making sure that is
 true, with a cast if necessary.  We don't cast them in the macro
-definitions because that would prevent `lint' or `gcc -Wall' from
+definitions because that would prevent 'lint' or 'gcc -Wall' from
 detecting sins such as passing a pointer.  To detect calling these with
-less than a `bfd_vma', use `gcc -Wconversion' on a host with 64 bit
-`bfd_vma''s.
+less than a 'bfd_vma', use 'gcc -Wconversion' on a host with 64 bit
+'bfd_vma''s.
 
      /* Byte swapping macros for user section data.  */
 
@@ -8369,15 +8009,15 @@ less than a `bfd_vma', use `gcc -Wconversion' on a host with 64 bit
         : (bits) == 64 ? bfd_put_64 (abfd, val, ptr)                \
         : (abort (), (void) 0))
 
-2.15.1.4 `bfd_h_put_size'
+2.15.1.4 'bfd_h_put_size'
 .........................
 
 *Description*
-These macros have the same function as their `bfd_get_x' brethren,
+These macros have the same function as their 'bfd_get_x' brethren,
 except that they are used for removing information for the header
-records of object files. Believe it or not, some object files keep
-their header records in big endian order and their data in little
-endian order.
+records of object files.  Believe it or not, some object files keep
+their header records in big endian order and their data in little endian
+order.
 
      /* Byte swapping macros for file header data.  */
 
@@ -8436,7 +8076,8 @@ endian order.
      #define H_GET_S16 bfd_h_get_signed_16
      #define H_GET_S8  bfd_h_get_signed_8
 
-2.15.1.5 `bfd_log2'
+
+2.15.1.5 'bfd_log2'
 ...................
 
 *Synopsis*
@@ -8454,16 +8095,16 @@ File: bfd.info,  Node: File Caching,  Next: Linker Functions,  Prev: Internal,
 The file caching mechanism is embedded within BFD and allows the
 application to open as many BFDs as it wants without regard to the
 underlying operating system's file descriptor limit (often as low as 20
-open files).  The module in `cache.c' maintains a least recently used
-list of `BFD_CACHE_MAX_OPEN' files, and exports the name
-`bfd_cache_lookup', which runs around and makes sure that the required
-BFD is open. If not, then it chooses a file to close, closes it and
+open files).  The module in 'cache.c' maintains a least recently used
+list of 'bfd_cache_max_open' files, and exports the name
+'bfd_cache_lookup', which runs around and makes sure that the required
+BFD is open.  If not, then it chooses a file to close, closes it and
 opens the one wanted, returning its file handle.
 
 2.16.1 Caching functions
 ------------------------
 
-2.16.1.1 `bfd_cache_init'
+2.16.1.1 'bfd_cache_init'
 .........................
 
 *Synopsis*
@@ -8471,43 +8112,43 @@ opens the one wanted, returning its file handle.
    *Description*
 Add a newly opened BFD to the cache.
 
-2.16.1.2 `bfd_cache_close'
+2.16.1.2 'bfd_cache_close'
 ..........................
 
 *Synopsis*
      bfd_boolean bfd_cache_close (bfd *abfd);
    *Description*
-Remove the BFD ABFD from the cache. If the attached file is open, then
+Remove the BFD ABFD from the cache.  If the attached file is open, then
 close it too.
 
    *Returns*
-`FALSE' is returned if closing the file fails, `TRUE' is returned if
-all is well.
+'FALSE' is returned if closing the file fails, 'TRUE' is returned if all
+is well.
 
-2.16.1.3 `bfd_cache_close_all'
+2.16.1.3 'bfd_cache_close_all'
 ..............................
 
 *Synopsis*
      bfd_boolean bfd_cache_close_all (void);
    *Description*
-Remove all BFDs from the cache. If the attached file is open, then
+Remove all BFDs from the cache.  If the attached file is open, then
 close it too.
 
    *Returns*
-`FALSE' is returned if closing one of the file fails, `TRUE' is
-returned if all is well.
+'FALSE' is returned if closing one of the file fails, 'TRUE' is returned
+if all is well.
 
-2.16.1.4 `bfd_open_file'
+2.16.1.4 'bfd_open_file'
 ........................
 
 *Synopsis*
      FILE* bfd_open_file (bfd *abfd);
    *Description*
-Call the OS to open a file for ABFD.  Return the `FILE *' (possibly
-`NULL') that results from this operation.  Set up the BFD so that
-future accesses know the file is open. If the `FILE *' returned is
-`NULL', then it won't have been put in the cache, so it won't have to
-be removed from it.
+Call the OS to open a file for ABFD.  Return the 'FILE *' (possibly
+'NULL') that results from this operation.  Set up the BFD so that future
+accesses know the file is open.  If the 'FILE *' returned is 'NULL',
+then it won't have been put in the cache, so it won't have to be removed
+from it.
 
 
 File: bfd.info,  Node: Linker Functions,  Next: Hash Tables,  Prev: File Caching,  Up: BFD front end
@@ -8515,31 +8156,31 @@ File: bfd.info,  Node: Linker Functions,  Next: Hash Tables,  Prev: File Caching
 2.17 Linker Functions
 =====================
 
-The linker uses three special entry points in the BFD target vector.
-It is not necessary to write special routines for these entry points
-when creating a new BFD back end, since generic versions are provided.
-However, writing them can speed up linking and make it use
-significantly less runtime memory.
+The linker uses three special entry points in the BFD target vector.  It
+is not necessary to write special routines for these entry points when
+creating a new BFD back end, since generic versions are provided.
+However, writing them can speed up linking and make it use significantly
+less runtime memory.
 
    The first routine creates a hash table used by the other routines.
 The second routine adds the symbols from an object file to the hash
 table.  The third routine takes all the object files and links them
-together to create the output file.  These routines are designed so
-that the linker proper does not need to know anything about the symbols
-in the object files that it is linking.  The linker merely arranges the
+together to create the output file.  These routines are designed so that
+the linker proper does not need to know anything about the symbols in
+the object files that it is linking.  The linker merely arranges the
 sections as directed by the linker script and lets BFD handle the
 details of symbols and relocs.
 
    The second routine and third routines are passed a pointer to a
-`struct bfd_link_info' structure (defined in `bfdlink.h') which holds
-information relevant to the link, including the linker hash table
-(which was created by the first routine) and a set of callback
-functions to the linker proper.
-
-   The generic linker routines are in `linker.c', and use the header
-file `genlink.h'.  As of this writing, the only back ends which have
-implemented versions of these routines are a.out (in `aoutx.h') and
-ECOFF (in `ecoff.c').  The a.out routines are used as examples
+'struct bfd_link_info' structure (defined in 'bfdlink.h') which holds
+information relevant to the link, including the linker hash table (which
+was created by the first routine) and a set of callback functions to the
+linker proper.
+
+   The generic linker routines are in 'linker.c', and use the header
+file 'genlink.h'.  As of this writing, the only back ends which have
+implemented versions of these routines are a.out (in 'aoutx.h') and
+ECOFF (in 'ecoff.c').  The a.out routines are used as examples
 throughout this section.
 
 * Menu:
@@ -8554,26 +8195,26 @@ File: bfd.info,  Node: Creating a Linker Hash Table,  Next: Adding Symbols to th
 2.17.1 Creating a linker hash table
 -----------------------------------
 
-The linker routines must create a hash table, which must be derived
-from `struct bfd_link_hash_table' described in `bfdlink.c'.  *Note Hash
+The linker routines must create a hash table, which must be derived from
+'struct bfd_link_hash_table' described in 'bfdlink.c'.  *Note Hash
 Tables::, for information on how to create a derived hash table.  This
 entry point is called using the target vector of the linker output file.
 
-   The `_bfd_link_hash_table_create' entry point must allocate and
+   The '_bfd_link_hash_table_create' entry point must allocate and
 initialize an instance of the desired hash table.  If the back end does
 not require any additional information to be stored with the entries in
-the hash table, the entry point may simply create a `struct
-bfd_link_hash_table'.  Most likely, however, some additional
-information will be needed.
-
-   For example, with each entry in the hash table the a.out linker
-keeps the index the symbol has in the final output file (this index
-number is used so that when doing a relocatable link the symbol index
-used in the output file can be quickly filled in when copying over a
-reloc).  The a.out linker code defines the required structures and
-functions for a hash table derived from `struct bfd_link_hash_table'.
-The a.out linker hash table is created by the function
-`NAME(aout,link_hash_table_create)'; it simply allocates space for the
+the hash table, the entry point may simply create a 'struct
+bfd_link_hash_table'.  Most likely, however, some additional information
+will be needed.
+
+   For example, with each entry in the hash table the a.out linker keeps
+the index the symbol has in the final output file (this index number is
+used so that when doing a relocatable link the symbol index used in the
+output file can be quickly filled in when copying over a reloc).  The
+a.out linker code defines the required structures and functions for a
+hash table derived from 'struct bfd_link_hash_table'.  The a.out linker
+hash table is created by the function
+'NAME(aout,link_hash_table_create)'; it simply allocates space for the
 hash table, initializes it, and returns a pointer to it.
 
    When writing the linker routines for a new back end, you will
@@ -8587,7 +8228,7 @@ File: bfd.info,  Node: Adding Symbols to the Hash Table,  Next: Performing the F
 2.17.2 Adding symbols to the hash table
 ---------------------------------------
 
-The linker proper will call the `_bfd_link_add_symbols' entry point for
+The linker proper will call the '_bfd_link_add_symbols' entry point for
 each object file or archive which is to be linked (typically these are
 the files named on the command line, but some may also come from the
 linker script).  The entry point is responsible for examining the file.
@@ -8596,7 +8237,7 @@ hash table.  For an archive, BFD must determine which elements of the
 archive should be used and adding them to the link.
 
    The a.out version of this entry point is
-`NAME(aout,link_add_symbols)'.
+'NAME(aout,link_add_symbols)'.
 
 * Menu:
 
@@ -8612,29 +8253,29 @@ File: bfd.info,  Node: Differing file formats,  Next: Adding symbols from an obj
 
 Normally all the files involved in a link will be of the same format,
 but it is also possible to link together different format object files,
-and the back end must support that.  The `_bfd_link_add_symbols' entry
-point is called via the target vector of the file to be added.  This
-has an important consequence: the function may not assume that the hash
+and the back end must support that.  The '_bfd_link_add_symbols' entry
+point is called via the target vector of the file to be added.  This has
+an important consequence: the function may not assume that the hash
 table is the type created by the corresponding
-`_bfd_link_hash_table_create' vector.  All the `_bfd_link_add_symbols'
+'_bfd_link_hash_table_create' vector.  All the '_bfd_link_add_symbols'
 function can assume about the hash table is that it is derived from
-`struct bfd_link_hash_table'.
+'struct bfd_link_hash_table'.
 
-   Sometimes the `_bfd_link_add_symbols' function must store some
-information in the hash table entry to be used by the `_bfd_final_link'
+   Sometimes the '_bfd_link_add_symbols' function must store some
+information in the hash table entry to be used by the '_bfd_final_link'
 function.  In such a case the output bfd xvec must be checked to make
 sure that the hash table was created by an object file of the same
 format.
 
-   The `_bfd_final_link' routine must be prepared to handle a hash
-entry without any extra information added by the
-`_bfd_link_add_symbols' function.  A hash entry without extra
-information will also occur when the linker script directs the linker
-to create a symbol.  Note that, regardless of how a hash table entry is
-added, all the fields will be initialized to some sort of null value by
-the hash table entry initialization function.
+   The '_bfd_final_link' routine must be prepared to handle a hash entry
+without any extra information added by the '_bfd_link_add_symbols'
+function.  A hash entry without extra information will also occur when
+the linker script directs the linker to create a symbol.  Note that,
+regardless of how a hash table entry is added, all the fields will be
+initialized to some sort of null value by the hash table entry
+initialization function.
 
-   See `ecoff_link_add_externals' for an example of how to check the
+   See 'ecoff_link_add_externals' for an example of how to check the
 output bfd before saving information (in this case, the ECOFF external
 symbol debugging information) in a hash table entry.
 
@@ -8644,38 +8285,38 @@ File: bfd.info,  Node: Adding symbols from an object file,  Next: Adding symbols
 2.17.2.2 Adding symbols from an object file
 ...........................................
 
-When the `_bfd_link_add_symbols' routine is passed an object file, it
+When the '_bfd_link_add_symbols' routine is passed an object file, it
 must add all externally visible symbols in that object file to the hash
 table.  The actual work of adding the symbol to the hash table is
-normally handled by the function `_bfd_generic_link_add_one_symbol'.
-The `_bfd_link_add_symbols' routine is responsible for reading all the
+normally handled by the function '_bfd_generic_link_add_one_symbol'.
+The '_bfd_link_add_symbols' routine is responsible for reading all the
 symbols from the object file and passing the correct information to
-`_bfd_generic_link_add_one_symbol'.
+'_bfd_generic_link_add_one_symbol'.
 
-   The `_bfd_link_add_symbols' routine should not use
-`bfd_canonicalize_symtab' to read the symbols.  The point of providing
+   The '_bfd_link_add_symbols' routine should not use
+'bfd_canonicalize_symtab' to read the symbols.  The point of providing
 this routine is to avoid the overhead of converting the symbols into
-generic `asymbol' structures.
+generic 'asymbol' structures.
 
-   `_bfd_generic_link_add_one_symbol' handles the details of combining
+   '_bfd_generic_link_add_one_symbol' handles the details of combining
 common symbols, warning about multiple definitions, and so forth.  It
 takes arguments which describe the symbol to add, notably symbol flags,
 a section, and an offset.  The symbol flags include such things as
-`BSF_WEAK' or `BSF_INDIRECT'.  The section is a section in the object
-file, or something like `bfd_und_section_ptr' for an undefined symbol
-or `bfd_com_section_ptr' for a common symbol.
+'BSF_WEAK' or 'BSF_INDIRECT'.  The section is a section in the object
+file, or something like 'bfd_und_section_ptr' for an undefined symbol or
+'bfd_com_section_ptr' for a common symbol.
 
-   If the `_bfd_final_link' routine is also going to need to read the
-symbol information, the `_bfd_link_add_symbols' routine should save it
-somewhere attached to the object file BFD.  However, the information
-should only be saved if the `keep_memory' field of the `info' argument
-is TRUE, so that the `-no-keep-memory' linker switch is effective.
+   If the '_bfd_final_link' routine is also going to need to read the
+symbol information, the '_bfd_link_add_symbols' routine should save it
+somewhere attached to the object file BFD. However, the information
+should only be saved if the 'keep_memory' field of the 'info' argument
+is TRUE, so that the '-no-keep-memory' linker switch is effective.
 
    The a.out function which adds symbols from an object file is
-`aout_link_add_object_symbols', and most of the interesting work is in
-`aout_link_add_symbols'.  The latter saves pointers to the hash tables
-entries created by `_bfd_generic_link_add_one_symbol' indexed by symbol
-number, so that the `_bfd_final_link' routine does not have to call the
+'aout_link_add_object_symbols', and most of the interesting work is in
+'aout_link_add_symbols'.  The latter saves pointers to the hash tables
+entries created by '_bfd_generic_link_add_one_symbol' indexed by symbol
+number, so that the '_bfd_final_link' routine does not have to call the
 hash table lookup routine to locate the entry.
 
 
@@ -8684,50 +8325,50 @@ File: bfd.info,  Node: Adding symbols from an archive,  Prev: Adding symbols fro
 2.17.2.3 Adding symbols from an archive
 .......................................
 
-When the `_bfd_link_add_symbols' routine is passed an archive, it must
+When the '_bfd_link_add_symbols' routine is passed an archive, it must
 look through the symbols defined by the archive and decide which
 elements of the archive should be included in the link.  For each such
-element it must call the `add_archive_element' linker callback, and it
+element it must call the 'add_archive_element' linker callback, and it
 must add the symbols from the object file to the linker hash table.
 (The callback may in fact indicate that a replacement BFD should be
 used, in which case the symbols from that BFD should be added to the
 linker hash table instead.)
 
    In most cases the work of looking through the symbols in the archive
-should be done by the `_bfd_generic_link_add_archive_symbols' function.
+should be done by the '_bfd_generic_link_add_archive_symbols' function.
 This function builds a hash table from the archive symbol table and
-looks through the list of undefined symbols to see which elements
-should be included.  `_bfd_generic_link_add_archive_symbols' is passed
-a function to call to make the final decision about adding an archive
+looks through the list of undefined symbols to see which elements should
+be included.  '_bfd_generic_link_add_archive_symbols' is passed a
+function to call to make the final decision about adding an archive
 element to the link and to do the actual work of adding the symbols to
 the linker hash table.
 
-   The function passed to `_bfd_generic_link_add_archive_symbols' must
+   The function passed to '_bfd_generic_link_add_archive_symbols' must
 read the symbols of the archive element and decide whether the archive
 element should be included in the link.  If the element is to be
-included, the `add_archive_element' linker callback routine must be
+included, the 'add_archive_element' linker callback routine must be
 called with the element as an argument, and the element's symbols must
 be added to the linker hash table just as though the element had itself
-been passed to the `_bfd_link_add_symbols' function.  The
-`add_archive_element' callback has the option to indicate that it would
-like to replace the element archive with a substitute BFD, in which
-case it is the symbols of that substitute BFD that must be added to the
+been passed to the '_bfd_link_add_symbols' function.  The
+'add_archive_element' callback has the option to indicate that it would
+like to replace the element archive with a substitute BFD, in which case
+it is the symbols of that substitute BFD that must be added to the
 linker hash table instead.
 
-   When the a.out `_bfd_link_add_symbols' function receives an archive,
-it calls `_bfd_generic_link_add_archive_symbols' passing
-`aout_link_check_archive_element' as the function argument.
-`aout_link_check_archive_element' calls `aout_link_check_ar_symbols'.
-If the latter decides to add the element (an element is only added if
-it provides a real, non-common, definition for a previously undefined
-or common symbol) it calls the `add_archive_element' callback and then
-`aout_link_check_archive_element' calls `aout_link_add_symbols' to
+   When the a.out '_bfd_link_add_symbols' function receives an archive,
+it calls '_bfd_generic_link_add_archive_symbols' passing
+'aout_link_check_archive_element' as the function argument.
+'aout_link_check_archive_element' calls 'aout_link_check_ar_symbols'.
+If the latter decides to add the element (an element is only added if it
+provides a real, non-common, definition for a previously undefined or
+common symbol) it calls the 'add_archive_element' callback and then
+'aout_link_check_archive_element' calls 'aout_link_add_symbols' to
 actually add the symbols to the linker hash table - possibly those of a
-substitute BFD, if the `add_archive_element' callback avails itself of
+substitute BFD, if the 'add_archive_element' callback avails itself of
 that option.
 
    The ECOFF back end is unusual in that it does not normally call
-`_bfd_generic_link_add_archive_symbols', because ECOFF archives already
+'_bfd_generic_link_add_archive_symbols', because ECOFF archives already
 contain a hash table of symbols.  The ECOFF back end searches the
 archive itself to avoid the overhead of creating a new hash table.
 
@@ -8738,22 +8379,22 @@ File: bfd.info,  Node: Performing the Final Link,  Prev: Adding Symbols to the H
 --------------------------------
 
 When all the input files have been processed, the linker calls the
-`_bfd_final_link' entry point of the output BFD.  This routine is
+'_bfd_final_link' entry point of the output BFD. This routine is
 responsible for producing the final output file, which has several
 aspects.  It must relocate the contents of the input sections and copy
-the data into the output sections.  It must build an output symbol
-table including any local symbols from the input files and the global
-symbols from the hash table.  When producing relocatable output, it must
-modify the input relocs and write them into the output file.  There may
-also be object format dependent work to be done.
+the data into the output sections.  It must build an output symbol table
+including any local symbols from the input files and the global symbols
+from the hash table.  When producing relocatable output, it must modify
+the input relocs and write them into the output file.  There may also be
+object format dependent work to be done.
 
-   The linker will also call the `write_object_contents' entry point
+   The linker will also call the 'write_object_contents' entry point
 when the BFD is closed.  The two entry points must work together in
 order to produce the correct output file.
 
    The details of how this works are inevitably dependent upon the
-specific object file format.  The a.out `_bfd_final_link' routine is
-`NAME(aout,final_link)'.
+specific object file format.  The a.out '_bfd_final_link' routine is
+'NAME(aout,final_link)'.
 
 * Menu:
 
@@ -8767,22 +8408,22 @@ File: bfd.info,  Node: Information provided by the linker,  Next: Relocating the
 2.17.3.1 Information provided by the linker
 ...........................................
 
-Before the linker calls the `_bfd_final_link' entry point, it sets up
+Before the linker calls the '_bfd_final_link' entry point, it sets up
 some data structures for the function to use.
 
-   The `input_bfds' field of the `bfd_link_info' structure will point
-to a list of all the input files included in the link.  These files are
-linked through the `link_next' field of the `bfd' structure.
-
-   Each section in the output file will have a list of `link_order'
-structures attached to the `map_head.link_order' field (the
-`link_order' structure is defined in `bfdlink.h').  These structures
-describe how to create the contents of the output section in terms of
-the contents of various input sections, fill constants, and,
-eventually, other types of information.  They also describe relocs that
-must be created by the BFD backend, but do not correspond to any input
-file; this is used to support -Ur, which builds constructors while
-generating a relocatable object file.
+   The 'input_bfds' field of the 'bfd_link_info' structure will point to
+a list of all the input files included in the link.  These files are
+linked through the 'link_next' field of the 'bfd' structure.
+
+   Each section in the output file will have a list of 'link_order'
+structures attached to the 'map_head.link_order' field (the 'link_order'
+structure is defined in 'bfdlink.h').  These structures describe how to
+create the contents of the output section in terms of the contents of
+various input sections, fill constants, and, eventually, other types of
+information.  They also describe relocs that must be created by the BFD
+backend, but do not correspond to any input file; this is used to
+support -Ur, which builds constructors while generating a relocatable
+object file.
 
 
 File: bfd.info,  Node: Relocating the section contents,  Next: Writing the symbol table,  Prev: Information provided by the linker,  Up: Performing the Final Link
@@ -8790,33 +8431,32 @@ File: bfd.info,  Node: Relocating the section contents,  Next: Writing the symbo
 2.17.3.2 Relocating the section contents
 ........................................
 
-The `_bfd_final_link' function should look through the `link_order'
+The '_bfd_final_link' function should look through the 'link_order'
 structures attached to each section of the output file.  Each
-`link_order' structure should either be handled specially, or it should
-be passed to the function `_bfd_default_link_order' which will do the
-right thing (`_bfd_default_link_order' is defined in `linker.c').
+'link_order' structure should either be handled specially, or it should
+be passed to the function '_bfd_default_link_order' which will do the
+right thing ('_bfd_default_link_order' is defined in 'linker.c').
 
-   For efficiency, a `link_order' of type `bfd_indirect_link_order'
+   For efficiency, a 'link_order' of type 'bfd_indirect_link_order'
 whose associated section belongs to a BFD of the same format as the
-output BFD must be handled specially.  This type of `link_order'
+output BFD must be handled specially.  This type of 'link_order'
 describes part of an output section in terms of a section belonging to
-one of the input files.  The `_bfd_final_link' function should read the
+one of the input files.  The '_bfd_final_link' function should read the
 contents of the section and any associated relocs, apply the relocs to
 the section contents, and write out the modified section contents.  If
 performing a relocatable link, the relocs themselves must also be
 modified and written out.
 
-   The functions `_bfd_relocate_contents' and
-`_bfd_final_link_relocate' provide some general support for performing
-the actual relocations, notably overflow checking.  Their arguments
-include information about the symbol the relocation is against and a
-`reloc_howto_type' argument which describes the relocation to perform.
-These functions are defined in `reloc.c'.
+   The functions '_bfd_relocate_contents' and '_bfd_final_link_relocate'
+provide some general support for performing the actual relocations,
+notably overflow checking.  Their arguments include information about
+the symbol the relocation is against and a 'reloc_howto_type' argument
+which describes the relocation to perform.  These functions are defined
+in 'reloc.c'.
 
    The a.out function which handles reading, relocating, and writing
-section contents is `aout_link_input_section'.  The actual relocation
-is done in `aout_link_input_section_std' and
-`aout_link_input_section_ext'.
+section contents is 'aout_link_input_section'.  The actual relocation is
+done in 'aout_link_input_section_std' and 'aout_link_input_section_ext'.
 
 
 File: bfd.info,  Node: Writing the symbol table,  Prev: Relocating the section contents,  Up: Performing the Final Link
@@ -8824,45 +8464,45 @@ File: bfd.info,  Node: Writing the symbol table,  Prev: Relocating the section c
 2.17.3.3 Writing the symbol table
 .................................
 
-The `_bfd_final_link' function must gather all the symbols in the input
-files and write them out.  It must also write out all the symbols in
-the global hash table.  This must be controlled by the `strip' and
-`discard' fields of the `bfd_link_info' structure.
+The '_bfd_final_link' function must gather all the symbols in the input
+files and write them out.  It must also write out all the symbols in the
+global hash table.  This must be controlled by the 'strip' and 'discard'
+fields of the 'bfd_link_info' structure.
 
    The local symbols of the input files will not have been entered into
-the linker hash table.  The `_bfd_final_link' routine must consider
-each input file and include the symbols in the output file.  It may be
-convenient to do this when looking through the `link_order' structures,
-or it may be done by stepping through the `input_bfds' list.
-
-   The `_bfd_final_link' routine must also traverse the global hash
-table to gather all the externally visible symbols.  It is possible
-that most of the externally visible symbols may be written out when
-considering the symbols of each input file, but it is still necessary
-to traverse the hash table since the linker script may have defined
-some symbols that are not in any of the input files.
-
-   The `strip' field of the `bfd_link_info' structure controls which
-symbols are written out.  The possible values are listed in
-`bfdlink.h'.  If the value is `strip_some', then the `keep_hash' field
-of the `bfd_link_info' structure is a hash table of symbols to keep;
-each symbol should be looked up in this hash table, and only symbols
-which are present should be included in the output file.
-
-   If the `strip' field of the `bfd_link_info' structure permits local
-symbols to be written out, the `discard' field is used to further
+the linker hash table.  The '_bfd_final_link' routine must consider each
+input file and include the symbols in the output file.  It may be
+convenient to do this when looking through the 'link_order' structures,
+or it may be done by stepping through the 'input_bfds' list.
+
+   The '_bfd_final_link' routine must also traverse the global hash
+table to gather all the externally visible symbols.  It is possible that
+most of the externally visible symbols may be written out when
+considering the symbols of each input file, but it is still necessary to
+traverse the hash table since the linker script may have defined some
+symbols that are not in any of the input files.
+
+   The 'strip' field of the 'bfd_link_info' structure controls which
+symbols are written out.  The possible values are listed in 'bfdlink.h'.
+If the value is 'strip_some', then the 'keep_hash' field of the
+'bfd_link_info' structure is a hash table of symbols to keep; each
+symbol should be looked up in this hash table, and only symbols which
+are present should be included in the output file.
+
+   If the 'strip' field of the 'bfd_link_info' structure permits local
+symbols to be written out, the 'discard' field is used to further
 controls which local symbols are included in the output file.  If the
-value is `discard_l', then all local symbols which begin with a certain
+value is 'discard_l', then all local symbols which begin with a certain
 prefix are discarded; this is controlled by the
-`bfd_is_local_label_name' entry point.
+'bfd_is_local_label_name' entry point.
 
    The a.out backend handles symbols by calling
-`aout_link_write_symbols' on each input BFD and then traversing the
-global hash table with the function `aout_link_write_other_symbol'.  It
-builds a string table while writing out the symbols, which is written
-to the output file at the end of `NAME(aout,final_link)'.
+'aout_link_write_symbols' on each input BFD and then traversing the
+global hash table with the function 'aout_link_write_other_symbol'.  It
+builds a string table while writing out the symbols, which is written to
+the output file at the end of 'NAME(aout,final_link)'.
 
-2.17.3.4 `bfd_link_split_section'
+2.17.3.4 'bfd_link_split_section'
 .................................
 
 *Synopsis*
@@ -8873,7 +8513,7 @@ link.
      #define bfd_link_split_section(abfd, sec) \
             BFD_SEND (abfd, _bfd_link_split_section, (abfd, sec))
 
-2.17.3.5 `bfd_section_already_linked'
+2.17.3.5 'bfd_section_already_linked'
 .....................................
 
 *Synopsis*
@@ -8886,7 +8526,7 @@ link.  Return TRUE if it has.
      #define bfd_section_already_linked(abfd, sec, info) \
             BFD_SEND (abfd, _section_already_linked, (abfd, sec, info))
 
-2.17.3.6 `bfd_generic_define_common_symbol'
+2.17.3.6 'bfd_generic_define_common_symbol'
 ...........................................
 
 *Synopsis*
@@ -8899,7 +8539,7 @@ and FALSE on failure.
      #define bfd_define_common_symbol(output_bfd, info, h) \
             BFD_SEND (output_bfd, _bfd_define_common_symbol, (output_bfd, info, h))
 
-2.17.3.7 `bfd_find_version_for_sym'
+2.17.3.7 'bfd_find_version_for_sym'
 ...................................
 
 *Synopsis*
@@ -8909,17 +8549,17 @@ and FALSE on failure.
    *Description*
 Search an elf version script tree for symbol versioning info and export
 / don't-export status for a given symbol.  Return non-NULL on success
-and NULL on failure; also sets the output `hide' boolean parameter.
+and NULL on failure; also sets the output 'hide' boolean parameter.
 
-2.17.3.8 `bfd_hide_sym_by_version'
+2.17.3.8 'bfd_hide_sym_by_version'
 ..................................
 
 *Synopsis*
      bfd_boolean bfd_hide_sym_by_version
         (struct bfd_elf_version_tree *verdefs, const char *sym_name);
    *Description*
-Search an elf version script tree for symbol versioning info for a
-given symbol.  Return TRUE if the symbol is hidden.
+Search an elf version script tree for symbol versioning info for a given
+symbol.  Return TRUE if the symbol is hidden.
 
 
 File: bfd.info,  Node: Hash Tables,  Prev: Linker Functions,  Up: BFD front end
@@ -8943,7 +8583,7 @@ back ends.  The linker may create thousands of hash table entries, and
 the overhead of allocating private data and storing and following
 pointers becomes noticeable.
 
-   The basic hash table code is in `hash.c'.
+   The basic hash table code is in 'hash.c'.
 
 * Menu:
 
@@ -8958,27 +8598,27 @@ File: bfd.info,  Node: Creating and Freeing a Hash Table,  Next: Looking Up or E
 2.18.1 Creating and freeing a hash table
 ----------------------------------------
 
-To create a hash table, create an instance of a `struct bfd_hash_table'
-(defined in `bfd.h') and call `bfd_hash_table_init' (if you know
+To create a hash table, create an instance of a 'struct bfd_hash_table'
+(defined in 'bfd.h') and call 'bfd_hash_table_init' (if you know
 approximately how many entries you will need, the function
-`bfd_hash_table_init_n', which takes a SIZE argument, may be used).
-`bfd_hash_table_init' returns `FALSE' if some sort of error occurs.
+'bfd_hash_table_init_n', which takes a SIZE argument, may be used).
+'bfd_hash_table_init' returns 'FALSE' if some sort of error occurs.
 
-   The function `bfd_hash_table_init' take as an argument a function to
+   The function 'bfd_hash_table_init' take as an argument a function to
 use to create new entries.  For a basic hash table, use the function
-`bfd_hash_newfunc'.  *Note Deriving a New Hash Table Type::, for why
-you would want to use a different value for this argument.
+'bfd_hash_newfunc'.  *Note Deriving a New Hash Table Type::, for why you
+would want to use a different value for this argument.
 
-   `bfd_hash_table_init' will create an objalloc which will be used to
+   'bfd_hash_table_init' will create an objalloc which will be used to
 allocate new entries.  You may allocate memory on this objalloc using
-`bfd_hash_allocate'.
+'bfd_hash_allocate'.
 
-   Use `bfd_hash_table_free' to free up all the memory that has been
-allocated for a hash table.  This will not free up the `struct
+   Use 'bfd_hash_table_free' to free up all the memory that has been
+allocated for a hash table.  This will not free up the 'struct
 bfd_hash_table' itself, which you must provide.
 
-   Use `bfd_hash_set_default_size' to set the default size of hash
-table to use.
+   Use 'bfd_hash_set_default_size' to set the default size of hash table
+to use.
 
 
 File: bfd.info,  Node: Looking Up or Entering a String,  Next: Traversing a Hash Table,  Prev: Creating and Freeing a Hash Table,  Up: Hash Tables
@@ -8986,24 +8626,24 @@ File: bfd.info,  Node: Looking Up or Entering a String,  Next: Traversing a Hash
 2.18.2 Looking up or entering a string
 --------------------------------------
 
-The function `bfd_hash_lookup' is used both to look up a string in the
+The function 'bfd_hash_lookup' is used both to look up a string in the
 hash table and to create a new entry.
 
-   If the CREATE argument is `FALSE', `bfd_hash_lookup' will look up a
-string.  If the string is found, it will returns a pointer to a `struct
+   If the CREATE argument is 'FALSE', 'bfd_hash_lookup' will look up a
+string.  If the string is found, it will returns a pointer to a 'struct
 bfd_hash_entry'.  If the string is not found in the table
-`bfd_hash_lookup' will return `NULL'.  You should not modify any of the
-fields in the returns `struct bfd_hash_entry'.
+'bfd_hash_lookup' will return 'NULL'.  You should not modify any of the
+fields in the returns 'struct bfd_hash_entry'.
 
-   If the CREATE argument is `TRUE', the string will be entered into
-the hash table if it is not already there.  Either way a pointer to a
-`struct bfd_hash_entry' will be returned, either to the existing
-structure or to a newly created one.  In this case, a `NULL' return
+   If the CREATE argument is 'TRUE', the string will be entered into the
+hash table if it is not already there.  Either way a pointer to a
+'struct bfd_hash_entry' will be returned, either to the existing
+structure or to a newly created one.  In this case, a 'NULL' return
 means that an error occurred.
 
-   If the CREATE argument is `TRUE', and a new entry is created, the
-COPY argument is used to decide whether to copy the string onto the
-hash table objalloc or not.  If COPY is passed as `FALSE', you must be
+   If the CREATE argument is 'TRUE', and a new entry is created, the
+COPY argument is used to decide whether to copy the string onto the hash
+table objalloc or not.  If COPY is passed as 'FALSE', you must be
 careful not to deallocate or modify the string as long as the hash table
 exists.
 
@@ -9013,16 +8653,16 @@ File: bfd.info,  Node: Traversing a Hash Table,  Next: Deriving a New Hash Table
 2.18.3 Traversing a hash table
 ------------------------------
 
-The function `bfd_hash_traverse' may be used to traverse a hash table,
+The function 'bfd_hash_traverse' may be used to traverse a hash table,
 calling a function on each element.  The traversal is done in a random
 order.
 
-   `bfd_hash_traverse' takes as arguments a function and a generic
-`void *' pointer.  The function is called with a hash table entry (a
-`struct bfd_hash_entry *') and the generic pointer passed to
-`bfd_hash_traverse'.  The function must return a `boolean' value, which
+   'bfd_hash_traverse' takes as arguments a function and a generic 'void
+*' pointer.  The function is called with a hash table entry (a 'struct
+bfd_hash_entry *') and the generic pointer passed to
+'bfd_hash_traverse'.  The function must return a 'boolean' value, which
 indicates whether to continue traversing the hash table.  If the
-function returns `FALSE', `bfd_hash_traverse' will stop the traversal
+function returns 'FALSE', 'bfd_hash_traverse' will stop the traversal
 and return immediately.
 
 
@@ -9031,8 +8671,8 @@ File: bfd.info,  Node: Deriving a New Hash Table Type,  Prev: Traversing a Hash
 2.18.4 Deriving a new hash table type
 -------------------------------------
 
-Many uses of hash tables want to store additional information which
-each entry in the hash table.  Some also find it convenient to store
+Many uses of hash tables want to store additional information which each
+entry in the hash table.  Some also find it convenient to store
 additional information with the hash table itself.  This may be done
 using a derived hash table.
 
@@ -9041,8 +8681,8 @@ table requires sticking together some boilerplate routines with a few
 differences specific to the type of hash table you want to create.
 
    An example of a derived hash table is the linker hash table.  The
-structures for this are defined in `bfdlink.h'.  The functions are in
-`linker.c'.
+structures for this are defined in 'bfdlink.h'.  The functions are in
+'linker.c'.
 
    You may also derive a hash table from an already derived hash table.
 For example, the a.out linker backend code uses a hash table derived
@@ -9065,16 +8705,16 @@ structure for the hash table itself.
 
    The first field in the structure for an entry in the hash table must
 be of the type used for an entry in the hash table you are deriving
-from.  If you are deriving from a basic hash table this is `struct
-bfd_hash_entry', which is defined in `bfd.h'.  The first field in the
+from.  If you are deriving from a basic hash table this is 'struct
+bfd_hash_entry', which is defined in 'bfd.h'.  The first field in the
 structure for the hash table itself must be of the type of the hash
 table you are deriving from itself.  If you are deriving from a basic
-hash table, this is `struct bfd_hash_table'.
+hash table, this is 'struct bfd_hash_table'.
 
-   For example, the linker hash table defines `struct
-bfd_link_hash_entry' (in `bfdlink.h').  The first field, `root', is of
-type `struct bfd_hash_entry'.  Similarly, the first field in `struct
-bfd_link_hash_table', `table', is of type `struct bfd_hash_table'.
+   For example, the linker hash table defines 'struct
+bfd_link_hash_entry' (in 'bfdlink.h').  The first field, 'root', is of
+type 'struct bfd_hash_entry'.  Similarly, the first field in 'struct
+bfd_link_hash_table', 'table', is of type 'struct bfd_hash_table'.
 
 
 File: bfd.info,  Node: Write the Derived Creation Routine,  Next: Write Other Derived Routines,  Prev: Define the Derived Structures,  Up: Deriving a New Hash Table Type
@@ -9084,23 +8724,23 @@ File: bfd.info,  Node: Write the Derived Creation Routine,  Next: Write Other De
 
 You must write a routine which will create and initialize an entry in
 the hash table.  This routine is passed as the function argument to
-`bfd_hash_table_init'.
+'bfd_hash_table_init'.
 
    In order to permit other hash tables to be derived from the hash
 table you are creating, this routine must be written in a standard way.
 
    The first argument to the creation routine is a pointer to a hash
-table entry.  This may be `NULL', in which case the routine should
+table entry.  This may be 'NULL', in which case the routine should
 allocate the right amount of space.  Otherwise the space has already
 been allocated by a hash table type derived from this one.
 
    After allocating space, the creation routine must call the creation
 routine of the hash table type it is derived from, passing in a pointer
-to the space it just allocated.  This will initialize any fields used
-by the base hash table.
+to the space it just allocated.  This will initialize any fields used by
+the base hash table.
 
-   Finally the creation routine must initialize any local fields for
-the new hash table type.
+   Finally the creation routine must initialize any local fields for the
+new hash table type.
 
    Here is a boilerplate example of a creation routine.  FUNCTION_NAME
 is the name of the routine.  ENTRY_TYPE is the type of an entry in the
@@ -9132,14 +8772,14 @@ routine of the hash table type your hash table is derived from.
        return (struct bfd_hash_entry *) ret;
      }
    *Description*
-The creation routine for the linker hash table, which is in `linker.c',
+The creation routine for the linker hash table, which is in 'linker.c',
 looks just like this example.  FUNCTION_NAME is
-`_bfd_link_hash_newfunc'.  ENTRY_TYPE is `struct bfd_link_hash_entry'.
-BASE_NEWFUNC is `bfd_hash_newfunc', the creation routine for a basic
+'_bfd_link_hash_newfunc'.  ENTRY_TYPE is 'struct bfd_link_hash_entry'.
+BASE_NEWFUNC is 'bfd_hash_newfunc', the creation routine for a basic
 hash table.
 
-   `_bfd_link_hash_newfunc' also initializes the local fields in a
-linker hash table entry: `type', `written' and `next'.
+   '_bfd_link_hash_newfunc' also initializes the local fields in a
+linker hash table entry: 'type', 'written' and 'next'.
 
 
 File: bfd.info,  Node: Write Other Derived Routines,  Prev: Write the Derived Creation Routine,  Up: Deriving a New Hash Table Type
@@ -9152,23 +8792,23 @@ You will want to write other routines for your new hash table, as well.
    You will want an initialization routine which calls the
 initialization routine of the hash table you are deriving from and
 initializes any other local fields.  For the linker hash table, this is
-`_bfd_link_hash_table_init' in `linker.c'.
+'_bfd_link_hash_table_init' in 'linker.c'.
 
    You will want a lookup routine which calls the lookup routine of the
 hash table you are deriving from and casts the result.  The linker hash
-table uses `bfd_link_hash_lookup' in `linker.c' (this actually takes an
+table uses 'bfd_link_hash_lookup' in 'linker.c' (this actually takes an
 additional argument which it uses to decide how to return the looked up
 value).
 
    You may want a traversal routine.  This should just call the
 traversal routine of the hash table you are deriving from with
-appropriate casts.  The linker hash table uses `bfd_link_hash_traverse'
-in `linker.c'.
+appropriate casts.  The linker hash table uses 'bfd_link_hash_traverse'
+in 'linker.c'.
 
    These routines may simply be defined as macros.  For example, the
 a.out backend linker hash table, which is derived from the linker hash
 table, uses macros for the lookup and traversal routines.  These are
-`aout_link_hash_lookup' and `aout_link_hash_traverse' in aoutx.h.
+'aout_link_hash_lookup' and 'aout_link_hash_traverse' in aoutx.h.
 
 
 File: bfd.info,  Node: BFD back ends,  Next: GNU Free Documentation License,  Prev: BFD front end,  Up: Top
@@ -9203,24 +8843,23 @@ BFD supports a number of different flavours of a.out format, though the
 major differences are only the sizes of the structures on disk, and the
 shape of the relocation information.
 
-   The support is split into a basic support file `aoutx.h' and other
-files which derive functions from the base. One derivation file is
-`aoutf1.h' (for a.out flavour 1), and adds to the basic a.out functions
-support for sun3, sun4, 386 and 29k a.out files, to create a target
-jump vector for a specific target.
+   The support is split into a basic support file 'aoutx.h' and other
+files which derive functions from the base.  One derivation file is
+'aoutf1.h' (for a.out flavour 1), and adds to the basic a.out functions
+support for sun3, sun4, 386 and 29k a.out files, to create a target jump
+vector for a specific target.
 
    This information is further split out into more specific files for
-each machine, including `sunos.c' for sun3 and sun4, `newsos3.c' for
-the Sony NEWS, and `demo64.c' for a demonstration of a 64 bit a.out
-format.
+each machine, including 'sunos.c' for sun3 and sun4, 'newsos3.c' for the
+Sony NEWS, and 'demo64.c' for a demonstration of a 64 bit a.out format.
 
-   The base file `aoutx.h' defines general mechanisms for reading and
+   The base file 'aoutx.h' defines general mechanisms for reading and
 writing records to and from disk and various other methods which BFD
-requires. It is included by `aout32.c' and `aout64.c' to form the names
-`aout_32_swap_exec_header_in', `aout_64_swap_exec_header_in', etc.
+requires.  It is included by 'aout32.c' and 'aout64.c' to form the names
+'aout_32_swap_exec_header_in', 'aout_64_swap_exec_header_in', etc.
 
    As an example, this is what goes on to make the back end for a sun4,
-from `aout32.c':
+from 'aout32.c':
 
             #define ARCH_SIZE 32
             #include "aoutx.h"
@@ -9234,24 +8873,24 @@ from `aout32.c':
             aout_32_get_reloc_upper_bound
             ...
 
-   from `sunos.c':
+   from 'sunos.c':
 
             #define TARGET_NAME "a.out-sunos-big"
             #define VECNAME    sunos_big_vec
             #include "aoutf1.h"
 
-   requires all the names from `aout32.c', and produces the jump vector
+   requires all the names from 'aout32.c', and produces the jump vector
 
             sunos_big_vec
 
-   The file `host-aout.c' is a special case.  It is for a large set of
+   The file 'host-aout.c' is a special case.  It is for a large set of
 hosts that use "more or less standard" a.out files, and for which
 cross-debugging is not interesting.  It uses the standard 32-bit a.out
 support routines, but determines the file offsets and addresses of the
-text, data, and BSS sections, the machine architecture and machine
-type, and the entry point address, in a host-dependent manner.  Once
-these values have been determined, generic code is used to handle the
-object file.
+text, data, and BSS sections, the machine architecture and machine type,
+and the entry point address, in a host-dependent manner.  Once these
+values have been determined, generic code is used to handle the object
+file.
 
    When porting it to run on a new system, you must supply:
 
@@ -9262,38 +8901,38 @@ object file.
              HOST_TEXT_START_ADDR
              HOST_STACK_END_ADDR
 
-   in the file `../include/sys/h-XXX.h' (for your host).  These values,
-plus the structures and macros defined in `a.out.h' on your host
-system, will produce a BFD target that will access ordinary a.out files
-on your host. To configure a new machine to use `host-aout.c', specify:
+   in the file '../include/sys/h-XXX.h' (for your host).  These values,
+plus the structures and macros defined in 'a.out.h' on your host system,
+will produce a BFD target that will access ordinary a.out files on your
+host.  To configure a new machine to use 'host-aout.c', specify:
 
             TDEFAULTS = -DDEFAULT_VECTOR=host_aout_big_vec
             TDEPFILES= host-aout.o trad-core.o
 
-   in the `config/XXX.mt' file, and modify `configure.in' to use the
-`XXX.mt' file (by setting "`bfd_target=XXX'") when your configuration
-is selected.
+   in the 'config/XXX.mt' file, and modify 'configure.in' to use the
+'XXX.mt' file (by setting "'bfd_target=XXX'") when your configuration is
+selected.
 
 3.2.1 Relocations
 -----------------
 
 *Description*
-The file `aoutx.h' provides for both the _standard_ and _extended_
-forms of a.out relocation records.
+The file 'aoutx.h' provides for both the _standard_ and _extended_ forms
+of a.out relocation records.
 
    The standard records contain only an address, a symbol index, and a
-type field. The extended records (used on 29ks and sparcs) also have a
+type field.  The extended records (used on 29ks and sparcs) also have a
 full integer for an addend.
 
 3.2.2 Internal entry points
 ---------------------------
 
 *Description*
-`aoutx.h' exports several routines for accessing the contents of an
+'aoutx.h' exports several routines for accessing the contents of an
 a.out file, which are gathered and exported in turn by various format
 specific files (eg sunos.c).
 
-3.2.2.1 `aout_SIZE_swap_exec_header_in'
+3.2.2.1 'aout_SIZE_swap_exec_header_in'
 .......................................
 
 *Synopsis*
@@ -9305,7 +8944,7 @@ specific files (eg sunos.c).
 Swap the information in an executable header RAW_BYTES taken from a raw
 byte stream memory image into the internal exec header structure EXECP.
 
-3.2.2.2 `aout_SIZE_swap_exec_header_out'
+3.2.2.2 'aout_SIZE_swap_exec_header_out'
 ........................................
 
 *Synopsis*
@@ -9314,10 +8953,10 @@ byte stream memory image into the internal exec header structure EXECP.
          struct internal_exec *execp,
          struct external_exec *raw_bytes);
    *Description*
-Swap the information in an internal exec header structure EXECP into
-the buffer RAW_BYTES ready for writing to disk.
+Swap the information in an internal exec header structure EXECP into the
+buffer RAW_BYTES ready for writing to disk.
 
-3.2.2.3 `aout_SIZE_some_aout_object_p'
+3.2.2.3 'aout_SIZE_some_aout_object_p'
 ......................................
 
 *Synopsis*
@@ -9331,7 +8970,7 @@ a.out file.  Do some more checking, and set up for access if it really
 is.  Call back to the calling environment's "finish up" function just
 before returning, to handle any last-minute setup.
 
-3.2.2.4 `aout_SIZE_mkobject'
+3.2.2.4 'aout_SIZE_mkobject'
 ............................
 
 *Synopsis*
@@ -9339,7 +8978,7 @@ before returning, to handle any last-minute setup.
    *Description*
 Initialize BFD ABFD for use with a.out files.
 
-3.2.2.5 `aout_SIZE_machine_type'
+3.2.2.5 'aout_SIZE_machine_type'
 ................................
 
 *Synopsis*
@@ -9348,15 +8987,15 @@ Initialize BFD ABFD for use with a.out files.
          unsigned long machine,
          bfd_boolean *unknown);
    *Description*
-Keep track of machine architecture and machine type for a.out's. Return
-the `machine_type' for a particular architecture and machine, or
-`M_UNKNOWN' if that exact architecture and machine can't be represented
+Keep track of machine architecture and machine type for a.out's.  Return
+the 'machine_type' for a particular architecture and machine, or
+'M_UNKNOWN' if that exact architecture and machine can't be represented
 in a.out format.
 
-   If the architecture is understood, machine type 0 (default) is
-always understood.
+   If the architecture is understood, machine type 0 (default) is always
+understood.
 
-3.2.2.6 `aout_SIZE_set_arch_mach'
+3.2.2.6 'aout_SIZE_set_arch_mach'
 .................................
 
 *Synopsis*
@@ -9369,7 +9008,7 @@ Set the architecture and the machine of the BFD ABFD to the values ARCH
 and MACHINE.  Verify that ABFD's format can support the architecture
 required.
 
-3.2.2.7 `aout_SIZE_new_section_hook'
+3.2.2.7 'aout_SIZE_new_section_hook'
 ....................................
 
 *Synopsis*
@@ -9377,7 +9016,7 @@ required.
         (bfd *abfd,
          asection *newsect);
    *Description*
-Called by the BFD in response to a `bfd_make_section' request.
+Called by the BFD in response to a 'bfd_make_section' request.
 
 
 File: bfd.info,  Node: coff,  Next: elf,  Prev: aout,  Up: BFD back ends
@@ -9390,16 +9029,16 @@ differences between formats are the sizes and alignments of fields in
 structures on disk, and the occasional extra field.
 
    Coff in all its varieties is implemented with a few common files and
-a number of implementation specific files. For example, The 88k bcs
-coff format is implemented in the file `coff-m88k.c'. This file
-`#include's `coff/m88k.h' which defines the external structure of the
-coff format for the 88k, and `coff/internal.h' which defines the
-internal structure. `coff-m88k.c' also defines the relocations used by
+a number of implementation specific files.  For example, The 88k bcs
+coff format is implemented in the file 'coff-m88k.c'.  This file
+'#include's 'coff/m88k.h' which defines the external structure of the
+coff format for the 88k, and 'coff/internal.h' which defines the
+internal structure.  'coff-m88k.c' also defines the relocations used by
 the 88k format *Note Relocations::.
 
    The Intel i960 processor version of coff is implemented in
-`coff-i960.c'. This file has the same structure as `coff-m88k.c',
-except that it includes `coff/i960.h' rather than `coff-m88k.h'.
+'coff-i960.c'.  This file has the same structure as 'coff-m88k.c',
+except that it includes 'coff/i960.h' rather than 'coff-m88k.h'.
 
 3.3.1 Porting to a new version of coff
 --------------------------------------
@@ -9407,20 +9046,20 @@ except that it includes `coff/i960.h' rather than `coff-m88k.h'.
 The recommended method is to select from the existing implementations
 the version of coff which is most like the one you want to use.  For
 example, we'll say that i386 coff is the one you select, and that your
-coff flavour is called foo.  Copy `i386coff.c' to `foocoff.c', copy
-`../include/coff/i386.h' to `../include/coff/foo.h', and add the lines
-to `targets.c' and `Makefile.in' so that your new back end is used.
-Alter the shapes of the structures in `../include/coff/foo.h' so that
-they match what you need. You will probably also have to add `#ifdef's
-to the code in `coff/internal.h' and `coffcode.h' if your version of
+coff flavour is called foo.  Copy 'i386coff.c' to 'foocoff.c', copy
+'../include/coff/i386.h' to '../include/coff/foo.h', and add the lines
+to 'targets.c' and 'Makefile.in' so that your new back end is used.
+Alter the shapes of the structures in '../include/coff/foo.h' so that
+they match what you need.  You will probably also have to add '#ifdef's
+to the code in 'coff/internal.h' and 'coffcode.h' if your version of
 coff is too wild.
 
    You can verify that your new BFD backend works quite simply by
-building `objdump' from the `binutils' directory, and making sure that
+building 'objdump' from the 'binutils' directory, and making sure that
 its version of what's going on and your host system's idea (assuming it
-has the pretty standard coff dump utility, usually called `att-dump' or
-just `dump') are the same.  Then clean up your code, and send what
-you've done to Cygnus. Then your stuff will be in the next release, and
+has the pretty standard coff dump utility, usually called 'att-dump' or
+just 'dump') are the same.  Then clean up your code, and send what
+you've done to Cygnus.  Then your stuff will be in the next release, and
 you won't have to keep integrating it.
 
 3.3.2 How the coff backend works
@@ -9435,31 +9074,31 @@ The target-specific routines are further split into ones which are
 basically the same for all Coff targets except that they use the
 external symbol format or use different values for certain constants.
 
-   The generic routines are in `coffgen.c'.  These routines work for
-any Coff target.  They use some hooks into the target specific code;
-the hooks are in a `bfd_coff_backend_data' structure, one of which
-exists for each target.
+   The generic routines are in 'coffgen.c'.  These routines work for any
+Coff target.  They use some hooks into the target specific code; the
+hooks are in a 'bfd_coff_backend_data' structure, one of which exists
+for each target.
 
-   The essentially similar target-specific routines are in
-`coffcode.h'.  This header file includes executable C code.  The
-various Coff targets first include the appropriate Coff header file,
-make any special defines that are needed, and then include `coffcode.h'.
+   The essentially similar target-specific routines are in 'coffcode.h'.
+This header file includes executable C code.  The various Coff targets
+first include the appropriate Coff header file, make any special defines
+that are needed, and then include 'coffcode.h'.
 
    Some of the Coff targets then also have additional routines in the
 target source file itself.
 
-   For example, `coff-i960.c' includes `coff/internal.h' and
-`coff/i960.h'.  It then defines a few constants, such as `I960', and
-includes `coffcode.h'.  Since the i960 has complex relocation types,
-`coff-i960.c' also includes some code to manipulate the i960 relocs.
-This code is not in `coffcode.h' because it would not be used by any
+   For example, 'coff-i960.c' includes 'coff/internal.h' and
+'coff/i960.h'.  It then defines a few constants, such as 'I960', and
+includes 'coffcode.h'.  Since the i960 has complex relocation types,
+'coff-i960.c' also includes some code to manipulate the i960 relocs.
+This code is not in 'coffcode.h' because it would not be used by any
 other target.
 
 3.3.2.2 Coff long section names
 ...............................
 
 In the standard Coff object format, section names are limited to the
-eight bytes available in the `s_name' field of the `SCNHDR' section
+eight bytes available in the 's_name' field of the 'SCNHDR' section
 header structure.  The format requires the field to be NUL-padded, but
 not necessarily NUL-terminated, so the longest section names permitted
 are a full eight characters.
@@ -9467,8 +9106,8 @@ are a full eight characters.
    The Microsoft PE variants of the Coff object file format add an
 extension to support the use of long section names.  This extension is
 defined in section 4 of the Microsoft PE/COFF specification (rev 8.1).
-If a section name is too long to fit into the section header's `s_name'
-field, it is instead placed into the string table, and the `s_name'
+If a section name is too long to fit into the section header's 's_name'
+field, it is instead placed into the string table, and the 's_name'
 field is filled with a slash ("/") followed by the ASCII decimal
 representation of the offset of the full name relative to the string
 table base.
@@ -9482,14 +9121,14 @@ images are to be truncated.
 contain a string table and long section names.  This would appear to be
 technically valid, as the standard only says that Coff debugging
 information is deprecated, not forbidden, and in practice it works,
-although some tools that parse PE files expecting the MS standard
-format may become confused; `PEview' is one known example.
+although some tools that parse PE files expecting the MS standard format
+may become confused; 'PEview' is one known example.
 
    The functionality is supported in BFD by code implemented under the
-control of the macro `COFF_LONG_SECTION_NAMES'.  If not defined, the
+control of the macro 'COFF_LONG_SECTION_NAMES'.  If not defined, the
 format does not support long section names in any way.  If defined, it
-is used to initialise a flag, `_bfd_coff_long_section_names', and a
-hook function pointer, `_bfd_coff_set_long_section_names', in the Coff
+is used to initialise a flag, '_bfd_coff_long_section_names', and a hook
+function pointer, '_bfd_coff_set_long_section_names', in the Coff
 backend data structure.  The flag controls the generation of long
 section names in output BFDs at runtime; if it is false, as it will be
 by default when generating an executable image, long section names are
@@ -9506,77 +9145,77 @@ when deciding what output format to generate, and means that a BFD that
 is opened for read and subsequently converted to a writeable BFD and
 modified in-place will retain whatever format it had on input.
 
-   If `COFF_LONG_SECTION_NAMES' is simply defined (blank), or is
-defined to the value "1", then long section names are enabled by
-default; if it is defined to the value zero, they are disabled by
-default (but still accepted in input BFDs).  The header `coffcode.h'
-defines a macro, `COFF_DEFAULT_LONG_SECTION_NAMES', which is used in
-the backends to initialise the backend data structure fields
-appropriately; see the comments for further detail.
+   If 'COFF_LONG_SECTION_NAMES' is simply defined (blank), or is defined
+to the value "1", then long section names are enabled by default; if it
+is defined to the value zero, they are disabled by default (but still
+accepted in input BFDs).  The header 'coffcode.h' defines a macro,
+'COFF_DEFAULT_LONG_SECTION_NAMES', which is used in the backends to
+initialise the backend data structure fields appropriately; see the
+comments for further detail.
 
 3.3.2.3 Bit twiddling
 .....................
 
-Each flavour of coff supported in BFD has its own header file
-describing the external layout of the structures. There is also an
-internal description of the coff layout, in `coff/internal.h'. A major
-function of the coff backend is swapping the bytes and twiddling the
-bits to translate the external form of the structures into the normal
-internal form. This is all performed in the `bfd_swap'_thing_direction
-routines. Some elements are different sizes between different versions
-of coff; it is the duty of the coff version specific include file to
-override the definitions of various packing routines in `coffcode.h'.
-E.g., the size of line number entry in coff is sometimes 16 bits, and
-sometimes 32 bits. `#define'ing `PUT_LNSZ_LNNO' and `GET_LNSZ_LNNO'
-will select the correct one. No doubt, some day someone will find a
-version of coff which has a varying field size not catered to at the
-moment. To port BFD, that person will have to add more `#defines'.
-Three of the bit twiddling routines are exported to `gdb';
-`coff_swap_aux_in', `coff_swap_sym_in' and `coff_swap_lineno_in'. `GDB'
-reads the symbol table on its own, but uses BFD to fix things up.  More
-of the bit twiddlers are exported for `gas'; `coff_swap_aux_out',
-`coff_swap_sym_out', `coff_swap_lineno_out', `coff_swap_reloc_out',
-`coff_swap_filehdr_out', `coff_swap_aouthdr_out',
-`coff_swap_scnhdr_out'. `Gas' currently keeps track of all the symbol
+Each flavour of coff supported in BFD has its own header file describing
+the external layout of the structures.  There is also an internal
+description of the coff layout, in 'coff/internal.h'.  A major function
+of the coff backend is swapping the bytes and twiddling the bits to
+translate the external form of the structures into the normal internal
+form.  This is all performed in the 'bfd_swap'_thing_direction routines.
+Some elements are different sizes between different versions of coff; it
+is the duty of the coff version specific include file to override the
+definitions of various packing routines in 'coffcode.h'.  E.g., the size
+of line number entry in coff is sometimes 16 bits, and sometimes 32
+bits.  '#define'ing 'PUT_LNSZ_LNNO' and 'GET_LNSZ_LNNO' will select the
+correct one.  No doubt, some day someone will find a version of coff
+which has a varying field size not catered to at the moment.  To port
+BFD, that person will have to add more '#defines'.  Three of the bit
+twiddling routines are exported to 'gdb'; 'coff_swap_aux_in',
+'coff_swap_sym_in' and 'coff_swap_lineno_in'.  'GDB' reads the symbol
+table on its own, but uses BFD to fix things up.  More of the bit
+twiddlers are exported for 'gas'; 'coff_swap_aux_out',
+'coff_swap_sym_out', 'coff_swap_lineno_out', 'coff_swap_reloc_out',
+'coff_swap_filehdr_out', 'coff_swap_aouthdr_out',
+'coff_swap_scnhdr_out'.  'Gas' currently keeps track of all the symbol
 table and reloc drudgery itself, thereby saving the internal BFD
-overhead, but uses BFD to swap things on the way out, making cross
-ports much safer.  Doing so also allows BFD (and thus the linker) to
-use the same header files as `gas', which makes one avenue to disaster
+overhead, but uses BFD to swap things on the way out, making cross ports
+much safer.  Doing so also allows BFD (and thus the linker) to use the
+same header files as 'gas', which makes one avenue to disaster
 disappear.
 
 3.3.2.4 Symbol reading
 ......................
 
 The simple canonical form for symbols used by BFD is not rich enough to
-keep all the information available in a coff symbol table. The back end
+keep all the information available in a coff symbol table.  The back end
 gets around this problem by keeping the original symbol table around,
 "behind the scenes".
 
    When a symbol table is requested (through a call to
-`bfd_canonicalize_symtab'), a request gets through to
-`coff_get_normalized_symtab'. This reads the symbol table from the coff
-file and swaps all the structures inside into the internal form. It
+'bfd_canonicalize_symtab'), a request gets through to
+'coff_get_normalized_symtab'.  This reads the symbol table from the coff
+file and swaps all the structures inside into the internal form.  It
 also fixes up all the pointers in the table (represented in the file by
 offsets from the first symbol in the table) into physical pointers to
-elements in the new internal table. This involves some work since the
+elements in the new internal table.  This involves some work since the
 meanings of fields change depending upon context: a field that is a
 pointer to another structure in the symbol table at one moment may be
-the size in bytes of a structure at the next.  Another pass is made
-over the table. All symbols which mark file names (`C_FILE' symbols)
-are modified so that the internal string points to the value in the
-auxent (the real filename) rather than the normal text associated with
-the symbol (`".file"').
+the size in bytes of a structure at the next.  Another pass is made over
+the table.  All symbols which mark file names ('C_FILE' symbols) are
+modified so that the internal string points to the value in the auxent
+(the real filename) rather than the normal text associated with the
+symbol ('".file"').
 
-   At this time the symbol names are moved around. Coff stores all
+   At this time the symbol names are moved around.  Coff stores all
 symbols less than nine characters long physically within the symbol
 table; longer strings are kept at the end of the file in the string
-table. This pass moves all strings into memory and replaces them with
+table.  This pass moves all strings into memory and replaces them with
 pointers to the strings.
 
    The symbol table is massaged once again, this time to create the
-canonical table used by the BFD application. Each symbol is inspected
-in turn, and a decision made (using the `sclass' field) about the
-various flags to set in the `asymbol'.  *Note Symbols::. The generated
+canonical table used by the BFD application.  Each symbol is inspected
+in turn, and a decision made (using the 'sclass' field) about the
+various flags to set in the 'asymbol'.  *Note Symbols::.  The generated
 canonical table shares strings with the hidden internal symbol table.
 
    Any linenumbers are read from the coff file too, and attached to the
@@ -9586,50 +9225,50 @@ symbols which own the functions the linenumbers belong to.
 ......................
 
 Writing a symbol to a coff file which didn't come from a coff file will
-lose any debugging information. The `asymbol' structure remembers the
+lose any debugging information.  The 'asymbol' structure remembers the
 BFD from which the symbol was taken, and on output the back end makes
 sure that the same destination target as source target is present.
 
    When the symbols have come from a coff file then all the debugging
 information is preserved.
 
-   Symbol tables are provided for writing to the back end in a vector
-of pointers to pointers. This allows applications like the linker to
+   Symbol tables are provided for writing to the back end in a vector of
+pointers to pointers.  This allows applications like the linker to
 accumulate and output large symbol tables without having to do too much
 byte copying.
 
-   This function runs through the provided symbol table and patches
-each symbol marked as a file place holder (`C_FILE') to point to the
-next file place holder in the list. It also marks each `offset' field
-in the list with the offset from the first symbol of the current symbol.
+   This function runs through the provided symbol table and patches each
+symbol marked as a file place holder ('C_FILE') to point to the next
+file place holder in the list.  It also marks each 'offset' field in the
+list with the offset from the first symbol of the current symbol.
 
    Another function of this procedure is to turn the canonical value
-form of BFD into the form used by coff. Internally, BFD expects symbol
+form of BFD into the form used by coff.  Internally, BFD expects symbol
 values to be offsets from a section base; so a symbol physically at
 0x120, but in a section starting at 0x100, would have the value 0x20.
-Coff expects symbols to contain their final value, so symbols have
-their values changed at this point to reflect their sum with their
-owning section.  This transformation uses the `output_section' field of
-the `asymbol''s `asection' *Note Sections::.
+Coff expects symbols to contain their final value, so symbols have their
+values changed at this point to reflect their sum with their owning
+section.  This transformation uses the 'output_section' field of the
+'asymbol''s 'asection' *Note Sections::.
 
-   * `coff_mangle_symbols'
+   * 'coff_mangle_symbols'
    This routine runs though the provided symbol table and uses the
 offsets generated by the previous pass and the pointers generated when
-the symbol table was read in to create the structured hierarchy
-required by coff. It changes each pointer to a symbol into the index
-into the symbol table of the asymbol.
+the symbol table was read in to create the structured hierarchy required
+by coff.  It changes each pointer to a symbol into the index into the
+symbol table of the asymbol.
 
-   * `coff_write_symbols'
-   This routine runs through the symbol table and patches up the
-symbols from their internal form into the coff way, calls the bit
-twiddlers, and writes out the table to the file.
+   * 'coff_write_symbols'
+   This routine runs through the symbol table and patches up the symbols
+from their internal form into the coff way, calls the bit twiddlers, and
+writes out the table to the file.
 
-3.3.2.6 `coff_symbol_type'
+3.3.2.6 'coff_symbol_type'
 ..........................
 
 *Description*
-The hidden information for an `asymbol' is described in a
-`combined_entry_type':
+The hidden information for an 'asymbol' is described in a
+'combined_entry_type':
 
 
      typedef struct coff_ptr_struct
@@ -9684,8 +9323,8 @@ The hidden information for an `asymbol' is described in a
        /* Have the line numbers been relocated yet ? */
        bfd_boolean done_lineno;
      } coff_symbol_type;
-   
-3.3.2.7 `bfd_coff_backend_data'
+
+3.3.2.7 'bfd_coff_backend_data'
 ...............................
 
      /* COFF symbol classifications.  */
@@ -9703,7 +9342,8 @@ The hidden information for an `asymbol' is described in a
        /* PE section symbol.  */
        COFF_SYMBOL_PE_SECTION
      };
-Special entry points for gdb to swap in coff symbol table parts:
+
+   Special entry points for gdb to swap in coff symbol table parts:
      typedef struct
      {
        void (*_bfd_coff_swap_aux_in)
@@ -9986,13 +9626,13 @@ Special entry points for gdb to swap in coff symbol table parts:
 3.3.2.8 Writing relocations
 ...........................
 
-To write relocations, the back end steps though the canonical
-relocation table and create an `internal_reloc'. The symbol index to
-use is removed from the `offset' field in the symbol table supplied.
-The address comes directly from the sum of the section base address and
-the relocation offset; the type is dug directly from the howto field.
-Then the `internal_reloc' is swapped into the shape of an
-`external_reloc' and written out to disk.
+To write relocations, the back end steps though the canonical relocation
+table and create an 'internal_reloc'.  The symbol index to use is
+removed from the 'offset' field in the symbol table supplied.  The
+address comes directly from the sum of the section base address and the
+relocation offset; the type is dug directly from the howto field.  Then
+the 'internal_reloc' is swapped into the shape of an 'external_reloc'
+and written out to disk.
 
 3.3.2.9 Reading linenumbers
 ...........................
@@ -10000,11 +9640,11 @@ Then the `internal_reloc' is swapped into the shape of an
 Creating the linenumber table is done by reading in the entire coff
 linenumber table, and creating another table for internal use.
 
-   A coff linenumber table is structured so that each function is
-marked as having a line number of 0. Each line within the function is
-an offset from the first line in the function. The base of the line
-number information for the table is stored in the symbol associated
-with the function.
+   A coff linenumber table is structured so that each function is marked
+as having a line number of 0.  Each line within the function is an
+offset from the first line in the function.  The base of the line number
+information for the table is stored in the symbol associated with the
+function.
 
    Note: The PE format uses line number 0 for a flag indicating a new
 source file.
@@ -10018,25 +9658,25 @@ and each symbol which marks a function is marked by pointing its...
 ............................
 
 Coff relocations are easily transformed into the internal BFD form
-(`arelent').
+('arelent').
 
    Reading a coff relocation table is done in the following stages:
 
    * Read the entire coff relocation table into memory.
 
-   * Process each relocation in turn; first swap it from the external
-     to the internal form.
+   * Process each relocation in turn; first swap it from the external to
+     the internal form.
 
    * Turn the symbol referenced in the relocation's symbol index into a
-     pointer into the canonical symbol table.  This table is the same
-     as the one returned by a call to `bfd_canonicalize_symtab'. The
-     back end will call that routine and save the result if a
+     pointer into the canonical symbol table.  This table is the same as
+     the one returned by a call to 'bfd_canonicalize_symtab'.  The back
+     end will call that routine and save the result if a
      canonicalization hasn't been done.
 
-   * The reloc index is turned into a pointer to a howto structure, in
-     a back end specific way. For instance, the 386 and 960 use the
-     `r_type' to directly produce an index into a howto table vector;
-     the 88k subtracts a number from the `r_type' field and creates an
+   * The reloc index is turned into a pointer to a howto structure, in a
+     back end specific way.  For instance, the 386 and 960 use the
+     'r_type' to directly produce an index into a howto table vector;
+     the 88k subtracts a number from the 'r_type' field and creates an
      addend field.
 
 
@@ -10058,18 +9698,18 @@ File: bfd.info,  Node: mmo,  Prev: elf,  Up: BFD back ends
 3.5 mmo backend
 ===============
 
-The mmo object format is used exclusively together with Professor
-Donald E. Knuth's educational 64-bit processor MMIX.  The simulator
-`mmix' which is available at
-`http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz'
+The mmo object format is used exclusively together with Professor Donald
+E. Knuth's educational 64-bit processor MMIX. The simulator 'mmix' which
+is available at
+<http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz>
 understands this format.  That package also includes a combined
-assembler and linker called `mmixal'.  The mmo format has no advantages
-feature-wise compared to e.g. ELF.  It is a simple non-relocatable
+assembler and linker called 'mmixal'.  The mmo format has no advantages
+feature-wise compared to e.g.  ELF. It is a simple non-relocatable
 object format with no support for archives or debugging information,
 except for symbol value information and line numbers (which is not yet
-implemented in BFD).  See
-`http://www-cs-faculty.stanford.edu/~knuth/mmix.html' for more
-information about MMIX.  The ELF format is used for intermediate object
+implemented in BFD). See
+<http://www-cs-faculty.stanford.edu/~knuth/mmix.html> for more
+information about MMIX. The ELF format is used for intermediate object
 files in the BFD implementation.
 
 * Menu:
@@ -10085,108 +9725,108 @@ File: bfd.info,  Node: File layout,  Next: Symbol-table,  Prev: mmo,  Up: mmo
 -----------------
 
 The mmo file contents is not partitioned into named sections as with
-e.g. ELF.  Memory areas is formed by specifying the location of the
-data that follows.  Only the memory area `0x0000...00' to `0x01ff...ff'
-is executable, so it is used for code (and constants) and the area
-`0x2000...00' to `0x20ff...ff' is used for writable data.  *Note mmo
+e.g. ELF. Memory areas is formed by specifying the location of the data
+that follows.  Only the memory area '0x0000...00' to '0x01ff...ff' is
+executable, so it is used for code (and constants) and the area
+'0x2000...00' to '0x20ff...ff' is used for writable data.  *Note mmo
 section mapping::.
 
    There is provision for specifying "special data" of 65536 different
-types.  We use type 80 (decimal), arbitrarily chosen the same as the
-ELF `e_machine' number for MMIX, filling it with section information
-normally found in ELF objects. *Note mmo section mapping::.
+types.  We use type 80 (decimal), arbitrarily chosen the same as the ELF
+'e_machine' number for MMIX, filling it with section information
+normally found in ELF objects.  *Note mmo section mapping::.
 
    Contents is entered as 32-bit words, xor:ed over previous contents,
-always zero-initialized.  A word that starts with the byte `0x98' forms
-a command called a `lopcode', where the next byte distinguished between
-the thirteen lopcodes.  The two remaining bytes, called the `Y' and `Z'
-fields, or the `YZ' field (a 16-bit big-endian number), are used for
+always zero-initialized.  A word that starts with the byte '0x98' forms
+a command called a 'lopcode', where the next byte distinguished between
+the thirteen lopcodes.  The two remaining bytes, called the 'Y' and 'Z'
+fields, or the 'YZ' field (a 16-bit big-endian number), are used for
 various purposes different for each lopcode.  As documented in
-`http://www-cs-faculty.stanford.edu/~knuth/mmixal-intro.ps.gz', the
+<http://www-cs-faculty.stanford.edu/~knuth/mmixal-intro.ps.gz>, the
 lopcodes are:
 
-`lop_quote'
+'lop_quote'
      0x98000001.  The next word is contents, regardless of whether it
      starts with 0x98 or not.
 
-`lop_loc'
-     0x9801YYZZ, where `Z' is 1 or 2.  This is a location directive,
-     setting the location for the next data to the next 32-bit word
-     (for Z = 1) or 64-bit word (for Z = 2), plus Y * 2^56.  Normally
-     `Y' is 0 for the text segment and 2 for the data segment.
+'lop_loc'
+     0x9801YYZZ, where 'Z' is 1 or 2.  This is a location directive,
+     setting the location for the next data to the next 32-bit word (for
+     Z = 1) or 64-bit word (for Z = 2), plus Y * 2^56.  Normally 'Y' is
+     0 for the text segment and 2 for the data segment.
 
-`lop_skip'
-     0x9802YYZZ.  Increase the current location by `YZ' bytes.
+'lop_skip'
+     0x9802YYZZ. Increase the current location by 'YZ' bytes.
 
-`lop_fixo'
-     0x9803YYZZ, where `Z' is 1 or 2.  Store the current location as 64
+'lop_fixo'
+     0x9803YYZZ, where 'Z' is 1 or 2.  Store the current location as 64
      bits into the location pointed to by the next 32-bit (Z = 1) or
      64-bit (Z = 2) word, plus Y * 2^56.
 
-`lop_fixr'
-     0x9804YYZZ.  `YZ' is stored into the current location plus 2 - 4 *
+'lop_fixr'
+     0x9804YYZZ. 'YZ' is stored into the current location plus 2 - 4 *
      YZ.
 
-`lop_fixrx'
-     0x980500ZZ.  `Z' is 16 or 24.  A value `L' derived from the
-     following 32-bit word are used in a manner similar to `YZ' in
+'lop_fixrx'
+     0x980500ZZ. 'Z' is 16 or 24.  A value 'L' derived from the
+     following 32-bit word are used in a manner similar to 'YZ' in
      lop_fixr: it is xor:ed into the current location minus 4 * L.  The
      first byte of the word is 0 or 1.  If it is 1, then L = (LOWEST 24
      BITS OF WORD) - 2^Z, if 0, then L = (LOWEST 24 BITS OF WORD).
 
-`lop_file'
-     0x9806YYZZ.  `Y' is the file number, `Z' is count of 32-bit words.
-     Set the file number to `Y' and the line counter to 0.  The next Z
-     * 4 bytes contain the file name, padded with zeros if the count is
-     not a multiple of four.  The same `Y' may occur multiple times,
-     but `Z' must be 0 for all but the first occurrence.
+'lop_file'
+     0x9806YYZZ. 'Y' is the file number, 'Z' is count of 32-bit words.
+     Set the file number to 'Y' and the line counter to 0.  The next Z *
+     4 bytes contain the file name, padded with zeros if the count is
+     not a multiple of four.  The same 'Y' may occur multiple times, but
+     'Z' must be 0 for all but the first occurrence.
 
-`lop_line'
-     0x9807YYZZ.  `YZ' is the line number.  Together with lop_file, it
+'lop_line'
+     0x9807YYZZ. 'YZ' is the line number.  Together with lop_file, it
      forms the source location for the next 32-bit word.  Note that for
      each non-lopcode 32-bit word, line numbers are assumed incremented
      by one.
 
-`lop_spec'
-     0x9808YYZZ.  `YZ' is the type number.  Data until the next lopcode
-     other than lop_quote forms special data of type `YZ'.  *Note mmo
+'lop_spec'
+     0x9808YYZZ. 'YZ' is the type number.  Data until the next lopcode
+     other than lop_quote forms special data of type 'YZ'.  *Note mmo
      section mapping::.
 
      Other types than 80, (or type 80 with a content that does not
-     parse) is stored in sections named `.MMIX.spec_data.N' where N is
-     the `YZ'-type.  The flags for such a sections say not to allocate
+     parse) is stored in sections named '.MMIX.spec_data.N' where N is
+     the 'YZ'-type.  The flags for such a sections say not to allocate
      or load the data.  The vma is 0.  Contents of multiple occurrences
      of special data N is concatenated to the data of the previous
      lop_spec Ns.  The location in data or code at which the lop_spec
      occurred is lost.
 
-`lop_pre'
-     0x980901ZZ.  The first lopcode in a file.  The `Z' field forms the
+'lop_pre'
+     0x980901ZZ. The first lopcode in a file.  The 'Z' field forms the
      length of header information in 32-bit words, where the first word
-     tells the time in seconds since `00:00:00 GMT Jan 1 1970'.
+     tells the time in seconds since '00:00:00 GMT Jan 1 1970'.
 
-`lop_post'
-     0x980a00ZZ.  Z > 32.  This lopcode follows after all
-     content-generating lopcodes in a program.  The `Z' field denotes
-     the value of `rG' at the beginning of the program.  The following
+'lop_post'
+     0x980a00ZZ. Z > 32.  This lopcode follows after all
+     content-generating lopcodes in a program.  The 'Z' field denotes
+     the value of 'rG' at the beginning of the program.  The following
      256 - Z big-endian 64-bit words are loaded into global registers
-     `$G' ... `$255'.
+     '$G' ... '$255'.
 
-`lop_stab'
+'lop_stab'
      0x980b0000.  The next-to-last lopcode in a program.  Must follow
      immediately after the lop_post lopcode and its data.  After this
      lopcode follows all symbols in a compressed format (*note
      Symbol-table::).
 
-`lop_end'
-     0x980cYYZZ.  The last lopcode in a program.  It must follow the
-     lop_stab lopcode and its data.  The `YZ' field contains the number
+'lop_end'
+     0x980cYYZZ. The last lopcode in a program.  It must follow the
+     lop_stab lopcode and its data.  The 'YZ' field contains the number
      of 32-bit words of symbol table information after the preceding
      lop_stab lopcode.
 
-   Note that the lopcode "fixups"; `lop_fixr', `lop_fixrx' and
-`lop_fixo' are not generated by BFD, but are handled.  They are
-generated by `mmixal'.
+   Note that the lopcode "fixups"; 'lop_fixr', 'lop_fixrx' and
+'lop_fixo' are not generated by BFD, but are handled.  They are
+generated by 'mmixal'.
 
    This trivial one-label, one-instruction file:
 
@@ -10223,22 +9863,22 @@ File: bfd.info,  Node: Symbol-table,  Next: mmo section mapping,  Prev: File lay
 -------------------------
 
 From mmixal.w (or really, the generated mmixal.tex) in
-`http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz'):
-"Symbols are stored and retrieved by means of a `ternary search trie',
-following ideas of Bentley and Sedgewick. (See ACM-SIAM Symp. on
-Discrete Algorithms `8' (1997), 360-369; R.Sedgewick, `Algorithms in C'
-(Reading, Mass.  Addison-Wesley, 1998), `15.4'.)  Each trie node stores
-a character, and there are branches to subtries for the cases where a
-given character is less than, equal to, or greater than the character
-in the trie.  There also is a pointer to a symbol table entry if a
-symbol ends at the current node."
+<http://www-cs-faculty.stanford.edu/~knuth/programs/mmix.tar.gz>):
+"Symbols are stored and retrieved by means of a 'ternary search trie',
+following ideas of Bentley and Sedgewick.  (See ACM-SIAM Symp. on
+Discrete Algorithms '8' (1997), 360-369; R.Sedgewick, 'Algorithms in C'
+(Reading, Mass. Addison-Wesley, 1998), '15.4'.)  Each trie node stores a
+character, and there are branches to subtries for the cases where a
+given character is less than, equal to, or greater than the character in
+the trie.  There also is a pointer to a symbol table entry if a symbol
+ends at the current node."
 
    So it's a tree encoded as a stream of bytes.  The stream of bytes
 acts on a single virtual global symbol, adding and removing characters
 and signalling complete symbol points.  Here, we read the stream and
 create symbols at the completion points.
 
-   First, there's a control byte `m'.  If any of the listed bits in `m'
+   First, there's a control byte 'm'.  If any of the listed bits in 'm'
 is nonzero, we execute what stands at the right, in the listed order:
 
       (MMO3_LEFT)
@@ -10248,7 +9888,7 @@ is nonzero, we execute what stands at the right, in the listed order:
       (MMO3_SYMBITS)
       0x2f - Read the next byte as a character and store it in the
              current character position; increment character position.
-             Test the bits of `m':
+             Test the bits of m:
 
              (MMO3_WCHAR)
              0x80 - The character is 16-bit (so read another byte,
@@ -10286,7 +9926,7 @@ is nonzero, we execute what stands at the right, in the listed order:
       0x10 - Traverse right trie.  (Read a new command byte and
              recurse.)
 
-   Let's look again at the `lop_stab' for the trivial file (*note File
+   Let's look again at the 'lop_stab' for the trivial file (*note File
 layout::).
 
       0x980b0000 - lop_stab for ":Main" = 0, serial 1.
@@ -10322,27 +9962,27 @@ File: bfd.info,  Node: mmo section mapping,  Prev: Symbol-table,  Up: mmo
 The implementation in BFD uses special data type 80 (decimal) to
 encapsulate and describe named sections, containing e.g. debug
 information.  If needed, any datum in the encapsulation will be quoted
-using lop_quote.  First comes a 32-bit word holding the number of
-32-bit words containing the zero-terminated zero-padded segment name.
-After the name there's a 32-bit word holding flags describing the
-section type.  Then comes a 64-bit big-endian word with the section
-length (in bytes), then another with the section start address.
-Depending on the type of section, the contents might follow,
-zero-padded to 32-bit boundary.  For a loadable section (such as data
-or code), the contents might follow at some later point, not
-necessarily immediately, as a lop_loc with the same start address as in
-the section description, followed by the contents.  This in effect
-forms a descriptor that must be emitted before the actual contents.
-Sections described this way must not overlap.
+using lop_quote.  First comes a 32-bit word holding the number of 32-bit
+words containing the zero-terminated zero-padded segment name.  After
+the name there's a 32-bit word holding flags describing the section
+type.  Then comes a 64-bit big-endian word with the section length (in
+bytes), then another with the section start address.  Depending on the
+type of section, the contents might follow, zero-padded to 32-bit
+boundary.  For a loadable section (such as data or code), the contents
+might follow at some later point, not necessarily immediately, as a
+lop_loc with the same start address as in the section description,
+followed by the contents.  This in effect forms a descriptor that must
+be emitted before the actual contents.  Sections described this way must
+not overlap.
 
    For areas that don't have such descriptors, synthetic sections are
-formed by BFD.  Consecutive contents in the two memory areas
-`0x0000...00' to `0x01ff...ff' and `0x2000...00' to `0x20ff...ff' are
-entered in sections named `.text' and `.data' respectively.  If an area
+formed by BFD. Consecutive contents in the two memory areas
+'0x0000...00' to '0x01ff...ff' and '0x2000...00' to '0x20ff...ff' are
+entered in sections named '.text' and '.data' respectively.  If an area
 is not otherwise described, but would together with a neighboring lower
-area be less than `0x40000000' bytes long, it is joined with the lower
+area be less than '0x40000000' bytes long, it is joined with the lower
 area and the gap is zero-filled.  For other cases, a new section is
-formed, named `.MMIX.sec.N'.  Here, N is a number, a running count
+formed, named '.MMIX.sec.N'.  Here, N is a number, a running count
 through the mmo file, starting at 0.
 
    A loadable section specified as:
@@ -10351,7 +9991,7 @@ through the mmo file, starting at 0.
       TETRA 1,2,3,4,-1,-2009
       BYTE 80
 
-   and linked to address `0x4', is represented by the sequence:
+   and linked to address '0x4', is represented by the sequence:
 
       0x98080050 - lop_spec 80
       0x00000002 - two 32-bit words for the section name
@@ -10380,7 +10020,7 @@ contents.  Compare this to a non-loaded section specified as:
       TETRA 200001,100002
       BYTE 38,40
 
-   This, when linked to address `0x200000000000001c', is represented by:
+   This, when linked to address '0x200000000000001c', is represented by:
 
       0x98080050 - lop_spec 80
       0x00000002 - two 32-bit words for the section name
@@ -10406,7 +10046,7 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
                      Version 1.3, 3 November 2008
 
      Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-     `http://fsf.org/'
+     <http://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.
@@ -10431,21 +10071,21 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      free program should come with manuals providing the same freedoms
      that the software does.  But this License is not limited to
      software manuals; it can be used for any textual work, regardless
-     of subject matter or whether it is published as a printed book.
-     We recommend this License principally for works whose purpose is
+     of subject matter or whether it is published as a printed book.  We
+     recommend this License principally for works whose purpose is
      instruction or reference.
 
   1. APPLICABILITY AND DEFINITIONS
 
      This License applies to any manual or other work, in any medium,
-     that contains a notice placed by the copyright holder saying it
-     can be distributed under the terms of this License.  Such a notice
+     that contains a notice placed by the copyright holder saying it can
+     be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
      "Document", below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as "you".  You
-     accept the license if you copy, modify or distribute the work in a
-     way requiring permission under copyright law.
+     of the public is a licensee, and is addressed as "you".  You accept
+     the license if you copy, modify or distribute the work in a way
+     requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
@@ -10463,12 +10103,12 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
-     titles are designated, as being those of Invariant Sections, in
-     the notice that says that the Document is released under this
-     License.  If a section does not fit the above definition of
-     Secondary then it is not allowed to be designated as Invariant.
-     The Document may contain zero Invariant Sections.  If the Document
-     does not identify any Invariant Sections then there are none.
+     titles are designated, as being those of Invariant Sections, in the
+     notice that says that the Document is released under this License.
+     If a section does not fit the above definition of Secondary then it
+     is not allowed to be designated as Invariant.  The Document may
+     contain zero Invariant Sections.  If the Document does not identify
+     any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -10479,27 +10119,27 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
-     straightforwardly with generic text editors or (for images
-     composed of pixels) generic paint programs or (for drawings) some
-     widely available drawing editor, and that is suitable for input to
-     text formatters or for automatic translation to a variety of
-     formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup, or absence of
-     markup, has been arranged to thwart or discourage subsequent
-     modification by readers is not Transparent.  An image format is
-     not Transparent if used for any substantial amount of text.  A
-     copy that is not "Transparent" is called "Opaque".
+     straightforwardly with generic text editors or (for images composed
+     of pixels) generic paint programs or (for drawings) some widely
+     available drawing editor, and that is suitable for input to text
+     formatters or for automatic translation to a variety of formats
+     suitable for input to text formatters.  A copy made in an otherwise
+     Transparent file format whose markup, or absence of markup, has
+     been arranged to thwart or discourage subsequent modification by
+     readers is not Transparent.  An image format is not Transparent if
+     used for any substantial amount of text.  A copy that is not
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
-     SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML, PostScript or PDF designed for
-     human modification.  Examples of transparent image formats include
-     PNG, XCF and JPG.  Opaque formats include proprietary formats that
-     can be read and edited only by proprietary word processors, SGML or
-     XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML, PostScript or PDF
-     produced by some word processors for output purposes only.
+     SGML or XML using a publicly available DTD, and standard-conforming
+     simple HTML, PostScript or PDF designed for human modification.
+     Examples of transparent image formats include PNG, XCF and JPG.
+     Opaque formats include proprietary formats that can be read and
+     edited only by proprietary word processors, SGML or XML for which
+     the DTD and/or processing tools are not generally available, and
+     the machine-generated HTML, PostScript or PDF produced by some word
+     processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
@@ -10537,8 +10177,8 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      may not use technical measures to obstruct or control the reading
      or further copying of the copies you make or distribute.  However,
      you may accept compensation in exchange for copies.  If you
-     distribute a large enough number of copies you must also follow
-     the conditions in section 3.
+     distribute a large enough number of copies you must also follow the
+     conditions in section 3.
 
      You may also lend copies, under the same conditions stated above,
      and you may publicly display copies.
@@ -10552,12 +10192,11 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
-     front cover must present the full title with all words of the
-     title equally prominent and visible.  You may add other material
-     on the covers in addition.  Copying with changes limited to the
-     covers, as long as they preserve the title of the Document and
-     satisfy these conditions, can be treated as verbatim copying in
-     other respects.
+     front cover must present the full title with all words of the title
+     equally prominent and visible.  You may add other material on the
+     covers in addition.  Copying with changes limited to the covers, as
+     long as they preserve the title of the Document and satisfy these
+     conditions, can be treated as verbatim copying in other respects.
 
      If the required texts for either cover are too voluminous to fit
      legibly, you should put the first ones listed (as many as fit
@@ -10565,40 +10204,39 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      adjacent pages.
 
      If you publish or distribute Opaque copies of the Document
-     numbering more than 100, you must either include a
-     machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a computer-network location from
-     which the general network-using public has access to download
-     using public-standard network protocols a complete Transparent
-     copy of the Document, free of added material.  If you use the
-     latter option, you must take reasonably prudent steps, when you
-     begin distribution of Opaque copies in quantity, to ensure that
-     this Transparent copy will remain thus accessible at the stated
-     location until at least one year after the last time you
-     distribute an Opaque copy (directly or through your agents or
-     retailers) of that edition to the public.
+     numbering more than 100, you must either include a machine-readable
+     Transparent copy along with each Opaque copy, or state in or with
+     each Opaque copy a computer-network location from which the general
+     network-using public has access to download using public-standard
+     network protocols a complete Transparent copy of the Document, free
+     of added material.  If you use the latter option, you must take
+     reasonably prudent steps, when you begin distribution of Opaque
+     copies in quantity, to ensure that this Transparent copy will
+     remain thus accessible at the stated location until at least one
+     year after the last time you distribute an Opaque copy (directly or
+     through your agents or retailers) of that edition to the public.
 
      It is requested, but not required, that you contact the authors of
-     the Document well before redistributing any large number of
-     copies, to give them a chance to provide you with an updated
-     version of the Document.
+     the Document well before redistributing any large number of copies,
+     to give them a chance to provide you with an updated version of the
+     Document.
 
   4. MODIFICATIONS
 
      You may copy and distribute a Modified Version of the Document
      under the conditions of sections 2 and 3 above, provided that you
-     release the Modified Version under precisely this License, with
-     the Modified Version filling the role of the Document, thus
-     licensing distribution and modification of the Modified Version to
-     whoever possesses a copy of it.  In addition, you must do these
-     things in the Modified Version:
+     release the Modified Version under precisely this License, with the
+     Modified Version filling the role of the Document, thus licensing
+     distribution and modification of the Modified Version to whoever
+     possesses a copy of it.  In addition, you must do these things in
+     the Modified Version:
 
        A. Use in the Title Page (and on the covers, if any) a title
-          distinct from that of the Document, and from those of
-          previous versions (which should, if there were any, be listed
-          in the History section of the Document).  You may use the
-          same title as a previous version if the original publisher of
-          that version gives permission.
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
 
        B. List on the Title Page, as authors, one or more persons or
           entities responsible for authorship of the modifications in
@@ -10628,31 +10266,30 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
 
        I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
-          authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section Entitled "History" in
-          the Document, create one stating the title, year, authors,
-          and publisher of the Document as given on its Title Page,
-          then add an item describing the Modified Version as stated in
-          the previous sentence.
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled "History" in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
 
        J. Preserve the network location, if any, given in the Document
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
-          previous versions it was based on.  These may be placed in
-          the "History" section.  You may omit a network location for a
-          work that was published at least four years before the
-          Document itself, or if the original publisher of the version
-          it refers to gives permission.
+          previous versions it was based on.  These may be placed in the
+          "History" section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
 
        K. For any section Entitled "Acknowledgements" or "Dedications",
-          Preserve the Title of the section, and preserve in the
-          section all the substance and tone of each of the contributor
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
 
-       L. Preserve all the Invariant Sections of the Document,
-          unaltered in their text and in their titles.  Section numbers
-          or the equivalent are not considered part of the section
-          titles.
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
 
        M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
@@ -10665,11 +10302,11 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
 
      If the Modified Version includes new front-matter sections or
      appendices that qualify as Secondary Sections and contain no
-     material copied from the Document, you may at your option
-     designate some or all of these sections as invariant.  To do this,
-     add their titles to the list of Invariant Sections in the Modified
-     Version's license notice.  These titles must be distinct from any
-     other section titles.
+     material copied from the Document, you may at your option designate
+     some or all of these sections as invariant.  To do this, add their
+     titles to the list of Invariant Sections in the Modified Version's
+     license notice.  These titles must be distinct from any other
+     section titles.
 
      You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
@@ -10678,15 +10315,15 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
-     and a passage of up to 25 words as a Back-Cover Text, to the end
-     of the list of Cover Texts in the Modified Version.  Only one
-     passage of Front-Cover Text and one of Back-Cover Text may be
-     added by (or through arrangements made by) any one entity.  If the
-     Document already includes a cover text for the same cover,
-     previously added by you or by arrangement made by the same entity
-     you are acting on behalf of, you may not add another; but you may
-     replace the old one, on explicit permission from the previous
-     publisher that added the old one.
+     and a passage of up to 25 words as a Back-Cover Text, to the end of
+     the list of Cover Texts in the Modified Version.  Only one passage
+     of Front-Cover Text and one of Back-Cover Text may be added by (or
+     through arrangements made by) any one entity.  If the Document
+     already includes a cover text for the same cover, previously added
+     by you or by arrangement made by the same entity you are acting on
+     behalf of, you may not add another; but you may replace the old
+     one, on explicit permission from the previous publisher that added
+     the old one.
 
      The author(s) and publisher(s) of the Document do not by this
      License give permission to use their names for publicity for or to
@@ -10696,8 +10333,8 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
 
      You may combine the Document with other documents released under
      this License, under the terms defined in section 4 above for
-     modified versions, provided that you include in the combination
-     all of the Invariant Sections of all of the original documents,
+     modified versions, provided that you include in the combination all
+     of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
      combined work in its license notice, and that you preserve all
      their Warranty Disclaimers.
@@ -10724,20 +10361,20 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      documents released under this License, and replace the individual
      copies of this License in the various documents with a single copy
      that is included in the collection, provided that you follow the
-     rules of this License for verbatim copying of each of the
-     documents in all other respects.
+     rules of this License for verbatim copying of each of the documents
+     in all other respects.
 
      You may extract a single document from such a collection, and
      distribute it individually under this License, provided you insert
-     a copy of this License into the extracted document, and follow
-     this License in all other respects regarding verbatim copying of
-     that document.
+     a copy of this License into the extracted document, and follow this
+     License in all other respects regarding verbatim copying of that
+     document.
 
   7. AGGREGATION WITH INDEPENDENT WORKS
 
      A compilation of the Document or its derivatives with other
-     separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, is called an "aggregate" if the
+     separate and independent documents or works, in or on a volume of a
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
      legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
@@ -10782,8 +10419,8 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
 
      However, if you cease all violation of this License, then your
      license from a particular copyright holder is reinstated (a)
-     provisionally, unless and until the copyright holder explicitly
-     and finally terminates your license, and (b) permanently, if the
+     provisionally, unless and until the copyright holder explicitly and
+     finally terminates your license, and (b) permanently, if the
      copyright holder fails to notify you of the violation by some
      reasonable means prior to 60 days after the cessation.
 
@@ -10795,33 +10432,33 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      after your receipt of the notice.
 
      Termination of your rights under this section does not terminate
-     the licenses of parties who have received copies or rights from
-     you under this License.  If your rights have been terminated and
-     not permanently reinstated, receipt of a copy of some or all of
-     the same material does not give you any rights to use it.
+     the licenses of parties who have received copies or rights from you
+     under this License.  If your rights have been terminated and not
+     permanently reinstated, receipt of a copy of some or all of the
+     same material does not give you any rights to use it.
 
- 10. FUTURE REVISIONS OF THIS LICENSE
+  10. FUTURE REVISIONS OF THIS LICENSE
 
      The Free Software Foundation may publish new, revised versions of
      the GNU Free Documentation License from time to time.  Such new
      versions will be similar in spirit to the present version, but may
      differ in detail to address new problems or concerns.  See
-     `http://www.gnu.org/copyleft/'.
+     <http://www.gnu.org/copyleft/>.
 
      Each version of the License is given a distinguishing version
      number.  If the Document specifies that a particular numbered
      version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
-     published (not as a draft) by the Free Software Foundation.  If
-     the Document does not specify a version number of this License,
-     you may choose any version ever published (not as a draft) by the
-     Free Software Foundation.  If the Document specifies that a proxy
-     can decide which future versions of this License can be used, that
+     published (not as a draft) by the Free Software Foundation.  If the
+     Document does not specify a version number of this License, you may
+     choose any version ever published (not as a draft) by the Free
+     Software Foundation.  If the Document specifies that a proxy can
+     decide which future versions of this License can be used, that
      proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
- 11. RELICENSING
+  11. RELICENSING
 
      "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
      World Wide Web server that publishes copyrightable works and also
@@ -10851,7 +10488,6 @@ File: bfd.info,  Node: GNU Free Documentation License,  Next: BFD Index,  Prev:
      site under CC-BY-SA on the same site at any time before August 1,
      2009, provided the MMC is eligible for relicensing.
 
-
 ADDENDUM: How to use this License for your documents
 ====================================================
 
@@ -10868,7 +10504,7 @@ notices just after the title page:
        Free Documentation License''.
 
    If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts."  line with this:
 
          with the Invariant Sections being LIST THEIR TITLES, with
          the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -10879,9 +10515,9 @@ combination of the three, merge those two alternatives to suit the
 situation.
 
    If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
 
 
 File: bfd.info,  Node: BFD Index,  Prev: GNU Free Documentation License,  Up: Top
@@ -10899,7 +10535,7 @@ BFD Index
 * _bfd_generic_link_add_one_symbol:      Adding symbols from an object file.
                                                              (line   19)
 * _bfd_generic_make_empty_symbol:        symbol handling functions.
-                                                             (line   92)
+                                                             (line   91)
 * _bfd_link_add_symbols in target vector: Adding Symbols to the Hash Table.
                                                              (line    6)
 * _bfd_link_final_link in target vector: Performing the Final Link.
@@ -10908,140 +10544,140 @@ BFD Index
                                                              (line    6)
 * _bfd_relocate_contents:                Relocating the section contents.
                                                              (line   22)
-* aout_SIZE_machine_type:                aout.               (line  147)
-* aout_SIZE_mkobject:                    aout.               (line  139)
-* aout_SIZE_new_section_hook:            aout.               (line  177)
-* aout_SIZE_set_arch_mach:               aout.               (line  164)
-* aout_SIZE_some_aout_object_p:          aout.               (line  125)
-* aout_SIZE_swap_exec_header_in:         aout.               (line  101)
-* aout_SIZE_swap_exec_header_out:        aout.               (line  113)
+* aout_SIZE_machine_type:                aout.               (line  145)
+* aout_SIZE_mkobject:                    aout.               (line  137)
+* aout_SIZE_new_section_hook:            aout.               (line  175)
+* aout_SIZE_set_arch_mach:               aout.               (line  162)
+* aout_SIZE_some_aout_object_p:          aout.               (line  123)
+* aout_SIZE_swap_exec_header_in:         aout.               (line   99)
+* aout_SIZE_swap_exec_header_out:        aout.               (line  111)
 * arelent_chain:                         typedef arelent.    (line  336)
 * BFD:                                   Overview.           (line    6)
 * BFD canonical format:                  Canonical format.   (line   11)
 * bfd_alloc:                             Opening and Closing.
-                                                             (line  218)
+                                                             (line  217)
 * bfd_alloc2:                            Opening and Closing.
-                                                             (line  227)
-* bfd_alt_mach_code:                     Miscellaneous.      (line  308)
-* bfd_arch_bits_per_address:             Architectures.      (line  570)
-* bfd_arch_bits_per_byte:                Architectures.      (line  562)
-* bfd_arch_default_fill:                 Architectures.      (line  651)
-* bfd_arch_get_compatible:               Architectures.      (line  505)
-* bfd_arch_list:                         Architectures.      (line  496)
-* bfd_arch_mach_octets_per_byte:         Architectures.      (line  639)
-* BFD_ARELOC_BFIN_ADD:                   howto manager.      (line 1111)
-* BFD_ARELOC_BFIN_ADDR:                  howto manager.      (line 1162)
-* BFD_ARELOC_BFIN_AND:                   howto manager.      (line 1132)
-* BFD_ARELOC_BFIN_COMP:                  howto manager.      (line 1153)
-* BFD_ARELOC_BFIN_CONST:                 howto manager.      (line 1108)
-* BFD_ARELOC_BFIN_DIV:                   howto manager.      (line 1120)
-* BFD_ARELOC_BFIN_HWPAGE:                howto manager.      (line 1159)
-* BFD_ARELOC_BFIN_LAND:                  howto manager.      (line 1141)
-* BFD_ARELOC_BFIN_LEN:                   howto manager.      (line 1147)
-* BFD_ARELOC_BFIN_LOR:                   howto manager.      (line 1144)
-* BFD_ARELOC_BFIN_LSHIFT:                howto manager.      (line 1126)
-* BFD_ARELOC_BFIN_MOD:                   howto manager.      (line 1123)
-* BFD_ARELOC_BFIN_MULT:                  howto manager.      (line 1117)
-* BFD_ARELOC_BFIN_NEG:                   howto manager.      (line 1150)
-* BFD_ARELOC_BFIN_OR:                    howto manager.      (line 1135)
-* BFD_ARELOC_BFIN_PAGE:                  howto manager.      (line 1156)
-* BFD_ARELOC_BFIN_PUSH:                  howto manager.      (line 1105)
-* BFD_ARELOC_BFIN_RSHIFT:                howto manager.      (line 1129)
-* BFD_ARELOC_BFIN_SUB:                   howto manager.      (line 1114)
-* BFD_ARELOC_BFIN_XOR:                   howto manager.      (line 1138)
-* bfd_cache_close:                       File Caching.       (line   26)
-* bfd_cache_close_all:                   File Caching.       (line   39)
-* bfd_cache_init:                        File Caching.       (line   18)
+                                                             (line  226)
+* bfd_alt_mach_code:                     Miscellaneous.      (line  302)
+* bfd_arch_bits_per_address:             Architectures.      (line  583)
+* bfd_arch_bits_per_byte:                Architectures.      (line  575)
+* bfd_arch_default_fill:                 Architectures.      (line  664)
+* bfd_arch_get_compatible:               Architectures.      (line  518)
+* bfd_arch_list:                         Architectures.      (line  509)
+* bfd_arch_mach_octets_per_byte:         Architectures.      (line  652)
+* BFD_ARELOC_BFIN_ADD:                   howto manager.      (line 1005)
+* BFD_ARELOC_BFIN_ADDR:                  howto manager.      (line 1039)
+* BFD_ARELOC_BFIN_AND:                   howto manager.      (line 1019)
+* BFD_ARELOC_BFIN_COMP:                  howto manager.      (line 1033)
+* BFD_ARELOC_BFIN_CONST:                 howto manager.      (line 1003)
+* BFD_ARELOC_BFIN_DIV:                   howto manager.      (line 1011)
+* BFD_ARELOC_BFIN_HWPAGE:                howto manager.      (line 1037)
+* BFD_ARELOC_BFIN_LAND:                  howto manager.      (line 1025)
+* BFD_ARELOC_BFIN_LEN:                   howto manager.      (line 1029)
+* BFD_ARELOC_BFIN_LOR:                   howto manager.      (line 1027)
+* BFD_ARELOC_BFIN_LSHIFT:                howto manager.      (line 1015)
+* BFD_ARELOC_BFIN_MOD:                   howto manager.      (line 1013)
+* BFD_ARELOC_BFIN_MULT:                  howto manager.      (line 1009)
+* BFD_ARELOC_BFIN_NEG:                   howto manager.      (line 1031)
+* BFD_ARELOC_BFIN_OR:                    howto manager.      (line 1021)
+* BFD_ARELOC_BFIN_PAGE:                  howto manager.      (line 1035)
+* BFD_ARELOC_BFIN_PUSH:                  howto manager.      (line 1001)
+* BFD_ARELOC_BFIN_RSHIFT:                howto manager.      (line 1017)
+* BFD_ARELOC_BFIN_SUB:                   howto manager.      (line 1007)
+* BFD_ARELOC_BFIN_XOR:                   howto manager.      (line 1023)
+* bfd_cache_close:                       File Caching.       (line   25)
+* bfd_cache_close_all:                   File Caching.       (line   38)
+* bfd_cache_init:                        File Caching.       (line   17)
 * bfd_calc_gnu_debuglink_crc32:          Opening and Closing.
-                                                             (line  254)
-* bfd_canonicalize_reloc:                Miscellaneous.      (line   19)
+                                                             (line  253)
+* bfd_canonicalize_reloc:                Miscellaneous.      (line   18)
 * bfd_canonicalize_symtab:               symbol handling functions.
-                                                             (line   50)
-* bfd_check_format:                      Formats.            (line   21)
-* bfd_check_format_matches:              Formats.            (line   52)
+                                                             (line   49)
+* bfd_check_format:                      Formats.            (line   20)
+* bfd_check_format_matches:              Formats.            (line   51)
 * bfd_check_overflow:                    typedef arelent.    (line  348)
 * bfd_close:                             Opening and Closing.
-                                                             (line  143)
+                                                             (line  142)
 * bfd_close_all_done:                    Opening and Closing.
-                                                             (line  161)
-* bfd_coff_backend_data:                 coff.               (line  305)
-* bfd_copy_private_bfd_data:             Miscellaneous.      (line  158)
-* bfd_copy_private_header_data:          Miscellaneous.      (line  140)
-* bfd_copy_private_section_data:         section prototypes. (line  278)
+                                                             (line  160)
+* bfd_coff_backend_data:                 coff.               (line  304)
+* bfd_copy_private_bfd_data:             Miscellaneous.      (line  155)
+* bfd_copy_private_header_data:          Miscellaneous.      (line  138)
+* bfd_copy_private_section_data:         section prototypes. (line  277)
 * bfd_copy_private_symbol_data:          symbol handling functions.
-                                                             (line  140)
-* bfd_core_file_failing_command:         Core Files.         (line   12)
-* bfd_core_file_failing_signal:          Core Files.         (line   21)
-* bfd_core_file_pid:                     Core Files.         (line   30)
+                                                             (line  139)
+* bfd_core_file_failing_command:         Core Files.         (line   11)
+* bfd_core_file_failing_signal:          Core Files.         (line   20)
+* bfd_core_file_pid:                     Core Files.         (line   29)
 * bfd_create:                            Opening and Closing.
-                                                             (line  180)
+                                                             (line  179)
 * bfd_create_gnu_debuglink_section:      Opening and Closing.
-                                                             (line  321)
+                                                             (line  362)
 * bfd_decode_symclass:                   symbol handling functions.
-                                                             (line  111)
-* bfd_default_arch_struct:               Architectures.      (line  517)
-* bfd_default_compatible:                Architectures.      (line  579)
-* bfd_default_reloc_type_lookup:         howto manager.      (line 3165)
-* bfd_default_scan:                      Architectures.      (line  588)
-* bfd_default_set_arch_mach:             Architectures.      (line  535)
-* bfd_demangle:                          Miscellaneous.      (line  359)
-* bfd_emul_get_commonpagesize:           Miscellaneous.      (line  339)
-* bfd_emul_get_maxpagesize:              Miscellaneous.      (line  319)
-* bfd_emul_set_commonpagesize:           Miscellaneous.      (line  350)
-* bfd_emul_set_maxpagesize:              Miscellaneous.      (line  330)
-* bfd_errmsg:                            Error reporting.    (line   67)
-* bfd_extract_object_only_section:       Opening and Closing.
-                                                             (line  350)
+                                                             (line  110)
+* bfd_default_arch_struct:               Architectures.      (line  530)
+* bfd_default_compatible:                Architectures.      (line  592)
+* bfd_default_reloc_type_lookup:         howto manager.      (line 2771)
+* bfd_default_scan:                      Architectures.      (line  601)
+* bfd_default_set_arch_mach:             Architectures.      (line  548)
+* bfd_demangle:                          Miscellaneous.      (line  353)
+* bfd_emul_get_commonpagesize:           Miscellaneous.      (line  333)
+* bfd_emul_get_maxpagesize:              Miscellaneous.      (line  313)
+* bfd_emul_set_commonpagesize:           Miscellaneous.      (line  344)
+* bfd_emul_set_maxpagesize:              Miscellaneous.      (line  324)
+* bfd_errmsg:                            Error reporting.    (line   66)
 * bfd_fdopenr:                           Opening and Closing.
-                                                             (line   51)
+                                                             (line   50)
 * bfd_fill_in_gnu_debuglink_section:     Opening and Closing.
-                                                             (line  335)
-* bfd_find_target:                       bfd_target.         (line  473)
+                                                             (line  376)
+* bfd_find_target:                       bfd_target.         (line  475)
 * bfd_find_version_for_sym:              Writing the symbol table.
-                                                             (line   81)
+                                                             (line   80)
+* bfd_follow_gnu_debugaltlink:           Opening and Closing.
+                                                             (line  342)
 * bfd_follow_gnu_debuglink:              Opening and Closing.
-                                                             (line  300)
+                                                             (line  321)
 * bfd_fopen:                             Opening and Closing.
-                                                             (line   12)
-* bfd_format_string:                     Formats.            (line   79)
+                                                             (line   11)
+* bfd_format_string:                     Formats.            (line   78)
 * bfd_generic_define_common_symbol:      Writing the symbol table.
-                                                             (line   68)
-* bfd_generic_discard_group:             section prototypes. (line  304)
-* bfd_generic_gc_sections:               howto manager.      (line 3196)
-* bfd_generic_get_relocated_section_contents: howto manager. (line 3226)
-* bfd_generic_is_group_section:          section prototypes. (line  296)
-* bfd_generic_lookup_section_flags:      howto manager.      (line 3206)
-* bfd_generic_merge_sections:            howto manager.      (line 3216)
-* bfd_generic_relax_section:             howto manager.      (line 3183)
-* bfd_get_arch:                          Architectures.      (line  546)
-* bfd_get_arch_info:                     Architectures.      (line  598)
-* bfd_get_arch_size:                     Miscellaneous.      (line   63)
-* bfd_get_assert_handler:                Error reporting.    (line  150)
+                                                             (line   67)
+* bfd_generic_discard_group:             section prototypes. (line  302)
+* bfd_generic_gc_sections:               howto manager.      (line 2802)
+* bfd_generic_get_relocated_section_contents: howto manager. (line 2832)
+* bfd_generic_is_group_section:          section prototypes. (line  294)
+* bfd_generic_lookup_section_flags:      howto manager.      (line 2812)
+* bfd_generic_merge_sections:            howto manager.      (line 2822)
+* bfd_generic_relax_section:             howto manager.      (line 2789)
+* bfd_get_alt_debug_link_info:           Opening and Closing.
+                                                             (line  278)
+* bfd_get_arch:                          Architectures.      (line  559)
+* bfd_get_arch_info:                     Architectures.      (line  611)
+* bfd_get_arch_size:                     Miscellaneous.      (line   61)
+* bfd_get_assert_handler:                Error reporting.    (line  149)
 * bfd_get_debug_link_info:               Opening and Closing.
-                                                             (line  268)
+                                                             (line  267)
 * bfd_get_error:                         Error reporting.    (line   48)
-* bfd_get_error_handler:                 Error reporting.    (line  118)
-* bfd_get_gp_size:                       Miscellaneous.      (line  104)
-* bfd_get_linker_section:                section prototypes. (line   36)
-* bfd_get_mach:                          Architectures.      (line  554)
-* bfd_get_mtime:                         Miscellaneous.      (line  418)
-* bfd_get_next_mapent:                   Archives.           (line   58)
-* bfd_get_next_section_by_name:          section prototypes. (line   26)
-* bfd_get_reloc_code_name:               howto manager.      (line 3174)
+* bfd_get_error_handler:                 Error reporting.    (line  117)
+* bfd_get_gp_size:                       Miscellaneous.      (line  102)
+* bfd_get_linker_section:                section prototypes. (line   35)
+* bfd_get_mach:                          Architectures.      (line  567)
+* bfd_get_mtime:                         Miscellaneous.      (line  403)
+* bfd_get_next_mapent:                   Archives.           (line   57)
+* bfd_get_next_section_by_name:          section prototypes. (line   25)
+* bfd_get_reloc_code_name:               howto manager.      (line 2780)
 * bfd_get_reloc_size:                    typedef arelent.    (line  327)
-* bfd_get_reloc_upper_bound:             Miscellaneous.      (line    9)
-* bfd_get_section_by_name:               section prototypes. (line   17)
-* bfd_get_section_by_name_if:            section prototypes. (line   45)
-* bfd_get_section_contents:              section prototypes. (line  251)
-* bfd_get_sign_extend_vma:               Miscellaneous.      (line   76)
-* bfd_get_size <1>:                      Internal.           (line   25)
-* bfd_get_size:                          Miscellaneous.      (line  427)
+* bfd_get_reloc_upper_bound:             Miscellaneous.      (line    8)
+* bfd_get_section_by_name:               section prototypes. (line   16)
+* bfd_get_section_by_name_if:            section prototypes. (line   44)
+* bfd_get_section_contents:              section prototypes. (line  250)
+* bfd_get_sign_extend_vma:               Miscellaneous.      (line   74)
+* bfd_get_size:                          Miscellaneous.      (line  412)
+* bfd_get_size <1>:                      Internal.           (line   24)
 * bfd_get_symtab_upper_bound:            symbol handling functions.
-                                                             (line    6)
-* bfd_get_target_info:                   bfd_target.         (line  489)
-* bfd_get_unique_section_name:           section prototypes. (line   64)
-* bfd_group_signature:                   Miscellaneous.      (line  370)
-* bfd_h_put_size:                        Internal.           (line   97)
+                                                             (line    5)
+* bfd_get_target_info:                   bfd_target.         (line  491)
+* bfd_get_unique_section_name:           section prototypes. (line   63)
 * bfd_hash_allocate:                     Creating and Freeing a Hash Table.
                                                              (line   17)
 * bfd_hash_lookup:                       Looking Up or Entering a String.
@@ -11059,2016 +10695,2069 @@ BFD Index
 * bfd_hash_traverse:                     Traversing a Hash Table.
                                                              (line    6)
 * bfd_hide_sym_by_version:               Writing the symbol table.
-                                                             (line   93)
-* bfd_init:                              Initialization.     (line   11)
+                                                             (line   92)
+* bfd_h_put_size:                        Internal.           (line   96)
+* bfd_init:                              Initialization.     (line   10)
 * bfd_install_relocation:                typedef arelent.    (line  389)
 * bfd_is_local_label:                    symbol handling functions.
-                                                             (line   17)
+                                                             (line   16)
 * bfd_is_local_label_name:               symbol handling functions.
-                                                             (line   26)
+                                                             (line   25)
 * bfd_is_target_special_symbol:          symbol handling functions.
-                                                             (line   38)
+                                                             (line   37)
 * bfd_is_undefined_symclass:             symbol handling functions.
-                                                             (line  120)
+                                                             (line  119)
 * bfd_link_split_section:                Writing the symbol table.
-                                                             (line   44)
+                                                             (line   43)
 * bfd_log2:                              Internal.           (line  164)
-* bfd_lookup_arch:                       Architectures.      (line  606)
+* bfd_lookup_arch:                       Architectures.      (line  619)
 * bfd_make_debug_symbol:                 symbol handling functions.
-                                                             (line  102)
+                                                             (line  101)
 * bfd_make_empty_symbol:                 symbol handling functions.
-                                                             (line   78)
+                                                             (line   77)
 * bfd_make_readable:                     Opening and Closing.
-                                                             (line  204)
-* bfd_make_section:                      section prototypes. (line  143)
-* bfd_make_section_anyway:               section prototypes. (line  114)
-* bfd_make_section_anyway_with_flags:    section prototypes. (line   96)
-* bfd_make_section_old_way:              section prototypes. (line   76)
-* bfd_make_section_with_flags:           section prototypes. (line  130)
+                                                             (line  203)
+* bfd_make_section:                      section prototypes. (line  141)
+* bfd_make_section_anyway:               section prototypes. (line  113)
+* bfd_make_section_anyway_with_flags:    section prototypes. (line   95)
+* bfd_make_section_old_way:              section prototypes. (line   75)
+* bfd_make_section_with_flags:           section prototypes. (line  129)
 * bfd_make_writable:                     Opening and Closing.
-                                                             (line  190)
-* bfd_malloc_and_get_section:            section prototypes. (line  268)
-* bfd_map_over_sections:                 section prototypes. (line  178)
-* bfd_merge_private_bfd_data:            Miscellaneous.      (line  174)
-* bfd_mmap:                              Miscellaneous.      (line  456)
-* bfd_octets_per_byte:                   Architectures.      (line  629)
-* bfd_open_file:                         File Caching.       (line   52)
+                                                             (line  189)
+* bfd_malloc_and_get_section:            section prototypes. (line  267)
+* bfd_map_over_sections:                 section prototypes. (line  176)
+* bfd_merge_private_bfd_data:            Miscellaneous.      (line  170)
+* bfd_mmap:                              Miscellaneous.      (line  440)
+* bfd_octets_per_byte:                   Architectures.      (line  642)
 * bfd_openr:                             Opening and Closing.
-                                                             (line   35)
+                                                             (line   34)
 * bfd_openr_iovec:                       Opening and Closing.
-                                                             (line   83)
-* bfd_openr_next_archived_file:          Archives.           (line   84)
+                                                             (line   82)
+* bfd_openr_next_archived_file:          Archives.           (line   83)
 * bfd_openstreamr:                       Opening and Closing.
-                                                             (line   74)
+                                                             (line   73)
 * bfd_openw:                             Opening and Closing.
-                                                             (line  131)
+                                                             (line  130)
+* bfd_open_file:                         File Caching.       (line   51)
 * bfd_perform_relocation:                typedef arelent.    (line  364)
-* bfd_perror:                            Error reporting.    (line   76)
+* bfd_perror:                            Error reporting.    (line   75)
+* bfd_printable_arch_mach:               Architectures.      (line  630)
+* bfd_printable_name:                    Architectures.      (line  490)
 * bfd_print_symbol_vandf:                symbol handling functions.
-                                                             (line   70)
-* bfd_printable_arch_mach:               Architectures.      (line  617)
-* bfd_printable_name:                    Architectures.      (line  477)
-* bfd_put_size:                          Internal.           (line   22)
-* BFD_RELOC_12_PCREL:                    howto manager.      (line   39)
-* BFD_RELOC_14:                          howto manager.      (line   31)
-* BFD_RELOC_16:                          howto manager.      (line   30)
-* BFD_RELOC_16_BASEREL:                  howto manager.      (line   99)
-* BFD_RELOC_16_GOT_PCREL:                howto manager.      (line   52)
-* BFD_RELOC_16_GOTOFF:                   howto manager.      (line   55)
-* BFD_RELOC_16_PCREL:                    howto manager.      (line   38)
-* BFD_RELOC_16_PCREL_S2:                 howto manager.      (line  111)
-* BFD_RELOC_16_PLT_PCREL:                howto manager.      (line   63)
-* BFD_RELOC_16_PLTOFF:                   howto manager.      (line   67)
-* BFD_RELOC_16C_ABS20:                   howto manager.      (line 2215)
-* BFD_RELOC_16C_ABS20_C:                 howto manager.      (line 2216)
-* BFD_RELOC_16C_ABS24:                   howto manager.      (line 2217)
-* BFD_RELOC_16C_ABS24_C:                 howto manager.      (line 2218)
-* BFD_RELOC_16C_DISP04:                  howto manager.      (line 2195)
-* BFD_RELOC_16C_DISP04_C:                howto manager.      (line 2196)
-* BFD_RELOC_16C_DISP08:                  howto manager.      (line 2197)
-* BFD_RELOC_16C_DISP08_C:                howto manager.      (line 2198)
-* BFD_RELOC_16C_DISP16:                  howto manager.      (line 2199)
-* BFD_RELOC_16C_DISP16_C:                howto manager.      (line 2200)
-* BFD_RELOC_16C_DISP24:                  howto manager.      (line 2201)
-* BFD_RELOC_16C_DISP24_C:                howto manager.      (line 2202)
-* BFD_RELOC_16C_DISP24a:                 howto manager.      (line 2203)
-* BFD_RELOC_16C_DISP24a_C:               howto manager.      (line 2204)
-* BFD_RELOC_16C_IMM04:                   howto manager.      (line 2219)
-* BFD_RELOC_16C_IMM04_C:                 howto manager.      (line 2220)
-* BFD_RELOC_16C_IMM16:                   howto manager.      (line 2221)
-* BFD_RELOC_16C_IMM16_C:                 howto manager.      (line 2222)
-* BFD_RELOC_16C_IMM20:                   howto manager.      (line 2223)
-* BFD_RELOC_16C_IMM20_C:                 howto manager.      (line 2224)
-* BFD_RELOC_16C_IMM24:                   howto manager.      (line 2225)
-* BFD_RELOC_16C_IMM24_C:                 howto manager.      (line 2226)
-* BFD_RELOC_16C_IMM32:                   howto manager.      (line 2227)
-* BFD_RELOC_16C_IMM32_C:                 howto manager.      (line 2228)
-* BFD_RELOC_16C_NUM08:                   howto manager.      (line 2189)
-* BFD_RELOC_16C_NUM08_C:                 howto manager.      (line 2190)
-* BFD_RELOC_16C_NUM16:                   howto manager.      (line 2191)
-* BFD_RELOC_16C_NUM16_C:                 howto manager.      (line 2192)
-* BFD_RELOC_16C_NUM32:                   howto manager.      (line 2193)
-* BFD_RELOC_16C_NUM32_C:                 howto manager.      (line 2194)
-* BFD_RELOC_16C_REG04:                   howto manager.      (line 2205)
-* BFD_RELOC_16C_REG04_C:                 howto manager.      (line 2206)
-* BFD_RELOC_16C_REG04a:                  howto manager.      (line 2207)
-* BFD_RELOC_16C_REG04a_C:                howto manager.      (line 2208)
-* BFD_RELOC_16C_REG14:                   howto manager.      (line 2209)
-* BFD_RELOC_16C_REG14_C:                 howto manager.      (line 2210)
-* BFD_RELOC_16C_REG16:                   howto manager.      (line 2211)
-* BFD_RELOC_16C_REG16_C:                 howto manager.      (line 2212)
-* BFD_RELOC_16C_REG20:                   howto manager.      (line 2213)
-* BFD_RELOC_16C_REG20_C:                 howto manager.      (line 2214)
-* BFD_RELOC_23_PCREL_S2:                 howto manager.      (line  112)
-* BFD_RELOC_24:                          howto manager.      (line   29)
-* BFD_RELOC_24_PCREL:                    howto manager.      (line   37)
-* BFD_RELOC_24_PLT_PCREL:                howto manager.      (line   62)
-* BFD_RELOC_26:                          howto manager.      (line   28)
-* BFD_RELOC_32:                          howto manager.      (line   27)
-* BFD_RELOC_32_BASEREL:                  howto manager.      (line   98)
-* BFD_RELOC_32_GOT_PCREL:                howto manager.      (line   51)
-* BFD_RELOC_32_GOTOFF:                   howto manager.      (line   54)
-* BFD_RELOC_32_PCREL:                    howto manager.      (line   36)
-* BFD_RELOC_32_PCREL_S2:                 howto manager.      (line  110)
-* BFD_RELOC_32_PLT_PCREL:                howto manager.      (line   61)
-* BFD_RELOC_32_PLTOFF:                   howto manager.      (line   66)
-* BFD_RELOC_32_SECREL:                   howto manager.      (line   48)
-* BFD_RELOC_386_COPY:                    howto manager.      (line  576)
-* BFD_RELOC_386_GLOB_DAT:                howto manager.      (line  577)
-* BFD_RELOC_386_GOT32:                   howto manager.      (line  574)
-* BFD_RELOC_386_GOTOFF:                  howto manager.      (line  580)
-* BFD_RELOC_386_GOTPC:                   howto manager.      (line  581)
-* BFD_RELOC_386_IRELATIVE:               howto manager.      (line  597)
-* BFD_RELOC_386_JUMP_SLOT:               howto manager.      (line  578)
-* BFD_RELOC_386_PLT32:                   howto manager.      (line  575)
-* BFD_RELOC_386_RELATIVE:                howto manager.      (line  579)
-* BFD_RELOC_386_TLS_DESC:                howto manager.      (line  596)
-* BFD_RELOC_386_TLS_DESC_CALL:           howto manager.      (line  595)
-* BFD_RELOC_386_TLS_DTPMOD32:            howto manager.      (line  591)
-* BFD_RELOC_386_TLS_DTPOFF32:            howto manager.      (line  592)
-* BFD_RELOC_386_TLS_GD:                  howto manager.      (line  586)
-* BFD_RELOC_386_TLS_GOTDESC:             howto manager.      (line  594)
-* BFD_RELOC_386_TLS_GOTIE:               howto manager.      (line  584)
-* BFD_RELOC_386_TLS_IE:                  howto manager.      (line  583)
-* BFD_RELOC_386_TLS_IE_32:               howto manager.      (line  589)
-* BFD_RELOC_386_TLS_LDM:                 howto manager.      (line  587)
-* BFD_RELOC_386_TLS_LDO_32:              howto manager.      (line  588)
-* BFD_RELOC_386_TLS_LE:                  howto manager.      (line  585)
-* BFD_RELOC_386_TLS_LE_32:               howto manager.      (line  590)
-* BFD_RELOC_386_TLS_TPOFF:               howto manager.      (line  582)
-* BFD_RELOC_386_TLS_TPOFF32:             howto manager.      (line  593)
-* BFD_RELOC_390_12:                      howto manager.      (line 1810)
-* BFD_RELOC_390_20:                      howto manager.      (line 1910)
-* BFD_RELOC_390_COPY:                    howto manager.      (line 1819)
-* BFD_RELOC_390_GLOB_DAT:                howto manager.      (line 1822)
-* BFD_RELOC_390_GOT12:                   howto manager.      (line 1813)
-* BFD_RELOC_390_GOT16:                   howto manager.      (line 1834)
-* BFD_RELOC_390_GOT20:                   howto manager.      (line 1911)
-* BFD_RELOC_390_GOT64:                   howto manager.      (line 1852)
-* BFD_RELOC_390_GOTENT:                  howto manager.      (line 1858)
-* BFD_RELOC_390_GOTOFF64:                howto manager.      (line 1861)
-* BFD_RELOC_390_GOTPC:                   howto manager.      (line 1831)
-* BFD_RELOC_390_GOTPCDBL:                howto manager.      (line 1849)
-* BFD_RELOC_390_GOTPLT12:                howto manager.      (line 1864)
-* BFD_RELOC_390_GOTPLT16:                howto manager.      (line 1867)
-* BFD_RELOC_390_GOTPLT20:                howto manager.      (line 1912)
-* BFD_RELOC_390_GOTPLT32:                howto manager.      (line 1870)
-* BFD_RELOC_390_GOTPLT64:                howto manager.      (line 1873)
-* BFD_RELOC_390_GOTPLTENT:               howto manager.      (line 1876)
-* BFD_RELOC_390_IRELATIVE:               howto manager.      (line 1916)
-* BFD_RELOC_390_JMP_SLOT:                howto manager.      (line 1825)
-* BFD_RELOC_390_PC16DBL:                 howto manager.      (line 1837)
-* BFD_RELOC_390_PC32DBL:                 howto manager.      (line 1843)
-* BFD_RELOC_390_PLT16DBL:                howto manager.      (line 1840)
-* BFD_RELOC_390_PLT32:                   howto manager.      (line 1816)
-* BFD_RELOC_390_PLT32DBL:                howto manager.      (line 1846)
-* BFD_RELOC_390_PLT64:                   howto manager.      (line 1855)
-* BFD_RELOC_390_PLTOFF16:                howto manager.      (line 1879)
-* BFD_RELOC_390_PLTOFF32:                howto manager.      (line 1882)
-* BFD_RELOC_390_PLTOFF64:                howto manager.      (line 1885)
-* BFD_RELOC_390_RELATIVE:                howto manager.      (line 1828)
-* BFD_RELOC_390_TLS_DTPMOD:              howto manager.      (line 1905)
-* BFD_RELOC_390_TLS_DTPOFF:              howto manager.      (line 1906)
-* BFD_RELOC_390_TLS_GD32:                howto manager.      (line 1891)
-* BFD_RELOC_390_TLS_GD64:                howto manager.      (line 1892)
-* BFD_RELOC_390_TLS_GDCALL:              howto manager.      (line 1889)
-* BFD_RELOC_390_TLS_GOTIE12:             howto manager.      (line 1893)
-* BFD_RELOC_390_TLS_GOTIE20:             howto manager.      (line 1913)
-* BFD_RELOC_390_TLS_GOTIE32:             howto manager.      (line 1894)
-* BFD_RELOC_390_TLS_GOTIE64:             howto manager.      (line 1895)
-* BFD_RELOC_390_TLS_IE32:                howto manager.      (line 1898)
-* BFD_RELOC_390_TLS_IE64:                howto manager.      (line 1899)
-* BFD_RELOC_390_TLS_IEENT:               howto manager.      (line 1900)
-* BFD_RELOC_390_TLS_LDCALL:              howto manager.      (line 1890)
-* BFD_RELOC_390_TLS_LDM32:               howto manager.      (line 1896)
-* BFD_RELOC_390_TLS_LDM64:               howto manager.      (line 1897)
-* BFD_RELOC_390_TLS_LDO32:               howto manager.      (line 1903)
-* BFD_RELOC_390_TLS_LDO64:               howto manager.      (line 1904)
-* BFD_RELOC_390_TLS_LE32:                howto manager.      (line 1901)
-* BFD_RELOC_390_TLS_LE64:                howto manager.      (line 1902)
-* BFD_RELOC_390_TLS_LOAD:                howto manager.      (line 1888)
-* BFD_RELOC_390_TLS_TPOFF:               howto manager.      (line 1907)
-* BFD_RELOC_64:                          howto manager.      (line   26)
-* BFD_RELOC_64_PCREL:                    howto manager.      (line   35)
-* BFD_RELOC_64_PLT_PCREL:                howto manager.      (line   60)
-* BFD_RELOC_64_PLTOFF:                   howto manager.      (line   65)
-* BFD_RELOC_68K_GLOB_DAT:                howto manager.      (line   78)
-* BFD_RELOC_68K_JMP_SLOT:                howto manager.      (line   79)
-* BFD_RELOC_68K_RELATIVE:                howto manager.      (line   80)
-* BFD_RELOC_68K_TLS_GD16:                howto manager.      (line   82)
-* BFD_RELOC_68K_TLS_GD32:                howto manager.      (line   81)
-* BFD_RELOC_68K_TLS_GD8:                 howto manager.      (line   83)
-* BFD_RELOC_68K_TLS_IE16:                howto manager.      (line   91)
-* BFD_RELOC_68K_TLS_IE32:                howto manager.      (line   90)
-* BFD_RELOC_68K_TLS_IE8:                 howto manager.      (line   92)
-* BFD_RELOC_68K_TLS_LDM16:               howto manager.      (line   85)
-* BFD_RELOC_68K_TLS_LDM32:               howto manager.      (line   84)
-* BFD_RELOC_68K_TLS_LDM8:                howto manager.      (line   86)
-* BFD_RELOC_68K_TLS_LDO16:               howto manager.      (line   88)
-* BFD_RELOC_68K_TLS_LDO32:               howto manager.      (line   87)
-* BFD_RELOC_68K_TLS_LDO8:                howto manager.      (line   89)
-* BFD_RELOC_68K_TLS_LE16:                howto manager.      (line   94)
-* BFD_RELOC_68K_TLS_LE32:                howto manager.      (line   93)
-* BFD_RELOC_68K_TLS_LE8:                 howto manager.      (line   95)
-* BFD_RELOC_8:                           howto manager.      (line   32)
-* BFD_RELOC_860_COPY:                    howto manager.      (line 2343)
-* BFD_RELOC_860_GLOB_DAT:                howto manager.      (line 2344)
-* BFD_RELOC_860_HAGOT:                   howto manager.      (line 2369)
-* BFD_RELOC_860_HAGOTOFF:                howto manager.      (line 2370)
-* BFD_RELOC_860_HAPC:                    howto manager.      (line 2371)
-* BFD_RELOC_860_HIGH:                    howto manager.      (line 2372)
-* BFD_RELOC_860_HIGHADJ:                 howto manager.      (line 2368)
-* BFD_RELOC_860_HIGOT:                   howto manager.      (line 2373)
-* BFD_RELOC_860_HIGOTOFF:                howto manager.      (line 2374)
-* BFD_RELOC_860_JUMP_SLOT:               howto manager.      (line 2345)
-* BFD_RELOC_860_LOGOT0:                  howto manager.      (line 2357)
-* BFD_RELOC_860_LOGOT1:                  howto manager.      (line 2359)
-* BFD_RELOC_860_LOGOTOFF0:               howto manager.      (line 2361)
-* BFD_RELOC_860_LOGOTOFF1:               howto manager.      (line 2363)
-* BFD_RELOC_860_LOGOTOFF2:               howto manager.      (line 2365)
-* BFD_RELOC_860_LOGOTOFF3:               howto manager.      (line 2366)
-* BFD_RELOC_860_LOPC:                    howto manager.      (line 2367)
-* BFD_RELOC_860_LOW0:                    howto manager.      (line 2350)
-* BFD_RELOC_860_LOW1:                    howto manager.      (line 2352)
-* BFD_RELOC_860_LOW2:                    howto manager.      (line 2354)
-* BFD_RELOC_860_LOW3:                    howto manager.      (line 2356)
-* BFD_RELOC_860_PC16:                    howto manager.      (line 2349)
-* BFD_RELOC_860_PC26:                    howto manager.      (line 2347)
-* BFD_RELOC_860_PLT26:                   howto manager.      (line 2348)
-* BFD_RELOC_860_RELATIVE:                howto manager.      (line 2346)
-* BFD_RELOC_860_SPGOT0:                  howto manager.      (line 2358)
-* BFD_RELOC_860_SPGOT1:                  howto manager.      (line 2360)
-* BFD_RELOC_860_SPGOTOFF0:               howto manager.      (line 2362)
-* BFD_RELOC_860_SPGOTOFF1:               howto manager.      (line 2364)
-* BFD_RELOC_860_SPLIT0:                  howto manager.      (line 2351)
-* BFD_RELOC_860_SPLIT1:                  howto manager.      (line 2353)
-* BFD_RELOC_860_SPLIT2:                  howto manager.      (line 2355)
-* BFD_RELOC_8_BASEREL:                   howto manager.      (line  103)
-* BFD_RELOC_8_FFnn:                      howto manager.      (line  107)
-* BFD_RELOC_8_GOT_PCREL:                 howto manager.      (line   53)
-* BFD_RELOC_8_GOTOFF:                    howto manager.      (line   59)
-* BFD_RELOC_8_PCREL:                     howto manager.      (line   40)
-* BFD_RELOC_8_PLT_PCREL:                 howto manager.      (line   64)
-* BFD_RELOC_8_PLTOFF:                    howto manager.      (line   71)
-* BFD_RELOC_AARCH64_ADD_LO12:            howto manager.      (line 2708)
-* BFD_RELOC_AARCH64_ADR_GOT_PAGE:        howto manager.      (line 2720)
-* BFD_RELOC_AARCH64_ADR_HI21_NC_PCREL:   howto manager.      (line 2729)
-* BFD_RELOC_AARCH64_ADR_HI21_PCREL:      howto manager.      (line 2725)
-* BFD_RELOC_AARCH64_ADR_LO21_PCREL:      howto manager.      (line 2734)
-* BFD_RELOC_AARCH64_BRANCH19:            howto manager.      (line 2738)
-* BFD_RELOC_AARCH64_CALL26:              howto manager.      (line 2743)
-* BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP:  howto manager.      (line 2748)
-* BFD_RELOC_AARCH64_GOT_LD_PREL19:       howto manager.      (line 2713)
-* BFD_RELOC_AARCH64_JUMP26:              howto manager.      (line 2752)
-* BFD_RELOC_AARCH64_LD64_GOT_LO12_NC:    howto manager.      (line 2762)
-* BFD_RELOC_AARCH64_LD_LO19_PCREL:       howto manager.      (line 2757)
-* BFD_RELOC_AARCH64_LDST128_LO12:        howto manager.      (line 2792)
-* BFD_RELOC_AARCH64_LDST16_LO12:         howto manager.      (line 2777)
-* BFD_RELOC_AARCH64_LDST32_LO12:         howto manager.      (line 2782)
-* BFD_RELOC_AARCH64_LDST64_LO12:         howto manager.      (line 2787)
-* BFD_RELOC_AARCH64_LDST8_LO12:          howto manager.      (line 2772)
-* BFD_RELOC_AARCH64_LDST_LO12:           howto manager.      (line 2767)
-* BFD_RELOC_AARCH64_MOVW_G0:             howto manager.      (line 2797)
-* BFD_RELOC_AARCH64_MOVW_G0_NC:          howto manager.      (line 2806)
-* BFD_RELOC_AARCH64_MOVW_G0_S:           howto manager.      (line 2801)
-* BFD_RELOC_AARCH64_MOVW_G1:             howto manager.      (line 2810)
-* BFD_RELOC_AARCH64_MOVW_G1_NC:          howto manager.      (line 2814)
-* BFD_RELOC_AARCH64_MOVW_G1_S:           howto manager.      (line 2818)
-* BFD_RELOC_AARCH64_MOVW_G2:             howto manager.      (line 2823)
-* BFD_RELOC_AARCH64_MOVW_G2_NC:          howto manager.      (line 2827)
-* BFD_RELOC_AARCH64_MOVW_G2_S:           howto manager.      (line 2831)
-* BFD_RELOC_AARCH64_MOVW_G3:             howto manager.      (line 2836)
-* BFD_RELOC_AARCH64_TLS_DTPMOD64:        howto manager.      (line 2923)
-* BFD_RELOC_AARCH64_TLS_DTPREL64:        howto manager.      (line 2926)
-* BFD_RELOC_AARCH64_TLS_TPREL64:         howto manager.      (line 2929)
-* BFD_RELOC_AARCH64_TLSDESC:             howto manager.      (line 2840)
-* BFD_RELOC_AARCH64_TLSDESC_ADD:         howto manager.      (line 2843)
-* BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC: howto manager.      (line 2846)
-* BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE:    howto manager.      (line 2849)
-* BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21:  howto manager.      (line 2852)
-* BFD_RELOC_AARCH64_TLSDESC_CALL:        howto manager.      (line 2855)
-* BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC: howto manager.     (line 2858)
-* BFD_RELOC_AARCH64_TLSDESC_LD64_PREL19: howto manager.      (line 2861)
-* BFD_RELOC_AARCH64_TLSDESC_LDR:         howto manager.      (line 2864)
-* BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC:   howto manager.      (line 2867)
-* BFD_RELOC_AARCH64_TLSDESC_OFF_G1:      howto manager.      (line 2870)
-* BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC:   howto manager.      (line 2873)
-* BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21:    howto manager.      (line 2878)
+                                                             (line   69)
+* bfd_put_size:                          Internal.           (line   21)
+* BFD_RELOC_12_PCREL:                    howto manager.      (line   37)
+* BFD_RELOC_14:                          howto manager.      (line   30)
+* BFD_RELOC_16:                          howto manager.      (line   29)
+* BFD_RELOC_16C_ABS20:                   howto manager.      (line 1896)
+* BFD_RELOC_16C_ABS20_C:                 howto manager.      (line 1897)
+* BFD_RELOC_16C_ABS24:                   howto manager.      (line 1898)
+* BFD_RELOC_16C_ABS24_C:                 howto manager.      (line 1899)
+* BFD_RELOC_16C_DISP04:                  howto manager.      (line 1876)
+* BFD_RELOC_16C_DISP04_C:                howto manager.      (line 1877)
+* BFD_RELOC_16C_DISP08:                  howto manager.      (line 1878)
+* BFD_RELOC_16C_DISP08_C:                howto manager.      (line 1879)
+* BFD_RELOC_16C_DISP16:                  howto manager.      (line 1880)
+* BFD_RELOC_16C_DISP16_C:                howto manager.      (line 1881)
+* BFD_RELOC_16C_DISP24:                  howto manager.      (line 1882)
+* BFD_RELOC_16C_DISP24a:                 howto manager.      (line 1884)
+* BFD_RELOC_16C_DISP24a_C:               howto manager.      (line 1885)
+* BFD_RELOC_16C_DISP24_C:                howto manager.      (line 1883)
+* BFD_RELOC_16C_IMM04:                   howto manager.      (line 1900)
+* BFD_RELOC_16C_IMM04_C:                 howto manager.      (line 1901)
+* BFD_RELOC_16C_IMM16:                   howto manager.      (line 1902)
+* BFD_RELOC_16C_IMM16_C:                 howto manager.      (line 1903)
+* BFD_RELOC_16C_IMM20:                   howto manager.      (line 1904)
+* BFD_RELOC_16C_IMM20_C:                 howto manager.      (line 1905)
+* BFD_RELOC_16C_IMM24:                   howto manager.      (line 1906)
+* BFD_RELOC_16C_IMM24_C:                 howto manager.      (line 1907)
+* BFD_RELOC_16C_IMM32:                   howto manager.      (line 1908)
+* BFD_RELOC_16C_IMM32_C:                 howto manager.      (line 1909)
+* BFD_RELOC_16C_NUM08:                   howto manager.      (line 1870)
+* BFD_RELOC_16C_NUM08_C:                 howto manager.      (line 1871)
+* BFD_RELOC_16C_NUM16:                   howto manager.      (line 1872)
+* BFD_RELOC_16C_NUM16_C:                 howto manager.      (line 1873)
+* BFD_RELOC_16C_NUM32:                   howto manager.      (line 1874)
+* BFD_RELOC_16C_NUM32_C:                 howto manager.      (line 1875)
+* BFD_RELOC_16C_REG04:                   howto manager.      (line 1886)
+* BFD_RELOC_16C_REG04a:                  howto manager.      (line 1888)
+* BFD_RELOC_16C_REG04a_C:                howto manager.      (line 1889)
+* BFD_RELOC_16C_REG04_C:                 howto manager.      (line 1887)
+* BFD_RELOC_16C_REG14:                   howto manager.      (line 1890)
+* BFD_RELOC_16C_REG14_C:                 howto manager.      (line 1891)
+* BFD_RELOC_16C_REG16:                   howto manager.      (line 1892)
+* BFD_RELOC_16C_REG16_C:                 howto manager.      (line 1893)
+* BFD_RELOC_16C_REG20:                   howto manager.      (line 1894)
+* BFD_RELOC_16C_REG20_C:                 howto manager.      (line 1895)
+* BFD_RELOC_16_BASEREL:                  howto manager.      (line   92)
+* BFD_RELOC_16_GOTOFF:                   howto manager.      (line   51)
+* BFD_RELOC_16_GOT_PCREL:                howto manager.      (line   48)
+* BFD_RELOC_16_PCREL:                    howto manager.      (line   36)
+* BFD_RELOC_16_PCREL_S2:                 howto manager.      (line  102)
+* BFD_RELOC_16_PLTOFF:                   howto manager.      (line   63)
+* BFD_RELOC_16_PLT_PCREL:                howto manager.      (line   59)
+* BFD_RELOC_23_PCREL_S2:                 howto manager.      (line  103)
+* BFD_RELOC_24:                          howto manager.      (line   28)
+* BFD_RELOC_24_PCREL:                    howto manager.      (line   35)
+* BFD_RELOC_24_PLT_PCREL:                howto manager.      (line   58)
+* BFD_RELOC_26:                          howto manager.      (line   27)
+* BFD_RELOC_32:                          howto manager.      (line   26)
+* BFD_RELOC_32_BASEREL:                  howto manager.      (line   91)
+* BFD_RELOC_32_GOTOFF:                   howto manager.      (line   50)
+* BFD_RELOC_32_GOT_PCREL:                howto manager.      (line   47)
+* BFD_RELOC_32_PCREL:                    howto manager.      (line   34)
+* BFD_RELOC_32_PCREL_S2:                 howto manager.      (line  101)
+* BFD_RELOC_32_PLTOFF:                   howto manager.      (line   62)
+* BFD_RELOC_32_PLT_PCREL:                howto manager.      (line   57)
+* BFD_RELOC_32_SECREL:                   howto manager.      (line   45)
+* BFD_RELOC_386_COPY:                    howto manager.      (line  510)
+* BFD_RELOC_386_GLOB_DAT:                howto manager.      (line  511)
+* BFD_RELOC_386_GOT32:                   howto manager.      (line  508)
+* BFD_RELOC_386_GOTOFF:                  howto manager.      (line  514)
+* BFD_RELOC_386_GOTPC:                   howto manager.      (line  515)
+* BFD_RELOC_386_IRELATIVE:               howto manager.      (line  531)
+* BFD_RELOC_386_JUMP_SLOT:               howto manager.      (line  512)
+* BFD_RELOC_386_PLT32:                   howto manager.      (line  509)
+* BFD_RELOC_386_RELATIVE:                howto manager.      (line  513)
+* BFD_RELOC_386_TLS_DESC:                howto manager.      (line  530)
+* BFD_RELOC_386_TLS_DESC_CALL:           howto manager.      (line  529)
+* BFD_RELOC_386_TLS_DTPMOD32:            howto manager.      (line  525)
+* BFD_RELOC_386_TLS_DTPOFF32:            howto manager.      (line  526)
+* BFD_RELOC_386_TLS_GD:                  howto manager.      (line  520)
+* BFD_RELOC_386_TLS_GOTDESC:             howto manager.      (line  528)
+* BFD_RELOC_386_TLS_GOTIE:               howto manager.      (line  518)
+* BFD_RELOC_386_TLS_IE:                  howto manager.      (line  517)
+* BFD_RELOC_386_TLS_IE_32:               howto manager.      (line  523)
+* BFD_RELOC_386_TLS_LDM:                 howto manager.      (line  521)
+* BFD_RELOC_386_TLS_LDO_32:              howto manager.      (line  522)
+* BFD_RELOC_386_TLS_LE:                  howto manager.      (line  519)
+* BFD_RELOC_386_TLS_LE_32:               howto manager.      (line  524)
+* BFD_RELOC_386_TLS_TPOFF:               howto manager.      (line  516)
+* BFD_RELOC_386_TLS_TPOFF32:             howto manager.      (line  527)
+* BFD_RELOC_390_12:                      howto manager.      (line 1560)
+* BFD_RELOC_390_20:                      howto manager.      (line 1641)
+* BFD_RELOC_390_COPY:                    howto manager.      (line 1566)
+* BFD_RELOC_390_GLOB_DAT:                howto manager.      (line 1568)
+* BFD_RELOC_390_GOT12:                   howto manager.      (line 1562)
+* BFD_RELOC_390_GOT16:                   howto manager.      (line 1576)
+* BFD_RELOC_390_GOT20:                   howto manager.      (line 1642)
+* BFD_RELOC_390_GOT64:                   howto manager.      (line 1596)
+* BFD_RELOC_390_GOTENT:                  howto manager.      (line 1600)
+* BFD_RELOC_390_GOTOFF64:                howto manager.      (line 1602)
+* BFD_RELOC_390_GOTPC:                   howto manager.      (line 1574)
+* BFD_RELOC_390_GOTPCDBL:                howto manager.      (line 1594)
+* BFD_RELOC_390_GOTPLT12:                howto manager.      (line 1604)
+* BFD_RELOC_390_GOTPLT16:                howto manager.      (line 1606)
+* BFD_RELOC_390_GOTPLT20:                howto manager.      (line 1643)
+* BFD_RELOC_390_GOTPLT32:                howto manager.      (line 1608)
+* BFD_RELOC_390_GOTPLT64:                howto manager.      (line 1610)
+* BFD_RELOC_390_GOTPLTENT:               howto manager.      (line 1612)
+* BFD_RELOC_390_IRELATIVE:               howto manager.      (line 1646)
+* BFD_RELOC_390_JMP_SLOT:                howto manager.      (line 1570)
+* BFD_RELOC_390_PC12DBL:                 howto manager.      (line 1578)
+* BFD_RELOC_390_PC16DBL:                 howto manager.      (line 1582)
+* BFD_RELOC_390_PC24DBL:                 howto manager.      (line 1586)
+* BFD_RELOC_390_PC32DBL:                 howto manager.      (line 1590)
+* BFD_RELOC_390_PLT12DBL:                howto manager.      (line 1580)
+* BFD_RELOC_390_PLT16DBL:                howto manager.      (line 1584)
+* BFD_RELOC_390_PLT24DBL:                howto manager.      (line 1588)
+* BFD_RELOC_390_PLT32:                   howto manager.      (line 1564)
+* BFD_RELOC_390_PLT32DBL:                howto manager.      (line 1592)
+* BFD_RELOC_390_PLT64:                   howto manager.      (line 1598)
+* BFD_RELOC_390_PLTOFF16:                howto manager.      (line 1614)
+* BFD_RELOC_390_PLTOFF32:                howto manager.      (line 1616)
+* BFD_RELOC_390_PLTOFF64:                howto manager.      (line 1618)
+* BFD_RELOC_390_RELATIVE:                howto manager.      (line 1572)
+* BFD_RELOC_390_TLS_DTPMOD:              howto manager.      (line 1637)
+* BFD_RELOC_390_TLS_DTPOFF:              howto manager.      (line 1638)
+* BFD_RELOC_390_TLS_GD32:                howto manager.      (line 1623)
+* BFD_RELOC_390_TLS_GD64:                howto manager.      (line 1624)
+* BFD_RELOC_390_TLS_GDCALL:              howto manager.      (line 1621)
+* BFD_RELOC_390_TLS_GOTIE12:             howto manager.      (line 1625)
+* BFD_RELOC_390_TLS_GOTIE20:             howto manager.      (line 1644)
+* BFD_RELOC_390_TLS_GOTIE32:             howto manager.      (line 1626)
+* BFD_RELOC_390_TLS_GOTIE64:             howto manager.      (line 1627)
+* BFD_RELOC_390_TLS_IE32:                howto manager.      (line 1630)
+* BFD_RELOC_390_TLS_IE64:                howto manager.      (line 1631)
+* BFD_RELOC_390_TLS_IEENT:               howto manager.      (line 1632)
+* BFD_RELOC_390_TLS_LDCALL:              howto manager.      (line 1622)
+* BFD_RELOC_390_TLS_LDM32:               howto manager.      (line 1628)
+* BFD_RELOC_390_TLS_LDM64:               howto manager.      (line 1629)
+* BFD_RELOC_390_TLS_LDO32:               howto manager.      (line 1635)
+* BFD_RELOC_390_TLS_LDO64:               howto manager.      (line 1636)
+* BFD_RELOC_390_TLS_LE32:                howto manager.      (line 1633)
+* BFD_RELOC_390_TLS_LE64:                howto manager.      (line 1634)
+* BFD_RELOC_390_TLS_LOAD:                howto manager.      (line 1620)
+* BFD_RELOC_390_TLS_TPOFF:               howto manager.      (line 1639)
+* BFD_RELOC_64:                          howto manager.      (line   25)
+* BFD_RELOC_64_PCREL:                    howto manager.      (line   33)
+* BFD_RELOC_64_PLTOFF:                   howto manager.      (line   61)
+* BFD_RELOC_64_PLT_PCREL:                howto manager.      (line   56)
+* BFD_RELOC_68K_GLOB_DAT:                howto manager.      (line   72)
+* BFD_RELOC_68K_JMP_SLOT:                howto manager.      (line   73)
+* BFD_RELOC_68K_RELATIVE:                howto manager.      (line   74)
+* BFD_RELOC_68K_TLS_GD16:                howto manager.      (line   76)
+* BFD_RELOC_68K_TLS_GD32:                howto manager.      (line   75)
+* BFD_RELOC_68K_TLS_GD8:                 howto manager.      (line   77)
+* BFD_RELOC_68K_TLS_IE16:                howto manager.      (line   85)
+* BFD_RELOC_68K_TLS_IE32:                howto manager.      (line   84)
+* BFD_RELOC_68K_TLS_IE8:                 howto manager.      (line   86)
+* BFD_RELOC_68K_TLS_LDM16:               howto manager.      (line   79)
+* BFD_RELOC_68K_TLS_LDM32:               howto manager.      (line   78)
+* BFD_RELOC_68K_TLS_LDM8:                howto manager.      (line   80)
+* BFD_RELOC_68K_TLS_LDO16:               howto manager.      (line   82)
+* BFD_RELOC_68K_TLS_LDO32:               howto manager.      (line   81)
+* BFD_RELOC_68K_TLS_LDO8:                howto manager.      (line   83)
+* BFD_RELOC_68K_TLS_LE16:                howto manager.      (line   88)
+* BFD_RELOC_68K_TLS_LE32:                howto manager.      (line   87)
+* BFD_RELOC_68K_TLS_LE8:                 howto manager.      (line   89)
+* BFD_RELOC_8:                           howto manager.      (line   31)
+* BFD_RELOC_860_COPY:                    howto manager.      (line 2011)
+* BFD_RELOC_860_GLOB_DAT:                howto manager.      (line 2012)
+* BFD_RELOC_860_HAGOT:                   howto manager.      (line 2037)
+* BFD_RELOC_860_HAGOTOFF:                howto manager.      (line 2038)
+* BFD_RELOC_860_HAPC:                    howto manager.      (line 2039)
+* BFD_RELOC_860_HIGH:                    howto manager.      (line 2040)
+* BFD_RELOC_860_HIGHADJ:                 howto manager.      (line 2036)
+* BFD_RELOC_860_HIGOT:                   howto manager.      (line 2041)
+* BFD_RELOC_860_HIGOTOFF:                howto manager.      (line 2042)
+* BFD_RELOC_860_JUMP_SLOT:               howto manager.      (line 2013)
+* BFD_RELOC_860_LOGOT0:                  howto manager.      (line 2025)
+* BFD_RELOC_860_LOGOT1:                  howto manager.      (line 2027)
+* BFD_RELOC_860_LOGOTOFF0:               howto manager.      (line 2029)
+* BFD_RELOC_860_LOGOTOFF1:               howto manager.      (line 2031)
+* BFD_RELOC_860_LOGOTOFF2:               howto manager.      (line 2033)
+* BFD_RELOC_860_LOGOTOFF3:               howto manager.      (line 2034)
+* BFD_RELOC_860_LOPC:                    howto manager.      (line 2035)
+* BFD_RELOC_860_LOW0:                    howto manager.      (line 2018)
+* BFD_RELOC_860_LOW1:                    howto manager.      (line 2020)
+* BFD_RELOC_860_LOW2:                    howto manager.      (line 2022)
+* BFD_RELOC_860_LOW3:                    howto manager.      (line 2024)
+* BFD_RELOC_860_PC16:                    howto manager.      (line 2017)
+* BFD_RELOC_860_PC26:                    howto manager.      (line 2015)
+* BFD_RELOC_860_PLT26:                   howto manager.      (line 2016)
+* BFD_RELOC_860_RELATIVE:                howto manager.      (line 2014)
+* BFD_RELOC_860_SPGOT0:                  howto manager.      (line 2026)
+* BFD_RELOC_860_SPGOT1:                  howto manager.      (line 2028)
+* BFD_RELOC_860_SPGOTOFF0:               howto manager.      (line 2030)
+* BFD_RELOC_860_SPGOTOFF1:               howto manager.      (line 2032)
+* BFD_RELOC_860_SPLIT0:                  howto manager.      (line 2019)
+* BFD_RELOC_860_SPLIT1:                  howto manager.      (line 2021)
+* BFD_RELOC_860_SPLIT2:                  howto manager.      (line 2023)
+* BFD_RELOC_8_BASEREL:                   howto manager.      (line   96)
+* BFD_RELOC_8_FFnn:                      howto manager.      (line   99)
+* BFD_RELOC_8_GOTOFF:                    howto manager.      (line   55)
+* BFD_RELOC_8_GOT_PCREL:                 howto manager.      (line   49)
+* BFD_RELOC_8_PCREL:                     howto manager.      (line   38)
+* BFD_RELOC_8_PLTOFF:                    howto manager.      (line   67)
+* BFD_RELOC_8_PLT_PCREL:                 howto manager.      (line   60)
+* BFD_RELOC_AARCH64_16:                  howto manager.      (line 2338)
+* BFD_RELOC_AARCH64_16_PCREL:            howto manager.      (line 2344)
+* BFD_RELOC_AARCH64_32:                  howto manager.      (line 2337)
+* BFD_RELOC_AARCH64_32_PCREL:            howto manager.      (line 2343)
+* BFD_RELOC_AARCH64_64:                  howto manager.      (line 2336)
+* BFD_RELOC_AARCH64_64_PCREL:            howto manager.      (line 2342)
+* BFD_RELOC_AARCH64_ADD_LO12:            howto manager.      (line 2394)
+* BFD_RELOC_AARCH64_ADR_GOT_PAGE:        howto manager.      (line 2440)
+* BFD_RELOC_AARCH64_ADR_HI21_NC_PCREL:   howto manager.      (line 2390)
+* BFD_RELOC_AARCH64_ADR_HI21_PCREL:      howto manager.      (line 2387)
+* BFD_RELOC_AARCH64_ADR_LO21_PCREL:      howto manager.      (line 2384)
+* BFD_RELOC_AARCH64_BRANCH19:            howto manager.      (line 2406)
+* BFD_RELOC_AARCH64_CALL26:              howto manager.      (line 2414)
+* BFD_RELOC_AARCH64_COPY:                howto manager.      (line 2511)
+* BFD_RELOC_AARCH64_GAS_INTERNAL_FIXUP:  howto manager.      (line 2535)
+* BFD_RELOC_AARCH64_GLOB_DAT:            howto manager.      (line 2513)
+* BFD_RELOC_AARCH64_GOT_LD_PREL19:       howto manager.      (line 2434)
+* BFD_RELOC_AARCH64_IRELATIVE:           howto manager.      (line 2527)
+* BFD_RELOC_AARCH64_JUMP26:              howto manager.      (line 2410)
+* BFD_RELOC_AARCH64_JUMP_SLOT:           howto manager.      (line 2515)
+* BFD_RELOC_AARCH64_LD32_GOT_LO12_NC:    howto manager.      (line 2448)
+* BFD_RELOC_AARCH64_LD64_GOT_LO12_NC:    howto manager.      (line 2444)
+* BFD_RELOC_AARCH64_LDST128_LO12:        howto manager.      (line 2430)
+* BFD_RELOC_AARCH64_LDST16_LO12:         howto manager.      (line 2418)
+* BFD_RELOC_AARCH64_LDST32_LO12:         howto manager.      (line 2422)
+* BFD_RELOC_AARCH64_LDST64_LO12:         howto manager.      (line 2426)
+* BFD_RELOC_AARCH64_LDST8_LO12:          howto manager.      (line 2398)
+* BFD_RELOC_AARCH64_LDST_LO12:           howto manager.      (line 2538)
+* BFD_RELOC_AARCH64_LD_GOT_LO12_NC:      howto manager.      (line 2542)
+* BFD_RELOC_AARCH64_LD_LO19_PCREL:       howto manager.      (line 2380)
+* BFD_RELOC_AARCH64_MOVW_G0:             howto manager.      (line 2347)
+* BFD_RELOC_AARCH64_MOVW_G0_NC:          howto manager.      (line 2350)
+* BFD_RELOC_AARCH64_MOVW_G0_S:           howto manager.      (line 2368)
+* BFD_RELOC_AARCH64_MOVW_G1:             howto manager.      (line 2353)
+* BFD_RELOC_AARCH64_MOVW_G1_NC:          howto manager.      (line 2356)
+* BFD_RELOC_AARCH64_MOVW_G1_S:           howto manager.      (line 2372)
+* BFD_RELOC_AARCH64_MOVW_G2:             howto manager.      (line 2359)
+* BFD_RELOC_AARCH64_MOVW_G2_NC:          howto manager.      (line 2362)
+* BFD_RELOC_AARCH64_MOVW_G2_S:           howto manager.      (line 2376)
+* BFD_RELOC_AARCH64_MOVW_G3:             howto manager.      (line 2365)
+* BFD_RELOC_AARCH64_NONE:                howto manager.      (line 2334)
+* BFD_RELOC_AARCH64_RELATIVE:            howto manager.      (line 2517)
+* BFD_RELOC_AARCH64_RELOC_END:           howto manager.      (line 2529)
+* BFD_RELOC_AARCH64_RELOC_START:         howto manager.      (line 2329)
+* BFD_RELOC_AARCH64_TLSDESC:             howto manager.      (line 2525)
+* BFD_RELOC_AARCH64_TLSDESC_ADD:         howto manager.      (line 2507)
+* BFD_RELOC_AARCH64_TLSDESC_ADD_LO12_NC: howto manager.      (line 2499)
+* BFD_RELOC_AARCH64_TLSDESC_ADR_PAGE21:  howto manager.      (line 2493)
+* BFD_RELOC_AARCH64_TLSDESC_ADR_PREL21:  howto manager.      (line 2491)
+* BFD_RELOC_AARCH64_TLSDESC_CALL:        howto manager.      (line 2509)
+* BFD_RELOC_AARCH64_TLSDESC_LD32_LO12_NC: howto manager.     (line 2497)
+* BFD_RELOC_AARCH64_TLSDESC_LD64_LO12_NC: howto manager.     (line 2495)
+* BFD_RELOC_AARCH64_TLSDESC_LDR:         howto manager.      (line 2505)
+* BFD_RELOC_AARCH64_TLSDESC_LD_LO12_NC:  howto manager.      (line 2548)
+* BFD_RELOC_AARCH64_TLSDESC_LD_PREL19:   howto manager.      (line 2489)
+* BFD_RELOC_AARCH64_TLSDESC_OFF_G0_NC:   howto manager.      (line 2503)
+* BFD_RELOC_AARCH64_TLSDESC_OFF_G1:      howto manager.      (line 2501)
+* BFD_RELOC_AARCH64_TLSGD_ADD_LO12_NC:   howto manager.      (line 2457)
+* BFD_RELOC_AARCH64_TLSGD_ADR_PAGE21:    howto manager.      (line 2452)
 * BFD_RELOC_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21: howto manager.
-                                                             (line 2884)
+                                                             (line 2465)
+* BFD_RELOC_AARCH64_TLSIE_LD32_GOTTPREL_LO12_NC: howto manager.
+                                                             (line 2469)
 * BFD_RELOC_AARCH64_TLSIE_LD64_GOTTPREL_LO12_NC: howto manager.
-                                                             (line 2890)
-* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19: howto manager. (line 2887)
+                                                             (line 2467)
+* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_LO12_NC: howto manager.
+                                                             (line 2545)
+* BFD_RELOC_AARCH64_TLSIE_LD_GOTTPREL_PREL19: howto manager. (line 2471)
 * BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G0_NC: howto manager.
-                                                             (line 2893)
-* BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1: howto manager.   (line 2896)
-* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12: howto manager.     (line 2899)
-* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12: howto manager.     (line 2902)
-* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC: howto manager.  (line 2905)
-* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0: howto manager.      (line 2908)
-* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC: howto manager.   (line 2911)
-* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1: howto manager.      (line 2914)
-* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC: howto manager.   (line 2917)
-* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2: howto manager.      (line 2920)
-* BFD_RELOC_AARCH64_TSTBR14:             howto manager.      (line 2932)
-* BFD_RELOC_ALPHA_BOH:                   howto manager.      (line  323)
-* BFD_RELOC_ALPHA_BRSGP:                 howto manager.      (line  306)
-* BFD_RELOC_ALPHA_BSR:                   howto manager.      (line  315)
-* BFD_RELOC_ALPHA_CODEADDR:              howto manager.      (line  297)
-* BFD_RELOC_ALPHA_DTPMOD64:              howto manager.      (line  329)
-* BFD_RELOC_ALPHA_DTPREL16:              howto manager.      (line  334)
-* BFD_RELOC_ALPHA_DTPREL64:              howto manager.      (line  331)
-* BFD_RELOC_ALPHA_DTPREL_HI16:           howto manager.      (line  332)
-* BFD_RELOC_ALPHA_DTPREL_LO16:           howto manager.      (line  333)
-* BFD_RELOC_ALPHA_ELF_LITERAL:           howto manager.      (line  262)
-* BFD_RELOC_ALPHA_GOTDTPREL16:           howto manager.      (line  330)
-* BFD_RELOC_ALPHA_GOTTPREL16:            howto manager.      (line  335)
-* BFD_RELOC_ALPHA_GPDISP:                howto manager.      (line  256)
-* BFD_RELOC_ALPHA_GPDISP_HI16:           howto manager.      (line  242)
-* BFD_RELOC_ALPHA_GPDISP_LO16:           howto manager.      (line  250)
-* BFD_RELOC_ALPHA_GPREL_HI16:            howto manager.      (line  301)
-* BFD_RELOC_ALPHA_GPREL_LO16:            howto manager.      (line  302)
-* BFD_RELOC_ALPHA_HINT:                  howto manager.      (line  288)
-* BFD_RELOC_ALPHA_LDA:                   howto manager.      (line  319)
-* BFD_RELOC_ALPHA_LINKAGE:               howto manager.      (line  293)
-* BFD_RELOC_ALPHA_LITERAL:               howto manager.      (line  261)
-* BFD_RELOC_ALPHA_LITUSE:                howto manager.      (line  263)
-* BFD_RELOC_ALPHA_NOP:                   howto manager.      (line  311)
-* BFD_RELOC_ALPHA_TLSGD:                 howto manager.      (line  327)
-* BFD_RELOC_ALPHA_TLSLDM:                howto manager.      (line  328)
-* BFD_RELOC_ALPHA_TPREL16:               howto manager.      (line  339)
-* BFD_RELOC_ALPHA_TPREL64:               howto manager.      (line  336)
-* BFD_RELOC_ALPHA_TPREL_HI16:            howto manager.      (line  337)
-* BFD_RELOC_ALPHA_TPREL_LO16:            howto manager.      (line  338)
-* BFD_RELOC_ARC_B22_PCREL:               howto manager.      (line 1040)
-* BFD_RELOC_ARC_B26:                     howto manager.      (line 1045)
-* BFD_RELOC_ARM_ADR_IMM:                 howto manager.      (line  926)
-* BFD_RELOC_ARM_ADRL_IMMEDIATE:          howto manager.      (line  912)
-* BFD_RELOC_ARM_ALU_PC_G0:               howto manager.      (line  876)
-* BFD_RELOC_ARM_ALU_PC_G0_NC:            howto manager.      (line  875)
-* BFD_RELOC_ARM_ALU_PC_G1:               howto manager.      (line  878)
-* BFD_RELOC_ARM_ALU_PC_G1_NC:            howto manager.      (line  877)
-* BFD_RELOC_ARM_ALU_PC_G2:               howto manager.      (line  879)
-* BFD_RELOC_ARM_ALU_SB_G0:               howto manager.      (line  890)
-* BFD_RELOC_ARM_ALU_SB_G0_NC:            howto manager.      (line  889)
-* BFD_RELOC_ARM_ALU_SB_G1:               howto manager.      (line  892)
-* BFD_RELOC_ARM_ALU_SB_G1_NC:            howto manager.      (line  891)
-* BFD_RELOC_ARM_ALU_SB_G2:               howto manager.      (line  893)
-* BFD_RELOC_ARM_CP_OFF_IMM:              howto manager.      (line  922)
-* BFD_RELOC_ARM_CP_OFF_IMM_S2:           howto manager.      (line  923)
-* BFD_RELOC_ARM_GLOB_DAT:                howto manager.      (line  850)
-* BFD_RELOC_ARM_GOT32:                   howto manager.      (line  851)
-* BFD_RELOC_ARM_GOT_PREL:                howto manager.      (line  856)
-* BFD_RELOC_ARM_GOTOFF:                  howto manager.      (line  854)
-* BFD_RELOC_ARM_GOTPC:                   howto manager.      (line  855)
-* BFD_RELOC_ARM_HVC:                     howto manager.      (line  919)
-* BFD_RELOC_ARM_HWLITERAL:               howto manager.      (line  933)
-* BFD_RELOC_ARM_IMMEDIATE:               howto manager.      (line  911)
-* BFD_RELOC_ARM_IN_POOL:                 howto manager.      (line  929)
-* BFD_RELOC_ARM_IRELATIVE:               howto manager.      (line  908)
-* BFD_RELOC_ARM_JUMP_SLOT:               howto manager.      (line  849)
-* BFD_RELOC_ARM_LDC_PC_G0:               howto manager.      (line  886)
-* BFD_RELOC_ARM_LDC_PC_G1:               howto manager.      (line  887)
-* BFD_RELOC_ARM_LDC_PC_G2:               howto manager.      (line  888)
-* BFD_RELOC_ARM_LDC_SB_G0:               howto manager.      (line  900)
-* BFD_RELOC_ARM_LDC_SB_G1:               howto manager.      (line  901)
-* BFD_RELOC_ARM_LDC_SB_G2:               howto manager.      (line  902)
-* BFD_RELOC_ARM_LDR_IMM:                 howto manager.      (line  927)
-* BFD_RELOC_ARM_LDR_PC_G0:               howto manager.      (line  880)
-* BFD_RELOC_ARM_LDR_PC_G1:               howto manager.      (line  881)
-* BFD_RELOC_ARM_LDR_PC_G2:               howto manager.      (line  882)
-* BFD_RELOC_ARM_LDR_SB_G0:               howto manager.      (line  894)
-* BFD_RELOC_ARM_LDR_SB_G1:               howto manager.      (line  895)
-* BFD_RELOC_ARM_LDR_SB_G2:               howto manager.      (line  896)
-* BFD_RELOC_ARM_LDRS_PC_G0:              howto manager.      (line  883)
-* BFD_RELOC_ARM_LDRS_PC_G1:              howto manager.      (line  884)
-* BFD_RELOC_ARM_LDRS_PC_G2:              howto manager.      (line  885)
-* BFD_RELOC_ARM_LDRS_SB_G0:              howto manager.      (line  897)
-* BFD_RELOC_ARM_LDRS_SB_G1:              howto manager.      (line  898)
-* BFD_RELOC_ARM_LDRS_SB_G2:              howto manager.      (line  899)
-* BFD_RELOC_ARM_LITERAL:                 howto manager.      (line  928)
-* BFD_RELOC_ARM_MOVT:                    howto manager.      (line  840)
-* BFD_RELOC_ARM_MOVT_PCREL:              howto manager.      (line  842)
-* BFD_RELOC_ARM_MOVW:                    howto manager.      (line  839)
-* BFD_RELOC_ARM_MOVW_PCREL:              howto manager.      (line  841)
-* BFD_RELOC_ARM_MULTI:                   howto manager.      (line  921)
-* BFD_RELOC_ARM_OFFSET_IMM:              howto manager.      (line  813)
-* BFD_RELOC_ARM_OFFSET_IMM8:             howto manager.      (line  930)
-* BFD_RELOC_ARM_PCREL_BLX:               howto manager.      (line  784)
-* BFD_RELOC_ARM_PCREL_BRANCH:            howto manager.      (line  780)
-* BFD_RELOC_ARM_PCREL_CALL:              howto manager.      (line  794)
-* BFD_RELOC_ARM_PCREL_JUMP:              howto manager.      (line  798)
-* BFD_RELOC_ARM_PLT32:                   howto manager.      (line  852)
-* BFD_RELOC_ARM_PREL31:                  howto manager.      (line  836)
-* BFD_RELOC_ARM_RELATIVE:                howto manager.      (line  853)
-* BFD_RELOC_ARM_ROSEGREL32:              howto manager.      (line  825)
-* BFD_RELOC_ARM_SBREL32:                 howto manager.      (line  828)
-* BFD_RELOC_ARM_SHIFT_IMM:               howto manager.      (line  917)
-* BFD_RELOC_ARM_SMC:                     howto manager.      (line  918)
-* BFD_RELOC_ARM_SWI:                     howto manager.      (line  920)
-* BFD_RELOC_ARM_T32_ADD_IMM:             howto manager.      (line  914)
-* BFD_RELOC_ARM_T32_ADD_PC12:            howto manager.      (line  916)
-* BFD_RELOC_ARM_T32_CP_OFF_IMM:          howto manager.      (line  924)
-* BFD_RELOC_ARM_T32_CP_OFF_IMM_S2:       howto manager.      (line  925)
-* BFD_RELOC_ARM_T32_IMM12:               howto manager.      (line  915)
-* BFD_RELOC_ARM_T32_IMMEDIATE:           howto manager.      (line  913)
-* BFD_RELOC_ARM_T32_OFFSET_IMM:          howto manager.      (line  932)
-* BFD_RELOC_ARM_T32_OFFSET_U8:           howto manager.      (line  931)
-* BFD_RELOC_ARM_TARGET1:                 howto manager.      (line  821)
-* BFD_RELOC_ARM_TARGET2:                 howto manager.      (line  831)
-* BFD_RELOC_ARM_THM_TLS_CALL:            howto manager.      (line  869)
-* BFD_RELOC_ARM_THM_TLS_DESCSEQ:         howto manager.      (line  871)
-* BFD_RELOC_ARM_THUMB_ADD:               howto manager.      (line  934)
-* BFD_RELOC_ARM_THUMB_IMM:               howto manager.      (line  935)
-* BFD_RELOC_ARM_THUMB_MOVT:              howto manager.      (line  844)
-* BFD_RELOC_ARM_THUMB_MOVT_PCREL:        howto manager.      (line  846)
-* BFD_RELOC_ARM_THUMB_MOVW:              howto manager.      (line  843)
-* BFD_RELOC_ARM_THUMB_MOVW_PCREL:        howto manager.      (line  845)
-* BFD_RELOC_ARM_THUMB_OFFSET:            howto manager.      (line  817)
-* BFD_RELOC_ARM_THUMB_SHIFT:             howto manager.      (line  936)
-* BFD_RELOC_ARM_TLS_CALL:                howto manager.      (line  868)
-* BFD_RELOC_ARM_TLS_DESC:                howto manager.      (line  872)
-* BFD_RELOC_ARM_TLS_DESCSEQ:             howto manager.      (line  870)
-* BFD_RELOC_ARM_TLS_DTPMOD32:            howto manager.      (line  863)
-* BFD_RELOC_ARM_TLS_DTPOFF32:            howto manager.      (line  862)
-* BFD_RELOC_ARM_TLS_GD32:                howto manager.      (line  859)
-* BFD_RELOC_ARM_TLS_GOTDESC:             howto manager.      (line  867)
-* BFD_RELOC_ARM_TLS_IE32:                howto manager.      (line  865)
-* BFD_RELOC_ARM_TLS_LDM32:               howto manager.      (line  861)
-* BFD_RELOC_ARM_TLS_LDO32:               howto manager.      (line  860)
-* BFD_RELOC_ARM_TLS_LE32:                howto manager.      (line  866)
-* BFD_RELOC_ARM_TLS_TPOFF32:             howto manager.      (line  864)
-* BFD_RELOC_ARM_V4BX:                    howto manager.      (line  905)
-* BFD_RELOC_AVR_13_PCREL:                howto manager.      (line 1635)
-* BFD_RELOC_AVR_16_PM:                   howto manager.      (line 1639)
-* BFD_RELOC_AVR_6:                       howto manager.      (line 1726)
-* BFD_RELOC_AVR_6_ADIW:                  howto manager.      (line 1730)
-* BFD_RELOC_AVR_7_PCREL:                 howto manager.      (line 1631)
-* BFD_RELOC_AVR_8_HI:                    howto manager.      (line 1738)
-* BFD_RELOC_AVR_8_HLO:                   howto manager.      (line 1742)
-* BFD_RELOC_AVR_8_LO:                    howto manager.      (line 1734)
-* BFD_RELOC_AVR_CALL:                    howto manager.      (line 1718)
-* BFD_RELOC_AVR_HH8_LDI:                 howto manager.      (line 1651)
-* BFD_RELOC_AVR_HH8_LDI_NEG:             howto manager.      (line 1670)
-* BFD_RELOC_AVR_HH8_LDI_PM:              howto manager.      (line 1699)
-* BFD_RELOC_AVR_HH8_LDI_PM_NEG:          howto manager.      (line 1713)
-* BFD_RELOC_AVR_HI8_LDI:                 howto manager.      (line 1647)
-* BFD_RELOC_AVR_HI8_LDI_GS:              howto manager.      (line 1693)
-* BFD_RELOC_AVR_HI8_LDI_NEG:             howto manager.      (line 1665)
-* BFD_RELOC_AVR_HI8_LDI_PM:              howto manager.      (line 1689)
-* BFD_RELOC_AVR_HI8_LDI_PM_NEG:          howto manager.      (line 1708)
-* BFD_RELOC_AVR_LDI:                     howto manager.      (line 1722)
-* BFD_RELOC_AVR_LO8_LDI:                 howto manager.      (line 1643)
-* BFD_RELOC_AVR_LO8_LDI_GS:              howto manager.      (line 1683)
-* BFD_RELOC_AVR_LO8_LDI_NEG:             howto manager.      (line 1660)
-* BFD_RELOC_AVR_LO8_LDI_PM:              howto manager.      (line 1679)
-* BFD_RELOC_AVR_LO8_LDI_PM_NEG:          howto manager.      (line 1704)
-* BFD_RELOC_AVR_MS8_LDI:                 howto manager.      (line 1656)
-* BFD_RELOC_AVR_MS8_LDI_NEG:             howto manager.      (line 1675)
-* BFD_RELOC_BFIN_10_PCREL:               howto manager.      (line 1065)
-* BFD_RELOC_BFIN_11_PCREL:               howto manager.      (line 1068)
-* BFD_RELOC_BFIN_12_PCREL_JUMP:          howto manager.      (line 1071)
-* BFD_RELOC_BFIN_12_PCREL_JUMP_S:        howto manager.      (line 1074)
-* BFD_RELOC_BFIN_16_HIGH:                howto manager.      (line 1053)
-* BFD_RELOC_BFIN_16_IMM:                 howto manager.      (line 1050)
-* BFD_RELOC_BFIN_16_LOW:                 howto manager.      (line 1062)
-* BFD_RELOC_BFIN_24_PCREL_CALL_X:        howto manager.      (line 1077)
-* BFD_RELOC_BFIN_24_PCREL_JUMP_L:        howto manager.      (line 1080)
-* BFD_RELOC_BFIN_4_PCREL:                howto manager.      (line 1056)
-* BFD_RELOC_BFIN_5_PCREL:                howto manager.      (line 1059)
-* BFD_RELOC_BFIN_FUNCDESC:               howto manager.      (line 1086)
-* BFD_RELOC_BFIN_FUNCDESC_GOT17M4:       howto manager.      (line 1087)
-* BFD_RELOC_BFIN_FUNCDESC_GOTHI:         howto manager.      (line 1088)
-* BFD_RELOC_BFIN_FUNCDESC_GOTLO:         howto manager.      (line 1089)
-* BFD_RELOC_BFIN_FUNCDESC_GOTOFF17M4:    howto manager.      (line 1091)
-* BFD_RELOC_BFIN_FUNCDESC_GOTOFFHI:      howto manager.      (line 1092)
-* BFD_RELOC_BFIN_FUNCDESC_GOTOFFLO:      howto manager.      (line 1093)
-* BFD_RELOC_BFIN_FUNCDESC_VALUE:         howto manager.      (line 1090)
-* BFD_RELOC_BFIN_GOT:                    howto manager.      (line 1099)
-* BFD_RELOC_BFIN_GOT17M4:                howto manager.      (line 1083)
-* BFD_RELOC_BFIN_GOTHI:                  howto manager.      (line 1084)
-* BFD_RELOC_BFIN_GOTLO:                  howto manager.      (line 1085)
-* BFD_RELOC_BFIN_GOTOFF17M4:             howto manager.      (line 1094)
-* BFD_RELOC_BFIN_GOTOFFHI:               howto manager.      (line 1095)
-* BFD_RELOC_BFIN_GOTOFFLO:               howto manager.      (line 1096)
-* BFD_RELOC_BFIN_PLTPC:                  howto manager.      (line 1102)
-* BFD_RELOC_C6000_ABS_H16:               howto manager.      (line 1454)
-* BFD_RELOC_C6000_ABS_L16:               howto manager.      (line 1453)
-* BFD_RELOC_C6000_ABS_S16:               howto manager.      (line 1452)
-* BFD_RELOC_C6000_ALIGN:                 howto manager.      (line 1475)
-* BFD_RELOC_C6000_COPY:                  howto manager.      (line 1470)
-* BFD_RELOC_C6000_DSBT_INDEX:            howto manager.      (line 1468)
-* BFD_RELOC_C6000_EHTYPE:                howto manager.      (line 1472)
-* BFD_RELOC_C6000_FPHEAD:                howto manager.      (line 1476)
-* BFD_RELOC_C6000_JUMP_SLOT:             howto manager.      (line 1471)
-* BFD_RELOC_C6000_NOCMP:                 howto manager.      (line 1477)
-* BFD_RELOC_C6000_PCR_H16:               howto manager.      (line 1473)
-* BFD_RELOC_C6000_PCR_L16:               howto manager.      (line 1474)
-* BFD_RELOC_C6000_PCR_S10:               howto manager.      (line 1450)
-* BFD_RELOC_C6000_PCR_S12:               howto manager.      (line 1449)
-* BFD_RELOC_C6000_PCR_S21:               howto manager.      (line 1448)
-* BFD_RELOC_C6000_PCR_S7:                howto manager.      (line 1451)
-* BFD_RELOC_C6000_PREL31:                howto manager.      (line 1469)
-* BFD_RELOC_C6000_SBR_GOT_H16_W:         howto manager.      (line 1467)
-* BFD_RELOC_C6000_SBR_GOT_L16_W:         howto manager.      (line 1466)
-* BFD_RELOC_C6000_SBR_GOT_U15_W:         howto manager.      (line 1465)
-* BFD_RELOC_C6000_SBR_H16_B:             howto manager.      (line 1462)
-* BFD_RELOC_C6000_SBR_H16_H:             howto manager.      (line 1463)
-* BFD_RELOC_C6000_SBR_H16_W:             howto manager.      (line 1464)
-* BFD_RELOC_C6000_SBR_L16_B:             howto manager.      (line 1459)
-* BFD_RELOC_C6000_SBR_L16_H:             howto manager.      (line 1460)
-* BFD_RELOC_C6000_SBR_L16_W:             howto manager.      (line 1461)
-* BFD_RELOC_C6000_SBR_S16:               howto manager.      (line 1458)
-* BFD_RELOC_C6000_SBR_U15_B:             howto manager.      (line 1455)
-* BFD_RELOC_C6000_SBR_U15_H:             howto manager.      (line 1456)
-* BFD_RELOC_C6000_SBR_U15_W:             howto manager.      (line 1457)
-* bfd_reloc_code_type:                   howto manager.      (line   10)
-* BFD_RELOC_CR16_ABS20:                  howto manager.      (line 2243)
-* BFD_RELOC_CR16_ABS24:                  howto manager.      (line 2244)
-* BFD_RELOC_CR16_DISP16:                 howto manager.      (line 2254)
-* BFD_RELOC_CR16_DISP20:                 howto manager.      (line 2255)
-* BFD_RELOC_CR16_DISP24:                 howto manager.      (line 2256)
-* BFD_RELOC_CR16_DISP24a:                howto manager.      (line 2257)
-* BFD_RELOC_CR16_DISP4:                  howto manager.      (line 2252)
-* BFD_RELOC_CR16_DISP8:                  howto manager.      (line 2253)
-* BFD_RELOC_CR16_GLOB_DAT:               howto manager.      (line 2263)
-* BFD_RELOC_CR16_GOT_REGREL20:           howto manager.      (line 2261)
-* BFD_RELOC_CR16_GOTC_REGREL20:          howto manager.      (line 2262)
-* BFD_RELOC_CR16_IMM16:                  howto manager.      (line 2247)
-* BFD_RELOC_CR16_IMM20:                  howto manager.      (line 2248)
-* BFD_RELOC_CR16_IMM24:                  howto manager.      (line 2249)
-* BFD_RELOC_CR16_IMM32:                  howto manager.      (line 2250)
-* BFD_RELOC_CR16_IMM32a:                 howto manager.      (line 2251)
-* BFD_RELOC_CR16_IMM4:                   howto manager.      (line 2245)
-* BFD_RELOC_CR16_IMM8:                   howto manager.      (line 2246)
-* BFD_RELOC_CR16_NUM16:                  howto manager.      (line 2232)
-* BFD_RELOC_CR16_NUM32:                  howto manager.      (line 2233)
-* BFD_RELOC_CR16_NUM32a:                 howto manager.      (line 2234)
-* BFD_RELOC_CR16_NUM8:                   howto manager.      (line 2231)
-* BFD_RELOC_CR16_REGREL0:                howto manager.      (line 2235)
-* BFD_RELOC_CR16_REGREL14:               howto manager.      (line 2238)
-* BFD_RELOC_CR16_REGREL14a:              howto manager.      (line 2239)
-* BFD_RELOC_CR16_REGREL16:               howto manager.      (line 2240)
-* BFD_RELOC_CR16_REGREL20:               howto manager.      (line 2241)
-* BFD_RELOC_CR16_REGREL20a:              howto manager.      (line 2242)
-* BFD_RELOC_CR16_REGREL4:                howto manager.      (line 2236)
-* BFD_RELOC_CR16_REGREL4a:               howto manager.      (line 2237)
-* BFD_RELOC_CR16_SWITCH16:               howto manager.      (line 2259)
-* BFD_RELOC_CR16_SWITCH32:               howto manager.      (line 2260)
-* BFD_RELOC_CR16_SWITCH8:                howto manager.      (line 2258)
-* BFD_RELOC_CRIS_16_DTPREL:              howto manager.      (line 2334)
-* BFD_RELOC_CRIS_16_GOT:                 howto manager.      (line 2310)
-* BFD_RELOC_CRIS_16_GOT_GD:              howto manager.      (line 2330)
-* BFD_RELOC_CRIS_16_GOT_TPREL:           howto manager.      (line 2336)
-* BFD_RELOC_CRIS_16_GOTPLT:              howto manager.      (line 2316)
-* BFD_RELOC_CRIS_16_TPREL:               howto manager.      (line 2338)
-* BFD_RELOC_CRIS_32_DTPREL:              howto manager.      (line 2333)
-* BFD_RELOC_CRIS_32_GD:                  howto manager.      (line 2331)
-* BFD_RELOC_CRIS_32_GOT:                 howto manager.      (line 2307)
-* BFD_RELOC_CRIS_32_GOT_GD:              howto manager.      (line 2329)
-* BFD_RELOC_CRIS_32_GOT_TPREL:           howto manager.      (line 2335)
-* BFD_RELOC_CRIS_32_GOTPLT:              howto manager.      (line 2313)
-* BFD_RELOC_CRIS_32_GOTREL:              howto manager.      (line 2319)
-* BFD_RELOC_CRIS_32_IE:                  howto manager.      (line 2340)
-* BFD_RELOC_CRIS_32_PLT_GOTREL:          howto manager.      (line 2322)
-* BFD_RELOC_CRIS_32_PLT_PCREL:           howto manager.      (line 2325)
-* BFD_RELOC_CRIS_32_TPREL:               howto manager.      (line 2337)
-* BFD_RELOC_CRIS_BDISP8:                 howto manager.      (line 2288)
-* BFD_RELOC_CRIS_COPY:                   howto manager.      (line 2301)
-* BFD_RELOC_CRIS_DTP:                    howto manager.      (line 2332)
-* BFD_RELOC_CRIS_DTPMOD:                 howto manager.      (line 2339)
-* BFD_RELOC_CRIS_GLOB_DAT:               howto manager.      (line 2302)
-* BFD_RELOC_CRIS_JUMP_SLOT:              howto manager.      (line 2303)
-* BFD_RELOC_CRIS_LAPCQ_OFFSET:           howto manager.      (line 2296)
-* BFD_RELOC_CRIS_RELATIVE:               howto manager.      (line 2304)
-* BFD_RELOC_CRIS_SIGNED_16:              howto manager.      (line 2294)
-* BFD_RELOC_CRIS_SIGNED_6:               howto manager.      (line 2290)
-* BFD_RELOC_CRIS_SIGNED_8:               howto manager.      (line 2292)
-* BFD_RELOC_CRIS_UNSIGNED_16:            howto manager.      (line 2295)
-* BFD_RELOC_CRIS_UNSIGNED_4:             howto manager.      (line 2297)
-* BFD_RELOC_CRIS_UNSIGNED_5:             howto manager.      (line 2289)
-* BFD_RELOC_CRIS_UNSIGNED_6:             howto manager.      (line 2291)
-* BFD_RELOC_CRIS_UNSIGNED_8:             howto manager.      (line 2293)
-* BFD_RELOC_CRX_ABS16:                   howto manager.      (line 2276)
-* BFD_RELOC_CRX_ABS32:                   howto manager.      (line 2277)
-* BFD_RELOC_CRX_IMM16:                   howto manager.      (line 2281)
-* BFD_RELOC_CRX_IMM32:                   howto manager.      (line 2282)
-* BFD_RELOC_CRX_NUM16:                   howto manager.      (line 2279)
-* BFD_RELOC_CRX_NUM32:                   howto manager.      (line 2280)
-* BFD_RELOC_CRX_NUM8:                    howto manager.      (line 2278)
-* BFD_RELOC_CRX_REGREL12:                howto manager.      (line 2272)
-* BFD_RELOC_CRX_REGREL22:                howto manager.      (line 2273)
-* BFD_RELOC_CRX_REGREL28:                howto manager.      (line 2274)
-* BFD_RELOC_CRX_REGREL32:                howto manager.      (line 2275)
-* BFD_RELOC_CRX_REL16:                   howto manager.      (line 2269)
-* BFD_RELOC_CRX_REL24:                   howto manager.      (line 2270)
-* BFD_RELOC_CRX_REL32:                   howto manager.      (line 2271)
-* BFD_RELOC_CRX_REL4:                    howto manager.      (line 2266)
-* BFD_RELOC_CRX_REL8:                    howto manager.      (line 2267)
-* BFD_RELOC_CRX_REL8_CMP:                howto manager.      (line 2268)
-* BFD_RELOC_CRX_SWITCH16:                howto manager.      (line 2284)
-* BFD_RELOC_CRX_SWITCH32:                howto manager.      (line 2285)
-* BFD_RELOC_CRX_SWITCH8:                 howto manager.      (line 2283)
-* BFD_RELOC_CTOR:                        howto manager.      (line  774)
-* BFD_RELOC_D10V_10_PCREL_L:             howto manager.      (line 1169)
-* BFD_RELOC_D10V_10_PCREL_R:             howto manager.      (line 1165)
-* BFD_RELOC_D10V_18:                     howto manager.      (line 1174)
-* BFD_RELOC_D10V_18_PCREL:               howto manager.      (line 1177)
-* BFD_RELOC_D30V_15:                     howto manager.      (line 1192)
-* BFD_RELOC_D30V_15_PCREL:               howto manager.      (line 1196)
-* BFD_RELOC_D30V_15_PCREL_R:             howto manager.      (line 1200)
-* BFD_RELOC_D30V_21:                     howto manager.      (line 1205)
-* BFD_RELOC_D30V_21_PCREL:               howto manager.      (line 1209)
-* BFD_RELOC_D30V_21_PCREL_R:             howto manager.      (line 1213)
-* BFD_RELOC_D30V_32:                     howto manager.      (line 1218)
-* BFD_RELOC_D30V_32_PCREL:               howto manager.      (line 1221)
-* BFD_RELOC_D30V_6:                      howto manager.      (line 1180)
-* BFD_RELOC_D30V_9_PCREL:                howto manager.      (line 1183)
-* BFD_RELOC_D30V_9_PCREL_R:              howto manager.      (line 1187)
-* BFD_RELOC_DLX_HI16_S:                  howto manager.      (line 1224)
-* BFD_RELOC_DLX_JMP26:                   howto manager.      (line 1230)
-* BFD_RELOC_DLX_LO16:                    howto manager.      (line 1227)
-* BFD_RELOC_EPIPHANY_HIGH:               howto manager.      (line 3135)
-* BFD_RELOC_EPIPHANY_IMM11:              howto manager.      (line 3144)
-* BFD_RELOC_EPIPHANY_IMM8:               howto manager.      (line 3148)
-* BFD_RELOC_EPIPHANY_LOW:                howto manager.      (line 3138)
-* BFD_RELOC_EPIPHANY_SIMM11:             howto manager.      (line 3141)
-* BFD_RELOC_EPIPHANY_SIMM24:             howto manager.      (line 3132)
-* BFD_RELOC_EPIPHANY_SIMM8:              howto manager.      (line 3129)
-* BFD_RELOC_FR30_10_IN_8:                howto manager.      (line 1499)
-* BFD_RELOC_FR30_12_PCREL:               howto manager.      (line 1507)
-* BFD_RELOC_FR30_20:                     howto manager.      (line 1483)
-* BFD_RELOC_FR30_48:                     howto manager.      (line 1480)
-* BFD_RELOC_FR30_6_IN_4:                 howto manager.      (line 1487)
-* BFD_RELOC_FR30_8_IN_8:                 howto manager.      (line 1491)
-* BFD_RELOC_FR30_9_IN_8:                 howto manager.      (line 1495)
-* BFD_RELOC_FR30_9_PCREL:                howto manager.      (line 1503)
-* BFD_RELOC_FRV_FUNCDESC:                howto manager.      (line  490)
-* BFD_RELOC_FRV_FUNCDESC_GOT12:          howto manager.      (line  491)
-* BFD_RELOC_FRV_FUNCDESC_GOTHI:          howto manager.      (line  492)
-* BFD_RELOC_FRV_FUNCDESC_GOTLO:          howto manager.      (line  493)
-* BFD_RELOC_FRV_FUNCDESC_GOTOFF12:       howto manager.      (line  495)
-* BFD_RELOC_FRV_FUNCDESC_GOTOFFHI:       howto manager.      (line  496)
-* BFD_RELOC_FRV_FUNCDESC_GOTOFFLO:       howto manager.      (line  497)
-* BFD_RELOC_FRV_FUNCDESC_VALUE:          howto manager.      (line  494)
-* BFD_RELOC_FRV_GETTLSOFF:               howto manager.      (line  501)
-* BFD_RELOC_FRV_GETTLSOFF_RELAX:         howto manager.      (line  514)
-* BFD_RELOC_FRV_GOT12:                   howto manager.      (line  487)
-* BFD_RELOC_FRV_GOTHI:                   howto manager.      (line  488)
-* BFD_RELOC_FRV_GOTLO:                   howto manager.      (line  489)
-* BFD_RELOC_FRV_GOTOFF12:                howto manager.      (line  498)
-* BFD_RELOC_FRV_GOTOFFHI:                howto manager.      (line  499)
-* BFD_RELOC_FRV_GOTOFFLO:                howto manager.      (line  500)
-* BFD_RELOC_FRV_GOTTLSDESC12:            howto manager.      (line  503)
-* BFD_RELOC_FRV_GOTTLSDESCHI:            howto manager.      (line  504)
-* BFD_RELOC_FRV_GOTTLSDESCLO:            howto manager.      (line  505)
-* BFD_RELOC_FRV_GOTTLSOFF12:             howto manager.      (line  509)
-* BFD_RELOC_FRV_GOTTLSOFFHI:             howto manager.      (line  510)
-* BFD_RELOC_FRV_GOTTLSOFFLO:             howto manager.      (line  511)
-* BFD_RELOC_FRV_GPREL12:                 howto manager.      (line  482)
-* BFD_RELOC_FRV_GPREL32:                 howto manager.      (line  484)
-* BFD_RELOC_FRV_GPRELHI:                 howto manager.      (line  485)
-* BFD_RELOC_FRV_GPRELLO:                 howto manager.      (line  486)
-* BFD_RELOC_FRV_GPRELU12:                howto manager.      (line  483)
-* BFD_RELOC_FRV_HI16:                    howto manager.      (line  481)
-* BFD_RELOC_FRV_LABEL16:                 howto manager.      (line  478)
-* BFD_RELOC_FRV_LABEL24:                 howto manager.      (line  479)
-* BFD_RELOC_FRV_LO16:                    howto manager.      (line  480)
-* BFD_RELOC_FRV_TLSDESC_RELAX:           howto manager.      (line  513)
-* BFD_RELOC_FRV_TLSDESC_VALUE:           howto manager.      (line  502)
-* BFD_RELOC_FRV_TLSMOFF:                 howto manager.      (line  516)
-* BFD_RELOC_FRV_TLSMOFF12:               howto manager.      (line  506)
-* BFD_RELOC_FRV_TLSMOFFHI:               howto manager.      (line  507)
-* BFD_RELOC_FRV_TLSMOFFLO:               howto manager.      (line  508)
-* BFD_RELOC_FRV_TLSOFF:                  howto manager.      (line  512)
-* BFD_RELOC_FRV_TLSOFF_RELAX:            howto manager.      (line  515)
-* BFD_RELOC_GPREL16:                     howto manager.      (line  125)
-* BFD_RELOC_GPREL32:                     howto manager.      (line  126)
-* BFD_RELOC_H8_DIR16A8:                  howto manager.      (line 2381)
-* BFD_RELOC_H8_DIR16R8:                  howto manager.      (line 2382)
-* BFD_RELOC_H8_DIR24A8:                  howto manager.      (line 2383)
-* BFD_RELOC_H8_DIR24R8:                  howto manager.      (line 2384)
-* BFD_RELOC_H8_DIR32A16:                 howto manager.      (line 2385)
-* BFD_RELOC_H8_DISP32A16:                howto manager.      (line 2386)
-* BFD_RELOC_HI16:                        howto manager.      (line  352)
-* BFD_RELOC_HI16_BASEREL:                howto manager.      (line  101)
-* BFD_RELOC_HI16_GOTOFF:                 howto manager.      (line   57)
-* BFD_RELOC_HI16_PCREL:                  howto manager.      (line  364)
-* BFD_RELOC_HI16_PLTOFF:                 howto manager.      (line   69)
-* BFD_RELOC_HI16_S:                      howto manager.      (line  355)
-* BFD_RELOC_HI16_S_BASEREL:              howto manager.      (line  102)
-* BFD_RELOC_HI16_S_GOTOFF:               howto manager.      (line   58)
-* BFD_RELOC_HI16_S_PCREL:                howto manager.      (line  367)
-* BFD_RELOC_HI16_S_PLTOFF:               howto manager.      (line   70)
-* BFD_RELOC_HI22:                        howto manager.      (line  120)
-* BFD_RELOC_I370_D12:                    howto manager.      (line  771)
-* BFD_RELOC_I960_CALLJ:                  howto manager.      (line  132)
-* BFD_RELOC_IA64_COPY:                   howto manager.      (line 2063)
-* BFD_RELOC_IA64_DIR32LSB:               howto manager.      (line 2008)
-* BFD_RELOC_IA64_DIR32MSB:               howto manager.      (line 2007)
-* BFD_RELOC_IA64_DIR64LSB:               howto manager.      (line 2010)
-* BFD_RELOC_IA64_DIR64MSB:               howto manager.      (line 2009)
-* BFD_RELOC_IA64_DTPMOD64LSB:            howto manager.      (line 2073)
-* BFD_RELOC_IA64_DTPMOD64MSB:            howto manager.      (line 2072)
-* BFD_RELOC_IA64_DTPREL14:               howto manager.      (line 2075)
-* BFD_RELOC_IA64_DTPREL22:               howto manager.      (line 2076)
-* BFD_RELOC_IA64_DTPREL32LSB:            howto manager.      (line 2079)
-* BFD_RELOC_IA64_DTPREL32MSB:            howto manager.      (line 2078)
-* BFD_RELOC_IA64_DTPREL64I:              howto manager.      (line 2077)
-* BFD_RELOC_IA64_DTPREL64LSB:            howto manager.      (line 2081)
-* BFD_RELOC_IA64_DTPREL64MSB:            howto manager.      (line 2080)
-* BFD_RELOC_IA64_FPTR32LSB:              howto manager.      (line 2025)
-* BFD_RELOC_IA64_FPTR32MSB:              howto manager.      (line 2024)
-* BFD_RELOC_IA64_FPTR64I:                howto manager.      (line 2023)
-* BFD_RELOC_IA64_FPTR64LSB:              howto manager.      (line 2027)
-* BFD_RELOC_IA64_FPTR64MSB:              howto manager.      (line 2026)
-* BFD_RELOC_IA64_GPREL22:                howto manager.      (line 2011)
-* BFD_RELOC_IA64_GPREL32LSB:             howto manager.      (line 2014)
-* BFD_RELOC_IA64_GPREL32MSB:             howto manager.      (line 2013)
-* BFD_RELOC_IA64_GPREL64I:               howto manager.      (line 2012)
-* BFD_RELOC_IA64_GPREL64LSB:             howto manager.      (line 2016)
-* BFD_RELOC_IA64_GPREL64MSB:             howto manager.      (line 2015)
-* BFD_RELOC_IA64_IMM14:                  howto manager.      (line 2004)
-* BFD_RELOC_IA64_IMM22:                  howto manager.      (line 2005)
-* BFD_RELOC_IA64_IMM64:                  howto manager.      (line 2006)
-* BFD_RELOC_IA64_IPLTLSB:                howto manager.      (line 2062)
-* BFD_RELOC_IA64_IPLTMSB:                howto manager.      (line 2061)
-* BFD_RELOC_IA64_LDXMOV:                 howto manager.      (line 2065)
-* BFD_RELOC_IA64_LTOFF22:                howto manager.      (line 2017)
-* BFD_RELOC_IA64_LTOFF22X:               howto manager.      (line 2064)
-* BFD_RELOC_IA64_LTOFF64I:               howto manager.      (line 2018)
-* BFD_RELOC_IA64_LTOFF_DTPMOD22:         howto manager.      (line 2074)
-* BFD_RELOC_IA64_LTOFF_DTPREL22:         howto manager.      (line 2082)
-* BFD_RELOC_IA64_LTOFF_FPTR22:           howto manager.      (line 2039)
-* BFD_RELOC_IA64_LTOFF_FPTR32LSB:        howto manager.      (line 2042)
-* BFD_RELOC_IA64_LTOFF_FPTR32MSB:        howto manager.      (line 2041)
-* BFD_RELOC_IA64_LTOFF_FPTR64I:          howto manager.      (line 2040)
-* BFD_RELOC_IA64_LTOFF_FPTR64LSB:        howto manager.      (line 2044)
-* BFD_RELOC_IA64_LTOFF_FPTR64MSB:        howto manager.      (line 2043)
-* BFD_RELOC_IA64_LTOFF_TPREL22:          howto manager.      (line 2071)
-* BFD_RELOC_IA64_LTV32LSB:               howto manager.      (line 2058)
-* BFD_RELOC_IA64_LTV32MSB:               howto manager.      (line 2057)
-* BFD_RELOC_IA64_LTV64LSB:               howto manager.      (line 2060)
-* BFD_RELOC_IA64_LTV64MSB:               howto manager.      (line 2059)
-* BFD_RELOC_IA64_PCREL21B:               howto manager.      (line 2028)
-* BFD_RELOC_IA64_PCREL21BI:              howto manager.      (line 2029)
-* BFD_RELOC_IA64_PCREL21F:               howto manager.      (line 2031)
-* BFD_RELOC_IA64_PCREL21M:               howto manager.      (line 2030)
-* BFD_RELOC_IA64_PCREL22:                howto manager.      (line 2032)
-* BFD_RELOC_IA64_PCREL32LSB:             howto manager.      (line 2036)
-* BFD_RELOC_IA64_PCREL32MSB:             howto manager.      (line 2035)
-* BFD_RELOC_IA64_PCREL60B:               howto manager.      (line 2033)
-* BFD_RELOC_IA64_PCREL64I:               howto manager.      (line 2034)
-* BFD_RELOC_IA64_PCREL64LSB:             howto manager.      (line 2038)
-* BFD_RELOC_IA64_PCREL64MSB:             howto manager.      (line 2037)
-* BFD_RELOC_IA64_PLTOFF22:               howto manager.      (line 2019)
-* BFD_RELOC_IA64_PLTOFF64I:              howto manager.      (line 2020)
-* BFD_RELOC_IA64_PLTOFF64LSB:            howto manager.      (line 2022)
-* BFD_RELOC_IA64_PLTOFF64MSB:            howto manager.      (line 2021)
-* BFD_RELOC_IA64_REL32LSB:               howto manager.      (line 2054)
-* BFD_RELOC_IA64_REL32MSB:               howto manager.      (line 2053)
-* BFD_RELOC_IA64_REL64LSB:               howto manager.      (line 2056)
-* BFD_RELOC_IA64_REL64MSB:               howto manager.      (line 2055)
-* BFD_RELOC_IA64_SECREL32LSB:            howto manager.      (line 2050)
-* BFD_RELOC_IA64_SECREL32MSB:            howto manager.      (line 2049)
-* BFD_RELOC_IA64_SECREL64LSB:            howto manager.      (line 2052)
-* BFD_RELOC_IA64_SECREL64MSB:            howto manager.      (line 2051)
-* BFD_RELOC_IA64_SEGREL32LSB:            howto manager.      (line 2046)
-* BFD_RELOC_IA64_SEGREL32MSB:            howto manager.      (line 2045)
-* BFD_RELOC_IA64_SEGREL64LSB:            howto manager.      (line 2048)
-* BFD_RELOC_IA64_SEGREL64MSB:            howto manager.      (line 2047)
-* BFD_RELOC_IA64_TPREL14:                howto manager.      (line 2066)
-* BFD_RELOC_IA64_TPREL22:                howto manager.      (line 2067)
-* BFD_RELOC_IA64_TPREL64I:               howto manager.      (line 2068)
-* BFD_RELOC_IA64_TPREL64LSB:             howto manager.      (line 2070)
-* BFD_RELOC_IA64_TPREL64MSB:             howto manager.      (line 2069)
-* BFD_RELOC_IP2K_ADDR16CJP:              howto manager.      (line 1956)
-* BFD_RELOC_IP2K_BANK:                   howto manager.      (line 1953)
-* BFD_RELOC_IP2K_EX8DATA:                howto manager.      (line 1964)
-* BFD_RELOC_IP2K_FR9:                    howto manager.      (line 1950)
-* BFD_RELOC_IP2K_FR_OFFSET:              howto manager.      (line 1977)
-* BFD_RELOC_IP2K_HI8DATA:                howto manager.      (line 1963)
-* BFD_RELOC_IP2K_HI8INSN:                howto manager.      (line 1968)
-* BFD_RELOC_IP2K_LO8DATA:                howto manager.      (line 1962)
-* BFD_RELOC_IP2K_LO8INSN:                howto manager.      (line 1967)
-* BFD_RELOC_IP2K_PAGE3:                  howto manager.      (line 1959)
-* BFD_RELOC_IP2K_PC_SKIP:                howto manager.      (line 1971)
-* BFD_RELOC_IP2K_TEXT:                   howto manager.      (line 1974)
-* BFD_RELOC_IQ2000_OFFSET_16:            howto manager.      (line 2472)
-* BFD_RELOC_IQ2000_OFFSET_21:            howto manager.      (line 2473)
-* BFD_RELOC_IQ2000_UHI16:                howto manager.      (line 2474)
-* BFD_RELOC_LM32_16_GOT:                 howto manager.      (line 2579)
-* BFD_RELOC_LM32_BRANCH:                 howto manager.      (line 2578)
-* BFD_RELOC_LM32_CALL:                   howto manager.      (line 2577)
-* BFD_RELOC_LM32_COPY:                   howto manager.      (line 2582)
-* BFD_RELOC_LM32_GLOB_DAT:               howto manager.      (line 2583)
-* BFD_RELOC_LM32_GOTOFF_HI16:            howto manager.      (line 2580)
-* BFD_RELOC_LM32_GOTOFF_LO16:            howto manager.      (line 2581)
-* BFD_RELOC_LM32_JMP_SLOT:               howto manager.      (line 2584)
-* BFD_RELOC_LM32_RELATIVE:               howto manager.      (line 2585)
-* BFD_RELOC_LO10:                        howto manager.      (line  121)
-* BFD_RELOC_LO16:                        howto manager.      (line  361)
-* BFD_RELOC_LO16_BASEREL:                howto manager.      (line  100)
-* BFD_RELOC_LO16_GOTOFF:                 howto manager.      (line   56)
-* BFD_RELOC_LO16_PCREL:                  howto manager.      (line  370)
-* BFD_RELOC_LO16_PLTOFF:                 howto manager.      (line   68)
-* BFD_RELOC_M32C_HI8:                    howto manager.      (line 1233)
-* BFD_RELOC_M32C_RL_1ADDR:               howto manager.      (line 1235)
-* BFD_RELOC_M32C_RL_2ADDR:               howto manager.      (line 1236)
-* BFD_RELOC_M32C_RL_JUMP:                howto manager.      (line 1234)
-* BFD_RELOC_M32R_10_PCREL:               howto manager.      (line 1243)
-* BFD_RELOC_M32R_18_PCREL:               howto manager.      (line 1247)
-* BFD_RELOC_M32R_24:                     howto manager.      (line 1239)
-* BFD_RELOC_M32R_26_PCREL:               howto manager.      (line 1250)
-* BFD_RELOC_M32R_26_PLTREL:              howto manager.      (line 1269)
-* BFD_RELOC_M32R_COPY:                   howto manager.      (line 1270)
-* BFD_RELOC_M32R_GLOB_DAT:               howto manager.      (line 1271)
-* BFD_RELOC_M32R_GOT16_HI_SLO:           howto manager.      (line 1280)
-* BFD_RELOC_M32R_GOT16_HI_ULO:           howto manager.      (line 1279)
-* BFD_RELOC_M32R_GOT16_LO:               howto manager.      (line 1281)
-* BFD_RELOC_M32R_GOT24:                  howto manager.      (line 1268)
-* BFD_RELOC_M32R_GOTOFF:                 howto manager.      (line 1274)
-* BFD_RELOC_M32R_GOTOFF_HI_SLO:          howto manager.      (line 1276)
-* BFD_RELOC_M32R_GOTOFF_HI_ULO:          howto manager.      (line 1275)
-* BFD_RELOC_M32R_GOTOFF_LO:              howto manager.      (line 1277)
-* BFD_RELOC_M32R_GOTPC24:                howto manager.      (line 1278)
-* BFD_RELOC_M32R_GOTPC_HI_SLO:           howto manager.      (line 1283)
-* BFD_RELOC_M32R_GOTPC_HI_ULO:           howto manager.      (line 1282)
-* BFD_RELOC_M32R_GOTPC_LO:               howto manager.      (line 1284)
-* BFD_RELOC_M32R_HI16_SLO:               howto manager.      (line 1257)
-* BFD_RELOC_M32R_HI16_ULO:               howto manager.      (line 1253)
-* BFD_RELOC_M32R_JMP_SLOT:               howto manager.      (line 1272)
-* BFD_RELOC_M32R_LO16:                   howto manager.      (line 1261)
-* BFD_RELOC_M32R_RELATIVE:               howto manager.      (line 1273)
-* BFD_RELOC_M32R_SDA16:                  howto manager.      (line 1264)
-* BFD_RELOC_M68HC11_24:                  howto manager.      (line 2118)
-* BFD_RELOC_M68HC11_3B:                  howto manager.      (line 2093)
-* BFD_RELOC_M68HC11_HI8:                 howto manager.      (line 2085)
-* BFD_RELOC_M68HC11_LO16:                howto manager.      (line 2107)
-* BFD_RELOC_M68HC11_LO8:                 howto manager.      (line 2089)
-* BFD_RELOC_M68HC11_PAGE:                howto manager.      (line 2113)
-* BFD_RELOC_M68HC11_RL_GROUP:            howto manager.      (line 2102)
-* BFD_RELOC_M68HC11_RL_JUMP:             howto manager.      (line 2096)
-* BFD_RELOC_M68HC12_10_PCREL:            howto manager.      (line 2178)
-* BFD_RELOC_M68HC12_16B:                 howto manager.      (line 2172)
-* BFD_RELOC_M68HC12_5B:                  howto manager.      (line 2124)
-* BFD_RELOC_M68HC12_9_PCREL:             howto manager.      (line 2175)
-* BFD_RELOC_M68HC12_9B:                  howto manager.      (line 2169)
-* BFD_RELOC_M68HC12_HI8XG:               howto manager.      (line 2185)
-* BFD_RELOC_M68HC12_LO8XG:               howto manager.      (line 2181)
-* BFD_RELOC_MACH_O_LOCAL_SECTDIFF:       howto manager.      (line 2592)
-* BFD_RELOC_MACH_O_PAIR:                 howto manager.      (line 2595)
-* BFD_RELOC_MACH_O_SECTDIFF:             howto manager.      (line 2588)
-* BFD_RELOC_MACH_O_X86_64_BRANCH32:      howto manager.      (line 2598)
-* BFD_RELOC_MACH_O_X86_64_BRANCH8:       howto manager.      (line 2599)
-* BFD_RELOC_MACH_O_X86_64_GOT:           howto manager.      (line 2603)
-* BFD_RELOC_MACH_O_X86_64_GOT_LOAD:      howto manager.      (line 2606)
-* BFD_RELOC_MACH_O_X86_64_PCREL32_1:     howto manager.      (line 2616)
-* BFD_RELOC_MACH_O_X86_64_PCREL32_2:     howto manager.      (line 2619)
-* BFD_RELOC_MACH_O_X86_64_PCREL32_4:     howto manager.      (line 2622)
-* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32:  howto manager.      (line 2610)
-* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64:  howto manager.      (line 2613)
-* BFD_RELOC_MCORE_PCREL_32:              howto manager.      (line 1514)
-* BFD_RELOC_MCORE_PCREL_IMM11BY2:        howto manager.      (line 1512)
-* BFD_RELOC_MCORE_PCREL_IMM4BY2:         howto manager.      (line 1513)
-* BFD_RELOC_MCORE_PCREL_IMM8BY4:         howto manager.      (line 1511)
-* BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2:    howto manager.      (line 1515)
-* BFD_RELOC_MCORE_RVA:                   howto manager.      (line 1516)
-* BFD_RELOC_MEP_16:                      howto manager.      (line 1520)
-* BFD_RELOC_MEP_32:                      howto manager.      (line 1521)
-* BFD_RELOC_MEP_8:                       howto manager.      (line 1519)
-* BFD_RELOC_MEP_ADDR24A4:                howto manager.      (line 1536)
-* BFD_RELOC_MEP_GNU_VTENTRY:             howto manager.      (line 1538)
-* BFD_RELOC_MEP_GNU_VTINHERIT:           howto manager.      (line 1537)
-* BFD_RELOC_MEP_GPREL:                   howto manager.      (line 1530)
-* BFD_RELOC_MEP_HI16S:                   howto manager.      (line 1529)
-* BFD_RELOC_MEP_HI16U:                   howto manager.      (line 1528)
-* BFD_RELOC_MEP_LOW16:                   howto manager.      (line 1527)
-* BFD_RELOC_MEP_PCABS24A2:               howto manager.      (line 1526)
-* BFD_RELOC_MEP_PCREL12A2:               howto manager.      (line 1523)
-* BFD_RELOC_MEP_PCREL17A2:               howto manager.      (line 1524)
-* BFD_RELOC_MEP_PCREL24A2:               howto manager.      (line 1525)
-* BFD_RELOC_MEP_PCREL8A2:                howto manager.      (line 1522)
-* BFD_RELOC_MEP_TPREL:                   howto manager.      (line 1531)
-* BFD_RELOC_MEP_TPREL7:                  howto manager.      (line 1532)
-* BFD_RELOC_MEP_TPREL7A2:                howto manager.      (line 1533)
-* BFD_RELOC_MEP_TPREL7A4:                howto manager.      (line 1534)
-* BFD_RELOC_MEP_UIMM24:                  howto manager.      (line 1535)
-* BFD_RELOC_METAG_COPY:                  howto manager.      (line 1560)
-* BFD_RELOC_METAG_GETSET_GOT:            howto manager.      (line 1552)
-* BFD_RELOC_METAG_GETSET_GOTOFF:         howto manager.      (line 1551)
-* BFD_RELOC_METAG_GETSETOFF:             howto manager.      (line 1544)
-* BFD_RELOC_METAG_GLOB_DAT:              howto manager.      (line 1563)
-* BFD_RELOC_METAG_GOTOFF:                howto manager.      (line 1558)
-* BFD_RELOC_METAG_HI16_GOTOFF:           howto manager.      (line 1549)
-* BFD_RELOC_METAG_HI16_GOTPC:            howto manager.      (line 1553)
-* BFD_RELOC_METAG_HI16_PLT:              howto manager.      (line 1555)
-* BFD_RELOC_METAG_HIADDR16:              howto manager.      (line 1541)
-* BFD_RELOC_METAG_HIOG:                  howto manager.      (line 1545)
-* BFD_RELOC_METAG_JMP_SLOT:              howto manager.      (line 1561)
-* BFD_RELOC_METAG_LO16_GOTOFF:           howto manager.      (line 1550)
-* BFD_RELOC_METAG_LO16_GOTPC:            howto manager.      (line 1554)
-* BFD_RELOC_METAG_LO16_PLT:              howto manager.      (line 1556)
-* BFD_RELOC_METAG_LOADDR16:              howto manager.      (line 1542)
-* BFD_RELOC_METAG_LOOG:                  howto manager.      (line 1546)
-* BFD_RELOC_METAG_PLT:                   howto manager.      (line 1559)
-* BFD_RELOC_METAG_REL16:                 howto manager.      (line 1548)
-* BFD_RELOC_METAG_REL8:                  howto manager.      (line 1547)
-* BFD_RELOC_METAG_RELATIVE:              howto manager.      (line 1562)
-* BFD_RELOC_METAG_RELBRANCH:             howto manager.      (line 1543)
-* BFD_RELOC_METAG_RELBRANCH_PLT:         howto manager.      (line 1557)
-* BFD_RELOC_METAG_TLS_DTPMOD:            howto manager.      (line 1574)
-* BFD_RELOC_METAG_TLS_DTPOFF:            howto manager.      (line 1575)
-* BFD_RELOC_METAG_TLS_GD:                howto manager.      (line 1564)
-* BFD_RELOC_METAG_TLS_IE:                howto manager.      (line 1569)
-* BFD_RELOC_METAG_TLS_IENONPIC:          howto manager.      (line 1570)
-* BFD_RELOC_METAG_TLS_IENONPIC_HI16:     howto manager.      (line 1571)
-* BFD_RELOC_METAG_TLS_IENONPIC_LO16:     howto manager.      (line 1572)
-* BFD_RELOC_METAG_TLS_LDM:               howto manager.      (line 1565)
-* BFD_RELOC_METAG_TLS_LDO:               howto manager.      (line 1568)
-* BFD_RELOC_METAG_TLS_LDO_HI16:          howto manager.      (line 1566)
-* BFD_RELOC_METAG_TLS_LDO_LO16:          howto manager.      (line 1567)
-* BFD_RELOC_METAG_TLS_LE:                howto manager.      (line 1576)
-* BFD_RELOC_METAG_TLS_LE_HI16:           howto manager.      (line 1577)
-* BFD_RELOC_METAG_TLS_LE_LO16:           howto manager.      (line 1578)
-* BFD_RELOC_METAG_TLS_TPOFF:             howto manager.      (line 1573)
-* BFD_RELOC_MICROBLAZE_32_GOTOFF:        howto manager.      (line 2669)
-* BFD_RELOC_MICROBLAZE_32_LO:            howto manager.      (line 2625)
-* BFD_RELOC_MICROBLAZE_32_LO_PCREL:      howto manager.      (line 2629)
-* BFD_RELOC_MICROBLAZE_32_ROSDA:         howto manager.      (line 2633)
-* BFD_RELOC_MICROBLAZE_32_RWSDA:         howto manager.      (line 2637)
-* BFD_RELOC_MICROBLAZE_32_SYM_OP_SYM:    howto manager.      (line 2641)
-* BFD_RELOC_MICROBLAZE_32_TLSDTPMOD:     howto manager.      (line 2690)
-* BFD_RELOC_MICROBLAZE_32_TLSDTPREL:     howto manager.      (line 2693)
-* BFD_RELOC_MICROBLAZE_64_GOT:           howto manager.      (line 2655)
-* BFD_RELOC_MICROBLAZE_64_GOTOFF:        howto manager.      (line 2664)
-* BFD_RELOC_MICROBLAZE_64_GOTPC:         howto manager.      (line 2650)
-* BFD_RELOC_MICROBLAZE_64_NONE:          howto manager.      (line 2645)
-* BFD_RELOC_MICROBLAZE_64_PLT:           howto manager.      (line 2659)
-* BFD_RELOC_MICROBLAZE_64_TLS:           howto manager.      (line 2677)
-* BFD_RELOC_MICROBLAZE_64_TLSDTPREL:     howto manager.      (line 2696)
-* BFD_RELOC_MICROBLAZE_64_TLSGD:         howto manager.      (line 2680)
-* BFD_RELOC_MICROBLAZE_64_TLSGOTTPREL:   howto manager.      (line 2700)
-* BFD_RELOC_MICROBLAZE_64_TLSLD:         howto manager.      (line 2685)
-* BFD_RELOC_MICROBLAZE_64_TLSTPREL:      howto manager.      (line 2704)
-* BFD_RELOC_MICROBLAZE_COPY:             howto manager.      (line 2673)
-* BFD_RELOC_MICROMIPS_10_PCREL_S1:       howto manager.      (line  404)
-* BFD_RELOC_MICROMIPS_16_PCREL_S1:       howto manager.      (line  405)
-* BFD_RELOC_MICROMIPS_7_PCREL_S1:        howto manager.      (line  403)
-* BFD_RELOC_MICROMIPS_CALL16:            howto manager.      (line  417)
-* BFD_RELOC_MICROMIPS_CALL_HI16:         howto manager.      (line  423)
-* BFD_RELOC_MICROMIPS_CALL_LO16:         howto manager.      (line  425)
-* BFD_RELOC_MICROMIPS_GOT16:             howto manager.      (line  415)
-* BFD_RELOC_MICROMIPS_GOT_DISP:          howto manager.      (line  433)
-* BFD_RELOC_MICROMIPS_GOT_HI16:          howto manager.      (line  419)
-* BFD_RELOC_MICROMIPS_GOT_LO16:          howto manager.      (line  421)
-* BFD_RELOC_MICROMIPS_GOT_OFST:          howto manager.      (line  431)
-* BFD_RELOC_MICROMIPS_GOT_PAGE:          howto manager.      (line  429)
-* BFD_RELOC_MICROMIPS_GPREL16:           howto manager.      (line  408)
-* BFD_RELOC_MICROMIPS_HI16:              howto manager.      (line  409)
-* BFD_RELOC_MICROMIPS_HI16_S:            howto manager.      (line  410)
-* BFD_RELOC_MICROMIPS_HIGHER:            howto manager.      (line  442)
-* BFD_RELOC_MICROMIPS_HIGHEST:           howto manager.      (line  440)
-* BFD_RELOC_MICROMIPS_JALR:              howto manager.      (line  448)
-* BFD_RELOC_MICROMIPS_JMP:               howto manager.      (line  343)
-* BFD_RELOC_MICROMIPS_LITERAL:           howto manager.      (line  400)
-* BFD_RELOC_MICROMIPS_LO16:              howto manager.      (line  411)
-* BFD_RELOC_MICROMIPS_SCN_DISP:          howto manager.      (line  444)
-* BFD_RELOC_MICROMIPS_SUB:               howto manager.      (line  427)
-* BFD_RELOC_MICROMIPS_TLS_DTPREL_HI16:   howto manager.      (line  458)
-* BFD_RELOC_MICROMIPS_TLS_DTPREL_LO16:   howto manager.      (line  460)
-* BFD_RELOC_MICROMIPS_TLS_GD:            howto manager.      (line  454)
-* BFD_RELOC_MICROMIPS_TLS_GOTTPREL:      howto manager.      (line  462)
-* BFD_RELOC_MICROMIPS_TLS_LDM:           howto manager.      (line  456)
-* BFD_RELOC_MICROMIPS_TLS_TPREL_HI16:    howto manager.      (line  466)
-* BFD_RELOC_MICROMIPS_TLS_TPREL_LO16:    howto manager.      (line  468)
-* BFD_RELOC_MIPS16_CALL16:               howto manager.      (line  374)
-* BFD_RELOC_MIPS16_GOT16:                howto manager.      (line  373)
-* BFD_RELOC_MIPS16_GPREL:                howto manager.      (line  349)
-* BFD_RELOC_MIPS16_HI16:                 howto manager.      (line  378)
-* BFD_RELOC_MIPS16_HI16_S:               howto manager.      (line  381)
-* BFD_RELOC_MIPS16_JMP:                  howto manager.      (line  346)
-* BFD_RELOC_MIPS16_LO16:                 howto manager.      (line  387)
-* BFD_RELOC_MIPS16_TLS_DTPREL_HI16:      howto manager.      (line  392)
-* BFD_RELOC_MIPS16_TLS_DTPREL_LO16:      howto manager.      (line  393)
-* BFD_RELOC_MIPS16_TLS_GD:               howto manager.      (line  390)
-* BFD_RELOC_MIPS16_TLS_GOTTPREL:         howto manager.      (line  394)
-* BFD_RELOC_MIPS16_TLS_LDM:              howto manager.      (line  391)
-* BFD_RELOC_MIPS16_TLS_TPREL_HI16:       howto manager.      (line  395)
-* BFD_RELOC_MIPS16_TLS_TPREL_LO16:       howto manager.      (line  396)
-* BFD_RELOC_MIPS_CALL16:                 howto manager.      (line  416)
-* BFD_RELOC_MIPS_CALL_HI16:              howto manager.      (line  422)
-* BFD_RELOC_MIPS_CALL_LO16:              howto manager.      (line  424)
-* BFD_RELOC_MIPS_COPY:                   howto manager.      (line  471)
-* BFD_RELOC_MIPS_DELETE:                 howto manager.      (line  438)
-* BFD_RELOC_MIPS_GOT16:                  howto manager.      (line  414)
-* BFD_RELOC_MIPS_GOT_DISP:               howto manager.      (line  432)
-* BFD_RELOC_MIPS_GOT_HI16:               howto manager.      (line  418)
-* BFD_RELOC_MIPS_GOT_LO16:               howto manager.      (line  420)
-* BFD_RELOC_MIPS_GOT_OFST:               howto manager.      (line  430)
-* BFD_RELOC_MIPS_GOT_PAGE:               howto manager.      (line  428)
-* BFD_RELOC_MIPS_HIGHER:                 howto manager.      (line  441)
-* BFD_RELOC_MIPS_HIGHEST:                howto manager.      (line  439)
-* BFD_RELOC_MIPS_INSERT_A:               howto manager.      (line  436)
-* BFD_RELOC_MIPS_INSERT_B:               howto manager.      (line  437)
-* BFD_RELOC_MIPS_JALR:                   howto manager.      (line  447)
-* BFD_RELOC_MIPS_JMP:                    howto manager.      (line  342)
-* BFD_RELOC_MIPS_JUMP_SLOT:              howto manager.      (line  472)
-* BFD_RELOC_MIPS_LITERAL:                howto manager.      (line  399)
-* BFD_RELOC_MIPS_REL16:                  howto manager.      (line  445)
-* BFD_RELOC_MIPS_RELGOT:                 howto manager.      (line  446)
-* BFD_RELOC_MIPS_SCN_DISP:               howto manager.      (line  443)
-* BFD_RELOC_MIPS_SHIFT5:                 howto manager.      (line  434)
-* BFD_RELOC_MIPS_SHIFT6:                 howto manager.      (line  435)
-* BFD_RELOC_MIPS_SUB:                    howto manager.      (line  426)
-* BFD_RELOC_MIPS_TLS_DTPMOD32:           howto manager.      (line  449)
-* BFD_RELOC_MIPS_TLS_DTPMOD64:           howto manager.      (line  451)
-* BFD_RELOC_MIPS_TLS_DTPREL32:           howto manager.      (line  450)
-* BFD_RELOC_MIPS_TLS_DTPREL64:           howto manager.      (line  452)
-* BFD_RELOC_MIPS_TLS_DTPREL_HI16:        howto manager.      (line  457)
-* BFD_RELOC_MIPS_TLS_DTPREL_LO16:        howto manager.      (line  459)
-* BFD_RELOC_MIPS_TLS_GD:                 howto manager.      (line  453)
-* BFD_RELOC_MIPS_TLS_GOTTPREL:           howto manager.      (line  461)
-* BFD_RELOC_MIPS_TLS_LDM:                howto manager.      (line  455)
-* BFD_RELOC_MIPS_TLS_TPREL32:            howto manager.      (line  463)
-* BFD_RELOC_MIPS_TLS_TPREL64:            howto manager.      (line  464)
-* BFD_RELOC_MIPS_TLS_TPREL_HI16:         howto manager.      (line  465)
-* BFD_RELOC_MIPS_TLS_TPREL_LO16:         howto manager.      (line  467)
-* BFD_RELOC_MMIX_ADDR19:                 howto manager.      (line 1607)
-* BFD_RELOC_MMIX_ADDR27:                 howto manager.      (line 1611)
-* BFD_RELOC_MMIX_BASE_PLUS_OFFSET:       howto manager.      (line 1623)
-* BFD_RELOC_MMIX_CBRANCH:                howto manager.      (line 1587)
-* BFD_RELOC_MMIX_CBRANCH_1:              howto manager.      (line 1589)
-* BFD_RELOC_MMIX_CBRANCH_2:              howto manager.      (line 1590)
-* BFD_RELOC_MMIX_CBRANCH_3:              howto manager.      (line 1591)
-* BFD_RELOC_MMIX_CBRANCH_J:              howto manager.      (line 1588)
-* BFD_RELOC_MMIX_GETA:                   howto manager.      (line 1581)
-* BFD_RELOC_MMIX_GETA_1:                 howto manager.      (line 1582)
-* BFD_RELOC_MMIX_GETA_2:                 howto manager.      (line 1583)
-* BFD_RELOC_MMIX_GETA_3:                 howto manager.      (line 1584)
-* BFD_RELOC_MMIX_JMP:                    howto manager.      (line 1601)
-* BFD_RELOC_MMIX_JMP_1:                  howto manager.      (line 1602)
-* BFD_RELOC_MMIX_JMP_2:                  howto manager.      (line 1603)
-* BFD_RELOC_MMIX_JMP_3:                  howto manager.      (line 1604)
-* BFD_RELOC_MMIX_LOCAL:                  howto manager.      (line 1627)
-* BFD_RELOC_MMIX_PUSHJ:                  howto manager.      (line 1594)
-* BFD_RELOC_MMIX_PUSHJ_1:                howto manager.      (line 1595)
-* BFD_RELOC_MMIX_PUSHJ_2:                howto manager.      (line 1596)
-* BFD_RELOC_MMIX_PUSHJ_3:                howto manager.      (line 1597)
-* BFD_RELOC_MMIX_PUSHJ_STUBBABLE:        howto manager.      (line 1598)
-* BFD_RELOC_MMIX_REG:                    howto manager.      (line 1619)
-* BFD_RELOC_MMIX_REG_OR_BYTE:            howto manager.      (line 1615)
-* BFD_RELOC_MN10300_16_PCREL:            howto manager.      (line  570)
-* BFD_RELOC_MN10300_32_PCREL:            howto manager.      (line  566)
-* BFD_RELOC_MN10300_ALIGN:               howto manager.      (line  551)
-* BFD_RELOC_MN10300_COPY:                howto manager.      (line  534)
-* BFD_RELOC_MN10300_GLOB_DAT:            howto manager.      (line  537)
-* BFD_RELOC_MN10300_GOT16:               howto manager.      (line  530)
-* BFD_RELOC_MN10300_GOT24:               howto manager.      (line  526)
-* BFD_RELOC_MN10300_GOT32:               howto manager.      (line  522)
-* BFD_RELOC_MN10300_GOTOFF24:            howto manager.      (line  519)
-* BFD_RELOC_MN10300_JMP_SLOT:            howto manager.      (line  540)
-* BFD_RELOC_MN10300_RELATIVE:            howto manager.      (line  543)
-* BFD_RELOC_MN10300_SYM_DIFF:            howto manager.      (line  546)
-* BFD_RELOC_MN10300_TLS_DTPMOD:          howto manager.      (line  561)
-* BFD_RELOC_MN10300_TLS_DTPOFF:          howto manager.      (line  562)
-* BFD_RELOC_MN10300_TLS_GD:              howto manager.      (line  555)
-* BFD_RELOC_MN10300_TLS_GOTIE:           howto manager.      (line  558)
-* BFD_RELOC_MN10300_TLS_IE:              howto manager.      (line  559)
-* BFD_RELOC_MN10300_TLS_LD:              howto manager.      (line  556)
-* BFD_RELOC_MN10300_TLS_LDO:             howto manager.      (line  557)
-* BFD_RELOC_MN10300_TLS_LE:              howto manager.      (line  560)
-* BFD_RELOC_MN10300_TLS_TPOFF:           howto manager.      (line  563)
-* BFD_RELOC_MOXIE_10_PCREL:              howto manager.      (line  475)
-* BFD_RELOC_MSP430_10_PCREL:             howto manager.      (line 2427)
-* BFD_RELOC_MSP430_16:                   howto manager.      (line 2429)
-* BFD_RELOC_MSP430_16_BYTE:              howto manager.      (line 2431)
-* BFD_RELOC_MSP430_16_PCREL:             howto manager.      (line 2428)
-* BFD_RELOC_MSP430_16_PCREL_BYTE:        howto manager.      (line 2430)
-* BFD_RELOC_MSP430_2X_PCREL:             howto manager.      (line 2432)
-* BFD_RELOC_MSP430_RL_PCREL:             howto manager.      (line 2433)
-* BFD_RELOC_MT_GNU_VTENTRY:              howto manager.      (line 2421)
-* BFD_RELOC_MT_GNU_VTINHERIT:            howto manager.      (line 2418)
-* BFD_RELOC_MT_HI16:                     howto manager.      (line 2412)
-* BFD_RELOC_MT_LO16:                     howto manager.      (line 2415)
-* BFD_RELOC_MT_PC16:                     howto manager.      (line 2409)
-* BFD_RELOC_MT_PCINSN8:                  howto manager.      (line 2424)
-* BFD_RELOC_NIOS2_ALIGN:                 howto manager.      (line 2450)
-* BFD_RELOC_NIOS2_CACHE_OPX:             howto manager.      (line 2440)
-* BFD_RELOC_NIOS2_CALL16:                howto manager.      (line 2452)
-* BFD_RELOC_NIOS2_CALL26:                howto manager.      (line 2438)
-* BFD_RELOC_NIOS2_CALLR:                 howto manager.      (line 2449)
-* BFD_RELOC_NIOS2_CJMP:                  howto manager.      (line 2448)
-* BFD_RELOC_NIOS2_COPY:                  howto manager.      (line 2465)
-* BFD_RELOC_NIOS2_GLOB_DAT:              howto manager.      (line 2466)
-* BFD_RELOC_NIOS2_GOT16:                 howto manager.      (line 2451)
-* BFD_RELOC_NIOS2_GOTOFF:                howto manager.      (line 2469)
-* BFD_RELOC_NIOS2_GOTOFF_HA:             howto manager.      (line 2454)
-* BFD_RELOC_NIOS2_GOTOFF_LO:             howto manager.      (line 2453)
-* BFD_RELOC_NIOS2_GPREL:                 howto manager.      (line 2446)
-* BFD_RELOC_NIOS2_HI16:                  howto manager.      (line 2443)
-* BFD_RELOC_NIOS2_HIADJ16:               howto manager.      (line 2445)
-* BFD_RELOC_NIOS2_IMM5:                  howto manager.      (line 2439)
-* BFD_RELOC_NIOS2_IMM6:                  howto manager.      (line 2441)
-* BFD_RELOC_NIOS2_IMM8:                  howto manager.      (line 2442)
-* BFD_RELOC_NIOS2_JUMP_SLOT:             howto manager.      (line 2467)
-* BFD_RELOC_NIOS2_LO16:                  howto manager.      (line 2444)
-* BFD_RELOC_NIOS2_PCREL_HA:              howto manager.      (line 2456)
-* BFD_RELOC_NIOS2_PCREL_LO:              howto manager.      (line 2455)
-* BFD_RELOC_NIOS2_RELATIVE:              howto manager.      (line 2468)
-* BFD_RELOC_NIOS2_S16:                   howto manager.      (line 2436)
-* BFD_RELOC_NIOS2_TLS_DTPMOD:            howto manager.      (line 2462)
-* BFD_RELOC_NIOS2_TLS_DTPREL:            howto manager.      (line 2463)
-* BFD_RELOC_NIOS2_TLS_GD16:              howto manager.      (line 2457)
-* BFD_RELOC_NIOS2_TLS_IE16:              howto manager.      (line 2460)
-* BFD_RELOC_NIOS2_TLS_LDM16:             howto manager.      (line 2458)
-* BFD_RELOC_NIOS2_TLS_LDO16:             howto manager.      (line 2459)
-* BFD_RELOC_NIOS2_TLS_LE16:              howto manager.      (line 2461)
-* BFD_RELOC_NIOS2_TLS_TPREL:             howto manager.      (line 2464)
-* BFD_RELOC_NIOS2_U16:                   howto manager.      (line 2437)
-* BFD_RELOC_NIOS2_UJMP:                  howto manager.      (line 2447)
-* BFD_RELOC_NONE:                        howto manager.      (line  135)
-* BFD_RELOC_NS32K_DISP_16:               howto manager.      (line  636)
-* BFD_RELOC_NS32K_DISP_16_PCREL:         howto manager.      (line  639)
-* BFD_RELOC_NS32K_DISP_32:               howto manager.      (line  637)
-* BFD_RELOC_NS32K_DISP_32_PCREL:         howto manager.      (line  640)
-* BFD_RELOC_NS32K_DISP_8:                howto manager.      (line  635)
-* BFD_RELOC_NS32K_DISP_8_PCREL:          howto manager.      (line  638)
-* BFD_RELOC_NS32K_IMM_16:                howto manager.      (line  630)
-* BFD_RELOC_NS32K_IMM_16_PCREL:          howto manager.      (line  633)
-* BFD_RELOC_NS32K_IMM_32:                howto manager.      (line  631)
-* BFD_RELOC_NS32K_IMM_32_PCREL:          howto manager.      (line  634)
-* BFD_RELOC_NS32K_IMM_8:                 howto manager.      (line  629)
-* BFD_RELOC_NS32K_IMM_8_PCREL:           howto manager.      (line  632)
-* BFD_RELOC_OPENRISC_ABS_26:             howto manager.      (line 2377)
-* BFD_RELOC_OPENRISC_REL_26:             howto manager.      (line 2378)
-* BFD_RELOC_PDP11_DISP_6_PCREL:          howto manager.      (line  644)
-* BFD_RELOC_PDP11_DISP_8_PCREL:          howto manager.      (line  643)
-* BFD_RELOC_PJ_CODE_DIR16:               howto manager.      (line  649)
-* BFD_RELOC_PJ_CODE_DIR32:               howto manager.      (line  650)
-* BFD_RELOC_PJ_CODE_HI16:                howto manager.      (line  647)
-* BFD_RELOC_PJ_CODE_LO16:                howto manager.      (line  648)
-* BFD_RELOC_PJ_CODE_REL16:               howto manager.      (line  651)
-* BFD_RELOC_PJ_CODE_REL32:               howto manager.      (line  652)
-* BFD_RELOC_PPC64_ADDR16_DS:             howto manager.      (line  714)
-* BFD_RELOC_PPC64_ADDR16_LO_DS:          howto manager.      (line  715)
-* BFD_RELOC_PPC64_DTPREL16_DS:           howto manager.      (line  763)
-* BFD_RELOC_PPC64_DTPREL16_HIGHER:       howto manager.      (line  765)
-* BFD_RELOC_PPC64_DTPREL16_HIGHERA:      howto manager.      (line  766)
-* BFD_RELOC_PPC64_DTPREL16_HIGHEST:      howto manager.      (line  767)
-* BFD_RELOC_PPC64_DTPREL16_HIGHESTA:     howto manager.      (line  768)
-* BFD_RELOC_PPC64_DTPREL16_LO_DS:        howto manager.      (line  764)
-* BFD_RELOC_PPC64_GOT16_DS:              howto manager.      (line  716)
-* BFD_RELOC_PPC64_GOT16_LO_DS:           howto manager.      (line  717)
-* BFD_RELOC_PPC64_HIGHER:                howto manager.      (line  702)
-* BFD_RELOC_PPC64_HIGHER_S:              howto manager.      (line  703)
-* BFD_RELOC_PPC64_HIGHEST:               howto manager.      (line  704)
-* BFD_RELOC_PPC64_HIGHEST_S:             howto manager.      (line  705)
-* BFD_RELOC_PPC64_PLT16_LO_DS:           howto manager.      (line  718)
-* BFD_RELOC_PPC64_PLTGOT16:              howto manager.      (line  710)
-* BFD_RELOC_PPC64_PLTGOT16_DS:           howto manager.      (line  723)
-* BFD_RELOC_PPC64_PLTGOT16_HA:           howto manager.      (line  713)
-* BFD_RELOC_PPC64_PLTGOT16_HI:           howto manager.      (line  712)
-* BFD_RELOC_PPC64_PLTGOT16_LO:           howto manager.      (line  711)
-* BFD_RELOC_PPC64_PLTGOT16_LO_DS:        howto manager.      (line  724)
-* BFD_RELOC_PPC64_SECTOFF_DS:            howto manager.      (line  719)
-* BFD_RELOC_PPC64_SECTOFF_LO_DS:         howto manager.      (line  720)
-* BFD_RELOC_PPC64_TOC:                   howto manager.      (line  709)
-* BFD_RELOC_PPC64_TOC16_DS:              howto manager.      (line  721)
-* BFD_RELOC_PPC64_TOC16_HA:              howto manager.      (line  708)
-* BFD_RELOC_PPC64_TOC16_HI:              howto manager.      (line  707)
-* BFD_RELOC_PPC64_TOC16_LO:              howto manager.      (line  706)
-* BFD_RELOC_PPC64_TOC16_LO_DS:           howto manager.      (line  722)
-* BFD_RELOC_PPC64_TPREL16_DS:            howto manager.      (line  757)
-* BFD_RELOC_PPC64_TPREL16_HIGHER:        howto manager.      (line  759)
-* BFD_RELOC_PPC64_TPREL16_HIGHERA:       howto manager.      (line  760)
-* BFD_RELOC_PPC64_TPREL16_HIGHEST:       howto manager.      (line  761)
-* BFD_RELOC_PPC64_TPREL16_HIGHESTA:      howto manager.      (line  762)
-* BFD_RELOC_PPC64_TPREL16_LO_DS:         howto manager.      (line  758)
-* BFD_RELOC_PPC_B16:                     howto manager.      (line  658)
-* BFD_RELOC_PPC_B16_BRNTAKEN:            howto manager.      (line  660)
-* BFD_RELOC_PPC_B16_BRTAKEN:             howto manager.      (line  659)
-* BFD_RELOC_PPC_B26:                     howto manager.      (line  655)
-* BFD_RELOC_PPC_BA16:                    howto manager.      (line  661)
-* BFD_RELOC_PPC_BA16_BRNTAKEN:           howto manager.      (line  663)
-* BFD_RELOC_PPC_BA16_BRTAKEN:            howto manager.      (line  662)
-* BFD_RELOC_PPC_BA26:                    howto manager.      (line  656)
-* BFD_RELOC_PPC_COPY:                    howto manager.      (line  664)
-* BFD_RELOC_PPC_DTPMOD:                  howto manager.      (line  730)
-* BFD_RELOC_PPC_DTPREL:                  howto manager.      (line  740)
-* BFD_RELOC_PPC_DTPREL16:                howto manager.      (line  736)
-* BFD_RELOC_PPC_DTPREL16_HA:             howto manager.      (line  739)
-* BFD_RELOC_PPC_DTPREL16_HI:             howto manager.      (line  738)
-* BFD_RELOC_PPC_DTPREL16_LO:             howto manager.      (line  737)
-* BFD_RELOC_PPC_EMB_BIT_FLD:             howto manager.      (line  683)
-* BFD_RELOC_PPC_EMB_MRKREF:              howto manager.      (line  678)
-* BFD_RELOC_PPC_EMB_NADDR16:             howto manager.      (line  670)
-* BFD_RELOC_PPC_EMB_NADDR16_HA:          howto manager.      (line  673)
-* BFD_RELOC_PPC_EMB_NADDR16_HI:          howto manager.      (line  672)
-* BFD_RELOC_PPC_EMB_NADDR16_LO:          howto manager.      (line  671)
-* BFD_RELOC_PPC_EMB_NADDR32:             howto manager.      (line  669)
-* BFD_RELOC_PPC_EMB_RELSDA:              howto manager.      (line  684)
-* BFD_RELOC_PPC_EMB_RELSEC16:            howto manager.      (line  679)
-* BFD_RELOC_PPC_EMB_RELST_HA:            howto manager.      (line  682)
-* BFD_RELOC_PPC_EMB_RELST_HI:            howto manager.      (line  681)
-* BFD_RELOC_PPC_EMB_RELST_LO:            howto manager.      (line  680)
-* BFD_RELOC_PPC_EMB_SDA21:               howto manager.      (line  677)
-* BFD_RELOC_PPC_EMB_SDA2I16:             howto manager.      (line  675)
-* BFD_RELOC_PPC_EMB_SDA2REL:             howto manager.      (line  676)
-* BFD_RELOC_PPC_EMB_SDAI16:              howto manager.      (line  674)
-* BFD_RELOC_PPC_GLOB_DAT:                howto manager.      (line  665)
-* BFD_RELOC_PPC_GOT_DTPREL16:            howto manager.      (line  753)
-* BFD_RELOC_PPC_GOT_DTPREL16_HA:         howto manager.      (line  756)
-* BFD_RELOC_PPC_GOT_DTPREL16_HI:         howto manager.      (line  755)
-* BFD_RELOC_PPC_GOT_DTPREL16_LO:         howto manager.      (line  754)
-* BFD_RELOC_PPC_GOT_TLSGD16:             howto manager.      (line  741)
-* BFD_RELOC_PPC_GOT_TLSGD16_HA:          howto manager.      (line  744)
-* BFD_RELOC_PPC_GOT_TLSGD16_HI:          howto manager.      (line  743)
-* BFD_RELOC_PPC_GOT_TLSGD16_LO:          howto manager.      (line  742)
-* BFD_RELOC_PPC_GOT_TLSLD16:             howto manager.      (line  745)
-* BFD_RELOC_PPC_GOT_TLSLD16_HA:          howto manager.      (line  748)
-* BFD_RELOC_PPC_GOT_TLSLD16_HI:          howto manager.      (line  747)
-* BFD_RELOC_PPC_GOT_TLSLD16_LO:          howto manager.      (line  746)
-* BFD_RELOC_PPC_GOT_TPREL16:             howto manager.      (line  749)
-* BFD_RELOC_PPC_GOT_TPREL16_HA:          howto manager.      (line  752)
-* BFD_RELOC_PPC_GOT_TPREL16_HI:          howto manager.      (line  751)
-* BFD_RELOC_PPC_GOT_TPREL16_LO:          howto manager.      (line  750)
-* BFD_RELOC_PPC_JMP_SLOT:                howto manager.      (line  666)
-* BFD_RELOC_PPC_LOCAL24PC:               howto manager.      (line  668)
-* BFD_RELOC_PPC_RELATIVE:                howto manager.      (line  667)
-* BFD_RELOC_PPC_TLS:                     howto manager.      (line  727)
-* BFD_RELOC_PPC_TLSGD:                   howto manager.      (line  728)
-* BFD_RELOC_PPC_TLSLD:                   howto manager.      (line  729)
-* BFD_RELOC_PPC_TOC16:                   howto manager.      (line  657)
-* BFD_RELOC_PPC_TPREL:                   howto manager.      (line  735)
-* BFD_RELOC_PPC_TPREL16:                 howto manager.      (line  731)
-* BFD_RELOC_PPC_TPREL16_HA:              howto manager.      (line  734)
-* BFD_RELOC_PPC_TPREL16_HI:              howto manager.      (line  733)
-* BFD_RELOC_PPC_TPREL16_LO:              howto manager.      (line  732)
-* BFD_RELOC_PPC_VLE_HA16A:               howto manager.      (line  692)
-* BFD_RELOC_PPC_VLE_HA16D:               howto manager.      (line  693)
-* BFD_RELOC_PPC_VLE_HI16A:               howto manager.      (line  690)
-* BFD_RELOC_PPC_VLE_HI16D:               howto manager.      (line  691)
-* BFD_RELOC_PPC_VLE_LO16A:               howto manager.      (line  688)
-* BFD_RELOC_PPC_VLE_LO16D:               howto manager.      (line  689)
-* BFD_RELOC_PPC_VLE_REL15:               howto manager.      (line  686)
-* BFD_RELOC_PPC_VLE_REL24:               howto manager.      (line  687)
-* BFD_RELOC_PPC_VLE_REL8:                howto manager.      (line  685)
-* BFD_RELOC_PPC_VLE_SDA21:               howto manager.      (line  694)
-* BFD_RELOC_PPC_VLE_SDA21_LO:            howto manager.      (line  695)
-* BFD_RELOC_PPC_VLE_SDAREL_HA16A:        howto manager.      (line  700)
-* BFD_RELOC_PPC_VLE_SDAREL_HA16D:        howto manager.      (line  701)
-* BFD_RELOC_PPC_VLE_SDAREL_HI16A:        howto manager.      (line  698)
-* BFD_RELOC_PPC_VLE_SDAREL_HI16D:        howto manager.      (line  699)
-* BFD_RELOC_PPC_VLE_SDAREL_LO16A:        howto manager.      (line  696)
-* BFD_RELOC_PPC_VLE_SDAREL_LO16D:        howto manager.      (line  697)
-* BFD_RELOC_RELC:                        howto manager.      (line 2395)
-* BFD_RELOC_RL78_16_OP:                  howto manager.      (line 1750)
-* BFD_RELOC_RL78_16U:                    howto manager.      (line 1754)
-* BFD_RELOC_RL78_24_OP:                  howto manager.      (line 1751)
-* BFD_RELOC_RL78_24U:                    howto manager.      (line 1755)
-* BFD_RELOC_RL78_32_OP:                  howto manager.      (line 1752)
-* BFD_RELOC_RL78_8U:                     howto manager.      (line 1753)
-* BFD_RELOC_RL78_ABS16:                  howto manager.      (line 1767)
-* BFD_RELOC_RL78_ABS16_REV:              howto manager.      (line 1768)
-* BFD_RELOC_RL78_ABS16U:                 howto manager.      (line 1771)
-* BFD_RELOC_RL78_ABS16UL:                howto manager.      (line 1773)
-* BFD_RELOC_RL78_ABS16UW:                howto manager.      (line 1772)
-* BFD_RELOC_RL78_ABS32:                  howto manager.      (line 1769)
-* BFD_RELOC_RL78_ABS32_REV:              howto manager.      (line 1770)
-* BFD_RELOC_RL78_ABS8:                   howto manager.      (line 1766)
-* BFD_RELOC_RL78_CODE:                   howto manager.      (line 1778)
-* BFD_RELOC_RL78_DIFF:                   howto manager.      (line 1757)
-* BFD_RELOC_RL78_DIR3U_PCREL:            howto manager.      (line 1756)
-* BFD_RELOC_RL78_GPRELB:                 howto manager.      (line 1758)
-* BFD_RELOC_RL78_GPRELL:                 howto manager.      (line 1760)
-* BFD_RELOC_RL78_GPRELW:                 howto manager.      (line 1759)
-* BFD_RELOC_RL78_HI16:                   howto manager.      (line 1775)
-* BFD_RELOC_RL78_HI8:                    howto manager.      (line 1776)
-* BFD_RELOC_RL78_LO16:                   howto manager.      (line 1777)
-* BFD_RELOC_RL78_NEG16:                  howto manager.      (line 1747)
-* BFD_RELOC_RL78_NEG24:                  howto manager.      (line 1748)
-* BFD_RELOC_RL78_NEG32:                  howto manager.      (line 1749)
-* BFD_RELOC_RL78_NEG8:                   howto manager.      (line 1746)
-* BFD_RELOC_RL78_OP_AND:                 howto manager.      (line 1764)
-* BFD_RELOC_RL78_OP_NEG:                 howto manager.      (line 1763)
-* BFD_RELOC_RL78_OP_SHRA:                howto manager.      (line 1765)
-* BFD_RELOC_RL78_OP_SUBTRACT:            howto manager.      (line 1762)
-* BFD_RELOC_RL78_RELAX:                  howto manager.      (line 1774)
-* BFD_RELOC_RL78_SYM:                    howto manager.      (line 1761)
-* BFD_RELOC_RVA:                         howto manager.      (line  104)
-* BFD_RELOC_RX_16_OP:                    howto manager.      (line 1785)
-* BFD_RELOC_RX_16U:                      howto manager.      (line 1789)
-* BFD_RELOC_RX_24_OP:                    howto manager.      (line 1786)
-* BFD_RELOC_RX_24U:                      howto manager.      (line 1790)
-* BFD_RELOC_RX_32_OP:                    howto manager.      (line 1787)
-* BFD_RELOC_RX_8U:                       howto manager.      (line 1788)
-* BFD_RELOC_RX_ABS16:                    howto manager.      (line 1800)
-* BFD_RELOC_RX_ABS16_REV:                howto manager.      (line 1801)
-* BFD_RELOC_RX_ABS16U:                   howto manager.      (line 1804)
-* BFD_RELOC_RX_ABS16UL:                  howto manager.      (line 1806)
-* BFD_RELOC_RX_ABS16UW:                  howto manager.      (line 1805)
-* BFD_RELOC_RX_ABS32:                    howto manager.      (line 1802)
-* BFD_RELOC_RX_ABS32_REV:                howto manager.      (line 1803)
-* BFD_RELOC_RX_ABS8:                     howto manager.      (line 1799)
-* BFD_RELOC_RX_DIFF:                     howto manager.      (line 1792)
-* BFD_RELOC_RX_DIR3U_PCREL:              howto manager.      (line 1791)
-* BFD_RELOC_RX_GPRELB:                   howto manager.      (line 1793)
-* BFD_RELOC_RX_GPRELL:                   howto manager.      (line 1795)
-* BFD_RELOC_RX_GPRELW:                   howto manager.      (line 1794)
-* BFD_RELOC_RX_NEG16:                    howto manager.      (line 1782)
-* BFD_RELOC_RX_NEG24:                    howto manager.      (line 1783)
-* BFD_RELOC_RX_NEG32:                    howto manager.      (line 1784)
-* BFD_RELOC_RX_NEG8:                     howto manager.      (line 1781)
-* BFD_RELOC_RX_OP_NEG:                   howto manager.      (line 1798)
-* BFD_RELOC_RX_OP_SUBTRACT:              howto manager.      (line 1797)
-* BFD_RELOC_RX_RELAX:                    howto manager.      (line 1807)
-* BFD_RELOC_RX_SYM:                      howto manager.      (line 1796)
-* BFD_RELOC_SCORE16_BRANCH:              howto manager.      (line 1938)
-* BFD_RELOC_SCORE16_JMP:                 howto manager.      (line 1935)
-* BFD_RELOC_SCORE_BCMP:                  howto manager.      (line 1941)
-* BFD_RELOC_SCORE_BRANCH:                howto manager.      (line 1926)
-* BFD_RELOC_SCORE_CALL15:                howto manager.      (line 1946)
-* BFD_RELOC_SCORE_DUMMY2:                howto manager.      (line 1922)
-* BFD_RELOC_SCORE_DUMMY_HI16:            howto manager.      (line 1947)
-* BFD_RELOC_SCORE_GOT15:                 howto manager.      (line 1944)
-* BFD_RELOC_SCORE_GOT_LO16:              howto manager.      (line 1945)
-* BFD_RELOC_SCORE_GPREL15:               howto manager.      (line 1919)
-* BFD_RELOC_SCORE_IMM30:                 howto manager.      (line 1929)
-* BFD_RELOC_SCORE_IMM32:                 howto manager.      (line 1932)
-* BFD_RELOC_SCORE_JMP:                   howto manager.      (line 1923)
-* BFD_RELOC_SH_ALIGN:                    howto manager.      (line  962)
-* BFD_RELOC_SH_CODE:                     howto manager.      (line  963)
-* BFD_RELOC_SH_COPY:                     howto manager.      (line  968)
-* BFD_RELOC_SH_COPY64:                   howto manager.      (line  993)
-* BFD_RELOC_SH_COUNT:                    howto manager.      (line  961)
-* BFD_RELOC_SH_DATA:                     howto manager.      (line  964)
-* BFD_RELOC_SH_DISP12:                   howto manager.      (line  944)
-* BFD_RELOC_SH_DISP12BY2:                howto manager.      (line  945)
-* BFD_RELOC_SH_DISP12BY4:                howto manager.      (line  946)
-* BFD_RELOC_SH_DISP12BY8:                howto manager.      (line  947)
-* BFD_RELOC_SH_DISP20:                   howto manager.      (line  948)
-* BFD_RELOC_SH_DISP20BY8:                howto manager.      (line  949)
-* BFD_RELOC_SH_FUNCDESC:                 howto manager.      (line 1036)
-* BFD_RELOC_SH_GLOB_DAT:                 howto manager.      (line  969)
-* BFD_RELOC_SH_GLOB_DAT64:               howto manager.      (line  994)
-* BFD_RELOC_SH_GOT10BY4:                 howto manager.      (line  997)
-* BFD_RELOC_SH_GOT10BY8:                 howto manager.      (line  998)
-* BFD_RELOC_SH_GOT20:                    howto manager.      (line 1030)
-* BFD_RELOC_SH_GOT_HI16:                 howto manager.      (line  976)
-* BFD_RELOC_SH_GOT_LOW16:                howto manager.      (line  973)
-* BFD_RELOC_SH_GOT_MEDHI16:              howto manager.      (line  975)
-* BFD_RELOC_SH_GOT_MEDLOW16:             howto manager.      (line  974)
-* BFD_RELOC_SH_GOTFUNCDESC:              howto manager.      (line 1032)
-* BFD_RELOC_SH_GOTFUNCDESC20:            howto manager.      (line 1033)
-* BFD_RELOC_SH_GOTOFF20:                 howto manager.      (line 1031)
-* BFD_RELOC_SH_GOTOFF_HI16:              howto manager.      (line  988)
-* BFD_RELOC_SH_GOTOFF_LOW16:             howto manager.      (line  985)
-* BFD_RELOC_SH_GOTOFF_MEDHI16:           howto manager.      (line  987)
-* BFD_RELOC_SH_GOTOFF_MEDLOW16:          howto manager.      (line  986)
-* BFD_RELOC_SH_GOTOFFFUNCDESC:           howto manager.      (line 1034)
-* BFD_RELOC_SH_GOTOFFFUNCDESC20:         howto manager.      (line 1035)
-* BFD_RELOC_SH_GOTPC:                    howto manager.      (line  972)
-* BFD_RELOC_SH_GOTPC_HI16:               howto manager.      (line  992)
-* BFD_RELOC_SH_GOTPC_LOW16:              howto manager.      (line  989)
-* BFD_RELOC_SH_GOTPC_MEDHI16:            howto manager.      (line  991)
-* BFD_RELOC_SH_GOTPC_MEDLOW16:           howto manager.      (line  990)
-* BFD_RELOC_SH_GOTPLT10BY4:              howto manager.      (line  999)
-* BFD_RELOC_SH_GOTPLT10BY8:              howto manager.      (line 1000)
-* BFD_RELOC_SH_GOTPLT32:                 howto manager.      (line 1001)
-* BFD_RELOC_SH_GOTPLT_HI16:              howto manager.      (line  980)
-* BFD_RELOC_SH_GOTPLT_LOW16:             howto manager.      (line  977)
-* BFD_RELOC_SH_GOTPLT_MEDHI16:           howto manager.      (line  979)
-* BFD_RELOC_SH_GOTPLT_MEDLOW16:          howto manager.      (line  978)
-* BFD_RELOC_SH_IMM3:                     howto manager.      (line  942)
-* BFD_RELOC_SH_IMM3U:                    howto manager.      (line  943)
-* BFD_RELOC_SH_IMM4:                     howto manager.      (line  950)
-* BFD_RELOC_SH_IMM4BY2:                  howto manager.      (line  951)
-* BFD_RELOC_SH_IMM4BY4:                  howto manager.      (line  952)
-* BFD_RELOC_SH_IMM8:                     howto manager.      (line  953)
-* BFD_RELOC_SH_IMM8BY2:                  howto manager.      (line  954)
-* BFD_RELOC_SH_IMM8BY4:                  howto manager.      (line  955)
-* BFD_RELOC_SH_IMM_HI16:                 howto manager.      (line 1019)
-* BFD_RELOC_SH_IMM_HI16_PCREL:           howto manager.      (line 1020)
-* BFD_RELOC_SH_IMM_LOW16:                howto manager.      (line 1013)
-* BFD_RELOC_SH_IMM_LOW16_PCREL:          howto manager.      (line 1014)
-* BFD_RELOC_SH_IMM_MEDHI16:              howto manager.      (line 1017)
-* BFD_RELOC_SH_IMM_MEDHI16_PCREL:        howto manager.      (line 1018)
-* BFD_RELOC_SH_IMM_MEDLOW16:             howto manager.      (line 1015)
-* BFD_RELOC_SH_IMM_MEDLOW16_PCREL:       howto manager.      (line 1016)
-* BFD_RELOC_SH_IMMS10:                   howto manager.      (line 1007)
-* BFD_RELOC_SH_IMMS10BY2:                howto manager.      (line 1008)
-* BFD_RELOC_SH_IMMS10BY4:                howto manager.      (line 1009)
-* BFD_RELOC_SH_IMMS10BY8:                howto manager.      (line 1010)
-* BFD_RELOC_SH_IMMS16:                   howto manager.      (line 1011)
-* BFD_RELOC_SH_IMMS6:                    howto manager.      (line 1004)
-* BFD_RELOC_SH_IMMS6BY32:                howto manager.      (line 1005)
-* BFD_RELOC_SH_IMMU16:                   howto manager.      (line 1012)
-* BFD_RELOC_SH_IMMU5:                    howto manager.      (line 1003)
-* BFD_RELOC_SH_IMMU6:                    howto manager.      (line 1006)
-* BFD_RELOC_SH_JMP_SLOT:                 howto manager.      (line  970)
-* BFD_RELOC_SH_JMP_SLOT64:               howto manager.      (line  995)
-* BFD_RELOC_SH_LABEL:                    howto manager.      (line  965)
-* BFD_RELOC_SH_LOOP_END:                 howto manager.      (line  967)
-* BFD_RELOC_SH_LOOP_START:               howto manager.      (line  966)
-* BFD_RELOC_SH_PCDISP12BY2:              howto manager.      (line  941)
-* BFD_RELOC_SH_PCDISP8BY2:               howto manager.      (line  940)
-* BFD_RELOC_SH_PCRELIMM8BY2:             howto manager.      (line  956)
-* BFD_RELOC_SH_PCRELIMM8BY4:             howto manager.      (line  957)
-* BFD_RELOC_SH_PLT_HI16:                 howto manager.      (line  984)
-* BFD_RELOC_SH_PLT_LOW16:                howto manager.      (line  981)
-* BFD_RELOC_SH_PLT_MEDHI16:              howto manager.      (line  983)
-* BFD_RELOC_SH_PLT_MEDLOW16:             howto manager.      (line  982)
-* BFD_RELOC_SH_PT_16:                    howto manager.      (line 1021)
-* BFD_RELOC_SH_RELATIVE:                 howto manager.      (line  971)
-* BFD_RELOC_SH_RELATIVE64:               howto manager.      (line  996)
-* BFD_RELOC_SH_SHMEDIA_CODE:             howto manager.      (line 1002)
-* BFD_RELOC_SH_SWITCH16:                 howto manager.      (line  958)
-* BFD_RELOC_SH_SWITCH32:                 howto manager.      (line  959)
-* BFD_RELOC_SH_TLS_DTPMOD32:             howto manager.      (line 1027)
-* BFD_RELOC_SH_TLS_DTPOFF32:             howto manager.      (line 1028)
-* BFD_RELOC_SH_TLS_GD_32:                howto manager.      (line 1022)
-* BFD_RELOC_SH_TLS_IE_32:                howto manager.      (line 1025)
-* BFD_RELOC_SH_TLS_LD_32:                howto manager.      (line 1023)
-* BFD_RELOC_SH_TLS_LDO_32:               howto manager.      (line 1024)
-* BFD_RELOC_SH_TLS_LE_32:                howto manager.      (line 1026)
-* BFD_RELOC_SH_TLS_TPOFF32:              howto manager.      (line 1029)
-* BFD_RELOC_SH_USES:                     howto manager.      (line  960)
-* BFD_RELOC_SIZE32:                      howto manager.      (line   74)
-* BFD_RELOC_SIZE64:                      howto manager.      (line   75)
-* BFD_RELOC_SPARC13:                     howto manager.      (line  138)
-* BFD_RELOC_SPARC22:                     howto manager.      (line  137)
-* BFD_RELOC_SPARC_10:                    howto manager.      (line  167)
-* BFD_RELOC_SPARC_11:                    howto manager.      (line  168)
-* BFD_RELOC_SPARC_5:                     howto manager.      (line  180)
-* BFD_RELOC_SPARC_6:                     howto manager.      (line  179)
-* BFD_RELOC_SPARC_64:                    howto manager.      (line  166)
-* BFD_RELOC_SPARC_7:                     howto manager.      (line  178)
-* BFD_RELOC_SPARC_BASE13:                howto manager.      (line  162)
-* BFD_RELOC_SPARC_BASE22:                howto manager.      (line  163)
-* BFD_RELOC_SPARC_COPY:                  howto manager.      (line  145)
-* BFD_RELOC_SPARC_DISP64:                howto manager.      (line  181)
-* BFD_RELOC_SPARC_GLOB_DAT:              howto manager.      (line  146)
-* BFD_RELOC_SPARC_GOT10:                 howto manager.      (line  139)
-* BFD_RELOC_SPARC_GOT13:                 howto manager.      (line  140)
-* BFD_RELOC_SPARC_GOT22:                 howto manager.      (line  141)
-* BFD_RELOC_SPARC_GOTDATA_HIX22:         howto manager.      (line  152)
-* BFD_RELOC_SPARC_GOTDATA_LOX10:         howto manager.      (line  153)
-* BFD_RELOC_SPARC_GOTDATA_OP:            howto manager.      (line  156)
-* BFD_RELOC_SPARC_GOTDATA_OP_HIX22:      howto manager.      (line  154)
-* BFD_RELOC_SPARC_GOTDATA_OP_LOX10:      howto manager.      (line  155)
-* BFD_RELOC_SPARC_H34:                   howto manager.      (line  190)
-* BFD_RELOC_SPARC_H44:                   howto manager.      (line  186)
-* BFD_RELOC_SPARC_HH22:                  howto manager.      (line  170)
-* BFD_RELOC_SPARC_HIX22:                 howto manager.      (line  184)
-* BFD_RELOC_SPARC_HM10:                  howto manager.      (line  171)
-* BFD_RELOC_SPARC_IRELATIVE:             howto manager.      (line  158)
-* BFD_RELOC_SPARC_JMP_IREL:              howto manager.      (line  157)
-* BFD_RELOC_SPARC_JMP_SLOT:              howto manager.      (line  147)
-* BFD_RELOC_SPARC_L44:                   howto manager.      (line  188)
-* BFD_RELOC_SPARC_LM22:                  howto manager.      (line  172)
-* BFD_RELOC_SPARC_LOX10:                 howto manager.      (line  185)
-* BFD_RELOC_SPARC_M44:                   howto manager.      (line  187)
-* BFD_RELOC_SPARC_OLO10:                 howto manager.      (line  169)
-* BFD_RELOC_SPARC_PC10:                  howto manager.      (line  142)
-* BFD_RELOC_SPARC_PC22:                  howto manager.      (line  143)
-* BFD_RELOC_SPARC_PC_HH22:               howto manager.      (line  173)
-* BFD_RELOC_SPARC_PC_HM10:               howto manager.      (line  174)
-* BFD_RELOC_SPARC_PC_LM22:               howto manager.      (line  175)
-* BFD_RELOC_SPARC_PLT32:                 howto manager.      (line  182)
-* BFD_RELOC_SPARC_PLT64:                 howto manager.      (line  183)
-* BFD_RELOC_SPARC_REGISTER:              howto manager.      (line  189)
-* BFD_RELOC_SPARC_RELATIVE:              howto manager.      (line  148)
-* BFD_RELOC_SPARC_REV32:                 howto manager.      (line  196)
-* BFD_RELOC_SPARC_SIZE32:                howto manager.      (line  191)
-* BFD_RELOC_SPARC_SIZE64:                howto manager.      (line  192)
-* BFD_RELOC_SPARC_TLS_DTPMOD32:          howto manager.      (line  217)
-* BFD_RELOC_SPARC_TLS_DTPMOD64:          howto manager.      (line  218)
-* BFD_RELOC_SPARC_TLS_DTPOFF32:          howto manager.      (line  219)
-* BFD_RELOC_SPARC_TLS_DTPOFF64:          howto manager.      (line  220)
-* BFD_RELOC_SPARC_TLS_GD_ADD:            howto manager.      (line  201)
-* BFD_RELOC_SPARC_TLS_GD_CALL:           howto manager.      (line  202)
-* BFD_RELOC_SPARC_TLS_GD_HI22:           howto manager.      (line  199)
-* BFD_RELOC_SPARC_TLS_GD_LO10:           howto manager.      (line  200)
-* BFD_RELOC_SPARC_TLS_IE_ADD:            howto manager.      (line  214)
-* BFD_RELOC_SPARC_TLS_IE_HI22:           howto manager.      (line  210)
-* BFD_RELOC_SPARC_TLS_IE_LD:             howto manager.      (line  212)
-* BFD_RELOC_SPARC_TLS_IE_LDX:            howto manager.      (line  213)
-* BFD_RELOC_SPARC_TLS_IE_LO10:           howto manager.      (line  211)
-* BFD_RELOC_SPARC_TLS_LDM_ADD:           howto manager.      (line  205)
-* BFD_RELOC_SPARC_TLS_LDM_CALL:          howto manager.      (line  206)
-* BFD_RELOC_SPARC_TLS_LDM_HI22:          howto manager.      (line  203)
-* BFD_RELOC_SPARC_TLS_LDM_LO10:          howto manager.      (line  204)
-* BFD_RELOC_SPARC_TLS_LDO_ADD:           howto manager.      (line  209)
-* BFD_RELOC_SPARC_TLS_LDO_HIX22:         howto manager.      (line  207)
-* BFD_RELOC_SPARC_TLS_LDO_LOX10:         howto manager.      (line  208)
-* BFD_RELOC_SPARC_TLS_LE_HIX22:          howto manager.      (line  215)
-* BFD_RELOC_SPARC_TLS_LE_LOX10:          howto manager.      (line  216)
-* BFD_RELOC_SPARC_TLS_TPOFF32:           howto manager.      (line  221)
-* BFD_RELOC_SPARC_TLS_TPOFF64:           howto manager.      (line  222)
-* BFD_RELOC_SPARC_UA16:                  howto manager.      (line  149)
-* BFD_RELOC_SPARC_UA32:                  howto manager.      (line  150)
-* BFD_RELOC_SPARC_UA64:                  howto manager.      (line  151)
-* BFD_RELOC_SPARC_WDISP10:               howto manager.      (line  193)
-* BFD_RELOC_SPARC_WDISP16:               howto manager.      (line  176)
-* BFD_RELOC_SPARC_WDISP19:               howto manager.      (line  177)
-* BFD_RELOC_SPARC_WDISP22:               howto manager.      (line  136)
-* BFD_RELOC_SPARC_WPLT30:                howto manager.      (line  144)
-* BFD_RELOC_SPU_ADD_PIC:                 howto manager.      (line  239)
-* BFD_RELOC_SPU_HI16:                    howto manager.      (line  236)
-* BFD_RELOC_SPU_IMM10:                   howto manager.      (line  227)
-* BFD_RELOC_SPU_IMM10W:                  howto manager.      (line  228)
-* BFD_RELOC_SPU_IMM16:                   howto manager.      (line  229)
-* BFD_RELOC_SPU_IMM16W:                  howto manager.      (line  230)
-* BFD_RELOC_SPU_IMM18:                   howto manager.      (line  231)
-* BFD_RELOC_SPU_IMM7:                    howto manager.      (line  225)
-* BFD_RELOC_SPU_IMM8:                    howto manager.      (line  226)
-* BFD_RELOC_SPU_LO16:                    howto manager.      (line  235)
-* BFD_RELOC_SPU_PCREL16:                 howto manager.      (line  234)
-* BFD_RELOC_SPU_PCREL9a:                 howto manager.      (line  232)
-* BFD_RELOC_SPU_PCREL9b:                 howto manager.      (line  233)
-* BFD_RELOC_SPU_PPU32:                   howto manager.      (line  237)
-* BFD_RELOC_SPU_PPU64:                   howto manager.      (line  238)
-* BFD_RELOC_THUMB_PCREL_BLX:             howto manager.      (line  789)
-* BFD_RELOC_THUMB_PCREL_BRANCH12:        howto manager.      (line  803)
-* BFD_RELOC_THUMB_PCREL_BRANCH20:        howto manager.      (line  804)
-* BFD_RELOC_THUMB_PCREL_BRANCH23:        howto manager.      (line  805)
-* BFD_RELOC_THUMB_PCREL_BRANCH25:        howto manager.      (line  806)
-* BFD_RELOC_THUMB_PCREL_BRANCH7:         howto manager.      (line  801)
-* BFD_RELOC_THUMB_PCREL_BRANCH9:         howto manager.      (line  802)
-* BFD_RELOC_TIC30_LDP:                   howto manager.      (line 1421)
-* BFD_RELOC_TIC54X_16_OF_23:             howto manager.      (line 1439)
-* BFD_RELOC_TIC54X_23:                   howto manager.      (line 1436)
-* BFD_RELOC_TIC54X_MS7_OF_23:            howto manager.      (line 1444)
-* BFD_RELOC_TIC54X_PARTLS7:              howto manager.      (line 1426)
-* BFD_RELOC_TIC54X_PARTMS9:              howto manager.      (line 1431)
-* BFD_RELOC_TILEGX_BROFF_X1:             howto manager.      (line 3029)
-* BFD_RELOC_TILEGX_COPY:                 howto manager.      (line 3025)
-* BFD_RELOC_TILEGX_DEST_IMM8_X1:         howto manager.      (line 3036)
-* BFD_RELOC_TILEGX_GLOB_DAT:             howto manager.      (line 3026)
-* BFD_RELOC_TILEGX_HW0:                  howto manager.      (line 3018)
-* BFD_RELOC_TILEGX_HW0_LAST:             howto manager.      (line 3022)
-* BFD_RELOC_TILEGX_HW1:                  howto manager.      (line 3019)
-* BFD_RELOC_TILEGX_HW1_LAST:             howto manager.      (line 3023)
-* BFD_RELOC_TILEGX_HW2:                  howto manager.      (line 3020)
-* BFD_RELOC_TILEGX_HW2_LAST:             howto manager.      (line 3024)
-* BFD_RELOC_TILEGX_HW3:                  howto manager.      (line 3021)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0:         howto manager.      (line 3045)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_GOT:     howto manager.      (line 3073)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST:    howto manager.      (line 3053)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_GOT: howto manager.     (line 3081)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PCREL: howto manager.   (line 3067)
+                                                             (line 2463)
+* BFD_RELOC_AARCH64_TLSIE_MOVW_GOTTPREL_G1: howto manager.   (line 2461)
+* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_HI12: howto manager.     (line 2483)
+* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12: howto manager.     (line 2485)
+* BFD_RELOC_AARCH64_TLSLE_ADD_TPREL_LO12_NC: howto manager.  (line 2487)
+* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0: howto manager.      (line 2479)
+* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G0_NC: howto manager.   (line 2481)
+* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1: howto manager.      (line 2475)
+* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G1_NC: howto manager.   (line 2477)
+* BFD_RELOC_AARCH64_TLSLE_MOVW_TPREL_G2: howto manager.      (line 2473)
+* BFD_RELOC_AARCH64_TLS_DTPMOD:          howto manager.      (line 2519)
+* BFD_RELOC_AARCH64_TLS_DTPREL:          howto manager.      (line 2521)
+* BFD_RELOC_AARCH64_TLS_TPREL:           howto manager.      (line 2523)
+* BFD_RELOC_AARCH64_TSTBR14:             howto manager.      (line 2402)
+* BFD_RELOC_ALPHA_BOH:                   howto manager.      (line  292)
+* BFD_RELOC_ALPHA_BRSGP:                 howto manager.      (line  279)
+* BFD_RELOC_ALPHA_BSR:                   howto manager.      (line  286)
+* BFD_RELOC_ALPHA_CODEADDR:              howto manager.      (line  272)
+* BFD_RELOC_ALPHA_DTPMOD64:              howto manager.      (line  297)
+* BFD_RELOC_ALPHA_DTPREL16:              howto manager.      (line  302)
+* BFD_RELOC_ALPHA_DTPREL64:              howto manager.      (line  299)
+* BFD_RELOC_ALPHA_DTPREL_HI16:           howto manager.      (line  300)
+* BFD_RELOC_ALPHA_DTPREL_LO16:           howto manager.      (line  301)
+* BFD_RELOC_ALPHA_ELF_LITERAL:           howto manager.      (line  240)
+* BFD_RELOC_ALPHA_GOTDTPREL16:           howto manager.      (line  298)
+* BFD_RELOC_ALPHA_GOTTPREL16:            howto manager.      (line  303)
+* BFD_RELOC_ALPHA_GPDISP:                howto manager.      (line  235)
+* BFD_RELOC_ALPHA_GPDISP_HI16:           howto manager.      (line  223)
+* BFD_RELOC_ALPHA_GPDISP_LO16:           howto manager.      (line  230)
+* BFD_RELOC_ALPHA_GPREL_HI16:            howto manager.      (line  275)
+* BFD_RELOC_ALPHA_GPREL_LO16:            howto manager.      (line  276)
+* BFD_RELOC_ALPHA_HINT:                  howto manager.      (line  265)
+* BFD_RELOC_ALPHA_LDA:                   howto manager.      (line  289)
+* BFD_RELOC_ALPHA_LINKAGE:               howto manager.      (line  269)
+* BFD_RELOC_ALPHA_LITERAL:               howto manager.      (line  239)
+* BFD_RELOC_ALPHA_LITUSE:                howto manager.      (line  241)
+* BFD_RELOC_ALPHA_NOP:                   howto manager.      (line  283)
+* BFD_RELOC_ALPHA_TLSGD:                 howto manager.      (line  295)
+* BFD_RELOC_ALPHA_TLSLDM:                howto manager.      (line  296)
+* BFD_RELOC_ALPHA_TPREL16:               howto manager.      (line  307)
+* BFD_RELOC_ALPHA_TPREL64:               howto manager.      (line  304)
+* BFD_RELOC_ALPHA_TPREL_HI16:            howto manager.      (line  305)
+* BFD_RELOC_ALPHA_TPREL_LO16:            howto manager.      (line  306)
+* BFD_RELOC_ARC_B22_PCREL:               howto manager.      (line  952)
+* BFD_RELOC_ARC_B26:                     howto manager.      (line  956)
+* BFD_RELOC_ARM_ADRL_IMMEDIATE:          howto manager.      (line  826)
+* BFD_RELOC_ARM_ADR_IMM:                 howto manager.      (line  840)
+* BFD_RELOC_ARM_ALU_PC_G0:               howto manager.      (line  793)
+* BFD_RELOC_ARM_ALU_PC_G0_NC:            howto manager.      (line  792)
+* BFD_RELOC_ARM_ALU_PC_G1:               howto manager.      (line  795)
+* BFD_RELOC_ARM_ALU_PC_G1_NC:            howto manager.      (line  794)
+* BFD_RELOC_ARM_ALU_PC_G2:               howto manager.      (line  796)
+* BFD_RELOC_ARM_ALU_SB_G0:               howto manager.      (line  807)
+* BFD_RELOC_ARM_ALU_SB_G0_NC:            howto manager.      (line  806)
+* BFD_RELOC_ARM_ALU_SB_G1:               howto manager.      (line  809)
+* BFD_RELOC_ARM_ALU_SB_G1_NC:            howto manager.      (line  808)
+* BFD_RELOC_ARM_ALU_SB_G2:               howto manager.      (line  810)
+* BFD_RELOC_ARM_CP_OFF_IMM:              howto manager.      (line  836)
+* BFD_RELOC_ARM_CP_OFF_IMM_S2:           howto manager.      (line  837)
+* BFD_RELOC_ARM_GLOB_DAT:                howto manager.      (line  769)
+* BFD_RELOC_ARM_GOT32:                   howto manager.      (line  770)
+* BFD_RELOC_ARM_GOTOFF:                  howto manager.      (line  773)
+* BFD_RELOC_ARM_GOTPC:                   howto manager.      (line  774)
+* BFD_RELOC_ARM_GOT_PREL:                howto manager.      (line  775)
+* BFD_RELOC_ARM_HVC:                     howto manager.      (line  833)
+* BFD_RELOC_ARM_HWLITERAL:               howto manager.      (line  847)
+* BFD_RELOC_ARM_IMMEDIATE:               howto manager.      (line  825)
+* BFD_RELOC_ARM_IN_POOL:                 howto manager.      (line  843)
+* BFD_RELOC_ARM_IRELATIVE:               howto manager.      (line  823)
+* BFD_RELOC_ARM_JUMP_SLOT:               howto manager.      (line  768)
+* BFD_RELOC_ARM_LDC_PC_G0:               howto manager.      (line  803)
+* BFD_RELOC_ARM_LDC_PC_G1:               howto manager.      (line  804)
+* BFD_RELOC_ARM_LDC_PC_G2:               howto manager.      (line  805)
+* BFD_RELOC_ARM_LDC_SB_G0:               howto manager.      (line  817)
+* BFD_RELOC_ARM_LDC_SB_G1:               howto manager.      (line  818)
+* BFD_RELOC_ARM_LDC_SB_G2:               howto manager.      (line  819)
+* BFD_RELOC_ARM_LDRS_PC_G0:              howto manager.      (line  800)
+* BFD_RELOC_ARM_LDRS_PC_G1:              howto manager.      (line  801)
+* BFD_RELOC_ARM_LDRS_PC_G2:              howto manager.      (line  802)
+* BFD_RELOC_ARM_LDRS_SB_G0:              howto manager.      (line  814)
+* BFD_RELOC_ARM_LDRS_SB_G1:              howto manager.      (line  815)
+* BFD_RELOC_ARM_LDRS_SB_G2:              howto manager.      (line  816)
+* BFD_RELOC_ARM_LDR_IMM:                 howto manager.      (line  841)
+* BFD_RELOC_ARM_LDR_PC_G0:               howto manager.      (line  797)
+* BFD_RELOC_ARM_LDR_PC_G1:               howto manager.      (line  798)
+* BFD_RELOC_ARM_LDR_PC_G2:               howto manager.      (line  799)
+* BFD_RELOC_ARM_LDR_SB_G0:               howto manager.      (line  811)
+* BFD_RELOC_ARM_LDR_SB_G1:               howto manager.      (line  812)
+* BFD_RELOC_ARM_LDR_SB_G2:               howto manager.      (line  813)
+* BFD_RELOC_ARM_LITERAL:                 howto manager.      (line  842)
+* BFD_RELOC_ARM_MOVT:                    howto manager.      (line  760)
+* BFD_RELOC_ARM_MOVT_PCREL:              howto manager.      (line  762)
+* BFD_RELOC_ARM_MOVW:                    howto manager.      (line  759)
+* BFD_RELOC_ARM_MOVW_PCREL:              howto manager.      (line  761)
+* BFD_RELOC_ARM_MULTI:                   howto manager.      (line  835)
+* BFD_RELOC_ARM_OFFSET_IMM:              howto manager.      (line  740)
+* BFD_RELOC_ARM_OFFSET_IMM8:             howto manager.      (line  844)
+* BFD_RELOC_ARM_PCREL_BLX:               howto manager.      (line  716)
+* BFD_RELOC_ARM_PCREL_BRANCH:            howto manager.      (line  713)
+* BFD_RELOC_ARM_PCREL_CALL:              howto manager.      (line  724)
+* BFD_RELOC_ARM_PCREL_JUMP:              howto manager.      (line  727)
+* BFD_RELOC_ARM_PLT32:                   howto manager.      (line  771)
+* BFD_RELOC_ARM_PREL31:                  howto manager.      (line  757)
+* BFD_RELOC_ARM_RELATIVE:                howto manager.      (line  772)
+* BFD_RELOC_ARM_ROSEGREL32:              howto manager.      (line  749)
+* BFD_RELOC_ARM_SBREL32:                 howto manager.      (line  751)
+* BFD_RELOC_ARM_SHIFT_IMM:               howto manager.      (line  831)
+* BFD_RELOC_ARM_SMC:                     howto manager.      (line  832)
+* BFD_RELOC_ARM_SWI:                     howto manager.      (line  834)
+* BFD_RELOC_ARM_T32_ADD_IMM:             howto manager.      (line  828)
+* BFD_RELOC_ARM_T32_ADD_PC12:            howto manager.      (line  830)
+* BFD_RELOC_ARM_T32_CP_OFF_IMM:          howto manager.      (line  838)
+* BFD_RELOC_ARM_T32_CP_OFF_IMM_S2:       howto manager.      (line  839)
+* BFD_RELOC_ARM_T32_IMM12:               howto manager.      (line  829)
+* BFD_RELOC_ARM_T32_IMMEDIATE:           howto manager.      (line  827)
+* BFD_RELOC_ARM_T32_OFFSET_IMM:          howto manager.      (line  846)
+* BFD_RELOC_ARM_T32_OFFSET_U8:           howto manager.      (line  845)
+* BFD_RELOC_ARM_TARGET1:                 howto manager.      (line  746)
+* BFD_RELOC_ARM_TARGET2:                 howto manager.      (line  753)
+* BFD_RELOC_ARM_THM_TLS_CALL:            howto manager.      (line  787)
+* BFD_RELOC_ARM_THM_TLS_DESCSEQ:         howto manager.      (line  789)
+* BFD_RELOC_ARM_THUMB_ADD:               howto manager.      (line  848)
+* BFD_RELOC_ARM_THUMB_IMM:               howto manager.      (line  849)
+* BFD_RELOC_ARM_THUMB_MOVT:              howto manager.      (line  764)
+* BFD_RELOC_ARM_THUMB_MOVT_PCREL:        howto manager.      (line  766)
+* BFD_RELOC_ARM_THUMB_MOVW:              howto manager.      (line  763)
+* BFD_RELOC_ARM_THUMB_MOVW_PCREL:        howto manager.      (line  765)
+* BFD_RELOC_ARM_THUMB_OFFSET:            howto manager.      (line  743)
+* BFD_RELOC_ARM_THUMB_SHIFT:             howto manager.      (line  850)
+* BFD_RELOC_ARM_TLS_CALL:                howto manager.      (line  786)
+* BFD_RELOC_ARM_TLS_DESC:                howto manager.      (line  790)
+* BFD_RELOC_ARM_TLS_DESCSEQ:             howto manager.      (line  788)
+* BFD_RELOC_ARM_TLS_DTPMOD32:            howto manager.      (line  781)
+* BFD_RELOC_ARM_TLS_DTPOFF32:            howto manager.      (line  780)
+* BFD_RELOC_ARM_TLS_GD32:                howto manager.      (line  777)
+* BFD_RELOC_ARM_TLS_GOTDESC:             howto manager.      (line  785)
+* BFD_RELOC_ARM_TLS_IE32:                howto manager.      (line  783)
+* BFD_RELOC_ARM_TLS_LDM32:               howto manager.      (line  779)
+* BFD_RELOC_ARM_TLS_LDO32:               howto manager.      (line  778)
+* BFD_RELOC_ARM_TLS_LE32:                howto manager.      (line  784)
+* BFD_RELOC_ARM_TLS_TPOFF32:             howto manager.      (line  782)
+* BFD_RELOC_ARM_V4BX:                    howto manager.      (line  821)
+* BFD_RELOC_AVR_13_PCREL:                howto manager.      (line 1412)
+* BFD_RELOC_AVR_16_PM:                   howto manager.      (line 1415)
+* BFD_RELOC_AVR_6:                       howto manager.      (line 1483)
+* BFD_RELOC_AVR_6_ADIW:                  howto manager.      (line 1486)
+* BFD_RELOC_AVR_7_PCREL:                 howto manager.      (line 1409)
+* BFD_RELOC_AVR_8_HI:                    howto manager.      (line 1492)
+* BFD_RELOC_AVR_8_HLO:                   howto manager.      (line 1495)
+* BFD_RELOC_AVR_8_LO:                    howto manager.      (line 1489)
+* BFD_RELOC_AVR_CALL:                    howto manager.      (line 1477)
+* BFD_RELOC_AVR_HH8_LDI:                 howto manager.      (line 1424)
+* BFD_RELOC_AVR_HH8_LDI_NEG:             howto manager.      (line 1439)
+* BFD_RELOC_AVR_HH8_LDI_PM:              howto manager.      (line 1462)
+* BFD_RELOC_AVR_HH8_LDI_PM_NEG:          howto manager.      (line 1473)
+* BFD_RELOC_AVR_HI8_LDI:                 howto manager.      (line 1421)
+* BFD_RELOC_AVR_HI8_LDI_GS:              howto manager.      (line 1457)
+* BFD_RELOC_AVR_HI8_LDI_NEG:             howto manager.      (line 1435)
+* BFD_RELOC_AVR_HI8_LDI_PM:              howto manager.      (line 1454)
+* BFD_RELOC_AVR_HI8_LDI_PM_NEG:          howto manager.      (line 1469)
+* BFD_RELOC_AVR_LDI:                     howto manager.      (line 1480)
+* BFD_RELOC_AVR_LO8_LDI:                 howto manager.      (line 1418)
+* BFD_RELOC_AVR_LO8_LDI_GS:              howto manager.      (line 1449)
+* BFD_RELOC_AVR_LO8_LDI_NEG:             howto manager.      (line 1431)
+* BFD_RELOC_AVR_LO8_LDI_PM:              howto manager.      (line 1446)
+* BFD_RELOC_AVR_LO8_LDI_PM_NEG:          howto manager.      (line 1466)
+* BFD_RELOC_AVR_MS8_LDI:                 howto manager.      (line 1428)
+* BFD_RELOC_AVR_MS8_LDI_NEG:             howto manager.      (line 1443)
+* BFD_RELOC_BFIN_10_PCREL:               howto manager.      (line  970)
+* BFD_RELOC_BFIN_11_PCREL:               howto manager.      (line  972)
+* BFD_RELOC_BFIN_12_PCREL_JUMP:          howto manager.      (line  974)
+* BFD_RELOC_BFIN_12_PCREL_JUMP_S:        howto manager.      (line  976)
+* BFD_RELOC_BFIN_16_HIGH:                howto manager.      (line  962)
+* BFD_RELOC_BFIN_16_IMM:                 howto manager.      (line  960)
+* BFD_RELOC_BFIN_16_LOW:                 howto manager.      (line  968)
+* BFD_RELOC_BFIN_24_PCREL_CALL_X:        howto manager.      (line  978)
+* BFD_RELOC_BFIN_24_PCREL_JUMP_L:        howto manager.      (line  980)
+* BFD_RELOC_BFIN_4_PCREL:                howto manager.      (line  964)
+* BFD_RELOC_BFIN_5_PCREL:                howto manager.      (line  966)
+* BFD_RELOC_BFIN_FUNCDESC:               howto manager.      (line  985)
+* BFD_RELOC_BFIN_FUNCDESC_GOT17M4:       howto manager.      (line  986)
+* BFD_RELOC_BFIN_FUNCDESC_GOTHI:         howto manager.      (line  987)
+* BFD_RELOC_BFIN_FUNCDESC_GOTLO:         howto manager.      (line  988)
+* BFD_RELOC_BFIN_FUNCDESC_GOTOFF17M4:    howto manager.      (line  990)
+* BFD_RELOC_BFIN_FUNCDESC_GOTOFFHI:      howto manager.      (line  991)
+* BFD_RELOC_BFIN_FUNCDESC_GOTOFFLO:      howto manager.      (line  992)
+* BFD_RELOC_BFIN_FUNCDESC_VALUE:         howto manager.      (line  989)
+* BFD_RELOC_BFIN_GOT:                    howto manager.      (line  997)
+* BFD_RELOC_BFIN_GOT17M4:                howto manager.      (line  982)
+* BFD_RELOC_BFIN_GOTHI:                  howto manager.      (line  983)
+* BFD_RELOC_BFIN_GOTLO:                  howto manager.      (line  984)
+* BFD_RELOC_BFIN_GOTOFF17M4:             howto manager.      (line  993)
+* BFD_RELOC_BFIN_GOTOFFHI:               howto manager.      (line  994)
+* BFD_RELOC_BFIN_GOTOFFLO:               howto manager.      (line  995)
+* BFD_RELOC_BFIN_PLTPC:                  howto manager.      (line  999)
+* BFD_RELOC_C6000_ABS_H16:               howto manager.      (line 1254)
+* BFD_RELOC_C6000_ABS_L16:               howto manager.      (line 1253)
+* BFD_RELOC_C6000_ABS_S16:               howto manager.      (line 1252)
+* BFD_RELOC_C6000_ALIGN:                 howto manager.      (line 1275)
+* BFD_RELOC_C6000_COPY:                  howto manager.      (line 1270)
+* BFD_RELOC_C6000_DSBT_INDEX:            howto manager.      (line 1268)
+* BFD_RELOC_C6000_EHTYPE:                howto manager.      (line 1272)
+* BFD_RELOC_C6000_FPHEAD:                howto manager.      (line 1276)
+* BFD_RELOC_C6000_JUMP_SLOT:             howto manager.      (line 1271)
+* BFD_RELOC_C6000_NOCMP:                 howto manager.      (line 1277)
+* BFD_RELOC_C6000_PCR_H16:               howto manager.      (line 1273)
+* BFD_RELOC_C6000_PCR_L16:               howto manager.      (line 1274)
+* BFD_RELOC_C6000_PCR_S10:               howto manager.      (line 1250)
+* BFD_RELOC_C6000_PCR_S12:               howto manager.      (line 1249)
+* BFD_RELOC_C6000_PCR_S21:               howto manager.      (line 1248)
+* BFD_RELOC_C6000_PCR_S7:                howto manager.      (line 1251)
+* BFD_RELOC_C6000_PREL31:                howto manager.      (line 1269)
+* BFD_RELOC_C6000_SBR_GOT_H16_W:         howto manager.      (line 1267)
+* BFD_RELOC_C6000_SBR_GOT_L16_W:         howto manager.      (line 1266)
+* BFD_RELOC_C6000_SBR_GOT_U15_W:         howto manager.      (line 1265)
+* BFD_RELOC_C6000_SBR_H16_B:             howto manager.      (line 1262)
+* BFD_RELOC_C6000_SBR_H16_H:             howto manager.      (line 1263)
+* BFD_RELOC_C6000_SBR_H16_W:             howto manager.      (line 1264)
+* BFD_RELOC_C6000_SBR_L16_B:             howto manager.      (line 1259)
+* BFD_RELOC_C6000_SBR_L16_H:             howto manager.      (line 1260)
+* BFD_RELOC_C6000_SBR_L16_W:             howto manager.      (line 1261)
+* BFD_RELOC_C6000_SBR_S16:               howto manager.      (line 1258)
+* BFD_RELOC_C6000_SBR_U15_B:             howto manager.      (line 1255)
+* BFD_RELOC_C6000_SBR_U15_H:             howto manager.      (line 1256)
+* BFD_RELOC_C6000_SBR_U15_W:             howto manager.      (line 1257)
+* bfd_reloc_code_type:                   howto manager.      (line    9)
+* BFD_RELOC_CR16_ABS20:                  howto manager.      (line 1923)
+* BFD_RELOC_CR16_ABS24:                  howto manager.      (line 1924)
+* BFD_RELOC_CR16_DISP16:                 howto manager.      (line 1934)
+* BFD_RELOC_CR16_DISP20:                 howto manager.      (line 1935)
+* BFD_RELOC_CR16_DISP24:                 howto manager.      (line 1936)
+* BFD_RELOC_CR16_DISP24a:                howto manager.      (line 1937)
+* BFD_RELOC_CR16_DISP4:                  howto manager.      (line 1932)
+* BFD_RELOC_CR16_DISP8:                  howto manager.      (line 1933)
+* BFD_RELOC_CR16_GLOB_DAT:               howto manager.      (line 1943)
+* BFD_RELOC_CR16_GOTC_REGREL20:          howto manager.      (line 1942)
+* BFD_RELOC_CR16_GOT_REGREL20:           howto manager.      (line 1941)
+* BFD_RELOC_CR16_IMM16:                  howto manager.      (line 1927)
+* BFD_RELOC_CR16_IMM20:                  howto manager.      (line 1928)
+* BFD_RELOC_CR16_IMM24:                  howto manager.      (line 1929)
+* BFD_RELOC_CR16_IMM32:                  howto manager.      (line 1930)
+* BFD_RELOC_CR16_IMM32a:                 howto manager.      (line 1931)
+* BFD_RELOC_CR16_IMM4:                   howto manager.      (line 1925)
+* BFD_RELOC_CR16_IMM8:                   howto manager.      (line 1926)
+* BFD_RELOC_CR16_NUM16:                  howto manager.      (line 1912)
+* BFD_RELOC_CR16_NUM32:                  howto manager.      (line 1913)
+* BFD_RELOC_CR16_NUM32a:                 howto manager.      (line 1914)
+* BFD_RELOC_CR16_NUM8:                   howto manager.      (line 1911)
+* BFD_RELOC_CR16_REGREL0:                howto manager.      (line 1915)
+* BFD_RELOC_CR16_REGREL14:               howto manager.      (line 1918)
+* BFD_RELOC_CR16_REGREL14a:              howto manager.      (line 1919)
+* BFD_RELOC_CR16_REGREL16:               howto manager.      (line 1920)
+* BFD_RELOC_CR16_REGREL20:               howto manager.      (line 1921)
+* BFD_RELOC_CR16_REGREL20a:              howto manager.      (line 1922)
+* BFD_RELOC_CR16_REGREL4:                howto manager.      (line 1916)
+* BFD_RELOC_CR16_REGREL4a:               howto manager.      (line 1917)
+* BFD_RELOC_CR16_SWITCH16:               howto manager.      (line 1939)
+* BFD_RELOC_CR16_SWITCH32:               howto manager.      (line 1940)
+* BFD_RELOC_CR16_SWITCH8:                howto manager.      (line 1938)
+* BFD_RELOC_CRIS_16_DTPREL:              howto manager.      (line 2003)
+* BFD_RELOC_CRIS_16_GOT:                 howto manager.      (line 1985)
+* BFD_RELOC_CRIS_16_GOTPLT:              howto manager.      (line 1989)
+* BFD_RELOC_CRIS_16_GOT_GD:              howto manager.      (line 1999)
+* BFD_RELOC_CRIS_16_GOT_TPREL:           howto manager.      (line 2005)
+* BFD_RELOC_CRIS_16_TPREL:               howto manager.      (line 2007)
+* BFD_RELOC_CRIS_32_DTPREL:              howto manager.      (line 2002)
+* BFD_RELOC_CRIS_32_GD:                  howto manager.      (line 2000)
+* BFD_RELOC_CRIS_32_GOT:                 howto manager.      (line 1983)
+* BFD_RELOC_CRIS_32_GOTPLT:              howto manager.      (line 1987)
+* BFD_RELOC_CRIS_32_GOTREL:              howto manager.      (line 1991)
+* BFD_RELOC_CRIS_32_GOT_GD:              howto manager.      (line 1998)
+* BFD_RELOC_CRIS_32_GOT_TPREL:           howto manager.      (line 2004)
+* BFD_RELOC_CRIS_32_IE:                  howto manager.      (line 2009)
+* BFD_RELOC_CRIS_32_PLT_GOTREL:          howto manager.      (line 1993)
+* BFD_RELOC_CRIS_32_PLT_PCREL:           howto manager.      (line 1995)
+* BFD_RELOC_CRIS_32_TPREL:               howto manager.      (line 2006)
+* BFD_RELOC_CRIS_BDISP8:                 howto manager.      (line 1966)
+* BFD_RELOC_CRIS_COPY:                   howto manager.      (line 1978)
+* BFD_RELOC_CRIS_DTP:                    howto manager.      (line 2001)
+* BFD_RELOC_CRIS_DTPMOD:                 howto manager.      (line 2008)
+* BFD_RELOC_CRIS_GLOB_DAT:               howto manager.      (line 1979)
+* BFD_RELOC_CRIS_JUMP_SLOT:              howto manager.      (line 1980)
+* BFD_RELOC_CRIS_LAPCQ_OFFSET:           howto manager.      (line 1974)
+* BFD_RELOC_CRIS_RELATIVE:               howto manager.      (line 1981)
+* BFD_RELOC_CRIS_SIGNED_16:              howto manager.      (line 1972)
+* BFD_RELOC_CRIS_SIGNED_6:               howto manager.      (line 1968)
+* BFD_RELOC_CRIS_SIGNED_8:               howto manager.      (line 1970)
+* BFD_RELOC_CRIS_UNSIGNED_16:            howto manager.      (line 1973)
+* BFD_RELOC_CRIS_UNSIGNED_4:             howto manager.      (line 1975)
+* BFD_RELOC_CRIS_UNSIGNED_5:             howto manager.      (line 1967)
+* BFD_RELOC_CRIS_UNSIGNED_6:             howto manager.      (line 1969)
+* BFD_RELOC_CRIS_UNSIGNED_8:             howto manager.      (line 1971)
+* BFD_RELOC_CRX_ABS16:                   howto manager.      (line 1955)
+* BFD_RELOC_CRX_ABS32:                   howto manager.      (line 1956)
+* BFD_RELOC_CRX_IMM16:                   howto manager.      (line 1960)
+* BFD_RELOC_CRX_IMM32:                   howto manager.      (line 1961)
+* BFD_RELOC_CRX_NUM16:                   howto manager.      (line 1958)
+* BFD_RELOC_CRX_NUM32:                   howto manager.      (line 1959)
+* BFD_RELOC_CRX_NUM8:                    howto manager.      (line 1957)
+* BFD_RELOC_CRX_REGREL12:                howto manager.      (line 1951)
+* BFD_RELOC_CRX_REGREL22:                howto manager.      (line 1952)
+* BFD_RELOC_CRX_REGREL28:                howto manager.      (line 1953)
+* BFD_RELOC_CRX_REGREL32:                howto manager.      (line 1954)
+* BFD_RELOC_CRX_REL16:                   howto manager.      (line 1948)
+* BFD_RELOC_CRX_REL24:                   howto manager.      (line 1949)
+* BFD_RELOC_CRX_REL32:                   howto manager.      (line 1950)
+* BFD_RELOC_CRX_REL4:                    howto manager.      (line 1945)
+* BFD_RELOC_CRX_REL8:                    howto manager.      (line 1946)
+* BFD_RELOC_CRX_REL8_CMP:                howto manager.      (line 1947)
+* BFD_RELOC_CRX_SWITCH16:                howto manager.      (line 1963)
+* BFD_RELOC_CRX_SWITCH32:                howto manager.      (line 1964)
+* BFD_RELOC_CRX_SWITCH8:                 howto manager.      (line 1962)
+* BFD_RELOC_CTOR:                        howto manager.      (line  708)
+* BFD_RELOC_D10V_10_PCREL_L:             howto manager.      (line 1044)
+* BFD_RELOC_D10V_10_PCREL_R:             howto manager.      (line 1041)
+* BFD_RELOC_D10V_18:                     howto manager.      (line 1048)
+* BFD_RELOC_D10V_18_PCREL:               howto manager.      (line 1050)
+* BFD_RELOC_D30V_15:                     howto manager.      (line 1061)
+* BFD_RELOC_D30V_15_PCREL:               howto manager.      (line 1064)
+* BFD_RELOC_D30V_15_PCREL_R:             howto manager.      (line 1067)
+* BFD_RELOC_D30V_21:                     howto manager.      (line 1071)
+* BFD_RELOC_D30V_21_PCREL:               howto manager.      (line 1074)
+* BFD_RELOC_D30V_21_PCREL_R:             howto manager.      (line 1077)
+* BFD_RELOC_D30V_32:                     howto manager.      (line 1081)
+* BFD_RELOC_D30V_32_PCREL:               howto manager.      (line 1083)
+* BFD_RELOC_D30V_6:                      howto manager.      (line 1052)
+* BFD_RELOC_D30V_9_PCREL:                howto manager.      (line 1054)
+* BFD_RELOC_D30V_9_PCREL_R:              howto manager.      (line 1057)
+* BFD_RELOC_DLX_HI16_S:                  howto manager.      (line 1085)
+* BFD_RELOC_DLX_JMP26:                   howto manager.      (line 1089)
+* BFD_RELOC_DLX_LO16:                    howto manager.      (line 1087)
+* BFD_RELOC_EPIPHANY_HIGH:               howto manager.      (line 2745)
+* BFD_RELOC_EPIPHANY_IMM11:              howto manager.      (line 2751)
+* BFD_RELOC_EPIPHANY_IMM8:               howto manager.      (line 2754)
+* BFD_RELOC_EPIPHANY_LOW:                howto manager.      (line 2747)
+* BFD_RELOC_EPIPHANY_SIMM11:             howto manager.      (line 2749)
+* BFD_RELOC_EPIPHANY_SIMM24:             howto manager.      (line 2743)
+* BFD_RELOC_EPIPHANY_SIMM8:              howto manager.      (line 2741)
+* BFD_RELOC_FR30_10_IN_8:                howto manager.      (line 1293)
+* BFD_RELOC_FR30_12_PCREL:               howto manager.      (line 1299)
+* BFD_RELOC_FR30_20:                     howto manager.      (line 1281)
+* BFD_RELOC_FR30_48:                     howto manager.      (line 1279)
+* BFD_RELOC_FR30_6_IN_4:                 howto manager.      (line 1284)
+* BFD_RELOC_FR30_8_IN_8:                 howto manager.      (line 1287)
+* BFD_RELOC_FR30_9_IN_8:                 howto manager.      (line 1290)
+* BFD_RELOC_FR30_9_PCREL:                howto manager.      (line 1296)
+* BFD_RELOC_FRV_FUNCDESC:                howto manager.      (line  438)
+* BFD_RELOC_FRV_FUNCDESC_GOT12:          howto manager.      (line  439)
+* BFD_RELOC_FRV_FUNCDESC_GOTHI:          howto manager.      (line  440)
+* BFD_RELOC_FRV_FUNCDESC_GOTLO:          howto manager.      (line  441)
+* BFD_RELOC_FRV_FUNCDESC_GOTOFF12:       howto manager.      (line  443)
+* BFD_RELOC_FRV_FUNCDESC_GOTOFFHI:       howto manager.      (line  444)
+* BFD_RELOC_FRV_FUNCDESC_GOTOFFLO:       howto manager.      (line  445)
+* BFD_RELOC_FRV_FUNCDESC_VALUE:          howto manager.      (line  442)
+* BFD_RELOC_FRV_GETTLSOFF:               howto manager.      (line  449)
+* BFD_RELOC_FRV_GETTLSOFF_RELAX:         howto manager.      (line  462)
+* BFD_RELOC_FRV_GOT12:                   howto manager.      (line  435)
+* BFD_RELOC_FRV_GOTHI:                   howto manager.      (line  436)
+* BFD_RELOC_FRV_GOTLO:                   howto manager.      (line  437)
+* BFD_RELOC_FRV_GOTOFF12:                howto manager.      (line  446)
+* BFD_RELOC_FRV_GOTOFFHI:                howto manager.      (line  447)
+* BFD_RELOC_FRV_GOTOFFLO:                howto manager.      (line  448)
+* BFD_RELOC_FRV_GOTTLSDESC12:            howto manager.      (line  451)
+* BFD_RELOC_FRV_GOTTLSDESCHI:            howto manager.      (line  452)
+* BFD_RELOC_FRV_GOTTLSDESCLO:            howto manager.      (line  453)
+* BFD_RELOC_FRV_GOTTLSOFF12:             howto manager.      (line  457)
+* BFD_RELOC_FRV_GOTTLSOFFHI:             howto manager.      (line  458)
+* BFD_RELOC_FRV_GOTTLSOFFLO:             howto manager.      (line  459)
+* BFD_RELOC_FRV_GPREL12:                 howto manager.      (line  430)
+* BFD_RELOC_FRV_GPREL32:                 howto manager.      (line  432)
+* BFD_RELOC_FRV_GPRELHI:                 howto manager.      (line  433)
+* BFD_RELOC_FRV_GPRELLO:                 howto manager.      (line  434)
+* BFD_RELOC_FRV_GPRELU12:                howto manager.      (line  431)
+* BFD_RELOC_FRV_HI16:                    howto manager.      (line  429)
+* BFD_RELOC_FRV_LABEL16:                 howto manager.      (line  426)
+* BFD_RELOC_FRV_LABEL24:                 howto manager.      (line  427)
+* BFD_RELOC_FRV_LO16:                    howto manager.      (line  428)
+* BFD_RELOC_FRV_TLSDESC_RELAX:           howto manager.      (line  461)
+* BFD_RELOC_FRV_TLSDESC_VALUE:           howto manager.      (line  450)
+* BFD_RELOC_FRV_TLSMOFF:                 howto manager.      (line  464)
+* BFD_RELOC_FRV_TLSMOFF12:               howto manager.      (line  454)
+* BFD_RELOC_FRV_TLSMOFFHI:               howto manager.      (line  455)
+* BFD_RELOC_FRV_TLSMOFFLO:               howto manager.      (line  456)
+* BFD_RELOC_FRV_TLSOFF:                  howto manager.      (line  460)
+* BFD_RELOC_FRV_TLSOFF_RELAX:            howto manager.      (line  463)
+* BFD_RELOC_GPREL16:                     howto manager.      (line  114)
+* BFD_RELOC_GPREL32:                     howto manager.      (line  115)
+* BFD_RELOC_H8_DIR16A8:                  howto manager.      (line 2047)
+* BFD_RELOC_H8_DIR16R8:                  howto manager.      (line 2048)
+* BFD_RELOC_H8_DIR24A8:                  howto manager.      (line 2049)
+* BFD_RELOC_H8_DIR24R8:                  howto manager.      (line 2050)
+* BFD_RELOC_H8_DIR32A16:                 howto manager.      (line 2051)
+* BFD_RELOC_H8_DISP32A16:                howto manager.      (line 2052)
+* BFD_RELOC_HI16:                        howto manager.      (line  316)
+* BFD_RELOC_HI16_BASEREL:                howto manager.      (line   94)
+* BFD_RELOC_HI16_GOTOFF:                 howto manager.      (line   53)
+* BFD_RELOC_HI16_PCREL:                  howto manager.      (line  325)
+* BFD_RELOC_HI16_PLTOFF:                 howto manager.      (line   65)
+* BFD_RELOC_HI16_S:                      howto manager.      (line  318)
+* BFD_RELOC_HI16_S_BASEREL:              howto manager.      (line   95)
+* BFD_RELOC_HI16_S_GOTOFF:               howto manager.      (line   54)
+* BFD_RELOC_HI16_S_PCREL:                howto manager.      (line  327)
+* BFD_RELOC_HI16_S_PLTOFF:               howto manager.      (line   66)
+* BFD_RELOC_HI22:                        howto manager.      (line  110)
+* BFD_RELOC_I370_D12:                    howto manager.      (line  706)
+* BFD_RELOC_I960_CALLJ:                  howto manager.      (line  120)
+* BFD_RELOC_IA64_COPY:                   howto manager.      (line 1772)
+* BFD_RELOC_IA64_DIR32LSB:               howto manager.      (line 1717)
+* BFD_RELOC_IA64_DIR32MSB:               howto manager.      (line 1716)
+* BFD_RELOC_IA64_DIR64LSB:               howto manager.      (line 1719)
+* BFD_RELOC_IA64_DIR64MSB:               howto manager.      (line 1718)
+* BFD_RELOC_IA64_DTPMOD64LSB:            howto manager.      (line 1782)
+* BFD_RELOC_IA64_DTPMOD64MSB:            howto manager.      (line 1781)
+* BFD_RELOC_IA64_DTPREL14:               howto manager.      (line 1784)
+* BFD_RELOC_IA64_DTPREL22:               howto manager.      (line 1785)
+* BFD_RELOC_IA64_DTPREL32LSB:            howto manager.      (line 1788)
+* BFD_RELOC_IA64_DTPREL32MSB:            howto manager.      (line 1787)
+* BFD_RELOC_IA64_DTPREL64I:              howto manager.      (line 1786)
+* BFD_RELOC_IA64_DTPREL64LSB:            howto manager.      (line 1790)
+* BFD_RELOC_IA64_DTPREL64MSB:            howto manager.      (line 1789)
+* BFD_RELOC_IA64_FPTR32LSB:              howto manager.      (line 1734)
+* BFD_RELOC_IA64_FPTR32MSB:              howto manager.      (line 1733)
+* BFD_RELOC_IA64_FPTR64I:                howto manager.      (line 1732)
+* BFD_RELOC_IA64_FPTR64LSB:              howto manager.      (line 1736)
+* BFD_RELOC_IA64_FPTR64MSB:              howto manager.      (line 1735)
+* BFD_RELOC_IA64_GPREL22:                howto manager.      (line 1720)
+* BFD_RELOC_IA64_GPREL32LSB:             howto manager.      (line 1723)
+* BFD_RELOC_IA64_GPREL32MSB:             howto manager.      (line 1722)
+* BFD_RELOC_IA64_GPREL64I:               howto manager.      (line 1721)
+* BFD_RELOC_IA64_GPREL64LSB:             howto manager.      (line 1725)
+* BFD_RELOC_IA64_GPREL64MSB:             howto manager.      (line 1724)
+* BFD_RELOC_IA64_IMM14:                  howto manager.      (line 1713)
+* BFD_RELOC_IA64_IMM22:                  howto manager.      (line 1714)
+* BFD_RELOC_IA64_IMM64:                  howto manager.      (line 1715)
+* BFD_RELOC_IA64_IPLTLSB:                howto manager.      (line 1771)
+* BFD_RELOC_IA64_IPLTMSB:                howto manager.      (line 1770)
+* BFD_RELOC_IA64_LDXMOV:                 howto manager.      (line 1774)
+* BFD_RELOC_IA64_LTOFF22:                howto manager.      (line 1726)
+* BFD_RELOC_IA64_LTOFF22X:               howto manager.      (line 1773)
+* BFD_RELOC_IA64_LTOFF64I:               howto manager.      (line 1727)
+* BFD_RELOC_IA64_LTOFF_DTPMOD22:         howto manager.      (line 1783)
+* BFD_RELOC_IA64_LTOFF_DTPREL22:         howto manager.      (line 1791)
+* BFD_RELOC_IA64_LTOFF_FPTR22:           howto manager.      (line 1748)
+* BFD_RELOC_IA64_LTOFF_FPTR32LSB:        howto manager.      (line 1751)
+* BFD_RELOC_IA64_LTOFF_FPTR32MSB:        howto manager.      (line 1750)
+* BFD_RELOC_IA64_LTOFF_FPTR64I:          howto manager.      (line 1749)
+* BFD_RELOC_IA64_LTOFF_FPTR64LSB:        howto manager.      (line 1753)
+* BFD_RELOC_IA64_LTOFF_FPTR64MSB:        howto manager.      (line 1752)
+* BFD_RELOC_IA64_LTOFF_TPREL22:          howto manager.      (line 1780)
+* BFD_RELOC_IA64_LTV32LSB:               howto manager.      (line 1767)
+* BFD_RELOC_IA64_LTV32MSB:               howto manager.      (line 1766)
+* BFD_RELOC_IA64_LTV64LSB:               howto manager.      (line 1769)
+* BFD_RELOC_IA64_LTV64MSB:               howto manager.      (line 1768)
+* BFD_RELOC_IA64_PCREL21B:               howto manager.      (line 1737)
+* BFD_RELOC_IA64_PCREL21BI:              howto manager.      (line 1738)
+* BFD_RELOC_IA64_PCREL21F:               howto manager.      (line 1740)
+* BFD_RELOC_IA64_PCREL21M:               howto manager.      (line 1739)
+* BFD_RELOC_IA64_PCREL22:                howto manager.      (line 1741)
+* BFD_RELOC_IA64_PCREL32LSB:             howto manager.      (line 1745)
+* BFD_RELOC_IA64_PCREL32MSB:             howto manager.      (line 1744)
+* BFD_RELOC_IA64_PCREL60B:               howto manager.      (line 1742)
+* BFD_RELOC_IA64_PCREL64I:               howto manager.      (line 1743)
+* BFD_RELOC_IA64_PCREL64LSB:             howto manager.      (line 1747)
+* BFD_RELOC_IA64_PCREL64MSB:             howto manager.      (line 1746)
+* BFD_RELOC_IA64_PLTOFF22:               howto manager.      (line 1728)
+* BFD_RELOC_IA64_PLTOFF64I:              howto manager.      (line 1729)
+* BFD_RELOC_IA64_PLTOFF64LSB:            howto manager.      (line 1731)
+* BFD_RELOC_IA64_PLTOFF64MSB:            howto manager.      (line 1730)
+* BFD_RELOC_IA64_REL32LSB:               howto manager.      (line 1763)
+* BFD_RELOC_IA64_REL32MSB:               howto manager.      (line 1762)
+* BFD_RELOC_IA64_REL64LSB:               howto manager.      (line 1765)
+* BFD_RELOC_IA64_REL64MSB:               howto manager.      (line 1764)
+* BFD_RELOC_IA64_SECREL32LSB:            howto manager.      (line 1759)
+* BFD_RELOC_IA64_SECREL32MSB:            howto manager.      (line 1758)
+* BFD_RELOC_IA64_SECREL64LSB:            howto manager.      (line 1761)
+* BFD_RELOC_IA64_SECREL64MSB:            howto manager.      (line 1760)
+* BFD_RELOC_IA64_SEGREL32LSB:            howto manager.      (line 1755)
+* BFD_RELOC_IA64_SEGREL32MSB:            howto manager.      (line 1754)
+* BFD_RELOC_IA64_SEGREL64LSB:            howto manager.      (line 1757)
+* BFD_RELOC_IA64_SEGREL64MSB:            howto manager.      (line 1756)
+* BFD_RELOC_IA64_TPREL14:                howto manager.      (line 1775)
+* BFD_RELOC_IA64_TPREL22:                howto manager.      (line 1776)
+* BFD_RELOC_IA64_TPREL64I:               howto manager.      (line 1777)
+* BFD_RELOC_IA64_TPREL64LSB:             howto manager.      (line 1779)
+* BFD_RELOC_IA64_TPREL64MSB:             howto manager.      (line 1778)
+* BFD_RELOC_IP2K_ADDR16CJP:              howto manager.      (line 1674)
+* BFD_RELOC_IP2K_BANK:                   howto manager.      (line 1672)
+* BFD_RELOC_IP2K_EX8DATA:                howto manager.      (line 1680)
+* BFD_RELOC_IP2K_FR9:                    howto manager.      (line 1670)
+* BFD_RELOC_IP2K_FR_OFFSET:              howto manager.      (line 1689)
+* BFD_RELOC_IP2K_HI8DATA:                howto manager.      (line 1679)
+* BFD_RELOC_IP2K_HI8INSN:                howto manager.      (line 1683)
+* BFD_RELOC_IP2K_LO8DATA:                howto manager.      (line 1678)
+* BFD_RELOC_IP2K_LO8INSN:                howto manager.      (line 1682)
+* BFD_RELOC_IP2K_PAGE3:                  howto manager.      (line 1676)
+* BFD_RELOC_IP2K_PC_SKIP:                howto manager.      (line 1685)
+* BFD_RELOC_IP2K_TEXT:                   howto manager.      (line 1687)
+* BFD_RELOC_IQ2000_OFFSET_16:            howto manager.      (line 2140)
+* BFD_RELOC_IQ2000_OFFSET_21:            howto manager.      (line 2141)
+* BFD_RELOC_IQ2000_UHI16:                howto manager.      (line 2142)
+* BFD_RELOC_LM32_16_GOT:                 howto manager.      (line 2232)
+* BFD_RELOC_LM32_BRANCH:                 howto manager.      (line 2231)
+* BFD_RELOC_LM32_CALL:                   howto manager.      (line 2230)
+* BFD_RELOC_LM32_COPY:                   howto manager.      (line 2235)
+* BFD_RELOC_LM32_GLOB_DAT:               howto manager.      (line 2236)
+* BFD_RELOC_LM32_GOTOFF_HI16:            howto manager.      (line 2233)
+* BFD_RELOC_LM32_GOTOFF_LO16:            howto manager.      (line 2234)
+* BFD_RELOC_LM32_JMP_SLOT:               howto manager.      (line 2237)
+* BFD_RELOC_LM32_RELATIVE:               howto manager.      (line 2238)
+* BFD_RELOC_LO10:                        howto manager.      (line  111)
+* BFD_RELOC_LO16:                        howto manager.      (line  323)
+* BFD_RELOC_LO16_BASEREL:                howto manager.      (line   93)
+* BFD_RELOC_LO16_GOTOFF:                 howto manager.      (line   52)
+* BFD_RELOC_LO16_PCREL:                  howto manager.      (line  329)
+* BFD_RELOC_LO16_PLTOFF:                 howto manager.      (line   64)
+* BFD_RELOC_M32C_HI8:                    howto manager.      (line 1091)
+* BFD_RELOC_M32C_RL_1ADDR:               howto manager.      (line 1093)
+* BFD_RELOC_M32C_RL_2ADDR:               howto manager.      (line 1094)
+* BFD_RELOC_M32C_RL_JUMP:                howto manager.      (line 1092)
+* BFD_RELOC_M32R_10_PCREL:               howto manager.      (line 1099)
+* BFD_RELOC_M32R_18_PCREL:               howto manager.      (line 1102)
+* BFD_RELOC_M32R_24:                     howto manager.      (line 1096)
+* BFD_RELOC_M32R_26_PCREL:               howto manager.      (line 1104)
+* BFD_RELOC_M32R_26_PLTREL:              howto manager.      (line 1118)
+* BFD_RELOC_M32R_COPY:                   howto manager.      (line 1119)
+* BFD_RELOC_M32R_GLOB_DAT:               howto manager.      (line 1120)
+* BFD_RELOC_M32R_GOT16_HI_SLO:           howto manager.      (line 1129)
+* BFD_RELOC_M32R_GOT16_HI_ULO:           howto manager.      (line 1128)
+* BFD_RELOC_M32R_GOT16_LO:               howto manager.      (line 1130)
+* BFD_RELOC_M32R_GOT24:                  howto manager.      (line 1117)
+* BFD_RELOC_M32R_GOTOFF:                 howto manager.      (line 1123)
+* BFD_RELOC_M32R_GOTOFF_HI_SLO:          howto manager.      (line 1125)
+* BFD_RELOC_M32R_GOTOFF_HI_ULO:          howto manager.      (line 1124)
+* BFD_RELOC_M32R_GOTOFF_LO:              howto manager.      (line 1126)
+* BFD_RELOC_M32R_GOTPC24:                howto manager.      (line 1127)
+* BFD_RELOC_M32R_GOTPC_HI_SLO:           howto manager.      (line 1132)
+* BFD_RELOC_M32R_GOTPC_HI_ULO:           howto manager.      (line 1131)
+* BFD_RELOC_M32R_GOTPC_LO:               howto manager.      (line 1133)
+* BFD_RELOC_M32R_HI16_SLO:               howto manager.      (line 1109)
+* BFD_RELOC_M32R_HI16_ULO:               howto manager.      (line 1106)
+* BFD_RELOC_M32R_JMP_SLOT:               howto manager.      (line 1121)
+* BFD_RELOC_M32R_LO16:                   howto manager.      (line 1112)
+* BFD_RELOC_M32R_RELATIVE:               howto manager.      (line 1122)
+* BFD_RELOC_M32R_SDA16:                  howto manager.      (line 1114)
+* BFD_RELOC_M68HC11_24:                  howto manager.      (line 1819)
+* BFD_RELOC_M68HC11_3B:                  howto manager.      (line 1799)
+* BFD_RELOC_M68HC11_HI8:                 howto manager.      (line 1793)
+* BFD_RELOC_M68HC11_LO16:                howto manager.      (line 1810)
+* BFD_RELOC_M68HC11_LO8:                 howto manager.      (line 1796)
+* BFD_RELOC_M68HC11_PAGE:                howto manager.      (line 1815)
+* BFD_RELOC_M68HC11_RL_GROUP:            howto manager.      (line 1806)
+* BFD_RELOC_M68HC11_RL_JUMP:             howto manager.      (line 1801)
+* BFD_RELOC_M68HC12_10_PCREL:            howto manager.      (line 1862)
+* BFD_RELOC_M68HC12_16B:                 howto manager.      (line 1858)
+* BFD_RELOC_M68HC12_5B:                  howto manager.      (line 1824)
+* BFD_RELOC_M68HC12_9B:                  howto manager.      (line 1856)
+* BFD_RELOC_M68HC12_9_PCREL:             howto manager.      (line 1860)
+* BFD_RELOC_M68HC12_HI8XG:               howto manager.      (line 1867)
+* BFD_RELOC_M68HC12_LO8XG:               howto manager.      (line 1864)
+* BFD_RELOC_MACH_O_LOCAL_SECTDIFF:       howto manager.      (line 2243)
+* BFD_RELOC_MACH_O_PAIR:                 howto manager.      (line 2245)
+* BFD_RELOC_MACH_O_SECTDIFF:             howto manager.      (line 2240)
+* BFD_RELOC_MACH_O_X86_64_BRANCH32:      howto manager.      (line 2247)
+* BFD_RELOC_MACH_O_X86_64_BRANCH8:       howto manager.      (line 2248)
+* BFD_RELOC_MACH_O_X86_64_GOT:           howto manager.      (line 2251)
+* BFD_RELOC_MACH_O_X86_64_GOT_LOAD:      howto manager.      (line 2253)
+* BFD_RELOC_MACH_O_X86_64_PCREL32_1:     howto manager.      (line 2260)
+* BFD_RELOC_MACH_O_X86_64_PCREL32_2:     howto manager.      (line 2262)
+* BFD_RELOC_MACH_O_X86_64_PCREL32_4:     howto manager.      (line 2264)
+* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR32:  howto manager.      (line 2256)
+* BFD_RELOC_MACH_O_X86_64_SUBTRACTOR64:  howto manager.      (line 2258)
+* BFD_RELOC_MCORE_PCREL_32:              howto manager.      (line 1305)
+* BFD_RELOC_MCORE_PCREL_IMM11BY2:        howto manager.      (line 1303)
+* BFD_RELOC_MCORE_PCREL_IMM4BY2:         howto manager.      (line 1304)
+* BFD_RELOC_MCORE_PCREL_IMM8BY4:         howto manager.      (line 1302)
+* BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2:    howto manager.      (line 1306)
+* BFD_RELOC_MCORE_RVA:                   howto manager.      (line 1307)
+* BFD_RELOC_MEP_16:                      howto manager.      (line 1310)
+* BFD_RELOC_MEP_32:                      howto manager.      (line 1311)
+* BFD_RELOC_MEP_8:                       howto manager.      (line 1309)
+* BFD_RELOC_MEP_ADDR24A4:                howto manager.      (line 1326)
+* BFD_RELOC_MEP_GNU_VTENTRY:             howto manager.      (line 1328)
+* BFD_RELOC_MEP_GNU_VTINHERIT:           howto manager.      (line 1327)
+* BFD_RELOC_MEP_GPREL:                   howto manager.      (line 1320)
+* BFD_RELOC_MEP_HI16S:                   howto manager.      (line 1319)
+* BFD_RELOC_MEP_HI16U:                   howto manager.      (line 1318)
+* BFD_RELOC_MEP_LOW16:                   howto manager.      (line 1317)
+* BFD_RELOC_MEP_PCABS24A2:               howto manager.      (line 1316)
+* BFD_RELOC_MEP_PCREL12A2:               howto manager.      (line 1313)
+* BFD_RELOC_MEP_PCREL17A2:               howto manager.      (line 1314)
+* BFD_RELOC_MEP_PCREL24A2:               howto manager.      (line 1315)
+* BFD_RELOC_MEP_PCREL8A2:                howto manager.      (line 1312)
+* BFD_RELOC_MEP_TPREL:                   howto manager.      (line 1321)
+* BFD_RELOC_MEP_TPREL7:                  howto manager.      (line 1322)
+* BFD_RELOC_MEP_TPREL7A2:                howto manager.      (line 1323)
+* BFD_RELOC_MEP_TPREL7A4:                howto manager.      (line 1324)
+* BFD_RELOC_MEP_UIMM24:                  howto manager.      (line 1325)
+* BFD_RELOC_METAG_COPY:                  howto manager.      (line 1349)
+* BFD_RELOC_METAG_GETSETOFF:             howto manager.      (line 1333)
+* BFD_RELOC_METAG_GETSET_GOT:            howto manager.      (line 1341)
+* BFD_RELOC_METAG_GETSET_GOTOFF:         howto manager.      (line 1340)
+* BFD_RELOC_METAG_GLOB_DAT:              howto manager.      (line 1352)
+* BFD_RELOC_METAG_GOTOFF:                howto manager.      (line 1347)
+* BFD_RELOC_METAG_HI16_GOTOFF:           howto manager.      (line 1338)
+* BFD_RELOC_METAG_HI16_GOTPC:            howto manager.      (line 1342)
+* BFD_RELOC_METAG_HI16_PLT:              howto manager.      (line 1344)
+* BFD_RELOC_METAG_HIADDR16:              howto manager.      (line 1330)
+* BFD_RELOC_METAG_HIOG:                  howto manager.      (line 1334)
+* BFD_RELOC_METAG_JMP_SLOT:              howto manager.      (line 1350)
+* BFD_RELOC_METAG_LO16_GOTOFF:           howto manager.      (line 1339)
+* BFD_RELOC_METAG_LO16_GOTPC:            howto manager.      (line 1343)
+* BFD_RELOC_METAG_LO16_PLT:              howto manager.      (line 1345)
+* BFD_RELOC_METAG_LOADDR16:              howto manager.      (line 1331)
+* BFD_RELOC_METAG_LOOG:                  howto manager.      (line 1335)
+* BFD_RELOC_METAG_PLT:                   howto manager.      (line 1348)
+* BFD_RELOC_METAG_REL16:                 howto manager.      (line 1337)
+* BFD_RELOC_METAG_REL8:                  howto manager.      (line 1336)
+* BFD_RELOC_METAG_RELATIVE:              howto manager.      (line 1351)
+* BFD_RELOC_METAG_RELBRANCH:             howto manager.      (line 1332)
+* BFD_RELOC_METAG_RELBRANCH_PLT:         howto manager.      (line 1346)
+* BFD_RELOC_METAG_TLS_DTPMOD:            howto manager.      (line 1363)
+* BFD_RELOC_METAG_TLS_DTPOFF:            howto manager.      (line 1364)
+* BFD_RELOC_METAG_TLS_GD:                howto manager.      (line 1353)
+* BFD_RELOC_METAG_TLS_IE:                howto manager.      (line 1358)
+* BFD_RELOC_METAG_TLS_IENONPIC:          howto manager.      (line 1359)
+* BFD_RELOC_METAG_TLS_IENONPIC_HI16:     howto manager.      (line 1360)
+* BFD_RELOC_METAG_TLS_IENONPIC_LO16:     howto manager.      (line 1361)
+* BFD_RELOC_METAG_TLS_LDM:               howto manager.      (line 1354)
+* BFD_RELOC_METAG_TLS_LDO:               howto manager.      (line 1357)
+* BFD_RELOC_METAG_TLS_LDO_HI16:          howto manager.      (line 1355)
+* BFD_RELOC_METAG_TLS_LDO_LO16:          howto manager.      (line 1356)
+* BFD_RELOC_METAG_TLS_LE:                howto manager.      (line 1365)
+* BFD_RELOC_METAG_TLS_LE_HI16:           howto manager.      (line 1366)
+* BFD_RELOC_METAG_TLS_LE_LO16:           howto manager.      (line 1367)
+* BFD_RELOC_METAG_TLS_TPOFF:             howto manager.      (line 1362)
+* BFD_RELOC_MICROBLAZE_32_GOTOFF:        howto manager.      (line 2300)
+* BFD_RELOC_MICROBLAZE_32_LO:            howto manager.      (line 2266)
+* BFD_RELOC_MICROBLAZE_32_LO_PCREL:      howto manager.      (line 2269)
+* BFD_RELOC_MICROBLAZE_32_ROSDA:         howto manager.      (line 2272)
+* BFD_RELOC_MICROBLAZE_32_RWSDA:         howto manager.      (line 2275)
+* BFD_RELOC_MICROBLAZE_32_SYM_OP_SYM:    howto manager.      (line 2278)
+* BFD_RELOC_MICROBLAZE_32_TLSDTPMOD:     howto manager.      (line 2316)
+* BFD_RELOC_MICROBLAZE_32_TLSDTPREL:     howto manager.      (line 2318)
+* BFD_RELOC_MICROBLAZE_64_GOT:           howto manager.      (line 2289)
+* BFD_RELOC_MICROBLAZE_64_GOTOFF:        howto manager.      (line 2296)
+* BFD_RELOC_MICROBLAZE_64_GOTPC:         howto manager.      (line 2285)
+* BFD_RELOC_MICROBLAZE_64_NONE:          howto manager.      (line 2281)
+* BFD_RELOC_MICROBLAZE_64_PLT:           howto manager.      (line 2292)
+* BFD_RELOC_MICROBLAZE_64_TLS:           howto manager.      (line 2306)
+* BFD_RELOC_MICROBLAZE_64_TLSDTPREL:     howto manager.      (line 2320)
+* BFD_RELOC_MICROBLAZE_64_TLSGD:         howto manager.      (line 2308)
+* BFD_RELOC_MICROBLAZE_64_TLSGOTTPREL:   howto manager.      (line 2323)
+* BFD_RELOC_MICROBLAZE_64_TLSLD:         howto manager.      (line 2312)
+* BFD_RELOC_MICROBLAZE_64_TLSTPREL:      howto manager.      (line 2326)
+* BFD_RELOC_MICROBLAZE_COPY:             howto manager.      (line 2303)
+* BFD_RELOC_MICROMIPS_10_PCREL_S1:       howto manager.      (line  356)
+* BFD_RELOC_MICROMIPS_16_PCREL_S1:       howto manager.      (line  357)
+* BFD_RELOC_MICROMIPS_7_PCREL_S1:        howto manager.      (line  355)
+* BFD_RELOC_MICROMIPS_CALL16:            howto manager.      (line  367)
+* BFD_RELOC_MICROMIPS_CALL_HI16:         howto manager.      (line  373)
+* BFD_RELOC_MICROMIPS_CALL_LO16:         howto manager.      (line  375)
+* BFD_RELOC_MICROMIPS_GOT16:             howto manager.      (line  365)
+* BFD_RELOC_MICROMIPS_GOT_DISP:          howto manager.      (line  383)
+* BFD_RELOC_MICROMIPS_GOT_HI16:          howto manager.      (line  369)
+* BFD_RELOC_MICROMIPS_GOT_LO16:          howto manager.      (line  371)
+* BFD_RELOC_MICROMIPS_GOT_OFST:          howto manager.      (line  381)
+* BFD_RELOC_MICROMIPS_GOT_PAGE:          howto manager.      (line  379)
+* BFD_RELOC_MICROMIPS_GPREL16:           howto manager.      (line  359)
+* BFD_RELOC_MICROMIPS_HI16:              howto manager.      (line  360)
+* BFD_RELOC_MICROMIPS_HI16_S:            howto manager.      (line  361)
+* BFD_RELOC_MICROMIPS_HIGHER:            howto manager.      (line  392)
+* BFD_RELOC_MICROMIPS_HIGHEST:           howto manager.      (line  390)
+* BFD_RELOC_MICROMIPS_JALR:              howto manager.      (line  398)
+* BFD_RELOC_MICROMIPS_JMP:               howto manager.      (line  310)
+* BFD_RELOC_MICROMIPS_LITERAL:           howto manager.      (line  353)
+* BFD_RELOC_MICROMIPS_LO16:              howto manager.      (line  362)
+* BFD_RELOC_MICROMIPS_SCN_DISP:          howto manager.      (line  394)
+* BFD_RELOC_MICROMIPS_SUB:               howto manager.      (line  377)
+* BFD_RELOC_MICROMIPS_TLS_DTPREL_HI16:   howto manager.      (line  408)
+* BFD_RELOC_MICROMIPS_TLS_DTPREL_LO16:   howto manager.      (line  410)
+* BFD_RELOC_MICROMIPS_TLS_GD:            howto manager.      (line  404)
+* BFD_RELOC_MICROMIPS_TLS_GOTTPREL:      howto manager.      (line  412)
+* BFD_RELOC_MICROMIPS_TLS_LDM:           howto manager.      (line  406)
+* BFD_RELOC_MICROMIPS_TLS_TPREL_HI16:    howto manager.      (line  416)
+* BFD_RELOC_MICROMIPS_TLS_TPREL_LO16:    howto manager.      (line  418)
+* BFD_RELOC_MIPS16_CALL16:               howto manager.      (line  332)
+* BFD_RELOC_MIPS16_GOT16:                howto manager.      (line  331)
+* BFD_RELOC_MIPS16_GPREL:                howto manager.      (line  314)
+* BFD_RELOC_MIPS16_HI16:                 howto manager.      (line  335)
+* BFD_RELOC_MIPS16_HI16_S:               howto manager.      (line  337)
+* BFD_RELOC_MIPS16_JMP:                  howto manager.      (line  312)
+* BFD_RELOC_MIPS16_LO16:                 howto manager.      (line  342)
+* BFD_RELOC_MIPS16_TLS_DTPREL_HI16:      howto manager.      (line  346)
+* BFD_RELOC_MIPS16_TLS_DTPREL_LO16:      howto manager.      (line  347)
+* BFD_RELOC_MIPS16_TLS_GD:               howto manager.      (line  344)
+* BFD_RELOC_MIPS16_TLS_GOTTPREL:         howto manager.      (line  348)
+* BFD_RELOC_MIPS16_TLS_LDM:              howto manager.      (line  345)
+* BFD_RELOC_MIPS16_TLS_TPREL_HI16:       howto manager.      (line  349)
+* BFD_RELOC_MIPS16_TLS_TPREL_LO16:       howto manager.      (line  350)
+* BFD_RELOC_MIPS_CALL16:                 howto manager.      (line  366)
+* BFD_RELOC_MIPS_CALL_HI16:              howto manager.      (line  372)
+* BFD_RELOC_MIPS_CALL_LO16:              howto manager.      (line  374)
+* BFD_RELOC_MIPS_COPY:                   howto manager.      (line  421)
+* BFD_RELOC_MIPS_DELETE:                 howto manager.      (line  388)
+* BFD_RELOC_MIPS_EH:                     howto manager.      (line  419)
+* BFD_RELOC_MIPS_GOT16:                  howto manager.      (line  364)
+* BFD_RELOC_MIPS_GOT_DISP:               howto manager.      (line  382)
+* BFD_RELOC_MIPS_GOT_HI16:               howto manager.      (line  368)
+* BFD_RELOC_MIPS_GOT_LO16:               howto manager.      (line  370)
+* BFD_RELOC_MIPS_GOT_OFST:               howto manager.      (line  380)
+* BFD_RELOC_MIPS_GOT_PAGE:               howto manager.      (line  378)
+* BFD_RELOC_MIPS_HIGHER:                 howto manager.      (line  391)
+* BFD_RELOC_MIPS_HIGHEST:                howto manager.      (line  389)
+* BFD_RELOC_MIPS_INSERT_A:               howto manager.      (line  386)
+* BFD_RELOC_MIPS_INSERT_B:               howto manager.      (line  387)
+* BFD_RELOC_MIPS_JALR:                   howto manager.      (line  397)
+* BFD_RELOC_MIPS_JMP:                    howto manager.      (line  309)
+* BFD_RELOC_MIPS_JUMP_SLOT:              howto manager.      (line  422)
+* BFD_RELOC_MIPS_LITERAL:                howto manager.      (line  352)
+* BFD_RELOC_MIPS_REL16:                  howto manager.      (line  395)
+* BFD_RELOC_MIPS_RELGOT:                 howto manager.      (line  396)
+* BFD_RELOC_MIPS_SCN_DISP:               howto manager.      (line  393)
+* BFD_RELOC_MIPS_SHIFT5:                 howto manager.      (line  384)
+* BFD_RELOC_MIPS_SHIFT6:                 howto manager.      (line  385)
+* BFD_RELOC_MIPS_SUB:                    howto manager.      (line  376)
+* BFD_RELOC_MIPS_TLS_DTPMOD32:           howto manager.      (line  399)
+* BFD_RELOC_MIPS_TLS_DTPMOD64:           howto manager.      (line  401)
+* BFD_RELOC_MIPS_TLS_DTPREL32:           howto manager.      (line  400)
+* BFD_RELOC_MIPS_TLS_DTPREL64:           howto manager.      (line  402)
+* BFD_RELOC_MIPS_TLS_DTPREL_HI16:        howto manager.      (line  407)
+* BFD_RELOC_MIPS_TLS_DTPREL_LO16:        howto manager.      (line  409)
+* BFD_RELOC_MIPS_TLS_GD:                 howto manager.      (line  403)
+* BFD_RELOC_MIPS_TLS_GOTTPREL:           howto manager.      (line  411)
+* BFD_RELOC_MIPS_TLS_LDM:                howto manager.      (line  405)
+* BFD_RELOC_MIPS_TLS_TPREL32:            howto manager.      (line  413)
+* BFD_RELOC_MIPS_TLS_TPREL64:            howto manager.      (line  414)
+* BFD_RELOC_MIPS_TLS_TPREL_HI16:         howto manager.      (line  415)
+* BFD_RELOC_MIPS_TLS_TPREL_LO16:         howto manager.      (line  417)
+* BFD_RELOC_MMIX_ADDR19:                 howto manager.      (line 1391)
+* BFD_RELOC_MMIX_ADDR27:                 howto manager.      (line 1394)
+* BFD_RELOC_MMIX_BASE_PLUS_OFFSET:       howto manager.      (line 1403)
+* BFD_RELOC_MMIX_CBRANCH:                howto manager.      (line 1374)
+* BFD_RELOC_MMIX_CBRANCH_1:              howto manager.      (line 1376)
+* BFD_RELOC_MMIX_CBRANCH_2:              howto manager.      (line 1377)
+* BFD_RELOC_MMIX_CBRANCH_3:              howto manager.      (line 1378)
+* BFD_RELOC_MMIX_CBRANCH_J:              howto manager.      (line 1375)
+* BFD_RELOC_MMIX_GETA:                   howto manager.      (line 1369)
+* BFD_RELOC_MMIX_GETA_1:                 howto manager.      (line 1370)
+* BFD_RELOC_MMIX_GETA_2:                 howto manager.      (line 1371)
+* BFD_RELOC_MMIX_GETA_3:                 howto manager.      (line 1372)
+* BFD_RELOC_MMIX_JMP:                    howto manager.      (line 1386)
+* BFD_RELOC_MMIX_JMP_1:                  howto manager.      (line 1387)
+* BFD_RELOC_MMIX_JMP_2:                  howto manager.      (line 1388)
+* BFD_RELOC_MMIX_JMP_3:                  howto manager.      (line 1389)
+* BFD_RELOC_MMIX_LOCAL:                  howto manager.      (line 1406)
+* BFD_RELOC_MMIX_PUSHJ:                  howto manager.      (line 1380)
+* BFD_RELOC_MMIX_PUSHJ_1:                howto manager.      (line 1381)
+* BFD_RELOC_MMIX_PUSHJ_2:                howto manager.      (line 1382)
+* BFD_RELOC_MMIX_PUSHJ_3:                howto manager.      (line 1383)
+* BFD_RELOC_MMIX_PUSHJ_STUBBABLE:        howto manager.      (line 1384)
+* BFD_RELOC_MMIX_REG:                    howto manager.      (line 1400)
+* BFD_RELOC_MMIX_REG_OR_BYTE:            howto manager.      (line 1397)
+* BFD_RELOC_MN10300_16_PCREL:            howto manager.      (line  505)
+* BFD_RELOC_MN10300_32_PCREL:            howto manager.      (line  502)
+* BFD_RELOC_MN10300_ALIGN:               howto manager.      (line  489)
+* BFD_RELOC_MN10300_COPY:                howto manager.      (line  477)
+* BFD_RELOC_MN10300_GLOB_DAT:            howto manager.      (line  479)
+* BFD_RELOC_MN10300_GOT16:               howto manager.      (line  474)
+* BFD_RELOC_MN10300_GOT24:               howto manager.      (line  471)
+* BFD_RELOC_MN10300_GOT32:               howto manager.      (line  468)
+* BFD_RELOC_MN10300_GOTOFF24:            howto manager.      (line  466)
+* BFD_RELOC_MN10300_JMP_SLOT:            howto manager.      (line  481)
+* BFD_RELOC_MN10300_RELATIVE:            howto manager.      (line  483)
+* BFD_RELOC_MN10300_SYM_DIFF:            howto manager.      (line  485)
+* BFD_RELOC_MN10300_TLS_DTPMOD:          howto manager.      (line  498)
+* BFD_RELOC_MN10300_TLS_DTPOFF:          howto manager.      (line  499)
+* BFD_RELOC_MN10300_TLS_GD:              howto manager.      (line  492)
+* BFD_RELOC_MN10300_TLS_GOTIE:           howto manager.      (line  495)
+* BFD_RELOC_MN10300_TLS_IE:              howto manager.      (line  496)
+* BFD_RELOC_MN10300_TLS_LD:              howto manager.      (line  493)
+* BFD_RELOC_MN10300_TLS_LDO:             howto manager.      (line  494)
+* BFD_RELOC_MN10300_TLS_LE:              howto manager.      (line  497)
+* BFD_RELOC_MN10300_TLS_TPOFF:           howto manager.      (line  500)
+* BFD_RELOC_MOXIE_10_PCREL:              howto manager.      (line  424)
+* BFD_RELOC_MSP430X_ABS16:               howto manager.      (line 2100)
+* BFD_RELOC_MSP430X_ABS20_ADR_DST:       howto manager.      (line 2097)
+* BFD_RELOC_MSP430X_ABS20_ADR_SRC:       howto manager.      (line 2096)
+* BFD_RELOC_MSP430X_ABS20_EXT_DST:       howto manager.      (line 2094)
+* BFD_RELOC_MSP430X_ABS20_EXT_ODST:      howto manager.      (line 2095)
+* BFD_RELOC_MSP430X_ABS20_EXT_SRC:       howto manager.      (line 2093)
+* BFD_RELOC_MSP430X_PCR16:               howto manager.      (line 2098)
+* BFD_RELOC_MSP430X_PCR20_CALL:          howto manager.      (line 2099)
+* BFD_RELOC_MSP430X_PCR20_EXT_DST:       howto manager.      (line 2091)
+* BFD_RELOC_MSP430X_PCR20_EXT_ODST:      howto manager.      (line 2092)
+* BFD_RELOC_MSP430X_PCR20_EXT_SRC:       howto manager.      (line 2090)
+* BFD_RELOC_MSP430_10_PCREL:             howto manager.      (line 2082)
+* BFD_RELOC_MSP430_16:                   howto manager.      (line 2084)
+* BFD_RELOC_MSP430_16_BYTE:              howto manager.      (line 2086)
+* BFD_RELOC_MSP430_16_PCREL:             howto manager.      (line 2083)
+* BFD_RELOC_MSP430_16_PCREL_BYTE:        howto manager.      (line 2085)
+* BFD_RELOC_MSP430_2X_PCREL:             howto manager.      (line 2087)
+* BFD_RELOC_MSP430_ABS8:                 howto manager.      (line 2089)
+* BFD_RELOC_MSP430_ABS_HI16:             howto manager.      (line 2101)
+* BFD_RELOC_MSP430_PREL31:               howto manager.      (line 2102)
+* BFD_RELOC_MSP430_RL_PCREL:             howto manager.      (line 2088)
+* BFD_RELOC_MSP430_SYM_DIFF:             howto manager.      (line 2103)
+* BFD_RELOC_MT_GNU_VTENTRY:              howto manager.      (line 2078)
+* BFD_RELOC_MT_GNU_VTINHERIT:            howto manager.      (line 2076)
+* BFD_RELOC_MT_HI16:                     howto manager.      (line 2072)
+* BFD_RELOC_MT_LO16:                     howto manager.      (line 2074)
+* BFD_RELOC_MT_PC16:                     howto manager.      (line 2070)
+* BFD_RELOC_MT_PCINSN8:                  howto manager.      (line 2080)
+* BFD_RELOC_NIOS2_ALIGN:                 howto manager.      (line 2119)
+* BFD_RELOC_NIOS2_CACHE_OPX:             howto manager.      (line 2109)
+* BFD_RELOC_NIOS2_CALL16:                howto manager.      (line 2121)
+* BFD_RELOC_NIOS2_CALL26:                howto manager.      (line 2107)
+* BFD_RELOC_NIOS2_CALLR:                 howto manager.      (line 2118)
+* BFD_RELOC_NIOS2_CJMP:                  howto manager.      (line 2117)
+* BFD_RELOC_NIOS2_COPY:                  howto manager.      (line 2134)
+* BFD_RELOC_NIOS2_GLOB_DAT:              howto manager.      (line 2135)
+* BFD_RELOC_NIOS2_GOT16:                 howto manager.      (line 2120)
+* BFD_RELOC_NIOS2_GOTOFF:                howto manager.      (line 2138)
+* BFD_RELOC_NIOS2_GOTOFF_HA:             howto manager.      (line 2123)
+* BFD_RELOC_NIOS2_GOTOFF_LO:             howto manager.      (line 2122)
+* BFD_RELOC_NIOS2_GPREL:                 howto manager.      (line 2115)
+* BFD_RELOC_NIOS2_HI16:                  howto manager.      (line 2112)
+* BFD_RELOC_NIOS2_HIADJ16:               howto manager.      (line 2114)
+* BFD_RELOC_NIOS2_IMM5:                  howto manager.      (line 2108)
+* BFD_RELOC_NIOS2_IMM6:                  howto manager.      (line 2110)
+* BFD_RELOC_NIOS2_IMM8:                  howto manager.      (line 2111)
+* BFD_RELOC_NIOS2_JUMP_SLOT:             howto manager.      (line 2136)
+* BFD_RELOC_NIOS2_LO16:                  howto manager.      (line 2113)
+* BFD_RELOC_NIOS2_PCREL_HA:              howto manager.      (line 2125)
+* BFD_RELOC_NIOS2_PCREL_LO:              howto manager.      (line 2124)
+* BFD_RELOC_NIOS2_RELATIVE:              howto manager.      (line 2137)
+* BFD_RELOC_NIOS2_S16:                   howto manager.      (line 2105)
+* BFD_RELOC_NIOS2_TLS_DTPMOD:            howto manager.      (line 2131)
+* BFD_RELOC_NIOS2_TLS_DTPREL:            howto manager.      (line 2132)
+* BFD_RELOC_NIOS2_TLS_GD16:              howto manager.      (line 2126)
+* BFD_RELOC_NIOS2_TLS_IE16:              howto manager.      (line 2129)
+* BFD_RELOC_NIOS2_TLS_LDM16:             howto manager.      (line 2127)
+* BFD_RELOC_NIOS2_TLS_LDO16:             howto manager.      (line 2128)
+* BFD_RELOC_NIOS2_TLS_LE16:              howto manager.      (line 2130)
+* BFD_RELOC_NIOS2_TLS_TPREL:             howto manager.      (line 2133)
+* BFD_RELOC_NIOS2_U16:                   howto manager.      (line 2106)
+* BFD_RELOC_NIOS2_UJMP:                  howto manager.      (line 2116)
+* BFD_RELOC_NONE:                        howto manager.      (line  122)
+* BFD_RELOC_NS32K_DISP_16:               howto manager.      (line  570)
+* BFD_RELOC_NS32K_DISP_16_PCREL:         howto manager.      (line  573)
+* BFD_RELOC_NS32K_DISP_32:               howto manager.      (line  571)
+* BFD_RELOC_NS32K_DISP_32_PCREL:         howto manager.      (line  574)
+* BFD_RELOC_NS32K_DISP_8:                howto manager.      (line  569)
+* BFD_RELOC_NS32K_DISP_8_PCREL:          howto manager.      (line  572)
+* BFD_RELOC_NS32K_IMM_16:                howto manager.      (line  564)
+* BFD_RELOC_NS32K_IMM_16_PCREL:          howto manager.      (line  567)
+* BFD_RELOC_NS32K_IMM_32:                howto manager.      (line  565)
+* BFD_RELOC_NS32K_IMM_32_PCREL:          howto manager.      (line  568)
+* BFD_RELOC_NS32K_IMM_8:                 howto manager.      (line  563)
+* BFD_RELOC_NS32K_IMM_8_PCREL:           howto manager.      (line  566)
+* BFD_RELOC_OPENRISC_ABS_26:             howto manager.      (line 2044)
+* BFD_RELOC_OPENRISC_REL_26:             howto manager.      (line 2045)
+* BFD_RELOC_PDP11_DISP_6_PCREL:          howto manager.      (line  577)
+* BFD_RELOC_PDP11_DISP_8_PCREL:          howto manager.      (line  576)
+* BFD_RELOC_PJ_CODE_DIR16:               howto manager.      (line  581)
+* BFD_RELOC_PJ_CODE_DIR32:               howto manager.      (line  582)
+* BFD_RELOC_PJ_CODE_HI16:                howto manager.      (line  579)
+* BFD_RELOC_PJ_CODE_LO16:                howto manager.      (line  580)
+* BFD_RELOC_PJ_CODE_REL16:               howto manager.      (line  583)
+* BFD_RELOC_PJ_CODE_REL32:               howto manager.      (line  584)
+* BFD_RELOC_PPC64_ADDR16_DS:             howto manager.      (line  645)
+* BFD_RELOC_PPC64_ADDR16_HIGH:           howto manager.      (line  656)
+* BFD_RELOC_PPC64_ADDR16_HIGHA:          howto manager.      (line  657)
+* BFD_RELOC_PPC64_ADDR16_LO_DS:          howto manager.      (line  646)
+* BFD_RELOC_PPC64_DTPREL16_DS:           howto manager.      (line  695)
+* BFD_RELOC_PPC64_DTPREL16_HIGH:         howto manager.      (line  703)
+* BFD_RELOC_PPC64_DTPREL16_HIGHA:        howto manager.      (line  704)
+* BFD_RELOC_PPC64_DTPREL16_HIGHER:       howto manager.      (line  697)
+* BFD_RELOC_PPC64_DTPREL16_HIGHERA:      howto manager.      (line  698)
+* BFD_RELOC_PPC64_DTPREL16_HIGHEST:      howto manager.      (line  699)
+* BFD_RELOC_PPC64_DTPREL16_HIGHESTA:     howto manager.      (line  700)
+* BFD_RELOC_PPC64_DTPREL16_LO_DS:        howto manager.      (line  696)
+* BFD_RELOC_PPC64_GOT16_DS:              howto manager.      (line  647)
+* BFD_RELOC_PPC64_GOT16_LO_DS:           howto manager.      (line  648)
+* BFD_RELOC_PPC64_HIGHER:                howto manager.      (line  633)
+* BFD_RELOC_PPC64_HIGHER_S:              howto manager.      (line  634)
+* BFD_RELOC_PPC64_HIGHEST:               howto manager.      (line  635)
+* BFD_RELOC_PPC64_HIGHEST_S:             howto manager.      (line  636)
+* BFD_RELOC_PPC64_PLT16_LO_DS:           howto manager.      (line  649)
+* BFD_RELOC_PPC64_PLTGOT16:              howto manager.      (line  641)
+* BFD_RELOC_PPC64_PLTGOT16_DS:           howto manager.      (line  654)
+* BFD_RELOC_PPC64_PLTGOT16_HA:           howto manager.      (line  644)
+* BFD_RELOC_PPC64_PLTGOT16_HI:           howto manager.      (line  643)
+* BFD_RELOC_PPC64_PLTGOT16_LO:           howto manager.      (line  642)
+* BFD_RELOC_PPC64_PLTGOT16_LO_DS:        howto manager.      (line  655)
+* BFD_RELOC_PPC64_SECTOFF_DS:            howto manager.      (line  650)
+* BFD_RELOC_PPC64_SECTOFF_LO_DS:         howto manager.      (line  651)
+* BFD_RELOC_PPC64_TOC:                   howto manager.      (line  640)
+* BFD_RELOC_PPC64_TOC16_DS:              howto manager.      (line  652)
+* BFD_RELOC_PPC64_TOC16_HA:              howto manager.      (line  639)
+* BFD_RELOC_PPC64_TOC16_HI:              howto manager.      (line  638)
+* BFD_RELOC_PPC64_TOC16_LO:              howto manager.      (line  637)
+* BFD_RELOC_PPC64_TOC16_LO_DS:           howto manager.      (line  653)
+* BFD_RELOC_PPC64_TPREL16_DS:            howto manager.      (line  689)
+* BFD_RELOC_PPC64_TPREL16_HIGH:          howto manager.      (line  701)
+* BFD_RELOC_PPC64_TPREL16_HIGHA:         howto manager.      (line  702)
+* BFD_RELOC_PPC64_TPREL16_HIGHER:        howto manager.      (line  691)
+* BFD_RELOC_PPC64_TPREL16_HIGHERA:       howto manager.      (line  692)
+* BFD_RELOC_PPC64_TPREL16_HIGHEST:       howto manager.      (line  693)
+* BFD_RELOC_PPC64_TPREL16_HIGHESTA:      howto manager.      (line  694)
+* BFD_RELOC_PPC64_TPREL16_LO_DS:         howto manager.      (line  690)
+* BFD_RELOC_PPC_B16:                     howto manager.      (line  589)
+* BFD_RELOC_PPC_B16_BRNTAKEN:            howto manager.      (line  591)
+* BFD_RELOC_PPC_B16_BRTAKEN:             howto manager.      (line  590)
+* BFD_RELOC_PPC_B26:                     howto manager.      (line  586)
+* BFD_RELOC_PPC_BA16:                    howto manager.      (line  592)
+* BFD_RELOC_PPC_BA16_BRNTAKEN:           howto manager.      (line  594)
+* BFD_RELOC_PPC_BA16_BRTAKEN:            howto manager.      (line  593)
+* BFD_RELOC_PPC_BA26:                    howto manager.      (line  587)
+* BFD_RELOC_PPC_COPY:                    howto manager.      (line  595)
+* BFD_RELOC_PPC_DTPMOD:                  howto manager.      (line  662)
+* BFD_RELOC_PPC_DTPREL:                  howto manager.      (line  672)
+* BFD_RELOC_PPC_DTPREL16:                howto manager.      (line  668)
+* BFD_RELOC_PPC_DTPREL16_HA:             howto manager.      (line  671)
+* BFD_RELOC_PPC_DTPREL16_HI:             howto manager.      (line  670)
+* BFD_RELOC_PPC_DTPREL16_LO:             howto manager.      (line  669)
+* BFD_RELOC_PPC_EMB_BIT_FLD:             howto manager.      (line  614)
+* BFD_RELOC_PPC_EMB_MRKREF:              howto manager.      (line  609)
+* BFD_RELOC_PPC_EMB_NADDR16:             howto manager.      (line  601)
+* BFD_RELOC_PPC_EMB_NADDR16_HA:          howto manager.      (line  604)
+* BFD_RELOC_PPC_EMB_NADDR16_HI:          howto manager.      (line  603)
+* BFD_RELOC_PPC_EMB_NADDR16_LO:          howto manager.      (line  602)
+* BFD_RELOC_PPC_EMB_NADDR32:             howto manager.      (line  600)
+* BFD_RELOC_PPC_EMB_RELSDA:              howto manager.      (line  615)
+* BFD_RELOC_PPC_EMB_RELSEC16:            howto manager.      (line  610)
+* BFD_RELOC_PPC_EMB_RELST_HA:            howto manager.      (line  613)
+* BFD_RELOC_PPC_EMB_RELST_HI:            howto manager.      (line  612)
+* BFD_RELOC_PPC_EMB_RELST_LO:            howto manager.      (line  611)
+* BFD_RELOC_PPC_EMB_SDA21:               howto manager.      (line  608)
+* BFD_RELOC_PPC_EMB_SDA2I16:             howto manager.      (line  606)
+* BFD_RELOC_PPC_EMB_SDA2REL:             howto manager.      (line  607)
+* BFD_RELOC_PPC_EMB_SDAI16:              howto manager.      (line  605)
+* BFD_RELOC_PPC_GLOB_DAT:                howto manager.      (line  596)
+* BFD_RELOC_PPC_GOT_DTPREL16:            howto manager.      (line  685)
+* BFD_RELOC_PPC_GOT_DTPREL16_HA:         howto manager.      (line  688)
+* BFD_RELOC_PPC_GOT_DTPREL16_HI:         howto manager.      (line  687)
+* BFD_RELOC_PPC_GOT_DTPREL16_LO:         howto manager.      (line  686)
+* BFD_RELOC_PPC_GOT_TLSGD16:             howto manager.      (line  673)
+* BFD_RELOC_PPC_GOT_TLSGD16_HA:          howto manager.      (line  676)
+* BFD_RELOC_PPC_GOT_TLSGD16_HI:          howto manager.      (line  675)
+* BFD_RELOC_PPC_GOT_TLSGD16_LO:          howto manager.      (line  674)
+* BFD_RELOC_PPC_GOT_TLSLD16:             howto manager.      (line  677)
+* BFD_RELOC_PPC_GOT_TLSLD16_HA:          howto manager.      (line  680)
+* BFD_RELOC_PPC_GOT_TLSLD16_HI:          howto manager.      (line  679)
+* BFD_RELOC_PPC_GOT_TLSLD16_LO:          howto manager.      (line  678)
+* BFD_RELOC_PPC_GOT_TPREL16:             howto manager.      (line  681)
+* BFD_RELOC_PPC_GOT_TPREL16_HA:          howto manager.      (line  684)
+* BFD_RELOC_PPC_GOT_TPREL16_HI:          howto manager.      (line  683)
+* BFD_RELOC_PPC_GOT_TPREL16_LO:          howto manager.      (line  682)
+* BFD_RELOC_PPC_JMP_SLOT:                howto manager.      (line  597)
+* BFD_RELOC_PPC_LOCAL24PC:               howto manager.      (line  599)
+* BFD_RELOC_PPC_RELATIVE:                howto manager.      (line  598)
+* BFD_RELOC_PPC_TLS:                     howto manager.      (line  659)
+* BFD_RELOC_PPC_TLSGD:                   howto manager.      (line  660)
+* BFD_RELOC_PPC_TLSLD:                   howto manager.      (line  661)
+* BFD_RELOC_PPC_TOC16:                   howto manager.      (line  588)
+* BFD_RELOC_PPC_TPREL:                   howto manager.      (line  667)
+* BFD_RELOC_PPC_TPREL16:                 howto manager.      (line  663)
+* BFD_RELOC_PPC_TPREL16_HA:              howto manager.      (line  666)
+* BFD_RELOC_PPC_TPREL16_HI:              howto manager.      (line  665)
+* BFD_RELOC_PPC_TPREL16_LO:              howto manager.      (line  664)
+* BFD_RELOC_PPC_VLE_HA16A:               howto manager.      (line  623)
+* BFD_RELOC_PPC_VLE_HA16D:               howto manager.      (line  624)
+* BFD_RELOC_PPC_VLE_HI16A:               howto manager.      (line  621)
+* BFD_RELOC_PPC_VLE_HI16D:               howto manager.      (line  622)
+* BFD_RELOC_PPC_VLE_LO16A:               howto manager.      (line  619)
+* BFD_RELOC_PPC_VLE_LO16D:               howto manager.      (line  620)
+* BFD_RELOC_PPC_VLE_REL15:               howto manager.      (line  617)
+* BFD_RELOC_PPC_VLE_REL24:               howto manager.      (line  618)
+* BFD_RELOC_PPC_VLE_REL8:                howto manager.      (line  616)
+* BFD_RELOC_PPC_VLE_SDA21:               howto manager.      (line  625)
+* BFD_RELOC_PPC_VLE_SDA21_LO:            howto manager.      (line  626)
+* BFD_RELOC_PPC_VLE_SDAREL_HA16A:        howto manager.      (line  631)
+* BFD_RELOC_PPC_VLE_SDAREL_HA16D:        howto manager.      (line  632)
+* BFD_RELOC_PPC_VLE_SDAREL_HI16A:        howto manager.      (line  629)
+* BFD_RELOC_PPC_VLE_SDAREL_HI16D:        howto manager.      (line  630)
+* BFD_RELOC_PPC_VLE_SDAREL_LO16A:        howto manager.      (line  627)
+* BFD_RELOC_PPC_VLE_SDAREL_LO16D:        howto manager.      (line  628)
+* BFD_RELOC_RELC:                        howto manager.      (line 2059)
+* BFD_RELOC_RL78_16U:                    howto manager.      (line 1506)
+* BFD_RELOC_RL78_16_OP:                  howto manager.      (line 1502)
+* BFD_RELOC_RL78_24U:                    howto manager.      (line 1507)
+* BFD_RELOC_RL78_24_OP:                  howto manager.      (line 1503)
+* BFD_RELOC_RL78_32_OP:                  howto manager.      (line 1504)
+* BFD_RELOC_RL78_8U:                     howto manager.      (line 1505)
+* BFD_RELOC_RL78_ABS16:                  howto manager.      (line 1519)
+* BFD_RELOC_RL78_ABS16U:                 howto manager.      (line 1523)
+* BFD_RELOC_RL78_ABS16UL:                howto manager.      (line 1525)
+* BFD_RELOC_RL78_ABS16UW:                howto manager.      (line 1524)
+* BFD_RELOC_RL78_ABS16_REV:              howto manager.      (line 1520)
+* BFD_RELOC_RL78_ABS32:                  howto manager.      (line 1521)
+* BFD_RELOC_RL78_ABS32_REV:              howto manager.      (line 1522)
+* BFD_RELOC_RL78_ABS8:                   howto manager.      (line 1518)
+* BFD_RELOC_RL78_CODE:                   howto manager.      (line 1530)
+* BFD_RELOC_RL78_DIFF:                   howto manager.      (line 1509)
+* BFD_RELOC_RL78_DIR3U_PCREL:            howto manager.      (line 1508)
+* BFD_RELOC_RL78_GPRELB:                 howto manager.      (line 1510)
+* BFD_RELOC_RL78_GPRELL:                 howto manager.      (line 1512)
+* BFD_RELOC_RL78_GPRELW:                 howto manager.      (line 1511)
+* BFD_RELOC_RL78_HI16:                   howto manager.      (line 1527)
+* BFD_RELOC_RL78_HI8:                    howto manager.      (line 1528)
+* BFD_RELOC_RL78_LO16:                   howto manager.      (line 1529)
+* BFD_RELOC_RL78_NEG16:                  howto manager.      (line 1499)
+* BFD_RELOC_RL78_NEG24:                  howto manager.      (line 1500)
+* BFD_RELOC_RL78_NEG32:                  howto manager.      (line 1501)
+* BFD_RELOC_RL78_NEG8:                   howto manager.      (line 1498)
+* BFD_RELOC_RL78_OP_AND:                 howto manager.      (line 1516)
+* BFD_RELOC_RL78_OP_NEG:                 howto manager.      (line 1515)
+* BFD_RELOC_RL78_OP_SHRA:                howto manager.      (line 1517)
+* BFD_RELOC_RL78_OP_SUBTRACT:            howto manager.      (line 1514)
+* BFD_RELOC_RL78_RELAX:                  howto manager.      (line 1526)
+* BFD_RELOC_RL78_SYM:                    howto manager.      (line 1513)
+* BFD_RELOC_RVA:                         howto manager.      (line   97)
+* BFD_RELOC_RX_16U:                      howto manager.      (line 1540)
+* BFD_RELOC_RX_16_OP:                    howto manager.      (line 1536)
+* BFD_RELOC_RX_24U:                      howto manager.      (line 1541)
+* BFD_RELOC_RX_24_OP:                    howto manager.      (line 1537)
+* BFD_RELOC_RX_32_OP:                    howto manager.      (line 1538)
+* BFD_RELOC_RX_8U:                       howto manager.      (line 1539)
+* BFD_RELOC_RX_ABS16:                    howto manager.      (line 1551)
+* BFD_RELOC_RX_ABS16U:                   howto manager.      (line 1555)
+* BFD_RELOC_RX_ABS16UL:                  howto manager.      (line 1557)
+* BFD_RELOC_RX_ABS16UW:                  howto manager.      (line 1556)
+* BFD_RELOC_RX_ABS16_REV:                howto manager.      (line 1552)
+* BFD_RELOC_RX_ABS32:                    howto manager.      (line 1553)
+* BFD_RELOC_RX_ABS32_REV:                howto manager.      (line 1554)
+* BFD_RELOC_RX_ABS8:                     howto manager.      (line 1550)
+* BFD_RELOC_RX_DIFF:                     howto manager.      (line 1543)
+* BFD_RELOC_RX_DIR3U_PCREL:              howto manager.      (line 1542)
+* BFD_RELOC_RX_GPRELB:                   howto manager.      (line 1544)
+* BFD_RELOC_RX_GPRELL:                   howto manager.      (line 1546)
+* BFD_RELOC_RX_GPRELW:                   howto manager.      (line 1545)
+* BFD_RELOC_RX_NEG16:                    howto manager.      (line 1533)
+* BFD_RELOC_RX_NEG24:                    howto manager.      (line 1534)
+* BFD_RELOC_RX_NEG32:                    howto manager.      (line 1535)
+* BFD_RELOC_RX_NEG8:                     howto manager.      (line 1532)
+* BFD_RELOC_RX_OP_NEG:                   howto manager.      (line 1549)
+* BFD_RELOC_RX_OP_SUBTRACT:              howto manager.      (line 1548)
+* BFD_RELOC_RX_RELAX:                    howto manager.      (line 1558)
+* BFD_RELOC_RX_SYM:                      howto manager.      (line 1547)
+* BFD_RELOC_SCORE16_BRANCH:              howto manager.      (line 1661)
+* BFD_RELOC_SCORE16_JMP:                 howto manager.      (line 1659)
+* BFD_RELOC_SCORE_BCMP:                  howto manager.      (line 1663)
+* BFD_RELOC_SCORE_BRANCH:                howto manager.      (line 1653)
+* BFD_RELOC_SCORE_CALL15:                howto manager.      (line 1667)
+* BFD_RELOC_SCORE_DUMMY2:                howto manager.      (line 1650)
+* BFD_RELOC_SCORE_DUMMY_HI16:            howto manager.      (line 1668)
+* BFD_RELOC_SCORE_GOT15:                 howto manager.      (line 1665)
+* BFD_RELOC_SCORE_GOT_LO16:              howto manager.      (line 1666)
+* BFD_RELOC_SCORE_GPREL15:               howto manager.      (line 1648)
+* BFD_RELOC_SCORE_IMM30:                 howto manager.      (line 1655)
+* BFD_RELOC_SCORE_IMM32:                 howto manager.      (line 1657)
+* BFD_RELOC_SCORE_JMP:                   howto manager.      (line 1651)
+* BFD_RELOC_SH_ALIGN:                    howto manager.      (line  875)
+* BFD_RELOC_SH_CODE:                     howto manager.      (line  876)
+* BFD_RELOC_SH_COPY:                     howto manager.      (line  881)
+* BFD_RELOC_SH_COPY64:                   howto manager.      (line  906)
+* BFD_RELOC_SH_COUNT:                    howto manager.      (line  874)
+* BFD_RELOC_SH_DATA:                     howto manager.      (line  877)
+* BFD_RELOC_SH_DISP12:                   howto manager.      (line  857)
+* BFD_RELOC_SH_DISP12BY2:                howto manager.      (line  858)
+* BFD_RELOC_SH_DISP12BY4:                howto manager.      (line  859)
+* BFD_RELOC_SH_DISP12BY8:                howto manager.      (line  860)
+* BFD_RELOC_SH_DISP20:                   howto manager.      (line  861)
+* BFD_RELOC_SH_DISP20BY8:                howto manager.      (line  862)
+* BFD_RELOC_SH_FUNCDESC:                 howto manager.      (line  949)
+* BFD_RELOC_SH_GLOB_DAT:                 howto manager.      (line  882)
+* BFD_RELOC_SH_GLOB_DAT64:               howto manager.      (line  907)
+* BFD_RELOC_SH_GOT10BY4:                 howto manager.      (line  910)
+* BFD_RELOC_SH_GOT10BY8:                 howto manager.      (line  911)
+* BFD_RELOC_SH_GOT20:                    howto manager.      (line  943)
+* BFD_RELOC_SH_GOTFUNCDESC:              howto manager.      (line  945)
+* BFD_RELOC_SH_GOTFUNCDESC20:            howto manager.      (line  946)
+* BFD_RELOC_SH_GOTOFF20:                 howto manager.      (line  944)
+* BFD_RELOC_SH_GOTOFFFUNCDESC:           howto manager.      (line  947)
+* BFD_RELOC_SH_GOTOFFFUNCDESC20:         howto manager.      (line  948)
+* BFD_RELOC_SH_GOTOFF_HI16:              howto manager.      (line  901)
+* BFD_RELOC_SH_GOTOFF_LOW16:             howto manager.      (line  898)
+* BFD_RELOC_SH_GOTOFF_MEDHI16:           howto manager.      (line  900)
+* BFD_RELOC_SH_GOTOFF_MEDLOW16:          howto manager.      (line  899)
+* BFD_RELOC_SH_GOTPC:                    howto manager.      (line  885)
+* BFD_RELOC_SH_GOTPC_HI16:               howto manager.      (line  905)
+* BFD_RELOC_SH_GOTPC_LOW16:              howto manager.      (line  902)
+* BFD_RELOC_SH_GOTPC_MEDHI16:            howto manager.      (line  904)
+* BFD_RELOC_SH_GOTPC_MEDLOW16:           howto manager.      (line  903)
+* BFD_RELOC_SH_GOTPLT10BY4:              howto manager.      (line  912)
+* BFD_RELOC_SH_GOTPLT10BY8:              howto manager.      (line  913)
+* BFD_RELOC_SH_GOTPLT32:                 howto manager.      (line  914)
+* BFD_RELOC_SH_GOTPLT_HI16:              howto manager.      (line  893)
+* BFD_RELOC_SH_GOTPLT_LOW16:             howto manager.      (line  890)
+* BFD_RELOC_SH_GOTPLT_MEDHI16:           howto manager.      (line  892)
+* BFD_RELOC_SH_GOTPLT_MEDLOW16:          howto manager.      (line  891)
+* BFD_RELOC_SH_GOT_HI16:                 howto manager.      (line  889)
+* BFD_RELOC_SH_GOT_LOW16:                howto manager.      (line  886)
+* BFD_RELOC_SH_GOT_MEDHI16:              howto manager.      (line  888)
+* BFD_RELOC_SH_GOT_MEDLOW16:             howto manager.      (line  887)
+* BFD_RELOC_SH_IMM3:                     howto manager.      (line  855)
+* BFD_RELOC_SH_IMM3U:                    howto manager.      (line  856)
+* BFD_RELOC_SH_IMM4:                     howto manager.      (line  863)
+* BFD_RELOC_SH_IMM4BY2:                  howto manager.      (line  864)
+* BFD_RELOC_SH_IMM4BY4:                  howto manager.      (line  865)
+* BFD_RELOC_SH_IMM8:                     howto manager.      (line  866)
+* BFD_RELOC_SH_IMM8BY2:                  howto manager.      (line  867)
+* BFD_RELOC_SH_IMM8BY4:                  howto manager.      (line  868)
+* BFD_RELOC_SH_IMMS10:                   howto manager.      (line  920)
+* BFD_RELOC_SH_IMMS10BY2:                howto manager.      (line  921)
+* BFD_RELOC_SH_IMMS10BY4:                howto manager.      (line  922)
+* BFD_RELOC_SH_IMMS10BY8:                howto manager.      (line  923)
+* BFD_RELOC_SH_IMMS16:                   howto manager.      (line  924)
+* BFD_RELOC_SH_IMMS6:                    howto manager.      (line  917)
+* BFD_RELOC_SH_IMMS6BY32:                howto manager.      (line  918)
+* BFD_RELOC_SH_IMMU16:                   howto manager.      (line  925)
+* BFD_RELOC_SH_IMMU5:                    howto manager.      (line  916)
+* BFD_RELOC_SH_IMMU6:                    howto manager.      (line  919)
+* BFD_RELOC_SH_IMM_HI16:                 howto manager.      (line  932)
+* BFD_RELOC_SH_IMM_HI16_PCREL:           howto manager.      (line  933)
+* BFD_RELOC_SH_IMM_LOW16:                howto manager.      (line  926)
+* BFD_RELOC_SH_IMM_LOW16_PCREL:          howto manager.      (line  927)
+* BFD_RELOC_SH_IMM_MEDHI16:              howto manager.      (line  930)
+* BFD_RELOC_SH_IMM_MEDHI16_PCREL:        howto manager.      (line  931)
+* BFD_RELOC_SH_IMM_MEDLOW16:             howto manager.      (line  928)
+* BFD_RELOC_SH_IMM_MEDLOW16_PCREL:       howto manager.      (line  929)
+* BFD_RELOC_SH_JMP_SLOT:                 howto manager.      (line  883)
+* BFD_RELOC_SH_JMP_SLOT64:               howto manager.      (line  908)
+* BFD_RELOC_SH_LABEL:                    howto manager.      (line  878)
+* BFD_RELOC_SH_LOOP_END:                 howto manager.      (line  880)
+* BFD_RELOC_SH_LOOP_START:               howto manager.      (line  879)
+* BFD_RELOC_SH_PCDISP12BY2:              howto manager.      (line  854)
+* BFD_RELOC_SH_PCDISP8BY2:               howto manager.      (line  853)
+* BFD_RELOC_SH_PCRELIMM8BY2:             howto manager.      (line  869)
+* BFD_RELOC_SH_PCRELIMM8BY4:             howto manager.      (line  870)
+* BFD_RELOC_SH_PLT_HI16:                 howto manager.      (line  897)
+* BFD_RELOC_SH_PLT_LOW16:                howto manager.      (line  894)
+* BFD_RELOC_SH_PLT_MEDHI16:              howto manager.      (line  896)
+* BFD_RELOC_SH_PLT_MEDLOW16:             howto manager.      (line  895)
+* BFD_RELOC_SH_PT_16:                    howto manager.      (line  934)
+* BFD_RELOC_SH_RELATIVE:                 howto manager.      (line  884)
+* BFD_RELOC_SH_RELATIVE64:               howto manager.      (line  909)
+* BFD_RELOC_SH_SHMEDIA_CODE:             howto manager.      (line  915)
+* BFD_RELOC_SH_SWITCH16:                 howto manager.      (line  871)
+* BFD_RELOC_SH_SWITCH32:                 howto manager.      (line  872)
+* BFD_RELOC_SH_TLS_DTPMOD32:             howto manager.      (line  940)
+* BFD_RELOC_SH_TLS_DTPOFF32:             howto manager.      (line  941)
+* BFD_RELOC_SH_TLS_GD_32:                howto manager.      (line  935)
+* BFD_RELOC_SH_TLS_IE_32:                howto manager.      (line  938)
+* BFD_RELOC_SH_TLS_LDO_32:               howto manager.      (line  937)
+* BFD_RELOC_SH_TLS_LD_32:                howto manager.      (line  936)
+* BFD_RELOC_SH_TLS_LE_32:                howto manager.      (line  939)
+* BFD_RELOC_SH_TLS_TPOFF32:              howto manager.      (line  942)
+* BFD_RELOC_SH_USES:                     howto manager.      (line  873)
+* BFD_RELOC_SIZE32:                      howto manager.      (line   69)
+* BFD_RELOC_SIZE64:                      howto manager.      (line   70)
+* BFD_RELOC_SPARC13:                     howto manager.      (line  125)
+* BFD_RELOC_SPARC22:                     howto manager.      (line  124)
+* BFD_RELOC_SPARC_10:                    howto manager.      (line  152)
+* BFD_RELOC_SPARC_11:                    howto manager.      (line  153)
+* BFD_RELOC_SPARC_5:                     howto manager.      (line  165)
+* BFD_RELOC_SPARC_6:                     howto manager.      (line  164)
+* BFD_RELOC_SPARC_64:                    howto manager.      (line  151)
+* BFD_RELOC_SPARC_7:                     howto manager.      (line  163)
+* BFD_RELOC_SPARC_BASE13:                howto manager.      (line  148)
+* BFD_RELOC_SPARC_BASE22:                howto manager.      (line  149)
+* BFD_RELOC_SPARC_COPY:                  howto manager.      (line  132)
+* BFD_RELOC_SPARC_DISP64:                howto manager.      (line  166)
+* BFD_RELOC_SPARC_GLOB_DAT:              howto manager.      (line  133)
+* BFD_RELOC_SPARC_GOT10:                 howto manager.      (line  126)
+* BFD_RELOC_SPARC_GOT13:                 howto manager.      (line  127)
+* BFD_RELOC_SPARC_GOT22:                 howto manager.      (line  128)
+* BFD_RELOC_SPARC_GOTDATA_HIX22:         howto manager.      (line  139)
+* BFD_RELOC_SPARC_GOTDATA_LOX10:         howto manager.      (line  140)
+* BFD_RELOC_SPARC_GOTDATA_OP:            howto manager.      (line  143)
+* BFD_RELOC_SPARC_GOTDATA_OP_HIX22:      howto manager.      (line  141)
+* BFD_RELOC_SPARC_GOTDATA_OP_LOX10:      howto manager.      (line  142)
+* BFD_RELOC_SPARC_H34:                   howto manager.      (line  175)
+* BFD_RELOC_SPARC_H44:                   howto manager.      (line  171)
+* BFD_RELOC_SPARC_HH22:                  howto manager.      (line  155)
+* BFD_RELOC_SPARC_HIX22:                 howto manager.      (line  169)
+* BFD_RELOC_SPARC_HM10:                  howto manager.      (line  156)
+* BFD_RELOC_SPARC_IRELATIVE:             howto manager.      (line  145)
+* BFD_RELOC_SPARC_JMP_IREL:              howto manager.      (line  144)
+* BFD_RELOC_SPARC_JMP_SLOT:              howto manager.      (line  134)
+* BFD_RELOC_SPARC_L44:                   howto manager.      (line  173)
+* BFD_RELOC_SPARC_LM22:                  howto manager.      (line  157)
+* BFD_RELOC_SPARC_LOX10:                 howto manager.      (line  170)
+* BFD_RELOC_SPARC_M44:                   howto manager.      (line  172)
+* BFD_RELOC_SPARC_OLO10:                 howto manager.      (line  154)
+* BFD_RELOC_SPARC_PC10:                  howto manager.      (line  129)
+* BFD_RELOC_SPARC_PC22:                  howto manager.      (line  130)
+* BFD_RELOC_SPARC_PC_HH22:               howto manager.      (line  158)
+* BFD_RELOC_SPARC_PC_HM10:               howto manager.      (line  159)
+* BFD_RELOC_SPARC_PC_LM22:               howto manager.      (line  160)
+* BFD_RELOC_SPARC_PLT32:                 howto manager.      (line  167)
+* BFD_RELOC_SPARC_PLT64:                 howto manager.      (line  168)
+* BFD_RELOC_SPARC_REGISTER:              howto manager.      (line  174)
+* BFD_RELOC_SPARC_RELATIVE:              howto manager.      (line  135)
+* BFD_RELOC_SPARC_REV32:                 howto manager.      (line  180)
+* BFD_RELOC_SPARC_SIZE32:                howto manager.      (line  176)
+* BFD_RELOC_SPARC_SIZE64:                howto manager.      (line  177)
+* BFD_RELOC_SPARC_TLS_DTPMOD32:          howto manager.      (line  200)
+* BFD_RELOC_SPARC_TLS_DTPMOD64:          howto manager.      (line  201)
+* BFD_RELOC_SPARC_TLS_DTPOFF32:          howto manager.      (line  202)
+* BFD_RELOC_SPARC_TLS_DTPOFF64:          howto manager.      (line  203)
+* BFD_RELOC_SPARC_TLS_GD_ADD:            howto manager.      (line  184)
+* BFD_RELOC_SPARC_TLS_GD_CALL:           howto manager.      (line  185)
+* BFD_RELOC_SPARC_TLS_GD_HI22:           howto manager.      (line  182)
+* BFD_RELOC_SPARC_TLS_GD_LO10:           howto manager.      (line  183)
+* BFD_RELOC_SPARC_TLS_IE_ADD:            howto manager.      (line  197)
+* BFD_RELOC_SPARC_TLS_IE_HI22:           howto manager.      (line  193)
+* BFD_RELOC_SPARC_TLS_IE_LD:             howto manager.      (line  195)
+* BFD_RELOC_SPARC_TLS_IE_LDX:            howto manager.      (line  196)
+* BFD_RELOC_SPARC_TLS_IE_LO10:           howto manager.      (line  194)
+* BFD_RELOC_SPARC_TLS_LDM_ADD:           howto manager.      (line  188)
+* BFD_RELOC_SPARC_TLS_LDM_CALL:          howto manager.      (line  189)
+* BFD_RELOC_SPARC_TLS_LDM_HI22:          howto manager.      (line  186)
+* BFD_RELOC_SPARC_TLS_LDM_LO10:          howto manager.      (line  187)
+* BFD_RELOC_SPARC_TLS_LDO_ADD:           howto manager.      (line  192)
+* BFD_RELOC_SPARC_TLS_LDO_HIX22:         howto manager.      (line  190)
+* BFD_RELOC_SPARC_TLS_LDO_LOX10:         howto manager.      (line  191)
+* BFD_RELOC_SPARC_TLS_LE_HIX22:          howto manager.      (line  198)
+* BFD_RELOC_SPARC_TLS_LE_LOX10:          howto manager.      (line  199)
+* BFD_RELOC_SPARC_TLS_TPOFF32:           howto manager.      (line  204)
+* BFD_RELOC_SPARC_TLS_TPOFF64:           howto manager.      (line  205)
+* BFD_RELOC_SPARC_UA16:                  howto manager.      (line  136)
+* BFD_RELOC_SPARC_UA32:                  howto manager.      (line  137)
+* BFD_RELOC_SPARC_UA64:                  howto manager.      (line  138)
+* BFD_RELOC_SPARC_WDISP10:               howto manager.      (line  178)
+* BFD_RELOC_SPARC_WDISP16:               howto manager.      (line  161)
+* BFD_RELOC_SPARC_WDISP19:               howto manager.      (line  162)
+* BFD_RELOC_SPARC_WDISP22:               howto manager.      (line  123)
+* BFD_RELOC_SPARC_WPLT30:                howto manager.      (line  131)
+* BFD_RELOC_SPU_ADD_PIC:                 howto manager.      (line  221)
+* BFD_RELOC_SPU_HI16:                    howto manager.      (line  218)
+* BFD_RELOC_SPU_IMM10:                   howto manager.      (line  209)
+* BFD_RELOC_SPU_IMM10W:                  howto manager.      (line  210)
+* BFD_RELOC_SPU_IMM16:                   howto manager.      (line  211)
+* BFD_RELOC_SPU_IMM16W:                  howto manager.      (line  212)
+* BFD_RELOC_SPU_IMM18:                   howto manager.      (line  213)
+* BFD_RELOC_SPU_IMM7:                    howto manager.      (line  207)
+* BFD_RELOC_SPU_IMM8:                    howto manager.      (line  208)
+* BFD_RELOC_SPU_LO16:                    howto manager.      (line  217)
+* BFD_RELOC_SPU_PCREL16:                 howto manager.      (line  216)
+* BFD_RELOC_SPU_PCREL9a:                 howto manager.      (line  214)
+* BFD_RELOC_SPU_PCREL9b:                 howto manager.      (line  215)
+* BFD_RELOC_SPU_PPU32:                   howto manager.      (line  219)
+* BFD_RELOC_SPU_PPU64:                   howto manager.      (line  220)
+* BFD_RELOC_THUMB_PCREL_BLX:             howto manager.      (line  720)
+* BFD_RELOC_THUMB_PCREL_BRANCH12:        howto manager.      (line  731)
+* BFD_RELOC_THUMB_PCREL_BRANCH20:        howto manager.      (line  732)
+* BFD_RELOC_THUMB_PCREL_BRANCH23:        howto manager.      (line  733)
+* BFD_RELOC_THUMB_PCREL_BRANCH25:        howto manager.      (line  734)
+* BFD_RELOC_THUMB_PCREL_BRANCH7:         howto manager.      (line  729)
+* BFD_RELOC_THUMB_PCREL_BRANCH9:         howto manager.      (line  730)
+* BFD_RELOC_TIC30_LDP:                   howto manager.      (line 1227)
+* BFD_RELOC_TIC54X_16_OF_23:             howto manager.      (line 1241)
+* BFD_RELOC_TIC54X_23:                   howto manager.      (line 1239)
+* BFD_RELOC_TIC54X_MS7_OF_23:            howto manager.      (line 1245)
+* BFD_RELOC_TIC54X_PARTLS7:              howto manager.      (line 1231)
+* BFD_RELOC_TIC54X_PARTMS9:              howto manager.      (line 1235)
+* BFD_RELOC_TILEGX_BROFF_X1:             howto manager.      (line 2642)
+* BFD_RELOC_TILEGX_COPY:                 howto manager.      (line 2638)
+* BFD_RELOC_TILEGX_DEST_IMM8_X1:         howto manager.      (line 2649)
+* BFD_RELOC_TILEGX_GLOB_DAT:             howto manager.      (line 2639)
+* BFD_RELOC_TILEGX_HW0:                  howto manager.      (line 2631)
+* BFD_RELOC_TILEGX_HW0_LAST:             howto manager.      (line 2635)
+* BFD_RELOC_TILEGX_HW1:                  howto manager.      (line 2632)
+* BFD_RELOC_TILEGX_HW1_LAST:             howto manager.      (line 2636)
+* BFD_RELOC_TILEGX_HW2:                  howto manager.      (line 2633)
+* BFD_RELOC_TILEGX_HW2_LAST:             howto manager.      (line 2637)
+* BFD_RELOC_TILEGX_HW3:                  howto manager.      (line 2634)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0:         howto manager.      (line 2658)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_GOT:     howto manager.      (line 2686)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST:    howto manager.      (line 2666)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_GOT: howto manager.     (line 2694)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PCREL: howto manager.   (line 2680)
 * BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_PLT_PCREL: howto manager.
-                                                             (line 3101)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_GD: howto manager.  (line 3095)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_IE: howto manager.  (line 3107)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_LE: howto manager.  (line 3091)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_PCREL:   howto manager.      (line 3059)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_PLT_PCREL: howto manager.    (line 3075)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_GD:  howto manager.      (line 3087)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_IE:  howto manager.      (line 3099)
-* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_LE:  howto manager.      (line 3089)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1:         howto manager.      (line 3047)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST:    howto manager.      (line 3055)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_GOT: howto manager.     (line 3083)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PCREL: howto manager.   (line 3069)
+                                                             (line 2714)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_GD: howto manager.  (line 2708)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_IE: howto manager.  (line 2720)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_LAST_TLS_LE: howto manager.  (line 2704)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_PCREL:   howto manager.      (line 2672)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_PLT_PCREL: howto manager.    (line 2688)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_GD:  howto manager.      (line 2700)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_IE:  howto manager.      (line 2712)
+* BFD_RELOC_TILEGX_IMM16_X0_HW0_TLS_LE:  howto manager.      (line 2702)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1:         howto manager.      (line 2660)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST:    howto manager.      (line 2668)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_GOT: howto manager.     (line 2696)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PCREL: howto manager.   (line 2682)
 * BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_PLT_PCREL: howto manager.
-                                                             (line 3103)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_GD: howto manager.  (line 3097)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_IE: howto manager.  (line 3109)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_LE: howto manager.  (line 3093)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_PCREL:   howto manager.      (line 3061)
-* BFD_RELOC_TILEGX_IMM16_X0_HW1_PLT_PCREL: howto manager.    (line 3077)
-* BFD_RELOC_TILEGX_IMM16_X0_HW2:         howto manager.      (line 3049)
-* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST:    howto manager.      (line 3057)
-* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PCREL: howto manager.   (line 3071)
+                                                             (line 2716)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_GD: howto manager.  (line 2710)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_IE: howto manager.  (line 2722)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_LAST_TLS_LE: howto manager.  (line 2706)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_PCREL:   howto manager.      (line 2674)
+* BFD_RELOC_TILEGX_IMM16_X0_HW1_PLT_PCREL: howto manager.    (line 2690)
+* BFD_RELOC_TILEGX_IMM16_X0_HW2:         howto manager.      (line 2662)
+* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST:    howto manager.      (line 2670)
+* BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PCREL: howto manager.   (line 2684)
 * BFD_RELOC_TILEGX_IMM16_X0_HW2_LAST_PLT_PCREL: howto manager.
-                                                             (line 3105)
-* BFD_RELOC_TILEGX_IMM16_X0_HW2_PCREL:   howto manager.      (line 3063)
-* BFD_RELOC_TILEGX_IMM16_X0_HW2_PLT_PCREL: howto manager.    (line 3079)
-* BFD_RELOC_TILEGX_IMM16_X0_HW3:         howto manager.      (line 3051)
-* BFD_RELOC_TILEGX_IMM16_X0_HW3_PCREL:   howto manager.      (line 3065)
-* BFD_RELOC_TILEGX_IMM16_X0_HW3_PLT_PCREL: howto manager.    (line 3085)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0:         howto manager.      (line 3046)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_GOT:     howto manager.      (line 3074)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST:    howto manager.      (line 3054)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_GOT: howto manager.     (line 3082)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PCREL: howto manager.   (line 3068)
+                                                             (line 2718)
+* BFD_RELOC_TILEGX_IMM16_X0_HW2_PCREL:   howto manager.      (line 2676)
+* BFD_RELOC_TILEGX_IMM16_X0_HW2_PLT_PCREL: howto manager.    (line 2692)
+* BFD_RELOC_TILEGX_IMM16_X0_HW3:         howto manager.      (line 2664)
+* BFD_RELOC_TILEGX_IMM16_X0_HW3_PCREL:   howto manager.      (line 2678)
+* BFD_RELOC_TILEGX_IMM16_X0_HW3_PLT_PCREL: howto manager.    (line 2698)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0:         howto manager.      (line 2659)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_GOT:     howto manager.      (line 2687)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST:    howto manager.      (line 2667)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_GOT: howto manager.     (line 2695)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PCREL: howto manager.   (line 2681)
 * BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_PLT_PCREL: howto manager.
-                                                             (line 3102)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_GD: howto manager.  (line 3096)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_IE: howto manager.  (line 3108)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_LE: howto manager.  (line 3092)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_PCREL:   howto manager.      (line 3060)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_PLT_PCREL: howto manager.    (line 3076)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_GD:  howto manager.      (line 3088)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_IE:  howto manager.      (line 3100)
-* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_LE:  howto manager.      (line 3090)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1:         howto manager.      (line 3048)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST:    howto manager.      (line 3056)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_GOT: howto manager.     (line 3084)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PCREL: howto manager.   (line 3070)
+                                                             (line 2715)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_GD: howto manager.  (line 2709)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_IE: howto manager.  (line 2721)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_LAST_TLS_LE: howto manager.  (line 2705)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_PCREL:   howto manager.      (line 2673)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_PLT_PCREL: howto manager.    (line 2689)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_GD:  howto manager.      (line 2701)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_IE:  howto manager.      (line 2713)
+* BFD_RELOC_TILEGX_IMM16_X1_HW0_TLS_LE:  howto manager.      (line 2703)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1:         howto manager.      (line 2661)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST:    howto manager.      (line 2669)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_GOT: howto manager.     (line 2697)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PCREL: howto manager.   (line 2683)
 * BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_PLT_PCREL: howto manager.
-                                                             (line 3104)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_GD: howto manager.  (line 3098)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_IE: howto manager.  (line 3110)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_LE: howto manager.  (line 3094)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_PCREL:   howto manager.      (line 3062)
-* BFD_RELOC_TILEGX_IMM16_X1_HW1_PLT_PCREL: howto manager.    (line 3078)
-* BFD_RELOC_TILEGX_IMM16_X1_HW2:         howto manager.      (line 3050)
-* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST:    howto manager.      (line 3058)
-* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PCREL: howto manager.   (line 3072)
+                                                             (line 2717)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_GD: howto manager.  (line 2711)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_IE: howto manager.  (line 2723)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_LAST_TLS_LE: howto manager.  (line 2707)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_PCREL:   howto manager.      (line 2675)
+* BFD_RELOC_TILEGX_IMM16_X1_HW1_PLT_PCREL: howto manager.    (line 2691)
+* BFD_RELOC_TILEGX_IMM16_X1_HW2:         howto manager.      (line 2663)
+* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST:    howto manager.      (line 2671)
+* BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PCREL: howto manager.   (line 2685)
 * BFD_RELOC_TILEGX_IMM16_X1_HW2_LAST_PLT_PCREL: howto manager.
-                                                             (line 3106)
-* BFD_RELOC_TILEGX_IMM16_X1_HW2_PCREL:   howto manager.      (line 3064)
-* BFD_RELOC_TILEGX_IMM16_X1_HW2_PLT_PCREL: howto manager.    (line 3080)
-* BFD_RELOC_TILEGX_IMM16_X1_HW3:         howto manager.      (line 3052)
-* BFD_RELOC_TILEGX_IMM16_X1_HW3_PCREL:   howto manager.      (line 3066)
-* BFD_RELOC_TILEGX_IMM16_X1_HW3_PLT_PCREL: howto manager.    (line 3086)
-* BFD_RELOC_TILEGX_IMM8_X0:              howto manager.      (line 3032)
-* BFD_RELOC_TILEGX_IMM8_X0_TLS_ADD:      howto manager.      (line 3123)
-* BFD_RELOC_TILEGX_IMM8_X0_TLS_GD_ADD:   howto manager.      (line 3118)
-* BFD_RELOC_TILEGX_IMM8_X1:              howto manager.      (line 3034)
-* BFD_RELOC_TILEGX_IMM8_X1_TLS_ADD:      howto manager.      (line 3124)
-* BFD_RELOC_TILEGX_IMM8_X1_TLS_GD_ADD:   howto manager.      (line 3119)
-* BFD_RELOC_TILEGX_IMM8_Y0:              howto manager.      (line 3033)
-* BFD_RELOC_TILEGX_IMM8_Y0_TLS_ADD:      howto manager.      (line 3125)
-* BFD_RELOC_TILEGX_IMM8_Y0_TLS_GD_ADD:   howto manager.      (line 3120)
-* BFD_RELOC_TILEGX_IMM8_Y1:              howto manager.      (line 3035)
-* BFD_RELOC_TILEGX_IMM8_Y1_TLS_ADD:      howto manager.      (line 3126)
-* BFD_RELOC_TILEGX_IMM8_Y1_TLS_GD_ADD:   howto manager.      (line 3121)
-* BFD_RELOC_TILEGX_JMP_SLOT:             howto manager.      (line 3027)
-* BFD_RELOC_TILEGX_JUMPOFF_X1:           howto manager.      (line 3030)
-* BFD_RELOC_TILEGX_JUMPOFF_X1_PLT:       howto manager.      (line 3031)
-* BFD_RELOC_TILEGX_MF_IMM14_X1:          howto manager.      (line 3038)
-* BFD_RELOC_TILEGX_MMEND_X0:             howto manager.      (line 3040)
-* BFD_RELOC_TILEGX_MMSTART_X0:           howto manager.      (line 3039)
-* BFD_RELOC_TILEGX_MT_IMM14_X1:          howto manager.      (line 3037)
-* BFD_RELOC_TILEGX_RELATIVE:             howto manager.      (line 3028)
-* BFD_RELOC_TILEGX_SHAMT_X0:             howto manager.      (line 3041)
-* BFD_RELOC_TILEGX_SHAMT_X1:             howto manager.      (line 3042)
-* BFD_RELOC_TILEGX_SHAMT_Y0:             howto manager.      (line 3043)
-* BFD_RELOC_TILEGX_SHAMT_Y1:             howto manager.      (line 3044)
-* BFD_RELOC_TILEGX_TLS_DTPMOD32:         howto manager.      (line 3114)
-* BFD_RELOC_TILEGX_TLS_DTPMOD64:         howto manager.      (line 3111)
-* BFD_RELOC_TILEGX_TLS_DTPOFF32:         howto manager.      (line 3115)
-* BFD_RELOC_TILEGX_TLS_DTPOFF64:         howto manager.      (line 3112)
-* BFD_RELOC_TILEGX_TLS_GD_CALL:          howto manager.      (line 3117)
-* BFD_RELOC_TILEGX_TLS_IE_LOAD:          howto manager.      (line 3122)
-* BFD_RELOC_TILEGX_TLS_TPOFF32:          howto manager.      (line 3116)
-* BFD_RELOC_TILEGX_TLS_TPOFF64:          howto manager.      (line 3113)
-* BFD_RELOC_TILEPRO_BROFF_X1:            howto manager.      (line 2941)
-* BFD_RELOC_TILEPRO_COPY:                howto manager.      (line 2937)
-* BFD_RELOC_TILEPRO_DEST_IMM8_X1:        howto manager.      (line 2948)
-* BFD_RELOC_TILEPRO_GLOB_DAT:            howto manager.      (line 2938)
-* BFD_RELOC_TILEPRO_IMM16_X0:            howto manager.      (line 2951)
-* BFD_RELOC_TILEPRO_IMM16_X0_GOT:        howto manager.      (line 2967)
-* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HA:     howto manager.      (line 2973)
-* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HI:     howto manager.      (line 2971)
-* BFD_RELOC_TILEPRO_IMM16_X0_GOT_LO:     howto manager.      (line 2969)
-* BFD_RELOC_TILEPRO_IMM16_X0_HA:         howto manager.      (line 2957)
-* BFD_RELOC_TILEPRO_IMM16_X0_HA_PCREL:   howto manager.      (line 2965)
-* BFD_RELOC_TILEPRO_IMM16_X0_HI:         howto manager.      (line 2955)
-* BFD_RELOC_TILEPRO_IMM16_X0_HI_PCREL:   howto manager.      (line 2963)
-* BFD_RELOC_TILEPRO_IMM16_X0_LO:         howto manager.      (line 2953)
-* BFD_RELOC_TILEPRO_IMM16_X0_LO_PCREL:   howto manager.      (line 2961)
-* BFD_RELOC_TILEPRO_IMM16_X0_PCREL:      howto manager.      (line 2959)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD:     howto manager.      (line 2989)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HA:  howto manager.      (line 2995)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HI:  howto manager.      (line 2993)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_LO:  howto manager.      (line 2991)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE:     howto manager.      (line 2997)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HA:  howto manager.      (line 3003)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HI:  howto manager.      (line 3001)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_LO:  howto manager.      (line 2999)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE:     howto manager.      (line 3008)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HA:  howto manager.      (line 3014)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HI:  howto manager.      (line 3012)
-* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_LO:  howto manager.      (line 3010)
-* BFD_RELOC_TILEPRO_IMM16_X1:            howto manager.      (line 2952)
-* BFD_RELOC_TILEPRO_IMM16_X1_GOT:        howto manager.      (line 2968)
-* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HA:     howto manager.      (line 2974)
-* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HI:     howto manager.      (line 2972)
-* BFD_RELOC_TILEPRO_IMM16_X1_GOT_LO:     howto manager.      (line 2970)
-* BFD_RELOC_TILEPRO_IMM16_X1_HA:         howto manager.      (line 2958)
-* BFD_RELOC_TILEPRO_IMM16_X1_HA_PCREL:   howto manager.      (line 2966)
-* BFD_RELOC_TILEPRO_IMM16_X1_HI:         howto manager.      (line 2956)
-* BFD_RELOC_TILEPRO_IMM16_X1_HI_PCREL:   howto manager.      (line 2964)
-* BFD_RELOC_TILEPRO_IMM16_X1_LO:         howto manager.      (line 2954)
-* BFD_RELOC_TILEPRO_IMM16_X1_LO_PCREL:   howto manager.      (line 2962)
-* BFD_RELOC_TILEPRO_IMM16_X1_PCREL:      howto manager.      (line 2960)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD:     howto manager.      (line 2990)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HA:  howto manager.      (line 2996)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HI:  howto manager.      (line 2994)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_LO:  howto manager.      (line 2992)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE:     howto manager.      (line 2998)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HA:  howto manager.      (line 3004)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HI:  howto manager.      (line 3002)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_LO:  howto manager.      (line 3000)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE:     howto manager.      (line 3009)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HA:  howto manager.      (line 3015)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HI:  howto manager.      (line 3013)
-* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_LO:  howto manager.      (line 3011)
-* BFD_RELOC_TILEPRO_IMM8_X0:             howto manager.      (line 2944)
-* BFD_RELOC_TILEPRO_IMM8_X0_TLS_GD_ADD:  howto manager.      (line 2984)
-* BFD_RELOC_TILEPRO_IMM8_X1:             howto manager.      (line 2946)
-* BFD_RELOC_TILEPRO_IMM8_X1_TLS_GD_ADD:  howto manager.      (line 2985)
-* BFD_RELOC_TILEPRO_IMM8_Y0:             howto manager.      (line 2945)
-* BFD_RELOC_TILEPRO_IMM8_Y0_TLS_GD_ADD:  howto manager.      (line 2986)
-* BFD_RELOC_TILEPRO_IMM8_Y1:             howto manager.      (line 2947)
-* BFD_RELOC_TILEPRO_IMM8_Y1_TLS_GD_ADD:  howto manager.      (line 2987)
-* BFD_RELOC_TILEPRO_JMP_SLOT:            howto manager.      (line 2939)
-* BFD_RELOC_TILEPRO_JOFFLONG_X1:         howto manager.      (line 2942)
-* BFD_RELOC_TILEPRO_JOFFLONG_X1_PLT:     howto manager.      (line 2943)
-* BFD_RELOC_TILEPRO_MF_IMM15_X1:         howto manager.      (line 2950)
-* BFD_RELOC_TILEPRO_MMEND_X0:            howto manager.      (line 2976)
-* BFD_RELOC_TILEPRO_MMEND_X1:            howto manager.      (line 2978)
-* BFD_RELOC_TILEPRO_MMSTART_X0:          howto manager.      (line 2975)
-* BFD_RELOC_TILEPRO_MMSTART_X1:          howto manager.      (line 2977)
-* BFD_RELOC_TILEPRO_MT_IMM15_X1:         howto manager.      (line 2949)
-* BFD_RELOC_TILEPRO_RELATIVE:            howto manager.      (line 2940)
-* BFD_RELOC_TILEPRO_SHAMT_X0:            howto manager.      (line 2979)
-* BFD_RELOC_TILEPRO_SHAMT_X1:            howto manager.      (line 2980)
-* BFD_RELOC_TILEPRO_SHAMT_Y0:            howto manager.      (line 2981)
-* BFD_RELOC_TILEPRO_SHAMT_Y1:            howto manager.      (line 2982)
-* BFD_RELOC_TILEPRO_TLS_DTPMOD32:        howto manager.      (line 3005)
-* BFD_RELOC_TILEPRO_TLS_DTPOFF32:        howto manager.      (line 3006)
-* BFD_RELOC_TILEPRO_TLS_GD_CALL:         howto manager.      (line 2983)
-* BFD_RELOC_TILEPRO_TLS_IE_LOAD:         howto manager.      (line 2988)
-* BFD_RELOC_TILEPRO_TLS_TPOFF32:         howto manager.      (line 3007)
-* bfd_reloc_type_lookup:                 howto manager.      (line 3152)
-* BFD_RELOC_V850_16_GOT:                 howto manager.      (line 1385)
-* BFD_RELOC_V850_16_GOTOFF:              howto manager.      (line 1409)
-* BFD_RELOC_V850_16_PCREL:               howto manager.      (line 1355)
-* BFD_RELOC_V850_16_S1:                  howto manager.      (line 1373)
-* BFD_RELOC_V850_16_SPLIT_OFFSET:        howto manager.      (line 1370)
-* BFD_RELOC_V850_17_PCREL:               howto manager.      (line 1358)
-* BFD_RELOC_V850_22_PCREL:               howto manager.      (line 1290)
-* BFD_RELOC_V850_22_PLT_PCREL:           howto manager.      (line 1391)
-* BFD_RELOC_V850_23:                     howto manager.      (line 1361)
-* BFD_RELOC_V850_32_ABS:                 howto manager.      (line 1367)
-* BFD_RELOC_V850_32_GOT:                 howto manager.      (line 1388)
-* BFD_RELOC_V850_32_GOTOFF:              howto manager.      (line 1412)
-* BFD_RELOC_V850_32_GOTPCREL:            howto manager.      (line 1382)
-* BFD_RELOC_V850_32_PCREL:               howto manager.      (line 1364)
-* BFD_RELOC_V850_32_PLT_PCREL:           howto manager.      (line 1394)
-* BFD_RELOC_V850_9_PCREL:                howto manager.      (line 1287)
-* BFD_RELOC_V850_ALIGN:                  howto manager.      (line 1348)
-* BFD_RELOC_V850_CALLT_15_16_OFFSET:     howto manager.      (line 1379)
-* BFD_RELOC_V850_CALLT_16_16_OFFSET:     howto manager.      (line 1339)
-* BFD_RELOC_V850_CALLT_6_7_OFFSET:       howto manager.      (line 1336)
-* BFD_RELOC_V850_CODE:                   howto manager.      (line 1415)
-* BFD_RELOC_V850_COPY:                   howto manager.      (line 1397)
-* BFD_RELOC_V850_DATA:                   howto manager.      (line 1418)
-* BFD_RELOC_V850_GLOB_DAT:               howto manager.      (line 1400)
-* BFD_RELOC_V850_JMP_SLOT:               howto manager.      (line 1403)
-* BFD_RELOC_V850_LO16_S1:                howto manager.      (line 1376)
-* BFD_RELOC_V850_LO16_SPLIT_OFFSET:      howto manager.      (line 1351)
-* BFD_RELOC_V850_LONGCALL:               howto manager.      (line 1342)
-* BFD_RELOC_V850_LONGJUMP:               howto manager.      (line 1345)
-* BFD_RELOC_V850_RELATIVE:               howto manager.      (line 1406)
-* BFD_RELOC_V850_SDA_15_16_OFFSET:       howto manager.      (line 1296)
-* BFD_RELOC_V850_SDA_16_16_OFFSET:       howto manager.      (line 1293)
-* BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET: howto manager.      (line 1328)
-* BFD_RELOC_V850_TDA_16_16_OFFSET:       howto manager.      (line 1318)
-* BFD_RELOC_V850_TDA_4_4_OFFSET:         howto manager.      (line 1325)
-* BFD_RELOC_V850_TDA_4_5_OFFSET:         howto manager.      (line 1321)
-* BFD_RELOC_V850_TDA_6_8_OFFSET:         howto manager.      (line 1307)
-* BFD_RELOC_V850_TDA_7_7_OFFSET:         howto manager.      (line 1315)
-* BFD_RELOC_V850_TDA_7_8_OFFSET:         howto manager.      (line 1311)
-* BFD_RELOC_V850_ZDA_15_16_OFFSET:       howto manager.      (line 1303)
-* BFD_RELOC_V850_ZDA_16_16_OFFSET:       howto manager.      (line 1300)
-* BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET: howto manager.      (line 1332)
-* BFD_RELOC_VAX_GLOB_DAT:                howto manager.      (line 2404)
-* BFD_RELOC_VAX_JMP_SLOT:                howto manager.      (line 2405)
-* BFD_RELOC_VAX_RELATIVE:                howto manager.      (line 2406)
-* BFD_RELOC_VPE4KMATH_DATA:              howto manager.      (line 1980)
-* BFD_RELOC_VPE4KMATH_INSN:              howto manager.      (line 1981)
-* BFD_RELOC_VTABLE_ENTRY:                howto manager.      (line 1985)
-* BFD_RELOC_VTABLE_INHERIT:              howto manager.      (line 1984)
-* BFD_RELOC_X86_64_32S:                  howto manager.      (line  607)
-* BFD_RELOC_X86_64_COPY:                 howto manager.      (line  602)
-* BFD_RELOC_X86_64_DTPMOD64:             howto manager.      (line  608)
-* BFD_RELOC_X86_64_DTPOFF32:             howto manager.      (line  613)
-* BFD_RELOC_X86_64_DTPOFF64:             howto manager.      (line  609)
-* BFD_RELOC_X86_64_GLOB_DAT:             howto manager.      (line  603)
-* BFD_RELOC_X86_64_GOT32:                howto manager.      (line  600)
-* BFD_RELOC_X86_64_GOT64:                howto manager.      (line  618)
-* BFD_RELOC_X86_64_GOTOFF64:             howto manager.      (line  616)
-* BFD_RELOC_X86_64_GOTPC32:              howto manager.      (line  617)
-* BFD_RELOC_X86_64_GOTPC32_TLSDESC:      howto manager.      (line  623)
-* BFD_RELOC_X86_64_GOTPC64:              howto manager.      (line  620)
-* BFD_RELOC_X86_64_GOTPCREL:             howto manager.      (line  606)
-* BFD_RELOC_X86_64_GOTPCREL64:           howto manager.      (line  619)
-* BFD_RELOC_X86_64_GOTPLT64:             howto manager.      (line  621)
-* BFD_RELOC_X86_64_GOTTPOFF:             howto manager.      (line  614)
-* BFD_RELOC_X86_64_IRELATIVE:            howto manager.      (line  626)
-* BFD_RELOC_X86_64_JUMP_SLOT:            howto manager.      (line  604)
-* BFD_RELOC_X86_64_PLT32:                howto manager.      (line  601)
-* BFD_RELOC_X86_64_PLTOFF64:             howto manager.      (line  622)
-* BFD_RELOC_X86_64_RELATIVE:             howto manager.      (line  605)
-* BFD_RELOC_X86_64_TLSDESC:              howto manager.      (line  625)
-* BFD_RELOC_X86_64_TLSDESC_CALL:         howto manager.      (line  624)
-* BFD_RELOC_X86_64_TLSGD:                howto manager.      (line  611)
-* BFD_RELOC_X86_64_TLSLD:                howto manager.      (line  612)
-* BFD_RELOC_X86_64_TPOFF32:              howto manager.      (line  615)
-* BFD_RELOC_X86_64_TPOFF64:              howto manager.      (line  610)
-* BFD_RELOC_XC16X_PAG:                   howto manager.      (line 2398)
-* BFD_RELOC_XC16X_POF:                   howto manager.      (line 2399)
-* BFD_RELOC_XC16X_SEG:                   howto manager.      (line 2400)
-* BFD_RELOC_XC16X_SOF:                   howto manager.      (line 2401)
-* BFD_RELOC_XGATE_24:                    howto manager.      (line 2143)
-* BFD_RELOC_XGATE_GPAGE:                 howto manager.      (line 2140)
-* BFD_RELOC_XGATE_IMM3:                  howto manager.      (line 2160)
-* BFD_RELOC_XGATE_IMM4:                  howto manager.      (line 2163)
-* BFD_RELOC_XGATE_IMM5:                  howto manager.      (line 2166)
-* BFD_RELOC_XGATE_IMM8_HI:               howto manager.      (line 2156)
-* BFD_RELOC_XGATE_IMM8_LO:               howto manager.      (line 2152)
-* BFD_RELOC_XGATE_LO16:                  howto manager.      (line 2136)
-* BFD_RELOC_XGATE_PCREL_10:              howto manager.      (line 2149)
-* BFD_RELOC_XGATE_PCREL_9:               howto manager.      (line 2146)
-* BFD_RELOC_XGATE_RL_GROUP:              howto manager.      (line 2131)
-* BFD_RELOC_XGATE_RL_JUMP:               howto manager.      (line 2127)
-* BFD_RELOC_XSTORMY16_12:                howto manager.      (line 2390)
-* BFD_RELOC_XSTORMY16_24:                howto manager.      (line 2391)
-* BFD_RELOC_XSTORMY16_FPTR16:            howto manager.      (line 2392)
-* BFD_RELOC_XSTORMY16_REL_12:            howto manager.      (line 2389)
-* BFD_RELOC_XTENSA_ASM_EXPAND:           howto manager.      (line 2546)
-* BFD_RELOC_XTENSA_ASM_SIMPLIFY:         howto manager.      (line 2551)
-* BFD_RELOC_XTENSA_DIFF16:               howto manager.      (line 2493)
-* BFD_RELOC_XTENSA_DIFF32:               howto manager.      (line 2494)
-* BFD_RELOC_XTENSA_DIFF8:                howto manager.      (line 2492)
-* BFD_RELOC_XTENSA_GLOB_DAT:             howto manager.      (line 2482)
-* BFD_RELOC_XTENSA_JMP_SLOT:             howto manager.      (line 2483)
-* BFD_RELOC_XTENSA_OP0:                  howto manager.      (line 2540)
-* BFD_RELOC_XTENSA_OP1:                  howto manager.      (line 2541)
-* BFD_RELOC_XTENSA_OP2:                  howto manager.      (line 2542)
-* BFD_RELOC_XTENSA_PLT:                  howto manager.      (line 2487)
-* BFD_RELOC_XTENSA_RELATIVE:             howto manager.      (line 2484)
-* BFD_RELOC_XTENSA_RTLD:                 howto manager.      (line 2477)
-* BFD_RELOC_XTENSA_SLOT0_ALT:            howto manager.      (line 2522)
-* BFD_RELOC_XTENSA_SLOT0_OP:             howto manager.      (line 2502)
-* BFD_RELOC_XTENSA_SLOT10_ALT:           howto manager.      (line 2532)
-* BFD_RELOC_XTENSA_SLOT10_OP:            howto manager.      (line 2512)
-* BFD_RELOC_XTENSA_SLOT11_ALT:           howto manager.      (line 2533)
-* BFD_RELOC_XTENSA_SLOT11_OP:            howto manager.      (line 2513)
-* BFD_RELOC_XTENSA_SLOT12_ALT:           howto manager.      (line 2534)
-* BFD_RELOC_XTENSA_SLOT12_OP:            howto manager.      (line 2514)
-* BFD_RELOC_XTENSA_SLOT13_ALT:           howto manager.      (line 2535)
-* BFD_RELOC_XTENSA_SLOT13_OP:            howto manager.      (line 2515)
-* BFD_RELOC_XTENSA_SLOT14_ALT:           howto manager.      (line 2536)
-* BFD_RELOC_XTENSA_SLOT14_OP:            howto manager.      (line 2516)
-* BFD_RELOC_XTENSA_SLOT1_ALT:            howto manager.      (line 2523)
-* BFD_RELOC_XTENSA_SLOT1_OP:             howto manager.      (line 2503)
-* BFD_RELOC_XTENSA_SLOT2_ALT:            howto manager.      (line 2524)
-* BFD_RELOC_XTENSA_SLOT2_OP:             howto manager.      (line 2504)
-* BFD_RELOC_XTENSA_SLOT3_ALT:            howto manager.      (line 2525)
-* BFD_RELOC_XTENSA_SLOT3_OP:             howto manager.      (line 2505)
-* BFD_RELOC_XTENSA_SLOT4_ALT:            howto manager.      (line 2526)
-* BFD_RELOC_XTENSA_SLOT4_OP:             howto manager.      (line 2506)
-* BFD_RELOC_XTENSA_SLOT5_ALT:            howto manager.      (line 2527)
-* BFD_RELOC_XTENSA_SLOT5_OP:             howto manager.      (line 2507)
-* BFD_RELOC_XTENSA_SLOT6_ALT:            howto manager.      (line 2528)
-* BFD_RELOC_XTENSA_SLOT6_OP:             howto manager.      (line 2508)
-* BFD_RELOC_XTENSA_SLOT7_ALT:            howto manager.      (line 2529)
-* BFD_RELOC_XTENSA_SLOT7_OP:             howto manager.      (line 2509)
-* BFD_RELOC_XTENSA_SLOT8_ALT:            howto manager.      (line 2530)
-* BFD_RELOC_XTENSA_SLOT8_OP:             howto manager.      (line 2510)
-* BFD_RELOC_XTENSA_SLOT9_ALT:            howto manager.      (line 2531)
-* BFD_RELOC_XTENSA_SLOT9_OP:             howto manager.      (line 2511)
-* BFD_RELOC_XTENSA_TLS_ARG:              howto manager.      (line 2561)
-* BFD_RELOC_XTENSA_TLS_CALL:             howto manager.      (line 2562)
-* BFD_RELOC_XTENSA_TLS_DTPOFF:           howto manager.      (line 2558)
-* BFD_RELOC_XTENSA_TLS_FUNC:             howto manager.      (line 2560)
-* BFD_RELOC_XTENSA_TLS_TPOFF:            howto manager.      (line 2559)
-* BFD_RELOC_XTENSA_TLSDESC_ARG:          howto manager.      (line 2557)
-* BFD_RELOC_XTENSA_TLSDESC_FN:           howto manager.      (line 2556)
-* BFD_RELOC_Z80_DISP8:                   howto manager.      (line 2565)
-* BFD_RELOC_Z8K_CALLR:                   howto manager.      (line 2571)
-* BFD_RELOC_Z8K_DISP7:                   howto manager.      (line 2568)
-* BFD_RELOC_Z8K_IMM4L:                   howto manager.      (line 2574)
-* bfd_rename_section:                    section prototypes. (line  169)
-* bfd_scan_arch:                         Architectures.      (line  486)
-* bfd_scan_vma:                          Miscellaneous.      (line  124)
-* bfd_seach_for_target:                  bfd_target.         (line  524)
+                                                             (line 2719)
+* BFD_RELOC_TILEGX_IMM16_X1_HW2_PCREL:   howto manager.      (line 2677)
+* BFD_RELOC_TILEGX_IMM16_X1_HW2_PLT_PCREL: howto manager.    (line 2693)
+* BFD_RELOC_TILEGX_IMM16_X1_HW3:         howto manager.      (line 2665)
+* BFD_RELOC_TILEGX_IMM16_X1_HW3_PCREL:   howto manager.      (line 2679)
+* BFD_RELOC_TILEGX_IMM16_X1_HW3_PLT_PCREL: howto manager.    (line 2699)
+* BFD_RELOC_TILEGX_IMM8_X0:              howto manager.      (line 2645)
+* BFD_RELOC_TILEGX_IMM8_X0_TLS_ADD:      howto manager.      (line 2736)
+* BFD_RELOC_TILEGX_IMM8_X0_TLS_GD_ADD:   howto manager.      (line 2731)
+* BFD_RELOC_TILEGX_IMM8_X1:              howto manager.      (line 2647)
+* BFD_RELOC_TILEGX_IMM8_X1_TLS_ADD:      howto manager.      (line 2737)
+* BFD_RELOC_TILEGX_IMM8_X1_TLS_GD_ADD:   howto manager.      (line 2732)
+* BFD_RELOC_TILEGX_IMM8_Y0:              howto manager.      (line 2646)
+* BFD_RELOC_TILEGX_IMM8_Y0_TLS_ADD:      howto manager.      (line 2738)
+* BFD_RELOC_TILEGX_IMM8_Y0_TLS_GD_ADD:   howto manager.      (line 2733)
+* BFD_RELOC_TILEGX_IMM8_Y1:              howto manager.      (line 2648)
+* BFD_RELOC_TILEGX_IMM8_Y1_TLS_ADD:      howto manager.      (line 2739)
+* BFD_RELOC_TILEGX_IMM8_Y1_TLS_GD_ADD:   howto manager.      (line 2734)
+* BFD_RELOC_TILEGX_JMP_SLOT:             howto manager.      (line 2640)
+* BFD_RELOC_TILEGX_JUMPOFF_X1:           howto manager.      (line 2643)
+* BFD_RELOC_TILEGX_JUMPOFF_X1_PLT:       howto manager.      (line 2644)
+* BFD_RELOC_TILEGX_MF_IMM14_X1:          howto manager.      (line 2651)
+* BFD_RELOC_TILEGX_MMEND_X0:             howto manager.      (line 2653)
+* BFD_RELOC_TILEGX_MMSTART_X0:           howto manager.      (line 2652)
+* BFD_RELOC_TILEGX_MT_IMM14_X1:          howto manager.      (line 2650)
+* BFD_RELOC_TILEGX_RELATIVE:             howto manager.      (line 2641)
+* BFD_RELOC_TILEGX_SHAMT_X0:             howto manager.      (line 2654)
+* BFD_RELOC_TILEGX_SHAMT_X1:             howto manager.      (line 2655)
+* BFD_RELOC_TILEGX_SHAMT_Y0:             howto manager.      (line 2656)
+* BFD_RELOC_TILEGX_SHAMT_Y1:             howto manager.      (line 2657)
+* BFD_RELOC_TILEGX_TLS_DTPMOD32:         howto manager.      (line 2727)
+* BFD_RELOC_TILEGX_TLS_DTPMOD64:         howto manager.      (line 2724)
+* BFD_RELOC_TILEGX_TLS_DTPOFF32:         howto manager.      (line 2728)
+* BFD_RELOC_TILEGX_TLS_DTPOFF64:         howto manager.      (line 2725)
+* BFD_RELOC_TILEGX_TLS_GD_CALL:          howto manager.      (line 2730)
+* BFD_RELOC_TILEGX_TLS_IE_LOAD:          howto manager.      (line 2735)
+* BFD_RELOC_TILEGX_TLS_TPOFF32:          howto manager.      (line 2729)
+* BFD_RELOC_TILEGX_TLS_TPOFF64:          howto manager.      (line 2726)
+* BFD_RELOC_TILEPRO_BROFF_X1:            howto manager.      (line 2555)
+* BFD_RELOC_TILEPRO_COPY:                howto manager.      (line 2551)
+* BFD_RELOC_TILEPRO_DEST_IMM8_X1:        howto manager.      (line 2562)
+* BFD_RELOC_TILEPRO_GLOB_DAT:            howto manager.      (line 2552)
+* BFD_RELOC_TILEPRO_IMM16_X0:            howto manager.      (line 2565)
+* BFD_RELOC_TILEPRO_IMM16_X0_GOT:        howto manager.      (line 2581)
+* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HA:     howto manager.      (line 2587)
+* BFD_RELOC_TILEPRO_IMM16_X0_GOT_HI:     howto manager.      (line 2585)
+* BFD_RELOC_TILEPRO_IMM16_X0_GOT_LO:     howto manager.      (line 2583)
+* BFD_RELOC_TILEPRO_IMM16_X0_HA:         howto manager.      (line 2571)
+* BFD_RELOC_TILEPRO_IMM16_X0_HA_PCREL:   howto manager.      (line 2579)
+* BFD_RELOC_TILEPRO_IMM16_X0_HI:         howto manager.      (line 2569)
+* BFD_RELOC_TILEPRO_IMM16_X0_HI_PCREL:   howto manager.      (line 2577)
+* BFD_RELOC_TILEPRO_IMM16_X0_LO:         howto manager.      (line 2567)
+* BFD_RELOC_TILEPRO_IMM16_X0_LO_PCREL:   howto manager.      (line 2575)
+* BFD_RELOC_TILEPRO_IMM16_X0_PCREL:      howto manager.      (line 2573)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD:     howto manager.      (line 2603)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HA:  howto manager.      (line 2609)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_HI:  howto manager.      (line 2607)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_GD_LO:  howto manager.      (line 2605)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE:     howto manager.      (line 2611)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HA:  howto manager.      (line 2617)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_HI:  howto manager.      (line 2615)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_IE_LO:  howto manager.      (line 2613)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE:     howto manager.      (line 2622)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HA:  howto manager.      (line 2628)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_HI:  howto manager.      (line 2626)
+* BFD_RELOC_TILEPRO_IMM16_X0_TLS_LE_LO:  howto manager.      (line 2624)
+* BFD_RELOC_TILEPRO_IMM16_X1:            howto manager.      (line 2566)
+* BFD_RELOC_TILEPRO_IMM16_X1_GOT:        howto manager.      (line 2582)
+* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HA:     howto manager.      (line 2588)
+* BFD_RELOC_TILEPRO_IMM16_X1_GOT_HI:     howto manager.      (line 2586)
+* BFD_RELOC_TILEPRO_IMM16_X1_GOT_LO:     howto manager.      (line 2584)
+* BFD_RELOC_TILEPRO_IMM16_X1_HA:         howto manager.      (line 2572)
+* BFD_RELOC_TILEPRO_IMM16_X1_HA_PCREL:   howto manager.      (line 2580)
+* BFD_RELOC_TILEPRO_IMM16_X1_HI:         howto manager.      (line 2570)
+* BFD_RELOC_TILEPRO_IMM16_X1_HI_PCREL:   howto manager.      (line 2578)
+* BFD_RELOC_TILEPRO_IMM16_X1_LO:         howto manager.      (line 2568)
+* BFD_RELOC_TILEPRO_IMM16_X1_LO_PCREL:   howto manager.      (line 2576)
+* BFD_RELOC_TILEPRO_IMM16_X1_PCREL:      howto manager.      (line 2574)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD:     howto manager.      (line 2604)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HA:  howto manager.      (line 2610)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_HI:  howto manager.      (line 2608)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_GD_LO:  howto manager.      (line 2606)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE:     howto manager.      (line 2612)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HA:  howto manager.      (line 2618)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_HI:  howto manager.      (line 2616)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_IE_LO:  howto manager.      (line 2614)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE:     howto manager.      (line 2623)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HA:  howto manager.      (line 2629)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_HI:  howto manager.      (line 2627)
+* BFD_RELOC_TILEPRO_IMM16_X1_TLS_LE_LO:  howto manager.      (line 2625)
+* BFD_RELOC_TILEPRO_IMM8_X0:             howto manager.      (line 2558)
+* BFD_RELOC_TILEPRO_IMM8_X0_TLS_GD_ADD:  howto manager.      (line 2598)
+* BFD_RELOC_TILEPRO_IMM8_X1:             howto manager.      (line 2560)
+* BFD_RELOC_TILEPRO_IMM8_X1_TLS_GD_ADD:  howto manager.      (line 2599)
+* BFD_RELOC_TILEPRO_IMM8_Y0:             howto manager.      (line 2559)
+* BFD_RELOC_TILEPRO_IMM8_Y0_TLS_GD_ADD:  howto manager.      (line 2600)
+* BFD_RELOC_TILEPRO_IMM8_Y1:             howto manager.      (line 2561)
+* BFD_RELOC_TILEPRO_IMM8_Y1_TLS_GD_ADD:  howto manager.      (line 2601)
+* BFD_RELOC_TILEPRO_JMP_SLOT:            howto manager.      (line 2553)
+* BFD_RELOC_TILEPRO_JOFFLONG_X1:         howto manager.      (line 2556)
+* BFD_RELOC_TILEPRO_JOFFLONG_X1_PLT:     howto manager.      (line 2557)
+* BFD_RELOC_TILEPRO_MF_IMM15_X1:         howto manager.      (line 2564)
+* BFD_RELOC_TILEPRO_MMEND_X0:            howto manager.      (line 2590)
+* BFD_RELOC_TILEPRO_MMEND_X1:            howto manager.      (line 2592)
+* BFD_RELOC_TILEPRO_MMSTART_X0:          howto manager.      (line 2589)
+* BFD_RELOC_TILEPRO_MMSTART_X1:          howto manager.      (line 2591)
+* BFD_RELOC_TILEPRO_MT_IMM15_X1:         howto manager.      (line 2563)
+* BFD_RELOC_TILEPRO_RELATIVE:            howto manager.      (line 2554)
+* BFD_RELOC_TILEPRO_SHAMT_X0:            howto manager.      (line 2593)
+* BFD_RELOC_TILEPRO_SHAMT_X1:            howto manager.      (line 2594)
+* BFD_RELOC_TILEPRO_SHAMT_Y0:            howto manager.      (line 2595)
+* BFD_RELOC_TILEPRO_SHAMT_Y1:            howto manager.      (line 2596)
+* BFD_RELOC_TILEPRO_TLS_DTPMOD32:        howto manager.      (line 2619)
+* BFD_RELOC_TILEPRO_TLS_DTPOFF32:        howto manager.      (line 2620)
+* BFD_RELOC_TILEPRO_TLS_GD_CALL:         howto manager.      (line 2597)
+* BFD_RELOC_TILEPRO_TLS_IE_LOAD:         howto manager.      (line 2602)
+* BFD_RELOC_TILEPRO_TLS_TPOFF32:         howto manager.      (line 2621)
+* bfd_reloc_type_lookup:                 howto manager.      (line 2758)
+* BFD_RELOC_V850_16_GOT:                 howto manager.      (line 1203)
+* BFD_RELOC_V850_16_GOTOFF:              howto manager.      (line 1219)
+* BFD_RELOC_V850_16_PCREL:               howto manager.      (line 1183)
+* BFD_RELOC_V850_16_S1:                  howto manager.      (line 1195)
+* BFD_RELOC_V850_16_SPLIT_OFFSET:        howto manager.      (line 1193)
+* BFD_RELOC_V850_17_PCREL:               howto manager.      (line 1185)
+* BFD_RELOC_V850_22_PCREL:               howto manager.      (line 1137)
+* BFD_RELOC_V850_22_PLT_PCREL:           howto manager.      (line 1207)
+* BFD_RELOC_V850_23:                     howto manager.      (line 1187)
+* BFD_RELOC_V850_32_ABS:                 howto manager.      (line 1191)
+* BFD_RELOC_V850_32_GOT:                 howto manager.      (line 1205)
+* BFD_RELOC_V850_32_GOTOFF:              howto manager.      (line 1221)
+* BFD_RELOC_V850_32_GOTPCREL:            howto manager.      (line 1201)
+* BFD_RELOC_V850_32_PCREL:               howto manager.      (line 1189)
+* BFD_RELOC_V850_32_PLT_PCREL:           howto manager.      (line 1209)
+* BFD_RELOC_V850_9_PCREL:                howto manager.      (line 1135)
+* BFD_RELOC_V850_ALIGN:                  howto manager.      (line 1178)
+* BFD_RELOC_V850_CALLT_15_16_OFFSET:     howto manager.      (line 1199)
+* BFD_RELOC_V850_CALLT_16_16_OFFSET:     howto manager.      (line 1172)
+* BFD_RELOC_V850_CALLT_6_7_OFFSET:       howto manager.      (line 1170)
+* BFD_RELOC_V850_CODE:                   howto manager.      (line 1223)
+* BFD_RELOC_V850_COPY:                   howto manager.      (line 1211)
+* BFD_RELOC_V850_DATA:                   howto manager.      (line 1225)
+* BFD_RELOC_V850_GLOB_DAT:               howto manager.      (line 1213)
+* BFD_RELOC_V850_JMP_SLOT:               howto manager.      (line 1215)
+* BFD_RELOC_V850_LO16_S1:                howto manager.      (line 1197)
+* BFD_RELOC_V850_LO16_SPLIT_OFFSET:      howto manager.      (line 1180)
+* BFD_RELOC_V850_LONGCALL:               howto manager.      (line 1174)
+* BFD_RELOC_V850_LONGJUMP:               howto manager.      (line 1176)
+* BFD_RELOC_V850_RELATIVE:               howto manager.      (line 1217)
+* BFD_RELOC_V850_SDA_15_16_OFFSET:       howto manager.      (line 1141)
+* BFD_RELOC_V850_SDA_16_16_OFFSET:       howto manager.      (line 1139)
+* BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET: howto manager.      (line 1164)
+* BFD_RELOC_V850_TDA_16_16_OFFSET:       howto manager.      (line 1157)
+* BFD_RELOC_V850_TDA_4_4_OFFSET:         howto manager.      (line 1162)
+* BFD_RELOC_V850_TDA_4_5_OFFSET:         howto manager.      (line 1159)
+* BFD_RELOC_V850_TDA_6_8_OFFSET:         howto manager.      (line 1149)
+* BFD_RELOC_V850_TDA_7_7_OFFSET:         howto manager.      (line 1155)
+* BFD_RELOC_V850_TDA_7_8_OFFSET:         howto manager.      (line 1152)
+* BFD_RELOC_V850_ZDA_15_16_OFFSET:       howto manager.      (line 1146)
+* BFD_RELOC_V850_ZDA_16_16_OFFSET:       howto manager.      (line 1144)
+* BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET: howto manager.      (line 1167)
+* BFD_RELOC_VAX_GLOB_DAT:                howto manager.      (line 2066)
+* BFD_RELOC_VAX_JMP_SLOT:                howto manager.      (line 2067)
+* BFD_RELOC_VAX_RELATIVE:                howto manager.      (line 2068)
+* BFD_RELOC_VPE4KMATH_DATA:              howto manager.      (line 1691)
+* BFD_RELOC_VPE4KMATH_INSN:              howto manager.      (line 1692)
+* BFD_RELOC_VTABLE_ENTRY:                howto manager.      (line 1695)
+* BFD_RELOC_VTABLE_INHERIT:              howto manager.      (line 1694)
+* BFD_RELOC_X86_64_32S:                  howto manager.      (line  540)
+* BFD_RELOC_X86_64_COPY:                 howto manager.      (line  535)
+* BFD_RELOC_X86_64_DTPMOD64:             howto manager.      (line  541)
+* BFD_RELOC_X86_64_DTPOFF32:             howto manager.      (line  546)
+* BFD_RELOC_X86_64_DTPOFF64:             howto manager.      (line  542)
+* BFD_RELOC_X86_64_GLOB_DAT:             howto manager.      (line  536)
+* BFD_RELOC_X86_64_GOT32:                howto manager.      (line  533)
+* BFD_RELOC_X86_64_GOT64:                howto manager.      (line  551)
+* BFD_RELOC_X86_64_GOTOFF64:             howto manager.      (line  549)
+* BFD_RELOC_X86_64_GOTPC32:              howto manager.      (line  550)
+* BFD_RELOC_X86_64_GOTPC32_TLSDESC:      howto manager.      (line  556)
+* BFD_RELOC_X86_64_GOTPC64:              howto manager.      (line  553)
+* BFD_RELOC_X86_64_GOTPCREL:             howto manager.      (line  539)
+* BFD_RELOC_X86_64_GOTPCREL64:           howto manager.      (line  552)
+* BFD_RELOC_X86_64_GOTPLT64:             howto manager.      (line  554)
+* BFD_RELOC_X86_64_GOTTPOFF:             howto manager.      (line  547)
+* BFD_RELOC_X86_64_IRELATIVE:            howto manager.      (line  559)
+* BFD_RELOC_X86_64_JUMP_SLOT:            howto manager.      (line  537)
+* BFD_RELOC_X86_64_PC32_BND:             howto manager.      (line  560)
+* BFD_RELOC_X86_64_PLT32:                howto manager.      (line  534)
+* BFD_RELOC_X86_64_PLT32_BND:            howto manager.      (line  561)
+* BFD_RELOC_X86_64_PLTOFF64:             howto manager.      (line  555)
+* BFD_RELOC_X86_64_RELATIVE:             howto manager.      (line  538)
+* BFD_RELOC_X86_64_TLSDESC:              howto manager.      (line  558)
+* BFD_RELOC_X86_64_TLSDESC_CALL:         howto manager.      (line  557)
+* BFD_RELOC_X86_64_TLSGD:                howto manager.      (line  544)
+* BFD_RELOC_X86_64_TLSLD:                howto manager.      (line  545)
+* BFD_RELOC_X86_64_TPOFF32:              howto manager.      (line  548)
+* BFD_RELOC_X86_64_TPOFF64:              howto manager.      (line  543)
+* BFD_RELOC_XC16X_PAG:                   howto manager.      (line 2061)
+* BFD_RELOC_XC16X_POF:                   howto manager.      (line 2062)
+* BFD_RELOC_XC16X_SEG:                   howto manager.      (line 2063)
+* BFD_RELOC_XC16X_SOF:                   howto manager.      (line 2064)
+* BFD_RELOC_XGATE_24:                    howto manager.      (line 1838)
+* BFD_RELOC_XGATE_GPAGE:                 howto manager.      (line 1836)
+* BFD_RELOC_XGATE_IMM3:                  howto manager.      (line 1850)
+* BFD_RELOC_XGATE_IMM4:                  howto manager.      (line 1852)
+* BFD_RELOC_XGATE_IMM5:                  howto manager.      (line 1854)
+* BFD_RELOC_XGATE_IMM8_HI:               howto manager.      (line 1847)
+* BFD_RELOC_XGATE_IMM8_LO:               howto manager.      (line 1844)
+* BFD_RELOC_XGATE_LO16:                  howto manager.      (line 1833)
+* BFD_RELOC_XGATE_PCREL_10:              howto manager.      (line 1842)
+* BFD_RELOC_XGATE_PCREL_9:               howto manager.      (line 1840)
+* BFD_RELOC_XGATE_RL_GROUP:              howto manager.      (line 1829)
+* BFD_RELOC_XGATE_RL_JUMP:               howto manager.      (line 1826)
+* BFD_RELOC_XSTORMY16_12:                howto manager.      (line 2055)
+* BFD_RELOC_XSTORMY16_24:                howto manager.      (line 2056)
+* BFD_RELOC_XSTORMY16_FPTR16:            howto manager.      (line 2057)
+* BFD_RELOC_XSTORMY16_REL_12:            howto manager.      (line 2054)
+* BFD_RELOC_XTENSA_ASM_EXPAND:           howto manager.      (line 2206)
+* BFD_RELOC_XTENSA_ASM_SIMPLIFY:         howto manager.      (line 2210)
+* BFD_RELOC_XTENSA_DIFF16:               howto manager.      (line 2157)
+* BFD_RELOC_XTENSA_DIFF32:               howto manager.      (line 2158)
+* BFD_RELOC_XTENSA_DIFF8:                howto manager.      (line 2156)
+* BFD_RELOC_XTENSA_GLOB_DAT:             howto manager.      (line 2148)
+* BFD_RELOC_XTENSA_JMP_SLOT:             howto manager.      (line 2149)
+* BFD_RELOC_XTENSA_OP0:                  howto manager.      (line 2201)
+* BFD_RELOC_XTENSA_OP1:                  howto manager.      (line 2202)
+* BFD_RELOC_XTENSA_OP2:                  howto manager.      (line 2203)
+* BFD_RELOC_XTENSA_PLT:                  howto manager.      (line 2152)
+* BFD_RELOC_XTENSA_RELATIVE:             howto manager.      (line 2150)
+* BFD_RELOC_XTENSA_RTLD:                 howto manager.      (line 2144)
+* BFD_RELOC_XTENSA_SLOT0_ALT:            howto manager.      (line 2184)
+* BFD_RELOC_XTENSA_SLOT0_OP:             howto manager.      (line 2165)
+* BFD_RELOC_XTENSA_SLOT10_ALT:           howto manager.      (line 2194)
+* BFD_RELOC_XTENSA_SLOT10_OP:            howto manager.      (line 2175)
+* BFD_RELOC_XTENSA_SLOT11_ALT:           howto manager.      (line 2195)
+* BFD_RELOC_XTENSA_SLOT11_OP:            howto manager.      (line 2176)
+* BFD_RELOC_XTENSA_SLOT12_ALT:           howto manager.      (line 2196)
+* BFD_RELOC_XTENSA_SLOT12_OP:            howto manager.      (line 2177)
+* BFD_RELOC_XTENSA_SLOT13_ALT:           howto manager.      (line 2197)
+* BFD_RELOC_XTENSA_SLOT13_OP:            howto manager.      (line 2178)
+* BFD_RELOC_XTENSA_SLOT14_ALT:           howto manager.      (line 2198)
+* BFD_RELOC_XTENSA_SLOT14_OP:            howto manager.      (line 2179)
+* BFD_RELOC_XTENSA_SLOT1_ALT:            howto manager.      (line 2185)
+* BFD_RELOC_XTENSA_SLOT1_OP:             howto manager.      (line 2166)
+* BFD_RELOC_XTENSA_SLOT2_ALT:            howto manager.      (line 2186)
+* BFD_RELOC_XTENSA_SLOT2_OP:             howto manager.      (line 2167)
+* BFD_RELOC_XTENSA_SLOT3_ALT:            howto manager.      (line 2187)
+* BFD_RELOC_XTENSA_SLOT3_OP:             howto manager.      (line 2168)
+* BFD_RELOC_XTENSA_SLOT4_ALT:            howto manager.      (line 2188)
+* BFD_RELOC_XTENSA_SLOT4_OP:             howto manager.      (line 2169)
+* BFD_RELOC_XTENSA_SLOT5_ALT:            howto manager.      (line 2189)
+* BFD_RELOC_XTENSA_SLOT5_OP:             howto manager.      (line 2170)
+* BFD_RELOC_XTENSA_SLOT6_ALT:            howto manager.      (line 2190)
+* BFD_RELOC_XTENSA_SLOT6_OP:             howto manager.      (line 2171)
+* BFD_RELOC_XTENSA_SLOT7_ALT:            howto manager.      (line 2191)
+* BFD_RELOC_XTENSA_SLOT7_OP:             howto manager.      (line 2172)
+* BFD_RELOC_XTENSA_SLOT8_ALT:            howto manager.      (line 2192)
+* BFD_RELOC_XTENSA_SLOT8_OP:             howto manager.      (line 2173)
+* BFD_RELOC_XTENSA_SLOT9_ALT:            howto manager.      (line 2193)
+* BFD_RELOC_XTENSA_SLOT9_OP:             howto manager.      (line 2174)
+* BFD_RELOC_XTENSA_TLSDESC_ARG:          howto manager.      (line 2215)
+* BFD_RELOC_XTENSA_TLSDESC_FN:           howto manager.      (line 2214)
+* BFD_RELOC_XTENSA_TLS_ARG:              howto manager.      (line 2219)
+* BFD_RELOC_XTENSA_TLS_CALL:             howto manager.      (line 2220)
+* BFD_RELOC_XTENSA_TLS_DTPOFF:           howto manager.      (line 2216)
+* BFD_RELOC_XTENSA_TLS_FUNC:             howto manager.      (line 2218)
+* BFD_RELOC_XTENSA_TLS_TPOFF:            howto manager.      (line 2217)
+* BFD_RELOC_Z80_DISP8:                   howto manager.      (line 2222)
+* BFD_RELOC_Z8K_CALLR:                   howto manager.      (line 2226)
+* BFD_RELOC_Z8K_DISP7:                   howto manager.      (line 2224)
+* BFD_RELOC_Z8K_IMM4L:                   howto manager.      (line 2228)
+* bfd_rename_section:                    section prototypes. (line  167)
+* bfd_scan_arch:                         Architectures.      (line  499)
+* bfd_scan_vma:                          Miscellaneous.      (line  122)
+* bfd_seach_for_target:                  bfd_target.         (line  526)
+* bfd_sections_find_if:                  section prototypes. (line  197)
 * bfd_section_already_linked:            Writing the symbol table.
-                                                             (line   55)
-* bfd_section_list_clear:                section prototypes. (line    8)
-* bfd_sections_find_if:                  section prototypes. (line  199)
-* bfd_set_arch_info:                     Architectures.      (line  527)
-* bfd_set_archive_head:                  Archives.           (line   75)
+                                                             (line   54)
+* bfd_section_list_clear:                section prototypes. (line    7)
+* bfd_set_archive_head:                  Archives.           (line   74)
+* bfd_set_arch_info:                     Architectures.      (line  540)
 * bfd_set_assert_handler:                Error reporting.    (line  141)
-* bfd_set_default_target:                bfd_target.         (line  463)
-* bfd_set_error:                         Error reporting.    (line   57)
+* bfd_set_default_target:                bfd_target.         (line  465)
+* bfd_set_error:                         Error reporting.    (line   56)
 * bfd_set_error_handler:                 Error reporting.    (line   99)
-* bfd_set_error_program_name:            Error reporting.    (line  108)
-* bfd_set_file_flags:                    Miscellaneous.      (line   44)
-* bfd_set_format:                        Formats.            (line   68)
-* bfd_set_gp_size:                       Miscellaneous.      (line  114)
-* bfd_set_private_flags:                 Miscellaneous.      (line  191)
-* bfd_set_reloc:                         Miscellaneous.      (line   34)
-* bfd_set_section_contents:              section prototypes. (line  230)
-* bfd_set_section_flags:                 section prototypes. (line  154)
-* bfd_set_section_size:                  section prototypes. (line  216)
-* bfd_set_start_address:                 Miscellaneous.      (line   93)
+* bfd_set_error_program_name:            Error reporting.    (line  107)
+* bfd_set_file_flags:                    Miscellaneous.      (line   43)
+* bfd_set_format:                        Formats.            (line   67)
+* bfd_set_gp_size:                       Miscellaneous.      (line  112)
+* bfd_set_private_flags:                 Miscellaneous.      (line  186)
+* bfd_set_reloc:                         Miscellaneous.      (line   33)
+* bfd_set_section_contents:              section prototypes. (line  229)
+* bfd_set_section_flags:                 section prototypes. (line  152)
+* bfd_set_section_size:                  section prototypes. (line  214)
+* bfd_set_start_address:                 Miscellaneous.      (line   91)
 * bfd_set_symtab:                        symbol handling functions.
-                                                             (line   60)
+                                                             (line   59)
 * bfd_symbol_info:                       symbol handling functions.
-                                                             (line  130)
-* bfd_target_list:                       bfd_target.         (line  515)
-* bfd_write_bigendian_4byte_int:         Internal.           (line   13)
+                                                             (line  129)
+* bfd_target_list:                       bfd_target.         (line  517)
+* bfd_write_bigendian_4byte_int:         Internal.           (line   12)
 * bfd_zalloc:                            Opening and Closing.
-                                                             (line  236)
+                                                             (line  235)
 * bfd_zalloc2:                           Opening and Closing.
-                                                             (line  245)
-* coff_symbol_type:                      coff.               (line  245)
-* core_file_matches_executable_p:        Core Files.         (line   39)
+                                                             (line  244)
+* coff_symbol_type:                      coff.               (line  244)
+* core_file_matches_executable_p:        Core Files.         (line   38)
 * find_separate_debug_file:              Opening and Closing.
-                                                             (line  288)
-* generic_core_file_matches_executable_p: Core Files.        (line   49)
+                                                             (line  307)
+* generic_core_file_matches_executable_p: Core Files.        (line   48)
 * Hash tables:                           Hash Tables.        (line    6)
 * internal object-file format:           Canonical format.   (line   11)
 * Linker:                                Linker Functions.   (line    6)
-* Other functions:                       Miscellaneous.      (line  206)
+* Other functions:                       Miscellaneous.      (line  200)
+* separate_alt_debug_file_exists:        Opening and Closing.
+                                                             (line  298)
 * separate_debug_file_exists:            Opening and Closing.
-                                                             (line  279)
-* struct bfd_iovec:                      Miscellaneous.      (line  378)
+                                                             (line  289)
+* struct bfd_iovec:                      Miscellaneous.      (line  364)
 * target vector (_bfd_final_link):       Performing the Final Link.
                                                              (line    6)
 * target vector (_bfd_link_add_symbols): Adding Symbols to the Hash Table.
                                                              (line    6)
 * target vector (_bfd_link_hash_table_create): Creating a Linker Hash Table.
                                                              (line    6)
-* The HOWTO Macro:                       typedef arelent.    (line  288)
+* The HOWTO Macro:                       typedef arelent.    (line  289)
 * what is it?:                           Overview.           (line    6)
 
 
 
 Tag Table:
-Node: Top1182
-Node: Overview1521
-Node: History2572
-Node: How It Works3518
-Node: What BFD Version 2 Can Do5061
-Node: BFD information loss6376
-Node: Canonical format8908
-Node: BFD front end13280
-Node: typedef bfd13704
-Node: Error reporting24749
-Node: Miscellaneous29616
-Node: Memory Usage46984
-Node: Initialization48212
-Node: Sections48671
-Node: Section Input49154
-Node: Section Output50519
-Node: typedef asection53005
-Node: section prototypes78341
-Node: Symbols88598
-Node: Reading Symbols90193
-Node: Writing Symbols91300
-Node: Mini Symbols93041
-Node: typedef asymbol94015
-Node: symbol handling functions100254
-Node: Archives105596
-Node: Formats109625
-Node: Relocations112573
-Node: typedef arelent113300
-Node: howto manager128936
-Node: Core Files231991
-Node: Targets234029
-Node: bfd_target235999
-Node: Architectures259221
-Node: Opening and Closing285391
-Node: Internal297409
-Node: File Caching303754
-Node: Linker Functions305668
-Node: Creating a Linker Hash Table307341
-Node: Adding Symbols to the Hash Table309079
-Node: Differing file formats309979
-Node: Adding symbols from an object file311704
-Node: Adding symbols from an archive313855
-Node: Performing the Final Link316784
-Node: Information provided by the linker318026
-Node: Relocating the section contents319180
-Node: Writing the symbol table320931
-Node: Hash Tables325315
-Node: Creating and Freeing a Hash Table326513
-Node: Looking Up or Entering a String327763
-Node: Traversing a Hash Table329016
-Node: Deriving a New Hash Table Type329805
-Node: Define the Derived Structures330871
-Node: Write the Derived Creation Routine331952
-Node: Write Other Derived Routines334576
-Node: BFD back ends335891
-Node: What to Put Where336161
-Node: aout336341
-Node: coff342659
-Node: elf371096
-Node: mmo371497
-Node: File layout372425
-Node: Symbol-table378072
-Node: mmo section mapping381841
-Node: GNU Free Documentation License385493
-Node: BFD Index410576
+Node: Top1056
+Node: Overview1392
+Node: History2450
+Node: How It Works3395
+Node: What BFD Version 2 Can Do4932
+Node: BFD information loss6249
+Node: Canonical format8790
+Node: BFD front end13167
+Node: typedef bfd13591
+Node: Error reporting24512
+Node: Miscellaneous29371
+Node: Memory Usage46501
+Node: Initialization47732
+Node: Sections48191
+Node: Section Input48674
+Node: Section Output50043
+Node: typedef asection52530
+Node: section prototypes78695
+Node: Symbols88963
+Node: Reading Symbols90566
+Node: Writing Symbols91674
+Node: Mini Symbols93418
+Node: typedef asymbol94392
+Node: symbol handling functions100433
+Node: Archives105764
+Node: Formats109792
+Node: Relocations112743
+Node: typedef arelent113470
+Node: howto manager129121
+Node: Core Files235284
+Node: Targets237322
+Node: bfd_target239297
+Node: Architectures262511
+Node: Opening and Closing289383
+Node: Internal302723
+Node: File Caching309070
+Node: Linker Functions310988
+Node: Creating a Linker Hash Table312662
+Node: Adding Symbols to the Hash Table314401
+Node: Differing file formats315301
+Node: Adding symbols from an object file317026
+Node: Adding symbols from an archive319176
+Node: Performing the Final Link322105
+Node: Information provided by the linker323346
+Node: Relocating the section contents324500
+Node: Writing the symbol table326252
+Node: Hash Tables330635
+Node: Creating and Freeing a Hash Table331833
+Node: Looking Up or Entering a String333083
+Node: Traversing a Hash Table334336
+Node: Deriving a New Hash Table Type335125
+Node: Define the Derived Structures336191
+Node: Write the Derived Creation Routine337272
+Node: Write Other Derived Routines339896
+Node: BFD back ends341211
+Node: What to Put Where341481
+Node: aout341661
+Node: coff347984
+Node: elf376458
+Node: mmo376859
+Node: File layout377784
+Node: Symbol-table383422
+Node: mmo section mapping387189
+Node: GNU Free Documentation License390843
+Node: BFD Index415906
 
 End Tag Table
diff --git a/share/info/binutils.info b/share/info/binutils.info
index 7bba45b..f7d0976 100644
--- a/share/info/binutils.info
+++ b/share/info/binutils.info
@@ -1,7 +1,7 @@
-This is binutils.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/binutils/doc/binutils.texi.
+This is binutils.info, produced by makeinfo version 4.8 from
+binutils.texi.
 
-Copyright (C) 1991-2013 Free Software Foundation, Inc.
+   Copyright (C) 1991-2013 Free Software Foundation, Inc.
 
    Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -43,7 +43,7 @@ Introduction
 ************
 
 This brief manual contains documentation for the GNU binary utilities
-(Linux/GNU Binutils) version 2.23.52.0.2:
+(GNU Binutils) version 2.23.91:
 
    This document is distributed under the terms of the GNU Free
 Documentation License version 1.3.  A copy of the license is included
@@ -207,12 +207,15 @@ of the following, but you must specify only one of them:
 
      The modifier `v' makes `ar' list each file as it is appended.
 
-     Since the point of this operation is speed, the archive's symbol
-     table index is not updated, even if it already existed; you can
-     use `ar s' or `ranlib' explicitly to update the symbol table index.
+     Since the point of this operation is speed, implementations of
+     `ar' have the option of not updating the archive's symbol table if
+     one exists.  Too many different systems however assume that symbol
+     tables are always up-to-date, so GNU `ar' will rebuild the table
+     even with a quick append.
 
-     However, too many different systems assume quick append rebuilds
-     the index, so GNU `ar' implements `q' as a synonym for `r'.
+     Note - GNU `ar' treats the command `qs' as a synonym for `r' -
+     replacing already existing files in the archive and appending new
+     ones at the end.
 
 `r'
      Insert the files MEMBER... into ARCHIVE (with _replacement_). This
@@ -589,7 +592,7 @@ object files are listed as arguments, `nm' assumes the file `a.out'.
           same name.  If the symbol is defined anywhere, the common
           symbols are treated as undefined references.  For more
           details on common symbols, see the discussion of -warn-common
-          in *note Linker options: (ld.info)Options.
+          in *Note Linker options: (ld.info)Options.
 
     `D'
     `d'
@@ -612,6 +615,9 @@ object files are listed as arguments, `nm' assumes the file `a.out'.
           be invoked at runtime.  The runtime execution will then
           return the value to be used in the relocation.
 
+    `I'
+          The symbol is an indirect reference to another symbol.
+
     `N'
           The symbol is a debugging symbol.
 
@@ -665,8 +671,7 @@ object files are listed as arguments, `nm' assumes the file `a.out'.
           The symbol is a stabs symbol in an a.out object file.  In
           this case, the next values printed are the stabs other field,
           the stabs desc field, and the stab type.  Stabs symbols are
-          used to hold debugging information.  For more information,
-          see *note Stabs: (stabs.info)Top.
+          used to hold debugging information.
 
     `?'
           The symbol type is unknown, or object file format specific.
@@ -791,8 +796,8 @@ equivalent.
 
 `--plugin NAME'
      Load the plugin called NAME to add support for extra target types.
-     This option is only available if the toolchain has been built with
-     plugin support enabled.
+     This option is only available if the toolchain has been built
+     with plugin support enabled.
 
 `--size-sort'
      Sort symbols by size.  The size is computed as the difference
@@ -804,8 +809,8 @@ equivalent.
 `--special-syms'
      Display symbols which have a target-specific special meaning.
      These symbols are usually used by the target for some special
-     processing and are not normally helpful when included included in
-     the normal symbol lists.  For example for ARM targets this option
+     processing and are not normally helpful when included in the
+     normal symbol lists.  For example for ARM targets this option
      would skip the mapping symbols used to mark transitions between
      ARM code, THUMB code and data.
 
@@ -1827,6 +1832,9 @@ given.
           instruction mnemonic.  I.e., print 'daddu' or 'or' instead of
           'move', 'sll' instead of 'nop', etc.
 
+    `virt'
+          Disassemble the virtualization ASE instructions.
+
     `gpr-names=ABI'
           Print GPR (general-purpose register) names as appropriate for
           the specified ABI.  By default, GPR names are selected
@@ -1884,7 +1892,7 @@ given.
 
      For XCOFF, the available options are: `header', `aout',
      `sections', `syms', `relocs', `lineno', `loader', `except',
-     `typchk', `traceback' and `toc'.
+     `typchk', `traceback', `toc' and `ldinfo'.
 
 `-r'
 `--reloc'
@@ -1973,8 +1981,7 @@ given.
      in which `.stab' debugging symbol-table entries are carried in an
      ELF section.  In most other file formats, debugging symbol-table
      entries are interleaved with linkage symbols, and are visible in
-     the `--syms' output.  For more information on stabs symbols, see
-     *note Stabs: (stabs.info)Top.
+     the `--syms' output.
 
 `--start-address=ADDRESS'
      Start displaying data at the specified address.  This affects the
@@ -2138,8 +2145,9 @@ their placement in the archive.
      header will show zero for the UID, GID, and timestamp.  When this
      option is used, multiple runs will produce identical output files.
 
-     This is the default unless `binutils' was configured with
-     `--enable-deterministic-archives'.
+     If `binutils' was configured with
+     `--enable-deterministic-archives', then this mode is on by
+     default.  It can be disabled with the `-U' option, described below.
 
 `-t'
      Update the timestamp of the symbol map of an archive.
@@ -2149,8 +2157,9 @@ their placement in the archive.
      the `-D' option, above: the archive index will get actual UID,
      GID, timestamp, and file mode values.
 
-     This is the default unless `binutils' was configured with
-     `--enable-deterministic-archives'.
+     If `binutils' was configured _without_
+     `--enable-deterministic-archives', then this mode is on by default.
+
 
 
 File: binutils.info,  Node: size,  Next: strings,  Prev: ranlib,  Up: Top
@@ -2818,7 +2827,7 @@ file language used in header files, see the `linkers' section,
 `NLMLINK' in particular, of the `NLM Development and Tools Overview',
 which is part of the NLM Software Developer's Kit ("NLM SDK"),
 available from Novell, Inc.  `nlmconv' uses the GNU Binary File
-Descriptor library to read INFILE; see *note BFD: (ld.info)BFD, for
+Descriptor library to read INFILE; see *Note BFD: (ld.info)BFD, for
 more information.
 
    `nlmconv' can perform a link step.  In other words, you can list
@@ -2940,7 +2949,7 @@ Compiler.
      Specify the BFD format to use for a bin file as output.  This is a
      BFD target name; you can use the `--help' option to see a list of
      supported targets.  Normally `windmc' will use the default format,
-     which is the first one listed by the `--help' option.  *note
+     which is the first one listed by the `--help' option.  *Note
      Target Selection::.
 
 `-h PATH'
@@ -3092,7 +3101,7 @@ available to Windows.
      This is a BFD target name; you can use the `--help' option to see
      a list of supported targets.  Normally `windres' will use the
      default format, which is the first one listed by the `--help'
-     option.  *note Target Selection::.
+     option.  *Note Target Selection::.
 
 `--preprocessor PROGRAM'
      When `windres' reads an `rc' file, it runs it through the C
@@ -3657,8 +3666,9 @@ equivalent.  At least one option besides `-v' or `-H' must be given.
 `-u'
 `--unwind'
      Displays the contents of the file's unwind section, if it has one.
-     Only the unwind sections for IA64 ELF files, as well as ARM unwind
-     tables (`.ARM.exidx' / `.ARM.extab') are currently supported.
+     Only the unwind sections for IA64 ELF files, as well as ARM
+     unwind tables (`.ARM.exidx' / `.ARM.extab') are currently
+     supported.
 
 `-d'
 `--dynamic'
@@ -4059,8 +4069,7 @@ recommend you contact that organization first.
 individuals in the file `etc/SERVICE' in the GNU Emacs distribution.
 
    In any event, we also recommend that you send bug reports for the
-binary utilities to `http://www.sourceware.org/bugzilla/ and
-mailto:hjl.tools@gmail.com'.
+binary utilities to `http://www.sourceware.org/bugzilla/'.
 
    The fundamental principle of reporting bugs usefully is this:
 *report all the facts*.  If you are not sure whether to state a fact or
@@ -4689,21 +4698,23 @@ Binutils Index
 
 * Menu:
 
-* --enable-deterministic-archives <1>:   strip.               (line 105)
-* --enable-deterministic-archives <2>:   ranlib.              (line  32)
-* --enable-deterministic-archives <3>:   objcopy.             (line 292)
-* --enable-deterministic-archives:       ar cmdline.          (line 148)
-* .stab:                                 objdump.             (line 410)
-* Add prefix to absolute paths:          objdump.             (line 353)
+* --enable-deterministic-archives <1>:   objcopy.             (line 302)
+* --enable-deterministic-archives <2>:   ranlib.              (line  44)
+* --enable-deterministic-archives <3>:   ar cmdline.          (line 151)
+* --enable-deterministic-archives <4>:   strip.               (line 115)
+* --enable-deterministic-archives <5>:   ar cmdline.          (line 224)
+* --enable-deterministic-archives:       objcopy.             (line 292)
+* .stab:                                 objdump.             (line 413)
+* Add prefix to absolute paths:          objdump.             (line 356)
 * addr2line:                             addr2line.           (line   6)
 * address to file name and line number:  addr2line.           (line   6)
-* all header information, object file:   objdump.             (line 529)
+* all header information, object file:   objdump.             (line 531)
 * ar:                                    ar.                  (line   6)
 * ar compatibility:                      ar.                  (line  60)
 * architecture:                          objdump.             (line 197)
 * architectures available:               objdump.             (line 182)
 * archive contents:                      ranlib.              (line   6)
-* Archive file symbol index information: readelf.             (line 154)
+* Archive file symbol index information: readelf.             (line 155)
 * archive headers:                       objdump.             (line  67)
 * archives:                              ar.                  (line   6)
 * base files:                            dlltool.             (line 124)
@@ -4719,80 +4730,83 @@ Binutils Index
 * changing start address:                objcopy.             (line 332)
 * collections of files:                  ar.                  (line   6)
 * compatibility, ar:                     ar.                  (line  60)
-* contents of archive:                   ar cmdline.          (line  94)
+* contents of archive:                   ar cmdline.          (line  97)
 * crash:                                 Bug Criteria.        (line   9)
-* creating archives:                     ar cmdline.          (line 142)
-* creating thin archive:                 ar cmdline.          (line 207)
+* creating archives:                     ar cmdline.          (line 145)
+* creating thin archive:                 ar cmdline.          (line 210)
 * cxxfilt:                               c++filt.             (line  14)
-* dates in archive:                      ar cmdline.          (line 181)
-* debug symbols:                         objdump.             (line 375)
-* debugging symbols:                     nm.                  (line 145)
+* dates in archive:                      ar cmdline.          (line 184)
+* debug symbols:                         objdump.             (line 413)
+* debugging symbols:                     nm.                  (line 147)
 * deleting from archive:                 ar cmdline.          (line  26)
 * demangling C++ symbols:                c++filt.             (line   6)
-* demangling in nm:                      nm.                  (line 153)
-* demangling in objdump <1>:             addr2line.           (line  78)
-* demangling in objdump:                 objdump.             (line  95)
-* deterministic archives <1>:            strip.               (line 105)
-* deterministic archives <2>:            ranlib.              (line  32)
-* deterministic archives <3>:            objcopy.             (line 292)
-* deterministic archives:                ar cmdline.          (line 148)
+* demangling in nm:                      nm.                  (line 155)
+* demangling in objdump <1>:             objdump.             (line  95)
+* demangling in objdump:                 addr2line.           (line  78)
+* deterministic archives <1>:            ranlib.              (line  32)
+* deterministic archives <2>:            objcopy.             (line 292)
+* deterministic archives <3>:            ar cmdline.          (line 224)
+* deterministic archives <4>:            strip.               (line 105)
+* deterministic archives <5>:            ar cmdline.          (line 151)
+* deterministic archives <6>:            ranlib.              (line  44)
+* deterministic archives:                objcopy.             (line 302)
 * disassembling object code:             objdump.             (line 117)
 * disassembly architecture:              objdump.             (line 197)
 * disassembly endianness:                objdump.             (line 137)
-* disassembly, with source:              objdump.             (line 349)
+* disassembly, with source:              objdump.             (line 352)
 * discarding symbols:                    strip.               (line   6)
 * DLL:                                   dlltool.             (line   6)
 * dlltool:                               dlltool.             (line   6)
-* DWARF:                                 objdump.             (line 375)
-* dynamic relocation entries, in object file: objdump.        (line 337)
-* dynamic symbol table entries, printing: objdump.            (line 513)
-* dynamic symbols:                       nm.                  (line 165)
-* ELF dynamic section information:       readelf.             (line 112)
+* DWARF:                                 objdump.             (line 378)
+* dynamic relocation entries, in object file: objdump.        (line 340)
+* dynamic symbol table entries, printing: objdump.            (line 515)
+* dynamic symbols:                       nm.                  (line 167)
+* ELF dynamic section information:       readelf.             (line 113)
 * ELF dynamic symbol table information:  readelf.             (line  88)
 * ELF file header information:           readelf.             (line  57)
 * ELF file information:                  readelf.             (line   6)
 * ELF notes:                             readelf.             (line  97)
-* ELF object file format:                objdump.             (line 410)
+* ELF object file format:                objdump.             (line 413)
 * ELF program header information:        readelf.             (line  63)
 * ELF reloc information:                 readelf.             (line 101)
 * ELF section group information:         readelf.             (line  74)
-* ELF section information:               readelf.             (line  69)
+* ELF section information:               readelf.             (line  79)
 * ELF segment information:               readelf.             (line  63)
 * ELF symbol table information:          readelf.             (line  84)
-* ELF version sections information:      readelf.             (line 116)
+* ELF version sections information:      readelf.             (line 117)
 * elfedit:                               elfedit.             (line   6)
 * endianness:                            objdump.             (line 137)
 * error on valid input:                  Bug Criteria.        (line  12)
-* external symbols:                      nm.                  (line 177)
-* extract from archive:                  ar cmdline.          (line 109)
+* external symbols:                      nm.                  (line 179)
+* extract from archive:                  ar cmdline.          (line 112)
 * fatal signal:                          Bug Criteria.        (line   9)
-* file name:                             nm.                  (line 139)
-* header information, all:               objdump.             (line 529)
+* file name:                             nm.                  (line 141)
+* header information, all:               objdump.             (line 531)
 * input .def file:                       dlltool.             (line 120)
-* input file name:                       nm.                  (line 139)
-* Instruction width:                     objdump.             (line 370)
+* input file name:                       nm.                  (line 141)
+* Instruction width:                     objdump.             (line 373)
 * libraries:                             ar.                  (line  25)
 * listings strings:                      strings.             (line   6)
-* load plugin:                           nm.                  (line 250)
+* load plugin:                           nm.                  (line 252)
 * machine instructions:                  objdump.             (line 117)
 * moving in archive:                     ar cmdline.          (line  34)
 * MRI compatibility, ar:                 ar scripts.          (line   8)
-* name duplication in archive:           ar cmdline.          (line 103)
+* name duplication in archive:           ar cmdline.          (line 106)
 * name length:                           ar.                  (line  18)
 * nm:                                    nm.                  (line   6)
-* nm compatibility:                      nm.                  (line 149)
-* nm format:                             nm.                  (line 149)
-* not writing archive index:             ar cmdline.          (line 200)
+* nm compatibility:                      nm.                  (line 173)
+* nm format:                             nm.                  (line 173)
+* not writing archive index:             ar cmdline.          (line 203)
 * objdump:                               objdump.             (line   6)
-* object code format <1>:                addr2line.           (line  73)
-* object code format <2>:                strings.             (line  67)
-* object code format <3>:                size.                (line  84)
+* object code format <1>:                strings.             (line  67)
+* object code format <2>:                nm.                  (line 278)
+* object code format <3>:                addr2line.           (line  73)
 * object code format <4>:                objdump.             (line  81)
-* object code format:                    nm.                  (line 276)
+* object code format:                    size.                (line  84)
 * object file header:                    objdump.             (line 143)
 * object file information:               objdump.             (line   6)
 * object file offsets:                   objdump.             (line 148)
-* object file sections:                  objdump.             (line 344)
+* object file sections:                  objdump.             (line 347)
 * object formats available:              objdump.             (line 182)
 * operations on archive:                 ar cmdline.          (line  22)
 * printing from archive:                 ar cmdline.          (line  46)
@@ -4800,85 +4814,85 @@ Binutils Index
 * quick append to archive:               ar cmdline.          (line  54)
 * radix for section sizes:               size.                (line  66)
 * ranlib <1>:                            ranlib.              (line   6)
-* ranlib:                                ar cmdline.          (line  88)
+* ranlib:                                ar cmdline.          (line  91)
 * readelf:                               readelf.             (line   6)
-* relative placement in archive:         ar cmdline.          (line 130)
-* relocation entries, in object file:    objdump.             (line 331)
+* relative placement in archive:         ar cmdline.          (line 133)
+* relocation entries, in object file:    objdump.             (line 334)
 * removing symbols:                      strip.               (line   6)
-* repeated names in archive:             ar cmdline.          (line 103)
-* replacement in archive:                ar cmdline.          (line  70)
+* repeated names in archive:             ar cmdline.          (line 106)
+* replacement in archive:                ar cmdline.          (line  73)
 * reporting bugs:                        Reporting Bugs.      (line   6)
 * scripts, ar:                           ar scripts.          (line   8)
 * section addresses in objdump:          objdump.             (line  73)
 * section headers:                       objdump.             (line 164)
 * section information:                   objdump.             (line 187)
 * section sizes:                         size.                (line   6)
-* sections, full contents:               objdump.             (line 344)
+* sections, full contents:               objdump.             (line 347)
 * size:                                  size.                (line   6)
 * size display format:                   size.                (line  27)
 * size number format:                    size.                (line  66)
-* sorting symbols:                       nm.                  (line 200)
+* sorting symbols:                       nm.                  (line 202)
 * source code context:                   objdump.             (line 157)
-* source disassembly:                    objdump.             (line 349)
-* source file name:                      nm.                  (line 139)
+* source disassembly:                    objdump.             (line 352)
+* source file name:                      nm.                  (line 141)
 * source filenames for object files:     objdump.             (line 191)
-* stab:                                  objdump.             (line 410)
-* start-address:                         objdump.             (line 420)
-* stop-address:                          objdump.             (line 424)
+* stab:                                  objdump.             (line 413)
+* start-address:                         objdump.             (line 422)
+* stop-address:                          objdump.             (line 426)
 * strings:                               strings.             (line   6)
 * strings, printing:                     strings.             (line   6)
 * strip:                                 strip.               (line   6)
-* Strip absolute paths:                  objdump.             (line 356)
-* symbol index <1>:                      ranlib.              (line   6)
-* symbol index:                          ar.                  (line  28)
-* symbol index, listing:                 nm.                  (line 222)
-* symbol line numbers:                   nm.                  (line 185)
-* symbol table entries, printing:        objdump.             (line 429)
+* Strip absolute paths:                  objdump.             (line 359)
+* symbol index <1>:                      ar.                  (line  28)
+* symbol index:                          ranlib.              (line   6)
+* symbol index, listing:                 nm.                  (line 224)
+* symbol line numbers:                   nm.                  (line 187)
+* symbol table entries, printing:        objdump.             (line 431)
 * symbols:                               nm.                  (line   6)
 * symbols, discarding:                   strip.               (line   6)
 * thin archives:                         ar.                  (line  40)
-* undefined symbols:                     nm.                  (line 233)
+* undefined symbols:                     nm.                  (line 235)
 * Unix compatibility, ar:                ar cmdline.          (line   8)
 * unwind information:                    readelf.             (line 106)
 * Update ELF header:                     elfedit.             (line   6)
-* updating an archive:                   ar cmdline.          (line 212)
+* updating an archive:                   ar cmdline.          (line 215)
 * version:                               Top.                 (line   6)
 * VMA in objdump:                        objdump.             (line  73)
-* wide output, printing:                 objdump.             (line 535)
-* writing archive index:                 ar cmdline.          (line 194)
+* wide output, printing:                 objdump.             (line 537)
+* writing archive index:                 ar cmdline.          (line 197)
 
 
 
 Tag Table:
-Node: Top2020
-Node: ar3743
-Node: ar cmdline6881
-Node: ar scripts17096
-Node: nm22784
-Node: objcopy32680
-Node: objdump64449
-Node: ranlib86578
-Node: size88095
-Node: strings91099
-Node: strip93557
-Node: c++filt100789
-Ref: c++filt-Footnote-1105630
-Node: addr2line105736
-Node: nlmconv110073
-Node: windmc112678
-Node: windres116327
-Node: dlltool122688
-Node: def file format135568
-Node: readelf138107
-Node: elfedit145657
-Node: Common Options147911
-Node: Selecting the Target System148951
-Node: Target Selection149883
-Node: Architecture Selection151865
-Node: Reporting Bugs152693
-Node: Bug Criteria153472
-Node: Bug Reporting154025
-Node: GNU Free Documentation License160926
-Node: Binutils Index186105
+Node: Top1896
+Node: ar3609
+Node: ar cmdline6747
+Node: ar scripts17089
+Node: nm22777
+Node: objcopy32671
+Node: objdump64440
+Node: ranlib86571
+Node: size88176
+Node: strings91180
+Node: strip93638
+Node: c++filt100870
+Ref: c++filt-Footnote-1105711
+Node: addr2line105817
+Node: nlmconv110154
+Node: windmc112759
+Node: windres116408
+Node: dlltool122769
+Node: def file format135649
+Node: readelf138188
+Node: elfedit145743
+Node: Common Options147997
+Node: Selecting the Target System149037
+Node: Target Selection149969
+Node: Architecture Selection151951
+Node: Reporting Bugs152779
+Node: Bug Criteria153558
+Node: Bug Reporting154111
+Node: GNU Free Documentation License160981
+Node: Binutils Index186160
 
 End Tag Table
diff --git a/share/info/configure.info b/share/info/configure.info
index 16af9fb..cee206a 100644
--- a/share/info/configure.info
+++ b/share/info/configure.info
@@ -1,5 +1,5 @@
-This is configure.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/etc/configure.texi.
+This is configure.info, produced by makeinfo version 4.8 from
+./configure.texi.
 
 INFO-DIR-SECTION GNU admin
 START-INFO-DIR-ENTRY
@@ -856,7 +856,7 @@ file:
      AC_OUTPUT(Makefile)
 
    The first four macros in this file, and the last one, were described
-above; see *note Write configure.in::.  If we omit these macros, then
+above; see *Note Write configure.in::.  If we omit these macros, then
 when we run `automake' we will get a reminder that we need them.
 
    The other macros are standard autoconf macros.
@@ -1510,7 +1510,7 @@ variables when the `configure' script is run.
      The first three parts of the canonical configuration name.
 
    The shell variables may be used by putting shell code in
-`configure.in'.  For an example, see *note Using Configuration Names::.
+`configure.in'.  For an example, see *Note Using Configuration Names::.
 
 
 File: configure.info,  Node: Specifying the Target,  Next: Using the Target Type,  Prev: Using the Host Type,  Up: Cross Compilation Tools
@@ -2710,64 +2710,64 @@ Index
 
 
 Tag Table:
-Node: Top1087
-Node: Introduction1615
-Node: Goals2697
-Node: Tools3421
-Node: History4415
-Node: Building7413
-Node: Getting Started10676
-Node: Write configure.in11189
-Node: Write Makefile.am18440
-Node: Write acconfig.h21617
-Node: Generate files23154
-Node: Getting Started Example25120
-Node: Getting Started Example 125875
-Node: Getting Started Example 227796
-Node: Getting Started Example 330791
-Node: Generate Files in Example33155
-Node: Files34245
-Node: Developer Files34856
-Node: Developer Files Picture35236
-Node: Written Developer Files36524
-Node: Generated Developer Files39076
-Node: Build Files42220
-Node: Build Files Picture42881
-Node: Build Files Description43645
-Node: Support Files45651
-Node: Configuration Names48533
-Node: Configuration Name Definition49033
-Node: Using Configuration Names51356
-Node: Cross Compilation Tools53326
-Node: Cross Compilation Concepts54017
-Node: Host and Target54985
-Node: Using the Host Type56486
-Node: Specifying the Target57835
-Node: Using the Target Type58624
-Node: Cross Tools in the Cygnus Tree62055
-Node: Host and Target Libraries63112
-Node: Target Library Configure Scripts66861
-Node: Make Targets in Cygnus Tree69953
-Node: Target libiberty71301
-Node: Canadian Cross72688
-Node: Canadian Cross Example73529
-Node: Canadian Cross Concepts74648
-Node: Build Cross Host Tools76160
-Node: Build and Host Options77112
-Node: CCross not in Cygnus Tree78898
-Node: CCross in Cygnus Tree79876
-Node: Standard Cygnus CCross80297
-Node: Cross Cygnus CCross81661
-Node: Supporting Canadian Cross84461
-Node: CCross in Configure85076
-Node: CCross in Make88244
-Node: Cygnus Configure89847
-Node: Cygnus Configure Basics90682
-Node: Cygnus Configure in C++ Libraries95360
-Node: Multilibs96367
-Node: Multilibs in gcc97412
-Node: Multilibs in Target Libraries98490
-Node: FAQ102681
-Node: Index106781
+Node: Top971
+Node: Introduction1499
+Node: Goals2581
+Node: Tools3305
+Node: History4299
+Node: Building7297
+Node: Getting Started10560
+Node: Write configure.in11073
+Node: Write Makefile.am18324
+Node: Write acconfig.h21501
+Node: Generate files23038
+Node: Getting Started Example25004
+Node: Getting Started Example 125759
+Node: Getting Started Example 227680
+Node: Getting Started Example 330675
+Node: Generate Files in Example33039
+Node: Files34129
+Node: Developer Files34740
+Node: Developer Files Picture35120
+Node: Written Developer Files36408
+Node: Generated Developer Files38960
+Node: Build Files42104
+Node: Build Files Picture42765
+Node: Build Files Description43529
+Node: Support Files45535
+Node: Configuration Names48417
+Node: Configuration Name Definition48917
+Node: Using Configuration Names51240
+Node: Cross Compilation Tools53210
+Node: Cross Compilation Concepts53901
+Node: Host and Target54869
+Node: Using the Host Type56370
+Node: Specifying the Target57719
+Node: Using the Target Type58508
+Node: Cross Tools in the Cygnus Tree61939
+Node: Host and Target Libraries62996
+Node: Target Library Configure Scripts66745
+Node: Make Targets in Cygnus Tree69837
+Node: Target libiberty71185
+Node: Canadian Cross72572
+Node: Canadian Cross Example73413
+Node: Canadian Cross Concepts74532
+Node: Build Cross Host Tools76044
+Node: Build and Host Options76996
+Node: CCross not in Cygnus Tree78782
+Node: CCross in Cygnus Tree79760
+Node: Standard Cygnus CCross80181
+Node: Cross Cygnus CCross81545
+Node: Supporting Canadian Cross84345
+Node: CCross in Configure84960
+Node: CCross in Make88128
+Node: Cygnus Configure89731
+Node: Cygnus Configure Basics90566
+Node: Cygnus Configure in C++ Libraries95244
+Node: Multilibs96251
+Node: Multilibs in gcc97296
+Node: Multilibs in Target Libraries98374
+Node: FAQ102565
+Node: Index106665
 
 End Tag Table
diff --git a/share/info/gprof.info b/share/info/gprof.info
index 1310dea..bb934b4 100644
--- a/share/info/gprof.info
+++ b/share/info/gprof.info
@@ -1,12 +1,6 @@
-This is gprof.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/gprof/gprof.texi.
+This is gprof.info, produced by makeinfo version 5.1 from gprof.texi.
 
-INFO-DIR-SECTION Software development
-START-INFO-DIR-ENTRY
-* gprof: (gprof).                Profiling your program's execution
-END-INFO-DIR-ENTRY
-
-   This file documents the gprof profiler of the GNU system.
+This file documents the gprof profiler of the GNU system.
 
    Copyright (C) 1988, 1992, 1997, 1998, 1999, 2000, 2001, 2003, 2007,
 2008, 2009 Free Software Foundation, Inc.
@@ -18,22 +12,27 @@ Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
 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
+* gprof: (gprof).                Profiling your program's execution
+END-INFO-DIR-ENTRY
+
 
 File: gprof.info,  Node: Top,  Next: Introduction,  Up: (dir)
 
 Profiling a Program: Where Does It Spend Its Time?
 **************************************************
 
-This manual describes the GNU profiler, `gprof', and how you can use it
+This manual describes the GNU profiler, 'gprof', and how you can use it
 to determine which parts of a program are taking most of the execution
 time.  We assume that you know how to write, compile, and execute
-programs.  GNU `gprof' was written by Jay Fenlason.
+programs.  GNU 'gprof' was written by Jay Fenlason.
 
-   This manual is for `gprof' (Linux/GNU Binutils) version 2.23.52.0.2.
+   This manual is for 'gprof' (GNU Binutils) version 2.24.0.
 
    This document is distributed under the terms of the GNU Free
-Documentation License version 1.3.  A copy of the license is included
-in the section entitled "GNU Free Documentation License".
+Documentation License version 1.3.  A copy of the license is included in
+the section entitled "GNU Free Documentation License".
 
 * Menu:
 
@@ -41,13 +40,13 @@ in the section entitled "GNU Free Documentation License".
 
 * Compiling::           How to compile your program for profiling.
 * Executing::           Executing your program to generate profile data
-* Invoking::            How to run `gprof', and its options
+* Invoking::            How to run 'gprof', and its options
 
-* Output::              Interpreting `gprof''s output
+* Output::              Interpreting 'gprof''s output
 
 * Inaccuracy::          Potential problems you should be aware of
 * How do I?::           Answers to common questions
-* Incompatibilities::   (between GNU `gprof' and Unix `gprof'.)
+* Incompatibilities::   (between GNU 'gprof' and Unix 'gprof'.)
 * Details::             Details of how profiling is done
 * GNU Free Documentation License::  GNU Free Documentation License
 
@@ -66,12 +65,11 @@ called more or less often than you expected.  This may help you spot
 bugs that had otherwise been unnoticed.
 
    Since the profiler uses information collected during the actual
-execution of your program, it can be used on programs that are too
-large or too complex to analyze by reading the source.  However, how
-your program is run will affect the information that shows up in the
-profile data.  If you don't use some feature of your program while it
-is being profiled, no profile information will be generated for that
-feature.
+execution of your program, it can be used on programs that are too large
+or too complex to analyze by reading the source.  However, how your
+program is run will affect the information that shows up in the profile
+data.  If you don't use some feature of your program while it is being
+profiled, no profile information will be generated for that feature.
 
    Profiling has several steps:
 
@@ -81,7 +79,7 @@ feature.
    * You must execute your program to generate a profile data file.
      *Note Executing the Program: Executing.
 
-   * You must run `gprof' to analyze the profile data.  *Note `gprof'
+   * You must run 'gprof' to analyze the profile data.  *Note 'gprof'
      Command Summary: Invoking.
 
    The next three chapters explain these steps in greater detail.
@@ -93,12 +91,11 @@ function, and how many times that function was called.  If you simply
 want to know which functions burn most of the cycles, it is stated
 concisely here.  *Note The Flat Profile: Flat Profile.
 
-   The "call graph" shows, for each function, which functions called
-it, which other functions it called, and how many times.  There is also
-an estimate of how much time was spent in the subroutines of each
-function.  This can suggest places where you might try to eliminate
-function calls that use a lot of time.  *Note The Call Graph: Call
-Graph.
+   The "call graph" shows, for each function, which functions called it,
+which other functions it called, and how many times.  There is also an
+estimate of how much time was spent in the subroutines of each function.
+This can suggest places where you might try to eliminate function calls
+that use a lot of time.  *Note The Call Graph: Call Graph.
 
    The "annotated source" listing is a copy of the program's source
 code, labeled with the number of times each line of the program was
@@ -117,32 +114,32 @@ File: gprof.info,  Node: Compiling,  Next: Executing,  Prev: Introduction,  Up:
 The first step in generating profile information for your program is to
 compile and link it with profiling enabled.
 
-   To compile a source file for profiling, specify the `-pg' option when
+   To compile a source file for profiling, specify the '-pg' option when
 you run the compiler.  (This is in addition to the options you normally
 use.)
 
-   To link the program for profiling, if you use a compiler such as `cc'
-to do the linking, simply specify `-pg' in addition to your usual
-options.  The same option, `-pg', alters either compilation or linking
+   To link the program for profiling, if you use a compiler such as 'cc'
+to do the linking, simply specify '-pg' in addition to your usual
+options.  The same option, '-pg', alters either compilation or linking
 to do what is necessary for profiling.  Here are examples:
 
      cc -g -c myprog.c utils.c -pg
      cc -o myprog myprog.o utils.o -pg
 
-   The `-pg' option also works with a command that both compiles and
+   The '-pg' option also works with a command that both compiles and
 links:
 
      cc -o myprog myprog.c utils.c -g -pg
 
-   Note: The `-pg' option must be part of your compilation options as
-well as your link options.  If it is not then no call-graph data will
-be gathered and when you run `gprof' you will get an error message like
+   Note: The '-pg' option must be part of your compilation options as
+well as your link options.  If it is not then no call-graph data will be
+gathered and when you run 'gprof' you will get an error message like
 this:
 
      gprof: gmon.out file is missing call-graph data
 
-   If you add the `-Q' switch to suppress the printing of the call
-graph data you will still be able to see the time samples:
+   If you add the '-Q' switch to suppress the printing of the call graph
+data you will still be able to see the time samples:
 
      Flat profile:
 
@@ -153,51 +150,51 @@ graph data you will still be able to see the time samples:
       35.29      0.14     0.06                             main
       20.59      0.17     0.04                             bazMillion
 
-   If you run the linker `ld' directly instead of through a compiler
-such as `cc', you may have to specify a profiling startup file
-`gcrt0.o' as the first input file instead of the usual startup file
-`crt0.o'.  In addition, you would probably want to specify the
-profiling C library, `libc_p.a', by writing `-lc_p' instead of the
-usual `-lc'.  This is not absolutely necessary, but doing this gives
-you number-of-calls information for standard library functions such as
-`read' and `open'.  For example:
+   If you run the linker 'ld' directly instead of through a compiler
+such as 'cc', you may have to specify a profiling startup file 'gcrt0.o'
+as the first input file instead of the usual startup file 'crt0.o'.  In
+addition, you would probably want to specify the profiling C library,
+'libc_p.a', by writing '-lc_p' instead of the usual '-lc'.  This is not
+absolutely necessary, but doing this gives you number-of-calls
+information for standard library functions such as 'read' and 'open'.
+For example:
 
      ld -o myprog /lib/gcrt0.o myprog.o utils.o -lc_p
 
    If you are running the program on a system which supports shared
-libraries you may run into problems with the profiling support code in
-a shared library being called before that library has been fully
+libraries you may run into problems with the profiling support code in a
+shared library being called before that library has been fully
 initialised.  This is usually detected by the program encountering a
 segmentation fault as soon as it is run.  The solution is to link
-against a static version of the library containing the profiling
-support code, which for `gcc' users can be done via the `-static' or
-`-static-libgcc' command line option.  For example:
+against a static version of the library containing the profiling support
+code, which for 'gcc' users can be done via the '-static' or
+'-static-libgcc' command line option.  For example:
 
      gcc -g -pg -static-libgcc myprog.c utils.c -o myprog
 
-   If you compile only some of the modules of the program with `-pg',
+   If you compile only some of the modules of the program with '-pg',
 you can still profile the program, but you won't get complete
-information about the modules that were compiled without `-pg'.  The
-only information you get for the functions in those modules is the
-total time spent in them; there is no record of how many times they
-were called, or from where.  This will not affect the flat profile
-(except that the `calls' field for the functions will be blank), but
-will greatly reduce the usefulness of the call graph.
+information about the modules that were compiled without '-pg'.  The
+only information you get for the functions in those modules is the total
+time spent in them; there is no record of how many times they were
+called, or from where.  This will not affect the flat profile (except
+that the 'calls' field for the functions will be blank), but will
+greatly reduce the usefulness of the call graph.
 
    If you wish to perform line-by-line profiling you should use the
-`gcov' tool instead of `gprof'.  See that tool's manual or info pages
+'gcov' tool instead of 'gprof'.  See that tool's manual or info pages
 for more details of how to do this.
 
-   Note, older versions of `gcc' produce line-by-line profiling
-information that works with `gprof' rather than `gcov' so there is
-still support for displaying this kind of information in `gprof'. *Note
+   Note, older versions of 'gcc' produce line-by-line profiling
+information that works with 'gprof' rather than 'gcov' so there is still
+support for displaying this kind of information in 'gprof'.  *Note
 Line-by-line Profiling: Line-by-line.
 
-   It also worth noting that `gcc' implements a
-`-finstrument-functions' command line option which will insert calls to
-special user supplied instrumentation routines at the entry and exit of
-every function in their program.  This can be used to implement an
-alternative profiling scheme.
+   It also worth noting that 'gcc' implements a '-finstrument-functions'
+command line option which will insert calls to special user supplied
+instrumentation routines at the entry and exit of every function in
+their program.  This can be used to implement an alternative profiling
+scheme.
 
 
 File: gprof.info,  Node: Executing,  Next: Invoking,  Prev: Compiling,  Up: Top
@@ -206,7 +203,7 @@ File: gprof.info,  Node: Executing,  Next: Invoking,  Prev: Compiling,  Up: Top
 ***********************
 
 Once the program is compiled for profiling, you must run it in order to
-generate the information that `gprof' needs.  Simply run the program as
+generate the information that 'gprof' needs.  Simply run the program as
 usual, using the normal arguments, file names, etc.  The program should
 run normally, producing the same output as usual.  It will, however, run
 somewhat slower than normal because of the time spent collecting and
@@ -220,62 +217,61 @@ command you give to your program is to quit, the profile data will show
 the time used in initialization and in cleanup, but not much else.
 
    Your program will write the profile data into a file called
-`gmon.out' just before exiting.  If there is already a file called
-`gmon.out', its contents are overwritten.  There is currently no way to
+'gmon.out' just before exiting.  If there is already a file called
+'gmon.out', its contents are overwritten.  There is currently no way to
 tell the program to write the profile data under a different name, but
 you can rename the file afterwards if you are concerned that it may be
 overwritten.
 
-   In order to write the `gmon.out' file properly, your program must
-exit normally: by returning from `main' or by calling `exit'.  Calling
-the low-level function `_exit' does not write the profile data, and
+   In order to write the 'gmon.out' file properly, your program must
+exit normally: by returning from 'main' or by calling 'exit'.  Calling
+the low-level function '_exit' does not write the profile data, and
 neither does abnormal termination due to an unhandled signal.
 
-   The `gmon.out' file is written in the program's _current working
+   The 'gmon.out' file is written in the program's _current working
 directory_ at the time it exits.  This means that if your program calls
-`chdir', the `gmon.out' file will be left in the last directory your
-program `chdir''d to.  If you don't have permission to write in this
+'chdir', the 'gmon.out' file will be left in the last directory your
+program 'chdir''d to.  If you don't have permission to write in this
 directory, the file is not written, and you will get an error message.
 
    Older versions of the GNU profiling library may also write a file
-called `bb.out'.  This file, if present, contains an human-readable
+called 'bb.out'.  This file, if present, contains an human-readable
 listing of the basic-block execution counts.  Unfortunately, the
-appearance of a human-readable `bb.out' means the basic-block counts
-didn't get written into `gmon.out'.  The Perl script `bbconv.pl',
-included with the `gprof' source distribution, will convert a `bb.out'
-file into a format readable by `gprof'.  Invoke it like this:
+appearance of a human-readable 'bb.out' means the basic-block counts
+didn't get written into 'gmon.out'.  The Perl script 'bbconv.pl',
+included with the 'gprof' source distribution, will convert a 'bb.out'
+file into a format readable by 'gprof'.  Invoke it like this:
 
      bbconv.pl < bb.out > BH-DATA
 
-   This translates the information in `bb.out' into a form that `gprof'
-can understand.  But you still need to tell `gprof' about the existence
+   This translates the information in 'bb.out' into a form that 'gprof'
+can understand.  But you still need to tell 'gprof' about the existence
 of this translated information.  To do that, include BB-DATA on the
-`gprof' command line, _along with `gmon.out'_, like this:
+'gprof' command line, _along with 'gmon.out'_, like this:
 
      gprof OPTIONS EXECUTABLE-FILE gmon.out BB-DATA [YET-MORE-PROFILE-DATA-FILES...] [> OUTFILE]
 
 
 File: gprof.info,  Node: Invoking,  Next: Output,  Prev: Executing,  Up: Top
 
-4 `gprof' Command Summary
+4 'gprof' Command Summary
 *************************
 
-After you have a profile data file `gmon.out', you can run `gprof' to
-interpret the information in it.  The `gprof' program prints a flat
+After you have a profile data file 'gmon.out', you can run 'gprof' to
+interpret the information in it.  The 'gprof' program prints a flat
 profile and a call graph on standard output.  Typically you would
-redirect the output of `gprof' into a file with `>'.
+redirect the output of 'gprof' into a file with '>'.
 
-   You run `gprof' like this:
+   You run 'gprof' like this:
 
      gprof OPTIONS [EXECUTABLE-FILE [PROFILE-DATA-FILES...]] [> OUTFILE]
 
 Here square-brackets indicate optional arguments.
 
-   If you omit the executable file name, the file `a.out' is used.  If
-you give no profile data file name, the file `gmon.out' is used.  If
-any file is not in the proper format, or if the profile data file does
-not appear to belong to the executable file, an error message is
-printed.
+   If you omit the executable file name, the file 'a.out' is used.  If
+you give no profile data file name, the file 'gmon.out' is used.  If any
+file is not in the proper format, or if the profile data file does not
+appear to belong to the executable file, an error message is printed.
 
    You can give more than one profile data file by entering all their
 names after the executable file name; then the statistics in all the
@@ -285,8 +281,8 @@ data files are summed together.
 
 * Menu:
 
-* Output Options::      Controlling `gprof''s output style
-* Analysis Options::    Controlling how `gprof' analyzes its data
+* Output Options::      Controlling 'gprof''s output style
+* Analysis Options::    Controlling how 'gprof' analyzes its data
 * Miscellaneous Options::
 * Deprecated Options::  Options you no longer need to use, but which
                             have been retained for compatibility
@@ -298,117 +294,117 @@ File: gprof.info,  Node: Output Options,  Next: Analysis Options,  Up: Invoking
 4.1 Output Options
 ==================
 
-These options specify which of several output formats `gprof' should
+These options specify which of several output formats 'gprof' should
 produce.
 
-   Many of these options take an optional "symspec" to specify
-functions to be included or excluded.  These options can be specified
-multiple times, with different symspecs, to include or exclude sets of
-symbols.  *Note Symspecs: Symspecs.
+   Many of these options take an optional "symspec" to specify functions
+to be included or excluded.  These options can be specified multiple
+times, with different symspecs, to include or exclude sets of symbols.
+*Note Symspecs: Symspecs.
 
-   Specifying any of these options overrides the default (`-p -q'),
+   Specifying any of these options overrides the default ('-p -q'),
 which prints a flat profile and call graph analysis for all functions.
 
-`-A[SYMSPEC]'
-`--annotated-source[=SYMSPEC]'
-     The `-A' option causes `gprof' to print annotated source code.  If
+'-A[SYMSPEC]'
+'--annotated-source[=SYMSPEC]'
+     The '-A' option causes 'gprof' to print annotated source code.  If
      SYMSPEC is specified, print output only for matching symbols.
      *Note The Annotated Source Listing: Annotated Source.
 
-`-b'
-`--brief'
-     If the `-b' option is given, `gprof' doesn't print the verbose
+'-b'
+'--brief'
+     If the '-b' option is given, 'gprof' doesn't print the verbose
      blurbs that try to explain the meaning of all of the fields in the
      tables.  This is useful if you intend to print out the output, or
      are tired of seeing the blurbs.
 
-`-C[SYMSPEC]'
-`--exec-counts[=SYMSPEC]'
-     The `-C' option causes `gprof' to print a tally of functions and
+'-C[SYMSPEC]'
+'--exec-counts[=SYMSPEC]'
+     The '-C' option causes 'gprof' to print a tally of functions and
      the number of times each was called.  If SYMSPEC is specified,
      print tally only for matching symbols.
 
      If the profile data file contains basic-block count records,
-     specifying the `-l' option, along with `-C', will cause basic-block
+     specifying the '-l' option, along with '-C', will cause basic-block
      execution counts to be tallied and displayed.
 
-`-i'
-`--file-info'
-     The `-i' option causes `gprof' to display summary information
-     about the profile data file(s) and then exit.  The number of
-     histogram, call graph, and basic-block count records is displayed.
+'-i'
+'--file-info'
+     The '-i' option causes 'gprof' to display summary information about
+     the profile data file(s) and then exit.  The number of histogram,
+     call graph, and basic-block count records is displayed.
 
-`-I DIRS'
-`--directory-path=DIRS'
-     The `-I' option specifies a list of search directories in which to
+'-I DIRS'
+'--directory-path=DIRS'
+     The '-I' option specifies a list of search directories in which to
      find source files.  Environment variable GPROF_PATH can also be
      used to convey this information.  Used mostly for annotated source
      output.
 
-`-J[SYMSPEC]'
-`--no-annotated-source[=SYMSPEC]'
-     The `-J' option causes `gprof' not to print annotated source code.
-     If SYMSPEC is specified, `gprof' prints annotated source, but
+'-J[SYMSPEC]'
+'--no-annotated-source[=SYMSPEC]'
+     The '-J' option causes 'gprof' not to print annotated source code.
+     If SYMSPEC is specified, 'gprof' prints annotated source, but
      excludes matching symbols.
 
-`-L'
-`--print-path'
+'-L'
+'--print-path'
      Normally, source filenames are printed with the path component
-     suppressed.  The `-L' option causes `gprof' to print the full
+     suppressed.  The '-L' option causes 'gprof' to print the full
      pathname of source filenames, which is determined from symbolic
      debugging information in the image file and is relative to the
      directory in which the compiler was invoked.
 
-`-p[SYMSPEC]'
-`--flat-profile[=SYMSPEC]'
-     The `-p' option causes `gprof' to print a flat profile.  If
-     SYMSPEC is specified, print flat profile only for matching symbols.
-     *Note The Flat Profile: Flat Profile.
+'-p[SYMSPEC]'
+'--flat-profile[=SYMSPEC]'
+     The '-p' option causes 'gprof' to print a flat profile.  If SYMSPEC
+     is specified, print flat profile only for matching symbols.  *Note
+     The Flat Profile: Flat Profile.
 
-`-P[SYMSPEC]'
-`--no-flat-profile[=SYMSPEC]'
-     The `-P' option causes `gprof' to suppress printing a flat profile.
-     If SYMSPEC is specified, `gprof' prints a flat profile, but
+'-P[SYMSPEC]'
+'--no-flat-profile[=SYMSPEC]'
+     The '-P' option causes 'gprof' to suppress printing a flat profile.
+     If SYMSPEC is specified, 'gprof' prints a flat profile, but
      excludes matching symbols.
 
-`-q[SYMSPEC]'
-`--graph[=SYMSPEC]'
-     The `-q' option causes `gprof' to print the call graph analysis.
+'-q[SYMSPEC]'
+'--graph[=SYMSPEC]'
+     The '-q' option causes 'gprof' to print the call graph analysis.
      If SYMSPEC is specified, print call graph only for matching symbols
      and their children.  *Note The Call Graph: Call Graph.
 
-`-Q[SYMSPEC]'
-`--no-graph[=SYMSPEC]'
-     The `-Q' option causes `gprof' to suppress printing the call graph.
-     If SYMSPEC is specified, `gprof' prints a call graph, but excludes
+'-Q[SYMSPEC]'
+'--no-graph[=SYMSPEC]'
+     The '-Q' option causes 'gprof' to suppress printing the call graph.
+     If SYMSPEC is specified, 'gprof' prints a call graph, but excludes
      matching symbols.
 
-`-t'
-`--table-length=NUM'
-     The `-t' option causes the NUM most active source lines in each
+'-t'
+'--table-length=NUM'
+     The '-t' option causes the NUM most active source lines in each
      source file to be listed when source annotation is enabled.  The
      default is 10.
 
-`-y'
-`--separate-files'
+'-y'
+'--separate-files'
      This option affects annotated source output only.  Normally,
-     `gprof' prints annotated source files to standard-output.  If this
+     'gprof' prints annotated source files to standard-output.  If this
      option is specified, annotated source for a file named
-     `path/FILENAME' is generated in the file `FILENAME-ann'.  If the
-     underlying file system would truncate `FILENAME-ann' so that it
-     overwrites the original `FILENAME', `gprof' generates annotated
-     source in the file `FILENAME.ann' instead (if the original file
-     name has an extension, that extension is _replaced_ with `.ann').
-
-`-Z[SYMSPEC]'
-`--no-exec-counts[=SYMSPEC]'
-     The `-Z' option causes `gprof' not to print a tally of functions
+     'path/FILENAME' is generated in the file 'FILENAME-ann'.  If the
+     underlying file system would truncate 'FILENAME-ann' so that it
+     overwrites the original 'FILENAME', 'gprof' generates annotated
+     source in the file 'FILENAME.ann' instead (if the original file
+     name has an extension, that extension is _replaced_ with '.ann').
+
+'-Z[SYMSPEC]'
+'--no-exec-counts[=SYMSPEC]'
+     The '-Z' option causes 'gprof' not to print a tally of functions
      and the number of times each was called.  If SYMSPEC is specified,
      print tally, but exclude matching symbols.
 
-`-r'
-`--function-ordering'
-     The `--function-ordering' option causes `gprof' to print a
+'-r'
+'--function-ordering'
+     The '--function-ordering' option causes 'gprof' to print a
      suggested function ordering for the program based on profiling
      data.  This option suggests an ordering which may improve paging,
      tlb and cache behavior for the program on systems which support
@@ -418,19 +414,19 @@ which prints a flat profile and call graph analysis for all functions.
      a particular order is system dependent and out of the scope of this
      manual.
 
-`-R MAP_FILE'
-`--file-ordering MAP_FILE'
-     The `--file-ordering' option causes `gprof' to print a suggested
-     .o link line ordering for the program based on profiling data.
-     This option suggests an ordering which may improve paging, tlb and
-     cache behavior for the program on systems which do not support
-     arbitrary ordering of functions in an executable.
+'-R MAP_FILE'
+'--file-ordering MAP_FILE'
+     The '--file-ordering' option causes 'gprof' to print a suggested .o
+     link line ordering for the program based on profiling data.  This
+     option suggests an ordering which may improve paging, tlb and cache
+     behavior for the program on systems which do not support arbitrary
+     ordering of functions in an executable.
 
-     Use of the `-a' argument is highly recommended with this option.
+     Use of the '-a' argument is highly recommended with this option.
 
      The MAP_FILE argument is a pathname to a file which provides
      function name to object file mappings.  The format of the file is
-     similar to the output of the program `nm'.
+     similar to the output of the program 'nm'.
 
           c-parse.o:00000000 T yyparse
           c-parse.o:00000004 C yyerrflag
@@ -441,32 +437,32 @@ which prints a flat profile and call graph analysis for all functions.
           c-decl.o:00000000 T print_lang_type
           ...
 
-     To create a MAP_FILE with GNU `nm', type a command like `nm
+     To create a MAP_FILE with GNU 'nm', type a command like 'nm
      --extern-only --defined-only -v --print-file-name program-name'.
 
-`-T'
-`--traditional'
-     The `-T' option causes `gprof' to print its output in
-     "traditional" BSD style.
+'-T'
+'--traditional'
+     The '-T' option causes 'gprof' to print its output in "traditional"
+     BSD style.
 
-`-w WIDTH'
-`--width=WIDTH'
+'-w WIDTH'
+'--width=WIDTH'
      Sets width of output lines to WIDTH.  Currently only used when
      printing the function index at the bottom of the call graph.
 
-`-x'
-`--all-lines'
-     This option affects annotated source output only.  By default,
-     only the lines at the beginning of a basic-block are annotated.
-     If this option is specified, every line in a basic-block is
-     annotated by repeating the annotation for the first line.  This
-     behavior is similar to `tcov''s `-a'.
+'-x'
+'--all-lines'
+     This option affects annotated source output only.  By default, only
+     the lines at the beginning of a basic-block are annotated.  If this
+     option is specified, every line in a basic-block is annotated by
+     repeating the annotation for the first line.  This behavior is
+     similar to 'tcov''s '-a'.
 
-`--demangle[=STYLE]'
-`--no-demangle'
+'--demangle[=STYLE]'
+'--no-demangle'
      These options control whether C++ symbol names should be demangled
      when printing output.  The default is to demangle symbols.  The
-     `--no-demangle' option may be used to turn off demangling.
+     '--no-demangle' option may be used to turn off demangling.
      Different compilers have different mangling styles.  The optional
      demangling style argument can be used to choose an appropriate
      demangling style for your compiler.
@@ -477,87 +473,86 @@ File: gprof.info,  Node: Analysis Options,  Next: Miscellaneous Options,  Prev:
 4.2 Analysis Options
 ====================
 
-`-a'
-`--no-static'
-     The `-a' option causes `gprof' to suppress the printing of
+'-a'
+'--no-static'
+     The '-a' option causes 'gprof' to suppress the printing of
      statically declared (private) functions.  (These are functions
      whose names are not listed as global, and which are not visible
      outside the file/function/block where they were defined.)  Time
      spent in these functions, calls to/from them, etc., will all be
      attributed to the function that was loaded directly before it in
-     the executable file.  This option affects both the flat profile
-     and the call graph.
+     the executable file.  This option affects both the flat profile and
+     the call graph.
 
-`-c'
-`--static-call-graph'
-     The `-c' option causes the call graph of the program to be
+'-c'
+'--static-call-graph'
+     The '-c' option causes the call graph of the program to be
      augmented by a heuristic which examines the text space of the
      object file and identifies function calls in the binary machine
      code.  Since normal call graph records are only generated when
      functions are entered, this option identifies children that could
-     have been called, but never were.  Calls to functions that were
-     not compiled with profiling enabled are also identified, but only
-     if symbol table entries are present for them.  Calls to dynamic
-     library routines are typically _not_ found by this option.
-     Parents or children identified via this heuristic are indicated in
-     the call graph with call counts of `0'.
-
-`-D'
-`--ignore-non-functions'
-     The `-D' option causes `gprof' to ignore symbols which are not
-     known to be functions.  This option will give more accurate
-     profile data on systems where it is supported (Solaris and HPUX for
+     have been called, but never were.  Calls to functions that were not
+     compiled with profiling enabled are also identified, but only if
+     symbol table entries are present for them.  Calls to dynamic
+     library routines are typically _not_ found by this option.  Parents
+     or children identified via this heuristic are indicated in the call
+     graph with call counts of '0'.
+
+'-D'
+'--ignore-non-functions'
+     The '-D' option causes 'gprof' to ignore symbols which are not
+     known to be functions.  This option will give more accurate profile
+     data on systems where it is supported (Solaris and HPUX for
      example).
 
-`-k FROM/TO'
-     The `-k' option allows you to delete from the call graph any arcs
+'-k FROM/TO'
+     The '-k' option allows you to delete from the call graph any arcs
      from symbols matching symspec FROM to those matching symspec TO.
 
-`-l'
-`--line'
-     The `-l' option enables line-by-line profiling, which causes
+'-l'
+'--line'
+     The '-l' option enables line-by-line profiling, which causes
      histogram hits to be charged to individual source code lines,
      instead of functions.  This feature only works with programs
-     compiled by older versions of the `gcc' compiler.  Newer versions
-     of `gcc' are designed to work with the `gcov' tool instead.
-
-     If the program was compiled with basic-block counting enabled,
-     this option will also identify how many times each line of code
-     was executed.  While line-by-line profiling can help isolate where
-     in a large function a program is spending its time, it also
-     significantly increases the running time of `gprof', and magnifies
+     compiled by older versions of the 'gcc' compiler.  Newer versions
+     of 'gcc' are designed to work with the 'gcov' tool instead.
+
+     If the program was compiled with basic-block counting enabled, this
+     option will also identify how many times each line of code was
+     executed.  While line-by-line profiling can help isolate where in a
+     large function a program is spending its time, it also
+     significantly increases the running time of 'gprof', and magnifies
      statistical inaccuracies.  *Note Statistical Sampling Error:
      Sampling Error.
 
-`-m NUM'
-`--min-count=NUM'
+'-m NUM'
+'--min-count=NUM'
      This option affects execution count output only.  Symbols that are
      executed less than NUM times are suppressed.
 
-`-nSYMSPEC'
-`--time=SYMSPEC'
-     The `-n' option causes `gprof', in its call graph analysis, to
-     only propagate times for symbols matching SYMSPEC.
+'-nSYMSPEC'
+'--time=SYMSPEC'
+     The '-n' option causes 'gprof', in its call graph analysis, to only
+     propagate times for symbols matching SYMSPEC.
 
-`-NSYMSPEC'
-`--no-time=SYMSPEC'
-     The `-n' option causes `gprof', in its call graph analysis, not to
+'-NSYMSPEC'
+'--no-time=SYMSPEC'
+     The '-n' option causes 'gprof', in its call graph analysis, not to
      propagate times for symbols matching SYMSPEC.
 
-`-SFILENAME'
-`--external-symbol-table=FILENAME'
-     The `-S' option causes `gprof' to read an external symbol table
-     file, such as `/proc/kallsyms', rather than read the symbol table
-     from the given object file (the default is `a.out'). This is useful
-     for profiling kernel modules.
+'-SFILENAME'
+'--external-symbol-table=FILENAME'
+     The '-S' option causes 'gprof' to read an external symbol table
+     file, such as '/proc/kallsyms', rather than read the symbol table
+     from the given object file (the default is 'a.out').  This is
+     useful for profiling kernel modules.
 
-`-z'
-`--display-unused-functions'
-     If you give the `-z' option, `gprof' will mention all functions in
+'-z'
+'--display-unused-functions'
+     If you give the '-z' option, 'gprof' will mention all functions in
      the flat profile, even those that were never called, and that had
-     no time spent in them.  This is useful in conjunction with the
-     `-c' option for discovering which routines were never called.
-
+     no time spent in them.  This is useful in conjunction with the '-c'
+     option for discovering which routines were never called.
 
 
 File: gprof.info,  Node: Miscellaneous Options,  Next: Deprecated Options,  Prev: Analysis Options,  Up: Invoking
@@ -565,40 +560,39 @@ File: gprof.info,  Node: Miscellaneous Options,  Next: Deprecated Options,  Prev
 4.3 Miscellaneous Options
 =========================
 
-`-d[NUM]'
-`--debug[=NUM]'
-     The `-d NUM' option specifies debugging options.  If NUM is not
-     specified, enable all debugging.  *Note Debugging `gprof':
+'-d[NUM]'
+'--debug[=NUM]'
+     The '-d NUM' option specifies debugging options.  If NUM is not
+     specified, enable all debugging.  *Note Debugging 'gprof':
      Debugging.
 
-`-h'
-`--help'
-     The `-h' option prints command line usage.
+'-h'
+'--help'
+     The '-h' option prints command line usage.
 
-`-ONAME'
-`--file-format=NAME'
+'-ONAME'
+'--file-format=NAME'
      Selects the format of the profile data files.  Recognized formats
-     are `auto' (the default), `bsd', `4.4bsd', `magic', and `prof'
-     (not yet supported).
+     are 'auto' (the default), 'bsd', '4.4bsd', 'magic', and 'prof' (not
+     yet supported).
 
-`-s'
-`--sum'
-     The `-s' option causes `gprof' to summarize the information in the
+'-s'
+'--sum'
+     The '-s' option causes 'gprof' to summarize the information in the
      profile data files it read in, and write out a profile data file
-     called `gmon.sum', which contains all the information from the
-     profile data files that `gprof' read in.  The file `gmon.sum' may
-     be one of the specified input files; the effect of this is to
-     merge the data in the other input files into `gmon.sum'.
+     called 'gmon.sum', which contains all the information from the
+     profile data files that 'gprof' read in.  The file 'gmon.sum' may
+     be one of the specified input files; the effect of this is to merge
+     the data in the other input files into 'gmon.sum'.
 
-     Eventually you can run `gprof' again without `-s' to analyze the
-     cumulative data in the file `gmon.sum'.
+     Eventually you can run 'gprof' again without '-s' to analyze the
+     cumulative data in the file 'gmon.sum'.
 
-`-v'
-`--version'
-     The `-v' flag causes `gprof' to print the current version number,
+'-v'
+'--version'
+     The '-v' flag causes 'gprof' to print the current version number,
      and then exit.
 
-
 
 File: gprof.info,  Node: Deprecated Options,  Next: Symspecs,  Prev: Miscellaneous Options,  Up: Invoking
 
@@ -607,45 +601,43 @@ File: gprof.info,  Node: Deprecated Options,  Next: Symspecs,  Prev: Miscellaneo
 
 These options have been replaced with newer versions that use symspecs.
 
-`-e FUNCTION_NAME'
-     The `-e FUNCTION' option tells `gprof' to not print information
+'-e FUNCTION_NAME'
+     The '-e FUNCTION' option tells 'gprof' to not print information
      about the function FUNCTION_NAME (and its children...) in the call
      graph.  The function will still be listed as a child of any
-     functions that call it, but its index number will be shown as
-     `[not printed]'.  More than one `-e' option may be given; only one
-     FUNCTION_NAME may be indicated with each `-e' option.
-
-`-E FUNCTION_NAME'
-     The `-E FUNCTION' option works like the `-e' option, but time
-     spent in the function (and children who were not called from
-     anywhere else), will not be used to compute the
-     percentages-of-time for the call graph.  More than one `-E' option
-     may be given; only one FUNCTION_NAME may be indicated with each
-     `-E' option.
-
-`-f FUNCTION_NAME'
-     The `-f FUNCTION' option causes `gprof' to limit the call graph to
+     functions that call it, but its index number will be shown as '[not
+     printed]'.  More than one '-e' option may be given; only one
+     FUNCTION_NAME may be indicated with each '-e' option.
+
+'-E FUNCTION_NAME'
+     The '-E FUNCTION' option works like the '-e' option, but time spent
+     in the function (and children who were not called from anywhere
+     else), will not be used to compute the percentages-of-time for the
+     call graph.  More than one '-E' option may be given; only one
+     FUNCTION_NAME may be indicated with each '-E' option.
+
+'-f FUNCTION_NAME'
+     The '-f FUNCTION' option causes 'gprof' to limit the call graph to
      the function FUNCTION_NAME and its children (and their
-     children...).  More than one `-f' option may be given; only one
-     FUNCTION_NAME may be indicated with each `-f' option.
-
-`-F FUNCTION_NAME'
-     The `-F FUNCTION' option works like the `-f' option, but only time
-     spent in the function and its children (and their children...)
-     will be used to determine total-time and percentages-of-time for
-     the call graph.  More than one `-F' option may be given; only one
-     FUNCTION_NAME may be indicated with each `-F' option.  The `-F'
-     option overrides the `-E' option.
-
-
-   Note that only one function can be specified with each `-e', `-E',
-`-f' or `-F' option.  To specify more than one function, use multiple
+     children...).  More than one '-f' option may be given; only one
+     FUNCTION_NAME may be indicated with each '-f' option.
+
+'-F FUNCTION_NAME'
+     The '-F FUNCTION' option works like the '-f' option, but only time
+     spent in the function and its children (and their children...) will
+     be used to determine total-time and percentages-of-time for the
+     call graph.  More than one '-F' option may be given; only one
+     FUNCTION_NAME may be indicated with each '-F' option.  The '-F'
+     option overrides the '-E' option.
+
+   Note that only one function can be specified with each '-e', '-E',
+'-f' or '-F' option.  To specify more than one function, use multiple
 options.  For example, this command:
 
      gprof -e boring -f foo -f bar myprogram > gprof.output
 
 lists in the call graph all functions that were reached from either
-`foo' or `bar' and were not reachable from `boring'.
+'foo' or 'bar' and were not reachable from 'boring'.
 
 
 File: gprof.info,  Node: Symspecs,  Prev: Deprecated Options,  Up: Invoking
@@ -664,15 +656,15 @@ syntax:
 
    Here are some sample symspecs:
 
-`main.c'
-     Selects everything in file `main.c'--the dot in the string tells
-     `gprof' to interpret the string as a filename, rather than as a
-     function name.  To select a file whose name does not contain a
-     dot, a trailing colon should be specified.  For example, `odd:' is
-     interpreted as the file named `odd'.
+'main.c'
+     Selects everything in file 'main.c'--the dot in the string tells
+     'gprof' to interpret the string as a filename, rather than as a
+     function name.  To select a file whose name does not contain a dot,
+     a trailing colon should be specified.  For example, 'odd:' is
+     interpreted as the file named 'odd'.
 
-`main'
-     Selects all functions named `main'.
+'main'
+     Selects all functions named 'main'.
 
      Note that there may be multiple instances of the same function name
      because some of the definitions may be local (i.e., static).
@@ -681,29 +673,29 @@ syntax:
      specific source file.
 
      Sometimes, function names contain dots.  In such cases, it is
-     necessary to add a leading colon to the name.  For example,
-     `:.mul' selects function `.mul'.
+     necessary to add a leading colon to the name.  For example, ':.mul'
+     selects function '.mul'.
 
      In some object file formats, symbols have a leading underscore.
-     `gprof' will normally not print these underscores.  When you name a
-     symbol in a symspec, you should type it exactly as `gprof' prints
+     'gprof' will normally not print these underscores.  When you name a
+     symbol in a symspec, you should type it exactly as 'gprof' prints
      it in its output.  For example, if the compiler produces a symbol
-     `_main' from your `main' function, `gprof' still prints it as
-     `main' in its output, so you should use `main' in symspecs.
+     '_main' from your 'main' function, 'gprof' still prints it as
+     'main' in its output, so you should use 'main' in symspecs.
 
-`main.c:main'
-     Selects function `main' in file `main.c'.
+'main.c:main'
+     Selects function 'main' in file 'main.c'.
 
-`main.c:134'
-     Selects line 134 in file `main.c'.
+'main.c:134'
+     Selects line 134 in file 'main.c'.
 
 
 File: gprof.info,  Node: Output,  Next: Inaccuracy,  Prev: Invoking,  Up: Top
 
-5 Interpreting `gprof''s Output
+5 Interpreting 'gprof''s Output
 *******************************
 
-`gprof' can produce several different output styles, the most important
+'gprof' can produce several different output styles, the most important
 of which are described below.  The simplest output styles (file
 information, execution count, and function and file ordering) are not
 described here, but are documented with the respective options that
@@ -716,7 +708,7 @@ trigger them.  *Note Output Options: Output Options.
 * Call Graph::          The call graph shows which functions called which
                             others, and how much time each function used
                             when its subroutine calls are included.
-* Line-by-line::        `gprof' can analyze individual source code lines
+* Line-by-line::        'gprof' can analyze individual source code lines
 * Annotated Source::    The annotated source listing displays source code
                             labeled with execution counts
 
@@ -727,7 +719,7 @@ File: gprof.info,  Node: Flat Profile,  Next: Call Graph,  Up: Output
 ====================
 
 The "flat profile" shows the total amount of time your program spent
-executing each function.  Unless the `-z' option is given, functions
+executing each function.  Unless the '-z' option is given, functions
 with no apparent time spent in them, and no apparent calls to them, are
 not mentioned.  Note that if a function was not compiled for profiling,
 and didn't run long enough to show up on the program counter histogram,
@@ -758,7 +750,7 @@ it will be indistinguishable from a function that was never called.
 
 The functions are sorted first by decreasing run-time spent in them,
 then by decreasing number of calls, then alphabetically by name.  The
-functions `mcount' and `profil' are part of the profiling apparatus and
+functions 'mcount' and 'profil' are part of the profiling apparatus and
 appear in every flat profile; their time gives a measure of the amount
 of overhead due to profiling.
 
@@ -768,59 +760,59 @@ margin of error in each of the time figures.  A time figure that is not
 much larger than this is not reliable.  In this example, each sample
 counted as 0.01 seconds, suggesting a 100 Hz sampling rate.  The
 program's total execution time was 0.06 seconds, as indicated by the
-`cumulative seconds' field.  Since each sample counted for 0.01
-seconds, this means only six samples were taken during the run.  Two of
-the samples occurred while the program was in the `open' function, as
-indicated by the `self seconds' field.  Each of the other four samples
-occurred one each in `offtime', `memccpy', `write', and `mcount'.
-Since only six samples were taken, none of these values can be regarded
-as particularly reliable.  In another run, the `self seconds' field for
-`mcount' might well be `0.00' or `0.02'.  *Note Statistical Sampling
+'cumulative seconds' field.  Since each sample counted for 0.01 seconds,
+this means only six samples were taken during the run.  Two of the
+samples occurred while the program was in the 'open' function, as
+indicated by the 'self seconds' field.  Each of the other four samples
+occurred one each in 'offtime', 'memccpy', 'write', and 'mcount'.  Since
+only six samples were taken, none of these values can be regarded as
+particularly reliable.  In another run, the 'self seconds' field for
+'mcount' might well be '0.00' or '0.02'.  *Note Statistical Sampling
 Error: Sampling Error, for a complete discussion.
 
-   The remaining functions in the listing (those whose `self seconds'
-field is `0.00') didn't appear in the histogram samples at all.
+   The remaining functions in the listing (those whose 'self seconds'
+field is '0.00') didn't appear in the histogram samples at all.
 However, the call graph indicated that they were called, so therefore
-they are listed, sorted in decreasing order by the `calls' field.
+they are listed, sorted in decreasing order by the 'calls' field.
 Clearly some time was spent executing these functions, but the paucity
 of histogram samples prevents any determination of how much time each
 took.
 
    Here is what the fields in each line mean:
 
-`% time'
+'% time'
      This is the percentage of the total execution time your program
      spent in this function.  These should all add up to 100%.
 
-`cumulative seconds'
+'cumulative seconds'
      This is the cumulative total number of seconds the computer spent
      executing this functions, plus the time spent in all the functions
      above this one in this table.
 
-`self seconds'
+'self seconds'
      This is the number of seconds accounted for by this function alone.
      The flat profile listing is sorted first by this number.
 
-`calls'
+'calls'
      This is the total number of times the function was called.  If the
      function was never called, or the number of times it was called
      cannot be determined (probably because the function was not
      compiled with profiling enabled), the "calls" field is blank.
 
-`self ms/call'
+'self ms/call'
      This represents the average number of milliseconds spent in this
      function per call, if this function is profiled.  Otherwise, this
      field is blank for this function.
 
-`total ms/call'
+'total ms/call'
      This represents the average number of milliseconds spent in this
      function and its descendants per call, if this function is
      profiled.  Otherwise, this field is blank for this function.  This
      is the only field in the flat profile that uses call graph
      analysis.
 
-`name'
-     This is the name of the function.   The flat profile is sorted by
+'name'
+     This is the name of the function.  The flat profile is sorted by
      this field alphabetically after the "self seconds" and "calls"
      fields are sorted.
 
@@ -832,11 +824,11 @@ File: gprof.info,  Node: Call Graph,  Next: Line-by-line,  Prev: Flat Profile,
 
 The "call graph" shows how much time was spent in each function and its
 children.  From this information, you can find functions that, while
-they themselves may not have used much time, called other functions
-that did use unusual amounts of time.
+they themselves may not have used much time, called other functions that
+did use unusual amounts of time.
 
    Here is a sample call from a small program.  This call came from the
-same `gprof' run as the flat profile example in the previous section.
+same 'gprof' run as the flat profile example in the previous section.
 
      granularity: each sample hit covers 2 byte(s) for 20.00% of 0.05 seconds
 
@@ -871,15 +863,15 @@ same `gprof' run as the flat profile example in the previous section.
 each function.  Each entry has one or more lines.
 
    In each entry, the primary line is the one that starts with an index
-number in square brackets.  The end of this line says which function
-the entry is for.  The preceding lines in the entry describe the
-callers of this function and the following lines describe its
-subroutines (also called "children" when we speak of the call graph).
+number in square brackets.  The end of this line says which function the
+entry is for.  The preceding lines in the entry describe the callers of
+this function and the following lines describe its subroutines (also
+called "children" when we speak of the call graph).
 
    The entries are sorted by time spent in the function and its
 subroutines.
 
-   The internal profiling function `mcount' (*note The Flat Profile:
+   The internal profiling function 'mcount' (*note The Flat Profile:
 Flat Profile.) is never mentioned in the call graph.
 
 * Menu:
@@ -888,7 +880,7 @@ Flat Profile.) is never mentioned in the call graph.
 * Callers::       Details of caller-lines' contents.
 * Subroutines::   Details of subroutine-lines' contents.
 * Cycles::        When there are cycles of recursion,
-                   such as `a' calls `b' calls `a'...
+                   such as 'a' calls 'b' calls 'a'...
 
 
 File: gprof.info,  Node: Primary,  Next: Callers,  Up: Call Graph
@@ -901,7 +893,7 @@ function which the entry is about and gives the overall statistics for
 this function.
 
    For reference, we repeat the primary line from the entry for function
-`report' in our main example, together with the heading line that shows
+'report' in our main example, together with the heading line that shows
 the names of the fields:
 
      index  % time    self  children called     name
@@ -910,7 +902,7 @@ the names of the fields:
 
    Here is what the fields in the primary line mean:
 
-`index'
+'index'
      Entries are numbered with consecutive integers.  Each function
      therefore has an index number, which appears at the beginning of
      its primary line.
@@ -920,7 +912,7 @@ the names of the fields:
      number guides you if you wish to look for the entry for that
      function.
 
-`% time'
+'% time'
      This is the percentage of the total time that was spent in this
      function, including time spent in subroutines called from this
      function.
@@ -929,35 +921,35 @@ the names of the fields:
      this function.  Therefore, adding up these percentages is
      meaningless.
 
-`self'
+'self'
      This is the total amount of time spent in this function.  This
-     should be identical to the number printed in the `seconds' field
+     should be identical to the number printed in the 'seconds' field
      for this function in the flat profile.
 
-`children'
-     This is the total amount of time spent in the subroutine calls
-     made by this function.  This should be equal to the sum of all the
-     `self' and `children' entries of the children listed directly
-     below this function.
+'children'
+     This is the total amount of time spent in the subroutine calls made
+     by this function.  This should be equal to the sum of all the
+     'self' and 'children' entries of the children listed directly below
+     this function.
 
-`called'
+'called'
      This is the number of times the function was called.
 
      If the function called itself recursively, there are two numbers,
-     separated by a `+'.  The first number counts non-recursive calls,
+     separated by a '+'.  The first number counts non-recursive calls,
      and the second counts recursive calls.
 
-     In the example above, the function `report' was called once from
-     `main'.
+     In the example above, the function 'report' was called once from
+     'main'.
 
-`name'
+'name'
      This is the name of the current function.  The index number is
      repeated after it.
 
      If the function is part of a cycle of recursion, the cycle number
      is printed between the function's name and the index number (*note
      How Mutually Recursive Functions Are Described: Cycles.).  For
-     example, if function `gnurr' is part of cycle number one, and has
+     example, if function 'gnurr' is part of cycle number one, and has
      index number twelve, its primary line would be end like this:
 
           gnurr <cycle 1> [12]
@@ -968,12 +960,12 @@ File: gprof.info,  Node: Callers,  Next: Subroutines,  Prev: Primary,  Up: Call
 5.2.2 Lines for a Function's Callers
 ------------------------------------
 
-A function's entry has a line for each function it was called by.
-These lines' fields correspond to the fields of the primary line, but
-their meanings are different because of the difference in context.
+A function's entry has a line for each function it was called by.  These
+lines' fields correspond to the fields of the primary line, but their
+meanings are different because of the difference in context.
 
    For reference, we repeat two lines from the entry for the function
-`report', the primary line and one caller-line preceding it, together
+'report', the primary line and one caller-line preceding it, together
 with the heading line that shows the names of the fields:
 
      index  % time    self  children called     name
@@ -981,31 +973,31 @@ with the heading line that shows the names of the fields:
                      0.00    0.05       1/1           main [2]
      [3]    100.0    0.00    0.05       1         report [3]
 
-   Here are the meanings of the fields in the caller-line for `report'
-called from `main':
+   Here are the meanings of the fields in the caller-line for 'report'
+called from 'main':
 
-`self'
-     An estimate of the amount of time spent in `report' itself when it
-     was called from `main'.
+'self'
+     An estimate of the amount of time spent in 'report' itself when it
+     was called from 'main'.
 
-`children'
-     An estimate of the amount of time spent in subroutines of `report'
-     when `report' was called from `main'.
+'children'
+     An estimate of the amount of time spent in subroutines of 'report'
+     when 'report' was called from 'main'.
 
-     The sum of the `self' and `children' fields is an estimate of the
-     amount of time spent within calls to `report' from `main'.
+     The sum of the 'self' and 'children' fields is an estimate of the
+     amount of time spent within calls to 'report' from 'main'.
 
-`called'
-     Two numbers: the number of times `report' was called from `main',
-     followed by the total number of non-recursive calls to `report'
+'called'
+     Two numbers: the number of times 'report' was called from 'main',
+     followed by the total number of non-recursive calls to 'report'
      from all its callers.
 
-`name and index number'
-     The name of the caller of `report' to which this line applies,
+'name and index number'
+     The name of the caller of 'report' to which this line applies,
      followed by the caller's index number.
 
      Not all functions have entries in the call graph; some options to
-     `gprof' request the omission of certain functions.  When a caller
+     'gprof' request the omission of certain functions.  When a caller
      has no entry of its own, it still has caller-lines in the entries
      of the functions it calls.
 
@@ -1013,7 +1005,7 @@ called from `main':
      printed between the name and the index number.
 
    If the identity of the callers of a function cannot be determined, a
-dummy caller-line is printed which has `<spontaneous>' as the "caller's
+dummy caller-line is printed which has '<spontaneous>' as the "caller's
 name" and all other fields blank.  This can happen for signal handlers.
 
 
@@ -1028,7 +1020,7 @@ fields correspond to the fields of the primary line, but their meanings
 are different because of the difference in context.
 
    For reference, we repeat two lines from the entry for the function
-`main', the primary line and a line for a subroutine, together with the
+'main', the primary line and a line for a subroutine, together with the
 heading line that shows the names of the fields:
 
      index  % time    self  children called     name
@@ -1036,29 +1028,29 @@ heading line that shows the names of the fields:
      [2]    100.0    0.00    0.05       1         main [2]
                      0.00    0.05       1/1           report [3]
 
-   Here are the meanings of the fields in the subroutine-line for `main'
-calling `report':
+   Here are the meanings of the fields in the subroutine-line for 'main'
+calling 'report':
 
-`self'
-     An estimate of the amount of time spent directly within `report'
-     when `report' was called from `main'.
+'self'
+     An estimate of the amount of time spent directly within 'report'
+     when 'report' was called from 'main'.
 
-`children'
-     An estimate of the amount of time spent in subroutines of `report'
-     when `report' was called from `main'.
+'children'
+     An estimate of the amount of time spent in subroutines of 'report'
+     when 'report' was called from 'main'.
 
-     The sum of the `self' and `children' fields is an estimate of the
-     total time spent in calls to `report' from `main'.
+     The sum of the 'self' and 'children' fields is an estimate of the
+     total time spent in calls to 'report' from 'main'.
 
-`called'
-     Two numbers, the number of calls to `report' from `main' followed
-     by the total number of non-recursive calls to `report'.  This
-     ratio is used to determine how much of `report''s `self' and
-     `children' time gets credited to `main'.  *Note Estimating
-     `children' Times: Assumptions.
+'called'
+     Two numbers, the number of calls to 'report' from 'main' followed
+     by the total number of non-recursive calls to 'report'.  This ratio
+     is used to determine how much of 'report''s 'self' and 'children'
+     time gets credited to 'main'.  *Note Estimating 'children' Times:
+     Assumptions.
 
-`name'
-     The name of the subroutine of `main' to which this line applies,
+'name'
+     The name of the subroutine of 'main' to which this line applies,
      followed by the subroutine's index number.
 
      If the caller is part of a recursion cycle, the cycle number is
@@ -1070,40 +1062,40 @@ File: gprof.info,  Node: Cycles,  Prev: Subroutines,  Up: Call Graph
 5.2.4 How Mutually Recursive Functions Are Described
 ----------------------------------------------------
 
-The graph may be complicated by the presence of "cycles of recursion"
-in the call graph.  A cycle exists if a function calls another function
+The graph may be complicated by the presence of "cycles of recursion" in
+the call graph.  A cycle exists if a function calls another function
 that (directly or indirectly) calls (or appears to call) the original
-function.  For example: if `a' calls `b', and `b' calls `a', then `a'
-and `b' form a cycle.
+function.  For example: if 'a' calls 'b', and 'b' calls 'a', then 'a'
+and 'b' form a cycle.
 
    Whenever there are call paths both ways between a pair of functions,
-they belong to the same cycle.  If `a' and `b' call each other and `b'
-and `c' call each other, all three make one cycle.  Note that even if
-`b' only calls `a' if it was not called from `a', `gprof' cannot
-determine this, so `a' and `b' are still considered a cycle.
+they belong to the same cycle.  If 'a' and 'b' call each other and 'b'
+and 'c' call each other, all three make one cycle.  Note that even if
+'b' only calls 'a' if it was not called from 'a', 'gprof' cannot
+determine this, so 'a' and 'b' are still considered a cycle.
 
    The cycles are numbered with consecutive integers.  When a function
 belongs to a cycle, each time the function name appears in the call
-graph it is followed by `<cycle NUMBER>'.
+graph it is followed by '<cycle NUMBER>'.
 
    The reason cycles matter is that they make the time values in the
-call graph paradoxical.  The "time spent in children" of `a' should
-include the time spent in its subroutine `b' and in `b''s
-subroutines--but one of `b''s subroutines is `a'!  How much of `a''s
-time should be included in the children of `a', when `a' is indirectly
+call graph paradoxical.  The "time spent in children" of 'a' should
+include the time spent in its subroutine 'b' and in 'b''s
+subroutines--but one of 'b''s subroutines is 'a'!  How much of 'a''s
+time should be included in the children of 'a', when 'a' is indirectly
 recursive?
 
-   The way `gprof' resolves this paradox is by creating a single entry
+   The way 'gprof' resolves this paradox is by creating a single entry
 for the cycle as a whole.  The primary line of this entry describes the
 total time spent directly in the functions of the cycle.  The
 "subroutines" of the cycle are the individual functions of the cycle,
 and all other functions that were called directly by them.  The
-"callers" of the cycle are the functions, outside the cycle, that
-called functions in the cycle.
+"callers" of the cycle are the functions, outside the cycle, that called
+functions in the cycle.
 
    Here is an example portion of a call graph which shows a cycle
-containing functions `a' and `b'.  The cycle was entered by a call to
-`a' from `main'; both `a' and `b' called `c'.
+containing functions 'a' and 'b'.  The cycle was entered by a call to
+'a' from 'main'; both 'a' and 'b' called 'c'.
 
      index  % time    self  children called     name
      ----------------------------------------
@@ -1125,8 +1117,8 @@ containing functions `a' and `b'.  The cycle was entered by a call to
      ----------------------------------------
 
 (The entire call graph for this program contains in addition an entry
-for `main', which calls `a', and an entry for `c', with callers `a' and
-`b'.)
+for 'main', which calls 'a', and an entry for 'c', with callers 'a' and
+'b'.)
 
      index  % time    self  children called     name
                                                   <spontaneous>
@@ -1159,41 +1151,41 @@ for `main', which calls `a', and an entry for `c', with callers `a' and
      [6]      0.00       0        0    6      c [6]
      ----------------------------------------
 
-   The `self' field of the cycle's primary line is the total time spent
-in all the functions of the cycle.  It equals the sum of the `self'
+   The 'self' field of the cycle's primary line is the total time spent
+in all the functions of the cycle.  It equals the sum of the 'self'
 fields for the individual functions in the cycle, found in the entry in
 the subroutine lines for these functions.
 
-   The `children' fields of the cycle's primary line and subroutine
-lines count only subroutines outside the cycle.  Even though `a' calls
-`b', the time spent in those calls to `b' is not counted in `a''s
-`children' time.  Thus, we do not encounter the problem of what to do
-when the time in those calls to `b' includes indirect recursive calls
-back to `a'.
+   The 'children' fields of the cycle's primary line and subroutine
+lines count only subroutines outside the cycle.  Even though 'a' calls
+'b', the time spent in those calls to 'b' is not counted in 'a''s
+'children' time.  Thus, we do not encounter the problem of what to do
+when the time in those calls to 'b' includes indirect recursive calls
+back to 'a'.
 
-   The `children' field of a caller-line in the cycle's entry estimates
+   The 'children' field of a caller-line in the cycle's entry estimates
 the amount of time spent _in the whole cycle_, and its other
 subroutines, on the times when that caller called a function in the
 cycle.
 
-   The `called' field in the primary line for the cycle has two numbers:
+   The 'called' field in the primary line for the cycle has two numbers:
 first, the number of times functions in the cycle were called by
 functions outside the cycle; second, the number of times they were
-called by functions in the cycle (including times when a function in
-the cycle calls itself).  This is a generalization of the usual split
-into non-recursive and recursive calls.
+called by functions in the cycle (including times when a function in the
+cycle calls itself).  This is a generalization of the usual split into
+non-recursive and recursive calls.
 
-   The `called' field of a subroutine-line for a cycle member in the
-cycle's entry says how many time that function was called from
-functions in the cycle.  The total of all these is the second number in
-the primary line's `called' field.
+   The 'called' field of a subroutine-line for a cycle member in the
+cycle's entry says how many time that function was called from functions
+in the cycle.  The total of all these is the second number in the
+primary line's 'called' field.
 
    In the individual entry for a function in a cycle, the other
 functions in the same cycle can appear as subroutines and as callers.
-These lines show how many times each function in the cycle called or
-was called from each other function in the cycle.  The `self' and
-`children' fields in these lines are blank because of the difficulty of
-defining meanings for them when recursion is going on.
+These lines show how many times each function in the cycle called or was
+called from each other function in the cycle.  The 'self' and 'children'
+fields in these lines are blank because of the difficulty of defining
+meanings for them when recursion is going on.
 
 
 File: gprof.info,  Node: Line-by-line,  Next: Annotated Source,  Prev: Call Graph,  Up: Output
@@ -1201,28 +1193,28 @@ File: gprof.info,  Node: Line-by-line,  Next: Annotated Source,  Prev: Call Grap
 5.3 Line-by-line Profiling
 ==========================
 
-`gprof''s `-l' option causes the program to perform "line-by-line"
+'gprof''s '-l' option causes the program to perform "line-by-line"
 profiling.  In this mode, histogram samples are assigned not to
-functions, but to individual lines of source code.  This only works
-with programs compiled with older versions of the `gcc' compiler.
-Newer versions of `gcc' use a different program - `gcov' - to display
+functions, but to individual lines of source code.  This only works with
+programs compiled with older versions of the 'gcc' compiler.  Newer
+versions of 'gcc' use a different program - 'gcov' - to display
 line-by-line profiling information.
 
-   With the older versions of `gcc' the program usually has to be
-compiled with a `-g' option, in addition to `-pg', in order to generate
+   With the older versions of 'gcc' the program usually has to be
+compiled with a '-g' option, in addition to '-pg', in order to generate
 debugging symbols for tracking source code lines.  Note, in much older
-versions of `gcc' the program had to be compiled with the `-a' command
+versions of 'gcc' the program had to be compiled with the '-a' command
 line option as well.
 
    The flat profile is the most useful output table in line-by-line
 mode.  The call graph isn't as useful as normal, since the current
-version of `gprof' does not propagate call graph arcs from source code
+version of 'gprof' does not propagate call graph arcs from source code
 lines to the enclosing function.  The call graph does, however, show
 each line of code that called each function, along with a count.
 
-   Here is a section of `gprof''s output, without line-by-line
-profiling.  Note that `ct_init' accounted for four histogram hits, and
-13327 calls to `init_block'.
+   Here is a section of 'gprof''s output, without line-by-line
+profiling.  Note that 'ct_init' accounted for four histogram hits, and
+13327 calls to 'init_block'.
 
      Flat profile:
 
@@ -1245,11 +1237,11 @@ profiling.  Note that `ct_init' accounted for four histogram hits, and
                      0.00    0.00   13327/13496       ct_init
      [7]      0.0    0.00    0.00   13496         init_block
 
-   Now let's look at some of `gprof''s output from the same program run,
-this time with line-by-line profiling enabled.  Note that `ct_init''s
+   Now let's look at some of 'gprof''s output from the same program run,
+this time with line-by-line profiling enabled.  Note that 'ct_init''s
 four histogram hits are broken down into four lines of source code--one
 hit occurred on each of lines 349, 351, 382 and 385.  In the call graph,
-note how `ct_init''s 13327 calls to `init_block' are broken down into
+note how 'ct_init''s 13327 calls to 'init_block' are broken down into
 one call from line 396, 3071 calls from line 384, 3730 calls from line
 385, and 6525 calls from 387.
 
@@ -1291,16 +1283,16 @@ File: gprof.info,  Node: Annotated Source,  Prev: Line-by-line,  Up: Output
 5.4 The Annotated Source Listing
 ================================
 
-`gprof''s `-A' option triggers an annotated source listing, which lists
+'gprof''s '-A' option triggers an annotated source listing, which lists
 the program's source code, each function labeled with the number of
-times it was called.  You may also need to specify the `-I' option, if
-`gprof' can't find the source code files.
+times it was called.  You may also need to specify the '-I' option, if
+'gprof' can't find the source code files.
 
-   With older versions of `gcc' compiling with `gcc ... -g -pg -a'
+   With older versions of 'gcc' compiling with 'gcc ... -g -pg -a'
 augments your program with basic-block counting code, in addition to
-function counting code.  This enables `gprof' to determine how many
-times each line of code was executed.  With newer versions of `gcc'
-support for displaying basic-block counts is provided by the `gcov'
+function counting code.  This enables 'gprof' to determine how many
+times each line of code was executed.  With newer versions of 'gcc'
+support for displaying basic-block counts is provided by the 'gcov'
 program.
 
    For example, consider the following function, taken from gzip, with
@@ -1326,17 +1318,17 @@ line numbers added:
      18     return c ^ 0xffffffffL;
      19 }
 
-   `updcrc' has at least five basic-blocks.  One is the function
-itself.  The `if' statement on line 9 generates two more basic-blocks,
-one for each branch of the `if'.  A fourth basic-block results from the
-`if' on line 13, and the contents of the `do' loop form the fifth
-basic-block.  The compiler may also generate additional basic-blocks to
-handle various special cases.
+   'updcrc' has at least five basic-blocks.  One is the function itself.
+The 'if' statement on line 9 generates two more basic-blocks, one for
+each branch of the 'if'.  A fourth basic-block results from the 'if' on
+line 13, and the contents of the 'do' loop form the fifth basic-block.
+The compiler may also generate additional basic-blocks to handle various
+special cases.
 
    A program augmented for basic-block counting can be analyzed with
-`gprof -l -A'.  The `-x' option is also helpful, to ensure that each
-line of code is labeled at least once.  Here is `updcrc''s annotated
-source listing for a sample `gzip' run:
+'gprof -l -A'.  The '-x' option is also helpful, to ensure that each
+line of code is labeled at least once.  Here is 'updcrc''s annotated
+source listing for a sample 'gzip' run:
 
                      ulg updcrc(s, n)
                          uch *s;
@@ -1359,8 +1351,8 @@ source listing for a sample `gzip' run:
                  2 ->}
 
    In this example, the function was called twice, passing once through
-each branch of the `if' statement.  The body of the `do' loop was
-executed a total of 26312 times.  Note how the `while' statement is
+each branch of the 'if' statement.  The body of the 'do' loop was
+executed a total of 26312 times.  Note how the 'while' statement is
 annotated.  It began execution 26312 times, once for each iteration
 through the loop.  One of those times (the last time) it exited, while
 it branched back to the beginning of the loop 26311 times.
@@ -1368,7 +1360,7 @@ it branched back to the beginning of the loop 26311 times.
 
 File: gprof.info,  Node: Inaccuracy,  Next: How do I?,  Prev: Output,  Up: Top
 
-6 Inaccuracy of `gprof' Output
+6 Inaccuracy of 'gprof' Output
 ******************************
 
 * Menu:
@@ -1382,7 +1374,7 @@ File: gprof.info,  Node: Sampling Error,  Next: Assumptions,  Up: Inaccuracy
 6.1 Statistical Sampling Error
 ==============================
 
-The run-time figures that `gprof' gives you are based on a sampling
+The run-time figures that 'gprof' gives you are based on a sampling
 process, so they are subject to statistical inaccuracy.  If a function
 runs only a small amount of time, so that on the average the sampling
 process ought to catch that function in the act only once, there is a
@@ -1395,8 +1387,8 @@ vary from run to run if your program is deterministic and single
 threaded.  In multi-threaded applications, or single threaded
 applications that link with multi-threaded libraries, the counts are
 only deterministic if the counting function is thread-safe.  (Note:
-beware that the mcount counting function in glibc is _not_
-thread-safe).  *Note Implementation of Profiling: Implementation.
+beware that the mcount counting function in glibc is _not_ thread-safe).
+*Note Implementation of Profiling: Implementation.
 
    The "sampling period" that is printed at the beginning of the flat
 profile says how often samples are taken.  The rule of thumb is that a
@@ -1405,15 +1397,15 @@ sampling period.
 
    The actual amount of error can be predicted.  For N samples, the
 _expected_ error is the square-root of N.  For example, if the sampling
-period is 0.01 seconds and `foo''s run-time is 1 second, N is 100
+period is 0.01 seconds and 'foo''s run-time is 1 second, N is 100
 samples (1 second/0.01 seconds), sqrt(N) is 10 samples, so the expected
-error in `foo''s run-time is 0.1 seconds (10*0.01 seconds), or ten
+error in 'foo''s run-time is 0.1 seconds (10*0.01 seconds), or ten
 percent of the observed value.  Again, if the sampling period is 0.01
-seconds and `bar''s run-time is 100 seconds, N is 10000 samples,
-sqrt(N) is 100 samples, so the expected error in `bar''s run-time is 1
-second, or one percent of the observed value.  It is likely to vary
-this much _on the average_ from one profiling run to the next.
-(_Sometimes_ it will vary more.)
+seconds and 'bar''s run-time is 100 seconds, N is 10000 samples, sqrt(N)
+is 100 samples, so the expected error in 'bar''s run-time is 1 second,
+or one percent of the observed value.  It is likely to vary this much
+_on the average_ from one profiling run to the next.  (_Sometimes_ it
+will vary more.)
 
    This does not mean that a small run-time figure is devoid of
 information.  If the program's _total_ run-time is large, a small
@@ -1423,16 +1415,16 @@ it is not worth optimizing.
 
    One way to get more accuracy is to give your program more (but
 similar) input data so it will take longer.  Another way is to combine
-the data from several runs, using the `-s' option of `gprof'.  Here is
+the data from several runs, using the '-s' option of 'gprof'.  Here is
 how:
 
   1. Run your program once.
 
-  2. Issue the command `mv gmon.out gmon.sum'.
+  2. Issue the command 'mv gmon.out gmon.sum'.
 
   3. Run your program again, the same as before.
 
-  4. Merge the new data in `gmon.out' into `gmon.sum' with this command:
+  4. Merge the new data in 'gmon.out' into 'gmon.sum' with this command:
 
           gprof -s EXECUTABLE-FILE gmon.out gmon.sum
 
@@ -1445,32 +1437,31 @@ how:
 
 File: gprof.info,  Node: Assumptions,  Prev: Sampling Error,  Up: Inaccuracy
 
-6.2 Estimating `children' Times
+6.2 Estimating 'children' Times
 ===============================
 
 Some of the figures in the call graph are estimates--for example, the
-`children' time values and all the time figures in caller and
-subroutine lines.
+'children' time values and all the time figures in caller and subroutine
+lines.
 
    There is no direct information about these measurements in the
-profile data itself.  Instead, `gprof' estimates them by making an
+profile data itself.  Instead, 'gprof' estimates them by making an
 assumption about your program that might or might not be true.
 
    The assumption made is that the average time spent in each call to
-any function `foo' is not correlated with who called `foo'.  If `foo'
-used 5 seconds in all, and 2/5 of the calls to `foo' came from `a',
-then `foo' contributes 2 seconds to `a''s `children' time, by
-assumption.
+any function 'foo' is not correlated with who called 'foo'.  If 'foo'
+used 5 seconds in all, and 2/5 of the calls to 'foo' came from 'a', then
+'foo' contributes 2 seconds to 'a''s 'children' time, by assumption.
 
    This assumption is usually true enough, but for some programs it is
-far from true.  Suppose that `foo' returns very quickly when its
-argument is zero; suppose that `a' always passes zero as an argument,
-while other callers of `foo' pass other arguments.  In this program,
-all the time spent in `foo' is in the calls from callers other than `a'.
-But `gprof' has no way of knowing this; it will blindly and incorrectly
-charge 2 seconds of time in `foo' to the children of `a'.
-
-   We hope some day to put more complete data into `gmon.out', so that
+far from true.  Suppose that 'foo' returns very quickly when its
+argument is zero; suppose that 'a' always passes zero as an argument,
+while other callers of 'foo' pass other arguments.  In this program, all
+the time spent in 'foo' is in the calls from callers other than 'a'.
+But 'gprof' has no way of knowing this; it will blindly and incorrectly
+charge 2 seconds of time in 'foo' to the children of 'a'.
+
+   We hope some day to put more complete data into 'gmon.out', so that
 this assumption is no longer needed, if we can figure out how.  For the
 novice, the estimated figures are usually more useful than misleading.
 
@@ -1481,23 +1472,27 @@ File: gprof.info,  Node: How do I?,  Next: Incompatibilities,  Prev: Inaccuracy,
 *****************************
 
 How can I get more exact information about hot spots in my program?
+
      Looking at the per-line call counts only tells part of the story.
-     Because `gprof' can only report call times and counts by function,
+     Because 'gprof' can only report call times and counts by function,
      the best way to get finer-grained information on where the program
      is spending its time is to re-factor large functions into sequences
      of calls to smaller ones.  Beware however that this can introduce
-     artificial hot spots since compiling with `-pg' adds a significant
+     artificial hot spots since compiling with '-pg' adds a significant
      overhead to function calls.  An alternative solution is to use a
      non-intrusive profiler, e.g. oprofile.
 
 How do I find which lines in my program were executed the most times?
-     Use the `gcov' program.
+
+     Use the 'gcov' program.
 
 How do I find which lines in my program called a particular function?
-     Use `gprof -l' and lookup the function in the call graph.  The
+
+     Use 'gprof -l' and lookup the function in the call graph.  The
      callers will be broken down by function and line number.
 
 How do I analyze a program that runs for less than a second?
+
      Try using a shell script like this one:
 
           for i in `seq 1 100`; do
@@ -1513,40 +1508,39 @@ How do I analyze a program that runs for less than a second?
      will be simple multiples of 100 (i.e., a function called once in
      each run will appear with a call count of 100).
 
-
 
 File: gprof.info,  Node: Incompatibilities,  Next: Details,  Prev: How do I?,  Up: Top
 
-8 Incompatibilities with Unix `gprof'
+8 Incompatibilities with Unix 'gprof'
 *************************************
 
-GNU `gprof' and Berkeley Unix `gprof' use the same data file
-`gmon.out', and provide essentially the same information.  But there
-are a few differences.
+GNU 'gprof' and Berkeley Unix 'gprof' use the same data file 'gmon.out',
+and provide essentially the same information.  But there are a few
+differences.
 
-   * GNU `gprof' uses a new, generalized file format with support for
+   * GNU 'gprof' uses a new, generalized file format with support for
      basic-block execution counts and non-realtime histograms.  A magic
-     cookie and version number allows `gprof' to easily identify new
+     cookie and version number allows 'gprof' to easily identify new
      style files.  Old BSD-style files can still be read.  *Note
      Profiling Data File Format: File Format.
 
-   * For a recursive function, Unix `gprof' lists the function as a
-     parent and as a child, with a `calls' field that lists the number
-     of recursive calls.  GNU `gprof' omits these lines and puts the
+   * For a recursive function, Unix 'gprof' lists the function as a
+     parent and as a child, with a 'calls' field that lists the number
+     of recursive calls.  GNU 'gprof' omits these lines and puts the
      number of recursive calls in the primary line.
 
-   * When a function is suppressed from the call graph with `-e', GNU
-     `gprof' still lists it as a subroutine of functions that call it.
+   * When a function is suppressed from the call graph with '-e', GNU
+     'gprof' still lists it as a subroutine of functions that call it.
 
-   * GNU `gprof' accepts the `-k' with its argument in the form
-     `from/to', instead of `from to'.
+   * GNU 'gprof' accepts the '-k' with its argument in the form
+     'from/to', instead of 'from to'.
 
-   * In the annotated source listing, if there are multiple basic
-     blocks on the same line, GNU `gprof' prints all of their counts,
-     separated by commas.
+   * In the annotated source listing, if there are multiple basic blocks
+     on the same line, GNU 'gprof' prints all of their counts, separated
+     by commas.
 
    * The blurbs, field widths, and output formats are different.  GNU
-     `gprof' prints blurbs after the tables, so that you can see the
+     'gprof' prints blurbs after the tables, so that you can see the
      tables without skipping the blurbs.
 
 
@@ -1558,9 +1552,9 @@ File: gprof.info,  Node: Details,  Next: GNU Free Documentation License,  Prev:
 * Menu:
 
 * Implementation::      How a program collects profiling information
-* File Format::         Format of `gmon.out' files
-* Internals::           `gprof''s internal operation
-* Debugging::           Using `gprof''s `-d' option
+* File Format::         Format of 'gmon.out' files
+* Internals::           'gprof''s internal operation
+* Debugging::           Using 'gprof''s '-d' option
 
 
 File: gprof.info,  Node: Implementation,  Next: File Format,  Up: Details
@@ -1573,99 +1567,98 @@ compiled so that when it is called, it will stash away some information
 about where it was called from.  From this, the profiler can figure out
 what function called it, and can count how many times it was called.
 This change is made by the compiler when your program is compiled with
-the `-pg' option, which causes every function to call `mcount' (or
-`_mcount', or `__mcount', depending on the OS and compiler) as one of
+the '-pg' option, which causes every function to call 'mcount' (or
+'_mcount', or '__mcount', depending on the OS and compiler) as one of
 its first operations.
 
-   The `mcount' routine, included in the profiling library, is
+   The 'mcount' routine, included in the profiling library, is
 responsible for recording in an in-memory call graph table both its
 parent routine (the child) and its parent's parent.  This is typically
-done by examining the stack frame to find both the address of the
-child, and the return address in the original parent.  Since this is a
-very machine-dependent operation, `mcount' itself is typically a short
+done by examining the stack frame to find both the address of the child,
+and the return address in the original parent.  Since this is a very
+machine-dependent operation, 'mcount' itself is typically a short
 assembly-language stub routine that extracts the required information,
-and then calls `__mcount_internal' (a normal C function) with two
-arguments--`frompc' and `selfpc'.  `__mcount_internal' is responsible
-for maintaining the in-memory call graph, which records `frompc',
-`selfpc', and the number of times each of these call arcs was traversed.
+and then calls '__mcount_internal' (a normal C function) with two
+arguments--'frompc' and 'selfpc'.  '__mcount_internal' is responsible
+for maintaining the in-memory call graph, which records 'frompc',
+'selfpc', and the number of times each of these call arcs was traversed.
 
    GCC Version 2 provides a magical function
-(`__builtin_return_address'), which allows a generic `mcount' function
+('__builtin_return_address'), which allows a generic 'mcount' function
 to extract the required information from the stack frame.  However, on
 some architectures, most notably the SPARC, using this builtin can be
 very computationally expensive, and an assembly language version of
-`mcount' is used for performance reasons.
+'mcount' is used for performance reasons.
 
    Number-of-calls information for library routines is collected by
 using a special version of the C library.  The programs in it are the
-same as in the usual C library, but they were compiled with `-pg'.  If
-you link your program with `gcc ... -pg', it automatically uses the
+same as in the usual C library, but they were compiled with '-pg'.  If
+you link your program with 'gcc ... -pg', it automatically uses the
 profiling version of the library.
 
-   Profiling also involves watching your program as it runs, and
-keeping a histogram of where the program counter happens to be every
-now and then.  Typically the program counter is looked at around 100
-times per second of run time, but the exact frequency may vary from
-system to system.
+   Profiling also involves watching your program as it runs, and keeping
+a histogram of where the program counter happens to be every now and
+then.  Typically the program counter is looked at around 100 times per
+second of run time, but the exact frequency may vary from system to
+system.
 
    This is done is one of two ways.  Most UNIX-like operating systems
-provide a `profil()' system call, which registers a memory array with
+provide a 'profil()' system call, which registers a memory array with
 the kernel, along with a scale factor that determines how the program's
-address space maps into the array.  Typical scaling values cause every
-2 to 8 bytes of address space to map into a single array slot.  On
-every tick of the system clock (assuming the profiled program is
-running), the value of the program counter is examined and the
-corresponding slot in the memory array is incremented.  Since this is
-done in the kernel, which had to interrupt the process anyway to handle
-the clock interrupt, very little additional system overhead is required.
+address space maps into the array.  Typical scaling values cause every 2
+to 8 bytes of address space to map into a single array slot.  On every
+tick of the system clock (assuming the profiled program is running), the
+value of the program counter is examined and the corresponding slot in
+the memory array is incremented.  Since this is done in the kernel,
+which had to interrupt the process anyway to handle the clock interrupt,
+very little additional system overhead is required.
 
    However, some operating systems, most notably Linux 2.0 (and
-earlier), do not provide a `profil()' system call.  On such a system,
-arrangements are made for the kernel to periodically deliver a signal
-to the process (typically via `setitimer()'), which then performs the
-same operation of examining the program counter and incrementing a slot
-in the memory array.  Since this method requires a signal to be
-delivered to user space every time a sample is taken, it uses
-considerably more overhead than kernel-based profiling.  Also, due to
-the added delay required to deliver the signal, this method is less
-accurate as well.
+earlier), do not provide a 'profil()' system call.  On such a system,
+arrangements are made for the kernel to periodically deliver a signal to
+the process (typically via 'setitimer()'), which then performs the same
+operation of examining the program counter and incrementing a slot in
+the memory array.  Since this method requires a signal to be delivered
+to user space every time a sample is taken, it uses considerably more
+overhead than kernel-based profiling.  Also, due to the added delay
+required to deliver the signal, this method is less accurate as well.
 
    A special startup routine allocates memory for the histogram and
-either calls `profil()' or sets up a clock signal handler.  This
-routine (`monstartup') can be invoked in several ways.  On Linux
-systems, a special profiling startup file `gcrt0.o', which invokes
-`monstartup' before `main', is used instead of the default `crt0.o'.
-Use of this special startup file is one of the effects of using `gcc
-... -pg' to link.  On SPARC systems, no special startup files are used.
-Rather, the `mcount' routine, when it is invoked for the first time
-(typically when `main' is called), calls `monstartup'.
-
-   If the compiler's `-a' option was used, basic-block counting is also
+either calls 'profil()' or sets up a clock signal handler.  This routine
+('monstartup') can be invoked in several ways.  On Linux systems, a
+special profiling startup file 'gcrt0.o', which invokes 'monstartup'
+before 'main', is used instead of the default 'crt0.o'.  Use of this
+special startup file is one of the effects of using 'gcc ... -pg' to
+link.  On SPARC systems, no special startup files are used.  Rather, the
+'mcount' routine, when it is invoked for the first time (typically when
+'main' is called), calls 'monstartup'.
+
+   If the compiler's '-a' option was used, basic-block counting is also
 enabled.  Each object file is then compiled with a static array of
 counts, initially zero.  In the executable code, every time a new
-basic-block begins (i.e., when an `if' statement appears), an extra
+basic-block begins (i.e., when an 'if' statement appears), an extra
 instruction is inserted to increment the corresponding count in the
 array.  At compile time, a paired array was constructed that recorded
 the starting address of each basic-block.  Taken together, the two
 arrays record the starting address of every basic-block, along with the
 number of times it was executed.
 
-   The profiling library also includes a function (`mcleanup') which is
-typically registered using `atexit()' to be called as the program
-exits, and is responsible for writing the file `gmon.out'.  Profiling
-is turned off, various headers are output, and the histogram is
-written, followed by the call-graph arcs and the basic-block counts.
+   The profiling library also includes a function ('mcleanup') which is
+typically registered using 'atexit()' to be called as the program exits,
+and is responsible for writing the file 'gmon.out'.  Profiling is turned
+off, various headers are output, and the histogram is written, followed
+by the call-graph arcs and the basic-block counts.
 
-   The output from `gprof' gives no indication of parts of your program
+   The output from 'gprof' gives no indication of parts of your program
 that are limited by I/O or swapping bandwidth.  This is because samples
-of the program counter are taken at fixed intervals of the program's
-run time.  Therefore, the time measurements in `gprof' output say
-nothing about time that your program was not running.  For example, a
-part of the program that creates so much data that it cannot all fit in
-physical memory at once may run very slowly due to thrashing, but
-`gprof' will say it uses little time.  On the other hand, sampling by
-run time has the advantage that the amount of load due to other users
-won't directly affect the output you get.
+of the program counter are taken at fixed intervals of the program's run
+time.  Therefore, the time measurements in 'gprof' output say nothing
+about time that your program was not running.  For example, a part of
+the program that creates so much data that it cannot all fit in physical
+memory at once may run very slowly due to thrashing, but 'gprof' will
+say it uses little time.  On the other hand, sampling by run time has
+the advantage that the amount of load due to other users won't directly
+affect the output you get.
 
 
 File: gprof.info,  Node: File Format,  Next: Internals,  Prev: Implementation,  Up: Details
@@ -1675,26 +1668,26 @@ File: gprof.info,  Node: File Format,  Next: Internals,  Prev: Implementation,
 
 The old BSD-derived file format used for profile data does not contain a
 magic cookie that allows to check whether a data file really is a
-`gprof' file.  Furthermore, it does not provide a version number, thus
-rendering changes to the file format almost impossible.  GNU `gprof'
+'gprof' file.  Furthermore, it does not provide a version number, thus
+rendering changes to the file format almost impossible.  GNU 'gprof'
 uses a new file format that provides these features.  For backward
-compatibility, GNU `gprof' continues to support the old BSD-derived
+compatibility, GNU 'gprof' continues to support the old BSD-derived
 format, but not all features are supported with it.  For example,
 basic-block execution counts cannot be accommodated by the old file
 format.
 
-   The new file format is defined in header file `gmon_out.h'.  It
+   The new file format is defined in header file 'gmon_out.h'.  It
 consists of a header containing the magic cookie and a version number,
 as well as some spare bytes available for future extensions.  All data
 in a profile data file is in the native format of the target for which
-the profile was collected.  GNU `gprof' adapts automatically to the
+the profile was collected.  GNU 'gprof' adapts automatically to the
 byte-order in use.
 
    In the new file format, the header is followed by a sequence of
 records.  Currently, there are three different record types: histogram
 records, call-graph arc records, and basic-block execution count
 records.  Each file can contain any number of each record type.  When
-reading a file, GNU `gprof' will ensure records of the same type are
+reading a file, GNU 'gprof' will ensure records of the same type are
 compatible with each other and compute the union of all records.  For
 example, for basic-block execution counts, the union is simply the sum
 of all execution counts for each basic-block.
@@ -1704,21 +1697,21 @@ of all execution counts for each basic-block.
 
 Histogram records consist of a header that is followed by an array of
 bins.  The header contains the text-segment range that the histogram
-spans, the size of the histogram in bytes (unlike in the old BSD
-format, this does not include the size of the header), the rate of the
-profiling clock, and the physical dimension that the bin counts
-represent after being scaled by the profiling clock rate.  The physical
-dimension is specified in two parts: a long name of up to 15 characters
-and a single character abbreviation.  For example, a histogram
-representing real-time would specify the long name as "seconds" and the
-abbreviation as "s".  This feature is useful for architectures that
-support performance monitor hardware (which, fortunately, is becoming
-increasingly common).  For example, under DEC OSF/1, the "uprofile"
-command can be used to produce a histogram of, say, instruction cache
-misses.  In this case, the dimension in the histogram header could be
-set to "i-cache misses" and the abbreviation could be set to "1"
-(because it is simply a count, not a physical dimension).  Also, the
-profiling rate would have to be set to 1 in this case.
+spans, the size of the histogram in bytes (unlike in the old BSD format,
+this does not include the size of the header), the rate of the profiling
+clock, and the physical dimension that the bin counts represent after
+being scaled by the profiling clock rate.  The physical dimension is
+specified in two parts: a long name of up to 15 characters and a single
+character abbreviation.  For example, a histogram representing real-time
+would specify the long name as "seconds" and the abbreviation as "s".
+This feature is useful for architectures that support performance
+monitor hardware (which, fortunately, is becoming increasingly common).
+For example, under DEC OSF/1, the "uprofile" command can be used to
+produce a histogram of, say, instruction cache misses.  In this case,
+the dimension in the histogram header could be set to "i-cache misses"
+and the abbreviation could be set to "1" (because it is simply a count,
+not a physical dimension).  Also, the profiling rate would have to be
+set to 1 in this case.
 
    Histogram bins are 16-bit numbers and each bin represent an equal
 amount of text-space.  For example, if the text-segment is one thousand
@@ -1731,170 +1724,167 @@ represents one hundred bytes.
 Call-graph records have a format that is identical to the one used in
 the BSD-derived file format.  It consists of an arc in the call graph
 and a count indicating the number of times the arc was traversed during
-program execution.  Arcs are specified by a pair of addresses: the
-first must be within caller's function and the second must be within
-the callee's function.  When performing profiling at the function
-level, these addresses can point anywhere within the respective
-function.  However, when profiling at the line-level, it is better if
-the addresses are as close to the call-site/entry-point as possible.
-This will ensure that the line-level call-graph is able to identify
-exactly which line of source code performed calls to a function.
+program execution.  Arcs are specified by a pair of addresses: the first
+must be within caller's function and the second must be within the
+callee's function.  When performing profiling at the function level,
+these addresses can point anywhere within the respective function.
+However, when profiling at the line-level, it is better if the addresses
+are as close to the call-site/entry-point as possible.  This will ensure
+that the line-level call-graph is able to identify exactly which line of
+source code performed calls to a function.
 
 9.2.3 Basic-Block Execution Count Records
 -----------------------------------------
 
 Basic-block execution count records consist of a header followed by a
-sequence of address/count pairs.  The header simply specifies the
-length of the sequence.  In an address/count pair, the address
-identifies a basic-block and the count specifies the number of times
-that basic-block was executed.  Any address within the basic-address can
-be used.
+sequence of address/count pairs.  The header simply specifies the length
+of the sequence.  In an address/count pair, the address identifies a
+basic-block and the count specifies the number of times that basic-block
+was executed.  Any address within the basic-address can be used.
 
 
 File: gprof.info,  Node: Internals,  Next: Debugging,  Prev: File Format,  Up: Details
 
-9.3 `gprof''s Internal Operation
+9.3 'gprof''s Internal Operation
 ================================
 
-Like most programs, `gprof' begins by processing its options.  During
-this stage, it may building its symspec list (`sym_ids.c:sym_id_add'),
-if options are specified which use symspecs.  `gprof' maintains a
-single linked list of symspecs, which will eventually get turned into
-12 symbol tables, organized into six include/exclude pairs--one pair
-each for the flat profile (INCL_FLAT/EXCL_FLAT), the call graph arcs
+Like most programs, 'gprof' begins by processing its options.  During
+this stage, it may building its symspec list ('sym_ids.c:sym_id_add'),
+if options are specified which use symspecs.  'gprof' maintains a single
+linked list of symspecs, which will eventually get turned into 12 symbol
+tables, organized into six include/exclude pairs--one pair each for the
+flat profile (INCL_FLAT/EXCL_FLAT), the call graph arcs
 (INCL_ARCS/EXCL_ARCS), printing in the call graph
 (INCL_GRAPH/EXCL_GRAPH), timing propagation in the call graph
 (INCL_TIME/EXCL_TIME), the annotated source listing
 (INCL_ANNO/EXCL_ANNO), and the execution count listing
 (INCL_EXEC/EXCL_EXEC).
 
-   After option processing, `gprof' finishes building the symspec list
-by adding all the symspecs in `default_excluded_list' to the exclude
+   After option processing, 'gprof' finishes building the symspec list
+by adding all the symspecs in 'default_excluded_list' to the exclude
 lists EXCL_TIME and EXCL_GRAPH, and if line-by-line profiling is
 specified, EXCL_FLAT as well.  These default excludes are not added to
 EXCL_ANNO, EXCL_ARCS, and EXCL_EXEC.
 
    Next, the BFD library is called to open the object file, verify that
-it is an object file, and read its symbol table (`core.c:core_init'),
-using `bfd_canonicalize_symtab' after mallocing an appropriately sized
+it is an object file, and read its symbol table ('core.c:core_init'),
+using 'bfd_canonicalize_symtab' after mallocing an appropriately sized
 array of symbols.  At this point, function mappings are read (if the
-`--file-ordering' option has been specified), and the core text space
-is read into memory (if the `-c' option was given).
+'--file-ordering' option has been specified), and the core text space is
+read into memory (if the '-c' option was given).
 
-   `gprof''s own symbol table, an array of Sym structures, is now built.
+   'gprof''s own symbol table, an array of Sym structures, is now built.
 This is done in one of two ways, by one of two routines, depending on
-whether line-by-line profiling (`-l' option) has been enabled.  For
+whether line-by-line profiling ('-l' option) has been enabled.  For
 normal profiling, the BFD canonical symbol table is scanned.  For
 line-by-line profiling, every text space address is examined, and a new
 symbol table entry gets created every time the line number changes.  In
 either case, two passes are made through the symbol table--one to count
 the size of the symbol table required, and the other to actually read
-the symbols.  In between the two passes, a single array of type `Sym'
-is created of the appropriate length.  Finally,
-`symtab.c:symtab_finalize' is called to sort the symbol table and
-remove duplicate entries (entries with the same memory address).
+the symbols.  In between the two passes, a single array of type 'Sym' is
+created of the appropriate length.  Finally, 'symtab.c:symtab_finalize'
+is called to sort the symbol table and remove duplicate entries (entries
+with the same memory address).
 
    The symbol table must be a contiguous array for two reasons.  First,
-the `qsort' library function (which sorts an array) will be used to
-sort the symbol table.  Also, the symbol lookup routine
-(`symtab.c:sym_lookup'), which finds symbols based on memory address,
+the 'qsort' library function (which sorts an array) will be used to sort
+the symbol table.  Also, the symbol lookup routine
+('symtab.c:sym_lookup'), which finds symbols based on memory address,
 uses a binary search algorithm which requires the symbol table to be a
-sorted array.  Function symbols are indicated with an `is_func' flag.
+sorted array.  Function symbols are indicated with an 'is_func' flag.
 Line number symbols have no special flags set.  Additionally, a symbol
-can have an `is_static' flag to indicate that it is a local symbol.
+can have an 'is_static' flag to indicate that it is a local symbol.
 
    With the symbol table read, the symspecs can now be translated into
-Syms (`sym_ids.c:sym_id_parse').  Remember that a single symspec can
-match multiple symbols.  An array of symbol tables (`syms') is created,
-each entry of which is a symbol table of Syms to be included or
-excluded from a particular listing.  The master symbol table and the
-symspecs are examined by nested loops, and every symbol that matches a
-symspec is inserted into the appropriate syms table.  This is done
-twice, once to count the size of each required symbol table, and again
-to build the tables, which have been malloced between passes.  From now
-on, to determine whether a symbol is on an include or exclude symspec
-list, `gprof' simply uses its standard symbol lookup routine on the
-appropriate table in the `syms' array.
+Syms ('sym_ids.c:sym_id_parse').  Remember that a single symspec can
+match multiple symbols.  An array of symbol tables ('syms') is created,
+each entry of which is a symbol table of Syms to be included or excluded
+from a particular listing.  The master symbol table and the symspecs are
+examined by nested loops, and every symbol that matches a symspec is
+inserted into the appropriate syms table.  This is done twice, once to
+count the size of each required symbol table, and again to build the
+tables, which have been malloced between passes.  From now on, to
+determine whether a symbol is on an include or exclude symspec list,
+'gprof' simply uses its standard symbol lookup routine on the
+appropriate table in the 'syms' array.
 
    Now the profile data file(s) themselves are read
-(`gmon_io.c:gmon_out_read'), first by checking for a new-style
-`gmon.out' header, then assuming this is an old-style BSD `gmon.out' if
+('gmon_io.c:gmon_out_read'), first by checking for a new-style
+'gmon.out' header, then assuming this is an old-style BSD 'gmon.out' if
 the magic number test failed.
 
-   New-style histogram records are read by `hist.c:hist_read_rec'.  For
+   New-style histogram records are read by 'hist.c:hist_read_rec'.  For
 the first histogram record, allocate a memory array to hold all the
-bins, and read them in.  When multiple profile data files (or files
-with multiple histogram records) are read, the memory ranges of each
-pair of histogram records must be either equal, or non-overlapping.
-For each pair of histogram records, the resolution (memory region size
-divided by the number of bins) must be the same.  The time unit must be
-the same for all histogram records. If the above containts are met, all
+bins, and read them in.  When multiple profile data files (or files with
+multiple histogram records) are read, the memory ranges of each pair of
+histogram records must be either equal, or non-overlapping.  For each
+pair of histogram records, the resolution (memory region size divided by
+the number of bins) must be the same.  The time unit must be the same
+for all histogram records.  If the above containts are met, all
 histograms for the same memory range are merged.
 
-   As each call graph record is read (`call_graph.c:cg_read_rec'), the
+   As each call graph record is read ('call_graph.c:cg_read_rec'), the
 parent and child addresses are matched to symbol table entries, and a
-call graph arc is created by `cg_arcs.c:arc_add', unless the arc fails
-a symspec check against INCL_ARCS/EXCL_ARCS.  As each arc is added, a
+call graph arc is created by 'cg_arcs.c:arc_add', unless the arc fails a
+symspec check against INCL_ARCS/EXCL_ARCS. As each arc is added, a
 linked list is maintained of the parent's child arcs, and of the child's
 parent arcs.  Both the child's call count and the arc's call count are
 incremented by the record's call count.
 
-   Basic-block records are read (`basic_blocks.c:bb_read_rec'), but
-only if line-by-line profiling has been selected.  Each basic-block
-address is matched to a corresponding line symbol in the symbol table,
-and an entry made in the symbol's bb_addr and bb_calls arrays.  Again,
-if multiple basic-block records are present for the same address, the
-call counts are cumulative.
+   Basic-block records are read ('basic_blocks.c:bb_read_rec'), but only
+if line-by-line profiling has been selected.  Each basic-block address
+is matched to a corresponding line symbol in the symbol table, and an
+entry made in the symbol's bb_addr and bb_calls arrays.  Again, if
+multiple basic-block records are present for the same address, the call
+counts are cumulative.
 
-   A gmon.sum file is dumped, if requested (`gmon_io.c:gmon_out_write').
+   A gmon.sum file is dumped, if requested ('gmon_io.c:gmon_out_write').
 
    If histograms were present in the data files, assign them to symbols
-(`hist.c:hist_assign_samples') by iterating over all the sample bins
-and assigning them to symbols.  Since the symbol table is sorted in
-order of ascending memory addresses, we can simple follow along in the
-symbol table as we make our pass over the sample bins.  This step
-includes a symspec check against INCL_FLAT/EXCL_FLAT.  Depending on the
-histogram scale factor, a sample bin may span multiple symbols, in
-which case a fraction of the sample count is allocated to each symbol,
-proportional to the degree of overlap.  This effect is rare for normal
-profiling, but overlaps are more common during line-by-line profiling,
-and can cause each of two adjacent lines to be credited with half a
-hit, for example.
-
-   If call graph data is present, `cg_arcs.c:cg_assemble' is called.
-First, if `-c' was specified, a machine-dependent routine (`find_call')
+('hist.c:hist_assign_samples') by iterating over all the sample bins and
+assigning them to symbols.  Since the symbol table is sorted in order of
+ascending memory addresses, we can simple follow along in the symbol
+table as we make our pass over the sample bins.  This step includes a
+symspec check against INCL_FLAT/EXCL_FLAT. Depending on the histogram
+scale factor, a sample bin may span multiple symbols, in which case a
+fraction of the sample count is allocated to each symbol, proportional
+to the degree of overlap.  This effect is rare for normal profiling, but
+overlaps are more common during line-by-line profiling, and can cause
+each of two adjacent lines to be credited with half a hit, for example.
+
+   If call graph data is present, 'cg_arcs.c:cg_assemble' is called.
+First, if '-c' was specified, a machine-dependent routine ('find_call')
 scans through each symbol's machine code, looking for subroutine call
 instructions, and adding them to the call graph with a zero call count.
-A topological sort is performed by depth-first numbering all the
-symbols (`cg_dfn.c:cg_dfn'), so that children are always numbered less
-than their parents, then making a array of pointers into the symbol
-table and sorting it into numerical order, which is reverse topological
-order (children appear before parents).  Cycles are also detected at
-this point, all members of which are assigned the same topological
-number.  Two passes are now made through this sorted array of symbol
-pointers.  The first pass, from end to beginning (parents to children),
-computes the fraction of child time to propagate to each parent and a
-print flag.  The print flag reflects symspec handling of
-INCL_GRAPH/EXCL_GRAPH, with a parent's include or exclude (print or no
-print) property being propagated to its children, unless they
-themselves explicitly appear in INCL_GRAPH or EXCL_GRAPH.  A second
-pass, from beginning to end (children to parents) actually propagates
-the timings along the call graph, subject to a check against
-INCL_TIME/EXCL_TIME.  With the print flag, fractions, and timings now
-stored in the symbol structures, the topological sort array is now
-discarded, and a new array of pointers is assembled, this time sorted
-by propagated time.
+A topological sort is performed by depth-first numbering all the symbols
+('cg_dfn.c:cg_dfn'), so that children are always numbered less than
+their parents, then making a array of pointers into the symbol table and
+sorting it into numerical order, which is reverse topological order
+(children appear before parents).  Cycles are also detected at this
+point, all members of which are assigned the same topological number.
+Two passes are now made through this sorted array of symbol pointers.
+The first pass, from end to beginning (parents to children), computes
+the fraction of child time to propagate to each parent and a print flag.
+The print flag reflects symspec handling of INCL_GRAPH/EXCL_GRAPH, with
+a parent's include or exclude (print or no print) property being
+propagated to its children, unless they themselves explicitly appear in
+INCL_GRAPH or EXCL_GRAPH. A second pass, from beginning to end (children
+to parents) actually propagates the timings along the call graph,
+subject to a check against INCL_TIME/EXCL_TIME. With the print flag,
+fractions, and timings now stored in the symbol structures, the
+topological sort array is now discarded, and a new array of pointers is
+assembled, this time sorted by propagated time.
 
    Finally, print the various outputs the user requested, which is now
-fairly straightforward.  The call graph (`cg_print.c:cg_print') and
-flat profile (`hist.c:hist_print') are regurgitations of values already
+fairly straightforward.  The call graph ('cg_print.c:cg_print') and flat
+profile ('hist.c:hist_print') are regurgitations of values already
 computed.  The annotated source listing
-(`basic_blocks.c:print_annotated_source') uses basic-block information,
+('basic_blocks.c:print_annotated_source') uses basic-block information,
 if present, to label each line of code with call counts, otherwise only
 the function call counts are presented.
 
    The function ordering code is marginally well documented in the
-source code itself (`cg_print.c').  Basically, the functions with the
+source code itself ('cg_print.c').  Basically, the functions with the
 most use and the most parents are placed first, followed by other
 functions with the most use, followed by lower use functions, followed
 by unused functions at the end.
@@ -1902,55 +1892,44 @@ by unused functions at the end.
 
 File: gprof.info,  Node: Debugging,  Prev: Internals,  Up: Details
 
-9.4 Debugging `gprof'
+9.4 Debugging 'gprof'
 =====================
 
-If `gprof' was compiled with debugging enabled, the `-d' option
-triggers debugging output (to stdout) which can be helpful in
-understanding its operation.  The debugging number specified is
-interpreted as a sum of the following options:
+If 'gprof' was compiled with debugging enabled, the '-d' option triggers
+debugging output (to stdout) which can be helpful in understanding its
+operation.  The debugging number specified is interpreted as a sum of
+the following options:
 
 2 - Topological sort
      Monitor depth-first numbering of symbols during call graph analysis
-
 4 - Cycles
      Shows symbols as they are identified as cycle heads
-
 16 - Tallying
      As the call graph arcs are read, show each arc and how the total
      calls to each function are tallied
-
 32 - Call graph arc sorting
      Details sorting individual parents/children within each call graph
      entry
-
 64 - Reading histogram and call graph records
      Shows address ranges of histograms as they are read, and each call
      graph arc
-
 128 - Symbol table
      Reading, classifying, and sorting the symbol table from the object
-     file.  For line-by-line profiling (`-l' option), also shows line
+     file.  For line-by-line profiling ('-l' option), also shows line
      numbers being assigned to memory addresses.
-
 256 - Static call graph
-     Trace operation of `-c' option
-
+     Trace operation of '-c' option
 512 - Symbol table and arc table lookups
      Detail operation of lookup routines
-
 1024 - Call graph propagation
      Shows how function times are propagated along the call graph
-
 2048 - Basic-blocks
      Shows basic-block records as they are read from profile data (only
-     meaningful with `-l' option)
-
+     meaningful with '-l' option)
 4096 - Symspecs
      Shows symspec-to-symbol pattern matching operation
-
 8192 - Annotate source
-     Tracks operation of `-A' option
+     Tracks operation of '-A' option
 
 
 File: gprof.info,  Node: GNU Free Documentation License,  Prev: Details,  Up: Top
@@ -1961,7 +1940,7 @@ Appendix A GNU Free Documentation License
                      Version 1.3, 3 November 2008
 
      Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-     `http://fsf.org/'
+     <http://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.
@@ -1986,21 +1965,21 @@ Appendix A GNU Free Documentation License
      free program should come with manuals providing the same freedoms
      that the software does.  But this License is not limited to
      software manuals; it can be used for any textual work, regardless
-     of subject matter or whether it is published as a printed book.
-     We recommend this License principally for works whose purpose is
+     of subject matter or whether it is published as a printed book.  We
+     recommend this License principally for works whose purpose is
      instruction or reference.
 
   1. APPLICABILITY AND DEFINITIONS
 
      This License applies to any manual or other work, in any medium,
-     that contains a notice placed by the copyright holder saying it
-     can be distributed under the terms of this License.  Such a notice
+     that contains a notice placed by the copyright holder saying it can
+     be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
      "Document", below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as "you".  You
-     accept the license if you copy, modify or distribute the work in a
-     way requiring permission under copyright law.
+     of the public is a licensee, and is addressed as "you".  You accept
+     the license if you copy, modify or distribute the work in a way
+     requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
@@ -2018,12 +1997,12 @@ Appendix A GNU Free Documentation License
      regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
-     titles are designated, as being those of Invariant Sections, in
-     the notice that says that the Document is released under this
-     License.  If a section does not fit the above definition of
-     Secondary then it is not allowed to be designated as Invariant.
-     The Document may contain zero Invariant Sections.  If the Document
-     does not identify any Invariant Sections then there are none.
+     titles are designated, as being those of Invariant Sections, in the
+     notice that says that the Document is released under this License.
+     If a section does not fit the above definition of Secondary then it
+     is not allowed to be designated as Invariant.  The Document may
+     contain zero Invariant Sections.  If the Document does not identify
+     any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -2034,27 +2013,27 @@ Appendix A GNU Free Documentation License
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
-     straightforwardly with generic text editors or (for images
-     composed of pixels) generic paint programs or (for drawings) some
-     widely available drawing editor, and that is suitable for input to
-     text formatters or for automatic translation to a variety of
-     formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup, or absence of
-     markup, has been arranged to thwart or discourage subsequent
-     modification by readers is not Transparent.  An image format is
-     not Transparent if used for any substantial amount of text.  A
-     copy that is not "Transparent" is called "Opaque".
+     straightforwardly with generic text editors or (for images composed
+     of pixels) generic paint programs or (for drawings) some widely
+     available drawing editor, and that is suitable for input to text
+     formatters or for automatic translation to a variety of formats
+     suitable for input to text formatters.  A copy made in an otherwise
+     Transparent file format whose markup, or absence of markup, has
+     been arranged to thwart or discourage subsequent modification by
+     readers is not Transparent.  An image format is not Transparent if
+     used for any substantial amount of text.  A copy that is not
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
-     SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML, PostScript or PDF designed for
-     human modification.  Examples of transparent image formats include
-     PNG, XCF and JPG.  Opaque formats include proprietary formats that
-     can be read and edited only by proprietary word processors, SGML or
-     XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML, PostScript or PDF
-     produced by some word processors for output purposes only.
+     SGML or XML using a publicly available DTD, and standard-conforming
+     simple HTML, PostScript or PDF designed for human modification.
+     Examples of transparent image formats include PNG, XCF and JPG.
+     Opaque formats include proprietary formats that can be read and
+     edited only by proprietary word processors, SGML or XML for which
+     the DTD and/or processing tools are not generally available, and
+     the machine-generated HTML, PostScript or PDF produced by some word
+     processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
@@ -2092,8 +2071,8 @@ Appendix A GNU Free Documentation License
      may not use technical measures to obstruct or control the reading
      or further copying of the copies you make or distribute.  However,
      you may accept compensation in exchange for copies.  If you
-     distribute a large enough number of copies you must also follow
-     the conditions in section 3.
+     distribute a large enough number of copies you must also follow the
+     conditions in section 3.
 
      You may also lend copies, under the same conditions stated above,
      and you may publicly display copies.
@@ -2107,12 +2086,11 @@ Appendix A GNU Free Documentation License
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
-     front cover must present the full title with all words of the
-     title equally prominent and visible.  You may add other material
-     on the covers in addition.  Copying with changes limited to the
-     covers, as long as they preserve the title of the Document and
-     satisfy these conditions, can be treated as verbatim copying in
-     other respects.
+     front cover must present the full title with all words of the title
+     equally prominent and visible.  You may add other material on the
+     covers in addition.  Copying with changes limited to the covers, as
+     long as they preserve the title of the Document and satisfy these
+     conditions, can be treated as verbatim copying in other respects.
 
      If the required texts for either cover are too voluminous to fit
      legibly, you should put the first ones listed (as many as fit
@@ -2120,40 +2098,39 @@ Appendix A GNU Free Documentation License
      adjacent pages.
 
      If you publish or distribute Opaque copies of the Document
-     numbering more than 100, you must either include a
-     machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a computer-network location from
-     which the general network-using public has access to download
-     using public-standard network protocols a complete Transparent
-     copy of the Document, free of added material.  If you use the
-     latter option, you must take reasonably prudent steps, when you
-     begin distribution of Opaque copies in quantity, to ensure that
-     this Transparent copy will remain thus accessible at the stated
-     location until at least one year after the last time you
-     distribute an Opaque copy (directly or through your agents or
-     retailers) of that edition to the public.
+     numbering more than 100, you must either include a machine-readable
+     Transparent copy along with each Opaque copy, or state in or with
+     each Opaque copy a computer-network location from which the general
+     network-using public has access to download using public-standard
+     network protocols a complete Transparent copy of the Document, free
+     of added material.  If you use the latter option, you must take
+     reasonably prudent steps, when you begin distribution of Opaque
+     copies in quantity, to ensure that this Transparent copy will
+     remain thus accessible at the stated location until at least one
+     year after the last time you distribute an Opaque copy (directly or
+     through your agents or retailers) of that edition to the public.
 
      It is requested, but not required, that you contact the authors of
-     the Document well before redistributing any large number of
-     copies, to give them a chance to provide you with an updated
-     version of the Document.
+     the Document well before redistributing any large number of copies,
+     to give them a chance to provide you with an updated version of the
+     Document.
 
   4. MODIFICATIONS
 
      You may copy and distribute a Modified Version of the Document
      under the conditions of sections 2 and 3 above, provided that you
-     release the Modified Version under precisely this License, with
-     the Modified Version filling the role of the Document, thus
-     licensing distribution and modification of the Modified Version to
-     whoever possesses a copy of it.  In addition, you must do these
-     things in the Modified Version:
+     release the Modified Version under precisely this License, with the
+     Modified Version filling the role of the Document, thus licensing
+     distribution and modification of the Modified Version to whoever
+     possesses a copy of it.  In addition, you must do these things in
+     the Modified Version:
 
        A. Use in the Title Page (and on the covers, if any) a title
-          distinct from that of the Document, and from those of
-          previous versions (which should, if there were any, be listed
-          in the History section of the Document).  You may use the
-          same title as a previous version if the original publisher of
-          that version gives permission.
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
 
        B. List on the Title Page, as authors, one or more persons or
           entities responsible for authorship of the modifications in
@@ -2183,31 +2160,30 @@ Appendix A GNU Free Documentation License
 
        I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
-          authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section Entitled "History" in
-          the Document, create one stating the title, year, authors,
-          and publisher of the Document as given on its Title Page,
-          then add an item describing the Modified Version as stated in
-          the previous sentence.
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled "History" in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
 
        J. Preserve the network location, if any, given in the Document
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
-          previous versions it was based on.  These may be placed in
-          the "History" section.  You may omit a network location for a
-          work that was published at least four years before the
-          Document itself, or if the original publisher of the version
-          it refers to gives permission.
+          previous versions it was based on.  These may be placed in the
+          "History" section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
 
        K. For any section Entitled "Acknowledgements" or "Dedications",
-          Preserve the Title of the section, and preserve in the
-          section all the substance and tone of each of the contributor
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
 
-       L. Preserve all the Invariant Sections of the Document,
-          unaltered in their text and in their titles.  Section numbers
-          or the equivalent are not considered part of the section
-          titles.
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
 
        M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
@@ -2220,11 +2196,11 @@ Appendix A GNU Free Documentation License
 
      If the Modified Version includes new front-matter sections or
      appendices that qualify as Secondary Sections and contain no
-     material copied from the Document, you may at your option
-     designate some or all of these sections as invariant.  To do this,
-     add their titles to the list of Invariant Sections in the Modified
-     Version's license notice.  These titles must be distinct from any
-     other section titles.
+     material copied from the Document, you may at your option designate
+     some or all of these sections as invariant.  To do this, add their
+     titles to the list of Invariant Sections in the Modified Version's
+     license notice.  These titles must be distinct from any other
+     section titles.
 
      You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
@@ -2233,15 +2209,15 @@ Appendix A GNU Free Documentation License
      definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
-     and a passage of up to 25 words as a Back-Cover Text, to the end
-     of the list of Cover Texts in the Modified Version.  Only one
-     passage of Front-Cover Text and one of Back-Cover Text may be
-     added by (or through arrangements made by) any one entity.  If the
-     Document already includes a cover text for the same cover,
-     previously added by you or by arrangement made by the same entity
-     you are acting on behalf of, you may not add another; but you may
-     replace the old one, on explicit permission from the previous
-     publisher that added the old one.
+     and a passage of up to 25 words as a Back-Cover Text, to the end of
+     the list of Cover Texts in the Modified Version.  Only one passage
+     of Front-Cover Text and one of Back-Cover Text may be added by (or
+     through arrangements made by) any one entity.  If the Document
+     already includes a cover text for the same cover, previously added
+     by you or by arrangement made by the same entity you are acting on
+     behalf of, you may not add another; but you may replace the old
+     one, on explicit permission from the previous publisher that added
+     the old one.
 
      The author(s) and publisher(s) of the Document do not by this
      License give permission to use their names for publicity for or to
@@ -2251,8 +2227,8 @@ Appendix A GNU Free Documentation License
 
      You may combine the Document with other documents released under
      this License, under the terms defined in section 4 above for
-     modified versions, provided that you include in the combination
-     all of the Invariant Sections of all of the original documents,
+     modified versions, provided that you include in the combination all
+     of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
      combined work in its license notice, and that you preserve all
      their Warranty Disclaimers.
@@ -2279,20 +2255,20 @@ Appendix A GNU Free Documentation License
      documents released under this License, and replace the individual
      copies of this License in the various documents with a single copy
      that is included in the collection, provided that you follow the
-     rules of this License for verbatim copying of each of the
-     documents in all other respects.
+     rules of this License for verbatim copying of each of the documents
+     in all other respects.
 
      You may extract a single document from such a collection, and
      distribute it individually under this License, provided you insert
-     a copy of this License into the extracted document, and follow
-     this License in all other respects regarding verbatim copying of
-     that document.
+     a copy of this License into the extracted document, and follow this
+     License in all other respects regarding verbatim copying of that
+     document.
 
   7. AGGREGATION WITH INDEPENDENT WORKS
 
      A compilation of the Document or its derivatives with other
-     separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, is called an "aggregate" if the
+     separate and independent documents or works, in or on a volume of a
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
      legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
@@ -2337,8 +2313,8 @@ Appendix A GNU Free Documentation License
 
      However, if you cease all violation of this License, then your
      license from a particular copyright holder is reinstated (a)
-     provisionally, unless and until the copyright holder explicitly
-     and finally terminates your license, and (b) permanently, if the
+     provisionally, unless and until the copyright holder explicitly and
+     finally terminates your license, and (b) permanently, if the
      copyright holder fails to notify you of the violation by some
      reasonable means prior to 60 days after the cessation.
 
@@ -2350,33 +2326,33 @@ Appendix A GNU Free Documentation License
      after your receipt of the notice.
 
      Termination of your rights under this section does not terminate
-     the licenses of parties who have received copies or rights from
-     you under this License.  If your rights have been terminated and
-     not permanently reinstated, receipt of a copy of some or all of
-     the same material does not give you any rights to use it.
+     the licenses of parties who have received copies or rights from you
+     under this License.  If your rights have been terminated and not
+     permanently reinstated, receipt of a copy of some or all of the
+     same material does not give you any rights to use it.
 
- 10. FUTURE REVISIONS OF THIS LICENSE
+  10. FUTURE REVISIONS OF THIS LICENSE
 
      The Free Software Foundation may publish new, revised versions of
      the GNU Free Documentation License from time to time.  Such new
      versions will be similar in spirit to the present version, but may
      differ in detail to address new problems or concerns.  See
-     `http://www.gnu.org/copyleft/'.
+     <http://www.gnu.org/copyleft/>.
 
      Each version of the License is given a distinguishing version
      number.  If the Document specifies that a particular numbered
      version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
-     published (not as a draft) by the Free Software Foundation.  If
-     the Document does not specify a version number of this License,
-     you may choose any version ever published (not as a draft) by the
-     Free Software Foundation.  If the Document specifies that a proxy
-     can decide which future versions of this License can be used, that
+     published (not as a draft) by the Free Software Foundation.  If the
+     Document does not specify a version number of this License, you may
+     choose any version ever published (not as a draft) by the Free
+     Software Foundation.  If the Document specifies that a proxy can
+     decide which future versions of this License can be used, that
      proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
- 11. RELICENSING
+  11. RELICENSING
 
      "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
      World Wide Web server that publishes copyrightable works and also
@@ -2406,7 +2382,6 @@ Appendix A GNU Free Documentation License
      site under CC-BY-SA on the same site at any time before August 1,
      2009, provided the MMC is eligible for relicensing.
 
-
 ADDENDUM: How to use this License for your documents
 ====================================================
 
@@ -2423,7 +2398,7 @@ notices just after the title page:
        Free Documentation License''.
 
    If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts."  line with this:
 
          with the Invariant Sections being LIST THEIR TITLES, with
          the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -2434,42 +2409,42 @@ combination of the three, merge those two alternatives to suit the
 situation.
 
    If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
 
 
 
 Tag Table:
-Node: Top897
-Node: Introduction2233
-Node: Compiling4725
-Node: Executing8781
-Node: Invoking11569
-Node: Output Options12984
-Node: Analysis Options20073
-Node: Miscellaneous Options23771
-Node: Deprecated Options25026
-Node: Symspecs27095
-Node: Output28921
-Node: Flat Profile29961
-Node: Call Graph34914
-Node: Primary38146
-Node: Callers40734
-Node: Subroutines42851
-Node: Cycles44692
-Node: Line-by-line51469
-Node: Annotated Source55542
-Node: Inaccuracy58541
-Node: Sampling Error58799
-Node: Assumptions61703
-Node: How do I?63173
-Node: Incompatibilities64727
-Node: Details66221
-Node: Implementation66614
-Node: File Format72511
-Node: Internals76801
-Node: Debugging85296
-Node: GNU Free Documentation License86897
+Node: Top774
+Node: Introduction2099
+Node: Compiling4590
+Node: Executing8646
+Node: Invoking11434
+Node: Output Options12849
+Node: Analysis Options19940
+Node: Miscellaneous Options23639
+Node: Deprecated Options24893
+Node: Symspecs26956
+Node: Output28782
+Node: Flat Profile29822
+Node: Call Graph34775
+Node: Primary38007
+Node: Callers40595
+Node: Subroutines42713
+Node: Cycles44554
+Node: Line-by-line51331
+Node: Annotated Source55405
+Node: Inaccuracy58402
+Node: Sampling Error58660
+Node: Assumptions61564
+Node: How do I?63034
+Node: Incompatibilities64591
+Node: Details66085
+Node: Implementation66478
+Node: File Format72377
+Node: Internals76665
+Node: Debugging85155
+Node: GNU Free Documentation License86745
 
 End Tag Table
diff --git a/share/info/ld.info b/share/info/ld.info
index ac12b21..b03a430 100644
--- a/share/info/ld.info
+++ b/share/info/ld.info
@@ -1,13 +1,6 @@
-This is ld.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/ld/ld.texinfo.
+This is ld.info, produced by makeinfo version 5.1 from ld.texinfo.
 
-INFO-DIR-SECTION Software development
-START-INFO-DIR-ENTRY
-* Ld: (ld).                       The GNU linker.
-END-INFO-DIR-ENTRY
-
-   This file documents the GNU linker LD (Linux/GNU Binutils) version
-2.23.52.0.2.
+This file documents the GNU linker LD (GNU Binutils) version 2.24.0.
 
    Copyright (C) 1991-2013 Free Software Foundation, Inc.
 
@@ -17,6 +10,10 @@ any later version published by the Free Software Foundation; with no
 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
 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
+* Ld: (ld).                       The GNU linker.
+END-INFO-DIR-ENTRY
 
 
 File: ld.info,  Node: Top,  Next: Overview,  Up: (dir)
@@ -24,21 +21,18 @@ File: ld.info,  Node: Top,  Next: Overview,  Up: (dir)
 LD
 **
 
-This file documents the GNU linker ld (Linux/GNU Binutils) version
-2.23.52.0.2.
+This file documents the GNU linker ld (GNU Binutils) version 2.24.0.
 
    This document is distributed under the terms of the GNU Free
-Documentation License version 1.3.  A copy of the license is included
-in the section entitled "GNU Free Documentation License".
+Documentation License version 1.3.  A copy of the license is included in
+the section entitled "GNU Free Documentation License".
 
 * Menu:
 
 * Overview::                    Overview
 * Invocation::                  Invocation
 * Scripts::                     Linker Scripts
-
 * Machine Dependent::           Machine Dependent Features
-
 * BFD::                         BFD
 
 * Reporting Bugs::              Reporting Bugs
@@ -52,24 +46,24 @@ File: ld.info,  Node: Overview,  Next: Invocation,  Prev: Top,  Up: Top
 1 Overview
 **********
 
-`ld' combines a number of object and archive files, relocates their
-data and ties up symbol references. Usually the last step in compiling
-a program is to run `ld'.
+'ld' combines a number of object and archive files, relocates their data
+and ties up symbol references.  Usually the last step in compiling a
+program is to run 'ld'.
 
-   `ld' accepts Linker Command Language files written in a superset of
+   'ld' accepts Linker Command Language files written in a superset of
 AT&T's Link Editor Command Language syntax, to provide explicit and
 total control over the linking process.
 
-   This version of `ld' uses the general purpose BFD libraries to
-operate on object files. This allows `ld' to read, combine, and write
-object files in many different formats--for example, COFF or `a.out'.
+   This version of 'ld' uses the general purpose BFD libraries to
+operate on object files.  This allows 'ld' to read, combine, and write
+object files in many different formats--for example, COFF or 'a.out'.
 Different formats may be linked together to produce any available kind
 of object file.  *Note BFD::, for more information.
 
    Aside from its flexibility, the GNU linker is more helpful than other
 linkers in providing diagnostic information.  Many linkers abandon
 execution immediately upon encountering an error; whenever possible,
-`ld' continues executing, allowing you to identify other errors (or, in
+'ld' continues executing, allowing you to identify other errors (or, in
 some cases, to get an output file in spite of the error).
 
 
@@ -78,7 +72,7 @@ File: ld.info,  Node: Invocation,  Next: Scripts,  Prev: Overview,  Up: Top
 2 Invocation
 ************
 
-The GNU linker `ld' is meant to cover a broad range of situations, and
+The GNU linker 'ld' is meant to cover a broad range of situations, and
 to be as compatible as possible with other linkers.  As a result, you
 have many choices to control its behavior.
 
@@ -93,22 +87,22 @@ File: ld.info,  Node: Options,  Next: Environment,  Up: Invocation
 2.1 Command Line Options
 ========================
 
-   The linker supports a plethora of command-line options, but in actual
+The linker supports a plethora of command-line options, but in actual
 practice few of them are used in any particular context.  For instance,
-a frequent use of `ld' is to link standard Unix object files on a
+a frequent use of 'ld' is to link standard Unix object files on a
 standard, supported Unix system.  On such a system, to link a file
-`hello.o':
+'hello.o':
 
      ld -o OUTPUT /lib/crt0.o hello.o -lc
 
-   This tells `ld' to produce a file called OUTPUT as the result of
-linking the file `/lib/crt0.o' with `hello.o' and the library `libc.a',
+   This tells 'ld' to produce a file called OUTPUT as the result of
+linking the file '/lib/crt0.o' with 'hello.o' and the library 'libc.a',
 which will come from the standard search directories.  (See the
-discussion of the `-l' option below.)
+discussion of the '-l' option below.)
 
-   Some of the command-line options to `ld' may be specified at any
+   Some of the command-line options to 'ld' may be specified at any
 point in the command line.  However, options which refer to files, such
-as `-l' or `-T', cause the file to be read at the point at which the
+as '-l' or '-T', cause the file to be read at the point at which the
 option appears in the command line, relative to the object files and
 other file options.  Repeating non-file options with a different
 argument will either have no further effect, or override prior
@@ -122,22 +116,22 @@ command-line options, except that an object file argument may not be
 placed between an option and its argument.
 
    Usually the linker is invoked with at least one object file, but you
-can specify other forms of binary input files using `-l', `-R', and the
+can specify other forms of binary input files using '-l', '-R', and the
 script command language.  If _no_ binary input files at all are
 specified, the linker does not produce any output, and issues the
-message `No input files'.
+message 'No input files'.
 
    If the linker cannot recognize the format of an object file, it will
 assume that it is a linker script.  A script specified in this way
 augments the main linker script used for the link (either the default
-linker script or the one specified by using `-T').  This feature
-permits the linker to link against a file which appears to be an object
-or an archive, but actually merely defines some symbol values, or uses
-`INPUT' or `GROUP' to load other objects.  Specifying a script in this
-way merely augments the main linker script, with the extra commands
-placed after the main script; use the `-T' option to replace the
-default linker script entirely, but note the effect of the `INSERT'
-command.  *Note Scripts::.
+linker script or the one specified by using '-T').  This feature permits
+the linker to link against a file which appears to be an object or an
+archive, but actually merely defines some symbol values, or uses 'INPUT'
+or 'GROUP' to load other objects.  Specifying a script in this way
+merely augments the main linker script, with the extra commands placed
+after the main script; use the '-T' option to replace the default linker
+script entirely, but note the effect of the 'INSERT' command.  *Note
+Scripts::.
 
    For options whose names are a single letter, option arguments must
 either follow the option letter without intervening whitespace, or be
@@ -145,22 +139,22 @@ given as separate arguments immediately following the option that
 requires them.
 
    For options whose names are multiple letters, either one dash or two
-can precede the option name; for example, `-trace-symbol' and
-`--trace-symbol' are equivalent.  Note--there is one exception to this
-rule.  Multiple letter options that start with a lower case 'o' can
-only be preceded by two dashes.  This is to reduce confusion with the
-`-o' option.  So for example `-omagic' sets the output file name to
-`magic' whereas `--omagic' sets the NMAGIC flag on the output.
+can precede the option name; for example, '-trace-symbol' and
+'--trace-symbol' are equivalent.  Note--there is one exception to this
+rule.  Multiple letter options that start with a lower case 'o' can only
+be preceded by two dashes.  This is to reduce confusion with the '-o'
+option.  So for example '-omagic' sets the output file name to 'magic'
+whereas '--omagic' sets the NMAGIC flag on the output.
 
    Arguments to multiple-letter options must either be separated from
 the option name by an equals sign, or be given as separate arguments
 immediately following the option that requires them.  For example,
-`--trace-symbol foo' and `--trace-symbol=foo' are equivalent.  Unique
+'--trace-symbol foo' and '--trace-symbol=foo' are equivalent.  Unique
 abbreviations of the names of multiple-letter options are accepted.
 
    Note--if the linker is being invoked indirectly, via a compiler
-driver (e.g. `gcc') then all the linker command line options should be
-prefixed by `-Wl,' (or whatever is appropriate for the particular
+driver (e.g.  'gcc') then all the linker command line options should be
+prefixed by '-Wl,' (or whatever is appropriate for the particular
 compiler driver) like this:
 
        gcc -Wl,--start-group foo.o bar.o -Wl,--end-group
@@ -178,172 +172,171 @@ the joined forms of both single- and multiple-letter options, such as:
    Here is a table of the generic command line switches accepted by the
 GNU linker:
 
-`@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 KEYWORD'
+'-a KEYWORD'
      This option is supported for HP/UX compatibility.  The KEYWORD
-     argument must be one of the strings `archive', `shared', or
-     `default'.  `-aarchive' is functionally equivalent to `-Bstatic',
+     argument must be one of the strings 'archive', 'shared', or
+     'default'.  '-aarchive' is functionally equivalent to '-Bstatic',
      and the other two keywords are functionally equivalent to
-     `-Bdynamic'.  This option may be used any number of times.
+     '-Bdynamic'.  This option may be used any number of times.
 
-`--audit AUDITLIB'
-     Adds AUDITLIB to the `DT_AUDIT' entry of the dynamic section.
+'--audit AUDITLIB'
+     Adds AUDITLIB to the 'DT_AUDIT' entry of the dynamic section.
      AUDITLIB is not checked for existence, nor will it use the
      DT_SONAME specified in the library.  If specified multiple times
-     `DT_AUDIT' will contain a colon separated list of audit interfaces
-     to use. If the linker finds an object with an audit entry while
+     'DT_AUDIT' will contain a colon separated list of audit interfaces
+     to use.  If the linker finds an object with an audit entry while
      searching for shared libraries, it will add a corresponding
-     `DT_DEPAUDIT' entry in the output file.  This option is only
+     'DT_DEPAUDIT' entry in the output file.  This option is only
      meaningful on ELF platforms supporting the rtld-audit interface.
 
-`-A ARCHITECTURE'
-`--architecture=ARCHITECTURE'
-     In the current release of `ld', this option is useful only for the
-     Intel 960 family of architectures.  In that `ld' configuration, the
-     ARCHITECTURE argument identifies the particular architecture in
-     the 960 family, enabling some safeguards and modifying the
-     archive-library search path.  *Note `ld' and the Intel 960 family:
+'-A ARCHITECTURE'
+'--architecture=ARCHITECTURE'
+     In the current release of 'ld', this option is useful only for the
+     Intel 960 family of architectures.  In that 'ld' configuration, the
+     ARCHITECTURE argument identifies the particular architecture in the
+     960 family, enabling some safeguards and modifying the
+     archive-library search path.  *Note 'ld' and the Intel 960 family:
      i960, for details.
 
-     Future releases of `ld' may support similar functionality for
-     other architecture families.
+     Future releases of 'ld' may support similar functionality for other
+     architecture families.
 
-`-b INPUT-FORMAT'
-`--format=INPUT-FORMAT'
-     `ld' may be configured to support more than one kind of object
-     file.  If your `ld' is configured this way, you can use the `-b'
+'-b INPUT-FORMAT'
+'--format=INPUT-FORMAT'
+     'ld' may be configured to support more than one kind of object
+     file.  If your 'ld' is configured this way, you can use the '-b'
      option to specify the binary format for input object files that
-     follow this option on the command line.  Even when `ld' is
-     configured to support alternative object formats, you don't
-     usually need to specify this, as `ld' should be configured to
-     expect as a default input format the most usual format on each
-     machine.  INPUT-FORMAT is a text string, the name of a particular
-     format supported by the BFD libraries.  (You can list the
-     available binary formats with `objdump -i'.)  *Note BFD::.
+     follow this option on the command line.  Even when 'ld' is
+     configured to support alternative object formats, you don't usually
+     need to specify this, as 'ld' should be configured to expect as a
+     default input format the most usual format on each machine.
+     INPUT-FORMAT is a text string, the name of a particular format
+     supported by the BFD libraries.  (You can list the available binary
+     formats with 'objdump -i'.)  *Note BFD::.
 
      You may want to use this option if you are linking files with an
-     unusual binary format.  You can also use `-b' to switch formats
+     unusual binary format.  You can also use '-b' to switch formats
      explicitly (when linking object files of different formats), by
-     including `-b INPUT-FORMAT' before each group of object files in a
+     including '-b INPUT-FORMAT' before each group of object files in a
      particular format.
 
      The default format is taken from the environment variable
-     `GNUTARGET'.  *Note Environment::.  You can also define the input
-     format from a script, using the command `TARGET'; see *note Format
+     'GNUTARGET'.  *Note Environment::.  You can also define the input
+     format from a script, using the command 'TARGET'; see *note Format
      Commands::.
 
-`-c MRI-COMMANDFILE'
-`--mri-script=MRI-COMMANDFILE'
-     For compatibility with linkers produced by MRI, `ld' accepts script
+'-c MRI-COMMANDFILE'
+'--mri-script=MRI-COMMANDFILE'
+     For compatibility with linkers produced by MRI, 'ld' accepts script
      files written in an alternate, restricted command language,
-     described in *note MRI Compatible Script Files: MRI.  Introduce
-     MRI script files with the option `-c'; use the `-T' option to run
-     linker scripts written in the general-purpose `ld' scripting
-     language.  If MRI-CMDFILE does not exist, `ld' looks for it in the
-     directories specified by any `-L' options.
-
-`-d'
-`-dc'
-`-dp'
+     described in *note MRI Compatible Script Files: MRI.  Introduce MRI
+     script files with the option '-c'; use the '-T' option to run
+     linker scripts written in the general-purpose 'ld' scripting
+     language.  If MRI-CMDFILE does not exist, 'ld' looks for it in the
+     directories specified by any '-L' options.
+
+'-d'
+'-dc'
+'-dp'
      These three options are equivalent; multiple forms are supported
      for compatibility with other linkers.  They assign space to common
-     symbols even if a relocatable output file is specified (with
-     `-r').  The script command `FORCE_COMMON_ALLOCATION' has the same
-     effect.  *Note Miscellaneous Commands::.
+     symbols even if a relocatable output file is specified (with '-r').
+     The script command 'FORCE_COMMON_ALLOCATION' has the same effect.
+     *Note Miscellaneous Commands::.
 
-`--depaudit AUDITLIB'
-`-P AUDITLIB'
-     Adds AUDITLIB to the `DT_DEPAUDIT' entry of the dynamic section.
+'--depaudit AUDITLIB'
+'-P AUDITLIB'
+     Adds AUDITLIB to the 'DT_DEPAUDIT' entry of the dynamic section.
      AUDITLIB is not checked for existence, nor will it use the
      DT_SONAME specified in the library.  If specified multiple times
-     `DT_DEPAUDIT' will contain a colon separated list of audit
-     interfaces to use.  This option is only meaningful on ELF
-     platforms supporting the rtld-audit interface.  The -P option is
-     provided for Solaris compatibility.
+     'DT_DEPAUDIT' will contain a colon separated list of audit
+     interfaces to use.  This option is only meaningful on ELF platforms
+     supporting the rtld-audit interface.  The -P option is provided for
+     Solaris compatibility.
 
-`-e ENTRY'
-`--entry=ENTRY'
+'-e ENTRY'
+'--entry=ENTRY'
      Use ENTRY as the explicit symbol for beginning execution of your
      program, rather than the default entry point.  If there is no
      symbol named ENTRY, the linker will try to parse ENTRY as a number,
      and use that as the entry address (the number will be interpreted
-     in base 10; you may use a leading `0x' for base 16, or a leading
-     `0' for base 8).  *Note Entry Point::, for a discussion of defaults
+     in base 10; you may use a leading '0x' for base 16, or a leading
+     '0' for base 8).  *Note Entry Point::, for a discussion of defaults
      and other ways of specifying the entry point.
 
-`--exclude-libs LIB,LIB,...'
-     Specifies a list of archive libraries from which symbols should
-     not be automatically exported.  The library names may be delimited
-     by commas or colons.  Specifying `--exclude-libs ALL' excludes
-     symbols in all archive libraries from automatic export.  This
-     option is available only for the i386 PE targeted port of the
-     linker and for ELF targeted ports.  For i386 PE, symbols
-     explicitly listed in a .def file are still exported, regardless of
-     this option.  For ELF targeted ports, symbols affected by this
-     option will be treated as hidden.
-
-`--exclude-modules-for-implib MODULE,MODULE,...'
+'--exclude-libs LIB,LIB,...'
+     Specifies a list of archive libraries from which symbols should not
+     be automatically exported.  The library names may be delimited by
+     commas or colons.  Specifying '--exclude-libs ALL' excludes symbols
+     in all archive libraries from automatic export.  This option is
+     available only for the i386 PE targeted port of the linker and for
+     ELF targeted ports.  For i386 PE, symbols explicitly listed in a
+     .def file are still exported, regardless of this option.  For ELF
+     targeted ports, symbols affected by this option will be treated as
+     hidden.
+
+'--exclude-modules-for-implib MODULE,MODULE,...'
      Specifies a list of object files or archive members, from which
      symbols should not be automatically exported, but which should be
-     copied wholesale into the import library being generated during
-     the link.  The module names may be delimited by commas or colons,
-     and must match exactly the filenames used by `ld' to open the
-     files; for archive members, this is simply the member name, but
-     for object files the name listed must include and match precisely
-     any path used to specify the input file on the linker's
-     command-line.  This option is available only for the i386 PE
-     targeted port of the linker.  Symbols explicitly listed in a .def
-     file are still exported, regardless of this option.
-
-`-E'
-`--export-dynamic'
-`--no-export-dynamic'
-     When creating a dynamically linked executable, using the `-E'
-     option or the `--export-dynamic' option causes the linker to add
+     copied wholesale into the import library being generated during the
+     link.  The module names may be delimited by commas or colons, and
+     must match exactly the filenames used by 'ld' to open the files;
+     for archive members, this is simply the member name, but for object
+     files the name listed must include and match precisely any path
+     used to specify the input file on the linker's command-line.  This
+     option is available only for the i386 PE targeted port of the
+     linker.  Symbols explicitly listed in a .def file are still
+     exported, regardless of this option.
+
+'-E'
+'--export-dynamic'
+'--no-export-dynamic'
+     When creating a dynamically linked executable, using the '-E'
+     option or the '--export-dynamic' option causes the linker to add
      all symbols to the dynamic symbol table.  The dynamic symbol table
-     is the set of symbols which are visible from dynamic objects at
-     run time.
+     is the set of symbols which are visible from dynamic objects at run
+     time.
 
      If you do not use either of these options (or use the
-     `--no-export-dynamic' option to restore the default behavior), the
-     dynamic symbol table will normally contain only those symbols
-     which are referenced by some dynamic object mentioned in the link.
+     '--no-export-dynamic' option to restore the default behavior), the
+     dynamic symbol table will normally contain only those symbols which
+     are referenced by some dynamic object mentioned in the link.
 
-     If you use `dlopen' to load a dynamic object which needs to refer
+     If you use 'dlopen' to load a dynamic object which needs to refer
      back to the symbols defined by the program, rather than some other
      dynamic object, then you will probably need to use this option when
      linking the program itself.
 
-     You can also use the dynamic list to control what symbols should
-     be added to the dynamic symbol table if the output format supports
-     it.  See the description of `--dynamic-list'.
+     You can also use the dynamic list to control what symbols should be
+     added to the dynamic symbol table if the output format supports it.
+     See the description of '--dynamic-list'.
 
      Note that this option is specific to ELF targeted ports.  PE
-     targets support a similar function to export all symbols from a
-     DLL or EXE; see the description of `--export-all-symbols' below.
+     targets support a similar function to export all symbols from a DLL
+     or EXE; see the description of '--export-all-symbols' below.
 
-`-EB'
+'-EB'
      Link big-endian objects.  This affects the default output format.
 
-`-EL'
+'-EL'
      Link little-endian objects.  This affects the default output
      format.
 
-`-f NAME'
-`--auxiliary=NAME'
+'-f NAME'
+'--auxiliary=NAME'
      When creating an ELF shared object, set the internal DT_AUXILIARY
      field to the specified name.  This tells the dynamic linker that
      the symbol table of the shared object should be used as an
@@ -363,13 +356,12 @@ GNU linker:
      entries will be created in the order in which they appear on the
      command line.
 
-`-F NAME'
-`--filter=NAME'
+'-F NAME'
+'--filter=NAME'
      When creating an ELF shared object, set the internal DT_FILTER
      field to the specified name.  This tells the dynamic linker that
-     the symbol table of the shared object which is being created
-     should be used as a filter on the symbol table of the shared
-     object NAME.
+     the symbol table of the shared object which is being created should
+     be used as a filter on the symbol table of the shared object NAME.
 
      If you later link a program against this filter object, then, when
      you run the program, the dynamic linker will see the DT_FILTER
@@ -379,128 +371,124 @@ GNU linker:
      filter object can be used to select a subset of the symbols
      provided by the object NAME.
 
-     Some older linkers used the `-F' option throughout a compilation
+     Some older linkers used the '-F' option throughout a compilation
      toolchain for specifying object-file format for both input and
-     output object files.  The GNU linker uses other mechanisms for
-     this purpose: the `-b', `--format', `--oformat' options, the
-     `TARGET' command in linker scripts, and the `GNUTARGET'
-     environment variable.  The GNU linker will ignore the `-F' option
-     when not creating an ELF shared object.
+     output object files.  The GNU linker uses other mechanisms for this
+     purpose: the '-b', '--format', '--oformat' options, the 'TARGET'
+     command in linker scripts, and the 'GNUTARGET' environment
+     variable.  The GNU linker will ignore the '-F' option when not
+     creating an ELF shared object.
 
-`-fini=NAME'
+'-fini=NAME'
      When creating an ELF executable or shared object, call NAME when
      the executable or shared object is unloaded, by setting DT_FINI to
-     the address of the function.  By default, the linker uses `_fini'
+     the address of the function.  By default, the linker uses '_fini'
      as the function to call.
 
-`-g'
+'-g'
      Ignored.  Provided for compatibility with other tools.
 
-`-G VALUE'
-`--gpsize=VALUE'
+'-G VALUE'
+'--gpsize=VALUE'
      Set the maximum size of objects to be optimized using the GP
      register to SIZE.  This is only meaningful for object file formats
-     such as MIPS ECOFF which supports putting large and small objects
-     into different sections.  This is ignored for other object file
-     formats.
+     such as MIPS ELF that support putting large and small objects into
+     different sections.  This is ignored for other object file formats.
 
-`-h NAME'
-`-soname=NAME'
+'-h NAME'
+'-soname=NAME'
      When creating an ELF shared object, set the internal DT_SONAME
      field to the specified name.  When an executable is linked with a
-     shared object which has a DT_SONAME field, then when the
-     executable is run the dynamic linker will attempt to load the
-     shared object specified by the DT_SONAME field rather than the
-     using the file name given to the linker.
+     shared object which has a DT_SONAME field, then when the executable
+     is run the dynamic linker will attempt to load the shared object
+     specified by the DT_SONAME field rather than the using the file
+     name given to the linker.
 
-`-i'
-     Perform an incremental link (same as option `-r').
+'-i'
+     Perform an incremental link (same as option '-r').
 
-`-init=NAME'
+'-init=NAME'
      When creating an ELF executable or shared object, call NAME when
      the executable or shared object is loaded, by setting DT_INIT to
-     the address of the function.  By default, the linker uses `_init'
+     the address of the function.  By default, the linker uses '_init'
      as the function to call.
 
-`-l NAMESPEC'
-`--library=NAMESPEC'
-     Add the archive or object file specified by NAMESPEC to the list
-     of files to link.  This option may be used any number of times.
-     If NAMESPEC is of the form `:FILENAME', `ld' will search the
-     library path for a file called FILENAME, otherwise it will search
-     the library path for a file called `libNAMESPEC.a'.
-
-     On systems which support shared libraries, `ld' may also search for
-     files other than `libNAMESPEC.a'.  Specifically, on ELF and SunOS
-     systems, `ld' will search a directory for a library called
-     `libNAMESPEC.so' before searching for one called `libNAMESPEC.a'.
-     (By convention, a `.so' extension indicates a shared library.)
-     Note that this behavior does not apply to `:FILENAME', which
-     always specifies a file called FILENAME.
+'-l NAMESPEC'
+'--library=NAMESPEC'
+     Add the archive or object file specified by NAMESPEC to the list of
+     files to link.  This option may be used any number of times.  If
+     NAMESPEC is of the form ':FILENAME', 'ld' will search the library
+     path for a file called FILENAME, otherwise it will search the
+     library path for a file called 'libNAMESPEC.a'.
+
+     On systems which support shared libraries, 'ld' may also search for
+     files other than 'libNAMESPEC.a'.  Specifically, on ELF and SunOS
+     systems, 'ld' will search a directory for a library called
+     'libNAMESPEC.so' before searching for one called 'libNAMESPEC.a'.
+     (By convention, a '.so' extension indicates a shared library.)
+     Note that this behavior does not apply to ':FILENAME', which always
+     specifies a file called FILENAME.
 
      The linker will search an archive only once, at the location where
      it is specified on the command line.  If the archive defines a
-     symbol which was undefined in some object which appeared before
-     the archive on the command line, the linker will include the
-     appropriate file(s) from the archive.  However, an undefined
-     symbol in an object appearing later on the command line will not
-     cause the linker to search the archive again.
+     symbol which was undefined in some object which appeared before the
+     archive on the command line, the linker will include the
+     appropriate file(s) from the archive.  However, an undefined symbol
+     in an object appearing later on the command line will not cause the
+     linker to search the archive again.
 
-     See the `-(' option for a way to force the linker to search
+     See the '-(' option for a way to force the linker to search
      archives multiple times.
 
      You may list the same archive multiple times on the command line.
 
      This type of archive searching is standard for Unix linkers.
-     However, if you are using `ld' on AIX, note that it is different
+     However, if you are using 'ld' on AIX, note that it is different
      from the behaviour of the AIX linker.
 
-`-L SEARCHDIR'
-`--library-path=SEARCHDIR'
-     Add path SEARCHDIR to the list of paths that `ld' will search for
-     archive libraries and `ld' control scripts.  You may use this
+'-L SEARCHDIR'
+'--library-path=SEARCHDIR'
+     Add path SEARCHDIR to the list of paths that 'ld' will search for
+     archive libraries and 'ld' control scripts.  You may use this
      option any number of times.  The directories are searched in the
-     order in which they are specified on the command line.
-     Directories specified on the command line are searched before the
-     default directories.  All `-L' options apply to all `-l' options,
-     regardless of the order in which the options appear.  `-L' options
-     do not affect how `ld' searches for a linker script unless `-T'
+     order in which they are specified on the command line.  Directories
+     specified on the command line are searched before the default
+     directories.  All '-L' options apply to all '-l' options,
+     regardless of the order in which the options appear.  '-L' options
+     do not affect how 'ld' searches for a linker script unless '-T'
      option is specified.
 
-     If SEARCHDIR begins with `=', then the `=' will be replaced by the
+     If SEARCHDIR begins with '=', then the '=' will be replaced by the
      "sysroot prefix", a path specified when the linker is configured.
 
      The default set of paths searched (without being specified with
-     `-L') depends on which emulation mode `ld' is using, and in some
+     '-L') depends on which emulation mode 'ld' is using, and in some
      cases also on how it was configured.  *Note Environment::.
 
      The paths can also be specified in a link script with the
-     `SEARCH_DIR' command.  Directories specified this way are searched
+     'SEARCH_DIR' command.  Directories specified this way are searched
      at the point in which the linker script appears in the command
      line.
 
-`-m EMULATION'
+'-m EMULATION'
      Emulate the EMULATION linker.  You can list the available
-     emulations with the `--verbose' or `-V' options.
+     emulations with the '--verbose' or '-V' options.
 
-     If the `-m' option is not used, the emulation is taken from the
-     `LDEMULATION' environment variable, if that is defined.
+     If the '-m' option is not used, the emulation is taken from the
+     'LDEMULATION' environment variable, if that is defined.
 
      Otherwise, the default emulation depends upon how the linker was
      configured.
 
-`-M'
-`--print-map'
+'-M'
+'--print-map'
      Print a link map to the standard output.  A link map provides
      information about the link, including the following:
 
         * Where object files are mapped into memory.
-
         * How common symbols are allocated.
-
         * All archive members included in the link, with a mention of
           the symbol which caused the archive member to be brought in.
-
         * The values assigned to symbols.
 
           Note - symbols whose values are computed by an expression
@@ -508,184 +496,183 @@ GNU linker:
           symbol may not have correct result displayed in the link map.
           This is because the linker discards intermediate results and
           only retains the final value of an expression.  Under such
-          circumstances the linker will display the final value
-          enclosed by square brackets.  Thus for example a linker
-          script containing:
+          circumstances the linker will display the final value enclosed
+          by square brackets.  Thus for example a linker script
+          containing:
 
                   foo = 1
                   foo = foo * 4
                   foo = foo + 8
 
-          will produce the following output in the link map if the `-M'
+          will produce the following output in the link map if the '-M'
           option is used:
 
                   0x00000001                foo = 0x1
                   [0x0000000c]                foo = (foo * 0x4)
                   [0x0000000c]                foo = (foo + 0x8)
 
-          See *note Expressions:: for more information about
-          expressions in linker scripts.
+          See *note Expressions:: for more information about expressions
+          in linker scripts.
 
-`-n'
-`--nmagic'
+'-n'
+'--nmagic'
      Turn off page alignment of sections, and disable linking against
      shared libraries.  If the output format supports Unix style magic
-     numbers, mark the output as `NMAGIC'.
+     numbers, mark the output as 'NMAGIC'.
 
-`-N'
-`--omagic'
+'-N'
+'--omagic'
      Set the text and data sections to be readable and writable.  Also,
      do not page-align the data segment, and disable linking against
      shared libraries.  If the output format supports Unix style magic
-     numbers, mark the output as `OMAGIC'. Note: Although a writable
-     text section is allowed for PE-COFF targets, it does not conform
-     to the format specification published by Microsoft.
+     numbers, mark the output as 'OMAGIC'.  Note: Although a writable
+     text section is allowed for PE-COFF targets, it does not conform to
+     the format specification published by Microsoft.
 
-`--no-omagic'
-     This option negates most of the effects of the `-N' option.  It
+'--no-omagic'
+     This option negates most of the effects of the '-N' option.  It
      sets the text section to be read-only, and forces the data segment
      to be page-aligned.  Note - this option does not enable linking
-     against shared libraries.  Use `-Bdynamic' for this.
+     against shared libraries.  Use '-Bdynamic' for this.
 
-`-o OUTPUT'
-`--output=OUTPUT'
-     Use OUTPUT as the name for the program produced by `ld'; if this
-     option is not specified, the name `a.out' is used by default.  The
-     script command `OUTPUT' can also specify the output file name.
+'-o OUTPUT'
+'--output=OUTPUT'
+     Use OUTPUT as the name for the program produced by 'ld'; if this
+     option is not specified, the name 'a.out' is used by default.  The
+     script command 'OUTPUT' can also specify the output file name.
 
-`-O LEVEL'
-     If LEVEL is a numeric values greater than zero `ld' optimizes the
+'-O LEVEL'
+     If LEVEL is a numeric values greater than zero 'ld' optimizes the
      output.  This might take significantly longer and therefore
      probably should only be enabled for the final binary.  At the
      moment this option only affects ELF shared library generation.
      Future releases of the linker may make more use of this option.
-     Also currently there is no difference in the linker's behaviour
-     for different non-zero values of this option.  Again this may
-     change with future releases.
+     Also currently there is no difference in the linker's behaviour for
+     different non-zero values of this option.  Again this may change
+     with future releases.
 
-`-q'
-`--emit-relocs'
+'-q'
+'--emit-relocs'
      Leave relocation sections and contents in fully linked executables.
-     Post link analysis and optimization tools may need this
-     information in order to perform correct modifications of
-     executables.  This results in larger executables.
+     Post link analysis and optimization tools may need this information
+     in order to perform correct modifications of executables.  This
+     results in larger executables.
 
      This option is currently only supported on ELF platforms.
 
-`--force-dynamic'
+'--force-dynamic'
      Force the output file to have dynamic sections.  This option is
      specific to VxWorks targets.
 
-`-r'
-`--relocatable'
-     Generate relocatable output--i.e., generate an output file that
-     can in turn serve as input to `ld'.  This is often called "partial
+'-r'
+'--relocatable'
+     Generate relocatable output--i.e., generate an output file that can
+     in turn serve as input to 'ld'.  This is often called "partial
      linking".  As a side effect, in environments that support standard
      Unix magic numbers, this option also sets the output file's magic
-     number to `OMAGIC'.  If this option is not specified, an absolute
+     number to 'OMAGIC'.  If this option is not specified, an absolute
      file is produced.  When linking C++ programs, this option _will
-     not_ resolve references to constructors; to do that, use `-Ur'.
+     not_ resolve references to constructors; to do that, use '-Ur'.
 
      When an input file does not have the same format as the output
-     file, partial linking is only supported if that input file does
-     not contain any relocations.  Different output formats can have
-     further restrictions; for example some `a.out'-based formats do
-     not support partial linking with input files in other formats at
-     all.
+     file, partial linking is only supported if that input file does not
+     contain any relocations.  Different output formats can have further
+     restrictions; for example some 'a.out'-based formats do not support
+     partial linking with input files in other formats at all.
 
-     This option does the same thing as `-i'.
+     This option does the same thing as '-i'.
 
-`-R FILENAME'
-`--just-symbols=FILENAME'
+'-R FILENAME'
+'--just-symbols=FILENAME'
      Read symbol names and their addresses from FILENAME, but do not
      relocate it or include it in the output.  This allows your output
      file to refer symbolically to absolute locations of memory defined
      in other programs.  You may use this option more than once.
 
-     For compatibility with other ELF linkers, if the `-R' option is
+     For compatibility with other ELF linkers, if the '-R' option is
      followed by a directory name, rather than a file name, it is
-     treated as the `-rpath' option.
+     treated as the '-rpath' option.
 
-`-s'
-`--strip-all'
+'-s'
+'--strip-all'
      Omit all symbol information from the output file.
 
-`-S'
-`--strip-debug'
+'-S'
+'--strip-debug'
      Omit debugger symbol information (but not all symbols) from the
      output file.
 
-`-t'
-`--trace'
-     Print the names of the input files as `ld' processes them.
+'-t'
+'--trace'
+     Print the names of the input files as 'ld' processes them.
 
-`-T SCRIPTFILE'
-`--script=SCRIPTFILE'
-     Use SCRIPTFILE as the linker script.  This script replaces `ld''s
+'-T SCRIPTFILE'
+'--script=SCRIPTFILE'
+     Use SCRIPTFILE as the linker script.  This script replaces 'ld''s
      default linker script (rather than adding to it), so COMMANDFILE
      must specify everything necessary to describe the output file.
      *Note Scripts::.  If SCRIPTFILE does not exist in the current
-     directory, `ld' looks for it in the directories specified by any
-     preceding `-L' options.  Multiple `-T' options accumulate.
+     directory, 'ld' looks for it in the directories specified by any
+     preceding '-L' options.  Multiple '-T' options accumulate.
 
-`-dT SCRIPTFILE'
-`--default-script=SCRIPTFILE'
+'-dT SCRIPTFILE'
+'--default-script=SCRIPTFILE'
      Use SCRIPTFILE as the default linker script.  *Note Scripts::.
 
-     This option is similar to the `--script' option except that
+     This option is similar to the '--script' option except that
      processing of the script is delayed until after the rest of the
      command line has been processed.  This allows options placed after
-     the `--default-script' option on the command line to affect the
+     the '--default-script' option on the command line to affect the
      behaviour of the linker script, which can be important when the
-     linker command line cannot be directly controlled by the user.
-     (eg because the command line is being constructed by another tool,
-     such as `gcc').
+     linker command line cannot be directly controlled by the user.  (eg
+     because the command line is being constructed by another tool, such
+     as 'gcc').
 
-`-u SYMBOL'
-`--undefined=SYMBOL'
+'-u SYMBOL'
+'--undefined=SYMBOL'
      Force SYMBOL to be entered in the output file as an undefined
      symbol.  Doing this may, for example, trigger linking of additional
-     modules from standard libraries.  `-u' may be repeated with
+     modules from standard libraries.  '-u' may be repeated with
      different option arguments to enter additional undefined symbols.
-     This option is equivalent to the `EXTERN' linker script command.
+     This option is equivalent to the 'EXTERN' linker script command.
 
-`-Ur'
+'-Ur'
      For anything other than C++ programs, this option is equivalent to
-     `-r': it generates relocatable output--i.e., an output file that
-     can in turn serve as input to `ld'.  When linking C++ programs,
-     `-Ur' _does_ resolve references to constructors, unlike `-r'.  It
-     does not work to use `-Ur' on files that were themselves linked
-     with `-Ur'; once the constructor table has been built, it cannot
-     be added to.  Use `-Ur' only for the last partial link, and `-r'
-     for the others.
-
-`--unique[=SECTION]'
+     '-r': it generates relocatable output--i.e., an output file that
+     can in turn serve as input to 'ld'.  When linking C++ programs,
+     '-Ur' _does_ resolve references to constructors, unlike '-r'.  It
+     does not work to use '-Ur' on files that were themselves linked
+     with '-Ur'; once the constructor table has been built, it cannot be
+     added to.  Use '-Ur' only for the last partial link, and '-r' for
+     the others.
+
+'--unique[=SECTION]'
      Creates a separate output section for every input section matching
      SECTION, or if the optional wildcard SECTION argument is missing,
      for every orphan input section.  An orphan section is one not
      specifically mentioned in a linker script.  You may use this option
-     multiple times on the command line;  It prevents the normal
-     merging of input sections with the same name, overriding output
-     section assignments in a linker script.
-
-`-v'
-`--version'
-`-V'
-     Display the version number for `ld'.  The `-V' option also lists
+     multiple times on the command line; It prevents the normal merging
+     of input sections with the same name, overriding output section
+     assignments in a linker script.
+
+'-v'
+'--version'
+'-V'
+     Display the version number for 'ld'.  The '-V' option also lists
      the supported emulations.
 
-`-x'
-`--discard-all'
+'-x'
+'--discard-all'
      Delete all local symbols.
 
-`-X'
-`--discard-locals'
+'-X'
+'--discard-locals'
      Delete all temporary local symbols.  (These symbols start with
-     system-specific local label prefixes, typically `.L' for ELF
-     systems or `L' for traditional a.out systems.)
+     system-specific local label prefixes, typically '.L' for ELF
+     systems or 'L' for traditional a.out systems.)
 
-`-y SYMBOL'
-`--trace-symbol=SYMBOL'
+'-y SYMBOL'
+'--trace-symbol=SYMBOL'
      Print the name of each linked file in which SYMBOL appears.  This
      option may be given any number of times.  On many systems it is
      necessary to prepend an underscore.
@@ -693,29 +680,30 @@ GNU linker:
      This option is useful when you have an undefined symbol in your
      link but don't know where the reference is coming from.
 
-`-Y PATH'
+'-Y PATH'
      Add PATH to the default library search path.  This option exists
      for Solaris compatibility.
 
-`-z KEYWORD'
+'-z KEYWORD'
      The recognized keywords are:
-    `combreloc'
+
+     'combreloc'
           Combines multiple reloc sections and sorts them to make
           dynamic symbol lookup caching possible.
 
-    `defs'
+     'defs'
           Disallows undefined symbols in object files.  Undefined
           symbols in shared libraries are still allowed.
 
-    `execstack'
+     'execstack'
           Marks the object as requiring executable stack.
 
-    `global'
+     'global'
           This option is only meaningful when building a shared object.
           It makes the symbols defined by this shared object available
           for symbol resolution of subsequently loaded libraries.
 
-    `initfirst'
+     'initfirst'
           This option is only meaningful when building a shared object.
           It marks the object so that its runtime initialization will
           occur before the runtime initialization of any other objects
@@ -723,181 +711,175 @@ GNU linker:
           runtime finalization of the object will occur after the
           runtime finalization of any other objects.
 
-    `interpose'
+     'interpose'
           Marks the object that its symbol table interposes before all
           symbols but the primary executable.
 
-    `lazy'
+     'lazy'
           When generating an executable or shared library, mark it to
           tell the dynamic linker to defer function call resolution to
           the point when the function is called (lazy binding), rather
           than at load time.  Lazy binding is the default.
 
-    `loadfltr'
-          Marks  the object that its filters be processed immediately at
+     'loadfltr'
+          Marks the object that its filters be processed immediately at
           runtime.
 
-    `muldefs'
+     'muldefs'
           Allows multiple definitions.
 
-    `nocombreloc'
+     'nocombreloc'
           Disables multiple reloc sections combining.
 
-    `nocopyreloc'
+     'nocopyreloc'
           Disables production of copy relocs.
 
-    `nodefaultlib'
+     'nodefaultlib'
           Marks the object that the search for dependencies of this
           object will ignore any default library search paths.
 
-    `nodelete'
+     'nodelete'
           Marks the object shouldn't be unloaded at runtime.
 
-    `nodlopen'
-          Marks the object not available to `dlopen'.
+     'nodlopen'
+          Marks the object not available to 'dlopen'.
 
-    `nodump'
-          Marks the object can not be dumped by `dldump'.
+     'nodump'
+          Marks the object can not be dumped by 'dldump'.
 
-    `noexecstack'
+     'noexecstack'
           Marks the object as not requiring executable stack.
 
-    `norelro'
-          Don't create an ELF `PT_GNU_RELRO' segment header in the
+     'norelro'
+          Don't create an ELF 'PT_GNU_RELRO' segment header in the
           object.
 
-    `now'
+     'now'
           When generating an executable or shared library, mark it to
           tell the dynamic linker to resolve all symbols when the
           program is started, or when the shared library is linked to
-          using dlopen, instead of deferring function call resolution
-          to the point when the function is first called.
+          using dlopen, instead of deferring function call resolution to
+          the point when the function is first called.
 
-    `origin'
+     'origin'
           Marks the object may contain $ORIGIN.
 
-    `relro'
-          Create an ELF `PT_GNU_RELRO' segment header in the object.
-
-    `nosecondary'
-          Convert secondary symbols to weak symbols when generating a
-          shared library.
+     'relro'
+          Create an ELF 'PT_GNU_RELRO' segment header in the object.
 
-    `max-page-size=VALUE'
+     'max-page-size=VALUE'
           Set the emulation maximum page size to VALUE.
 
-    `common-page-size=VALUE'
+     'common-page-size=VALUE'
           Set the emulation common page size to VALUE.
 
-    `stack-size=VALUE'
-          Specify a stack size for in an ELF `PT_GNU_STACK' segment.
+     'stack-size=VALUE'
+          Specify a stack size for in an ELF 'PT_GNU_STACK' segment.
           Specifying zero will override any default non-zero sized
-          `PT_GNU_STACK' segment creation.
-
+          'PT_GNU_STACK' segment creation.
 
      Other keywords are ignored for Solaris compatibility.
 
-`-( ARCHIVES -)'
-`--start-group ARCHIVES --end-group'
-     The ARCHIVES should be a list of archive files.  They may be
-     either explicit file names, or `-l' options.
+'-( ARCHIVES -)'
+'--start-group ARCHIVES --end-group'
+     The ARCHIVES should be a list of archive files.  They may be either
+     explicit file names, or '-l' options.
 
      The specified archives are searched repeatedly until no new
-     undefined references are created.  Normally, an archive is
-     searched only once in the order that it is specified on the
-     command line.  If a symbol in that archive is needed to resolve an
-     undefined symbol referred to by an object in an archive that
-     appears later on the command line, the linker would not be able to
-     resolve that reference.  By grouping the archives, they all be
-     searched repeatedly until all possible references are resolved.
+     undefined references are created.  Normally, an archive is searched
+     only once in the order that it is specified on the command line.
+     If a symbol in that archive is needed to resolve an undefined
+     symbol referred to by an object in an archive that appears later on
+     the command line, the linker would not be able to resolve that
+     reference.  By grouping the archives, they all be searched
+     repeatedly until all possible references are resolved.
 
      Using this option has a significant performance cost.  It is best
      to use it only when there are unavoidable circular references
      between two or more archives.
 
-`--accept-unknown-input-arch'
-`--no-accept-unknown-input-arch'
+'--accept-unknown-input-arch'
+'--no-accept-unknown-input-arch'
      Tells the linker to accept input files whose architecture cannot be
      recognised.  The assumption is that the user knows what they are
      doing and deliberately wants to link in these unknown input files.
      This was the default behaviour of the linker, before release 2.14.
      The default behaviour from release 2.14 onwards is to reject such
-     input files, and so the `--accept-unknown-input-arch' option has
+     input files, and so the '--accept-unknown-input-arch' option has
      been added to restore the old behaviour.
 
-`--as-needed'
-`--no-as-needed'
+'--as-needed'
+'--no-as-needed'
      This option affects ELF DT_NEEDED tags for dynamic libraries
-     mentioned on the command line after the `--as-needed' option.
+     mentioned on the command line after the '--as-needed' option.
      Normally the linker will add a DT_NEEDED tag for each dynamic
      library mentioned on the command line, regardless of whether the
-     library is actually needed or not.  `--as-needed' causes a
+     library is actually needed or not.  '--as-needed' causes a
      DT_NEEDED tag to only be emitted for a library that _at that point
-     in the link_ satisfies a non-weak undefined symbol reference from
-     a regular object file or, if the library is not found in the
+     in the link_ satisfies a non-weak undefined symbol reference from a
+     regular object file or, if the library is not found in the
      DT_NEEDED lists of other libraries, a non-weak undefined symbol
      reference from another dynamic library.  Object files or libraries
      appearing on the command line _after_ the library in question do
      not affect whether the library is seen as needed.  This is similar
      to the rules for extraction of object files from archives.
-     `--no-as-needed' restores the default behaviour.
+     '--no-as-needed' restores the default behaviour.
 
-`--add-needed'
-`--no-add-needed'
+'--add-needed'
+'--no-add-needed'
      These two options have been deprecated because of the similarity of
-     their names to the `--as-needed' and `--no-as-needed' options.
-     They have been replaced by `--copy-dt-needed-entries' and
-     `--no-copy-dt-needed-entries'.
+     their names to the '--as-needed' and '--no-as-needed' options.
+     They have been replaced by '--copy-dt-needed-entries' and
+     '--no-copy-dt-needed-entries'.
 
-`-assert KEYWORD'
+'-assert KEYWORD'
      This option is ignored for SunOS compatibility.
 
-`-Bdynamic'
-`-dy'
-`-call_shared'
+'-Bdynamic'
+'-dy'
+'-call_shared'
      Link against dynamic libraries.  This is only meaningful on
-     platforms for which shared libraries are supported.  This option
-     is normally the default on such platforms.  The different variants
-     of this option are for compatibility with various systems.  You
-     may use this option multiple times on the command line: it affects
-     library searching for `-l' options which follow it.
-
-`-Bgroup'
-     Set the `DF_1_GROUP' flag in the `DT_FLAGS_1' entry in the dynamic
+     platforms for which shared libraries are supported.  This option is
+     normally the default on such platforms.  The different variants of
+     this option are for compatibility with various systems.  You may
+     use this option multiple times on the command line: it affects
+     library searching for '-l' options which follow it.
+
+'-Bgroup'
+     Set the 'DF_1_GROUP' flag in the 'DT_FLAGS_1' entry in the dynamic
      section.  This causes the runtime linker to handle lookups in this
      object and its dependencies to be performed only inside the group.
-     `--unresolved-symbols=report-all' is implied.  This option is only
+     '--unresolved-symbols=report-all' is implied.  This option is only
      meaningful on ELF platforms which support shared libraries.
 
-`-Bstatic'
-`-dn'
-`-non_shared'
-`-static'
+'-Bstatic'
+'-dn'
+'-non_shared'
+'-static'
      Do not link against shared libraries.  This is only meaningful on
      platforms for which shared libraries are supported.  The different
-     variants of this option are for compatibility with various
-     systems.  You may use this option multiple times on the command
-     line: it affects library searching for `-l' options which follow
-     it.  This option also implies `--unresolved-symbols=report-all'.
-     This option can be used with `-shared'.  Doing so means that a
-     shared library is being created but that all of the library's
-     external references must be resolved by pulling in entries from
-     static libraries.
-
-`-Bsymbolic'
+     variants of this option are for compatibility with various systems.
+     You may use this option multiple times on the command line: it
+     affects library searching for '-l' options which follow it.  This
+     option also implies '--unresolved-symbols=report-all'.  This option
+     can be used with '-shared'.  Doing so means that a shared library
+     is being created but that all of the library's external references
+     must be resolved by pulling in entries from static libraries.
+
+'-Bsymbolic'
      When creating a shared library, bind references to global symbols
      to the definition within the shared library, if any.  Normally, it
      is possible for a program linked against a shared library to
      override the definition within the shared library.  This option is
      only meaningful on ELF platforms which support shared libraries.
 
-`-Bsymbolic-functions'
+'-Bsymbolic-functions'
      When creating a shared library, bind references to global function
      symbols to the definition within the shared library, if any.  This
      option is only meaningful on ELF platforms which support shared
      libraries.
 
-`--dynamic-list=DYNAMIC-LIST-FILE'
+'--dynamic-list=DYNAMIC-LIST-FILE'
      Specify the name of a dynamic list file to the linker.  This is
      typically used when creating shared libraries to specify a list of
      global symbols whose references shouldn't be bound to the
@@ -910,42 +892,42 @@ GNU linker:
      without scope and node name.  See *note VERSION:: for more
      information.
 
-`--dynamic-list-data'
+'--dynamic-list-data'
      Include all global data symbols to the dynamic list.
 
-`--dynamic-list-cpp-new'
+'--dynamic-list-cpp-new'
      Provide the builtin dynamic list for C++ operator new and delete.
      It is mainly useful for building shared libstdc++.
 
-`--dynamic-list-cpp-typeinfo'
+'--dynamic-list-cpp-typeinfo'
      Provide the builtin dynamic list for C++ runtime type
      identification.
 
-`--check-sections'
-`--no-check-sections'
+'--check-sections'
+'--no-check-sections'
      Asks the linker _not_ to check section addresses after they have
      been assigned to see if there are any overlaps.  Normally the
      linker will perform this check, and if it finds any overlaps it
      will produce suitable error messages.  The linker does know about,
      and does make allowances for sections in overlays.  The default
      behaviour can be restored by using the command line switch
-     `--check-sections'.  Section overlap is not usually checked for
+     '--check-sections'.  Section overlap is not usually checked for
      relocatable links.  You can force checking in that case by using
-     the `--check-sections' option.
+     the '--check-sections' option.
 
-`--copy-dt-needed-entries'
-`--no-copy-dt-needed-entries'
+'--copy-dt-needed-entries'
+'--no-copy-dt-needed-entries'
      This option affects the treatment of dynamic libraries referred to
      by DT_NEEDED tags _inside_ ELF dynamic libraries mentioned on the
      command line.  Normally the linker won't add a DT_NEEDED tag to the
      output binary for each library mentioned in a DT_NEEDED tag in an
-     input dynamic library.  With `--copy-dt-needed-entries' specified
+     input dynamic library.  With '--copy-dt-needed-entries' specified
      on the command line however any dynamic libraries that follow it
-     will have their DT_NEEDED entries added.  The default behaviour
-     can be restored with `--no-copy-dt-needed-entries'.
+     will have their DT_NEEDED entries added.  The default behaviour can
+     be restored with '--no-copy-dt-needed-entries'.
 
      This option also has an effect on the resolution of symbols in
-     dynamic libraries.  With `--copy-dt-needed-entries' dynamic
+     dynamic libraries.  With '--copy-dt-needed-entries' dynamic
      libraries mentioned on the command line will be recursively
      searched, following their DT_NEEDED tags to other libraries, in
      order to resolve symbols required by the output binary.  With the
@@ -953,90 +935,91 @@ GNU linker:
      follow it will stop with the dynamic library itself.  No DT_NEEDED
      links will be traversed to resolve symbols.
 
-`--cref'
+'--cref'
      Output a cross reference table.  If a linker map file is being
      generated, the cross reference table is printed to the map file.
      Otherwise, it is printed on the standard output.
 
      The format of the table is intentionally simple, so that it may be
-     easily processed by a script if necessary.  The symbols are
-     printed out, sorted by name.  For each symbol, a list of file
-     names is given.  If the symbol is defined, the first file listed
-     is the location of the definition.  The remaining files contain
-     references to the symbol.
-
-`--no-define-common'
+     easily processed by a script if necessary.  The symbols are printed
+     out, sorted by name.  For each symbol, a list of file names is
+     given.  If the symbol is defined, the first file listed is the
+     location of the definition.  If the symbol is defined as a common
+     value then any files where this happens appear next.  Finally any
+     files that reference the symbol are listed.
+
+'--no-define-common'
      This option inhibits the assignment of addresses to common symbols.
-     The script command `INHIBIT_COMMON_ALLOCATION' has the same effect.
+     The script command 'INHIBIT_COMMON_ALLOCATION' has the same effect.
      *Note Miscellaneous Commands::.
 
-     The `--no-define-common' option allows decoupling the decision to
+     The '--no-define-common' option allows decoupling the decision to
      assign addresses to Common symbols from the choice of the output
-     file type; otherwise a non-Relocatable output type forces
-     assigning addresses to Common symbols.  Using `--no-define-common'
-     allows Common symbols that are referenced from a shared library to
-     be assigned addresses only in the main program.  This eliminates
-     the unused duplicate space in the shared library, and also
-     prevents any possible confusion over resolving to the wrong
-     duplicate when there are many dynamic modules with specialized
-     search paths for runtime symbol resolution.
-
-`--defsym=SYMBOL=EXPRESSION'
+     file type; otherwise a non-Relocatable output type forces assigning
+     addresses to Common symbols.  Using '--no-define-common' allows
+     Common symbols that are referenced from a shared library to be
+     assigned addresses only in the main program.  This eliminates the
+     unused duplicate space in the shared library, and also prevents any
+     possible confusion over resolving to the wrong duplicate when there
+     are many dynamic modules with specialized search paths for runtime
+     symbol resolution.
+
+'--defsym=SYMBOL=EXPRESSION'
      Create a global symbol in the output file, containing the absolute
-     address given by EXPRESSION.  You may use this option as many
-     times as necessary to define multiple symbols in the command line.
-     A limited form of arithmetic is supported for the EXPRESSION in
-     this context: you may give a hexadecimal constant or the name of
-     an existing symbol, or use `+' and `-' to add or subtract
-     hexadecimal constants or symbols.  If you need more elaborate
-     expressions, consider using the linker command language from a
-     script (*note Assignment: Symbol Definitions: Assignments.).
-     _Note:_ there should be no white space between SYMBOL, the equals
-     sign ("<=>"), and EXPRESSION.
-
-`--demangle[=STYLE]'
-`--no-demangle'
+     address given by EXPRESSION.  You may use this option as many times
+     as necessary to define multiple symbols in the command line.  A
+     limited form of arithmetic is supported for the EXPRESSION in this
+     context: you may give a hexadecimal constant or the name of an
+     existing symbol, or use '+' and '-' to add or subtract hexadecimal
+     constants or symbols.  If you need more elaborate expressions,
+     consider using the linker command language from a script (*note
+     Assignment: Symbol Definitions: Assignments.).  _Note:_ there
+     should be no white space between SYMBOL, the equals sign ("<=>"),
+     and EXPRESSION.
+
+'--demangle[=STYLE]'
+'--no-demangle'
      These options control whether to demangle symbol names in error
-     messages and other output.  When the linker is told to demangle,
-     it tries to present symbol names in a readable fashion: it strips
-     leading underscores if they are used by the object file format,
-     and converts C++ mangled symbol names into user readable names.
+     messages and other output.  When the linker is told to demangle, it
+     tries to present symbol names in a readable fashion: it strips
+     leading underscores if they are used by the object file format, and
+     converts C++ mangled symbol names into user readable names.
      Different compilers have different mangling styles.  The optional
      demangling style argument can be used to choose an appropriate
      demangling style for your compiler.  The linker will demangle by
-     default unless the environment variable `COLLECT_NO_DEMANGLE' is
+     default unless the environment variable 'COLLECT_NO_DEMANGLE' is
      set.  These options may be used to override the default.
 
-`-IFILE'
-`--dynamic-linker=FILE'
+'-IFILE'
+'--dynamic-linker=FILE'
      Set the name of the dynamic linker.  This is only meaningful when
      generating dynamically linked ELF executables.  The default dynamic
-     linker is normally correct; don't use this unless you know what
-     you are doing.
+     linker is normally correct; don't use this unless you know what you
+     are doing.
 
-`--fatal-warnings'
-`--no-fatal-warnings'
+'--fatal-warnings'
+'--no-fatal-warnings'
      Treat all warnings as errors.  The default behaviour can be
-     restored with the option `--no-fatal-warnings'.
+     restored with the option '--no-fatal-warnings'.
 
-`--force-exe-suffix'
+'--force-exe-suffix'
      Make sure that an output file has a .exe suffix.
 
      If a successfully built fully linked output file does not have a
-     `.exe' or `.dll' suffix, this option forces the linker to copy the
-     output file to one of the same name with a `.exe' suffix. This
+     '.exe' or '.dll' suffix, this option forces the linker to copy the
+     output file to one of the same name with a '.exe' suffix.  This
      option is useful when using unmodified Unix makefiles on a
-     Microsoft Windows host, since some versions of Windows won't run
-     an image unless it ends in a `.exe' suffix.
+     Microsoft Windows host, since some versions of Windows won't run an
+     image unless it ends in a '.exe' suffix.
 
-`--gc-sections'
-`--no-gc-sections'
+'--gc-sections'
+'--no-gc-sections'
      Enable garbage collection of unused input sections.  It is ignored
      on targets that do not support this option.  The default behaviour
      (of not performing this garbage collection) can be restored by
-     specifying `--no-gc-sections' on the command line.
+     specifying '--no-gc-sections' on the command line.
 
-     `--gc-sections' decides which input sections are used by examining
+     '--gc-sections' decides which input sections are used by examining
      symbols and relocations.  The section containing the entry symbol
      and all sections containing symbols undefined on the command-line
      will be kept, as will sections containing symbols referenced by
@@ -1044,81 +1027,80 @@ GNU linker:
      linker must assume that any visible symbol is referenced.  Once
      this initial set of sections has been determined, the linker
      recursively marks as used any section referenced by their
-     relocations.  See `--entry' and `--undefined'.
+     relocations.  See '--entry' and '--undefined'.
 
      This option can be set when doing a partial link (enabled with
-     option `-r').  In this case the root of symbols kept must be
-     explicitly specified either by an `--entry' or `--undefined'
-     option or by a `ENTRY' command in the linker script.
+     option '-r').  In this case the root of symbols kept must be
+     explicitly specified either by an '--entry' or '--undefined' option
+     or by a 'ENTRY' command in the linker script.
 
-`--print-gc-sections'
-`--no-print-gc-sections'
+'--print-gc-sections'
+'--no-print-gc-sections'
      List all sections removed by garbage collection.  The listing is
      printed on stderr.  This option is only effective if garbage
-     collection has been enabled via the `--gc-sections') option.  The
+     collection has been enabled via the '--gc-sections') option.  The
      default behaviour (of not listing the sections that are removed)
-     can be restored by specifying `--no-print-gc-sections' on the
+     can be restored by specifying '--no-print-gc-sections' on the
      command line.
 
-`--print-output-format'
+'--print-output-format'
      Print the name of the default output format (perhaps influenced by
      other command-line options).  This is the string that would appear
-     in an `OUTPUT_FORMAT' linker script command (*note File
+     in an 'OUTPUT_FORMAT' linker script command (*note File
      Commands::).
 
-`--help'
+'--help'
      Print a summary of the command-line options on the standard output
      and exit.
 
-`--target-help'
+'--target-help'
      Print a summary of all target specific options on the standard
      output and exit.
 
-`-Map=MAPFILE'
+'-Map=MAPFILE'
      Print a link map to the file MAPFILE.  See the description of the
-     `-M' option, above.
+     '-M' option, above.
 
-`--no-keep-memory'
-     `ld' normally optimizes for speed over memory usage by caching the
-     symbol tables of input files in memory.  This option tells `ld' to
+'--no-keep-memory'
+     'ld' normally optimizes for speed over memory usage by caching the
+     symbol tables of input files in memory.  This option tells 'ld' to
      instead optimize for memory usage, by rereading the symbol tables
-     as necessary.  This may be required if `ld' runs out of memory
+     as necessary.  This may be required if 'ld' runs out of memory
      space while linking a large executable.
 
-`--no-undefined'
-`-z defs'
+'--no-undefined'
+'-z defs'
      Report unresolved symbol references from regular object files.
      This is done even if the linker is creating a non-symbolic shared
-     library.  The switch `--[no-]allow-shlib-undefined' controls the
+     library.  The switch '--[no-]allow-shlib-undefined' controls the
      behaviour for reporting unresolved references found in shared
      libraries being linked in.
 
-`--allow-multiple-definition'
-`-z muldefs'
+'--allow-multiple-definition'
+'-z muldefs'
      Normally when a symbol is defined multiple times, the linker will
-     report a fatal error. These options allow multiple definitions and
+     report a fatal error.  These options allow multiple definitions and
      the first definition will be used.
 
-`--allow-shlib-undefined'
-`--no-allow-shlib-undefined'
+'--allow-shlib-undefined'
+'--no-allow-shlib-undefined'
      Allows or disallows undefined symbols in shared libraries.  This
-     switch is similar to `--no-undefined' except that it determines
-     the behaviour when the undefined symbols are in a shared library
-     rather than a regular object file.  It does not affect how
-     undefined symbols in regular object files are handled.
+     switch is similar to '--no-undefined' except that it determines the
+     behaviour when the undefined symbols are in a shared library rather
+     than a regular object file.  It does not affect how undefined
+     symbols in regular object files are handled.
 
      The default behaviour is to report errors for any undefined symbols
      referenced in shared libraries if the linker is being used to
-     create an executable, but to allow them if the linker is being
-     used to create a shared library.
+     create an executable, but to allow them if the linker is being used
+     to create a shared library.
 
      The reasons for allowing undefined symbol references in shared
      libraries specified at link time are that:
 
-        * A shared library specified at link time may not be the same
-          as the one that is available at load time, so the symbol
-          might actually be resolvable at load time.
-
+        * A shared library specified at link time may not be the same as
+          the one that is available at load time, so the symbol might
+          actually be resolvable at load time.
         * There are some operating systems, eg BeOS and HPPA, where
           undefined symbols in shared libraries are normal.
 
@@ -1127,63 +1109,62 @@ GNU linker:
           current architecture.  This is used, for example, to
           dynamically select an appropriate memset function.
 
-`--no-undefined-version'
+'--no-undefined-version'
      Normally when a symbol has an undefined version, the linker will
-     ignore it. This option disallows symbols with undefined version
+     ignore it.  This option disallows symbols with undefined version
      and a fatal error will be issued instead.
 
-`--default-symver'
+'--default-symver'
      Create and use a default symbol version (the soname) for
      unversioned exported symbols.
 
-`--default-imported-symver'
+'--default-imported-symver'
      Create and use a default symbol version (the soname) for
      unversioned imported symbols.
 
-`--no-warn-mismatch'
-     Normally `ld' will give an error if you try to link together input
+'--no-warn-mismatch'
+     Normally 'ld' will give an error if you try to link together input
      files that are mismatched for some reason, perhaps because they
      have been compiled for different processors or for different
-     endiannesses.  This option tells `ld' that it should silently
+     endiannesses.  This option tells 'ld' that it should silently
      permit such possible errors.  This option should only be used with
-     care, in cases when you have taken some special action that
-     ensures that the linker errors are inappropriate.
+     care, in cases when you have taken some special action that ensures
+     that the linker errors are inappropriate.
 
-`--no-warn-search-mismatch'
-     Normally `ld' will give a warning if it finds an incompatible
+'--no-warn-search-mismatch'
+     Normally 'ld' will give a warning if it finds an incompatible
      library during a library search.  This option silences the warning.
 
-`--no-whole-archive'
-     Turn off the effect of the `--whole-archive' option for subsequent
+'--no-whole-archive'
+     Turn off the effect of the '--whole-archive' option for subsequent
      archive files.
 
-`--noinhibit-exec'
+'--noinhibit-exec'
      Retain the executable output file whenever it is still usable.
      Normally, the linker will not produce an output file if it
-     encounters errors during the link process; it exits without
-     writing an output file when it issues any error whatsoever.
-
-`-nostdlib'
-     Only search library directories explicitly specified on the
-     command line.  Library directories specified in linker scripts
-     (including linker scripts specified on the command line) are
-     ignored.
-
-`--oformat=OUTPUT-FORMAT'
-     `ld' may be configured to support more than one kind of object
-     file.  If your `ld' is configured this way, you can use the
-     `--oformat' option to specify the binary format for the output
-     object file.  Even when `ld' is configured to support alternative
-     object formats, you don't usually need to specify this, as `ld'
+     encounters errors during the link process; it exits without writing
+     an output file when it issues any error whatsoever.
+
+'-nostdlib'
+     Only search library directories explicitly specified on the command
+     line.  Library directories specified in linker scripts (including
+     linker scripts specified on the command line) are ignored.
+
+'--oformat=OUTPUT-FORMAT'
+     'ld' may be configured to support more than one kind of object
+     file.  If your 'ld' is configured this way, you can use the
+     '--oformat' option to specify the binary format for the output
+     object file.  Even when 'ld' is configured to support alternative
+     object formats, you don't usually need to specify this, as 'ld'
      should be configured to produce as a default output format the most
      usual format on each machine.  OUTPUT-FORMAT is a text string, the
      name of a particular format supported by the BFD libraries.  (You
-     can list the available binary formats with `objdump -i'.)  The
-     script command `OUTPUT_FORMAT' can also specify the output format,
+     can list the available binary formats with 'objdump -i'.)  The
+     script command 'OUTPUT_FORMAT' can also specify the output format,
      but this option overrides it.  *Note BFD::.
 
-`-pie'
-`--pic-executable'
+'-pie'
+'--pic-executable'
      Create a position independent executable.  This is currently only
      supported on ELF platforms.  Position independent executables are
      similar to shared libraries in that they are relocated by the
@@ -1192,166 +1173,159 @@ GNU linker:
      linked executables they can be executed and symbols defined in the
      executable cannot be overridden by shared libraries.
 
-`-qmagic'
+'-qmagic'
      This option is ignored for Linux compatibility.
 
-`-Qy'
+'-Qy'
      This option is ignored for SVR4 compatibility.
 
-`--relax'
-`--no-relax'
+'--relax'
+'--no-relax'
      An option with machine dependent effects.  This option is only
-     supported on a few targets.  *Note `ld' and the H8/300: H8/300.
-     *Note `ld' and the Intel 960 family: i960.  *Note `ld' and Xtensa
-     Processors: Xtensa.  *Note `ld' and the 68HC11 and 68HC12:
-     M68HC11/68HC12.  *Note `ld' and PowerPC 32-bit ELF Support:
-     PowerPC ELF32.
+     supported on a few targets.  *Note 'ld' and the H8/300: H8/300.
+     *Note 'ld' and the Intel 960 family: i960.  *Note 'ld' and Xtensa
+     Processors: Xtensa.  *Note 'ld' and the 68HC11 and 68HC12:
+     M68HC11/68HC12.  *Note 'ld' and PowerPC 32-bit ELF Support: PowerPC
+     ELF32.
 
-     On some platforms the `--relax' option performs target specific,
+     On some platforms the '--relax' option performs target specific,
      global optimizations that become possible when the linker resolves
      addressing in the program, such as relaxing address modes,
      synthesizing new instructions, selecting shorter version of current
      instructions, and combining constant values.
 
      On some platforms these link time global optimizations may make
-     symbolic debugging of the resulting executable impossible.  This
-     is known to be the case for the Matsushita MN10200 and MN10300
-     family of processors.
+     symbolic debugging of the resulting executable impossible.  This is
+     known to be the case for the Matsushita MN10200 and MN10300 family
+     of processors.
 
-     On platforms where this is not supported, `--relax' is accepted,
+     On platforms where this is not supported, '--relax' is accepted,
      but ignored.
 
-     On platforms where `--relax' is accepted the option `--no-relax'
+     On platforms where '--relax' is accepted the option '--no-relax'
      can be used to disable the feature.
 
-`--retain-symbols-file=FILENAME'
+'--retain-symbols-file=FILENAME'
      Retain _only_ the symbols listed in the file FILENAME, discarding
      all others.  FILENAME is simply a flat file, with one symbol name
      per line.  This option is especially useful in environments (such
      as VxWorks) where a large global symbol table is accumulated
      gradually, to conserve run-time memory.
 
-     `--retain-symbols-file' does _not_ discard undefined symbols, or
+     '--retain-symbols-file' does _not_ discard undefined symbols, or
      symbols needed for relocations.
 
-     You may only specify `--retain-symbols-file' once in the command
-     line.  It overrides `-s' and `-S'.
+     You may only specify '--retain-symbols-file' once in the command
+     line.  It overrides '-s' and '-S'.
 
-`-rpath=DIR'
+'-rpath=DIR'
      Add a directory to the runtime library search path.  This is used
-     when linking an ELF executable with shared objects.  All `-rpath'
+     when linking an ELF executable with shared objects.  All '-rpath'
      arguments are concatenated and passed to the runtime linker, which
-     uses them to locate shared objects at runtime.  The `-rpath'
-     option is also used when locating shared objects which are needed
-     by shared objects explicitly included in the link; see the
-     description of the `-rpath-link' option.  If `-rpath' is not used
-     when linking an ELF executable, the contents of the environment
-     variable `LD_RUN_PATH' will be used if it is defined.
-
-     The `-rpath' option may also be used on SunOS.  By default, on
+     uses them to locate shared objects at runtime.  The '-rpath' option
+     is also used when locating shared objects which are needed by
+     shared objects explicitly included in the link; see the description
+     of the '-rpath-link' option.  If '-rpath' is not used when linking
+     an ELF executable, the contents of the environment variable
+     'LD_RUN_PATH' will be used if it is defined.
+
+     The '-rpath' option may also be used on SunOS. By default, on
      SunOS, the linker will form a runtime search patch out of all the
-     `-L' options it is given.  If a `-rpath' option is used, the
-     runtime search path will be formed exclusively using the `-rpath'
-     options, ignoring the `-L' options.  This can be useful when using
-     gcc, which adds many `-L' options which may be on NFS mounted file
+     '-L' options it is given.  If a '-rpath' option is used, the
+     runtime search path will be formed exclusively using the '-rpath'
+     options, ignoring the '-L' options.  This can be useful when using
+     gcc, which adds many '-L' options which may be on NFS mounted file
      systems.
 
-     For compatibility with other ELF linkers, if the `-R' option is
+     For compatibility with other ELF linkers, if the '-R' option is
      followed by a directory name, rather than a file name, it is
-     treated as the `-rpath' option.
+     treated as the '-rpath' option.
 
-`-rpath-link=DIR'
+'-rpath-link=DIR'
      When using ELF or SunOS, one shared library may require another.
-     This happens when an `ld -shared' link includes a shared library
-     as one of the input files.
+     This happens when an 'ld -shared' link includes a shared library as
+     one of the input files.
 
      When the linker encounters such a dependency when doing a
      non-shared, non-relocatable link, it will automatically try to
      locate the required shared library and include it in the link, if
-     it is not included explicitly.  In such a case, the `-rpath-link'
+     it is not included explicitly.  In such a case, the '-rpath-link'
      option specifies the first set of directories to search.  The
-     `-rpath-link' option may specify a sequence of directory names
+     '-rpath-link' option may specify a sequence of directory names
      either by specifying a list of names separated by colons, or by
      appearing multiple times.
 
      This option should be used with caution as it overrides the search
-     path that may have been hard compiled into a shared library. In
+     path that may have been hard compiled into a shared library.  In
      such a case it is possible to use unintentionally a different
      search path than the runtime linker would do.
 
      The linker uses the following search paths to locate required
      shared libraries:
-       1. Any directories specified by `-rpath-link' options.
-
-       2. Any directories specified by `-rpath' options.  The difference
-          between `-rpath' and `-rpath-link' is that directories
-          specified by `-rpath' options are included in the executable
-          and used at runtime, whereas the `-rpath-link' option is only
-          effective at link time. Searching `-rpath' in this way is
+       1. Any directories specified by '-rpath-link' options.
+       2. Any directories specified by '-rpath' options.  The difference
+          between '-rpath' and '-rpath-link' is that directories
+          specified by '-rpath' options are included in the executable
+          and used at runtime, whereas the '-rpath-link' option is only
+          effective at link time.  Searching '-rpath' in this way is
           only supported by native linkers and cross linkers which have
-          been configured with the `--with-sysroot' option.
-
-       3. On an ELF system, for native linkers, if the `-rpath' and
-          `-rpath-link' options were not used, search the contents of
-          the environment variable `LD_RUN_PATH'.
-
-       4. On SunOS, if the `-rpath' option was not used, search any
-          directories specified using `-L' options.
-
+          been configured with the '--with-sysroot' option.
+       3. On an ELF system, for native linkers, if the '-rpath' and
+          '-rpath-link' options were not used, search the contents of
+          the environment variable 'LD_RUN_PATH'.
+       4. On SunOS, if the '-rpath' option was not used, search any
+          directories specified using '-L' options.
        5. For a native linker, search the contents of the environment
-          variable `LD_LIBRARY_PATH'.
-
-       6. For a native ELF linker, the directories in `DT_RUNPATH' or
-          `DT_RPATH' of a shared library are searched for shared
-          libraries needed by it. The `DT_RPATH' entries are ignored if
-          `DT_RUNPATH' entries exist.
-
-       7. The default directories, normally `/lib' and `/usr/lib'.
-
+          variable 'LD_LIBRARY_PATH'.
+       6. For a native ELF linker, the directories in 'DT_RUNPATH' or
+          'DT_RPATH' of a shared library are searched for shared
+          libraries needed by it.  The 'DT_RPATH' entries are ignored if
+          'DT_RUNPATH' entries exist.
+       7. The default directories, normally '/lib' and '/usr/lib'.
        8. For a native linker on an ELF system, if the file
-          `/etc/ld.so.conf' exists, the list of directories found in
+          '/etc/ld.so.conf' exists, the list of directories found in
           that file.
 
      If the required shared library is not found, the linker will issue
      a warning and continue with the link.
 
-`-shared'
-`-Bshareable'
+'-shared'
+'-Bshareable'
      Create a shared library.  This is currently only supported on ELF,
-     XCOFF and SunOS platforms.  On SunOS, the linker will
-     automatically create a shared library if the `-e' option is not
-     used and there are undefined symbols in the link.
-
-`--sort-common'
-`--sort-common=ascending'
-`--sort-common=descending'
-     This option tells `ld' to sort the common symbols by alignment in
+     XCOFF and SunOS platforms.  On SunOS, the linker will automatically
+     create a shared library if the '-e' option is not used and there
+     are undefined symbols in the link.
+
+'--sort-common'
+'--sort-common=ascending'
+'--sort-common=descending'
+     This option tells 'ld' to sort the common symbols by alignment in
      ascending or descending order when it places them in the
      appropriate output sections.  The symbol alignments considered are
      sixteen-byte or larger, eight-byte, four-byte, two-byte, and
-     one-byte. This is to prevent gaps between symbols due to alignment
+     one-byte.  This is to prevent gaps between symbols due to alignment
      constraints.  If no sorting order is specified, then descending
      order is assumed.
 
-`--sort-section=name'
-     This option will apply `SORT_BY_NAME' to all wildcard section
+'--sort-section=name'
+     This option will apply 'SORT_BY_NAME' to all wildcard section
      patterns in the linker script.
 
-`--sort-section=alignment'
-     This option will apply `SORT_BY_ALIGNMENT' to all wildcard section
+'--sort-section=alignment'
+     This option will apply 'SORT_BY_ALIGNMENT' to all wildcard section
      patterns in the linker script.
 
-`--split-by-file[=SIZE]'
-     Similar to `--split-by-reloc' but creates a new output section for
-     each input file when SIZE is reached.  SIZE defaults to a size of
-     1 if not given.
+'--split-by-file[=SIZE]'
+     Similar to '--split-by-reloc' but creates a new output section for
+     each input file when SIZE is reached.  SIZE defaults to a size of 1
+     if not given.
 
-`--split-by-reloc[=COUNT]'
+'--split-by-reloc[=COUNT]'
      Tries to creates extra sections in the output file so that no
      single output section in the file contains more than COUNT
-     relocations.  This is useful when generating huge relocatable
-     files for downloading into certain real time kernels with the COFF
-     object file format; since COFF cannot represent more than 65535
+     relocations.  This is useful when generating huge relocatable files
+     for downloading into certain real time kernels with the COFF object
+     file format; since COFF cannot represent more than 65535
      relocations in a single section.  Note that this will fail to work
      with object file formats which do not support arbitrary sections.
      The linker will not split up individual input sections for
@@ -1359,136 +1333,135 @@ GNU linker:
      COUNT relocations one output section will contain that many
      relocations.  COUNT defaults to a value of 32768.
 
-`--stats'
+'--stats'
      Compute and display statistics about the operation of the linker,
      such as execution time and memory usage.
 
-`--sysroot=DIRECTORY'
+'--sysroot=DIRECTORY'
      Use DIRECTORY as the location of the sysroot, overriding the
      configure-time default.  This option is only supported by linkers
-     that were configured using `--with-sysroot'.
+     that were configured using '--with-sysroot'.
 
-`--traditional-format'
-     For some targets, the output of `ld' is different in some ways from
-     the output of some existing linker.  This switch requests `ld' to
+'--traditional-format'
+     For some targets, the output of 'ld' is different in some ways from
+     the output of some existing linker.  This switch requests 'ld' to
      use the traditional format instead.
 
-     For example, on SunOS, `ld' combines duplicate entries in the
+     For example, on SunOS, 'ld' combines duplicate entries in the
      symbol string table.  This can reduce the size of an output file
-     with full debugging information by over 30 percent.
-     Unfortunately, the SunOS `dbx' program can not read the resulting
-     program (`gdb' has no trouble).  The `--traditional-format' switch
-     tells `ld' to not combine duplicate entries.
+     with full debugging information by over 30 percent.  Unfortunately,
+     the SunOS 'dbx' program can not read the resulting program ('gdb'
+     has no trouble).  The '--traditional-format' switch tells 'ld' to
+     not combine duplicate entries.
 
-`--section-start=SECTIONNAME=ORG'
+'--section-start=SECTIONNAME=ORG'
      Locate a section in the output file at the absolute address given
      by ORG.  You may use this option as many times as necessary to
-     locate multiple sections in the command line.  ORG must be a
-     single hexadecimal integer; for compatibility with other linkers,
-     you may omit the leading `0x' usually associated with hexadecimal
-     values.  _Note:_ there should be no white space between
-     SECTIONNAME, the equals sign ("<=>"), and ORG.
-
-`-Tbss=ORG'
-`-Tdata=ORG'
-`-Ttext=ORG'
-     Same as `--section-start', with `.bss', `.data' or `.text' as the
+     locate multiple sections in the command line.  ORG must be a single
+     hexadecimal integer; for compatibility with other linkers, you may
+     omit the leading '0x' usually associated with hexadecimal values.
+     _Note:_ there should be no white space between SECTIONNAME, the
+     equals sign ("<=>"), and ORG.
+
+'-Tbss=ORG'
+'-Tdata=ORG'
+'-Ttext=ORG'
+     Same as '--section-start', with '.bss', '.data' or '.text' as the
      SECTIONNAME.
 
-`-Ttext-segment=ORG'
+'-Ttext-segment=ORG'
      When creating an ELF executable or shared object, it will set the
      address of the first byte of the text segment.
 
-`-Trodata-segment=ORG'
+'-Trodata-segment=ORG'
      When creating an ELF executable or shared object for a target where
      the read-only data is in its own segment separate from the
      executable text, it will set the address of the first byte of the
      read-only data segment.
 
-`-Tldata-segment=ORG'
+'-Tldata-segment=ORG'
      When creating an ELF executable or shared object for x86-64 medium
      memory model, it will set the address of the first byte of the
      ldata segment.
 
-`--unresolved-symbols=METHOD'
+'--unresolved-symbols=METHOD'
      Determine how to handle unresolved symbols.  There are four
-     possible values for `method':
+     possible values for 'method':
 
-    `ignore-all'
+     'ignore-all'
           Do not report any unresolved symbols.
 
-    `report-all'
+     'report-all'
           Report all unresolved symbols.  This is the default.
 
-    `ignore-in-object-files'
+     'ignore-in-object-files'
           Report unresolved symbols that are contained in shared
           libraries, but ignore them if they come from regular object
           files.
 
-    `ignore-in-shared-libs'
-          Report unresolved symbols that come from regular object
-          files, but ignore them if they come from shared libraries.
-          This can be useful when creating a dynamic binary and it is
-          known that all the shared libraries that it should be
-          referencing are included on the linker's command line.
+     'ignore-in-shared-libs'
+          Report unresolved symbols that come from regular object files,
+          but ignore them if they come from shared libraries.  This can
+          be useful when creating a dynamic binary and it is known that
+          all the shared libraries that it should be referencing are
+          included on the linker's command line.
 
      The behaviour for shared libraries on their own can also be
-     controlled by the `--[no-]allow-shlib-undefined' option.
+     controlled by the '--[no-]allow-shlib-undefined' option.
 
      Normally the linker will generate an error message for each
      reported unresolved symbol but the option
-     `--warn-unresolved-symbols' can change this to a warning.
+     '--warn-unresolved-symbols' can change this to a warning.
 
-`--dll-verbose'
-`--verbose[=NUMBER]'
-     Display the version number for `ld' and list the linker emulations
+'--dll-verbose'
+'--verbose[=NUMBER]'
+     Display the version number for 'ld' and list the linker emulations
      supported.  Display which input files can and cannot be opened.
-     Display the linker script being used by the linker. If the
+     Display the linker script being used by the linker.  If the
      optional NUMBER argument > 1, plugin symbol status will also be
      displayed.
 
-`--version-script=VERSION-SCRIPTFILE'
+'--version-script=VERSION-SCRIPTFILE'
      Specify the name of a version script to the linker.  This is
-     typically used when creating shared libraries to specify
-     additional information about the version hierarchy for the library
-     being created.  This option is only fully supported on ELF
-     platforms which support shared libraries; see *note VERSION::.  It
-     is partially supported on PE platforms, which can use version
-     scripts to filter symbol visibility in auto-export mode: any
-     symbols marked `local' in the version script will not be exported.
-     *Note WIN32::.
-
-`--warn-common'
-     Warn when a common symbol is combined with another common symbol
-     or with a symbol definition.  Unix linkers allow this somewhat
-     sloppy practice, but linkers on some other operating systems do
-     not.  This option allows you to find potential problems from
-     combining global symbols.  Unfortunately, some C libraries use
-     this practice, so you may get some warnings about symbols in the
-     libraries as well as in your programs.
+     typically used when creating shared libraries to specify additional
+     information about the version hierarchy for the library being
+     created.  This option is only fully supported on ELF platforms
+     which support shared libraries; see *note VERSION::.  It is
+     partially supported on PE platforms, which can use version scripts
+     to filter symbol visibility in auto-export mode: any symbols marked
+     'local' in the version script will not be exported.  *Note WIN32::.
+
+'--warn-common'
+     Warn when a common symbol is combined with another common symbol or
+     with a symbol definition.  Unix linkers allow this somewhat sloppy
+     practice, but linkers on some other operating systems do not.  This
+     option allows you to find potential problems from combining global
+     symbols.  Unfortunately, some C libraries use this practice, so you
+     may get some warnings about symbols in the libraries as well as in
+     your programs.
 
      There are three kinds of global symbols, illustrated here by C
      examples:
 
-    `int i = 1;'
+     'int i = 1;'
           A definition, which goes in the initialized data section of
           the output file.
 
-    `extern int i;'
+     'extern int i;'
           An undefined reference, which does not allocate space.  There
           must be either a definition or a common symbol for the
           variable somewhere.
 
-    `int i;'
+     'int i;'
           A common symbol.  If there are only (one or more) common
-          symbols for a variable, it goes in the uninitialized data
-          area of the output file.  The linker merges multiple common
-          symbols for the same variable into a single symbol.  If they
-          are of different sizes, it picks the largest size.  The
-          linker turns a common symbol into a declaration, if there is
-          a definition of the same variable.
-
-     The `--warn-common' option can produce five kinds of warnings.
+          symbols for a variable, it goes in the uninitialized data area
+          of the output file.  The linker merges multiple common symbols
+          for the same variable into a single symbol.  If they are of
+          different sizes, it picks the largest size.  The linker turns
+          a common symbol into a declaration, if there is a definition
+          of the same variable.
+
+     The '--warn-common' option can produce five kinds of warnings.
      Each warning consists of a pair of lines: the first describes the
      symbol just encountered, and the second describes the previous
      symbol encountered with the same name.  One or both of the two
@@ -1501,9 +1474,9 @@ GNU linker:
                FILE(SECTION): warning: defined here
 
        2. Turning a common symbol into a reference, because a later
-          definition for the symbol is encountered.  This is the same
-          as the previous case, except that the symbols are encountered
-          in a different order.
+          definition for the symbol is encountered.  This is the same as
+          the previous case, except that the symbols are encountered in
+          a different order.
                FILE(SECTION): warning: definition of `SYMBOL'
                   overriding common
                FILE(SECTION): warning: common is here
@@ -1519,80 +1492,80 @@ GNU linker:
                   overridden by larger common
                FILE(SECTION): warning: larger common is here
 
-       5. Merging a common symbol with a previous smaller common
-          symbol.  This is the same as the previous case, except that
-          the symbols are encountered in a different order.
+       5. Merging a common symbol with a previous smaller common symbol.
+          This is the same as the previous case, except that the symbols
+          are encountered in a different order.
                FILE(SECTION): warning: common of `SYMBOL'
                   overriding smaller common
                FILE(SECTION): warning: smaller common is here
 
-`--warn-constructors'
+'--warn-constructors'
      Warn if any global constructors are used.  This is only useful for
      a few object file formats.  For formats like COFF or ELF, the
      linker can not detect the use of global constructors.
 
-`--warn-multiple-gp'
+'--warn-multiple-gp'
      Warn if multiple global pointer values are required in the output
      file.  This is only meaningful for certain processors, such as the
-     Alpha.  Specifically, some processors put large-valued constants
-     in a special section.  A special register (the global pointer)
-     points into the middle of this section, so that constants can be
-     loaded efficiently via a base-register relative addressing mode.
-     Since the offset in base-register relative mode is fixed and
-     relatively small (e.g., 16 bits), this limits the maximum size of
-     the constant pool.  Thus, in large programs, it is often necessary
-     to use multiple global pointer values in order to be able to
-     address all possible constants.  This option causes a warning to
-     be issued whenever this case occurs.
-
-`--warn-once'
+     Alpha.  Specifically, some processors put large-valued constants in
+     a special section.  A special register (the global pointer) points
+     into the middle of this section, so that constants can be loaded
+     efficiently via a base-register relative addressing mode.  Since
+     the offset in base-register relative mode is fixed and relatively
+     small (e.g., 16 bits), this limits the maximum size of the constant
+     pool.  Thus, in large programs, it is often necessary to use
+     multiple global pointer values in order to be able to address all
+     possible constants.  This option causes a warning to be issued
+     whenever this case occurs.
+
+'--warn-once'
      Only warn once for each undefined symbol, rather than once per
      module which refers to it.
 
-`--warn-section-align'
+'--warn-section-align'
      Warn if the address of an output section is changed because of
      alignment.  Typically, the alignment will be set by an input
      section.  The address will only be changed if it not explicitly
-     specified; that is, if the `SECTIONS' command does not specify a
+     specified; that is, if the 'SECTIONS' command does not specify a
      start address for the section (*note SECTIONS::).
 
-`--warn-shared-textrel'
+'--warn-shared-textrel'
      Warn if the linker adds a DT_TEXTREL to a shared object.
 
-`--warn-alternate-em'
+'--warn-alternate-em'
      Warn if an object has alternate ELF machine code.
 
-`--warn-unresolved-symbols'
+'--warn-unresolved-symbols'
      If the linker is going to report an unresolved symbol (see the
-     option `--unresolved-symbols') it will normally generate an error.
+     option '--unresolved-symbols') it will normally generate an error.
      This option makes it generate a warning instead.
 
-`--error-unresolved-symbols'
+'--error-unresolved-symbols'
      This restores the linker's default behaviour of generating errors
      when it is reporting unresolved symbols.
 
-`--whole-archive'
+'--whole-archive'
      For each archive mentioned on the command line after the
-     `--whole-archive' option, include every object file in the archive
+     '--whole-archive' option, include every object file in the archive
      in the link, rather than searching the archive for the required
-     object files.  This is normally used to turn an archive file into
-     a shared library, forcing every object to be included in the
+     object files.  This is normally used to turn an archive file into a
+     shared library, forcing every object to be included in the
      resulting shared library.  This option may be used more than once.
 
      Two notes when using this option from gcc: First, gcc doesn't know
-     about this option, so you have to use `-Wl,-whole-archive'.
-     Second, don't forget to use `-Wl,-no-whole-archive' after your
-     list of archives, because gcc will add its own list of archives to
-     your link and you may not want this flag to affect those as well.
+     about this option, so you have to use '-Wl,-whole-archive'.
+     Second, don't forget to use '-Wl,-no-whole-archive' after your list
+     of archives, because gcc will add its own list of archives to your
+     link and you may not want this flag to affect those as well.
 
-`--wrap=SYMBOL'
+'--wrap=SYMBOL'
      Use a wrapper function for SYMBOL.  Any undefined reference to
-     SYMBOL will be resolved to `__wrap_SYMBOL'.  Any undefined
-     reference to `__real_SYMBOL' will be resolved to SYMBOL.
+     SYMBOL will be resolved to '__wrap_SYMBOL'.  Any undefined
+     reference to '__real_SYMBOL' will be resolved to SYMBOL.
 
      This can be used to provide a wrapper for a system function.  The
-     wrapper function should be called `__wrap_SYMBOL'.  If it wishes
-     to call the system function, it should call `__real_SYMBOL'.
+     wrapper function should be called '__wrap_SYMBOL'.  If it wishes to
+     call the system function, it should call '__real_SYMBOL'.
 
      Here is a trivial example:
 
@@ -1603,37 +1576,37 @@ GNU linker:
             return __real_malloc (c);
           }
 
-     If you link other code with this file using `--wrap malloc', then
-     all calls to `malloc' will call the function `__wrap_malloc'
-     instead.  The call to `__real_malloc' in `__wrap_malloc' will call
-     the real `malloc' function.
+     If you link other code with this file using '--wrap malloc', then
+     all calls to 'malloc' will call the function '__wrap_malloc'
+     instead.  The call to '__real_malloc' in '__wrap_malloc' will call
+     the real 'malloc' function.
 
-     You may wish to provide a `__real_malloc' function as well, so that
-     links without the `--wrap' option will succeed.  If you do this,
-     you should not put the definition of `__real_malloc' in the same
-     file as `__wrap_malloc'; if you do, the assembler may resolve the
-     call before the linker has a chance to wrap it to `malloc'.
+     You may wish to provide a '__real_malloc' function as well, so that
+     links without the '--wrap' option will succeed.  If you do this,
+     you should not put the definition of '__real_malloc' in the same
+     file as '__wrap_malloc'; if you do, the assembler may resolve the
+     call before the linker has a chance to wrap it to 'malloc'.
 
-`--eh-frame-hdr'
-     Request creation of `.eh_frame_hdr' section and ELF
-     `PT_GNU_EH_FRAME' segment header.
+'--eh-frame-hdr'
+     Request creation of '.eh_frame_hdr' section and ELF
+     'PT_GNU_EH_FRAME' segment header.
 
-`--no-ld-generated-unwind-info'
-     Request creation of `.eh_frame' unwind info for linker generated
-     code sections like PLT.  This option is on by default if linker
+'--no-ld-generated-unwind-info'
+     Request creation of '.eh_frame' unwind info for linker generated
+     code sections like PLT. This option is on by default if linker
      generated unwind info is supported.
 
-`--enable-new-dtags'
-`--disable-new-dtags'
+'--enable-new-dtags'
+'--disable-new-dtags'
      This linker can create the new dynamic tags in ELF. But the older
-     ELF systems may not understand them. If you specify
-     `--enable-new-dtags', the new dynamic tags will be created as
+     ELF systems may not understand them.  If you specify
+     '--enable-new-dtags', the new dynamic tags will be created as
      needed and older dynamic tags will be omitted.  If you specify
-     `--disable-new-dtags', no new dynamic tags will be created. By
-     default, the new dynamic tags are not created. Note that those
+     '--disable-new-dtags', no new dynamic tags will be created.  By
+     default, the new dynamic tags are not created.  Note that those
      options are only available for ELF systems.
 
-`--hash-size=NUMBER'
+'--hash-size=NUMBER'
      Set the default size of the linker's hash tables to a prime number
      close to NUMBER.  Increasing this value can reduce the length of
      time it takes the linker to perform its tasks, at the expense of
@@ -1641,13 +1614,13 @@ GNU linker:
      this value can reduce the memory requirements at the expense of
      speed.
 
-`--hash-style=STYLE'
-     Set the type of linker's hash table(s).  STYLE can be either
-     `sysv' for classic ELF `.hash' section, `gnu' for new style GNU
-     `.gnu.hash' section or `both' for both the classic ELF `.hash' and
-     new style GNU `.gnu.hash' hash tables.  The default is `sysv'.
+'--hash-style=STYLE'
+     Set the type of linker's hash table(s).  STYLE can be either 'sysv'
+     for classic ELF '.hash' section, 'gnu' for new style GNU
+     '.gnu.hash' section or 'both' for both the classic ELF '.hash' and
+     new style GNU '.gnu.hash' hash tables.  The default is 'sysv'.
 
-`--reduce-memory-overheads'
+'--reduce-memory-overheads'
      This option reduces memory requirements at ld runtime, at the
      expense of linking speed.  This was introduced to select the old
      O(n^2) algorithm for link map file generation, rather than the new
@@ -1655,159 +1628,158 @@ GNU linker:
 
      Another effect of the switch is to set the default hash table size
      to 1021, which again saves memory at the cost of lengthening the
-     linker's run time.  This is not done however if the `--hash-size'
+     linker's run time.  This is not done however if the '--hash-size'
      switch has been used.
 
-     The `--reduce-memory-overheads' switch may be also be used to
+     The '--reduce-memory-overheads' switch may be also be used to
      enable other tradeoffs in future versions of the linker.
 
-`--build-id'
-`--build-id=STYLE'
-     Request creation of `.note.gnu.build-id' ELF note section.  The
+'--build-id'
+'--build-id=STYLE'
+     Request creation of '.note.gnu.build-id' ELF note section.  The
      contents of the note are unique bits identifying this linked file.
-     STYLE can be `uuid' to use 128 random bits, `sha1' to use a
-     160-bit SHA1 hash on the normative parts of the output contents,
-     `md5' to use a 128-bit MD5 hash on the normative parts of the
-     output contents, or `0xHEXSTRING' to use a chosen bit string
-     specified as an even number of hexadecimal digits (`-' and `:'
-     characters between digit pairs are ignored).  If STYLE is omitted,
-     `sha1' is used.
-
-     The `md5' and `sha1' styles produces an identifier that is always
+     STYLE can be 'uuid' to use 128 random bits, 'sha1' to use a 160-bit
+     SHA1 hash on the normative parts of the output contents, 'md5' to
+     use a 128-bit MD5 hash on the normative parts of the output
+     contents, or '0xHEXSTRING' to use a chosen bit string specified as
+     an even number of hexadecimal digits ('-' and ':' characters
+     between digit pairs are ignored).  If STYLE is omitted, 'sha1' is
+     used.
+
+     The 'md5' and 'sha1' styles produces an identifier that is always
      the same in an identical output file, but will be unique among all
      nonidentical output files.  It is not intended to be compared as a
      checksum for the file's contents.  A linked file may be changed
      later by other tools, but the build ID bit string identifying the
      original linked file does not change.
 
-     Passing `none' for STYLE disables the setting from any
-     `--build-id' options earlier on the command line.
+     Passing 'none' for STYLE disables the setting from any '--build-id'
+     options earlier on the command line.
 
 2.1.1 Options Specific to i386 PE Targets
 -----------------------------------------
 
-The i386 PE linker supports the `-shared' option, which causes the
+The i386 PE linker supports the '-shared' option, which causes the
 output to be a dynamically linked library (DLL) instead of a normal
-executable.  You should name the output `*.dll' when you use this
-option.  In addition, the linker fully supports the standard `*.def'
+executable.  You should name the output '*.dll' when you use this
+option.  In addition, the linker fully supports the standard '*.def'
 files, which may be specified on the linker command line like an object
 file (in fact, it should precede archives it exports symbols from, to
 ensure that they get linked in, just like a normal object file).
 
    In addition to the options common to all targets, the i386 PE linker
-support additional command line options that are specific to the i386
-PE target.  Options that take values may be separated from their values
-by either a space or an equals sign.
+support additional command line options that are specific to the i386 PE
+target.  Options that take values may be separated from their values by
+either a space or an equals sign.
 
-`--add-stdcall-alias'
+'--add-stdcall-alias'
      If given, symbols with a stdcall suffix (@NN) will be exported
      as-is and also with the suffix stripped.  [This option is specific
      to the i386 PE targeted port of the linker]
 
-`--base-file FILE'
+'--base-file FILE'
      Use FILE as the name of a file in which to save the base addresses
-     of all the relocations needed for generating DLLs with `dlltool'.
+     of all the relocations needed for generating DLLs with 'dlltool'.
      [This is an i386 PE specific option]
 
-`--dll'
+'--dll'
      Create a DLL instead of a regular executable.  You may also use
-     `-shared' or specify a `LIBRARY' in a given `.def' file.  [This
+     '-shared' or specify a 'LIBRARY' in a given '.def' file.  [This
      option is specific to the i386 PE targeted port of the linker]
 
-`--enable-long-section-names'
-`--disable-long-section-names'
+'--enable-long-section-names'
+'--disable-long-section-names'
      The PE variants of the Coff object format add an extension that
      permits the use of section names longer than eight characters, the
-     normal limit for Coff.  By default, these names are only allowed
-     in object files, as fully-linked executable images do not carry
-     the Coff string table required to support the longer names.  As a
-     GNU extension, it is possible to allow their use in executable
-     images as well, or to (probably pointlessly!)  disallow it in
-     object files, by using these two options.  Executable images
-     generated with these long section names are slightly non-standard,
-     carrying as they do a string table, and may generate confusing
-     output when examined with non-GNU PE-aware tools, such as file
-     viewers and dumpers.  However, GDB relies on the use of PE long
-     section names to find Dwarf-2 debug information sections in an
-     executable image at runtime, and so if neither option is specified
-     on the command-line, `ld' will enable long section names,
-     overriding the default and technically correct behaviour, when it
-     finds the presence of debug information while linking an executable
-     image and not stripping symbols.  [This option is valid for all PE
-     targeted ports of the linker]
-
-`--enable-stdcall-fixup'
-`--disable-stdcall-fixup'
+     normal limit for Coff.  By default, these names are only allowed in
+     object files, as fully-linked executable images do not carry the
+     Coff string table required to support the longer names.  As a GNU
+     extension, it is possible to allow their use in executable images
+     as well, or to (probably pointlessly!)  disallow it in object
+     files, by using these two options.  Executable images generated
+     with these long section names are slightly non-standard, carrying
+     as they do a string table, and may generate confusing output when
+     examined with non-GNU PE-aware tools, such as file viewers and
+     dumpers.  However, GDB relies on the use of PE long section names
+     to find Dwarf-2 debug information sections in an executable image
+     at runtime, and so if neither option is specified on the
+     command-line, 'ld' will enable long section names, overriding the
+     default and technically correct behaviour, when it finds the
+     presence of debug information while linking an executable image and
+     not stripping symbols.  [This option is valid for all PE targeted
+     ports of the linker]
+
+'--enable-stdcall-fixup'
+'--disable-stdcall-fixup'
      If the link finds a symbol that it cannot resolve, it will attempt
      to do "fuzzy linking" by looking for another defined symbol that
      differs only in the format of the symbol name (cdecl vs stdcall)
-     and will resolve that symbol by linking to the match.  For
-     example, the undefined symbol `_foo' might be linked to the
-     function `_foo@12', or the undefined symbol `_bar@16' might be
-     linked to the function `_bar'.  When the linker does this, it
-     prints a warning, since it normally should have failed to link,
-     but sometimes import libraries generated from third-party dlls may
-     need this feature to be usable.  If you specify
-     `--enable-stdcall-fixup', this feature is fully enabled and
-     warnings are not printed.  If you specify
-     `--disable-stdcall-fixup', this feature is disabled and such
+     and will resolve that symbol by linking to the match.  For example,
+     the undefined symbol '_foo' might be linked to the function
+     '_foo@12', or the undefined symbol '_bar@16' might be linked to the
+     function '_bar'.  When the linker does this, it prints a warning,
+     since it normally should have failed to link, but sometimes import
+     libraries generated from third-party dlls may need this feature to
+     be usable.  If you specify '--enable-stdcall-fixup', this feature
+     is fully enabled and warnings are not printed.  If you specify
+     '--disable-stdcall-fixup', this feature is disabled and such
      mismatches are considered to be errors.  [This option is specific
      to the i386 PE targeted port of the linker]
 
-`--leading-underscore'
-`--no-leading-underscore'
+'--leading-underscore'
+'--no-leading-underscore'
      For most targets default symbol-prefix is an underscore and is
-     defined in target's description. By this option it is possible to
+     defined in target's description.  By this option it is possible to
      disable/enable the default underscore symbol-prefix.
 
-`--export-all-symbols'
+'--export-all-symbols'
      If given, all global symbols in the objects used to build a DLL
-     will be exported by the DLL.  Note that this is the default if
-     there otherwise wouldn't be any exported symbols.  When symbols are
+     will be exported by the DLL. Note that this is the default if there
+     otherwise wouldn't be any exported symbols.  When symbols are
      explicitly exported via DEF files or implicitly exported via
      function attributes, the default is to not export anything else
-     unless this option is given.  Note that the symbols `DllMain@12',
-     `DllEntryPoint@0', `DllMainCRTStartup@12', and `impure_ptr' will
+     unless this option is given.  Note that the symbols 'DllMain@12',
+     'DllEntryPoint@0', 'DllMainCRTStartup@12', and 'impure_ptr' will
      not be automatically exported.  Also, symbols imported from other
-     DLLs will not be re-exported, nor will symbols specifying the
-     DLL's internal layout such as those beginning with `_head_' or
-     ending with `_iname'.  In addition, no symbols from `libgcc',
-     `libstd++', `libmingw32', or `crtX.o' will be exported.  Symbols
-     whose names begin with `__rtti_' or `__builtin_' will not be
-     exported, to help with C++ DLLs.  Finally, there is an extensive
-     list of cygwin-private symbols that are not exported (obviously,
-     this applies on when building DLLs for cygwin targets).  These
-     cygwin-excludes are: `_cygwin_dll_entry@12',
-     `_cygwin_crt0_common@8', `_cygwin_noncygwin_dll_entry@12',
-     `_fmode', `_impure_ptr', `cygwin_attach_dll', `cygwin_premain0',
-     `cygwin_premain1', `cygwin_premain2', `cygwin_premain3', and
-     `environ'.  [This option is specific to the i386 PE targeted port
+     DLLs will not be re-exported, nor will symbols specifying the DLL's
+     internal layout such as those beginning with '_head_' or ending
+     with '_iname'.  In addition, no symbols from 'libgcc', 'libstd++',
+     'libmingw32', or 'crtX.o' will be exported.  Symbols whose names
+     begin with '__rtti_' or '__builtin_' will not be exported, to help
+     with C++ DLLs.  Finally, there is an extensive list of
+     cygwin-private symbols that are not exported (obviously, this
+     applies on when building DLLs for cygwin targets).  These
+     cygwin-excludes are: '_cygwin_dll_entry@12',
+     '_cygwin_crt0_common@8', '_cygwin_noncygwin_dll_entry@12',
+     '_fmode', '_impure_ptr', 'cygwin_attach_dll', 'cygwin_premain0',
+     'cygwin_premain1', 'cygwin_premain2', 'cygwin_premain3', and
+     'environ'.  [This option is specific to the i386 PE targeted port
      of the linker]
 
-`--exclude-symbols SYMBOL,SYMBOL,...'
+'--exclude-symbols SYMBOL,SYMBOL,...'
      Specifies a list of symbols which should not be automatically
      exported.  The symbol names may be delimited by commas or colons.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--exclude-all-symbols'
+'--exclude-all-symbols'
      Specifies no symbols should be automatically exported.  [This
      option is specific to the i386 PE targeted port of the linker]
 
-`--file-alignment'
-     Specify the file alignment.  Sections in the file will always
-     begin at file offsets which are multiples of this number.  This
-     defaults to 512.  [This option is specific to the i386 PE targeted
-     port of the linker]
+'--file-alignment'
+     Specify the file alignment.  Sections in the file will always begin
+     at file offsets which are multiples of this number.  This defaults
+     to 512.  [This option is specific to the i386 PE targeted port of
+     the linker]
 
-`--heap RESERVE'
-`--heap RESERVE,COMMIT'
+'--heap RESERVE'
+'--heap RESERVE,COMMIT'
      Specify the number of bytes of memory to reserve (and optionally
-     commit) to be used as heap for this program.  The default is 1Mb
+     commit) to be used as heap for this program.  The default is 1MB
      reserved, 4K committed.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--image-base VALUE'
+'--image-base VALUE'
      Use VALUE as the base address of your program or dll.  This is the
      lowest memory location that will be used when your program or dll
      is loaded.  To reduce the need to relocate and improve performance
@@ -1816,94 +1788,100 @@ by either a space or an equals sign.
      and 0x10000000 for dlls.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--kill-at'
+'--kill-at'
      If given, the stdcall suffixes (@NN) will be stripped from symbols
      before they are exported.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--large-address-aware'
-     If given, the appropriate bit in the "Characteristics" field of
-     the COFF header is set to indicate that this executable supports
-     virtual addresses greater than 2 gigabytes.  This should be used
-     in conjunction with the /3GB or /USERVA=VALUE megabytes switch in
-     the "[operating systems]" section of the BOOT.INI.  Otherwise,
-     this bit has no effect.  [This option is specific to PE targeted
-     ports of the linker]
+'--large-address-aware'
+     If given, the appropriate bit in the "Characteristics" field of the
+     COFF header is set to indicate that this executable supports
+     virtual addresses greater than 2 gigabytes.  This should be used in
+     conjunction with the /3GB or /USERVA=VALUE megabytes switch in the
+     "[operating systems]" section of the BOOT.INI. Otherwise, this bit
+     has no effect.  [This option is specific to PE targeted ports of
+     the linker]
+
+'--disable-large-address-aware'
+     Reverts the effect of a previous '--large-address-aware' option.
+     This is useful if '--large-address-aware' is always set by the
+     compiler driver (e.g.  Cygwin gcc) and the executable does not
+     support virtual addresses greater than 2 gigabytes.  [This option
+     is specific to PE targeted ports of the linker]
 
-`--major-image-version VALUE'
+'--major-image-version VALUE'
      Sets the major number of the "image version".  Defaults to 1.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--major-os-version VALUE'
+'--major-os-version VALUE'
      Sets the major number of the "os version".  Defaults to 4.  [This
      option is specific to the i386 PE targeted port of the linker]
 
-`--major-subsystem-version VALUE'
+'--major-subsystem-version VALUE'
      Sets the major number of the "subsystem version".  Defaults to 4.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--minor-image-version VALUE'
+'--minor-image-version VALUE'
      Sets the minor number of the "image version".  Defaults to 0.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--minor-os-version VALUE'
+'--minor-os-version VALUE'
      Sets the minor number of the "os version".  Defaults to 0.  [This
      option is specific to the i386 PE targeted port of the linker]
 
-`--minor-subsystem-version VALUE'
+'--minor-subsystem-version VALUE'
      Sets the minor number of the "subsystem version".  Defaults to 0.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--output-def FILE'
+'--output-def FILE'
      The linker will create the file FILE which will contain a DEF file
      corresponding to the DLL the linker is generating.  This DEF file
-     (which should be called `*.def') may be used to create an import
-     library with `dlltool' or may be used as a reference to
+     (which should be called '*.def') may be used to create an import
+     library with 'dlltool' or may be used as a reference to
      automatically or implicitly exported symbols.  [This option is
      specific to the i386 PE targeted port of the linker]
 
-`--out-implib FILE'
+'--out-implib FILE'
      The linker will create the file FILE which will contain an import
-     lib corresponding to the DLL the linker is generating. This import
-     lib (which should be called `*.dll.a' or `*.a' may be used to link
-     clients against the generated DLL; this behaviour makes it
-     possible to skip a separate `dlltool' import library creation step.
-     [This option is specific to the i386 PE targeted port of the
-     linker]
+     lib corresponding to the DLL the linker is generating.  This import
+     lib (which should be called '*.dll.a' or '*.a' may be used to link
+     clients against the generated DLL; this behaviour makes it possible
+     to skip a separate 'dlltool' import library creation step.  [This
+     option is specific to the i386 PE targeted port of the linker]
 
-`--enable-auto-image-base'
+'--enable-auto-image-base'
      Automatically choose the image base for DLLs, unless one is
-     specified using the `--image-base' argument.  By using a hash
+     specified using the '--image-base' argument.  By using a hash
      generated from the dllname to create unique image bases for each
      DLL, in-memory collisions and relocations which can delay program
      execution are avoided.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--disable-auto-image-base'
+'--disable-auto-image-base'
      Do not automatically generate a unique image base.  If there is no
-     user-specified image base (`--image-base') then use the platform
+     user-specified image base ('--image-base') then use the platform
      default.  [This option is specific to the i386 PE targeted port of
      the linker]
 
-`--dll-search-prefix STRING'
-     When linking dynamically to a dll without an import library,
-     search for `<string><basename>.dll' in preference to
-     `lib<basename>.dll'. This behaviour allows easy distinction
-     between DLLs built for the various "subplatforms": native, cygwin,
-     uwin, pw, etc.  For instance, cygwin DLLs typically use
-     `--dll-search-prefix=cyg'.  [This option is specific to the i386
-     PE targeted port of the linker]
-
-`--enable-auto-import'
-     Do sophisticated linking of `_symbol' to `__imp__symbol' for DATA
+'--dll-search-prefix STRING'
+     When linking dynamically to a dll without an import library, search
+     for '<string><basename>.dll' in preference to 'lib<basename>.dll'.
+     This behaviour allows easy distinction between DLLs built for the
+     various "subplatforms": native, cygwin, uwin, pw, etc.  For
+     instance, cygwin DLLs typically use '--dll-search-prefix=cyg'.
+     [This option is specific to the i386 PE targeted port of the
+     linker]
+
+'--enable-auto-import'
+     Do sophisticated linking of '_symbol' to '__imp__symbol' for DATA
      imports from DLLs, and create the necessary thunking symbols when
-     building the import libraries with those DATA exports. Note: Use
+     building the import libraries with those DATA exports.  Note: Use
      of the 'auto-import' extension will cause the text section of the
-     image file to be made writable. This does not conform to the
+     image file to be made writable.  This does not conform to the
      PE-COFF format specification published by Microsoft.
 
      Note - use of the 'auto-import' extension will also cause read only
@@ -1915,23 +1893,23 @@ by either a space or an equals sign.
      Using 'auto-import' generally will 'just work' - but sometimes you
      may see this message:
 
-     "variable '<var>' can't be auto-imported. Please read the
-     documentation for ld's `--enable-auto-import' for details."
+     "variable '<var>' can't be auto-imported.  Please read the
+     documentation for ld's '--enable-auto-import' for details."
 
      This message occurs when some (sub)expression accesses an address
      ultimately given by the sum of two constants (Win32 import tables
      only allow one).  Instances where this may occur include accesses
      to member fields of struct variables imported from a DLL, as well
      as using a constant index into an array variable imported from a
-     DLL.  Any multiword variable (arrays, structs, long long, etc) may
+     DLL. Any multiword variable (arrays, structs, long long, etc) may
      trigger this error condition.  However, regardless of the exact
-     data type of the offending exported variable, ld will always
-     detect it, issue the warning, and exit.
+     data type of the offending exported variable, ld will always detect
+     it, issue the warning, and exit.
 
      There are several ways to address this difficulty, regardless of
      the data type of the exported variable:
 
-     One way is to use -enable-runtime-pseudo-reloc switch. This leaves
+     One way is to use -enable-runtime-pseudo-reloc switch.  This leaves
      the task of adjusting references in your client code for runtime
      environment, so this method works only when runtime environment
      supports this feature.
@@ -1968,13 +1946,12 @@ by either a space or an equals sign.
 
      A third method of dealing with this difficulty is to abandon
      'auto-import' for the offending symbol and mark it with
-     `__declspec(dllimport)'.  However, in practice that requires using
+     '__declspec(dllimport)'.  However, in practice that requires using
      compile-time #defines to indicate whether you are building a DLL,
      building client code that will link to the DLL, or merely
-     building/linking to a static library.   In making the choice
-     between the various methods of resolving the 'direct address with
-     constant offset' problem, you should consider typical real-world
-     usage:
+     building/linking to a static library.  In making the choice between
+     the various methods of resolving the 'direct address with constant
+     offset' problem, you should consider typical real-world usage:
 
      Original:
           --foo.h
@@ -2014,16 +1991,16 @@ by either a space or an equals sign.
 
      A fourth way to avoid this problem is to re-code your library to
      use a functional interface rather than a data interface for the
-     offending variables (e.g. set_foo() and get_foo() accessor
+     offending variables (e.g.  set_foo() and get_foo() accessor
      functions).  [This option is specific to the i386 PE targeted port
      of the linker]
 
-`--disable-auto-import'
-     Do not attempt to do sophisticated linking of `_symbol' to
-     `__imp__symbol' for DATA imports from DLLs.  [This option is
+'--disable-auto-import'
+     Do not attempt to do sophisticated linking of '_symbol' to
+     '__imp__symbol' for DATA imports from DLLs.  [This option is
      specific to the i386 PE targeted port of the linker]
 
-`--enable-runtime-pseudo-reloc'
+'--enable-runtime-pseudo-reloc'
      If your code contains expressions described in -enable-auto-import
      section, that is, DATA imports from DLL with non-zero offset, this
      switch will create a vector of 'runtime pseudo relocations' which
@@ -2031,70 +2008,75 @@ by either a space or an equals sign.
      data in your client code.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--disable-runtime-pseudo-reloc'
+'--disable-runtime-pseudo-reloc'
      Do not create pseudo relocations for non-zero offset DATA imports
      from DLLs.  [This option is specific to the i386 PE targeted port
      of the linker]
 
-`--enable-extra-pe-debug'
+'--enable-extra-pe-debug'
      Show additional debug info related to auto-import symbol thunking.
      [This option is specific to the i386 PE targeted port of the
      linker]
 
-`--section-alignment'
+'--section-alignment'
      Sets the section alignment.  Sections in memory will always begin
      at addresses which are a multiple of this number.  Defaults to
      0x1000.  [This option is specific to the i386 PE targeted port of
      the linker]
 
-`--stack RESERVE'
-`--stack RESERVE,COMMIT'
+'--stack RESERVE'
+'--stack RESERVE,COMMIT'
      Specify the number of bytes of memory to reserve (and optionally
-     commit) to be used as stack for this program.  The default is 2Mb
+     commit) to be used as stack for this program.  The default is 2MB
      reserved, 4K committed.  [This option is specific to the i386 PE
      targeted port of the linker]
 
-`--subsystem WHICH'
-`--subsystem WHICH:MAJOR'
-`--subsystem WHICH:MAJOR.MINOR'
+'--subsystem WHICH'
+'--subsystem WHICH:MAJOR'
+'--subsystem WHICH:MAJOR.MINOR'
      Specifies the subsystem under which your program will execute.  The
-     legal values for WHICH are `native', `windows', `console',
-     `posix', and `xbox'.  You may optionally set the subsystem version
-     also.  Numeric values are also accepted for WHICH.  [This option
-     is specific to the i386 PE targeted port of the linker]
+     legal values for WHICH are 'native', 'windows', 'console', 'posix',
+     and 'xbox'.  You may optionally set the subsystem version also.
+     Numeric values are also accepted for WHICH.  [This option is
+     specific to the i386 PE targeted port of the linker]
 
-     The following options set flags in the `DllCharacteristics' field
+     The following options set flags in the 'DllCharacteristics' field
      of the PE file header: [These options are specific to PE targeted
      ports of the linker]
 
-`--dynamicbase'
+'--dynamicbase'
      The image base address may be relocated using address space layout
-     randomization (ASLR).  This feature was introduced with MS Windows
+     randomization (ASLR). This feature was introduced with MS Windows
      Vista for i386 PE targets.
 
-`--forceinteg'
+'--forceinteg'
      Code integrity checks are enforced.
 
-`--nxcompat'
+'--nxcompat'
      The image is compatible with the Data Execution Prevention.  This
      feature was introduced with MS Windows XP SP2 for i386 PE targets.
 
-`--no-isolation'
+'--no-isolation'
      Although the image understands isolation, do not isolate the image.
 
-`--no-seh'
+'--no-seh'
      The image does not use SEH. No SE handler may be called from this
      image.
 
-`--no-bind'
+'--no-bind'
      Do not bind this image.
 
-`--wdmdriver'
+'--wdmdriver'
      The driver uses the MS Windows Driver Model.
 
-`--tsaware'
+'--tsaware'
      The image is Terminal Server aware.
 
+'--insert-timestamp'
+     Insert a real timestamp into the image, rather than the default
+     value of zero.  This will result in a slightly different results
+     with each invocation, which could be helpful for distributing
+     unique images.
 
 2.1.2 Options specific to C6X uClinux targets
 ---------------------------------------------
@@ -2103,52 +2085,64 @@ The C6X uClinux target uses a binary format called DSBT to support
 shared libraries.  Each shared library in the system needs to have a
 unique index; all executables use an index of 0.
 
-`--dsbt-size SIZE'
+'--dsbt-size SIZE'
      This option sets the number of entires in the DSBT of the current
      executable or shared library to SIZE.  The default is to create a
      table with 64 entries.
 
-`--dsbt-index INDEX'
-     This option sets the DSBT index of the current executable or
-     shared library to INDEX.  The default is 0, which is appropriate
-     for generating executables.  If a shared library is generated with
-     a DSBT index of 0, the `R_C6000_DSBT_INDEX' relocs are copied into
+'--dsbt-index INDEX'
+     This option sets the DSBT index of the current executable or shared
+     library to INDEX.  The default is 0, which is appropriate for
+     generating executables.  If a shared library is generated with a
+     DSBT index of 0, the 'R_C6000_DSBT_INDEX' relocs are copied into
      the output file.
 
-     The `--no-merge-exidx-entries' switch disables the merging of
+     The '--no-merge-exidx-entries' switch disables the merging of
      adjacent exidx entries in frame unwind info.
 
-
 2.1.3 Options specific to Motorola 68HC11 and 68HC12 targets
 ------------------------------------------------------------
 
 The 68HC11 and 68HC12 linkers support specific options to control the
 memory bank switching mapping and trampoline code generation.
 
-`--no-trampoline'
-     This option disables the generation of trampoline. By default a
-     trampoline is generated for each far function which is called
-     using a `jsr' instruction (this happens when a pointer to a far
-     function is taken).
+'--no-trampoline'
+     This option disables the generation of trampoline.  By default a
+     trampoline is generated for each far function which is called using
+     a 'jsr' instruction (this happens when a pointer to a far function
+     is taken).
 
-`--bank-window NAME'
+'--bank-window NAME'
      This option indicates to the linker the name of the memory region
-     in the `MEMORY' specification that describes the memory bank
+     in the 'MEMORY' specification that describes the memory bank
      window.  The definition of such region is then used by the linker
      to compute paging and addresses within the memory window.
 
-
 2.1.4 Options specific to Motorola 68K target
 ---------------------------------------------
 
 The following options are supported to control handling of GOT
 generation when linking for 68K targets.
 
-`--got=TYPE'
+'--got=TYPE'
      This option tells the linker which GOT generation scheme to use.
-     TYPE should be one of `single', `negative', `multigot' or
-     `target'.  For more information refer to the Info entry for `ld'.
+     TYPE should be one of 'single', 'negative', 'multigot' or 'target'.
+     For more information refer to the Info entry for 'ld'.
+
+2.1.5 Options specific to MIPS targets
+--------------------------------------
 
+The following options are supported to control microMIPS instruction
+generation when linking for MIPS targets.
+
+'--insn32'
+'--no-insn32'
+     These options control the choice of microMIPS instructions used in
+     code generated by the linker, such as that in the PLT or lazy
+     binding stubs, or in relaxation.  If '--insn32' is used, then the
+     linker only uses 32-bit instruction encodings.  By default or if
+     '--no-insn32' is used, all instruction encodings are used,
+     including 16-bit ones where possible.
 
 
 File: ld.info,  Node: Environment,  Prev: Options,  Up: Invocation
@@ -2156,14 +2150,14 @@ File: ld.info,  Node: Environment,  Prev: Options,  Up: Invocation
 2.2 Environment Variables
 =========================
 
-You can change the behaviour of `ld' with the environment variables
-`GNUTARGET', `LDEMULATION' and `COLLECT_NO_DEMANGLE'.
+You can change the behaviour of 'ld' with the environment variables
+'GNUTARGET', 'LDEMULATION' and 'COLLECT_NO_DEMANGLE'.
 
-   `GNUTARGET' determines the input-file object format if you don't use
-`-b' (or its synonym `--format').  Its value should be one of the BFD
-names for an input format (*note BFD::).  If there is no `GNUTARGET' in
-the environment, `ld' uses the natural format of the target. If
-`GNUTARGET' is set to `default' then BFD attempts to discover the input
+   'GNUTARGET' determines the input-file object format if you don't use
+'-b' (or its synonym '--format').  Its value should be one of the BFD
+names for an input format (*note BFD::).  If there is no 'GNUTARGET' in
+the environment, 'ld' uses the natural format of the target.  If
+'GNUTARGET' is set to 'default' then BFD attempts to discover the input
 format by examining binary input files; this method often succeeds, but
 there are potential ambiguities, since there is no method of ensuring
 that the magic number used to specify object-file formats is unique.
@@ -2171,19 +2165,19 @@ However, the configuration procedure for BFD on each system places the
 conventional format for that system first in the search-list, so
 ambiguities are resolved in favor of convention.
 
-   `LDEMULATION' determines the default emulation if you don't use the
-`-m' option.  The emulation can affect various aspects of linker
+   'LDEMULATION' determines the default emulation if you don't use the
+'-m' option.  The emulation can affect various aspects of linker
 behaviour, particularly the default linker script.  You can list the
-available emulations with the `--verbose' or `-V' options.  If the `-m'
-option is not used, and the `LDEMULATION' environment variable is not
+available emulations with the '--verbose' or '-V' options.  If the '-m'
+option is not used, and the 'LDEMULATION' environment variable is not
 defined, the default emulation depends upon how the linker was
 configured.
 
    Normally, the linker will default to demangling symbols.  However, if
-`COLLECT_NO_DEMANGLE' is set in the environment, then it will default
-to not demangling symbols.  This environment variable is used in a
-similar fashion by the `gcc' linker wrapper program.  The default may
-be overridden by the `--demangle' and `--no-demangle' options.
+'COLLECT_NO_DEMANGLE' is set in the environment, then it will default to
+not demangling symbols.  This environment variable is used in a similar
+fashion by the 'gcc' linker wrapper program.  The default may be
+overridden by the '--demangle' and '--no-demangle' options.
 
 
 File: ld.info,  Node: Scripts,  Next: Machine Dependent,  Prev: Invocation,  Up: Top
@@ -2194,20 +2188,20 @@ File: ld.info,  Node: Scripts,  Next: Machine Dependent,  Prev: Invocation,  Up:
 Every link is controlled by a "linker script".  This script is written
 in the linker command language.
 
-   The main purpose of the linker script is to describe how the
-sections in the input files should be mapped into the output file, and
-to control the memory layout of the output file.  Most linker scripts
-do nothing more than this.  However, when necessary, the linker script
-can also direct the linker to perform many other operations, using the
-commands described below.
+   The main purpose of the linker script is to describe how the sections
+in the input files should be mapped into the output file, and to control
+the memory layout of the output file.  Most linker scripts do nothing
+more than this.  However, when necessary, the linker script can also
+direct the linker to perform many other operations, using the commands
+described below.
 
    The linker always uses a linker script.  If you do not supply one
 yourself, the linker will use a default script that is compiled into the
-linker executable.  You can use the `--verbose' command line option to
+linker executable.  You can use the '--verbose' command line option to
 display the default linker script.  Certain command line options, such
-as `-r' or `-N', will affect the default linker script.
+as '-r' or '-N', will affect the default linker script.
 
-   You may supply your own linker script by using the `-T' command line
+   You may supply your own linker script by using the '-T' command line
 option.  When you do this, your linker script will replace the default
 linker script.
 
@@ -2240,12 +2234,12 @@ describe the linker script language.
 
    The linker combines input files into a single output file.  The
 output file and each input file are in a special data format known as an
-"object file format".  Each file is called an "object file".  The
-output file is often called an "executable", but for our purposes we
-will also call it an object file.  Each object file has, among other
-things, a list of "sections".  We sometimes refer to a section in an
-input file as an "input section"; similarly, a section in the output
-file is an "output section".
+"object file format".  Each file is called an "object file".  The output
+file is often called an "executable", but for our purposes we will also
+call it an object file.  Each object file has, among other things, a
+list of "sections".  We sometimes refer to a section in an input file as
+an "input section"; similarly, a section in the output file is an
+"output section".
 
    Each section in an object file has a name and a size.  Most sections
 also have an associated block of data, known as the "section contents".
@@ -2259,28 +2253,28 @@ debugging information.
 
    Every loadable or allocatable output section has two addresses.  The
 first is the "VMA", or virtual memory address.  This is the address the
-section will have when the output file is run.  The second is the
-"LMA", or load memory address.  This is the address at which the
-section will be loaded.  In most cases the two addresses will be the
-same.  An example of when they might be different is when a data section
-is loaded into ROM, and then copied into RAM when the program starts up
-(this technique is often used to initialize global variables in a ROM
-based system).  In this case the ROM address would be the LMA, and the
-RAM address would be the VMA.
-
-   You can see the sections in an object file by using the `objdump'
-program with the `-h' option.
+section will have when the output file is run.  The second is the "LMA",
+or load memory address.  This is the address at which the section will
+be loaded.  In most cases the two addresses will be the same.  An
+example of when they might be different is when a data section is loaded
+into ROM, and then copied into RAM when the program starts up (this
+technique is often used to initialize global variables in a ROM based
+system).  In this case the ROM address would be the LMA, and the RAM
+address would be the VMA.
+
+   You can see the sections in an object file by using the 'objdump'
+program with the '-h' option.
 
    Every object file also has a list of "symbols", known as the "symbol
 table".  A symbol may be defined or undefined.  Each symbol has a name,
-and each defined symbol has an address, among other information.  If
-you compile a C or C++ program into an object file, you will get a
-defined symbol for every defined function and global or static
-variable.  Every undefined function or global variable which is
-referenced in the input file will become an undefined symbol.
+and each defined symbol has an address, among other information.  If you
+compile a C or C++ program into an object file, you will get a defined
+symbol for every defined function and global or static variable.  Every
+undefined function or global variable which is referenced in the input
+file will become an undefined symbol.
 
-   You can see the symbols in an object file by using the `nm' program,
-or by using the `objdump' program with the `-t' option.
+   You can see the symbols in an object file by using the 'nm' program,
+or by using the 'objdump' program with the '-t' option.
 
 
 File: ld.info,  Node: Script Format,  Next: Simple Example,  Prev: Basic Script Concepts,  Up: Scripts
@@ -2302,7 +2296,7 @@ in double quotes.  There is no way to use a double quote character in a
 file name.
 
    You may include comments in linker scripts just as in C, delimited by
-`/*' and `*/'.  As in C, comments are syntactically equivalent to
+'/*' and '*/'.  As in C, comments are syntactically equivalent to
 whitespace.
 
 
@@ -2313,16 +2307,15 @@ File: ld.info,  Node: Simple Example,  Next: Simple Commands,  Prev: Script Form
 
 Many linker scripts are fairly simple.
 
-   The simplest possible linker script has just one command:
-`SECTIONS'.  You use the `SECTIONS' command to describe the memory
-layout of the output file.
+   The simplest possible linker script has just one command: 'SECTIONS'.
+You use the 'SECTIONS' command to describe the memory layout of the
+output file.
 
-   The `SECTIONS' command is a powerful command.  Here we will describe
+   The 'SECTIONS' command is a powerful command.  Here we will describe
 a simple use of it.  Let's assume your program consists only of code,
-initialized data, and uninitialized data.  These will be in the
-`.text', `.data', and `.bss' sections, respectively.  Let's assume
-further that these are the only sections which appear in your input
-files.
+initialized data, and uninitialized data.  These will be in the '.text',
+'.data', and '.bss' sections, respectively.  Let's assume further that
+these are the only sections which appear in your input files.
 
    For this example, let's say that the code should be loaded at address
 0x10000, and that the data should start at address 0x8000000.  Here is a
@@ -2336,42 +2329,42 @@ linker script which will do that:
        .bss : { *(.bss) }
      }
 
-   You write the `SECTIONS' command as the keyword `SECTIONS', followed
+   You write the 'SECTIONS' command as the keyword 'SECTIONS', followed
 by a series of symbol assignments and output section descriptions
 enclosed in curly braces.
 
-   The first line inside the `SECTIONS' command of the above example
-sets the value of the special symbol `.', which is the location
-counter.  If you do not specify the address of an output section in some
-other way (other ways are described later), the address is set from the
-current value of the location counter.  The location counter is then
-incremented by the size of the output section.  At the start of the
-`SECTIONS' command, the location counter has the value `0'.
+   The first line inside the 'SECTIONS' command of the above example
+sets the value of the special symbol '.', which is the location counter.
+If you do not specify the address of an output section in some other way
+(other ways are described later), the address is set from the current
+value of the location counter.  The location counter is then incremented
+by the size of the output section.  At the start of the 'SECTIONS'
+command, the location counter has the value '0'.
 
-   The second line defines an output section, `.text'.  The colon is
+   The second line defines an output section, '.text'.  The colon is
 required syntax which may be ignored for now.  Within the curly braces
 after the output section name, you list the names of the input sections
-which should be placed into this output section.  The `*' is a wildcard
-which matches any file name.  The expression `*(.text)' means all
-`.text' input sections in all input files.
-
-   Since the location counter is `0x10000' when the output section
-`.text' is defined, the linker will set the address of the `.text'
-section in the output file to be `0x10000'.
-
-   The remaining lines define the `.data' and `.bss' sections in the
-output file.  The linker will place the `.data' output section at
-address `0x8000000'.  After the linker places the `.data' output
-section, the value of the location counter will be `0x8000000' plus the
-size of the `.data' output section.  The effect is that the linker will
-place the `.bss' output section immediately after the `.data' output
+which should be placed into this output section.  The '*' is a wildcard
+which matches any file name.  The expression '*(.text)' means all
+'.text' input sections in all input files.
+
+   Since the location counter is '0x10000' when the output section
+'.text' is defined, the linker will set the address of the '.text'
+section in the output file to be '0x10000'.
+
+   The remaining lines define the '.data' and '.bss' sections in the
+output file.  The linker will place the '.data' output section at
+address '0x8000000'.  After the linker places the '.data' output
+section, the value of the location counter will be '0x8000000' plus the
+size of the '.data' output section.  The effect is that the linker will
+place the '.bss' output section immediately after the '.data' output
 section in memory.
 
    The linker will ensure that each output section has the required
 alignment, by increasing the location counter if necessary.  In this
-example, the specified addresses for the `.text' and `.data' sections
-will probably satisfy any alignment constraints, but the linker may
-have to create a small gap between the `.data' and `.bss' sections.
+example, the specified addresses for the '.text' and '.data' sections
+will probably satisfy any alignment constraints, but the linker may have
+to create a small gap between the '.data' and '.bss' sections.
 
    That's it!  That's a simple and complete linker script.
 
@@ -2387,7 +2380,6 @@ In this section we describe the simple linker script commands.
 
 * Entry Point::			Setting the entry point
 * File Commands::		Commands dealing with files
-
 * Format Commands::		Commands dealing with object file formats
 
 * REGION_ALIAS::		Assign alias names to memory regions
@@ -2400,25 +2392,21 @@ File: ld.info,  Node: Entry Point,  Next: File Commands,  Up: Simple Commands
 -----------------------------
 
 The first instruction to execute in a program is called the "entry
-point".  You can use the `ENTRY' linker script command to set the entry
+point".  You can use the 'ENTRY' linker script command to set the entry
 point.  The argument is a symbol name:
      ENTRY(SYMBOL)
 
    There are several ways to set the entry point.  The linker will set
 the entry point by trying each of the following methods in order, and
 stopping when one of them succeeds:
-   * the `-e' ENTRY command-line option;
-
-   * the `ENTRY(SYMBOL)' command in a linker script;
-
-   * the value of a target specific symbol, if it is defined;  For many
-     targets this is `start', but PE and BeOS based systems for example
+   * the '-e' ENTRY command-line option;
+   * the 'ENTRY(SYMBOL)' command in a linker script;
+   * the value of a target specific symbol, if it is defined; For many
+     targets this is 'start', but PE and BeOS based systems for example
      check a list of possible entry symbols, matching the first one
      found.
-
-   * the address of the first byte of the `.text' section, if present;
-
-   * The address `0'.
+   * the address of the first byte of the '.text' section, if present;
+   * The address '0'.
 
 
 File: ld.info,  Node: File Commands,  Next: Format Commands,  Prev: Entry Point,  Up: Simple Commands
@@ -2428,85 +2416,85 @@ File: ld.info,  Node: File Commands,  Next: Format Commands,  Prev: Entry Point,
 
 Several linker script commands deal with files.
 
-`INCLUDE FILENAME'
-     Include the linker script FILENAME at this point.  The file will
-     be searched for in the current directory, and in any directory
-     specified with the `-L' option.  You can nest calls to `INCLUDE'
-     up to 10 levels deep.
+'INCLUDE FILENAME'
+     Include the linker script FILENAME at this point.  The file will be
+     searched for in the current directory, and in any directory
+     specified with the '-L' option.  You can nest calls to 'INCLUDE' up
+     to 10 levels deep.
 
-     You can place `INCLUDE' directives at the top level, in `MEMORY' or
-     `SECTIONS' commands, or in output section descriptions.
+     You can place 'INCLUDE' directives at the top level, in 'MEMORY' or
+     'SECTIONS' commands, or in output section descriptions.
 
-`INPUT(FILE, FILE, ...)'
-`INPUT(FILE FILE ...)'
-     The `INPUT' command directs the linker to include the named files
+'INPUT(FILE, FILE, ...)'
+'INPUT(FILE FILE ...)'
+     The 'INPUT' command directs the linker to include the named files
      in the link, as though they were named on the command line.
 
-     For example, if you always want to include `subr.o' any time you do
+     For example, if you always want to include 'subr.o' any time you do
      a link, but you can't be bothered to put it on every link command
-     line, then you can put `INPUT (subr.o)' in your linker script.
+     line, then you can put 'INPUT (subr.o)' in your linker script.
 
      In fact, if you like, you can list all of your input files in the
-     linker script, and then invoke the linker with nothing but a `-T'
+     linker script, and then invoke the linker with nothing but a '-T'
      option.
 
      In case a "sysroot prefix" is configured, and the filename starts
-     with the `/' character, and the script being processed was located
-     inside the "sysroot prefix", the filename will be looked for in
-     the "sysroot prefix".  Otherwise, the linker will try to open the
-     file in the current directory.  If it is not found, the linker
-     will search through the archive library search path.  See the
-     description of `-L' in *note Command Line Options: Options.
+     with the '/' character, and the script being processed was located
+     inside the "sysroot prefix", the filename will be looked for in the
+     "sysroot prefix".  Otherwise, the linker will try to open the file
+     in the current directory.  If it is not found, the linker will
+     search through the archive library search path.  See the
+     description of '-L' in *note Command Line Options: Options.
 
-     If you use `INPUT (-lFILE)', `ld' will transform the name to
-     `libFILE.a', as with the command line argument `-l'.
+     If you use 'INPUT (-lFILE)', 'ld' will transform the name to
+     'libFILE.a', as with the command line argument '-l'.
 
-     When you use the `INPUT' command in an implicit linker script, the
+     When you use the 'INPUT' command in an implicit linker script, the
      files will be included in the link at the point at which the linker
      script file is included.  This can affect archive searching.
 
-`GROUP(FILE, FILE, ...)'
-`GROUP(FILE FILE ...)'
-     The `GROUP' command is like `INPUT', except that the named files
+'GROUP(FILE, FILE, ...)'
+'GROUP(FILE FILE ...)'
+     The 'GROUP' command is like 'INPUT', except that the named files
      should all be archives, and they are searched repeatedly until no
-     new undefined references are created.  See the description of `-('
+     new undefined references are created.  See the description of '-('
      in *note Command Line Options: Options.
 
-`AS_NEEDED(FILE, FILE, ...)'
-`AS_NEEDED(FILE FILE ...)'
-     This construct can appear only inside of the `INPUT' or `GROUP'
+'AS_NEEDED(FILE, FILE, ...)'
+'AS_NEEDED(FILE FILE ...)'
+     This construct can appear only inside of the 'INPUT' or 'GROUP'
      commands, among other filenames.  The files listed will be handled
-     as if they appear directly in the `INPUT' or `GROUP' commands,
-     with the exception of ELF shared libraries, that will be added only
-     when they are actually needed.  This construct essentially enables
-     `--as-needed' option for all the files listed inside of it and
-     restores previous `--as-needed' resp. `--no-as-needed' setting
+     as if they appear directly in the 'INPUT' or 'GROUP' commands, with
+     the exception of ELF shared libraries, that will be added only when
+     they are actually needed.  This construct essentially enables
+     '--as-needed' option for all the files listed inside of it and
+     restores previous '--as-needed' resp.  '--no-as-needed' setting
      afterwards.
 
-`OUTPUT(FILENAME)'
-     The `OUTPUT' command names the output file.  Using
-     `OUTPUT(FILENAME)' in the linker script is exactly like using `-o
+'OUTPUT(FILENAME)'
+     The 'OUTPUT' command names the output file.  Using
+     'OUTPUT(FILENAME)' in the linker script is exactly like using '-o
      FILENAME' on the command line (*note Command Line Options:
      Options.).  If both are used, the command line option takes
      precedence.
 
-     You can use the `OUTPUT' command to define a default name for the
-     output file other than the usual default of `a.out'.
+     You can use the 'OUTPUT' command to define a default name for the
+     output file other than the usual default of 'a.out'.
 
-`SEARCH_DIR(PATH)'
-     The `SEARCH_DIR' command adds PATH to the list of paths where `ld'
-     looks for archive libraries.  Using `SEARCH_DIR(PATH)' is exactly
-     like using `-L PATH' on the command line (*note Command Line
+'SEARCH_DIR(PATH)'
+     The 'SEARCH_DIR' command adds PATH to the list of paths where 'ld'
+     looks for archive libraries.  Using 'SEARCH_DIR(PATH)' is exactly
+     like using '-L PATH' on the command line (*note Command Line
      Options: Options.).  If both are used, then the linker will search
      both paths.  Paths specified using the command line option are
      searched first.
 
-`STARTUP(FILENAME)'
-     The `STARTUP' command is just like the `INPUT' command, except
-     that FILENAME will become the first input file to be linked, as
-     though it were specified first on the command line.  This may be
-     useful when using a system in which the entry point is always the
-     start of the first file.
+'STARTUP(FILENAME)'
+     The 'STARTUP' command is just like the 'INPUT' command, except that
+     FILENAME will become the first input file to be linked, as though
+     it were specified first on the command line.  This may be useful
+     when using a system in which the entry point is always the start of
+     the first file.
 
 
 File: ld.info,  Node: Format Commands,  Next: REGION_ALIAS,  Prev: File Commands,  Up: Simple Commands
@@ -2516,38 +2504,38 @@ File: ld.info,  Node: Format Commands,  Next: REGION_ALIAS,  Prev: File Commands
 
 A couple of linker script commands deal with object file formats.
 
-`OUTPUT_FORMAT(BFDNAME)'
-`OUTPUT_FORMAT(DEFAULT, BIG, LITTLE)'
-     The `OUTPUT_FORMAT' command names the BFD format to use for the
-     output file (*note BFD::).  Using `OUTPUT_FORMAT(BFDNAME)' is
-     exactly like using `--oformat BFDNAME' on the command line (*note
+'OUTPUT_FORMAT(BFDNAME)'
+'OUTPUT_FORMAT(DEFAULT, BIG, LITTLE)'
+     The 'OUTPUT_FORMAT' command names the BFD format to use for the
+     output file (*note BFD::).  Using 'OUTPUT_FORMAT(BFDNAME)' is
+     exactly like using '--oformat BFDNAME' on the command line (*note
      Command Line Options: Options.).  If both are used, the command
      line option takes precedence.
 
-     You can use `OUTPUT_FORMAT' with three arguments to use different
-     formats based on the `-EB' and `-EL' command line options.  This
+     You can use 'OUTPUT_FORMAT' with three arguments to use different
+     formats based on the '-EB' and '-EL' command line options.  This
      permits the linker script to set the output format based on the
      desired endianness.
 
-     If neither `-EB' nor `-EL' are used, then the output format will
-     be the first argument, DEFAULT.  If `-EB' is used, the output
-     format will be the second argument, BIG.  If `-EL' is used, the
-     output format will be the third argument, LITTLE.
+     If neither '-EB' nor '-EL' are used, then the output format will be
+     the first argument, DEFAULT.  If '-EB' is used, the output format
+     will be the second argument, BIG.  If '-EL' is used, the output
+     format will be the third argument, LITTLE.
 
-     For example, the default linker script for the MIPS ELF target
-     uses this command:
+     For example, the default linker script for the MIPS ELF target uses
+     this command:
           OUTPUT_FORMAT(elf32-bigmips, elf32-bigmips, elf32-littlemips)
      This says that the default format for the output file is
-     `elf32-bigmips', but if the user uses the `-EL' command line
-     option, the output file will be created in the `elf32-littlemips'
+     'elf32-bigmips', but if the user uses the '-EL' command line
+     option, the output file will be created in the 'elf32-littlemips'
      format.
 
-`TARGET(BFDNAME)'
-     The `TARGET' command names the BFD format to use when reading input
-     files.  It affects subsequent `INPUT' and `GROUP' commands.  This
-     command is like using `-b BFDNAME' on the command line (*note
-     Command Line Options: Options.).  If the `TARGET' command is used
-     but `OUTPUT_FORMAT' is not, then the last `TARGET' command is also
+'TARGET(BFDNAME)'
+     The 'TARGET' command names the BFD format to use when reading input
+     files.  It affects subsequent 'INPUT' and 'GROUP' commands.  This
+     command is like using '-b BFDNAME' on the command line (*note
+     Command Line Options: Options.).  If the 'TARGET' command is used
+     but 'OUTPUT_FORMAT' is not, then the last 'TARGET' command is also
      used to set the format for the output file.  *Note BFD::.
 
 
@@ -2562,43 +2550,40 @@ region.
 
      REGION_ALIAS(ALIAS, REGION)
 
-   The `REGION_ALIAS' function creates an alias name ALIAS for the
+   The 'REGION_ALIAS' function creates an alias name ALIAS for the
 memory region REGION.  This allows a flexible mapping of output sections
 to memory regions.  An example follows.
 
    Suppose we have an application for embedded systems which come with
 various memory storage devices.  All have a general purpose, volatile
-memory `RAM' that allows code execution or data storage.  Some may have
-a read-only, non-volatile memory `ROM' that allows code execution and
+memory 'RAM' that allows code execution or data storage.  Some may have
+a read-only, non-volatile memory 'ROM' that allows code execution and
 read-only data access.  The last variant is a read-only, non-volatile
-memory `ROM2' with read-only data access and no code execution
+memory 'ROM2' with read-only data access and no code execution
 capability.  We have four output sections:
 
-   * `.text' program code;
-
-   * `.rodata' read-only data;
-
-   * `.data' read-write initialized data;
-
-   * `.bss' read-write zero initialized data.
+   * '.text' program code;
+   * '.rodata' read-only data;
+   * '.data' read-write initialized data;
+   * '.bss' read-write zero initialized data.
 
    The goal is to provide a linker command file that contains a system
 independent part defining the output sections and a system dependent
 part mapping the output sections to the memory regions available on the
 system.  Our embedded systems come with three different memory setups
-`A', `B' and `C':
+'A', 'B' and 'C':
 Section            Variant A          Variant B          Variant C
 .text              RAM                ROM                ROM
 .rodata            RAM                ROM                ROM2
 .data              RAM                RAM/ROM            RAM/ROM2
 .bss               RAM                RAM                RAM
-   The notation `RAM/ROM' or `RAM/ROM2' means that this section is
-loaded into region `ROM' or `ROM2' respectively.  Please note that the
-load address of the `.data' section starts in all three variants at the
-end of the `.rodata' section.
+   The notation 'RAM/ROM' or 'RAM/ROM2' means that this section is
+loaded into region 'ROM' or 'ROM2' respectively.  Please note that the
+load address of the '.data' section starts in all three variants at the
+end of the '.rodata' section.
 
    The base linker script that deals with the output sections follows.
-It includes the system dependent `linkcmds.memory' file that describes
+It includes the system dependent 'linkcmds.memory' file that describes
 the memory layout:
      INCLUDE linkcmds.memory
 
@@ -2626,11 +2611,11 @@ the memory layout:
            } > REGION_BSS
        }
 
-   Now we need three different `linkcmds.memory' files to define memory
-regions and alias names.  The content of `linkcmds.memory' for the three
-variants `A', `B' and `C':
-`A'
-     Here everything goes into the `RAM'.
+   Now we need three different 'linkcmds.memory' files to define memory
+regions and alias names.  The content of 'linkcmds.memory' for the three
+variants 'A', 'B' and 'C':
+'A'
+     Here everything goes into the 'RAM'.
           MEMORY
             {
               RAM : ORIGIN = 0, LENGTH = 4M
@@ -2640,12 +2625,11 @@ variants `A', `B' and `C':
           REGION_ALIAS("REGION_RODATA", RAM);
           REGION_ALIAS("REGION_DATA", RAM);
           REGION_ALIAS("REGION_BSS", RAM);
-
-`B'
-     Program code and read-only data go into the `ROM'.  Read-write
-     data goes into the `RAM'.  An image of the initialized data is
-     loaded into the `ROM' and will be copied during system start into
-     the `RAM'.
+'B'
+     Program code and read-only data go into the 'ROM'.  Read-write data
+     goes into the 'RAM'.  An image of the initialized data is loaded
+     into the 'ROM' and will be copied during system start into the
+     'RAM'.
           MEMORY
             {
               ROM : ORIGIN = 0, LENGTH = 3M
@@ -2656,12 +2640,11 @@ variants `A', `B' and `C':
           REGION_ALIAS("REGION_RODATA", ROM);
           REGION_ALIAS("REGION_DATA", RAM);
           REGION_ALIAS("REGION_BSS", RAM);
-
-`C'
-     Program code goes into the `ROM'.  Read-only data goes into the
-     `ROM2'.  Read-write data goes into the `RAM'.  An image of the
-     initialized data is loaded into the `ROM2' and will be copied
-     during system start into the `RAM'.
+'C'
+     Program code goes into the 'ROM'.  Read-only data goes into the
+     'ROM2'.  Read-write data goes into the 'RAM'.  An image of the
+     initialized data is loaded into the 'ROM2' and will be copied
+     during system start into the 'RAM'.
           MEMORY
             {
               ROM : ORIGIN = 0, LENGTH = 2M
@@ -2675,7 +2658,7 @@ variants `A', `B' and `C':
           REGION_ALIAS("REGION_BSS", RAM);
 
    It is possible to write a common system initialization routine to
-copy the `.data' section from `ROM' or `ROM2' into the `RAM' if
+copy the '.data' section from 'ROM' or 'ROM2' into the 'RAM' if
 necessary:
      #include <string.h>
 
@@ -2699,42 +2682,42 @@ File: ld.info,  Node: Miscellaneous Commands,  Prev: REGION_ALIAS,  Up: Simple C
 
 There are a few other linker scripts commands.
 
-`ASSERT(EXP, MESSAGE)'
+'ASSERT(EXP, MESSAGE)'
      Ensure that EXP is non-zero.  If it is zero, then exit the linker
      with an error code, and print MESSAGE.
 
-`EXTERN(SYMBOL SYMBOL ...)'
+'EXTERN(SYMBOL SYMBOL ...)'
      Force SYMBOL to be entered in the output file as an undefined
      symbol.  Doing this may, for example, trigger linking of additional
      modules from standard libraries.  You may list several SYMBOLs for
-     each `EXTERN', and you may use `EXTERN' multiple times.  This
-     command has the same effect as the `-u' command-line option.
+     each 'EXTERN', and you may use 'EXTERN' multiple times.  This
+     command has the same effect as the '-u' command-line option.
 
-`FORCE_COMMON_ALLOCATION'
-     This command has the same effect as the `-d' command-line option:
-     to make `ld' assign space to common symbols even if a relocatable
-     output file is specified (`-r').
+'FORCE_COMMON_ALLOCATION'
+     This command has the same effect as the '-d' command-line option:
+     to make 'ld' assign space to common symbols even if a relocatable
+     output file is specified ('-r').
 
-`INHIBIT_COMMON_ALLOCATION'
-     This command has the same effect as the `--no-define-common'
-     command-line option: to make `ld' omit the assignment of addresses
+'INHIBIT_COMMON_ALLOCATION'
+     This command has the same effect as the '--no-define-common'
+     command-line option: to make 'ld' omit the assignment of addresses
      to common symbols even for a non-relocatable output file.
 
-`INSERT [ AFTER | BEFORE ] OUTPUT_SECTION'
-     This command is typically used in a script specified by `-T' to
-     augment the default `SECTIONS' with, for example, overlays.  It
+'INSERT [ AFTER | BEFORE ] OUTPUT_SECTION'
+     This command is typically used in a script specified by '-T' to
+     augment the default 'SECTIONS' with, for example, overlays.  It
      inserts all prior linker script statements after (or before)
-     OUTPUT_SECTION, and also causes `-T' to not override the default
+     OUTPUT_SECTION, and also causes '-T' to not override the default
      linker script.  The exact insertion point is as for orphan
      sections.  *Note Location Counter::.  The insertion happens after
      the linker has mapped input sections to output sections.  Prior to
-     the insertion, since `-T' scripts are parsed before the default
-     linker script, statements in the `-T' script occur before the
+     the insertion, since '-T' scripts are parsed before the default
+     linker script, statements in the '-T' script occur before the
      default linker script statements in the internal linker
      representation of the script.  In particular, input section
-     assignments will be made to `-T' output sections before those in
-     the default script.  Here is an example of how a `-T' script using
-     `INSERT' might look:
+     assignments will be made to '-T' output sections before those in
+     the default script.  Here is an example of how a '-T' script using
+     'INSERT' might look:
 
           SECTIONS
           {
@@ -2746,8 +2729,8 @@ There are a few other linker scripts commands.
           }
           INSERT AFTER .text;
 
-`NOCROSSREFS(SECTION SECTION ...)'
-     This command may be used to tell `ld' to issue an error about any
+'NOCROSSREFS(SECTION SECTION ...)'
+     This command may be used to tell 'ld' to issue an error about any
      references among certain output sections.
 
      In certain types of programs, particularly on embedded systems when
@@ -2756,21 +2739,21 @@ There are a few other linker scripts commands.
      sections would be errors.  For example, it would be an error if
      code in one section called a function defined in the other section.
 
-     The `NOCROSSREFS' command takes a list of output section names.  If
-     `ld' detects any cross references between the sections, it reports
+     The 'NOCROSSREFS' command takes a list of output section names.  If
+     'ld' detects any cross references between the sections, it reports
      an error and returns a non-zero exit status.  Note that the
-     `NOCROSSREFS' command uses output section names, not input section
+     'NOCROSSREFS' command uses output section names, not input section
      names.
 
-`OUTPUT_ARCH(BFDARCH)'
+'OUTPUT_ARCH(BFDARCH)'
      Specify a particular output machine architecture.  The argument is
      one of the names used by the BFD library (*note BFD::).  You can
-     see the architecture of an object file by using the `objdump'
-     program with the `-f' option.
+     see the architecture of an object file by using the 'objdump'
+     program with the '-f' option.
 
-`LD_FEATURE(STRING)'
-     This command may be used to modify `ld' behavior.  If STRING is
-     `"SANE_EXPR"' then absolute symbols and numbers in a script are
+'LD_FEATURE(STRING)'
+     This command may be used to modify 'ld' behavior.  If STRING is
+     '"SANE_EXPR"' then absolute symbols and numbers in a script are
      simply treated as numbers everywhere.  *Note Expression Section::.
 
 
@@ -2798,30 +2781,30 @@ File: ld.info,  Node: Simple Assignments,  Next: HIDDEN,  Up: Assignments
 
 You may assign to a symbol using any of the C assignment operators:
 
-`SYMBOL = EXPRESSION ;'
-`SYMBOL += EXPRESSION ;'
-`SYMBOL -= EXPRESSION ;'
-`SYMBOL *= EXPRESSION ;'
-`SYMBOL /= EXPRESSION ;'
-`SYMBOL <<= EXPRESSION ;'
-`SYMBOL >>= EXPRESSION ;'
-`SYMBOL &= EXPRESSION ;'
-`SYMBOL |= EXPRESSION ;'
-
-   The first case will define SYMBOL to the value of EXPRESSION.  In
-the other cases, SYMBOL must already be defined, and the value will be
+'SYMBOL = EXPRESSION ;'
+'SYMBOL += EXPRESSION ;'
+'SYMBOL -= EXPRESSION ;'
+'SYMBOL *= EXPRESSION ;'
+'SYMBOL /= EXPRESSION ;'
+'SYMBOL <<= EXPRESSION ;'
+'SYMBOL >>= EXPRESSION ;'
+'SYMBOL &= EXPRESSION ;'
+'SYMBOL |= EXPRESSION ;'
+
+   The first case will define SYMBOL to the value of EXPRESSION.  In the
+other cases, SYMBOL must already be defined, and the value will be
 adjusted accordingly.
 
-   The special symbol name `.' indicates the location counter.  You may
-only use this within a `SECTIONS' command.  *Note Location Counter::.
+   The special symbol name '.' indicates the location counter.  You may
+only use this within a 'SECTIONS' command.  *Note Location Counter::.
 
    The semicolon after EXPRESSION is required.
 
    Expressions are defined below; see *note Expressions::.
 
    You may write symbol assignments as commands in their own right, or
-as statements within a `SECTIONS' command, or as part of an output
-section description in a `SECTIONS' command.
+as statements within a 'SECTIONS' command, or as part of an output
+section description in a 'SECTIONS' command.
 
    The section of the symbol will be set from the section of the
 expression; for more information, see *note Expression Section::.
@@ -2840,10 +2823,10 @@ assignments may be used:
        _bdata = (. + 3) & ~ 3;
        .data : { *(.data) }
      }
-   In this example, the symbol `floating_point' will be defined as
-zero.  The symbol `_etext' will be defined as the address following the
-last `.text' input section.  The symbol `_bdata' will be defined as the
-address following the `.text' output section aligned upward to a 4 byte
+In this example, the symbol 'floating_point' will be defined as zero.
+The symbol '_etext' will be defined as the address following the last
+'.text' input section.  The symbol '_bdata' will be defined as the
+address following the '.text' output section aligned upward to a 4 byte
 boundary.
 
 
@@ -2853,10 +2836,10 @@ File: ld.info,  Node: HIDDEN,  Next: PROVIDE,  Prev: Simple Assignments,  Up: As
 ------------
 
 For ELF targeted ports, define a symbol that will be hidden and won't be
-exported.  The syntax is `HIDDEN(SYMBOL = EXPRESSION)'.
+exported.  The syntax is 'HIDDEN(SYMBOL = EXPRESSION)'.
 
    Here is the example from *note Simple Assignments::, rewritten to use
-`HIDDEN':
+'HIDDEN':
 
      HIDDEN(floating_point = 0);
      SECTIONS
@@ -2869,7 +2852,7 @@ exported.  The syntax is `HIDDEN(SYMBOL = EXPRESSION)'.
        HIDDEN(_bdata = (. + 3) & ~ 3);
        .data : { *(.data) }
      }
-   In this case none of the three symbols will be visible outside this
+In this case none of the three symbols will be visible outside this
 module.
 
 
@@ -2880,13 +2863,13 @@ File: ld.info,  Node: PROVIDE,  Next: PROVIDE_HIDDEN,  Prev: HIDDEN,  Up: Assign
 
 In some cases, it is desirable for a linker script to define a symbol
 only if it is referenced and is not defined by any object included in
-the link.  For example, traditional linkers defined the symbol `etext'.
-However, ANSI C requires that the user be able to use `etext' as a
-function name without encountering an error.  The `PROVIDE' keyword may
-be used to define a symbol, such as `etext', only if it is referenced
-but not defined.  The syntax is `PROVIDE(SYMBOL = EXPRESSION)'.
+the link.  For example, traditional linkers defined the symbol 'etext'.
+However, ANSI C requires that the user be able to use 'etext' as a
+function name without encountering an error.  The 'PROVIDE' keyword may
+be used to define a symbol, such as 'etext', only if it is referenced
+but not defined.  The syntax is 'PROVIDE(SYMBOL = EXPRESSION)'.
 
-   Here is an example of using `PROVIDE' to define `etext':
+   Here is an example of using 'PROVIDE' to define 'etext':
      SECTIONS
      {
        .text :
@@ -2897,11 +2880,11 @@ but not defined.  The syntax is `PROVIDE(SYMBOL = EXPRESSION)'.
          }
      }
 
-   In this example, if the program defines `_etext' (with a leading
+   In this example, if the program defines '_etext' (with a leading
 underscore), the linker will give a multiple definition error.  If, on
-the other hand, the program defines `etext' (with no leading
+the other hand, the program defines 'etext' (with no leading
 underscore), the linker will silently use the definition in the program.
-If the program references `etext' but does not define it, the linker
+If the program references 'etext' but does not define it, the linker
 will use the definition in the linker script.
 
 
@@ -2910,8 +2893,8 @@ File: ld.info,  Node: PROVIDE_HIDDEN,  Next: Source Code Reference,  Prev: PROVI
 3.5.4 PROVIDE_HIDDEN
 --------------------
 
-Similar to `PROVIDE'.  For ELF targeted ports, the symbol will be
-hidden and won't be exported.
+Similar to 'PROVIDE'.  For ELF targeted ports, the symbol will be hidden
+and won't be exported.
 
 
 File: ld.info,  Node: Source Code Reference,  Prev: PROVIDE_HIDDEN,  Up: Assignments
@@ -2927,11 +2910,11 @@ that does not have a value.
    Before going further, it is important to note that compilers often
 transform names in the source code into different names when they are
 stored in the symbol table.  For example, Fortran compilers commonly
-prepend or append an underscore, and C++ performs extensive `name
-mangling'.  Therefore there might be a discrepancy between the name of
-a variable as it is used in source code and the name of the same
-variable as it is defined in a linker script.  For example in C a
-linker script variable might be referred to as:
+prepend or append an underscore, and C++ performs extensive 'name
+mangling'.  Therefore there might be a discrepancy between the name of a
+variable as it is used in source code and the name of the same variable
+as it is defined in a linker script.  For example in C a linker script
+variable might be referred to as:
 
        extern int foo;
 
@@ -2952,8 +2935,8 @@ following C declaration, at file scope:
 
        int foo = 1000;
 
-   creates a entry called `foo' in the symbol table.  This entry holds
-the address of an `int' sized block of memory where the number 1000 is
+   creates an entry called 'foo' in the symbol table.  This entry holds
+the address of an 'int' sized block of memory where the number 1000 is
 initially stored.
 
    When a program references a symbol the compiler generates code that
@@ -2963,34 +2946,33 @@ So:
 
        foo = 1;
 
-   looks up the symbol `foo' in the symbol table, gets the address
+   looks up the symbol 'foo' in the symbol table, gets the address
 associated with this symbol and then writes the value 1 into that
 address.  Whereas:
 
        int * a = & foo;
 
-   looks up the symbol `foo' in the symbol table, gets it address and
+   looks up the symbol 'foo' in the symbol table, gets its address and
 then copies this address into the block of memory associated with the
-variable `a'.
+variable 'a'.
 
    Linker scripts symbol declarations, by contrast, create an entry in
-the symbol table but do not assign any memory to them.  Thus they are
-an address without a value.  So for example the linker script
-definition:
+the symbol table but do not assign any memory to them.  Thus they are an
+address without a value.  So for example the linker script definition:
 
        foo = 1000;
 
-   creates an entry in the symbol table called `foo' which holds the
+   creates an entry in the symbol table called 'foo' which holds the
 address of memory location 1000, but nothing special is stored at
-address 1000.  This means that you cannot access the _value_ of a
-linker script defined symbol - it has no value - all you can do is
-access the _address_ of a linker script defined symbol.
+address 1000.  This means that you cannot access the _value_ of a linker
+script defined symbol - it has no value - all you can do is access the
+_address_ of a linker script defined symbol.
 
    Hence when you are using a linker script defined symbol in source
-code you should always take the address of the symbol, and never
-attempt to use its value.  For example suppose you want to copy the
-contents of a section of memory called .ROM into a section called
-.FLASH and the linker script contains these declarations:
+code you should always take the address of the symbol, and never attempt
+to use its value.  For example suppose you want to copy the contents of
+a section of memory called .ROM into a section called .FLASH and the
+linker script contains these declarations:
 
        start_of_ROM   = .ROM;
        end_of_ROM     = .ROM + sizeof (.ROM) - 1;
@@ -3002,7 +2984,7 @@ contents of a section of memory called .ROM into a section called
 
        memcpy (& start_of_FLASH, & start_of_ROM, & end_of_ROM - & start_of_ROM);
 
-   Note the use of the `&' operators.  These are correct.
+   Note the use of the '&' operators.  These are correct.
 
 
 File: ld.info,  Node: SECTIONS,  Next: MEMORY,  Prev: Assignments,  Up: Scripts
@@ -3010,10 +2992,10 @@ File: ld.info,  Node: SECTIONS,  Next: MEMORY,  Prev: Assignments,  Up: Scripts
 3.6 SECTIONS Command
 ====================
 
-The `SECTIONS' command tells the linker how to map input sections into
+The 'SECTIONS' command tells the linker how to map input sections into
 output sections, and how to place the output sections in memory.
 
-   The format of the `SECTIONS' command is:
+   The format of the 'SECTIONS' command is:
      SECTIONS
      {
        SECTIONS-COMMAND
@@ -3023,16 +3005,13 @@ output sections, and how to place the output sections in memory.
 
    Each SECTIONS-COMMAND may of be one of the following:
 
-   * an `ENTRY' command (*note Entry command: Entry Point.)
-
+   * an 'ENTRY' command (*note Entry command: Entry Point.)
    * a symbol assignment (*note Assignments::)
-
    * an output section description
-
    * an overlay description
 
-   The `ENTRY' command and symbol assignments are permitted inside the
-`SECTIONS' command for convenience in using the location counter in
+   The 'ENTRY' command and symbol assignments are permitted inside the
+'SECTIONS' command for convenience in using the location counter in
 those commands.  This can also make the linker script easier to
 understand because you can use those commands at meaningful points in
 the layout of the output file.
@@ -3040,7 +3019,7 @@ the layout of the output file.
    Output section descriptions and overlay descriptions are described
 below.
 
-   If you do not use a `SECTIONS' command in your linker script, the
+   If you do not use a 'SECTIONS' command in your linker script, the
 linker will place each input section into an identically named output
 section in the order that the sections are first encountered in the
 input files.  If all input sections are present in the first file, for
@@ -3068,7 +3047,7 @@ File: ld.info,  Node: Output Section Description,  Next: Output Section Name,  U
 The full description of an output section looks like this:
      SECTION [ADDRESS] [(TYPE)] :
        [AT(LMA)]
-       [ALIGN(SECTION_ALIGN)]
+       [ALIGN(SECTION_ALIGN) | ALIGN_WITH_INPUT]
        [SUBALIGN(SUBSECTION_ALIGN)]
        [CONSTRAINT]
        {
@@ -3087,11 +3066,8 @@ line breaks and other white space are optional.
    Each OUTPUT-SECTION-COMMAND may be one of the following:
 
    * a symbol assignment (*note Assignments::)
-
    * an input section description (*note Input Section::)
-
    * data values to include directly (*note Output Section Data::)
-
    * a special output section keyword (*note Output Section Keywords::)
 
 
@@ -3102,15 +3078,15 @@ File: ld.info,  Node: Output Section Name,  Next: Output Section Address,  Prev:
 
 The name of the output section is SECTION.  SECTION must meet the
 constraints of your output format.  In formats which only support a
-limited number of sections, such as `a.out', the name must be one of
-the names supported by the format (`a.out', for example, allows only
-`.text', `.data' or `.bss'). If the output format supports any number
+limited number of sections, such as 'a.out', the name must be one of the
+names supported by the format ('a.out', for example, allows only
+'.text', '.data' or '.bss').  If the output format supports any number
 of sections, but with numbers and not names (as is the case for Oasys),
 the name should be supplied as a quoted numeric string.  A section name
-may consist of any sequence of characters, but a name which contains
-any unusual characters such as commas must be quoted.
+may consist of any sequence of characters, but a name which contains any
+unusual characters such as commas must be quoted.
 
-   The output section name `/DISCARD/' is special; *note Output Section
+   The output section name '/DISCARD/' is special; *note Output Section
 Discarding::.
 
 
@@ -3119,8 +3095,8 @@ File: ld.info,  Node: Output Section Address,  Next: Input Section,  Prev: Outpu
 3.6.3 Output Section Address
 ----------------------------
 
-The ADDRESS is an expression for the VMA (the virtual memory address)
-of the output section.  This address is optional, but if it is provided
+The ADDRESS is an expression for the VMA (the virtual memory address) of
+the output section.  This address is optional, but if it is provided
 then the output address will be set exactly as specified.
 
    If the output address is not specified then one will be chosen for
@@ -3153,18 +3129,18 @@ and
 
      .text : { *(.text) }
 
-are subtly different.  The first will set the address of the `.text'
-output section to the current value of the location counter.  The
-second will set it to the current value of the location counter aligned
-to the strictest alignment of any of the `.text' input sections.
+are subtly different.  The first will set the address of the '.text'
+output section to the current value of the location counter.  The second
+will set it to the current value of the location counter aligned to the
+strictest alignment of any of the '.text' input sections.
 
-   The ADDRESS may be an arbitrary expression; *note Expressions::.
-For example, if you want to align the section on a 0x10 byte boundary,
-so that the lowest four bits of the section address are zero, you could
-do something like this:
+   The ADDRESS may be an arbitrary expression; *note Expressions::.  For
+example, if you want to align the section on a 0x10 byte boundary, so
+that the lowest four bits of the section address are zero, you could do
+something like this:
      .text ALIGN(0x10) : { *(.text) }
-   This works because `ALIGN' returns the current location counter
-aligned upward to the specified value.
+This works because 'ALIGN' returns the current location counter aligned
+upward to the specified value.
 
    Specifying ADDRESS for a section will change the value of the
 location counter, provided that the section is non-empty.  (Empty
@@ -3205,25 +3181,24 @@ describe further below (*note Input Section Wildcards::).
 
    The most common input section description is to include all input
 sections with a particular name in the output section.  For example, to
-include all input `.text' sections, you would write:
+include all input '.text' sections, you would write:
      *(.text)
-   Here the `*' is a wildcard which matches any file name.  To exclude
-a list of files from matching the file name wildcard, EXCLUDE_FILE may
-be used to match all files except the ones specified in the
-EXCLUDE_FILE list.  For example:
+Here the '*' is a wildcard which matches any file name.  To exclude a
+list of files from matching the file name wildcard, EXCLUDE_FILE may be
+used to match all files except the ones specified in the EXCLUDE_FILE
+list.  For example:
      *(EXCLUDE_FILE (*crtend.o *otherfile.o) .ctors)
-   will cause all .ctors sections from all files except `crtend.o' and
-`otherfile.o' to be included.
+   will cause all .ctors sections from all files except 'crtend.o' and
+'otherfile.o' to be included.
 
    There are two ways to include more than one section:
      *(.text .rdata)
      *(.text) *(.rdata)
-   The difference between these is the order in which the `.text' and
-`.rdata' input sections will appear in the output section.  In the
-first example, they will be intermingled, appearing in the same order as
-they are found in the linker input.  In the second example, all `.text'
-input sections will appear first, followed by all `.rdata' input
-sections.
+The difference between these is the order in which the '.text' and
+'.rdata' input sections will appear in the output section.  In the first
+example, they will be intermingled, appearing in the same order as they
+are found in the linker input.  In the second example, all '.text' input
+sections will appear first, followed by all '.rdata' input sections.
 
    You can specify a file name to include sections from a particular
 file.  You would do this if one or more of your files contain special
@@ -3241,46 +3216,44 @@ sections:
        .text2 :  { INPUT_SECTION_FLAGS (!SHF_WRITE) *(.text) }
      }
 
-   In this example, the output section `.text' will be comprised of any
+   In this example, the output section '.text' will be comprised of any
 input section matching the name *(.text) whose section header flags
-`SHF_MERGE' and `SHF_STRINGS' are set.  The output section `.text2'
-will be comprised of any input section matching the name *(.text) whose
-section header flag `SHF_WRITE' is clear.
+'SHF_MERGE' and 'SHF_STRINGS' are set.  The output section '.text2' will
+be comprised of any input section matching the name *(.text) whose
+section header flag 'SHF_WRITE' is clear.
 
    You can also specify files within archives by writing a pattern
 matching the archive, a colon, then the pattern matching the file, with
 no whitespace around the colon.
 
-`archive:file'
+'archive:file'
      matches file within archive
-
-`archive:'
+'archive:'
      matches the whole archive
-
-`:file'
+':file'
      matches file but not one in an archive
 
-   Either one or both of `archive' and `file' can contain shell
+   Either one or both of 'archive' and 'file' can contain shell
 wildcards.  On DOS based file systems, the linker will assume that a
-single letter followed by a colon is a drive specifier, so `c:myfile.o'
-is a simple file specification, not `myfile.o' within an archive called
-`c'.  `archive:file' filespecs may also be used within an
-`EXCLUDE_FILE' list, but may not appear in other linker script
-contexts.  For instance, you cannot extract a file from an archive by
-using `archive:file' in an `INPUT' command.
+single letter followed by a colon is a drive specifier, so 'c:myfile.o'
+is a simple file specification, not 'myfile.o' within an archive called
+'c'.  'archive:file' filespecs may also be used within an 'EXCLUDE_FILE'
+list, but may not appear in other linker script contexts.  For instance,
+you cannot extract a file from an archive by using 'archive:file' in an
+'INPUT' command.
 
    If you use a file name without a list of sections, then all sections
 in the input file will be included in the output section.  This is not
 commonly done, but it may by useful on occasion.  For example:
      data.o
 
-   When you use a file name which is not an `archive:file' specifier
-and does not contain any wild card characters, the linker will first
-see if you also specified the file name on the linker command line or
-in an `INPUT' command.  If you did not, the linker will attempt to open
-the file as an input file, as though it appeared on the command line.
-Note that this differs from an `INPUT' command, because the linker will
-not search for the file in the archive search path.
+   When you use a file name which is not an 'archive:file' specifier and
+does not contain any wild card characters, the linker will first see if
+you also specified the file name on the linker command line or in an
+'INPUT' command.  If you did not, the linker will attempt to open the
+file as an input file, as though it appeared on the command line.  Note
+that this differs from an 'INPUT' command, because the linker will not
+search for the file in the archive search path.
 
 
 File: ld.info,  Node: Input Section Wildcards,  Next: Input Section Common,  Prev: Input Section Basics,  Up: Input Section
@@ -3291,80 +3264,75 @@ File: ld.info,  Node: Input Section Wildcards,  Next: Input Section Common,  Pre
 In an input section description, either the file name or the section
 name or both may be wildcard patterns.
 
-   The file name of `*' seen in many examples is a simple wildcard
+   The file name of '*' seen in many examples is a simple wildcard
 pattern for the file name.
 
    The wildcard patterns are like those used by the Unix shell.
 
-`*'
+'*'
      matches any number of characters
-
-`?'
+'?'
      matches any single character
-
-`[CHARS]'
-     matches a single instance of any of the CHARS; the `-' character
-     may be used to specify a range of characters, as in `[a-z]' to
+'[CHARS]'
+     matches a single instance of any of the CHARS; the '-' character
+     may be used to specify a range of characters, as in '[a-z]' to
      match any lower case letter
-
-`\'
+'\'
      quotes the following character
 
    When a file name is matched with a wildcard, the wildcard characters
-will not match a `/' character (used to separate directory names on
-Unix).  A pattern consisting of a single `*' character is an exception;
-it will always match any file name, whether it contains a `/' or not.
-In a section name, the wildcard characters will match a `/' character.
+will not match a '/' character (used to separate directory names on
+Unix).  A pattern consisting of a single '*' character is an exception;
+it will always match any file name, whether it contains a '/' or not.
+In a section name, the wildcard characters will match a '/' character.
 
    File name wildcard patterns only match files which are explicitly
-specified on the command line or in an `INPUT' command.  The linker
-does not search directories to expand wildcards.
+specified on the command line or in an 'INPUT' command.  The linker does
+not search directories to expand wildcards.
 
    If a file name matches more than one wildcard pattern, or if a file
 name appears explicitly and is also matched by a wildcard pattern, the
 linker will use the first match in the linker script.  For example, this
 sequence of input section descriptions is probably in error, because the
-`data.o' rule will not be used:
+'data.o' rule will not be used:
      .data : { *(.data) }
      .data1 : { data.o(.data) }
 
    Normally, the linker will place files and sections matched by
 wildcards in the order in which they are seen during the link.  You can
-change this by using the `SORT_BY_NAME' keyword, which appears before a
-wildcard pattern in parentheses (e.g., `SORT_BY_NAME(.text*)').  When
-the `SORT_BY_NAME' keyword is used, the linker will sort the files or
+change this by using the 'SORT_BY_NAME' keyword, which appears before a
+wildcard pattern in parentheses (e.g., 'SORT_BY_NAME(.text*)').  When
+the 'SORT_BY_NAME' keyword is used, the linker will sort the files or
 sections into ascending order by name before placing them in the output
 file.
 
-   `SORT_BY_ALIGNMENT' is very similar to `SORT_BY_NAME'. The
-difference is `SORT_BY_ALIGNMENT' will sort sections into ascending
-order by alignment before placing them in the output file.
+   'SORT_BY_ALIGNMENT' is very similar to 'SORT_BY_NAME'.  The
+difference is 'SORT_BY_ALIGNMENT' will sort sections into descending
+order by alignment before placing them in the output file.  Larger
+alignments are placed before smaller alignments in order to reduce the
+amount of padding necessary.
 
-   `SORT_BY_INIT_PRIORITY' is very similar to `SORT_BY_NAME'. The
-difference is `SORT_BY_INIT_PRIORITY' will sort sections into ascending
+   'SORT_BY_INIT_PRIORITY' is very similar to 'SORT_BY_NAME'.  The
+difference is 'SORT_BY_INIT_PRIORITY' will sort sections into ascending
 order by numerical value of the GCC init_priority attribute encoded in
 the section name before placing them in the output file.
 
-   `SORT' is an alias for `SORT_BY_NAME'.
+   'SORT' is an alias for 'SORT_BY_NAME'.
 
    When there are nested section sorting commands in linker script,
 there can be at most 1 level of nesting for section sorting commands.
 
-  1. `SORT_BY_NAME' (`SORT_BY_ALIGNMENT' (wildcard section pattern)).
-     It will sort the input sections by name first, then by alignment
-     if 2 sections have the same name.
-
-  2. `SORT_BY_ALIGNMENT' (`SORT_BY_NAME' (wildcard section pattern)).
-     It will sort the input sections by alignment first, then by name
-     if 2 sections have the same alignment.
-
-  3. `SORT_BY_NAME' (`SORT_BY_NAME' (wildcard section pattern)) is
-     treated the same as `SORT_BY_NAME' (wildcard section pattern).
-
-  4. `SORT_BY_ALIGNMENT' (`SORT_BY_ALIGNMENT' (wildcard section
-     pattern)) is treated the same as `SORT_BY_ALIGNMENT' (wildcard
+  1. 'SORT_BY_NAME' ('SORT_BY_ALIGNMENT' (wildcard section pattern)).
+     It will sort the input sections by name first, then by alignment if
+     two sections have the same name.
+  2. 'SORT_BY_ALIGNMENT' ('SORT_BY_NAME' (wildcard section pattern)).
+     It will sort the input sections by alignment first, then by name if
+     two sections have the same alignment.
+  3. 'SORT_BY_NAME' ('SORT_BY_NAME' (wildcard section pattern)) is
+     treated the same as 'SORT_BY_NAME' (wildcard section pattern).
+  4. 'SORT_BY_ALIGNMENT' ('SORT_BY_ALIGNMENT' (wildcard section
+     pattern)) is treated the same as 'SORT_BY_ALIGNMENT' (wildcard
      section pattern).
-
   5. All other nested section sorting commands are invalid.
 
    When both command line section sorting option and linker script
@@ -3375,30 +3343,29 @@ precedence over the command line option.
 command line option will make the section sorting command to be treated
 as nested sorting command.
 
-  1. `SORT_BY_NAME' (wildcard section pattern ) with `--sort-sections
-     alignment' is equivalent to `SORT_BY_NAME' (`SORT_BY_ALIGNMENT'
+  1. 'SORT_BY_NAME' (wildcard section pattern ) with '--sort-sections
+     alignment' is equivalent to 'SORT_BY_NAME' ('SORT_BY_ALIGNMENT'
+     (wildcard section pattern)).
+  2. 'SORT_BY_ALIGNMENT' (wildcard section pattern) with '--sort-section
+     name' is equivalent to 'SORT_BY_ALIGNMENT' ('SORT_BY_NAME'
      (wildcard section pattern)).
-
-  2. `SORT_BY_ALIGNMENT' (wildcard section pattern) with
-     `--sort-section name' is equivalent to `SORT_BY_ALIGNMENT'
-     (`SORT_BY_NAME' (wildcard section pattern)).
 
    If the section sorting command in linker script is nested, the
 command line option will be ignored.
 
-   `SORT_NONE' disables section sorting by ignoring the command line
+   'SORT_NONE' disables section sorting by ignoring the command line
 section sorting option.
 
    If you ever get confused about where input sections are going, use
-the `-M' linker option to generate a map file.  The map file shows
+the '-M' linker option to generate a map file.  The map file shows
 precisely how input sections are mapped to output sections.
 
    This example shows how wildcard patterns might be used to partition
-files.  This linker script directs the linker to place all `.text'
-sections in `.text' and all `.bss' sections in `.bss'.  The linker will
-place the `.data' section from all files beginning with an upper case
-character in `.DATA'; for all other files, the linker will place the
-`.data' section in `.data'.
+files.  This linker script directs the linker to place all '.text'
+sections in '.text' and all '.bss' sections in '.bss'.  The linker will
+place the '.data' section from all files beginning with an upper case
+character in '.DATA'; for all other files, the linker will place the
+'.data' section in '.data'.
      SECTIONS {
        .text : { *(.text) }
        .DATA : { [A-Z]*(.data) }
@@ -3415,28 +3382,28 @@ File: ld.info,  Node: Input Section Common,  Next: Input Section Keep,  Prev: In
 A special notation is needed for common symbols, because in many object
 file formats common symbols do not have a particular input section.  The
 linker treats common symbols as though they are in an input section
-named `COMMON'.
+named 'COMMON'.
 
-   You may use file names with the `COMMON' section just as with any
+   You may use file names with the 'COMMON' section just as with any
 other input sections.  You can use this to place common symbols from a
 particular input file in one section while common symbols from other
 input files are placed in another section.
 
    In most cases, common symbols in input files will be placed in the
-`.bss' section in the output file.  For example:
+'.bss' section in the output file.  For example:
      .bss { *(.bss) *(COMMON) }
 
    Some object file formats have more than one type of common symbol.
 For example, the MIPS ELF object file format distinguishes standard
 common symbols and small common symbols.  In this case, the linker will
 use a different special section name for other types of common symbols.
-In the case of MIPS ELF, the linker uses `COMMON' for standard common
-symbols and `.scommon' for small common symbols.  This permits you to
+In the case of MIPS ELF, the linker uses 'COMMON' for standard common
+symbols and '.scommon' for small common symbols.  This permits you to
 map the different types of common symbols into memory at different
 locations.
 
-   You will sometimes see `[COMMON]' in old linker scripts.  This
-notation is now considered obsolete.  It is equivalent to `*(COMMON)'.
+   You will sometimes see '[COMMON]' in old linker scripts.  This
+notation is now considered obsolete.  It is equivalent to '*(COMMON)'.
 
 
 File: ld.info,  Node: Input Section Keep,  Next: Input Section Example,  Prev: Input Section Common,  Up: Input Section
@@ -3444,10 +3411,10 @@ File: ld.info,  Node: Input Section Keep,  Next: Input Section Example,  Prev: I
 3.6.4.4 Input Section and Garbage Collection
 ............................................
 
-When link-time garbage collection is in use (`--gc-sections'), it is
+When link-time garbage collection is in use ('--gc-sections'), it is
 often useful to mark sections that should not be eliminated.  This is
 accomplished by surrounding an input section's wildcard entry with
-`KEEP()', as in `KEEP(*(.init))' or `KEEP(SORT_BY_NAME(*)(.ctors))'.
+'KEEP()', as in 'KEEP(*(.init))' or 'KEEP(SORT_BY_NAME(*)(.ctors))'.
 
 
 File: ld.info,  Node: Input Section Example,  Prev: Input Section Keep,  Up: Input Section
@@ -3456,13 +3423,13 @@ File: ld.info,  Node: Input Section Example,  Prev: Input Section Keep,  Up: Inp
 .............................
 
 The following example is a complete linker script.  It tells the linker
-to read all of the sections from file `all.o' and place them at the
-start of output section `outputa' which starts at location `0x10000'.
-All of section `.input1' from file `foo.o' follows immediately, in the
-same output section.  All of section `.input2' from `foo.o' goes into
-output section `outputb', followed by section `.input1' from `foo1.o'.
-All of the remaining `.input1' and `.input2' sections from any files
-are written to output section `outputc'.
+to read all of the sections from file 'all.o' and place them at the
+start of output section 'outputa' which starts at location '0x10000'.
+All of section '.input1' from file 'foo.o' follows immediately, in the
+same output section.  All of section '.input2' from 'foo.o' goes into
+output section 'outputb', followed by section '.input1' from 'foo1.o'.
+All of the remaining '.input1' and '.input2' sections from any files are
+written to output section 'outputc'.
 
      SECTIONS {
        outputa 0x10000 :
@@ -3489,24 +3456,24 @@ File: ld.info,  Node: Output Section Data,  Next: Output Section Keywords,  Prev
 -------------------------
 
 You can include explicit bytes of data in an output section by using
-`BYTE', `SHORT', `LONG', `QUAD', or `SQUAD' as an output section
+'BYTE', 'SHORT', 'LONG', 'QUAD', or 'SQUAD' as an output section
 command.  Each keyword is followed by an expression in parentheses
 providing the value to store (*note Expressions::).  The value of the
 expression is stored at the current value of the location counter.
 
-   The `BYTE', `SHORT', `LONG', and `QUAD' commands store one, two,
+   The 'BYTE', 'SHORT', 'LONG', and 'QUAD' commands store one, two,
 four, and eight bytes (respectively).  After storing the bytes, the
 location counter is incremented by the number of bytes stored.
 
    For example, this will store the byte 1 followed by the four byte
-value of the symbol `addr':
+value of the symbol 'addr':
      BYTE(1)
      LONG(addr)
 
-   When using a 64 bit host or target, `QUAD' and `SQUAD' are the same;
+   When using a 64 bit host or target, 'QUAD' and 'SQUAD' are the same;
 they both store an 8 byte, or 64 bit, value.  When both host and target
-are 32 bits, an expression is computed as 32 bits.  In this case `QUAD'
-stores a 32 bit value zero extended to 64 bits, and `SQUAD' stores a 32
+are 32 bits, an expression is computed as 32 bits.  In this case 'QUAD'
+stores a 32 bit value zero extended to 64 bits, and 'SQUAD' stores a 32
 bit value sign extended to 64 bits.
 
    If the object file format of the output file has an explicit
@@ -3517,28 +3484,28 @@ stored in the endianness of the first input object file.
 
    Note--these commands only work inside a section description and not
 between them, so the following will produce an error from the linker:
-     SECTIONS { .text : { *(.text) } LONG(1) .data : { *(.data) } }
+     SECTIONS { .text : { *(.text) } LONG(1) .data : { *(.data) } } 
    whereas this will work:
-     SECTIONS { .text : { *(.text) ; LONG(1) } .data : { *(.data) } }
+     SECTIONS { .text : { *(.text) ; LONG(1) } .data : { *(.data) } } 
 
-   You may use the `FILL' command to set the fill pattern for the
+   You may use the 'FILL' command to set the fill pattern for the
 current section.  It is followed by an expression in parentheses.  Any
 otherwise unspecified regions of memory within the section (for example,
 gaps left due to the required alignment of input sections) are filled
-with the value of the expression, repeated as necessary.  A `FILL'
+with the value of the expression, repeated as necessary.  A 'FILL'
 statement covers memory locations after the point at which it occurs in
-the section definition; by including more than one `FILL' statement,
-you can have different fill patterns in different parts of an output
+the section definition; by including more than one 'FILL' statement, you
+can have different fill patterns in different parts of an output
 section.
 
    This example shows how to fill unspecified regions of memory with the
-value `0x90':
+value '0x90':
      FILL(0x90909090)
 
-   The `FILL' command is similar to the `=FILLEXP' output section
+   The 'FILL' command is similar to the '=FILLEXP' output section
 attribute, but it only affects the part of the section following the
-`FILL' command, rather than the entire section.  If both are used, the
-`FILL' command takes precedence.  *Note Output Section Fill::, for
+'FILL' command, rather than the entire section.  If both are used, the
+'FILL' command takes precedence.  *Note Output Section Fill::, for
 details on the fill expression.
 
 
@@ -3550,43 +3517,43 @@ File: ld.info,  Node: Output Section Keywords,  Next: Output Section Discarding,
 There are a couple of keywords which can appear as output section
 commands.
 
-`CREATE_OBJECT_SYMBOLS'
+'CREATE_OBJECT_SYMBOLS'
      The command tells the linker to create a symbol for each input
      file.  The name of each symbol will be the name of the
      corresponding input file.  The section of each symbol will be the
-     output section in which the `CREATE_OBJECT_SYMBOLS' command
+     output section in which the 'CREATE_OBJECT_SYMBOLS' command
      appears.
 
      This is conventional for the a.out object file format.  It is not
      normally used for any other object file format.
 
-`CONSTRUCTORS'
+'CONSTRUCTORS'
      When linking using the a.out object file format, the linker uses an
      unusual set construct to support C++ global constructors and
      destructors.  When linking object file formats which do not support
      arbitrary sections, such as ECOFF and XCOFF, the linker will
      automatically recognize C++ global constructors and destructors by
-     name.  For these object file formats, the `CONSTRUCTORS' command
+     name.  For these object file formats, the 'CONSTRUCTORS' command
      tells the linker to place constructor information in the output
-     section where the `CONSTRUCTORS' command appears.  The
-     `CONSTRUCTORS' command is ignored for other object file formats.
+     section where the 'CONSTRUCTORS' command appears.  The
+     'CONSTRUCTORS' command is ignored for other object file formats.
 
-     The symbol `__CTOR_LIST__' marks the start of the global
-     constructors, and the symbol `__CTOR_END__' marks the end.
-     Similarly, `__DTOR_LIST__' and `__DTOR_END__' mark the start and
+     The symbol '__CTOR_LIST__' marks the start of the global
+     constructors, and the symbol '__CTOR_END__' marks the end.
+     Similarly, '__DTOR_LIST__' and '__DTOR_END__' mark the start and
      end of the global destructors.  The first word in the list is the
      number of entries, followed by the address of each constructor or
      destructor, followed by a zero word.  The compiler must arrange to
      actually run the code.  For these object file formats GNU C++
-     normally calls constructors from a subroutine `__main'; a call to
-     `__main' is automatically inserted into the startup code for
-     `main'.  GNU C++ normally runs destructors either by using
-     `atexit', or directly from the function `exit'.
+     normally calls constructors from a subroutine '__main'; a call to
+     '__main' is automatically inserted into the startup code for
+     'main'.  GNU C++ normally runs destructors either by using
+     'atexit', or directly from the function 'exit'.
 
-     For object file formats such as `COFF' or `ELF' which support
+     For object file formats such as 'COFF' or 'ELF' which support
      arbitrary section names, GNU C++ will normally arrange to put the
-     addresses of global constructors and destructors into the `.ctors'
-     and `.dtors' sections.  Placing the following sequence into your
+     addresses of global constructors and destructors into the '.ctors'
+     and '.dtors' sections.  Placing the following sequence into your
      linker script will build the sort of table which the GNU C++
      runtime code expects to see.
 
@@ -3605,16 +3572,15 @@ commands.
      which provides some control over the order in which global
      constructors are run, you must sort the constructors at link time
      to ensure that they are executed in the correct order.  When using
-     the `CONSTRUCTORS' command, use `SORT_BY_NAME(CONSTRUCTORS)'
-     instead.  When using the `.ctors' and `.dtors' sections, use
-     `*(SORT_BY_NAME(.ctors))' and `*(SORT_BY_NAME(.dtors))' instead of
-     just `*(.ctors)' and `*(.dtors)'.
+     the 'CONSTRUCTORS' command, use 'SORT_BY_NAME(CONSTRUCTORS)'
+     instead.  When using the '.ctors' and '.dtors' sections, use
+     '*(SORT_BY_NAME(.ctors))' and '*(SORT_BY_NAME(.dtors))' instead of
+     just '*(.ctors)' and '*(.dtors)'.
 
      Normally the compiler and linker will handle these issues
-     automatically, and you will not need to concern yourself with
-     them.  However, you may need to consider this if you are using C++
-     and writing your own linker scripts.
-
+     automatically, and you will not need to concern yourself with them.
+     However, you may need to consider this if you are using C++ and
+     writing your own linker scripts.
 
 
 File: ld.info,  Node: Output Section Discarding,  Next: Output Section Attributes,  Prev: Output Section Keywords,  Up: SECTIONS
@@ -3626,10 +3592,10 @@ The linker will not create output sections with no contents.  This is
 for convenience when referring to input sections that may or may not be
 present in any of the input files.  For example:
      .foo : { *(.foo) }
-   will only create a `.foo' section in the output file if there is a
-`.foo' section in at least one input file, and if the input sections
-are not all empty.  Other link script directives that allocate space in
-an output section will also create the output section.
+will only create a '.foo' section in the output file if there is a
+'.foo' section in at least one input file, and if the input sections are
+not all empty.  Other link script directives that allocate space in an
+output section will also create the output section.
 
    The linker will ignore address assignments (*note Output Section
 Address::) on discarded output sections, except when the linker script
@@ -3637,9 +3603,9 @@ defines symbols in the output section.  In that case the linker will
 obey the address assignments, possibly advancing dot even though the
 section is discarded.
 
-   The special output section name `/DISCARD/' may be used to discard
+   The special output section name '/DISCARD/' may be used to discard
 input sections.  Any input sections which are assigned to an output
-section named `/DISCARD/' are not included in the output file.
+section named '/DISCARD/' are not included in the output file.
 
 
 File: ld.info,  Node: Output Section Attributes,  Next: Overlay Description,  Prev: Output Section Discarding,  Up: SECTIONS
@@ -3661,9 +3627,8 @@ like this:
          ...
        } [>REGION] [AT>LMA_REGION] [:PHDR :PHDR ...] [=FILLEXP]
 
-   We've already described SECTION, ADDRESS, and
-OUTPUT-SECTION-COMMAND.  In this section we will describe the remaining
-section attributes.
+   We've already described SECTION, ADDRESS, and OUTPUT-SECTION-COMMAND.
+In this section we will describe the remaining section attributes.
 
 * Menu:
 
@@ -3685,14 +3650,13 @@ File: ld.info,  Node: Output Section Type,  Next: Output Section LMA,  Up: Outpu
 Each output section may have a type.  The type is a keyword in
 parentheses.  The following types are defined:
 
-`NOLOAD'
+'NOLOAD'
      The section should be marked as not loadable, so that it will not
      be loaded into memory when the program is run.
-
-`DSECT'
-`COPY'
-`INFO'
-`OVERLAY'
+'DSECT'
+'COPY'
+'INFO'
+'OVERLAY'
      These type names are supported for backward compatibility, and are
      rarely used.  They all have the same effect: the section should be
      marked as not allocatable, so that no memory is allocated for the
@@ -3700,8 +3664,8 @@ parentheses.  The following types are defined:
 
    The linker normally sets the attributes of an output section based on
 the input sections which map into it.  You can override this by using
-the section type.  For example, in the script sample below, the `ROM'
-section is addressed at memory location `0' and does not need to be
+the section type.  For example, in the script sample below, the 'ROM'
+section is addressed at memory location '0' and does not need to be
 loaded when the program is run.
      SECTIONS {
        ROM 0 (NOLOAD) : { ... }
@@ -3717,29 +3681,29 @@ File: ld.info,  Node: Output Section LMA,  Next: Forced Output Alignment,  Prev:
 Every section has a virtual address (VMA) and a load address (LMA); see
 *note Basic Script Concepts::.  The virtual address is specified by the
 *note Output Section Address:: described earlier.  The load address is
-specified by the `AT' or `AT>' keywords.  Specifying a load address is
+specified by the 'AT' or 'AT>' keywords.  Specifying a load address is
 optional.
 
-   The `AT' keyword takes an expression as an argument.  This specifies
-the exact load address of the section.  The `AT>' keyword takes the
-name of a memory region as an argument.  *Note MEMORY::.  The load
-address of the section is set to the next free address in the region,
-aligned to the section's alignment requirements.
+   The 'AT' keyword takes an expression as an argument.  This specifies
+the exact load address of the section.  The 'AT>' keyword takes the name
+of a memory region as an argument.  *Note MEMORY::.  The load address of
+the section is set to the next free address in the region, aligned to
+the section's alignment requirements.
 
-   If neither `AT' nor `AT>' is specified for an allocatable section,
+   If neither 'AT' nor 'AT>' is specified for an allocatable section,
 the linker will use the following heuristic to determine the load
 address:
 
-   * If the section has a specific VMA address, then this is used as
-     the LMA address as well.
+   * If the section has a specific VMA address, then this is used as the
+     LMA address as well.
 
    * If the section is not allocatable then its LMA is set to its VMA.
 
    * Otherwise if a memory region can be found that is compatible with
-     the current section, and this region contains at least one
-     section, then the LMA is set so the difference between the VMA and
-     LMA is the same as the difference between the VMA and LMA of the
-     last section in the located region.
+     the current section, and this region contains at least one section,
+     then the LMA is set so the difference between the VMA and LMA is
+     the same as the difference between the VMA and LMA of the last
+     section in the located region.
 
    * If no memory regions have been declared then a default region that
      covers the entire address space is used in the previous step.
@@ -3749,10 +3713,10 @@ address:
 
    This feature is designed to make it easy to build a ROM image.  For
 example, the following linker script creates three output sections: one
-called `.text', which starts at `0x1000', one called `.mdata', which is
-loaded at the end of the `.text' section even though its VMA is
-`0x2000', and one called `.bss' to hold uninitialized data at address
-`0x3000'.  The symbol `_data' is defined with the value `0x2000', which
+called '.text', which starts at '0x1000', one called '.mdata', which is
+loaded at the end of the '.text' section even though its VMA is
+'0x2000', and one called '.bss' to hold uninitialized data at address
+'0x3000'.  The symbol '_data' is defined with the value '0x2000', which
 shows that the location counter holds the VMA value, not the LMA value.
 
      SECTIONS
@@ -3789,7 +3753,11 @@ File: ld.info,  Node: Forced Output Alignment,  Next: Forced Input Alignment,  P
 3.6.8.3 Forced Output Alignment
 ...............................
 
-You can increase an output section's alignment by using ALIGN.
+You can increase an output section's alignment by using ALIGN. As an
+alternative you can force the output section alignment to the maximum
+alignment of all its input sections with ALIGN_WITH_INPUT. The alignment
+forced by ALIGN_WITH_INPUT is used even in case the load and virtual
+memory regions are different.
 
 
 File: ld.info,  Node: Forced Input Alignment,  Next: Output Section Constraint,  Prev: Forced Output Alignment,  Up: Output Section Attributes
@@ -3798,7 +3766,7 @@ File: ld.info,  Node: Forced Input Alignment,  Next: Output Section Constraint,
 ..............................
 
 You can force input section alignment within an output section by using
-SUBALIGN.  The value specified overrides any alignment given by input
+SUBALIGN. The value specified overrides any alignment given by input
 sections, whether larger or smaller.
 
 
@@ -3809,7 +3777,7 @@ File: ld.info,  Node: Output Section Constraint,  Next: Output Section Region,
 
 You can specify that an output section should only be created if all of
 its input sections are read-only or all of its input sections are
-read-write by using the keyword `ONLY_IF_RO' and `ONLY_IF_RW'
+read-write by using the keyword 'ONLY_IF_RO' and 'ONLY_IF_RW'
 respectively.
 
 
@@ -3819,7 +3787,7 @@ File: ld.info,  Node: Output Section Region,  Next: Output Section Phdr,  Prev:
 .............................
 
 You can assign a section to a previously defined region of memory by
-using `>REGION'.  *Note MEMORY::.
+using '>REGION'.  *Note MEMORY::.
 
    Here is a simple example:
      MEMORY { rom : ORIGIN = 0x1000, LENGTH = 0x1000 }
@@ -3832,10 +3800,10 @@ File: ld.info,  Node: Output Section Phdr,  Next: Output Section Fill,  Prev: Ou
 ...........................
 
 You can assign a section to a previously defined program segment by
-using `:PHDR'.  *Note PHDRS::.  If a section is assigned to one or more
+using ':PHDR'.  *Note PHDRS::.  If a section is assigned to one or more
 segments, then all subsequent allocated sections will be assigned to
-those segments as well, unless they use an explicitly `:PHDR' modifier.
-You can use `:NONE' to tell the linker to not put the section in any
+those segments as well, unless they use an explicitly ':PHDR' modifier.
+You can use ':NONE' to tell the linker to not put the section in any
 segment at all.
 
    Here is a simple example:
@@ -3848,20 +3816,20 @@ File: ld.info,  Node: Output Section Fill,  Prev: Output Section Phdr,  Up: Outp
 3.6.8.8 Output Section Fill
 ...........................
 
-You can set the fill pattern for an entire section by using `=FILLEXP'.
+You can set the fill pattern for an entire section by using '=FILLEXP'.
 FILLEXP is an expression (*note Expressions::).  Any otherwise
 unspecified regions of memory within the output section (for example,
 gaps left due to the required alignment of input sections) will be
-filled with the value, repeated as necessary.  If the fill expression
-is a simple hex number, ie. a string of hex digit starting with `0x'
-and without a trailing `k' or `M', then an arbitrarily long sequence of
-hex digits can be used to specify the fill pattern;  Leading zeros
-become part of the pattern too.  For all other cases, including extra
-parentheses or a unary `+', the fill pattern is the four least
+filled with the value, repeated as necessary.  If the fill expression is
+a simple hex number, ie.  a string of hex digit starting with '0x' and
+without a trailing 'k' or 'M', then an arbitrarily long sequence of hex
+digits can be used to specify the fill pattern; Leading zeros become
+part of the pattern too.  For all other cases, including extra
+parentheses or a unary '+', the fill pattern is the four least
 significant bytes of the value of the expression.  In all cases, the
 number is big-endian.
 
-   You can also change the fill value with a `FILL' command in the
+   You can also change the fill value with a 'FILL' command in the
 output section commands; (*note Output Section Data::).
 
    Here is a simple example:
@@ -3881,9 +3849,9 @@ required, perhaps by simply manipulating addressing bits.  This approach
 can be useful, for example, when a certain region of memory is faster
 than another.
 
-   Overlays are described using the `OVERLAY' command.  The `OVERLAY'
-command is used within a `SECTIONS' command, like an output section
-description.  The full syntax of the `OVERLAY' command is as follows:
+   Overlays are described using the 'OVERLAY' command.  The 'OVERLAY'
+command is used within a 'SECTIONS' command, like an output section
+description.  The full syntax of the 'OVERLAY' command is as follows:
      OVERLAY [START] : [NOCROSSREFS] [AT ( LDADDR )]
        {
          SECNAME1
@@ -3901,60 +3869,59 @@ description.  The full syntax of the `OVERLAY' command is as follows:
          ...
        } [>REGION] [:PHDR...] [=FILL]
 
-   Everything is optional except `OVERLAY' (a keyword), and each
-section must have a name (SECNAME1 and SECNAME2 above).  The section
-definitions within the `OVERLAY' construct are identical to those
-within the general `SECTIONS' construct (*note SECTIONS::), except that
-no addresses and no memory regions may be defined for sections within
-an `OVERLAY'.
+   Everything is optional except 'OVERLAY' (a keyword), and each section
+must have a name (SECNAME1 and SECNAME2 above).  The section definitions
+within the 'OVERLAY' construct are identical to those within the general
+'SECTIONS' construct (*note SECTIONS::), except that no addresses and no
+memory regions may be defined for sections within an 'OVERLAY'.
 
    The sections are all defined with the same starting address.  The
 load addresses of the sections are arranged such that they are
 consecutive in memory starting at the load address used for the
-`OVERLAY' as a whole (as with normal section definitions, the load
+'OVERLAY' as a whole (as with normal section definitions, the load
 address is optional, and defaults to the start address; the start
 address is also optional, and defaults to the current value of the
 location counter).
 
-   If the `NOCROSSREFS' keyword is used, and there are any references
-among the sections, the linker will report an error.  Since the
-sections all run at the same address, it normally does not make sense
-for one section to refer directly to another.  *Note NOCROSSREFS:
-Miscellaneous Commands.
+   If the 'NOCROSSREFS' keyword is used, and there are any references
+among the sections, the linker will report an error.  Since the sections
+all run at the same address, it normally does not make sense for one
+section to refer directly to another.  *Note NOCROSSREFS: Miscellaneous
+Commands.
 
-   For each section within the `OVERLAY', the linker automatically
-provides two symbols.  The symbol `__load_start_SECNAME' is defined as
+   For each section within the 'OVERLAY', the linker automatically
+provides two symbols.  The symbol '__load_start_SECNAME' is defined as
 the starting load address of the section.  The symbol
-`__load_stop_SECNAME' is defined as the final load address of the
+'__load_stop_SECNAME' is defined as the final load address of the
 section.  Any characters within SECNAME which are not legal within C
-identifiers are removed.  C (or assembler) code may use these symbols
-to move the overlaid sections around as necessary.
+identifiers are removed.  C (or assembler) code may use these symbols to
+move the overlaid sections around as necessary.
 
    At the end of the overlay, the value of the location counter is set
 to the start address of the overlay plus the size of the largest
 section.
 
    Here is an example.  Remember that this would appear inside a
-`SECTIONS' construct.
+'SECTIONS' construct.
        OVERLAY 0x1000 : AT (0x4000)
         {
           .text0 { o1/*.o(.text) }
           .text1 { o2/*.o(.text) }
         }
-This will define both `.text0' and `.text1' to start at address 0x1000.
-`.text0' will be loaded at address 0x4000, and `.text1' will be loaded
-immediately after `.text0'.  The following symbols will be defined if
-referenced: `__load_start_text0', `__load_stop_text0',
-`__load_start_text1', `__load_stop_text1'.
+This will define both '.text0' and '.text1' to start at address 0x1000.
+'.text0' will be loaded at address 0x4000, and '.text1' will be loaded
+immediately after '.text0'.  The following symbols will be defined if
+referenced: '__load_start_text0', '__load_stop_text0',
+'__load_start_text1', '__load_stop_text1'.
 
-   C code to copy overlay `.text1' into the overlay area might look
-like the following.
+   C code to copy overlay '.text1' into the overlay area might look like
+the following.
 
        extern char __load_start_text1, __load_stop_text1;
        memcpy ((char *) 0x1000, &__load_start_text1,
                &__load_stop_text1 - &__load_start_text1);
 
-   Note that the `OVERLAY' command is just syntactic sugar, since
+   Note that the 'OVERLAY' command is just syntactic sugar, since
 everything it does can be done using the more basic commands.  The above
 example could have been written identically as follows.
 
@@ -3973,9 +3940,9 @@ File: ld.info,  Node: MEMORY,  Next: PHDRS,  Prev: SECTIONS,  Up: Scripts
 ==================
 
 The linker's default configuration permits allocation of all available
-memory.  You can override this by using the `MEMORY' command.
+memory.  You can override this by using the 'MEMORY' command.
 
-   The `MEMORY' command describes the location and size of blocks of
+   The 'MEMORY' command describes the location and size of blocks of
 memory in the target.  You can use it to describe which memory regions
 may be used by the linker, and which memory regions it must avoid.  You
 can then assign sections to particular memory regions.  The linker will
@@ -3983,7 +3950,7 @@ set section addresses based on the memory regions, and will warn about
 regions that become too full.  The linker will not shuffle sections
 around to fit into the available regions.
 
-   A linker script may contain at most one use of the `MEMORY' command.
+   A linker script may contain at most one use of the 'MEMORY' command.
 However, you can define as many blocks of memory within it as you wish.
 The syntax is:
      MEMORY
@@ -3996,7 +3963,7 @@ The syntax is:
 The region name has no meaning outside of the linker script.  Region
 names are stored in a separate name space, and will not conflict with
 symbol names, file names, or section names.  Each memory region must
-have a distinct name within the `MEMORY' command.  However you can add
+have a distinct name within the 'MEMORY' command.  However you can add
 later alias names to existing memory regions with the *note
 REGION_ALIAS:: command.
 
@@ -4009,49 +3976,43 @@ the input section.  If you define region attributes, the linker will use
 them to select the memory region for the output section that it creates.
 
    The ATTR string must consist only of the following characters:
-`R'
+'R'
      Read-only section
-
-`W'
+'W'
      Read/write section
-
-`X'
+'X'
      Executable section
-
-`A'
+'A'
      Allocatable section
-
-`I'
+'I'
      Initialized section
-
-`L'
-     Same as `I'
-
-`!'
+'L'
+     Same as 'I'
+'!'
      Invert the sense of any of the attributes that follow
 
    If a unmapped section matches any of the listed attributes other than
-`!', it will be placed in the memory region.  The `!' attribute
-reverses this test, so that an unmapped section will be placed in the
-memory region only if it does not match any of the listed attributes.
+'!', it will be placed in the memory region.  The '!' attribute reverses
+this test, so that an unmapped section will be placed in the memory
+region only if it does not match any of the listed attributes.
 
    The ORIGIN is an numerical expression for the start address of the
-memory region.  The expression must evaluate to a constant and it
-cannot involve any symbols.  The keyword `ORIGIN' may be abbreviated to
-`org' or `o' (but not, for example, `ORG').
+memory region.  The expression must evaluate to a constant and it cannot
+involve any symbols.  The keyword 'ORIGIN' may be abbreviated to 'org'
+or 'o' (but not, for example, 'ORG').
 
    The LEN is an expression for the size in bytes of the memory region.
-As with the ORIGIN expression, the expression must be numerical only
-and must evaluate to a constant.  The keyword `LENGTH' may be
-abbreviated to `len' or `l'.
+As with the ORIGIN expression, the expression must be numerical only and
+must evaluate to a constant.  The keyword 'LENGTH' may be abbreviated to
+'len' or 'l'.
 
    In the following example, we specify that there are two memory
-regions available for allocation: one starting at `0' for 256 kilobytes,
-and the other starting at `0x40000000' for four megabytes.  The linker
-will place into the `rom' memory region every section which is not
+regions available for allocation: one starting at '0' for 256 kilobytes,
+and the other starting at '0x40000000' for four megabytes.  The linker
+will place into the 'rom' memory region every section which is not
 explicitly mapped into a memory region, and is either read-only or
 executable.  The linker will place other sections which are not
-explicitly mapped into a memory region into the `ram' memory region.
+explicitly mapped into a memory region into the 'ram' memory region.
 
      MEMORY
        {
@@ -4060,9 +4021,9 @@ explicitly mapped into a memory region into the `ram' memory region.
        }
 
    Once you define a memory region, you can direct the linker to place
-specific output sections into that memory region by using the `>REGION'
+specific output sections into that memory region by using the '>REGION'
 output section attribute.  For example, if you have a memory region
-named `mem', you would use `>mem' in the output section definition.
+named 'mem', you would use '>mem' in the output section definition.
 *Note Output Section Region::.  If no address was specified for the
 output section, the linker will set the address to the next available
 address within the memory region.  If the combined output sections
@@ -4070,7 +4031,7 @@ directed to a memory region are too large for the region, the linker
 will issue an error message.
 
    It is possible to access the origin and length of a memory in an
-expression via the `ORIGIN(MEMORY)' and `LENGTH(MEMORY)' functions:
+expression via the 'ORIGIN(MEMORY)' and 'LENGTH(MEMORY)' functions:
 
        _fstack = ORIGIN(ram) + LENGTH(ram) - 4;
 
@@ -4082,8 +4043,8 @@ File: ld.info,  Node: PHDRS,  Next: VERSION,  Prev: MEMORY,  Up: Scripts
 
 The ELF object file format uses "program headers", also knows as
 "segments".  The program headers describe how the program should be
-loaded into memory.  You can print them out by using the `objdump'
-program with the `-p' option.
+loaded into memory.  You can print them out by using the 'objdump'
+program with the '-p' option.
 
    When you run an ELF program on a native ELF system, the system loader
 reads the program headers in order to figure out how to load the
@@ -4093,16 +4054,16 @@ interprets program headers; for more information, see the ELF ABI.
 
    The linker will create reasonable program headers by default.
 However, in some cases, you may need to specify the program headers more
-precisely.  You may use the `PHDRS' command for this purpose.  When the
-linker sees the `PHDRS' command in the linker script, it will not
-create any program headers other than the ones specified.
+precisely.  You may use the 'PHDRS' command for this purpose.  When the
+linker sees the 'PHDRS' command in the linker script, it will not create
+any program headers other than the ones specified.
 
-   The linker only pays attention to the `PHDRS' command when
-generating an ELF output file.  In other cases, the linker will simply
-ignore `PHDRS'.
+   The linker only pays attention to the 'PHDRS' command when generating
+an ELF output file.  In other cases, the linker will simply ignore
+'PHDRS'.
 
-   This is the syntax of the `PHDRS' command.  The words `PHDRS',
-`FILEHDR', `AT', and `FLAGS' are keywords.
+   This is the syntax of the 'PHDRS' command.  The words 'PHDRS',
+'FILEHDR', 'AT', and 'FLAGS' are keywords.
 
      PHDRS
      {
@@ -4110,7 +4071,7 @@ ignore `PHDRS'.
              [ FLAGS ( FLAGS ) ] ;
      }
 
-   The NAME is used only for reference in the `SECTIONS' command of the
+   The NAME is used only for reference in the 'SECTIONS' command of the
 linker script.  It is not put into the output file.  Program header
 names are stored in a separate name space, and will not conflict with
 symbol names, file names, or section names.  Each program header must
@@ -4120,55 +4081,55 @@ usual for them to map to sections in ascending load address order.
    Certain program header types describe segments of memory which the
 system loader will load from the file.  In the linker script, you
 specify the contents of these segments by placing allocatable output
-sections in the segments.  You use the `:PHDR' output section attribute
+sections in the segments.  You use the ':PHDR' output section attribute
 to place a section in a particular segment.  *Note Output Section
 Phdr::.
 
    It is normal to put certain sections in more than one segment.  This
 merely implies that one segment of memory contains another.  You may
-repeat `:PHDR', using it once for each segment which should contain the
+repeat ':PHDR', using it once for each segment which should contain the
 section.
 
-   If you place a section in one or more segments using `:PHDR', then
+   If you place a section in one or more segments using ':PHDR', then
 the linker will place all subsequent allocatable sections which do not
-specify `:PHDR' in the same segments.  This is for convenience, since
+specify ':PHDR' in the same segments.  This is for convenience, since
 generally a whole set of contiguous sections will be placed in a single
-segment.  You can use `:NONE' to override the default segment and tell
+segment.  You can use ':NONE' to override the default segment and tell
 the linker to not put the section in any segment at all.
 
-   You may use the `FILEHDR' and `PHDRS' keywords after the program
+   You may use the 'FILEHDR' and 'PHDRS' keywords after the program
 header type to further describe the contents of the segment.  The
-`FILEHDR' keyword means that the segment should include the ELF file
-header.  The `PHDRS' keyword means that the segment should include the
+'FILEHDR' keyword means that the segment should include the ELF file
+header.  The 'PHDRS' keyword means that the segment should include the
 ELF program headers themselves.  If applied to a loadable segment
-(`PT_LOAD'), all prior loadable segments must have one of these
+('PT_LOAD'), all prior loadable segments must have one of these
 keywords.
 
-   The TYPE may be one of the following.  The numbers indicate the
-value of the keyword.
+   The TYPE may be one of the following.  The numbers indicate the value
+of the keyword.
 
-`PT_NULL' (0)
+'PT_NULL' (0)
      Indicates an unused program header.
 
-`PT_LOAD' (1)
-     Indicates that this program header describes a segment to be
-     loaded from the file.
+'PT_LOAD' (1)
+     Indicates that this program header describes a segment to be loaded
+     from the file.
 
-`PT_DYNAMIC' (2)
+'PT_DYNAMIC' (2)
      Indicates a segment where dynamic linking information can be found.
 
-`PT_INTERP' (3)
+'PT_INTERP' (3)
      Indicates a segment where the name of the program interpreter may
      be found.
 
-`PT_NOTE' (4)
+'PT_NOTE' (4)
      Indicates a segment holding note information.
 
-`PT_SHLIB' (5)
+'PT_SHLIB' (5)
      A reserved program header type, defined but not specified by the
      ELF ABI.
 
-`PT_PHDR' (6)
+'PT_PHDR' (6)
      Indicates a segment where the program headers may be found.
 
 EXPRESSION
@@ -4176,17 +4137,17 @@ EXPRESSION
      may be used for types not defined above.
 
    You can specify that a segment should be loaded at a particular
-address in memory by using an `AT' expression.  This is identical to the
-`AT' command used as an output section attribute (*note Output Section
-LMA::).  The `AT' command for a program header overrides the output
+address in memory by using an 'AT' expression.  This is identical to the
+'AT' command used as an output section attribute (*note Output Section
+LMA::).  The 'AT' command for a program header overrides the output
 section attribute.
 
    The linker will normally set the segment flags based on the sections
-which comprise the segment.  You may use the `FLAGS' keyword to
+which comprise the segment.  You may use the 'FLAGS' keyword to
 explicitly specify the segment flags.  The value of FLAGS must be an
-integer.  It is used to set the `p_flags' field of the program header.
+integer.  It is used to set the 'p_flags' field of the program header.
 
-   Here is an example of `PHDRS'.  This shows a typical set of program
+   Here is an example of 'PHDRS'.  This shows a typical set of program
 headers used on a native ELF system.
 
      PHDRS
@@ -4217,7 +4178,7 @@ File: ld.info,  Node: VERSION,  Next: Expressions,  Prev: PHDRS,  Up: Scripts
 3.9 VERSION Command
 ===================
 
-The linker supports symbol versions when using ELF.  Symbol versions are
+The linker supports symbol versions when using ELF. Symbol versions are
 only useful when using shared libraries.  The dynamic linker can use
 symbol versions to select a specific version of a function when it runs
 a program that may have been linked against an earlier version of the
@@ -4225,9 +4186,9 @@ shared library.
 
    You can include a version script directly in the main linker script,
 or you can supply the version script as an implicit linker script.  You
-can also use the `--version-script' linker option.
+can also use the '--version-script' linker option.
 
-   The syntax of the `VERSION' command is simply
+   The syntax of the 'VERSION' command is simply
      VERSION { version-script-commands }
 
    The format of the version script commands is identical to that used
@@ -4259,32 +4220,32 @@ few examples.
      	 extern "C++" {
      		 ns::*;
      		 "f(int, double)";
-     	 };
+	      };
      } VERS_1.2;
 
    This example version script defines three version nodes.  The first
-version node defined is `VERS_1.1'; it has no other dependencies.  The
-script binds the symbol `foo1' to `VERS_1.1'.  It reduces a number of
+version node defined is 'VERS_1.1'; it has no other dependencies.  The
+script binds the symbol 'foo1' to 'VERS_1.1'.  It reduces a number of
 symbols to local scope so that they are not visible outside of the
-shared library; this is done using wildcard patterns, so that any
-symbol whose name begins with `old', `original', or `new' is matched.
-The wildcard patterns available are the same as those used in the shell
-when matching filenames (also known as "globbing").  However, if you
-specify the symbol name inside double quotes, then the name is treated
-as literal, rather than as a glob pattern.
+shared library; this is done using wildcard patterns, so that any symbol
+whose name begins with 'old', 'original', or 'new' is matched.  The
+wildcard patterns available are the same as those used in the shell when
+matching filenames (also known as "globbing").  However, if you specify
+the symbol name inside double quotes, then the name is treated as
+literal, rather than as a glob pattern.
 
-   Next, the version script defines node `VERS_1.2'.  This node depends
-upon `VERS_1.1'.  The script binds the symbol `foo2' to the version
-node `VERS_1.2'.
+   Next, the version script defines node 'VERS_1.2'.  This node depends
+upon 'VERS_1.1'.  The script binds the symbol 'foo2' to the version node
+'VERS_1.2'.
 
-   Finally, the version script defines node `VERS_2.0'.  This node
-depends upon `VERS_1.2'.  The scripts binds the symbols `bar1' and
-`bar2' are bound to the version node `VERS_2.0'.
+   Finally, the version script defines node 'VERS_2.0'.  This node
+depends upon 'VERS_1.2'.  The scripts binds the symbols 'bar1' and
+'bar2' are bound to the version node 'VERS_2.0'.
 
    When the linker finds a symbol defined in a library which is not
 specifically bound to a version node, it will effectively bind it to an
 unspecified base version of the library.  You can bind all otherwise
-unspecified symbols to a given version node by using `global: *;'
+unspecified symbols to a given version node by using 'global: *;'
 somewhere in the version script.  Note that it's slightly crazy to use
 wildcards in a global spec except on the last version node.  Global
 wildcards elsewhere run the risk of accidentally adding symbols to the
@@ -4292,12 +4253,12 @@ set exported for an old version.  That's wrong since older versions
 ought to have a fixed set of symbols.
 
    The names of the version nodes have no specific meaning other than
-what they might suggest to the person reading them.  The `2.0' version
-could just as well have appeared in between `1.1' and `1.2'.  However,
+what they might suggest to the person reading them.  The '2.0' version
+could just as well have appeared in between '1.1' and '1.2'.  However,
 this would be a confusing way to write a version script.
 
-   Node name can be omitted, provided it is the only version node in
-the version script.  Such version script doesn't assign any versions to
+   Node name can be omitted, provided it is the only version node in the
+version script.  Such version script doesn't assign any versions to
 symbols, only selects which symbols will be globally visible out and
 which won't.
 
@@ -4330,11 +4291,10 @@ source file where the symbol is defined instead of in the versioning
 script.  This was done mainly to reduce the burden on the library
 maintainer.  You can do this by putting something like:
      __asm__(".symver original_foo,foo@VERS_1.1");
-   in the C source file.  This renames the function `original_foo' to
-be an alias for `foo' bound to the version node `VERS_1.1'.  The
-`local:' directive can be used to prevent the symbol `original_foo'
-from being exported. A `.symver' directive takes precedence over a
-version script.
+in the C source file.  This renames the function 'original_foo' to be an
+alias for 'foo' bound to the version node 'VERS_1.1'.  The 'local:'
+directive can be used to prevent the symbol 'original_foo' from being
+exported.  A '.symver' directive takes precedence over a version script.
 
    The second GNU extension is to allow multiple versions of the same
 function to appear in a given shared library.  In this way you can make
@@ -4342,7 +4302,7 @@ an incompatible change to an interface without increasing the major
 version number of the shared library, while still allowing applications
 linked against the old interface to continue to function.
 
-   To do this, you must use multiple `.symver' directives in the source
+   To do this, you must use multiple '.symver' directives in the source
 file.  Here is an example:
 
      __asm__(".symver original_foo,foo@");
@@ -4350,36 +4310,36 @@ file.  Here is an example:
      __asm__(".symver old_foo1,foo@VERS_1.2");
      __asm__(".symver new_foo,foo@@VERS_2.0");
 
-   In this example, `foo@' represents the symbol `foo' bound to the
+   In this example, 'foo@' represents the symbol 'foo' bound to the
 unspecified base version of the symbol.  The source file that contains
-this example would define 4 C functions: `original_foo', `old_foo',
-`old_foo1', and `new_foo'.
+this example would define 4 C functions: 'original_foo', 'old_foo',
+'old_foo1', and 'new_foo'.
 
    When you have multiple definitions of a given symbol, there needs to
 be some way to specify a default version to which external references to
-this symbol will be bound.  You can do this with the `foo@@VERS_2.0'
-type of `.symver' directive.  You can only declare one version of a
+this symbol will be bound.  You can do this with the 'foo@@VERS_2.0'
+type of '.symver' directive.  You can only declare one version of a
 symbol as the default in this manner; otherwise you would effectively
 have multiple definitions of the same symbol.
 
    If you wish to bind a reference to a specific version of the symbol
-within the shared library, you can use the aliases of convenience
-(i.e., `old_foo'), or you can use the `.symver' directive to
-specifically bind to an external version of the function in question.
+within the shared library, you can use the aliases of convenience (i.e.,
+'old_foo'), or you can use the '.symver' directive to specifically bind
+to an external version of the function in question.
 
    You can also specify the language in the version script:
 
      VERSION extern "lang" { version-script-commands }
 
-   The supported `lang's are `C', `C++', and `Java'.  The linker will
+   The supported 'lang's are 'C', 'C++', and 'Java'.  The linker will
 iterate over the list of symbols at the link time and demangle them
-according to `lang' before matching them to the patterns specified in
-`version-script-commands'.  The default `lang' is `C'.
+according to 'lang' before matching them to the patterns specified in
+'version-script-commands'.  The default 'lang' is 'C'.
 
    Demangled names may contains spaces and other special characters.  As
-described above, you can use a glob pattern to match demangled names,
-or you can use a double-quoted string to match the string exactly.  In
-the latter case, be aware that minor differences (such as differing
+described above, you can use a glob pattern to match demangled names, or
+you can use a double-quoted string to match the string exactly.  In the
+latter case, be aware that minor differences (such as differing
 whitespace) between the version script and the demangler output will
 cause a mismatch.  As the exact string generated by the demangler might
 change in the future, even if the mangled name does not, you should
@@ -4422,23 +4382,23 @@ File: ld.info,  Node: Constants,  Next: Symbolic Constants,  Up: Expressions
 
 All constants are integers.
 
-   As in C, the linker considers an integer beginning with `0' to be
-octal, and an integer beginning with `0x' or `0X' to be hexadecimal.
-Alternatively the linker accepts suffixes of `h' or `H' for
-hexadecimal, `o' or `O' for octal, `b' or `B' for binary and `d' or `D'
-for decimal.  Any integer value without a prefix or a suffix is
-considered to be decimal.
+   As in C, the linker considers an integer beginning with '0' to be
+octal, and an integer beginning with '0x' or '0X' to be hexadecimal.
+Alternatively the linker accepts suffixes of 'h' or 'H' for hexadecimal,
+'o' or 'O' for octal, 'b' or 'B' for binary and 'd' or 'D' for decimal.
+Any integer value without a prefix or a suffix is considered to be
+decimal.
 
-   In addition, you can use the suffixes `K' and `M' to scale a
-constant by `1024' or `1024*1024' respectively.  For example, the
-following all refer to the same quantity:
+   In addition, you can use the suffixes 'K' and 'M' to scale a constant
+by '1024' or '1024*1024' respectively.  For example, the following all
+refer to the same quantity:
 
      _fourk_1 = 4K;
      _fourk_2 = 4096;
      _fourk_3 = 0x1000;
      _fourk_4 = 10000o;
 
-   Note - the `K' and `M' suffixes cannot be used in conjunction with
+   Note - the 'K' and 'M' suffixes cannot be used in conjunction with
 the base suffixes mentioned above.
 
 
@@ -4448,12 +4408,12 @@ File: ld.info,  Node: Symbolic Constants,  Next: Symbols,  Prev: Constants,  Up:
 -------------------------
 
 It is possible to refer to target specific constants via the use of the
-`CONSTANT(NAME)' operator, where NAME is one of:
+'CONSTANT(NAME)' operator, where NAME is one of:
 
-`MAXPAGESIZE'
+'MAXPAGESIZE'
      The target's maximum page size.
 
-`COMMONPAGESIZE'
+'COMMONPAGESIZE'
      The target's default page size.
 
    So for example:
@@ -4478,8 +4438,8 @@ keyword by surrounding the symbol name in double quotes:
      "with a space" = "also with a space" + 10;
 
    Since symbols can contain many non-alphabetic characters, it is
-safest to delimit symbols with spaces.  For example, `A-B' is one
-symbol, whereas `A - B' is an expression involving subtraction.
+safest to delimit symbols with spaces.  For example, 'A-B' is one
+symbol, whereas 'A - B' is an expression involving subtraction.
 
 
 File: ld.info,  Node: Orphan Sections,  Next: Location Counter,  Prev: Symbols,  Up: Expressions
@@ -4488,13 +4448,13 @@ File: ld.info,  Node: Orphan Sections,  Next: Location Counter,  Prev: Symbols,
 ----------------------
 
 Orphan sections are sections present in the input files which are not
-explicitly placed into the output file by the linker script.  The
-linker will still copy these sections into the output file, but it has
-to guess as to where they should be placed.  The linker uses a simple
-heuristic to do this.  It attempts to place orphan sections after
-non-orphan sections of the same attribute, such as code vs data,
-loadable vs non-loadable, etc.  If there is not enough room to do this
-then it places at the end of the file.
+explicitly placed into the output file by the linker script.  The linker
+will still copy these sections into the output file, but it has to guess
+as to where they should be placed.  The linker uses a simple heuristic
+to do this.  It attempts to place orphan sections after non-orphan
+sections of the same attribute, such as code vs data, loadable vs
+non-loadable, etc.  If there is not enough room to do this then it
+places at the end of the file.
 
    For ELF targets, the attribute of the section includes section type
 as well as section flag.
@@ -4504,7 +4464,7 @@ the linker will automatically *note PROVIDE:: two symbols:
 __start_SECNAME and __stop_SECNAME, where SECNAME is the name of the
 section.  These indicate the start address and end address of the
 orphaned section respectively.  Note: most section names are not
-representable as C identifiers because they contain a `.' character.
+representable as C identifiers because they contain a '.' character.
 
 
 File: ld.info,  Node: Location Counter,  Next: Operators,  Prev: Orphan Sections,  Up: Expressions
@@ -4512,17 +4472,17 @@ File: ld.info,  Node: Location Counter,  Next: Operators,  Prev: Orphan Sections
 3.10.5 The Location Counter
 ---------------------------
 
-The special linker variable "dot" `.' always contains the current
-output location counter.  Since the `.' always refers to a location in
-an output section, it may only appear in an expression within a
-`SECTIONS' command.  The `.' symbol may appear anywhere that an
-ordinary symbol is allowed in an expression.
+The special linker variable "dot" '.' always contains the current output
+location counter.  Since the '.' always refers to a location in an
+output section, it may only appear in an expression within a 'SECTIONS'
+command.  The '.' symbol may appear anywhere that an ordinary symbol is
+allowed in an expression.
 
-   Assigning a value to `.' will cause the location counter to be
-moved.  This may be used to create holes in the output section.  The
-location counter may not be moved backwards inside an output section,
-and may not be moved backwards outside of an output section if so doing
-creates areas with overlapping LMAs.
+   Assigning a value to '.' will cause the location counter to be moved.
+This may be used to create holes in the output section.  The location
+counter may not be moved backwards inside an output section, and may not
+be moved backwards outside of an output section if so doing creates
+areas with overlapping LMAs.
 
      SECTIONS
      {
@@ -4535,17 +4495,17 @@ creates areas with overlapping LMAs.
            file3(.text)
          } = 0x12345678;
      }
-   In the previous example, the `.text' section from `file1' is located
-at the beginning of the output section `output'.  It is followed by a
-1000 byte gap.  Then the `.text' section from `file2' appears, also
-with a 1000 byte gap following before the `.text' section from `file3'.
-The notation `= 0x12345678' specifies what data to write in the gaps
-(*note Output Section Fill::).
-
-   Note: `.' actually refers to the byte offset from the start of the
-current containing object.  Normally this is the `SECTIONS' statement,
-whose start address is 0, hence `.' can be used as an absolute address.
-If `.' is used inside a section description however, it refers to the
+In the previous example, the '.text' section from 'file1' is located at
+the beginning of the output section 'output'.  It is followed by a 1000
+byte gap.  Then the '.text' section from 'file2' appears, also with a
+1000 byte gap following before the '.text' section from 'file3'.  The
+notation '= 0x12345678' specifies what data to write in the gaps (*note
+Output Section Fill::).
+
+   Note: '.' actually refers to the byte offset from the start of the
+current containing object.  Normally this is the 'SECTIONS' statement,
+whose start address is 0, hence '.' can be used as an absolute address.
+If '.' is used inside a section description however, it refers to the
 byte offset from the start of that section, not an absolute address.
 Thus in a script like this:
 
@@ -4563,14 +4523,14 @@ Thus in a script like this:
          }
      }
 
-   The `.text' section will be assigned a starting address of 0x100 and
+   The '.text' section will be assigned a starting address of 0x100 and
 a size of exactly 0x200 bytes, even if there is not enough data in the
-`.text' input sections to fill this area.  (If there is too much data,
-an error will be produced because this would be an attempt to move `.'
-backwards).  The `.data' section will start at 0x500 and it will have
-an extra 0x600 bytes worth of space after the end of the values from
-the `.data' input sections and before the end of the `.data' output
-section itself.
+'.text' input sections to fill this area.  (If there is too much data,
+an error will be produced because this would be an attempt to move '.'
+backwards).  The '.data' section will start at 0x500 and it will have an
+extra 0x600 bytes worth of space after the end of the values from the
+'.data' input sections and before the end of the '.data' output section
+itself.
 
    Setting symbols to the value of the location counter outside of an
 output section statement can result in unexpected values if the linker
@@ -4587,15 +4547,15 @@ needs to place orphan sections.  For example, given the following:
          end_of_data = . ;
      }
 
-   If the linker needs to place some input section, e.g. `.rodata', not
+   If the linker needs to place some input section, e.g.  '.rodata', not
 mentioned in the script, it might choose to place that section between
-`.text' and `.data'.  You might think the linker should place `.rodata'
+'.text' and '.data'.  You might think the linker should place '.rodata'
 on the blank line in the above script, but blank lines are of no
 particular significance to the linker.  As well, the linker doesn't
 associate the above symbol names with their sections.  Instead, it
 assumes that all assignments or other statements belong to the previous
-output section, except for the special case of an assignment to `.'.
-I.e., the linker will place the orphan `.rodata' section as if the
+output section, except for the special case of an assignment to '.'.
+I.e., the linker will place the orphan '.rodata' section as if the
 script was written as follows:
 
      SECTIONS
@@ -4611,9 +4571,9 @@ script was written as follows:
      }
 
    This may or may not be the script author's intention for the value of
-`start_of_data'.  One way to influence the orphan section placement is
+'start_of_data'.  One way to influence the orphan section placement is
 to assign the location counter to itself, as the linker assumes that an
-assignment to `.' is setting the start address of a following output
+assignment to '.' is setting the start address of a following output
 section and thus should be grouped with that section.  So you could
 write:
 
@@ -4629,8 +4589,8 @@ write:
          end_of_data = . ;
      }
 
-   Now, the orphan `.rodata' section will be placed between
-`end_of_text' and `start_of_data'.
+   Now, the orphan '.rodata' section will be placed between
+'end_of_text' and 'start_of_data'.
 
 
 File: ld.info,  Node: Operators,  Next: Evaluation,  Prev: Location Counter,  Up: Expressions
@@ -4680,7 +4640,7 @@ assignments dependent upon these are not performed until after
 allocation.
 
    Some expressions, such as those depending upon the location counter
-`.', must be evaluated during section allocation.
+'.', must be evaluated during section allocation.
 
    If the result of an expression is required, but the value is not
 available, then an error results.  For example, a script like the
@@ -4690,7 +4650,7 @@ following
          .text 9+this_isnt_constant :
            { *(.text) }
        }
-will cause the error message `non constant expression for initial
+will cause the error message 'non constant expression for initial
 address'.
 
 
@@ -4700,22 +4660,22 @@ File: ld.info,  Node: Expression Section,  Next: Builtin Functions,  Prev: Evalu
 -----------------------------------
 
 Addresses and symbols may be section relative, or absolute.  A section
-relative symbol is relocatable.  If you request relocatable output
-using the `-r' option, a further link operation may change the value of
-a section relative symbol.  On the other hand, an absolute symbol will
+relative symbol is relocatable.  If you request relocatable output using
+the '-r' option, a further link operation may change the value of a
+section relative symbol.  On the other hand, an absolute symbol will
 retain the same value throughout any further link operations.
 
    Some terms in linker expressions are addresses.  This is true of
 section relative symbols and for builtin functions that return an
-address, such as `ADDR', `LOADADDR', `ORIGIN' and `SEGMENT_START'.
+address, such as 'ADDR', 'LOADADDR', 'ORIGIN' and 'SEGMENT_START'.
 Other terms are simply numbers, or are builtin functions that return a
-non-address value, such as `LENGTH'.  One complication is that unless
-you set `LD_FEATURE ("SANE_EXPR")' (*note Miscellaneous Commands::),
+non-address value, such as 'LENGTH'.  One complication is that unless
+you set 'LD_FEATURE ("SANE_EXPR")' (*note Miscellaneous Commands::),
 numbers and absolute symbols are treated differently depending on their
-location, for compatibility with older versions of `ld'.  Expressions
+location, for compatibility with older versions of 'ld'.  Expressions
 appearing outside an output section definition treat all numbers as
 absolute addresses.  Expressions appearing inside an output section
-definition treat absolute symbols as numbers.  If `LD_FEATURE
+definition treat absolute symbols as numbers.  If 'LD_FEATURE
 ("SANE_EXPR")' is given, then absolute symbols and numbers are simply
 treated as numbers everywhere.
 
@@ -4734,9 +4694,9 @@ treated as numbers everywhere.
          ...
        }
 
-   both `.' and `__executable_start' are set to the absolute address
-0x100 in the first two assignments, then both `.' and `__data_start'
-are set to 0x10 relative to the `.data' section in the second two
+   both '.' and '__executable_start' are set to the absolute address
+0x100 in the first two assignments, then both '.' and '__data_start' are
+set to 0x10 relative to the '.data' section in the second two
 assignments.
 
    For expressions involving numbers, relative addresses and absolute
@@ -4745,12 +4705,10 @@ addresses, ld follows these rules to evaluate terms:
    * Unary operations on an absolute address or number, and binary
      operations on two absolute addresses or two numbers, or between one
      absolute address and a number, apply the operator to the value(s).
-
    * Unary operations on a relative address, and binary operations on
      two relative addresses in the same section or between one relative
      address and a number, apply the operator to the offset part of the
      address(es).
-
    * Other binary operations, that is, between two relative addresses
      not in the same section, or between a relative address and an
      absolute address, first convert any non-absolute term to an
@@ -4759,32 +4717,28 @@ addresses, ld follows these rules to evaluate terms:
    The result section of each sub-expression is as follows:
 
    * An operation involving only numbers results in a number.
-
-   * The result of comparisons, `&&' and `||' is also a number.
-
+   * The result of comparisons, '&&' and '||' is also a number.
    * The result of other binary arithmetic and logical operations on two
      relative addresses in the same section or two absolute addresses
      (after above conversions) is also a number.
-
    * The result of other operations on relative addresses or one
      relative address and a number, is a relative address in the same
      section as the relative operand(s).
-
    * The result of other operations on absolute addresses (after above
      conversions) is an absolute address.
 
-   You can use the builtin function `ABSOLUTE' to force an expression
-to be absolute when it would otherwise be relative.  For example, to
-create an absolute symbol set to the address of the end of the output
-section `.data':
+   You can use the builtin function 'ABSOLUTE' to force an expression to
+be absolute when it would otherwise be relative.  For example, to create
+an absolute symbol set to the address of the end of the output section
+'.data':
      SECTIONS
        {
          .data : { *(.data) _edata = ABSOLUTE(.); }
        }
-   If `ABSOLUTE' were not used, `_edata' would be relative to the
-`.data' section.
+If 'ABSOLUTE' were not used, '_edata' would be relative to the '.data'
+section.
 
-   Using `LOADADDR' also forces an expression absolute, since this
+   Using 'LOADADDR' also forces an expression absolute, since this
 particular builtin function returns an absolute address.
 
 
@@ -4796,19 +4750,19 @@ File: ld.info,  Node: Builtin Functions,  Prev: Expression Section,  Up: Express
 The linker script language includes a number of builtin functions for
 use in linker script expressions.
 
-`ABSOLUTE(EXP)'
+'ABSOLUTE(EXP)'
      Return the absolute (non-relocatable, as opposed to non-negative)
      value of the expression EXP.  Primarily useful to assign an
      absolute value to a symbol within a section definition, where
      symbol values are normally section relative.  *Note Expression
      Section::.
 
-`ADDR(SECTION)'
+'ADDR(SECTION)'
      Return the address (VMA) of the named SECTION.  Your script must
      previously have defined the location of that section.  In the
-     following example, `start_of_output_1', `symbol_1' and `symbol_2'
-     are assigned equivalent values, except that `symbol_1' will be
-     relative to the `.output1' section while the other two will be
+     following example, 'start_of_output_1', 'symbol_1' and 'symbol_2'
+     are assigned equivalent values, except that 'symbol_1' will be
+     relative to the '.output1' section while the other two will be
      absolute:
           SECTIONS { ...
             .output1 :
@@ -4823,18 +4777,18 @@ use in linker script expressions.
               }
           ... }
 
-`ALIGN(ALIGN)'
-`ALIGN(EXP,ALIGN)'
-     Return the location counter (`.') or arbitrary expression aligned
-     to the next ALIGN boundary.  The single operand `ALIGN' doesn't
+'ALIGN(ALIGN)'
+'ALIGN(EXP,ALIGN)'
+     Return the location counter ('.') or arbitrary expression aligned
+     to the next ALIGN boundary.  The single operand 'ALIGN' doesn't
      change the value of the location counter--it just does arithmetic
-     on it.  The two operand `ALIGN' allows an arbitrary expression to
-     be aligned upwards (`ALIGN(ALIGN)' is equivalent to `ALIGN(.,
+     on it.  The two operand 'ALIGN' allows an arbitrary expression to
+     be aligned upwards ('ALIGN(ALIGN)' is equivalent to 'ALIGN(.,
      ALIGN)').
 
-     Here is an example which aligns the output `.data' section to the
-     next `0x2000' byte boundary after the preceding section and sets a
-     variable within the section to the next `0x8000' boundary after the
+     Here is an example which aligns the output '.data' section to the
+     next '0x2000' byte boundary after the preceding section and sets a
+     variable within the section to the next '0x8000' boundary after the
      input sections:
           SECTIONS { ...
             .data ALIGN(0x2000): {
@@ -4842,19 +4796,19 @@ use in linker script expressions.
               variable = ALIGN(0x8000);
             }
           ... }
-     The first use of `ALIGN' in this example specifies the location of
-     a section because it is used as the optional ADDRESS attribute of
-     a section definition (*note Output Section Address::).  The second
-     use of `ALIGN' is used to defines the value of a symbol.
-
-     The builtin function `NEXT' is closely related to `ALIGN'.
-
-`ALIGNOF(SECTION)'
-     Return the alignment in bytes of the named SECTION, if that
-     section has been allocated.  If the section has not been allocated
-     when this is evaluated, the linker will report an error. In the
-     following example, the alignment of the `.output' section is
-     stored as the first value in that section.
+     The first use of 'ALIGN' in this example specifies the location of
+     a section because it is used as the optional ADDRESS attribute of a
+     section definition (*note Output Section Address::).  The second
+     use of 'ALIGN' is used to defines the value of a symbol.
+
+     The builtin function 'NEXT' is closely related to 'ALIGN'.
+
+'ALIGNOF(SECTION)'
+     Return the alignment in bytes of the named SECTION, if that section
+     has been allocated.  If the section has not been allocated when
+     this is evaluated, the linker will report an error.  In the
+     following example, the alignment of the '.output' section is stored
+     as the first value in that section.
           SECTIONS{ ...
             .output {
               LONG (ALIGNOF (.output))
@@ -4862,56 +4816,56 @@ use in linker script expressions.
               }
           ... }
 
-`BLOCK(EXP)'
-     This is a synonym for `ALIGN', for compatibility with older linker
+'BLOCK(EXP)'
+     This is a synonym for 'ALIGN', for compatibility with older linker
      scripts.  It is most often seen when setting the address of an
      output section.
 
-`DATA_SEGMENT_ALIGN(MAXPAGESIZE, COMMONPAGESIZE)'
+'DATA_SEGMENT_ALIGN(MAXPAGESIZE, COMMONPAGESIZE)'
      This is equivalent to either
           (ALIGN(MAXPAGESIZE) + (. & (MAXPAGESIZE - 1)))
      or
           (ALIGN(MAXPAGESIZE) + (. & (MAXPAGESIZE - COMMONPAGESIZE)))
      depending on whether the latter uses fewer COMMONPAGESIZE sized
      pages for the data segment (area between the result of this
-     expression and `DATA_SEGMENT_END') than the former or not.  If the
+     expression and 'DATA_SEGMENT_END') than the former or not.  If the
      latter form is used, it means COMMONPAGESIZE bytes of runtime
      memory will be saved at the expense of up to COMMONPAGESIZE wasted
      bytes in the on-disk file.
 
-     This expression can only be used directly in `SECTIONS' commands,
+     This expression can only be used directly in 'SECTIONS' commands,
      not in any output section descriptions and only once in the linker
      script.  COMMONPAGESIZE should be less or equal to MAXPAGESIZE and
-     should be the system page size the object wants to be optimized
-     for (while still working on system page sizes up to MAXPAGESIZE).
+     should be the system page size the object wants to be optimized for
+     (while still working on system page sizes up to MAXPAGESIZE).
 
      Example:
             . = DATA_SEGMENT_ALIGN(0x10000, 0x2000);
 
-`DATA_SEGMENT_END(EXP)'
-     This defines the end of data segment for `DATA_SEGMENT_ALIGN'
+'DATA_SEGMENT_END(EXP)'
+     This defines the end of data segment for 'DATA_SEGMENT_ALIGN'
      evaluation purposes.
 
             . = DATA_SEGMENT_END(.);
 
-`DATA_SEGMENT_RELRO_END(OFFSET, EXP)'
-     This defines the end of the `PT_GNU_RELRO' segment when `-z relro'
-     option is used.  Second argument is returned.  When `-z relro'
-     option is not present, `DATA_SEGMENT_RELRO_END' does nothing,
-     otherwise `DATA_SEGMENT_ALIGN' is padded so that EXP + OFFSET is
+'DATA_SEGMENT_RELRO_END(OFFSET, EXP)'
+     This defines the end of the 'PT_GNU_RELRO' segment when '-z relro'
+     option is used.  Second argument is returned.  When '-z relro'
+     option is not present, 'DATA_SEGMENT_RELRO_END' does nothing,
+     otherwise 'DATA_SEGMENT_ALIGN' is padded so that EXP + OFFSET is
      aligned to the most commonly used page boundary for particular
      target.  If present in the linker script, it must always come in
-     between `DATA_SEGMENT_ALIGN' and `DATA_SEGMENT_END'.
+     between 'DATA_SEGMENT_ALIGN' and 'DATA_SEGMENT_END'.
 
             . = DATA_SEGMENT_RELRO_END(24, .);
 
-`DEFINED(SYMBOL)'
+'DEFINED(SYMBOL)'
      Return 1 if SYMBOL is in the linker global symbol table and is
      defined before the statement using DEFINED in the script, otherwise
      return 0.  You can use this function to provide default values for
      symbols.  For example, the following script fragment shows how to
-     set a global symbol `begin' to the first location in the `.text'
-     section--but if a symbol called `begin' already existed, its value
+     set a global symbol 'begin' to the first location in the '.text'
+     section--but if a symbol called 'begin' already existed, its value
      is preserved:
 
           SECTIONS { ...
@@ -4922,41 +4876,45 @@ use in linker script expressions.
             ...
           }
 
-`LENGTH(MEMORY)'
+'LENGTH(MEMORY)'
      Return the length of the memory region named MEMORY.
 
-`LOADADDR(SECTION)'
+'LOADADDR(SECTION)'
      Return the absolute LMA of the named SECTION.  (*note Output
      Section LMA::).
 
-`MAX(EXP1, EXP2)'
+'LOG2CEIL(EXP)'
+     Return the binary logarithm of EXP rounded towards infinity.
+     'LOG2CEIL(0)' returns 0.
+
+'MAX(EXP1, EXP2)'
      Returns the maximum of EXP1 and EXP2.
 
-`MIN(EXP1, EXP2)'
+'MIN(EXP1, EXP2)'
      Returns the minimum of EXP1 and EXP2.
 
-`NEXT(EXP)'
+'NEXT(EXP)'
      Return the next unallocated address that is a multiple of EXP.
-     This function is closely related to `ALIGN(EXP)'; unless you use
-     the `MEMORY' command to define discontinuous memory for the output
+     This function is closely related to 'ALIGN(EXP)'; unless you use
+     the 'MEMORY' command to define discontinuous memory for the output
      file, the two functions are equivalent.
 
-`ORIGIN(MEMORY)'
+'ORIGIN(MEMORY)'
      Return the origin of the memory region named MEMORY.
 
-`SEGMENT_START(SEGMENT, DEFAULT)'
-     Return the base address of the named SEGMENT.  If an explicit
-     value has been given for this segment (with a command-line `-T'
-     option) that value will be returned; otherwise the value will be
-     DEFAULT.  At present, the `-T' command-line option can only be
+'SEGMENT_START(SEGMENT, DEFAULT)'
+     Return the base address of the named SEGMENT.  If an explicit value
+     has already been given for this segment (with a command-line '-T'
+     option) then that value will be returned otherwise the value will
+     be DEFAULT.  At present, the '-T' command-line option can only be
      used to set the base address for the "text", "data", and "bss"
-     sections, but you can use `SEGMENT_START' with any segment name.
+     sections, but you can use 'SEGMENT_START' with any segment name.
 
-`SIZEOF(SECTION)'
+'SIZEOF(SECTION)'
      Return the size in bytes of the named SECTION, if that section has
      been allocated.  If the section has not been allocated when this is
      evaluated, the linker will report an error.  In the following
-     example, `symbol_1' and `symbol_2' are assigned identical values:
+     example, 'symbol_1' and 'symbol_2' are assigned identical values:
           SECTIONS{ ...
             .output {
               .start = . ;
@@ -4967,23 +4925,23 @@ use in linker script expressions.
             symbol_2 = SIZEOF(.output);
           ... }
 
-`SIZEOF_HEADERS'
-`sizeof_headers'
+'SIZEOF_HEADERS'
+'sizeof_headers'
      Return the size in bytes of the output file's headers.  This is
-     information which appears at the start of the output file.  You
-     can use this number when setting the start address of the first
+     information which appears at the start of the output file.  You can
+     use this number when setting the start address of the first
      section, if you choose, to facilitate paging.
 
      When producing an ELF output file, if the linker script uses the
-     `SIZEOF_HEADERS' builtin function, the linker must compute the
+     'SIZEOF_HEADERS' builtin function, the linker must compute the
      number of program headers before it has determined all the section
      addresses and sizes.  If the linker later discovers that it needs
-     additional program headers, it will report an error `not enough
+     additional program headers, it will report an error 'not enough
      room for program headers'.  To avoid this error, you must avoid
-     using the `SIZEOF_HEADERS' function, or you must rework your linker
+     using the 'SIZEOF_HEADERS' function, or you must rework your linker
      script to avoid forcing the linker to use additional program
      headers, or you must define the program headers yourself using the
-     `PHDRS' command (*note PHDRS::).
+     'PHDRS' command (*note PHDRS::).
 
 
 File: ld.info,  Node: Implicit Linker Scripts,  Prev: Expressions,  Up: Scripts
@@ -4999,7 +4957,7 @@ linker will report an error.
    An implicit linker script will not replace the default linker script.
 
    Typically an implicit linker script would contain only symbol
-assignments, or the `INPUT', `GROUP', or `VERSION' commands.
+assignments, or the 'INPUT', 'GROUP', or 'VERSION' commands.
 
    Any input files read because of an implicit linker script will be
 read at the position in the command line where the implicit linker
@@ -5011,103 +4969,90 @@ File: ld.info,  Node: Machine Dependent,  Next: BFD,  Prev: Scripts,  Up: Top
 4 Machine Dependent Features
 ****************************
 
-`ld' has additional features on some platforms; the following sections
-describe them.  Machines where `ld' has no additional functionality are
+'ld' has additional features on some platforms; the following sections
+describe them.  Machines where 'ld' has no additional functionality are
 not listed.
 
 * Menu:
 
-
-* H8/300::                      `ld' and the H8/300
-
-* i960::                        `ld' and the Intel 960 family
-
-* M68HC11/68HC12::		`ld' and the Motorola 68HC11 and 68HC12 families
-
-* ARM::				`ld' and the ARM family
-
-* HPPA ELF32::                  `ld' and HPPA 32-bit ELF
-
-* M68K::			`ld' and the Motorola 68K family
-
-* MMIX::			`ld' and MMIX
-
-* MSP430::			`ld' and MSP430
-
-* PowerPC ELF32::		`ld' and PowerPC 32-bit ELF Support
-
-* PowerPC64 ELF64::		`ld' and PowerPC64 64-bit ELF Support
-
-* SPU ELF::			`ld' and SPU ELF Support
-
-* TI COFF::                     `ld' and TI COFF
-
-* WIN32::                       `ld' and WIN32 (cygwin/mingw)
-
-* Xtensa::                      `ld' and Xtensa Processors
+* H8/300::                      'ld' and the H8/300
+* i960::                        'ld' and the Intel 960 family
+* M68HC11/68HC12::		'ld' and the Motorola 68HC11 and 68HC12 families
+* ARM::				'ld' and the ARM family
+* HPPA ELF32::                  'ld' and HPPA 32-bit ELF
+* M68K::			'ld' and the Motorola 68K family
+* MIPS::			'ld' and the MIPS family
+* MMIX::			'ld' and MMIX
+* MSP430::			'ld' and MSP430
+* PowerPC ELF32::		'ld' and PowerPC 32-bit ELF Support
+* PowerPC64 ELF64::		'ld' and PowerPC64 64-bit ELF Support
+* SPU ELF::			'ld' and SPU ELF Support
+* TI COFF::                     'ld' and TI COFF
+* WIN32::                       'ld' and WIN32 (cygwin/mingw)
+* Xtensa::                      'ld' and Xtensa Processors
 
 
 File: ld.info,  Node: H8/300,  Next: i960,  Up: Machine Dependent
 
-4.1 `ld' and the H8/300
+4.1 'ld' and the H8/300
 =======================
 
-For the H8/300, `ld' can perform these global optimizations when you
-specify the `--relax' command-line option.
+For the H8/300, 'ld' can perform these global optimizations when you
+specify the '--relax' command-line option.
 
 _relaxing address modes_
-     `ld' finds all `jsr' and `jmp' instructions whose targets are
+     'ld' finds all 'jsr' and 'jmp' instructions whose targets are
      within eight bits, and turns them into eight-bit program-counter
-     relative `bsr' and `bra' instructions, respectively.
+     relative 'bsr' and 'bra' instructions, respectively.
 
 _synthesizing instructions_
-     `ld' finds all `mov.b' instructions which use the sixteen-bit
+     'ld' finds all 'mov.b' instructions which use the sixteen-bit
      absolute address form, but refer to the top page of memory, and
      changes them to use the eight-bit address form.  (That is: the
-     linker turns `mov.b `@'AA:16' into `mov.b `@'AA:8' whenever the
+     linker turns 'mov.b '@'AA:16' into 'mov.b '@'AA:8' whenever the
      address AA is in the top page of memory).
 
-     `ld' finds all `mov' instructions which use the register indirect
+     'ld' finds all 'mov' instructions which use the register indirect
      with 32-bit displacement addressing mode, but use a small
      displacement inside 16-bit displacement range, and changes them to
      use the 16-bit displacement form.  (That is: the linker turns
-     `mov.b `@'D:32,ERx' into `mov.b `@'D:16,ERx' whenever the
-     displacement D is in the 16 bit signed integer range. Only
+     'mov.b '@'D:32,ERx' into 'mov.b '@'D:16,ERx' whenever the
+     displacement D is in the 16 bit signed integer range.  Only
      implemented in ELF-format ld).
 
 _bit manipulation instructions_
-     `ld' finds all bit manipulation instructions like `band, bclr,
+     'ld' finds all bit manipulation instructions like 'band, bclr,
      biand, bild, bior, bist, bixor, bld, bnot, bor, bset, bst, btst,
      bxor' which use 32 bit and 16 bit absolute address form, but refer
      to the top page of memory, and changes them to use the 8 bit
-     address form.  (That is: the linker turns `bset #xx:3,`@'AA:32'
-     into `bset #xx:3,`@'AA:8' whenever the address AA is in the top
+     address form.  (That is: the linker turns 'bset #xx:3,'@'AA:32'
+     into 'bset #xx:3,'@'AA:8' whenever the address AA is in the top
      page of memory).
 
 _system control instructions_
-     `ld' finds all `ldc.w, stc.w' instructions which use the 32 bit
+     'ld' finds all 'ldc.w, stc.w' instructions which use the 32 bit
      absolute address form, but refer to the top page of memory, and
      changes them to use 16 bit address form.  (That is: the linker
-     turns `ldc.w `@'AA:32,ccr' into `ldc.w `@'AA:16,ccr' whenever the
+     turns 'ldc.w '@'AA:32,ccr' into 'ldc.w '@'AA:16,ccr' whenever the
      address AA is in the top page of memory).
 
 
 File: ld.info,  Node: i960,  Next: M68HC11/68HC12,  Prev: H8/300,  Up: Machine Dependent
 
-4.2 `ld' and the Intel 960 Family
+4.2 'ld' and the Intel 960 Family
 =================================
 
-You can use the `-AARCHITECTURE' command line option to specify one of
+You can use the '-AARCHITECTURE' command line option to specify one of
 the two-letter names identifying members of the 960 family; the option
 specifies the desired output target, and warns of any incompatible
 instructions in the input files.  It also modifies the linker's search
-strategy for archive libraries, to support the use of libraries
-specific to each particular architecture, by including in the search
-loop names suffixed with the string identifying the architecture.
+strategy for archive libraries, to support the use of libraries specific
+to each particular architecture, by including in the search loop names
+suffixed with the string identifying the architecture.
 
-   For example, if your `ld' command line included `-ACA' as well as
-`-ltry', the linker would look (in its built-in search paths, and in
-any paths you specify with `-L') for a library with the names
+   For example, if your 'ld' command line included '-ACA' as well as
+'-ltry', the linker would look (in its built-in search paths, and in any
+paths you specify with '-L') for a library with the names
 
      try
      libtry.a
@@ -5115,134 +5060,131 @@ any paths you specify with `-L') for a library with the names
      libtryca.a
 
 The first two possibilities would be considered in any event; the last
-two are due to the use of `-ACA'.
+two are due to the use of '-ACA'.
 
-   You can meaningfully use `-A' more than once on a command line, since
+   You can meaningfully use '-A' more than once on a command line, since
 the 960 architecture family allows combination of target architectures;
-each use will add another pair of name variants to search for when `-l'
+each use will add another pair of name variants to search for when '-l'
 specifies a library.
 
-   `ld' supports the `--relax' option for the i960 family.  If you
-specify `--relax', `ld' finds all `balx' and `calx' instructions whose
+   'ld' supports the '--relax' option for the i960 family.  If you
+specify '--relax', 'ld' finds all 'balx' and 'calx' instructions whose
 targets are within 24 bits, and turns them into 24-bit program-counter
-relative `bal' and `cal' instructions, respectively.  `ld' also turns
-`cal' instructions into `bal' instructions when it determines that the
+relative 'bal' and 'cal' instructions, respectively.  'ld' also turns
+'cal' instructions into 'bal' instructions when it determines that the
 target subroutine is a leaf routine (that is, the target subroutine does
 not itself call any subroutines).
 
-   The `--fix-cortex-a8' switch enables a link-time workaround for an
+   The '--fix-cortex-a8' switch enables a link-time workaround for an
 erratum in certain Cortex-A8 processors.  The workaround is enabled by
 default if you are targeting the ARM v7-A architecture profile.  It can
-be enabled otherwise by specifying `--fix-cortex-a8', or disabled
-unconditionally by specifying `--no-fix-cortex-a8'.
+be enabled otherwise by specifying '--fix-cortex-a8', or disabled
+unconditionally by specifying '--no-fix-cortex-a8'.
 
    The erratum only affects Thumb-2 code.  Please contact ARM for
 further details.
 
-   The `--no-merge-exidx-entries' switch disables the merging of
+   The '--no-merge-exidx-entries' switch disables the merging of
 adjacent exidx entries in debuginfo.
 
 
 File: ld.info,  Node: M68HC11/68HC12,  Next: ARM,  Prev: i960,  Up: Machine Dependent
 
-4.3 `ld' and the Motorola 68HC11 and 68HC12 families
+4.3 'ld' and the Motorola 68HC11 and 68HC12 families
 ====================================================
 
 4.3.1 Linker Relaxation
 -----------------------
 
-For the Motorola 68HC11, `ld' can perform these global optimizations
-when you specify the `--relax' command-line option.
+For the Motorola 68HC11, 'ld' can perform these global optimizations
+when you specify the '--relax' command-line option.
 
 _relaxing address modes_
-     `ld' finds all `jsr' and `jmp' instructions whose targets are
+     'ld' finds all 'jsr' and 'jmp' instructions whose targets are
      within eight bits, and turns them into eight-bit program-counter
-     relative `bsr' and `bra' instructions, respectively.
+     relative 'bsr' and 'bra' instructions, respectively.
 
-     `ld' also looks at all 16-bit extended addressing modes and
+     'ld' also looks at all 16-bit extended addressing modes and
      transforms them in a direct addressing mode when the address is in
      page 0 (between 0 and 0x0ff).
 
 _relaxing gcc instruction group_
-     When `gcc' is called with `-mrelax', it can emit group of
+     When 'gcc' is called with '-mrelax', it can emit group of
      instructions that the linker can optimize to use a 68HC11 direct
-     addressing mode. These instructions consists of `bclr' or `bset'
+     addressing mode.  These instructions consists of 'bclr' or 'bset'
      instructions.
 
-
 4.3.2 Trampoline Generation
 ---------------------------
 
-For 68HC11 and 68HC12, `ld' can generate trampoline code to call a far
-function using a normal `jsr' instruction. The linker will also change
+For 68HC11 and 68HC12, 'ld' can generate trampoline code to call a far
+function using a normal 'jsr' instruction.  The linker will also change
 the relocation to some far function to use the trampoline address
-instead of the function address. This is typically the case when a
-pointer to a function is taken. The pointer will in fact point to the
+instead of the function address.  This is typically the case when a
+pointer to a function is taken.  The pointer will in fact point to the
 function trampoline.
 
 
 File: ld.info,  Node: ARM,  Next: HPPA ELF32,  Prev: M68HC11/68HC12,  Up: Machine Dependent
 
-4.4 `ld' and the ARM family
+4.4 'ld' and the ARM family
 ===========================
 
-For the ARM, `ld' will generate code stubs to allow functions calls
+For the ARM, 'ld' will generate code stubs to allow functions calls
 between ARM and Thumb code.  These stubs only work with code that has
-been compiled and assembled with the `-mthumb-interwork' command line
+been compiled and assembled with the '-mthumb-interwork' command line
 option.  If it is necessary to link with old ARM object files or
 libraries, which have not been compiled with the -mthumb-interwork
-option then the `--support-old-code' command line switch should be
-given to the linker.  This will make it generate larger stub functions
-which will work with non-interworking aware ARM code.  Note, however,
-the linker does not support generating stubs for function calls to
+option then the '--support-old-code' command line switch should be given
+to the linker.  This will make it generate larger stub functions which
+will work with non-interworking aware ARM code.  Note, however, the
+linker does not support generating stubs for function calls to
 non-interworking aware Thumb code.
 
-   The `--thumb-entry' switch is a duplicate of the generic `--entry'
+   The '--thumb-entry' switch is a duplicate of the generic '--entry'
 switch, in that it sets the program's starting address.  But it also
 sets the bottom bit of the address, so that it can be branched to using
 a BX instruction, and the program will start executing in Thumb mode
 straight away.
 
-   The `--use-nul-prefixed-import-tables' switch is specifying, that
-the import tables idata4 and idata5 have to be generated with a zero
-element prefix for import libraries. This is the old style to generate
-import tables. By default this option is turned off.
+   The '--use-nul-prefixed-import-tables' switch is specifying, that the
+import tables idata4 and idata5 have to be generated with a zero element
+prefix for import libraries.  This is the old style to generate import
+tables.  By default this option is turned off.
 
-   The `--be8' switch instructs `ld' to generate BE8 format
-executables.  This option is only valid when linking big-endian objects.
-The resulting image will contain big-endian data and little-endian code.
+   The '--be8' switch instructs 'ld' to generate BE8 format executables.
+This option is only valid when linking big-endian objects.  The
+resulting image will contain big-endian data and little-endian code.
 
-   The `R_ARM_TARGET1' relocation is typically used for entries in the
-`.init_array' section.  It is interpreted as either `R_ARM_REL32' or
-`R_ARM_ABS32', depending on the target.  The `--target1-rel' and
-`--target1-abs' switches override the default.
+   The 'R_ARM_TARGET1' relocation is typically used for entries in the
+'.init_array' section.  It is interpreted as either 'R_ARM_REL32' or
+'R_ARM_ABS32', depending on the target.  The '--target1-rel' and
+'--target1-abs' switches override the default.
 
-   The `--target2=type' switch overrides the default definition of the
-`R_ARM_TARGET2' relocation.  Valid values for `type', their meanings,
+   The '--target2=type' switch overrides the default definition of the
+'R_ARM_TARGET2' relocation.  Valid values for 'type', their meanings,
 and target defaults are as follows:
-`rel'
-     `R_ARM_REL32' (arm*-*-elf, arm*-*-eabi)
-
-`abs'
-     `R_ARM_ABS32' (arm*-*-symbianelf)
-
-`got-rel'
-     `R_ARM_GOT_PREL' (arm*-*-linux, arm*-*-*bsd)
-
-   The `R_ARM_V4BX' relocation (defined by the ARM AAELF specification)
+'rel'
+     'R_ARM_REL32' (arm*-*-elf, arm*-*-eabi)
+'abs'
+     'R_ARM_ABS32' (arm*-*-symbianelf)
+'got-rel'
+     'R_ARM_GOT_PREL' (arm*-*-linux, arm*-*-*bsd)
+
+   The 'R_ARM_V4BX' relocation (defined by the ARM AAELF specification)
 enables objects compiled for the ARMv4 architecture to be
 interworking-safe when linked with other objects compiled for ARMv4t,
 but also allows pure ARMv4 binaries to be built from the same ARMv4
 objects.
 
-   In the latter case, the switch `--fix-v4bx' must be passed to the
-linker, which causes v4t `BX rM' instructions to be rewritten as `MOV
-PC,rM', since v4 processors do not have a `BX' instruction.
+   In the latter case, the switch '--fix-v4bx' must be passed to the
+linker, which causes v4t 'BX rM' instructions to be rewritten as 'MOV
+PC,rM', since v4 processors do not have a 'BX' instruction.
 
-   In the former case, the switch should not be used, and `R_ARM_V4BX'
+   In the former case, the switch should not be used, and 'R_ARM_V4BX'
 relocations are ignored.
 
-   Replace `BX rM' instructions identified by `R_ARM_V4BX' relocations
+   Replace 'BX rM' instructions identified by 'R_ARM_V4BX' relocations
 with a branch to the following veneer:
 
      TST rM, #1
@@ -5251,19 +5193,19 @@ with a branch to the following veneer:
 
    This allows generation of libraries/applications that work on ARMv4
 cores and are still interworking safe.  Note that the above veneer
-clobbers the condition flags, so may cause incorrect program behavior
-in rare cases.
+clobbers the condition flags, so may cause incorrect program behavior in
+rare cases.
 
-   The `--use-blx' switch enables the linker to use ARM/Thumb BLX
+   The '--use-blx' switch enables the linker to use ARM/Thumb BLX
 instructions (available on ARMv5t and above) in various situations.
 Currently it is used to perform calls via the PLT from Thumb code using
 BLX rather than using BX and a mode-switching stub before each PLT
-entry. This should lead to such calls executing slightly faster.
+entry.  This should lead to such calls executing slightly faster.
 
    This option is enabled implicitly for SymbianOS, so there is no need
 to specify it if you are using that target.
 
-   The `--vfp11-denorm-fix' switch enables a link-time workaround for a
+   The '--vfp11-denorm-fix' switch enables a link-time workaround for a
 bug in certain VFP11 coprocessor hardware, which sometimes allows
 instructions with denorm operands (which must be handled by support
 code) to have those operands overwritten by subsequent instructions
@@ -5272,74 +5214,74 @@ before the support code can read the intended values.
    The bug may be avoided in scalar mode if you allow at least one
 intervening instruction between a VFP11 instruction which uses a
 register and another instruction which writes to the same register, or
-at least two intervening instructions if vector mode is in use. The bug
+at least two intervening instructions if vector mode is in use.  The bug
 only affects full-compliance floating-point mode: you do not need this
-workaround if you are using "runfast" mode. Please contact ARM for
+workaround if you are using "runfast" mode.  Please contact ARM for
 further details.
 
    If you know you are using buggy VFP11 hardware, you can enable this
-workaround by specifying the linker option `--vfp-denorm-fix=scalar' if
-you are using the VFP11 scalar mode only, or `--vfp-denorm-fix=vector'
+workaround by specifying the linker option '--vfp-denorm-fix=scalar' if
+you are using the VFP11 scalar mode only, or '--vfp-denorm-fix=vector'
 if you are using vector mode (the latter also works for scalar code).
-The default is `--vfp-denorm-fix=none'.
+The default is '--vfp-denorm-fix=none'.
 
    If the workaround is enabled, instructions are scanned for
-potentially-troublesome sequences, and a veneer is created for each
-such sequence which may trigger the erratum. The veneer consists of the
+potentially-troublesome sequences, and a veneer is created for each such
+sequence which may trigger the erratum.  The veneer consists of the
 first instruction of the sequence and a branch back to the subsequent
-instruction. The original instruction is then replaced with a branch to
-the veneer. The extra cycles required to call and return from the veneer
-are sufficient to avoid the erratum in both the scalar and vector cases.
+instruction.  The original instruction is then replaced with a branch to
+the veneer.  The extra cycles required to call and return from the
+veneer are sufficient to avoid the erratum in both the scalar and vector
+cases.
 
-   The `--fix-arm1176' switch enables a link-time workaround for an
+   The '--fix-arm1176' switch enables a link-time workaround for an
 erratum in certain ARM1176 processors.  The workaround is enabled by
-default if you are targeting ARM v6 (excluding ARM v6T2) or earlier.
-It can be disabled unconditionally by specifying `--no-fix-arm1176'.
+default if you are targeting ARM v6 (excluding ARM v6T2) or earlier.  It
+can be disabled unconditionally by specifying '--no-fix-arm1176'.
 
    Further information is available in the "ARM1176JZ-S and ARM1176JZF-S
 Programmer Advice Notice" available on the ARM documentation website at:
 http://infocenter.arm.com/.
 
-   The `--no-enum-size-warning' switch prevents the linker from warning
+   The '--no-enum-size-warning' switch prevents the linker from warning
 when linking object files that specify incompatible EABI enumeration
 size attributes.  For example, with this switch enabled, linking of an
 object file using 32-bit enumeration values with another using
 enumeration values fitted into the smallest possible space will not be
 diagnosed.
 
-   The `--no-wchar-size-warning' switch prevents the linker from
-warning when linking object files that specify incompatible EABI
-`wchar_t' size attributes.  For example, with this switch enabled,
-linking of an object file using 32-bit `wchar_t' values with another
-using 16-bit `wchar_t' values will not be diagnosed.
+   The '--no-wchar-size-warning' switch prevents the linker from warning
+when linking object files that specify incompatible EABI 'wchar_t' size
+attributes.  For example, with this switch enabled, linking of an object
+file using 32-bit 'wchar_t' values with another using 16-bit 'wchar_t'
+values will not be diagnosed.
 
-   The `--pic-veneer' switch makes the linker use PIC sequences for
+   The '--pic-veneer' switch makes the linker use PIC sequences for
 ARM/Thumb interworking veneers, even if the rest of the binary is not
-PIC.  This avoids problems on uClinux targets where `--emit-relocs' is
+PIC. This avoids problems on uClinux targets where '--emit-relocs' is
 used to generate relocatable binaries.
 
    The linker will automatically generate and insert small sequences of
 code into a linked ARM ELF executable whenever an attempt is made to
-perform a function call to a symbol that is too far away.  The
-placement of these sequences of instructions - called stubs - is
-controlled by the command line option `--stub-group-size=N'.  The
-placement is important because a poor choice can create a need for
-duplicate stubs, increasing the code size.  The linker will try to
-group stubs together in order to reduce interruptions to the flow of
-code, but it needs guidance as to how big these groups should be and
-where they should be placed.
-
-   The value of `N', the parameter to the `--stub-group-size=' option
+perform a function call to a symbol that is too far away.  The placement
+of these sequences of instructions - called stubs - is controlled by the
+command line option '--stub-group-size=N'.  The placement is important
+because a poor choice can create a need for duplicate stubs, increasing
+the code size.  The linker will try to group stubs together in order to
+reduce interruptions to the flow of code, but it needs guidance as to
+how big these groups should be and where they should be placed.
+
+   The value of 'N', the parameter to the '--stub-group-size=' option
 controls where the stub groups are placed.  If it is negative then all
 stubs are placed after the first branch that needs them.  If it is
 positive then the stubs can be placed either before or after the
-branches that need them.  If the value of `N' is 1 (either +1 or -1)
+branches that need them.  If the value of 'N' is 1 (either +1 or -1)
 then the linker will choose exactly where to place groups of stubs,
-using its built in heuristics.  A value of `N' greater than 1 (or
+using its built in heuristics.  A value of 'N' greater than 1 (or
 smaller than -1) tells the linker that a single group of stubs can
-service at most `N' bytes from the input sections.
+service at most 'N' bytes from the input sections.
 
-   The default, if `--stub-group-size=' is not specified, is `N = +1'.
+   The default, if '--stub-group-size=' is not specified, is 'N = +1'.
 
    Farcalls stubs insertion is fully supported for the ARM-EABI target
 only, because it relies on object files properties not present
@@ -5348,74 +5290,87 @@ otherwise.
 
 File: ld.info,  Node: HPPA ELF32,  Next: M68K,  Prev: ARM,  Up: Machine Dependent
 
-4.5 `ld' and HPPA 32-bit ELF Support
+4.5 'ld' and HPPA 32-bit ELF Support
 ====================================
 
-When generating a shared library, `ld' will by default generate import
+When generating a shared library, 'ld' will by default generate import
 stubs suitable for use with a single sub-space application.  The
-`--multi-subspace' switch causes `ld' to generate export stubs, and
+'--multi-subspace' switch causes 'ld' to generate export stubs, and
 different (larger) import stubs suitable for use with multiple
 sub-spaces.
 
-   Long branch stubs and import/export stubs are placed by `ld' in stub
-sections located between groups of input sections.  `--stub-group-size'
+   Long branch stubs and import/export stubs are placed by 'ld' in stub
+sections located between groups of input sections.  '--stub-group-size'
 specifies the maximum size of a group of input sections handled by one
-stub section.  Since branch offsets are signed, a stub section may
-serve two groups of input sections, one group before the stub section,
-and one group after it.  However, when using conditional branches that
-require stubs, it may be better (for branch prediction) that stub
-sections only serve one group of input sections.  A negative value for
-`N' chooses this scheme, ensuring that branches to stubs always use a
-negative offset.  Two special values of `N' are recognized, `1' and
-`-1'.  These both instruct `ld' to automatically size input section
-groups for the branch types detected, with the same behaviour regarding
-stub placement as other positive or negative values of `N' respectively.
-
-   Note that `--stub-group-size' does not split input sections.  A
+stub section.  Since branch offsets are signed, a stub section may serve
+two groups of input sections, one group before the stub section, and one
+group after it.  However, when using conditional branches that require
+stubs, it may be better (for branch prediction) that stub sections only
+serve one group of input sections.  A negative value for 'N' chooses
+this scheme, ensuring that branches to stubs always use a negative
+offset.  Two special values of 'N' are recognized, '1' and '-1'.  These
+both instruct 'ld' to automatically size input section groups for the
+branch types detected, with the same behaviour regarding stub placement
+as other positive or negative values of 'N' respectively.
+
+   Note that '--stub-group-size' does not split input sections.  A
 single input section larger than the group size specified will of course
 create a larger group (of one section).  If input sections are too
 large, it may not be possible for a branch to reach its stub.
 
 
-File: ld.info,  Node: M68K,  Next: MMIX,  Prev: HPPA ELF32,  Up: Machine Dependent
+File: ld.info,  Node: M68K,  Next: MIPS,  Prev: HPPA ELF32,  Up: Machine Dependent
 
-4.6 `ld' and the Motorola 68K family
+4.6 'ld' and the Motorola 68K family
 ====================================
 
-The `--got=TYPE' option lets you choose the GOT generation scheme.  The
-choices are `single', `negative', `multigot' and `target'.  When
-`target' is selected the linker chooses the default GOT generation
-scheme for the current target.  `single' tells the linker to generate a
-single GOT with entries only at non-negative offsets.  `negative'
+The '--got=TYPE' option lets you choose the GOT generation scheme.  The
+choices are 'single', 'negative', 'multigot' and 'target'.  When
+'target' is selected the linker chooses the default GOT generation
+scheme for the current target.  'single' tells the linker to generate a
+single GOT with entries only at non-negative offsets.  'negative'
 instructs the linker to generate a single GOT with entries at both
 negative and positive offsets.  Not all environments support such GOTs.
-`multigot' allows the linker to generate several GOTs in the output
+'multigot' allows the linker to generate several GOTs in the output
 file.  All GOT references from a single input object file access the
 same GOT, but references from different input object files might access
 different GOTs.  Not all environments support such GOTs.
 
 
-File: ld.info,  Node: MMIX,  Next: MSP430,  Prev: M68K,  Up: Machine Dependent
+File: ld.info,  Node: MIPS,  Next: MMIX,  Prev: M68K,  Up: Machine Dependent
 
-4.7 `ld' and MMIX
+4.7 'ld' and the MIPS family
+============================
+
+The '--insn32' and '--no-insn32' options control the choice of microMIPS
+instructions used in code generated by the linker, such as that in the
+PLT or lazy binding stubs, or in relaxation.  If '--insn32' is used,
+then the linker only uses 32-bit instruction encodings.  By default or
+if '--no-insn32' is used, all instruction encodings are used, including
+16-bit ones where possible.
+
+
+File: ld.info,  Node: MMIX,  Next: MSP430,  Prev: MIPS,  Up: Machine Dependent
+
+4.8 'ld' and MMIX
 =================
 
-For MMIX, there is a choice of generating `ELF' object files or `mmo'
-object files when linking.  The simulator `mmix' understands the `mmo'
-format.  The binutils `objcopy' utility can translate between the two
+For MMIX, there is a choice of generating 'ELF' object files or 'mmo'
+object files when linking.  The simulator 'mmix' understands the 'mmo'
+format.  The binutils 'objcopy' utility can translate between the two
 formats.
 
-   There is one special section, the `.MMIX.reg_contents' section.
+   There is one special section, the '.MMIX.reg_contents' section.
 Contents in this section is assumed to correspond to that of global
 registers, and symbols referring to it are translated to special
 symbols, equal to registers.  In a final link, the start address of the
-`.MMIX.reg_contents' section corresponds to the first allocated global
-register multiplied by 8.  Register `$255' is not included in this
+'.MMIX.reg_contents' section corresponds to the first allocated global
+register multiplied by 8.  Register '$255' is not included in this
 section; it is always set to the program entry, which is at the symbol
-`Main' for `mmo' files.
+'Main' for 'mmo' files.
 
-   Global symbols with the prefix `__.MMIX.start.', for example
-`__.MMIX.start..text' and `__.MMIX.start..data' are special.  The
+   Global symbols with the prefix '__.MMIX.start.', for example
+'__.MMIX.start..text' and '__.MMIX.start..data' are special.  The
 default linker script uses these to set the default start address of a
 section.
 
@@ -5425,155 +5380,155 @@ section, are left out from an mmo file.
 
 File: ld.info,  Node: MSP430,  Next: PowerPC ELF32,  Prev: MMIX,  Up: Machine Dependent
 
-4.8 `ld' and MSP430
+4.9 'ld' and MSP430
 ===================
 
 For the MSP430 it is possible to select the MPU architecture.  The flag
-`-m [mpu type]' will select an appropriate linker script for selected
-MPU type.  (To get a list of known MPUs just pass `-m help' option to
+'-m [mpu type]' will select an appropriate linker script for selected
+MPU type.  (To get a list of known MPUs just pass '-m help' option to
 the linker).
 
    The linker will recognize some extra sections which are MSP430
 specific:
 
-``.vectors''
+''.vectors''
      Defines a portion of ROM where interrupt vectors located.
 
-``.bootloader''
+''.bootloader''
      Defines the bootloader portion of the ROM (if applicable).  Any
      code in this section will be uploaded to the MPU.
 
-``.infomem''
+''.infomem''
      Defines an information memory section (if applicable).  Any code in
      this section will be uploaded to the MPU.
 
-``.infomemnobits''
-     This is the same as the `.infomem' section except that any code in
+''.infomemnobits''
+     This is the same as the '.infomem' section except that any code in
      this section will not be uploaded to the MPU.
 
-``.noinit''
-     Denotes a portion of RAM located above `.bss' section.
+''.noinit''
+     Denotes a portion of RAM located above '.bss' section.
 
      The last two sections are used by gcc.
 
 
 File: ld.info,  Node: PowerPC ELF32,  Next: PowerPC64 ELF64,  Prev: MSP430,  Up: Machine Dependent
 
-4.9 `ld' and PowerPC 32-bit ELF Support
-=======================================
+4.10 'ld' and PowerPC 32-bit ELF Support
+========================================
 
 Branches on PowerPC processors are limited to a signed 26-bit
-displacement, which may result in `ld' giving `relocation truncated to
-fit' errors with very large programs.  `--relax' enables the generation
+displacement, which may result in 'ld' giving 'relocation truncated to
+fit' errors with very large programs.  '--relax' enables the generation
 of trampolines that can access the entire 32-bit address space.  These
-trampolines are inserted at section boundaries, so may not themselves
-be reachable if an input section exceeds 33M in size.  You may combine
-`-r' and `--relax' to add trampolines in a partial link.  In that case
-both branches to undefined symbols and inter-section branches are also
+trampolines are inserted at section boundaries, so may not themselves be
+reachable if an input section exceeds 33M in size.  You may combine '-r'
+and '--relax' to add trampolines in a partial link.  In that case both
+branches to undefined symbols and inter-section branches are also
 considered potentially out of range, and trampolines inserted.
 
-`--bss-plt'
-     Current PowerPC GCC accepts a `-msecure-plt' option that generates
+'--bss-plt'
+     Current PowerPC GCC accepts a '-msecure-plt' option that generates
      code capable of using a newer PLT and GOT layout that has the
      security advantage of no executable section ever needing to be
      writable and no writable section ever being executable.  PowerPC
-     `ld' will generate this layout, including stubs to access the PLT,
+     'ld' will generate this layout, including stubs to access the PLT,
      if all input files (including startup and static libraries) were
-     compiled with `-msecure-plt'.  `--bss-plt' forces the old BSS PLT
+     compiled with '-msecure-plt'.  '--bss-plt' forces the old BSS PLT
      (and GOT layout) which can give slightly better performance.
 
-`--secure-plt'
-     `ld' will use the new PLT and GOT layout if it is linking new
-     `-fpic' or `-fPIC' code, but does not do so automatically when
+'--secure-plt'
+     'ld' will use the new PLT and GOT layout if it is linking new
+     '-fpic' or '-fPIC' code, but does not do so automatically when
      linking non-PIC code.  This option requests the new PLT and GOT
      layout.  A warning will be given if some object file requires the
      old style BSS PLT.
 
-`--sdata-got'
+'--sdata-got'
      The new secure PLT and GOT are placed differently relative to other
-     sections compared to older BSS PLT and GOT placement.  The
-     location of `.plt' must change because the new secure PLT is an
-     initialized section while the old PLT is uninitialized.  The
-     reason for the `.got' change is more subtle:  The new placement
-     allows `.got' to be read-only in applications linked with `-z
-     relro -z now'.  However, this placement means that `.sdata' cannot
-     always be used in shared libraries, because the PowerPC ABI
-     accesses `.sdata' in shared libraries from the GOT pointer.
-     `--sdata-got' forces the old GOT placement.  PowerPC GCC doesn't
-     use `.sdata' in shared libraries, so this option is really only
-     useful for other compilers that may do so.
-
-`--emit-stub-syms'
-     This option causes `ld' to label linker stubs with a local symbol
+     sections compared to older BSS PLT and GOT placement.  The location
+     of '.plt' must change because the new secure PLT is an initialized
+     section while the old PLT is uninitialized.  The reason for the
+     '.got' change is more subtle: The new placement allows '.got' to be
+     read-only in applications linked with '-z relro -z now'.  However,
+     this placement means that '.sdata' cannot always be used in shared
+     libraries, because the PowerPC ABI accesses '.sdata' in shared
+     libraries from the GOT pointer.  '--sdata-got' forces the old GOT
+     placement.  PowerPC GCC doesn't use '.sdata' in shared libraries,
+     so this option is really only useful for other compilers that may
+     do so.
+
+'--emit-stub-syms'
+     This option causes 'ld' to label linker stubs with a local symbol
      that encodes the stub type and destination.
 
-`--no-tls-optimize'
-     PowerPC `ld' normally performs some optimization of code sequences
+'--no-tls-optimize'
+     PowerPC 'ld' normally performs some optimization of code sequences
      used to access Thread-Local Storage.  Use this option to disable
      the optimization.
 
 
 File: ld.info,  Node: PowerPC64 ELF64,  Next: SPU ELF,  Prev: PowerPC ELF32,  Up: Machine Dependent
 
-4.10 `ld' and PowerPC64 64-bit ELF Support
+4.11 'ld' and PowerPC64 64-bit ELF Support
 ==========================================
 
-`--stub-group-size'
-     Long branch stubs, PLT call stubs  and TOC adjusting stubs are
-     placed by `ld' in stub sections located between groups of input
-     sections.  `--stub-group-size' specifies the maximum size of a
+'--stub-group-size'
+     Long branch stubs, PLT call stubs and TOC adjusting stubs are
+     placed by 'ld' in stub sections located between groups of input
+     sections.  '--stub-group-size' specifies the maximum size of a
      group of input sections handled by one stub section.  Since branch
      offsets are signed, a stub section may serve two groups of input
      sections, one group before the stub section, and one group after
      it.  However, when using conditional branches that require stubs,
      it may be better (for branch prediction) that stub sections only
-     serve one group of input sections.  A negative value for `N'
+     serve one group of input sections.  A negative value for 'N'
      chooses this scheme, ensuring that branches to stubs always use a
-     negative offset.  Two special values of `N' are recognized, `1'
-     and `-1'.  These both instruct `ld' to automatically size input
-     section groups for the branch types detected, with the same
-     behaviour regarding stub placement as other positive or negative
-     values of `N' respectively.
+     negative offset.  Two special values of 'N' are recognized, '1' and
+     '-1'.  These both instruct 'ld' to automatically size input section
+     groups for the branch types detected, with the same behaviour
+     regarding stub placement as other positive or negative values of
+     'N' respectively.
 
-     Note that `--stub-group-size' does not split input sections.  A
+     Note that '--stub-group-size' does not split input sections.  A
      single input section larger than the group size specified will of
      course create a larger group (of one section).  If input sections
      are too large, it may not be possible for a branch to reach its
      stub.
 
-`--emit-stub-syms'
-     This option causes `ld' to label linker stubs with a local symbol
+'--emit-stub-syms'
+     This option causes 'ld' to label linker stubs with a local symbol
      that encodes the stub type and destination.
 
-`--dotsyms, --no-dotsyms'
-     These two options control how `ld' interprets version patterns in
-     a version script.  Older PowerPC64 compilers emitted both a
-     function descriptor symbol with the same name as the function, and
-     a code entry symbol with the name prefixed by a dot (`.').  To
-     properly version a function `foo', the version script thus needs
-     to control both `foo' and `.foo'.  The option `--dotsyms', on by
-     default, automatically adds the required dot-prefixed patterns.
-     Use `--no-dotsyms' to disable this feature.
-
-`--no-tls-optimize'
-     PowerPC64 `ld' normally performs some optimization of code
+'--dotsyms, --no-dotsyms'
+     These two options control how 'ld' interprets version patterns in a
+     version script.  Older PowerPC64 compilers emitted both a function
+     descriptor symbol with the same name as the function, and a code
+     entry symbol with the name prefixed by a dot ('.').  To properly
+     version a function 'foo', the version script thus needs to control
+     both 'foo' and '.foo'.  The option '--dotsyms', on by default,
+     automatically adds the required dot-prefixed patterns.  Use
+     '--no-dotsyms' to disable this feature.
+
+'--no-tls-optimize'
+     PowerPC64 'ld' normally performs some optimization of code
      sequences used to access Thread-Local Storage.  Use this option to
      disable the optimization.
 
-`--no-opd-optimize'
-     PowerPC64 `ld' normally removes `.opd' section entries
+'--no-opd-optimize'
+     PowerPC64 'ld' normally removes '.opd' section entries
      corresponding to deleted link-once functions, or functions removed
-     by the action of `--gc-sections' or linker script `/DISCARD/'.
-     Use this option to disable `.opd' optimization.
+     by the action of '--gc-sections' or linker script '/DISCARD/'.  Use
+     this option to disable '.opd' optimization.
 
-`--non-overlapping-opd'
+'--non-overlapping-opd'
      Some PowerPC64 compilers have an option to generate compressed
-     `.opd' entries spaced 16 bytes apart, overlapping the third word,
+     '.opd' entries spaced 16 bytes apart, overlapping the third word,
      the static chain pointer (unused in C) with the first word of the
      next entry.  This option expands such entries to the full 24 bytes.
 
-`--no-toc-optimize'
-     PowerPC64 `ld' normally removes unused `.toc' section entries.
+'--no-toc-optimize'
+     PowerPC64 'ld' normally removes unused '.toc' section entries.
      Such entries are detected by examining relocations that reference
      the TOC in code sections.  A reloc in a deleted code section marks
      a TOC word as unneeded, while a reloc in a kept code section marks
@@ -5586,128 +5541,128 @@ File: ld.info,  Node: PowerPC64 ELF64,  Next: SPU ELF,  Prev: PowerPC ELF32,  Up
      assembly code is used to insert TOC entries.  Use this option to
      disable the optimization.
 
-`--no-multi-toc'
-     If given any toc option besides `-mcmodel=medium' or
-     `-mcmodel=large', PowerPC64 GCC generates code for a TOC model
+'--no-multi-toc'
+     If given any toc option besides '-mcmodel=medium' or
+     '-mcmodel=large', PowerPC64 GCC generates code for a TOC model
      where TOC entries are accessed with a 16-bit offset from r2.  This
-     limits the total TOC size to 64K.  PowerPC64 `ld' extends this
-     limit by grouping code sections such that each group uses less
-     than 64K for its TOC entries, then inserts r2 adjusting stubs
-     between inter-group calls.  `ld' does not split apart input
-     sections, so cannot help if a single input file has a `.toc'
-     section that exceeds 64K, most likely from linking multiple files
-     with `ld -r'.  Use this option to turn off this feature.
-
-`--no-toc-sort'
-     By default, `ld' sorts TOC sections so that those whose file
-     happens to have a section called `.init' or `.fini' are placed
+     limits the total TOC size to 64K. PowerPC64 'ld' extends this limit
+     by grouping code sections such that each group uses less than 64K
+     for its TOC entries, then inserts r2 adjusting stubs between
+     inter-group calls.  'ld' does not split apart input sections, so
+     cannot help if a single input file has a '.toc' section that
+     exceeds 64K, most likely from linking multiple files with 'ld -r'.
+     Use this option to turn off this feature.
+
+'--no-toc-sort'
+     By default, 'ld' sorts TOC sections so that those whose file
+     happens to have a section called '.init' or '.fini' are placed
      first, followed by TOC sections referenced by code generated with
-     PowerPC64 gcc's `-mcmodel=small', and lastly TOC sections
+     PowerPC64 gcc's '-mcmodel=small', and lastly TOC sections
      referenced only by code generated with PowerPC64 gcc's
-     `-mcmodel=medium' or `-mcmodel=large' options.  Doing this results
-     in better TOC grouping for multi-TOC.  Use this option to turn off
+     '-mcmodel=medium' or '-mcmodel=large' options.  Doing this results
+     in better TOC grouping for multi-TOC. Use this option to turn off
      this feature.
 
-`--plt-align'
-`--no-plt-align'
+'--plt-align'
+'--no-plt-align'
      Use these options to control whether individual PLT call stubs are
      aligned to a 32-byte boundary, or to the specified power of two
-     boundary when using `--plt-align='.  By default PLT call stubs are
+     boundary when using '--plt-align='.  By default PLT call stubs are
      packed tightly.
 
-`--plt-static-chain'
-`--no-plt-static-chain'
+'--plt-static-chain'
+'--no-plt-static-chain'
      Use these options to control whether PLT call stubs load the static
-     chain pointer (r11).  `ld' defaults to not loading the static
-     chain since there is never any need to do so on a PLT call.
+     chain pointer (r11).  'ld' defaults to not loading the static chain
+     since there is never any need to do so on a PLT call.
 
-`--plt-thread-safe'
-`--no-thread-safe'
+'--plt-thread-safe'
+'--no-thread-safe'
      With power7's weakly ordered memory model, it is possible when
      using lazy binding for ld.so to update a plt entry in one thread
      and have another thread see the individual plt entry words update
      in the wrong order, despite ld.so carefully writing in the correct
      order and using memory write barriers.  To avoid this we need some
      sort of read barrier in the call stub, or use LD_BIND_NOW=1.  By
-     default, `ld' looks for calls to commonly used functions that
+     default, 'ld' looks for calls to commonly used functions that
      create threads, and if seen, adds the necessary barriers.  Use
      these options to change the default behaviour.
 
 
 File: ld.info,  Node: SPU ELF,  Next: TI COFF,  Prev: PowerPC64 ELF64,  Up: Machine Dependent
 
-4.11 `ld' and SPU ELF Support
+4.12 'ld' and SPU ELF Support
 =============================
 
-`--plugin'
+'--plugin'
      This option marks an executable as a PIC plugin module.
 
-`--no-overlays'
-     Normally, `ld' recognizes calls to functions within overlay
+'--no-overlays'
+     Normally, 'ld' recognizes calls to functions within overlay
      regions, and redirects such calls to an overlay manager via a stub.
-     `ld' also provides a built-in overlay manager.  This option turns
+     'ld' also provides a built-in overlay manager.  This option turns
      off all this special overlay handling.
 
-`--emit-stub-syms'
-     This option causes `ld' to label overlay stubs with a local symbol
+'--emit-stub-syms'
+     This option causes 'ld' to label overlay stubs with a local symbol
      that encodes the stub type and destination.
 
-`--extra-overlay-stubs'
-     This option causes `ld' to add overlay call stubs on all function
+'--extra-overlay-stubs'
+     This option causes 'ld' to add overlay call stubs on all function
      calls out of overlay regions.  Normally stubs are not added on
      calls to non-overlay regions.
 
-`--local-store=lo:hi'
-     `ld' usually checks that a final executable for SPU fits in the
+'--local-store=lo:hi'
+     'ld' usually checks that a final executable for SPU fits in the
      address range 0 to 256k.  This option may be used to change the
-     range.  Disable the check entirely with `--local-store=0:0'.
+     range.  Disable the check entirely with '--local-store=0:0'.
 
-`--stack-analysis'
+'--stack-analysis'
      SPU local store space is limited.  Over-allocation of stack space
      unnecessarily limits space available for code and data, while
      under-allocation results in runtime failures.  If given this
-     option, `ld' will provide an estimate of maximum stack usage.
-     `ld' does this by examining symbols in code sections to determine
-     the extents of functions, and looking at function prologues for
-     stack adjusting instructions.  A call-graph is created by looking
-     for relocations on branch instructions.  The graph is then searched
-     for the maximum stack usage path.  Note that this analysis does not
+     option, 'ld' will provide an estimate of maximum stack usage.  'ld'
+     does this by examining symbols in code sections to determine the
+     extents of functions, and looking at function prologues for stack
+     adjusting instructions.  A call-graph is created by looking for
+     relocations on branch instructions.  The graph is then searched for
+     the maximum stack usage path.  Note that this analysis does not
      find calls made via function pointers, and does not handle
      recursion and other cycles in the call graph.  Stack usage may be
      under-estimated if your code makes such calls.  Also, stack usage
-     for dynamic allocation, e.g. alloca, will not be detected.  If a
+     for dynamic allocation, e.g.  alloca, will not be detected.  If a
      link map is requested, detailed information about each function's
      stack usage and calls will be given.
 
-`--emit-stack-syms'
-     This option, if given along with `--stack-analysis' will result in
-     `ld' emitting stack sizing symbols for each function.  These take
-     the form `__stack_<function_name>' for global functions, and
-     `__stack_<number>_<function_name>' for static functions.
-     `<number>' is the section id in hex.  The value of such symbols is
+'--emit-stack-syms'
+     This option, if given along with '--stack-analysis' will result in
+     'ld' emitting stack sizing symbols for each function.  These take
+     the form '__stack_<function_name>' for global functions, and
+     '__stack_<number>_<function_name>' for static functions.
+     '<number>' is the section id in hex.  The value of such symbols is
      the stack requirement for the corresponding function.  The symbol
-     size will be zero, type `STT_NOTYPE', binding `STB_LOCAL', and
-     section `SHN_ABS'.
+     size will be zero, type 'STT_NOTYPE', binding 'STB_LOCAL', and
+     section 'SHN_ABS'.
 
 
 File: ld.info,  Node: TI COFF,  Next: WIN32,  Prev: SPU ELF,  Up: Machine Dependent
 
-4.12 `ld''s Support for Various TI COFF Versions
+4.13 'ld''s Support for Various TI COFF Versions
 ================================================
 
-The `--format' switch allows selection of one of the various TI COFF
+The '--format' switch allows selection of one of the various TI COFF
 versions.  The latest of this writing is 2; versions 0 and 1 are also
 supported.  The TI COFF versions also vary in header byte-order format;
-`ld' will read any version or byte order, but the output header format
+'ld' will read any version or byte order, but the output header format
 depends on the default specified by the specific target.
 
 
 File: ld.info,  Node: WIN32,  Next: Xtensa,  Prev: TI COFF,  Up: Machine Dependent
 
-4.13 `ld' and WIN32 (cygwin/mingw)
+4.14 'ld' and WIN32 (cygwin/mingw)
 ==================================
 
-This section describes some of the win32 specific `ld' issues.  See
+This section describes some of the win32 specific 'ld' issues.  See
 *note Command Line Options: Options. for detailed description of the
 command line options mentioned here.
 
@@ -5715,63 +5670,58 @@ _import libraries_
      The standard Windows linker creates and uses so-called import
      libraries, which contains information for linking to dll's.  They
      are regular static archives and are handled as any other static
-     archive.  The cygwin and mingw ports of `ld' have specific support
-     for creating such libraries provided with the `--out-implib'
+     archive.  The cygwin and mingw ports of 'ld' have specific support
+     for creating such libraries provided with the '--out-implib'
      command line option.
 
 _exporting DLL symbols_
-     The cygwin/mingw `ld' has several ways to export symbols for dll's.
+     The cygwin/mingw 'ld' has several ways to export symbols for dll's.
 
-    _using auto-export functionality_
-          By default `ld' exports symbols with the auto-export
+     _using auto-export functionality_
+          By default 'ld' exports symbols with the auto-export
           functionality, which is controlled by the following command
           line options:
 
-             * -export-all-symbols   [This is the default]
-
+             * -export-all-symbols [This is the default]
              * -exclude-symbols
-
              * -exclude-libs
-
              * -exclude-modules-for-implib
-
              * -version-script
 
-          When auto-export is in operation, `ld' will export all the
+          When auto-export is in operation, 'ld' will export all the
           non-local (global and common) symbols it finds in a DLL, with
-          the exception of a few symbols known to belong to the
-          system's runtime and libraries.  As it will often not be
-          desirable to export all of a DLL's symbols, which may include
-          private functions that are not part of any public interface,
-          the command-line options listed above may be used to filter
-          symbols out from the list for exporting.  The `--output-def'
+          the exception of a few symbols known to belong to the system's
+          runtime and libraries.  As it will often not be desirable to
+          export all of a DLL's symbols, which may include private
+          functions that are not part of any public interface, the
+          command-line options listed above may be used to filter
+          symbols out from the list for exporting.  The '--output-def'
           option can be used in order to see the final list of exported
           symbols with all exclusions taken into effect.
 
-          If `--export-all-symbols' is not given explicitly on the
+          If '--export-all-symbols' is not given explicitly on the
           command line, then the default auto-export behavior will be
           _disabled_ if either of the following are true:
 
              * A DEF file is used.
-
              * Any symbol in any object file was marked with the
                __declspec(dllexport) attribute.
 
-    _using a DEF file_
+     _using a DEF file_
           Another way of exporting symbols is using a DEF file.  A DEF
           file is an ASCII file containing definitions of symbols which
-          should be exported when a dll is created.  Usually it is
-          named `<dll name>.def' and is added as any other object file
-          to the linker's command line.  The file's name must end in
-          `.def' or `.DEF'.
+          should be exported when a dll is created.  Usually it is named
+          '<dll name>.def' and is added as any other object file to the
+          linker's command line.  The file's name must end in '.def' or
+          '.DEF'.
 
                gcc -o <output> <objectfiles> <dll name>.def
 
           Using a DEF file turns off the normal auto-export behavior,
-          unless the `--export-all-symbols' option is also used.
+          unless the '--export-all-symbols' option is also used.
 
           Here is an example of a DEF file for a shared library called
-          `xyz.dll':
+          'xyz.dll':
 
                LIBRARY "xyz.dll" BASE=0x20000000
 
@@ -5784,33 +5734,33 @@ _exporting DLL symbols_
                doo = foo == foo2
                eoo DATA == var1
 
-          This example defines a DLL with a non-default base address
-          and seven symbols in the export table. The third exported
-          symbol `_bar' is an alias for the second. The fourth symbol,
-          `another_foo' is resolved by "forwarding" to another module
-          and treating it as an alias for `afoo' exported from the DLL
-          `abc.dll'. The final symbol `var1' is declared to be a data
-          object. The `doo' symbol in export library is an alias of
-          `foo', which gets the string name in export table `foo2'. The
-          `eoo' symbol is an data export symbol, which gets in export
-          table the name `var1'.
-
-          The optional `LIBRARY <name>' command indicates the _internal_
-          name of the output DLL. If `<name>' does not include a suffix,
-          the default library suffix, `.DLL' is appended.
+          This example defines a DLL with a non-default base address and
+          seven symbols in the export table.  The third exported symbol
+          '_bar' is an alias for the second.  The fourth symbol,
+          'another_foo' is resolved by "forwarding" to another module
+          and treating it as an alias for 'afoo' exported from the DLL
+          'abc.dll'.  The final symbol 'var1' is declared to be a data
+          object.  The 'doo' symbol in export library is an alias of
+          'foo', which gets the string name in export table 'foo2'.  The
+          'eoo' symbol is an data export symbol, which gets in export
+          table the name 'var1'.
+
+          The optional 'LIBRARY <name>' command indicates the _internal_
+          name of the output DLL. If '<name>' does not include a suffix,
+          the default library suffix, '.DLL' is appended.
 
           When the .DEF file is used to build an application, rather
-          than a library, the `NAME <name>' command should be used
-          instead of `LIBRARY'. If `<name>' does not include a suffix,
-          the default executable suffix, `.EXE' is appended.
+          than a library, the 'NAME <name>' command should be used
+          instead of 'LIBRARY'.  If '<name>' does not include a suffix,
+          the default executable suffix, '.EXE' is appended.
 
-          With either `LIBRARY <name>' or `NAME <name>' the optional
-          specification `BASE = <number>' may be used to specify a
+          With either 'LIBRARY <name>' or 'NAME <name>' the optional
+          specification 'BASE = <number>' may be used to specify a
           non-default base address for the image.
 
-          If neither `LIBRARY <name>' nor  `NAME <name>' is specified,
-          or they specify an empty string, the internal name is the
-          same as the filename specified on the command line.
+          If neither 'LIBRARY <name>' nor 'NAME <name>' is specified, or
+          they specify an empty string, the internal name is the same as
+          the filename specified on the command line.
 
           The complete specification of an export symbol is:
 
@@ -5819,50 +5769,50 @@ _exporting DLL symbols_
                     | ( <name1> = <module-name> . <external-name>))
                  [ @ <integer> ] [NONAME] [DATA] [CONSTANT] [PRIVATE] [== <name3>] ) *
 
-          Declares `<name1>' as an exported symbol from the DLL, or
-          declares `<name1>' as an exported alias for `<name2>'; or
-          declares `<name1>' as a "forward" alias for the symbol
-          `<external-name>' in the DLL `<module-name>'.  Optionally,
-          the symbol may be exported by the specified ordinal
-          `<integer>' alias. The optional `<name3>' is the to be used
-          string in import/export table for the symbol.
+          Declares '<name1>' as an exported symbol from the DLL, or
+          declares '<name1>' as an exported alias for '<name2>'; or
+          declares '<name1>' as a "forward" alias for the symbol
+          '<external-name>' in the DLL '<module-name>'.  Optionally, the
+          symbol may be exported by the specified ordinal '<integer>'
+          alias.  The optional '<name3>' is the to be used string in
+          import/export table for the symbol.
 
           The optional keywords that follow the declaration indicate:
 
-          `NONAME': Do not put the symbol name in the DLL's export
-          table.  It will still be exported by its ordinal alias
-          (either the value specified by the .def specification or,
-          otherwise, the value assigned by the linker). The symbol
-          name, however, does remain visible in the import library (if
-          any), unless `PRIVATE' is also specified.
+          'NONAME': Do not put the symbol name in the DLL's export
+          table.  It will still be exported by its ordinal alias (either
+          the value specified by the .def specification or, otherwise,
+          the value assigned by the linker).  The symbol name, however,
+          does remain visible in the import library (if any), unless
+          'PRIVATE' is also specified.
 
-          `DATA': The symbol is a variable or object, rather than a
+          'DATA': The symbol is a variable or object, rather than a
           function.  The import lib will export only an indirect
-          reference to `foo' as the symbol `_imp__foo' (ie, `foo' must
-          be resolved as `*_imp__foo').
+          reference to 'foo' as the symbol '_imp__foo' (ie, 'foo' must
+          be resolved as '*_imp__foo').
 
-          `CONSTANT': Like `DATA', but put the undecorated `foo' as
-          well as `_imp__foo' into the import library. Both refer to the
+          'CONSTANT': Like 'DATA', but put the undecorated 'foo' as well
+          as '_imp__foo' into the import library.  Both refer to the
           read-only import address table's pointer to the variable, not
-          to the variable itself. This can be dangerous. If the user
-          code fails to add the `dllimport' attribute and also fails to
+          to the variable itself.  This can be dangerous.  If the user
+          code fails to add the 'dllimport' attribute and also fails to
           explicitly add the extra indirection that the use of the
           attribute enforces, the application will behave unexpectedly.
 
-          `PRIVATE': Put the symbol in the DLL's export table, but do
+          'PRIVATE': Put the symbol in the DLL's export table, but do
           not put it into the static import library used to resolve
-          imports at link time. The symbol can still be imported using
-          the `LoadLibrary/GetProcAddress' API at runtime or by by
-          using the GNU ld extension of linking directly to the DLL
-          without an import library.
+          imports at link time.  The symbol can still be imported using
+          the 'LoadLibrary/GetProcAddress' API at runtime or by by using
+          the GNU ld extension of linking directly to the DLL without an
+          import library.
 
           See ld/deffilep.y in the binutils sources for the full
           specification of other DEF file statements
 
-          While linking a shared dll, `ld' is able to create a DEF file
-          with the `--output-def <file>' command line option.
+          While linking a shared dll, 'ld' is able to create a DEF file
+          with the '--output-def <file>' command line option.
 
-    _Using decorations_
+     _Using decorations_
           Another way of marking symbols for export is to modify the
           source code itself, so that when building the DLL each symbol
           to be exported is declared as:
@@ -5870,11 +5820,10 @@ _exporting DLL symbols_
                __declspec(dllexport) int a_variable
                __declspec(dllexport) void a_function(int with_args)
 
-          All such symbols will be exported from the DLL.  If, however,
+          All such symbols will be exported from the DLL. If, however,
           any of the object files in the DLL contain symbols decorated
-          in this way, then the normal auto-export behavior is
-          disabled, unless the `--export-all-symbols' option is also
-          used.
+          in this way, then the normal auto-export behavior is disabled,
+          unless the '--export-all-symbols' option is also used.
 
           Note that object files that wish to access these symbols must
           _not_ decorate them with dllexport.  Instead, they should use
@@ -5889,31 +5838,31 @@ _exporting DLL symbols_
           included by client code the header must declare them as
           dllimport.  There are a number of idioms that are typically
           used to do this; often client code can omit the __declspec()
-          declaration completely.  See `--enable-auto-import' and
-          `automatic data imports' for more information.
+          declaration completely.  See '--enable-auto-import' and
+          'automatic data imports' for more information.
 
 _automatic data imports_
      The standard Windows dll format supports data imports from dlls
-     only by adding special decorations (dllimport/dllexport), which
-     let the compiler produce specific assembler instructions to deal
-     with this issue.  This increases the effort necessary to port
-     existing Un*x code to these platforms, especially for large c++
-     libraries and applications.  The auto-import feature, which was
-     initially provided by Paul Sokolovsky, allows one to omit the
-     decorations to achieve a behavior that conforms to that on
-     POSIX/Un*x platforms. This feature is enabled with the
-     `--enable-auto-import' command-line option, although it is enabled
-     by default on cygwin/mingw.  The `--enable-auto-import' option
-     itself now serves mainly to suppress any warnings that are
-     ordinarily emitted when linked objects trigger the feature's use.
+     only by adding special decorations (dllimport/dllexport), which let
+     the compiler produce specific assembler instructions to deal with
+     this issue.  This increases the effort necessary to port existing
+     Un*x code to these platforms, especially for large c++ libraries
+     and applications.  The auto-import feature, which was initially
+     provided by Paul Sokolovsky, allows one to omit the decorations to
+     achieve a behavior that conforms to that on POSIX/Un*x platforms.
+     This feature is enabled with the '--enable-auto-import'
+     command-line option, although it is enabled by default on
+     cygwin/mingw.  The '--enable-auto-import' option itself now serves
+     mainly to suppress any warnings that are ordinarily emitted when
+     linked objects trigger the feature's use.
 
      auto-import of variables does not always work flawlessly without
      additional assistance.  Sometimes, you will see this message
 
-     "variable '<var>' can't be auto-imported. Please read the
-     documentation for ld's `--enable-auto-import' for details."
+     "variable '<var>' can't be auto-imported.  Please read the
+     documentation for ld's '--enable-auto-import' for details."
 
-     The `--enable-auto-import' documentation explains why this error
+     The '--enable-auto-import' documentation explains why this error
      occurs, and several methods that can be used to overcome this
      difficulty.  One of these methods is the _runtime pseudo-relocs_
      feature, described below.
@@ -5928,38 +5877,38 @@ _automatic data imports_
      standard auto-import feature described above is unable to resolve
      these references.
 
-     The `--enable-runtime-pseudo-relocs' switch allows these
-     references to be resolved without error, while leaving the task of
-     adjusting the references themselves (with their non-zero addends)
-     to specialized code provided by the runtime environment.  Recent
-     versions of the cygwin and mingw environments and compilers
-     provide this runtime support; older versions do not.  However, the
-     support is only necessary on the developer's platform; the
-     compiled result will run without error on an older system.
+     The '--enable-runtime-pseudo-relocs' switch allows these references
+     to be resolved without error, while leaving the task of adjusting
+     the references themselves (with their non-zero addends) to
+     specialized code provided by the runtime environment.  Recent
+     versions of the cygwin and mingw environments and compilers provide
+     this runtime support; older versions do not.  However, the support
+     is only necessary on the developer's platform; the compiled result
+     will run without error on an older system.
 
-     `--enable-runtime-pseudo-relocs' is not the default; it must be
+     '--enable-runtime-pseudo-relocs' is not the default; it must be
      explicitly enabled as needed.
 
 _direct linking to a dll_
-     The cygwin/mingw ports of `ld' support the direct linking,
+     The cygwin/mingw ports of 'ld' support the direct linking,
      including data symbols, to a dll without the usage of any import
-     libraries.  This is much faster and uses much less memory than
-     does the traditional import library method, especially when
-     linking large libraries or applications.  When `ld' creates an
-     import lib, each function or variable exported from the dll is
-     stored in its own bfd, even though a single bfd could contain many
-     exports.  The overhead involved in storing, loading, and
-     processing so many bfd's is quite large, and explains the
-     tremendous time, memory, and storage needed to link against
-     particularly large or complex libraries when using import libs.
-
-     Linking directly to a dll uses no extra command-line switches
-     other than `-L' and `-l', because `ld' already searches for a
-     number of names to match each library.  All that is needed from
-     the developer's perspective is an understanding of this search, in
+     libraries.  This is much faster and uses much less memory than does
+     the traditional import library method, especially when linking
+     large libraries or applications.  When 'ld' creates an import lib,
+     each function or variable exported from the dll is stored in its
+     own bfd, even though a single bfd could contain many exports.  The
+     overhead involved in storing, loading, and processing so many bfd's
+     is quite large, and explains the tremendous time, memory, and
+     storage needed to link against particularly large or complex
+     libraries when using import libs.
+
+     Linking directly to a dll uses no extra command-line switches other
+     than '-L' and '-l', because 'ld' already searches for a number of
+     names to match each library.  All that is needed from the
+     developer's perspective is an understanding of this search, in
      order to force ld to select the dll instead of an import library.
 
-     For instance, when ld is called with the argument `-lxxx' it will
+     For instance, when ld is called with the argument '-lxxx' it will
      attempt to find, in the first directory of its search path,
 
           libxxx.dll.a
@@ -5972,21 +5921,21 @@ _direct linking to a dll_
 
      before moving on to the next directory in the search path.
 
-     (*) Actually, this is not `cygxxx.dll' but in fact is
-     `<prefix>xxx.dll', where `<prefix>' is set by the `ld' option
-     `--dll-search-prefix=<prefix>'. In the case of cygwin, the
-     standard gcc spec file includes `--dll-search-prefix=cyg', so in
-     effect we actually search for `cygxxx.dll'.
+     (*) Actually, this is not 'cygxxx.dll' but in fact is
+     '<prefix>xxx.dll', where '<prefix>' is set by the 'ld' option
+     '--dll-search-prefix=<prefix>'.  In the case of cygwin, the
+     standard gcc spec file includes '--dll-search-prefix=cyg', so in
+     effect we actually search for 'cygxxx.dll'.
 
-     Other win32-based unix environments, such as mingw or pw32, may
-     use other `<prefix>'es, although at present only cygwin makes use
-     of this feature.  It was originally intended to help avoid name
+     Other win32-based unix environments, such as mingw or pw32, may use
+     other '<prefix>'es, although at present only cygwin makes use of
+     this feature.  It was originally intended to help avoid name
      conflicts among dll's built for the various win32/un*x
      environments, so that (for example) two versions of a zlib dll
      could coexist on the same machine.
 
-     The generic cygwin/mingw path layout uses a `bin' directory for
-     applications and dll's and a `lib' directory for the import
+     The generic cygwin/mingw path layout uses a 'bin' directory for
+     applications and dll's and a 'lib' directory for the import
      libraries (using cygwin nomenclature):
 
           bin/
@@ -5998,15 +5947,15 @@ _direct linking to a dll_
      Linking directly to a dll without using the import library can be
      done two ways:
 
-     1. Use the dll directly by adding the `bin' path to the link line
+     1.  Use the dll directly by adding the 'bin' path to the link line
           gcc -Wl,-verbose  -o a.exe -L../bin/ -lxxx
 
      However, as the dll's often have version numbers appended to their
-     names (`cygncurses-5.dll') this will often fail, unless one
-     specifies `-L../bin -lncurses-5' to include the version.  Import
+     names ('cygncurses-5.dll') this will often fail, unless one
+     specifies '-L../bin -lncurses-5' to include the version.  Import
      libs are generally not versioned, and do not have this difficulty.
 
-     2. Create a symbolic link from the dll to a file in the `lib'
+     2.  Create a symbolic link from the dll to a file in the 'lib'
      directory according to the above mentioned search pattern.  This
      should be used to avoid unwanted changes in the tools needed for
      making the app/dll.
@@ -6017,8 +5966,8 @@ _direct linking to a dll_
 
           gcc -Wl,-verbose  -o a.exe -L../lib/ -lxxx
 
-     This technique also avoids the version number problems, because
-     the following is perfectly legal
+     This technique also avoids the version number problems, because the
+     following is perfectly legal
 
           bin/
           	cygxxx-5.dll
@@ -6027,22 +5976,22 @@ _direct linking to a dll_
 
      Linking directly to a dll without using an import lib will work
      even when auto-import features are exercised, and even when
-     `--enable-runtime-pseudo-relocs' is used.
+     '--enable-runtime-pseudo-relocs' is used.
 
      Given the improvements in speed and memory usage, one might
-     justifiably wonder why import libraries are used at all.  There
-     are three reasons:
+     justifiably wonder why import libraries are used at all.  There are
+     three reasons:
 
-     1. Until recently, the link-directly-to-dll functionality did _not_
-     work with auto-imported data.
+     1.  Until recently, the link-directly-to-dll functionality did
+     _not_ work with auto-imported data.
 
-     2. Sometimes it is necessary to include pure static objects within
+     2.  Sometimes it is necessary to include pure static objects within
      the import library (which otherwise contains only bfd's for
      indirection symbols that point to the exports of a dll).  Again,
-     the import lib for the cygwin kernel makes use of this ability,
-     and it is not possible to do this without an import lib.
+     the import lib for the cygwin kernel makes use of this ability, and
+     it is not possible to do this without an import lib.
 
-     3. Symbol aliases can only be resolved using an import lib.  This
+     3.  Symbol aliases can only be resolved using an import lib.  This
      is critical when linking against OS-supplied dll's (eg, the win32
      API) in which symbols are usually exported as undecorated aliases
      of their stdcall-decorated assembly names.
@@ -6050,17 +5999,16 @@ _direct linking to a dll_
      So, import libs are not going away.  But the ability to replace
      true import libs with a simple symbolic link to (or a copy of) a
      dll, in many cases, is a useful addition to the suite of tools
-     binutils makes available to the win32 developer.  Given the
-     massive improvements in memory requirements during linking, storage
+     binutils makes available to the win32 developer.  Given the massive
+     improvements in memory requirements during linking, storage
      requirements, and linking speed, we expect that many developers
      will soon begin to use this feature whenever possible.
 
 _symbol aliasing_
-
-    _adding additional names_
+     _adding additional names_
           Sometimes, it is useful to export symbols with additional
-          names.  A symbol `foo' will be exported as `foo', but it can
-          also be exported as `_foo' by using special directives in the
+          names.  A symbol 'foo' will be exported as 'foo', but it can
+          also be exported as '_foo' by using special directives in the
           DEF file when creating the dll.  This will affect also the
           optional created import library.  Consider the following DEF
           file:
@@ -6071,7 +6019,7 @@ _symbol aliasing_
                foo
                _foo = foo
 
-          The line `_foo = foo' maps the symbol `foo' to `_foo'.
+          The line '_foo = foo' maps the symbol 'foo' to '_foo'.
 
           Another method for creating a symbol alias is to create it in
           the source code using the "weak" attribute:
@@ -6082,11 +6030,11 @@ _symbol aliasing_
           See the gcc manual for more information about attributes and
           weak symbols.
 
-    _renaming symbols_
+     _renaming symbols_
           Sometimes it is useful to rename exports.  For instance, the
-          cygwin kernel does this regularly.  A symbol `_foo' can be
-          exported as `foo' but not as `_foo' by using special
-          directives in the DEF file. (This will also affect the import
+          cygwin kernel does this regularly.  A symbol '_foo' can be
+          exported as 'foo' but not as '_foo' by using special
+          directives in the DEF file.  (This will also affect the import
           library, if it is created).  In the following example:
 
                LIBRARY "xyz.dll" BASE=0x61000000
@@ -6094,56 +6042,54 @@ _symbol aliasing_
                EXPORTS
                _foo = foo
 
-          The line `_foo = foo' maps the exported symbol `foo' to
-          `_foo'.
+          The line '_foo = foo' maps the exported symbol 'foo' to
+          '_foo'.
 
      Note: using a DEF file disables the default auto-export behavior,
-     unless the `--export-all-symbols' command line option is used.
-     If, however, you are trying to rename symbols, then you should list
+     unless the '--export-all-symbols' command line option is used.  If,
+     however, you are trying to rename symbols, then you should list
      _all_ desired exports in the DEF file, including the symbols that
-     are not being renamed, and do _not_ use the `--export-all-symbols'
+     are not being renamed, and do _not_ use the '--export-all-symbols'
      option.  If you list only the renamed symbols in the DEF file, and
-     use `--export-all-symbols' to handle the other symbols, then the
-     both the new names _and_ the original names for the renamed
-     symbols will be exported.  In effect, you'd be aliasing those
-     symbols, not renaming them, which is probably not what you wanted.
+     use '--export-all-symbols' to handle the other symbols, then the
+     both the new names _and_ the original names for the renamed symbols
+     will be exported.  In effect, you'd be aliasing those symbols, not
+     renaming them, which is probably not what you wanted.
 
 _weak externals_
      The Windows object format, PE, specifies a form of weak symbols
-     called weak externals.  When a weak symbol is linked and the
-     symbol is not defined, the weak symbol becomes an alias for some
-     other symbol.  There are three variants of weak externals:
+     called weak externals.  When a weak symbol is linked and the symbol
+     is not defined, the weak symbol becomes an alias for some other
+     symbol.  There are three variants of weak externals:
         * Definition is searched for in objects and libraries,
           historically called lazy externals.
-
         * Definition is searched for only in other objects, not in
           libraries.  This form is not presently implemented.
-
         * No search; the symbol is an alias.  This form is not presently
           implemented.
      As a GNU extension, weak symbols that do not specify an alternate
-     symbol are supported.  If the symbol is undefined when linking,
-     the symbol uses a default value.
+     symbol are supported.  If the symbol is undefined when linking, the
+     symbol uses a default value.
 
 _aligned common symbols_
-     As a GNU extension to the PE file format, it is possible to
-     specify the desired alignment for a common symbol.  This
-     information is conveyed from the assembler or compiler to the
-     linker by means of GNU-specific commands carried in the object
-     file's `.drectve' section, which are recognized by `ld' and
-     respected when laying out the common symbols.  Native tools will
-     be able to process object files employing this GNU extension, but
-     will fail to respect the alignment instructions, and may issue
-     noisy warnings about unknown linker directives.
+     As a GNU extension to the PE file format, it is possible to specify
+     the desired alignment for a common symbol.  This information is
+     conveyed from the assembler or compiler to the linker by means of
+     GNU-specific commands carried in the object file's '.drectve'
+     section, which are recognized by 'ld' and respected when laying out
+     the common symbols.  Native tools will be able to process object
+     files employing this GNU extension, but will fail to respect the
+     alignment instructions, and may issue noisy warnings about unknown
+     linker directives.
 
 
 File: ld.info,  Node: Xtensa,  Prev: WIN32,  Up: Machine Dependent
 
-4.14 `ld' and Xtensa Processors
+4.15 'ld' and Xtensa Processors
 ===============================
 
-The default `ld' behavior for Xtensa processors is to interpret
-`SECTIONS' commands so that lists of explicitly named sections in a
+The default 'ld' behavior for Xtensa processors is to interpret
+'SECTIONS' commands so that lists of explicitly named sections in a
 specification with a wildcard file will be interleaved when necessary to
 keep literal pools within the range of PC-relative load offsets.  For
 example, with the command:
@@ -6155,44 +6101,43 @@ example, with the command:
        }
      }
 
-`ld' may interleave some of the `.literal' and `.text' sections from
+'ld' may interleave some of the '.literal' and '.text' sections from
 different object files to ensure that the literal pools are within the
-range of PC-relative load offsets.  A valid interleaving might place
-the `.literal' sections from an initial group of files followed by the
-`.text' sections of that group of files.  Then, the `.literal' sections
-from the rest of the files and the `.text' sections from the rest of
-the files would follow.
+range of PC-relative load offsets.  A valid interleaving might place the
+'.literal' sections from an initial group of files followed by the
+'.text' sections of that group of files.  Then, the '.literal' sections
+from the rest of the files and the '.text' sections from the rest of the
+files would follow.
 
-   Relaxation is enabled by default for the Xtensa version of `ld' and
+   Relaxation is enabled by default for the Xtensa version of 'ld' and
 provides two important link-time optimizations.  The first optimization
 is to combine identical literal values to reduce code size.  A redundant
-literal will be removed and all the `L32R' instructions that use it
-will be changed to reference an identical literal, as long as the
-location of the replacement literal is within the offset range of all
-the `L32R' instructions.  The second optimization is to remove
-unnecessary overhead from assembler-generated "longcall" sequences of
-`L32R'/`CALLXN' when the target functions are within range of direct
-`CALLN' instructions.
+literal will be removed and all the 'L32R' instructions that use it will
+be changed to reference an identical literal, as long as the location of
+the replacement literal is within the offset range of all the 'L32R'
+instructions.  The second optimization is to remove unnecessary overhead
+from assembler-generated "longcall" sequences of 'L32R'/'CALLXN' when
+the target functions are within range of direct 'CALLN' instructions.
 
    For each of these cases where an indirect call sequence can be
-optimized to a direct call, the linker will change the `CALLXN'
-instruction to a `CALLN' instruction, remove the `L32R' instruction,
-and remove the literal referenced by the `L32R' instruction if it is
-not used for anything else.  Removing the `L32R' instruction always
-reduces code size but can potentially hurt performance by changing the
-alignment of subsequent branch targets.  By default, the linker will
-always preserve alignments, either by switching some instructions
-between 24-bit encodings and the equivalent density instructions or by
-inserting a no-op in place of the `L32R' instruction that was removed.
-If code size is more important than performance, the `--size-opt'
-option can be used to prevent the linker from widening density
-instructions or inserting no-ops, except in a few cases where no-ops
-are required for correctness.
+optimized to a direct call, the linker will change the 'CALLXN'
+instruction to a 'CALLN' instruction, remove the 'L32R' instruction, and
+remove the literal referenced by the 'L32R' instruction if it is not
+used for anything else.  Removing the 'L32R' instruction always reduces
+code size but can potentially hurt performance by changing the alignment
+of subsequent branch targets.  By default, the linker will always
+preserve alignments, either by switching some instructions between
+24-bit encodings and the equivalent density instructions or by inserting
+a no-op in place of the 'L32R' instruction that was removed.  If code
+size is more important than performance, the '--size-opt' option can be
+used to prevent the linker from widening density instructions or
+inserting no-ops, except in a few cases where no-ops are required for
+correctness.
 
    The following Xtensa-specific command-line options can be used to
 control the linker:
 
-`--size-opt'
+'--size-opt'
      When optimizing indirect calls to direct calls, optimize for code
      size more than performance.  With this option, the linker will not
      insert no-ops or widen density instructions to preserve branch
@@ -6211,22 +6156,22 @@ object files whatever the object file format.  A different object file
 format can be supported simply by creating a new BFD back end and adding
 it to the library.  To conserve runtime memory, however, the linker and
 associated tools are usually configured to support only a subset of the
-object file formats available.  You can use `objdump -i' (*note
-objdump: (binutils.info)objdump.) to list all the formats available for
-your configuration.
+object file formats available.  You can use 'objdump -i' (*note objdump:
+(binutils.info)objdump.) to list all the formats available for your
+configuration.
 
    As with most implementations, BFD is a compromise between several
-conflicting requirements. The major factor influencing BFD design was
-efficiency: any time used converting between formats is time which
-would not have been spent had BFD not been involved. This is partly
-offset by abstraction payback; since BFD simplifies applications and
-back ends, more time and care may be spent optimizing algorithms for a
-greater speed.
+conflicting requirements.  The major factor influencing BFD design was
+efficiency: any time used converting between formats is time which would
+not have been spent had BFD not been involved.  This is partly offset by
+abstraction payback; since BFD simplifies applications and back ends,
+more time and care may be spent optimizing algorithms for a greater
+speed.
 
    One minor artifact of the BFD solution which you should bear in mind
 is the potential for information loss.  There are two places where
 useful information can be lost using the BFD mechanism: during
-conversion and during output. *Note BFD information loss::.
+conversion and during output.  *Note BFD information loss::.
 
 * Menu:
 
@@ -6243,18 +6188,18 @@ the format of the input object file.  They then build a descriptor in
 memory with pointers to routines that will be used to access elements of
 the object file's data structures.
 
-   As different information from the object files is required, BFD
-reads from different sections of the file and processes them.  For
-example, a very common operation for the linker is processing symbol
-tables.  Each BFD back end provides a routine for converting between
-the object file's representation of symbols and an internal canonical
-format. When the linker asks for the symbol table of an object file, it
-calls through a memory pointer to the routine from the relevant BFD
-back end which reads and converts the table into a canonical form.  The
-linker then operates upon the canonical form. When the link is finished
-and the linker writes the output file's symbol table, another BFD back
-end routine is called to take the newly created symbol table and
-convert it into the chosen output format.
+   As different information from the object files is required, BFD reads
+from different sections of the file and processes them.  For example, a
+very common operation for the linker is processing symbol tables.  Each
+BFD back end provides a routine for converting between the object file's
+representation of symbols and an internal canonical format.  When the
+linker asks for the symbol table of an object file, it calls through a
+memory pointer to the routine from the relevant BFD back end which reads
+and converts the table into a canonical form.  The linker then operates
+upon the canonical form.  When the link is finished and the linker
+writes the output file's symbol table, another BFD back end routine is
+called to take the newly created symbol table and convert it into the
+chosen output format.
 
 * Menu:
 
@@ -6267,25 +6212,25 @@ File: ld.info,  Node: BFD information loss,  Next: Canonical format,  Up: BFD ou
 5.1.1 Information Loss
 ----------------------
 
-_Information can be lost during output._ The output formats supported
-by BFD do not provide identical facilities, and information which can
-be described in one form has nowhere to go in another format. One
-example of this is alignment information in `b.out'. There is nowhere
-in an `a.out' format file to store alignment information on the
-contained data, so when a file is linked from `b.out' and an `a.out'
-image is produced, alignment information will not propagate to the
-output file. (The linker will still use the alignment information
-internally, so the link is performed correctly).
-
-   Another example is COFF section names. COFF files may contain an
-unlimited number of sections, each one with a textual section name. If
+_Information can be lost during output._  The output formats supported
+by BFD do not provide identical facilities, and information which can be
+described in one form has nowhere to go in another format.  One example
+of this is alignment information in 'b.out'.  There is nowhere in an
+'a.out' format file to store alignment information on the contained
+data, so when a file is linked from 'b.out' and an 'a.out' image is
+produced, alignment information will not propagate to the output file.
+(The linker will still use the alignment information internally, so the
+link is performed correctly).
+
+   Another example is COFF section names.  COFF files may contain an
+unlimited number of sections, each one with a textual section name.  If
 the target of the link is a format which does not have many sections
-(e.g., `a.out') or has sections without names (e.g., the Oasys format),
-the link cannot be done simply. You can circumvent this problem by
+(e.g., 'a.out') or has sections without names (e.g., the Oasys format),
+the link cannot be done simply.  You can circumvent this problem by
 describing the desired input-to-output section mapping with the linker
 command language.
 
-   _Information can be lost during canonicalization._ The BFD internal
+   _Information can be lost during canonicalization._  The BFD internal
 canonical form of the external formats is not exhaustive; there are
 structures in input formats for which there is no direct representation
 internally.  This means that the BFD back ends cannot maintain all
@@ -6296,16 +6241,16 @@ internal and back to external formats.
 format and writes another.  Each BFD back end is responsible for
 maintaining as much data as possible, and the internal BFD canonical
 form has structures which are opaque to the BFD core, and exported only
-to the back ends. When a file is read in one format, the canonical form
-is generated for BFD and the application. At the same time, the back
-end saves away any information which may otherwise be lost. If the data
+to the back ends.  When a file is read in one format, the canonical form
+is generated for BFD and the application.  At the same time, the back
+end saves away any information which may otherwise be lost.  If the data
 is then written back in the same format, the back end routine will be
 able to use the canonical form provided by the BFD core as well as the
 information it prepared earlier.  Since there is a great deal of
-commonality between back ends, there is no information lost when
-linking or copying big endian COFF to little endian COFF, or `a.out' to
-`b.out'.  When a mixture of formats is linked, the information is only
-lost from the files whose format differs from the destination.
+commonality between back ends, there is no information lost when linking
+or copying big endian COFF to little endian COFF, or 'a.out' to 'b.out'.
+When a mixture of formats is linked, the information is only lost from
+the files whose format differs from the destination.
 
 
 File: ld.info,  Node: Canonical format,  Prev: BFD information loss,  Up: BFD outline
@@ -6316,16 +6261,16 @@ File: ld.info,  Node: Canonical format,  Prev: BFD information loss,  Up: BFD ou
 The greatest potential for loss of information occurs when there is the
 least overlap between the information provided by the source format,
 that stored by the canonical format, and that needed by the destination
-format. A brief description of the canonical form may help you
+format.  A brief description of the canonical form may help you
 understand which kinds of data you can count on preserving across
-conversions.  
+conversions.
 
 _files_
      Information stored on a per-file basis includes target machine
      architecture, particular implementation format type, a demand
      pageable bit, and a write protected bit.  Information like Unix
      magic numbers is not stored here--only the magic numbers' meaning,
-     so a `ZMAGIC' file would have both the demand pageable bit and the
+     so a 'ZMAGIC' file would have both the demand pageable bit and the
      write protected text bit set.  The byte order of the target is
      stored on a per-file basis, so that big- and little-endian object
      files may be used with one another.
@@ -6344,14 +6289,14 @@ _symbols_
      section where they were defined.  Doing this ensures that each
      symbol points to its containing section.  Each symbol also has a
      varying amount of hidden private data for the BFD back end.  Since
-     the symbol points to the original file, the private data format
-     for that symbol is accessible.  `ld' can operate on a collection
-     of symbols of wildly different formats without problems.
-
-     Normal global and simple local symbols are maintained on output,
-     so an output file (no matter its format) will retain symbols
-     pointing to functions and to global, static, and common variables.
-     Some symbol information is not worth retaining; in `a.out', type
+     the symbol points to the original file, the private data format for
+     that symbol is accessible.  'ld' can operate on a collection of
+     symbols of wildly different formats without problems.
+
+     Normal global and simple local symbols are maintained on output, so
+     an output file (no matter its format) will retain symbols pointing
+     to functions and to global, static, and common variables.  Some
+     symbol information is not worth retaining; in 'a.out', type
      information is stored in the symbol table as long symbol names.
      This information would be useless to most COFF debuggers; the
      linker has command line switches to allow users to throw it away.
@@ -6359,17 +6304,17 @@ _symbols_
      There is one word of type information within the symbol, so if the
      format supports symbol type information within symbols (for
      example, COFF, IEEE, Oasys) and the type is simple enough to fit
-     within one word (nearly everything but aggregates), the
-     information will be preserved.
+     within one word (nearly everything but aggregates), the information
+     will be preserved.
 
 _relocation level_
      Each canonical BFD relocation record contains a pointer to the
      symbol to relocate to, the offset of the data to relocate, the
      section the data is in, and a pointer to a relocation type
-     descriptor. Relocation is performed by passing messages through
-     the relocation type descriptor and the symbol pointer. Therefore,
+     descriptor.  Relocation is performed by passing messages through
+     the relocation type descriptor and the symbol pointer.  Therefore,
      relocations can be performed on output data using a relocation
-     method that is only available in one of the input formats. For
+     method that is only available in one of the input formats.  For
      instance, Oasys provides a byte relocation format.  A relocation
      record requesting this relocation type would point indirectly to a
      routine to perform this, so the relocation may be performed on a
@@ -6381,13 +6326,13 @@ _line numbers_
      mapping between symbols, source line numbers, and addresses in the
      output file.  These addresses have to be relocated along with the
      symbol information.  Each symbol with an associated list of line
-     number records points to the first record of the list.  The head
-     of a line number list consists of a pointer to the symbol, which
-     allows finding out the address of the function whose line number
-     is being described. The rest of the list is made up of pairs:
-     offsets into the section and line numbers. Any format which can
-     simply derive this information can pass it successfully between
-     formats (COFF, IEEE and Oasys).
+     number records points to the first record of the list.  The head of
+     a line number list consists of a pointer to the symbol, which
+     allows finding out the address of the function whose line number is
+     being described.  The rest of the list is made up of pairs: offsets
+     into the section and line numbers.  Any format which can simply
+     derive this information can pass it successfully between formats
+     (COFF, IEEE and Oasys).
 
 
 File: ld.info,  Node: Reporting Bugs,  Next: MRI,  Prev: BFD,  Up: Top
@@ -6395,12 +6340,12 @@ File: ld.info,  Node: Reporting Bugs,  Next: MRI,  Prev: BFD,  Up: Top
 6 Reporting Bugs
 ****************
 
-Your bug reports play an essential role in making `ld' reliable.
+Your bug reports play an essential role in making 'ld' reliable.
 
    Reporting a bug may help you by bringing a solution to your problem,
 or it may not.  But in any case the principal function of a bug report
-is to help the entire community by making the next version of `ld' work
-better.  Bug reports are your contribution to the maintenance of `ld'.
+is to help the entire community by making the next version of 'ld' work
+better.  Bug reports are your contribution to the maintenance of 'ld'.
 
    In order for a bug report to serve its purpose, you must include the
 information that enables us to fix the bug.
@@ -6420,16 +6365,16 @@ If you are not sure whether you have found a bug, here are some
 guidelines:
 
    * If the linker gets a fatal signal, for any input whatever, that is
-     a `ld' bug.  Reliable linkers never crash.
+     a 'ld' bug.  Reliable linkers never crash.
 
-   * If `ld' produces an error message for valid input, that is a bug.
+   * If 'ld' produces an error message for valid input, that is a bug.
 
-   * If `ld' does not produce an error message for invalid input, that
+   * If 'ld' does not produce an error message for invalid input, that
      may be a bug.  In the general case, the linker can not verify that
      object files are correct.
 
    * If you are an experienced user of linkers, your suggestions for
-     improvement of `ld' are welcome in any case.
+     improvement of 'ld' are welcome in any case.
 
 
 File: ld.info,  Node: Bug Reporting,  Prev: Bug Criteria,  Up: Reporting Bugs
@@ -6438,18 +6383,18 @@ File: ld.info,  Node: Bug Reporting,  Prev: Bug Criteria,  Up: Reporting Bugs
 ======================
 
 A number of companies and individuals offer support for GNU products.
-If you obtained `ld' from a support organization, we recommend you
+If you obtained 'ld' from a support organization, we recommend you
 contact that organization first.
 
    You can find contact information for many support companies and
-individuals in the file `etc/SERVICE' in the GNU Emacs distribution.
+individuals in the file 'etc/SERVICE' in the GNU Emacs distribution.
 
-   Otherwise, send bug reports for `ld' to
-`http://www.sourceware.org/bugzilla/ and mailto:hjl.tools@gmail.com'.
+   Otherwise, send bug reports for 'ld' to
+<http://www.sourceware.org/bugzilla/>.
 
-   The fundamental principle of reporting bugs usefully is this:
-*report all the facts*.  If you are not sure whether to state a fact or
-leave it out, state it!
+   The fundamental principle of reporting bugs usefully is this: *report
+all the facts*.  If you are not sure whether to state a fact or leave it
+out, state it!
 
    Often people omit facts because they think they know what causes the
 problem and assume that some details do not matter.  Thus, you might
@@ -6462,8 +6407,8 @@ thing despite the bug.  Play it safe and give a specific, complete
 example.  That is the easiest thing for you to do, and the most helpful.
 
    Keep in mind that the purpose of a bug report is to enable us to fix
-the bug if it is new to us.  Therefore, always write your bug reports
-on the assumption that the bug has not been reported previously.
+the bug if it is new to us.  Therefore, always write your bug reports on
+the assumption that the bug has not been reported previously.
 
    Sometimes people give a few sketchy facts and ask, "Does this ring a
 bell?"  This cannot help us fix a bug, so it is basically useless.  We
@@ -6472,20 +6417,20 @@ might as well expedite matters by sending them to begin with.
 
    To enable us to fix the bug, you should include all these things:
 
-   * The version of `ld'.  `ld' announces it if you start it with the
-     `--version' argument.
+   * The version of 'ld'.  'ld' announces it if you start it with the
+     '--version' argument.
 
      Without this, we will not know whether there is any point in
-     looking for the bug in the current version of `ld'.
+     looking for the bug in the current version of 'ld'.
 
-   * Any patches you may have applied to the `ld' source, including any
-     patches made to the `BFD' library.
+   * Any patches you may have applied to the 'ld' source, including any
+     patches made to the 'BFD' library.
 
    * The type of machine you are using, and the operating system name
      and version number.
 
-   * What compiler (and its version) was used to compile `ld'--e.g.
-     "`gcc-2.7'".
+   * What compiler (and its version) was used to compile 'ld'--e.g.
+     "'gcc-2.7'".
 
    * The command arguments you gave the linker to link your example and
      observe the bug.  To guarantee you will not omit something
@@ -6498,29 +6443,29 @@ might as well expedite matters by sending them to begin with.
    * A complete input file, or set of input files, that will reproduce
      the bug.  It is generally most helpful to send the actual object
      files provided that they are reasonably small.  Say no more than
-     10K.  For bigger files you can either make them available by FTP
-     or HTTP or else state that you are willing to send the object
-     file(s) to whomever requests them.  (Note - your email will be
-     going to a mailing list, so we do not want to clog it up with
-     large attachments).  But small attachments are best.
-
-     If the source files were assembled using `gas' or compiled using
-     `gcc', then it may be OK to send the source files rather than the
+     10K. For bigger files you can either make them available by FTP or
+     HTTP or else state that you are willing to send the object file(s)
+     to whomever requests them.  (Note - your email will be going to a
+     mailing list, so we do not want to clog it up with large
+     attachments).  But small attachments are best.
+
+     If the source files were assembled using 'gas' or compiled using
+     'gcc', then it may be OK to send the source files rather than the
      object files.  In this case, be sure to say exactly what version of
-     `gas' or `gcc' was used to produce the object files.  Also say how
-     `gas' or `gcc' were configured.
+     'gas' or 'gcc' was used to produce the object files.  Also say how
+     'gas' or 'gcc' were configured.
 
    * A description of what behavior you observe that you believe is
      incorrect.  For example, "It gets a fatal signal."
 
-     Of course, if the bug is that `ld' gets a fatal signal, then we
+     Of course, if the bug is that 'ld' gets a fatal signal, then we
      will certainly notice it.  But if the bug is incorrect output, we
      might not notice unless it is glaringly wrong.  You might as well
      not give us a chance to make a mistake.
 
      Even if the problem you experience is a fatal signal, you should
      still say so explicitly.  Suppose something strange is going on,
-     such as, your copy of `ld' is out of sync, or you have encountered
+     such as, your copy of 'ld' is out of sync, or you have encountered
      a bug in the C library on your system.  (This has happened!)  Your
      copy might crash and ours would not.  If you told us to expect a
      crash, then when ours fails to crash, we would know that the bug
@@ -6528,15 +6473,15 @@ might as well expedite matters by sending them to begin with.
      crash, then we would not be able to draw any conclusion from our
      observations.
 
-   * If you wish to suggest changes to the `ld' source, send us context
-     diffs, as generated by `diff' with the `-u', `-c', or `-p' option.
+   * If you wish to suggest changes to the 'ld' source, send us context
+     diffs, as generated by 'diff' with the '-u', '-c', or '-p' option.
      Always send diffs from the old file to the new file.  If you even
-     discuss something in the `ld' source, refer to it by context, not
+     discuss something in the 'ld' source, refer to it by context, not
      by line number.
 
-     The line numbers in our development sources will not match those
-     in your sources.  Your line numbers would convey no useful
-     information to us.
+     The line numbers in our development sources will not match those in
+     your sources.  Your line numbers would convey no useful information
+     to us.
 
    Here are some things that are not necessary:
 
@@ -6551,8 +6496,8 @@ might as well expedite matters by sending them to begin with.
      debugger with breakpoints, not by pure deduction from a series of
      examples.  We recommend that you save your time for something else.
 
-     Of course, if you can find a simpler example to report _instead_
-     of the original one, that is a convenience for us.  Errors in the
+     Of course, if you can find a simpler example to report _instead_ of
+     the original one, that is a convenience for us.  Errors in the
      output will be easier to spot, running under the debugger will take
      less time, and so on.
 
@@ -6564,15 +6509,15 @@ might as well expedite matters by sending them to begin with.
 
      A patch for the bug does help us if it is a good one.  But do not
      omit the necessary information, such as the test case, on the
-     assumption that a patch is all we need.  We might see problems
-     with your patch and decide to fix the problem another way, or we
-     might not understand it at all.
+     assumption that a patch is all we need.  We might see problems with
+     your patch and decide to fix the problem another way, or we might
+     not understand it at all.
 
-     Sometimes with a program as complicated as `ld' it is very hard to
+     Sometimes with a program as complicated as 'ld' it is very hard to
      construct an example that will make the program follow a certain
      path through the code.  If you do not send us the example, we will
-     not be able to construct one, so we will not be able to verify
-     that the bug is fixed.
+     not be able to construct one, so we will not be able to verify that
+     the bug is fixed.
 
      And if we cannot understand what bug you are trying to fix, or why
      your patch should be an improvement, we will not install it.  A
@@ -6589,116 +6534,115 @@ File: ld.info,  Node: MRI,  Next: GNU Free Documentation License,  Prev: Reporti
 Appendix A MRI Compatible Script Files
 **************************************
 
-To aid users making the transition to GNU `ld' from the MRI linker,
-`ld' can use MRI compatible linker scripts as an alternative to the
-more general-purpose linker scripting language described in *note
-Scripts::.  MRI compatible linker scripts have a much simpler command
-set than the scripting language otherwise used with `ld'.  GNU `ld'
-supports the most commonly used MRI linker commands; these commands are
-described here.
+To aid users making the transition to GNU 'ld' from the MRI linker, 'ld'
+can use MRI compatible linker scripts as an alternative to the more
+general-purpose linker scripting language described in *note Scripts::.
+MRI compatible linker scripts have a much simpler command set than the
+scripting language otherwise used with 'ld'.  GNU 'ld' supports the most
+commonly used MRI linker commands; these commands are described here.
 
-   In general, MRI scripts aren't of much use with the `a.out' object
+   In general, MRI scripts aren't of much use with the 'a.out' object
 file format, since it only has three sections and MRI scripts lack some
 features to make use of them.
 
    You can specify a file containing an MRI-compatible script using the
-`-c' command-line option.
+'-c' command-line option.
 
    Each command in an MRI-compatible script occupies its own line; each
 command line starts with the keyword that identifies the command (though
 blank lines are also allowed for punctuation).  If a line of an
-MRI-compatible script begins with an unrecognized keyword, `ld' issues
-a warning message, but continues processing the script.
+MRI-compatible script begins with an unrecognized keyword, 'ld' issues a
+warning message, but continues processing the script.
 
-   Lines beginning with `*' are comments.
+   Lines beginning with '*' are comments.
 
    You can write these commands using all upper-case letters, or all
-lower case; for example, `chip' is the same as `CHIP'.  The following
+lower case; for example, 'chip' is the same as 'CHIP'.  The following
 list shows only the upper-case form of each command.
 
-`ABSOLUTE SECNAME'
-`ABSOLUTE SECNAME, SECNAME, ... SECNAME'
-     Normally, `ld' includes in the output file all sections from all
-     the input files.  However, in an MRI-compatible script, you can
-     use the `ABSOLUTE' command to restrict the sections that will be
-     present in your output program.  If the `ABSOLUTE' command is used
+'ABSOLUTE SECNAME'
+'ABSOLUTE SECNAME, SECNAME, ... SECNAME'
+     Normally, 'ld' includes in the output file all sections from all
+     the input files.  However, in an MRI-compatible script, you can use
+     the 'ABSOLUTE' command to restrict the sections that will be
+     present in your output program.  If the 'ABSOLUTE' command is used
      at all in a script, then only the sections named explicitly in
-     `ABSOLUTE' commands will appear in the linker output.  You can
+     'ABSOLUTE' commands will appear in the linker output.  You can
      still use other input sections (whatever you select on the command
-     line, or using `LOAD') to resolve addresses in the output file.
+     line, or using 'LOAD') to resolve addresses in the output file.
 
-`ALIAS OUT-SECNAME, IN-SECNAME'
-     Use this command to place the data from input section IN-SECNAME
-     in a section called OUT-SECNAME in the linker output file.
+'ALIAS OUT-SECNAME, IN-SECNAME'
+     Use this command to place the data from input section IN-SECNAME in
+     a section called OUT-SECNAME in the linker output file.
 
      IN-SECNAME may be an integer.
 
-`ALIGN SECNAME = EXPRESSION'
+'ALIGN SECNAME = EXPRESSION'
      Align the section called SECNAME to EXPRESSION.  The EXPRESSION
      should be a power of two.
 
-`BASE EXPRESSION'
+'BASE EXPRESSION'
      Use the value of EXPRESSION as the lowest address (other than
      absolute addresses) in the output file.
 
-`CHIP EXPRESSION'
-`CHIP EXPRESSION, EXPRESSION'
+'CHIP EXPRESSION'
+'CHIP EXPRESSION, EXPRESSION'
      This command does nothing; it is accepted only for compatibility.
 
-`END'
+'END'
      This command does nothing whatever; it's only accepted for
      compatibility.
 
-`FORMAT OUTPUT-FORMAT'
-     Similar to the `OUTPUT_FORMAT' command in the more general linker
+'FORMAT OUTPUT-FORMAT'
+     Similar to the 'OUTPUT_FORMAT' command in the more general linker
      language, but restricted to one of these output formats:
 
-       1. S-records, if OUTPUT-FORMAT is `S'
+       1. S-records, if OUTPUT-FORMAT is 'S'
 
-       2. IEEE, if OUTPUT-FORMAT is `IEEE'
+       2. IEEE, if OUTPUT-FORMAT is 'IEEE'
 
-       3. COFF (the `coff-m68k' variant in BFD), if OUTPUT-FORMAT is
-          `COFF'
+       3. COFF (the 'coff-m68k' variant in BFD), if OUTPUT-FORMAT is
+          'COFF'
 
-`LIST ANYTHING...'
+'LIST ANYTHING...'
      Print (to the standard output file) a link map, as produced by the
-     `ld' command-line option `-M'.
+     'ld' command-line option '-M'.
 
-     The keyword `LIST' may be followed by anything on the same line,
+     The keyword 'LIST' may be followed by anything on the same line,
      with no change in its effect.
 
-`LOAD FILENAME'
-`LOAD FILENAME, FILENAME, ... FILENAME'
+'LOAD FILENAME'
+'LOAD FILENAME, FILENAME, ... FILENAME'
      Include one or more object file FILENAME in the link; this has the
-     same effect as specifying FILENAME directly on the `ld' command
+     same effect as specifying FILENAME directly on the 'ld' command
      line.
 
-`NAME OUTPUT-NAME'
-     OUTPUT-NAME is the name for the program produced by `ld'; the
-     MRI-compatible command `NAME' is equivalent to the command-line
-     option `-o' or the general script language command `OUTPUT'.
+'NAME OUTPUT-NAME'
+     OUTPUT-NAME is the name for the program produced by 'ld'; the
+     MRI-compatible command 'NAME' is equivalent to the command-line
+     option '-o' or the general script language command 'OUTPUT'.
 
-`ORDER SECNAME, SECNAME, ... SECNAME'
-`ORDER SECNAME SECNAME SECNAME'
-     Normally, `ld' orders the sections in its output file in the order
+'ORDER SECNAME, SECNAME, ... SECNAME'
+'ORDER SECNAME SECNAME SECNAME'
+     Normally, 'ld' orders the sections in its output file in the order
      in which they first appear in the input files.  In an
      MRI-compatible script, you can override this ordering with the
-     `ORDER' command.  The sections you list with `ORDER' will appear
+     'ORDER' command.  The sections you list with 'ORDER' will appear
      first in your output file, in the order specified.
 
-`PUBLIC NAME=EXPRESSION'
-`PUBLIC NAME,EXPRESSION'
-`PUBLIC NAME EXPRESSION'
+'PUBLIC NAME=EXPRESSION'
+'PUBLIC NAME,EXPRESSION'
+'PUBLIC NAME EXPRESSION'
      Supply a value (EXPRESSION) for external symbol NAME used in the
      linker input files.
 
-`SECT SECNAME, EXPRESSION'
-`SECT SECNAME=EXPRESSION'
-`SECT SECNAME EXPRESSION'
-     You can use any of these three forms of the `SECT' command to
-     specify the start address (EXPRESSION) for section SECNAME.  If
-     you have more than one `SECT' statement for the same SECNAME, only
-     the _first_ sets the start address.
+'SECT SECNAME, EXPRESSION'
+'SECT SECNAME=EXPRESSION'
+'SECT SECNAME EXPRESSION'
+     You can use any of these three forms of the 'SECT' command to
+     specify the start address (EXPRESSION) for section SECNAME.  If you
+     have more than one 'SECT' statement for the same SECNAME, only the
+     _first_ sets the start address.
 
 
 File: ld.info,  Node: GNU Free Documentation License,  Next: LD Index,  Prev: MRI,  Up: Top
@@ -6709,7 +6653,7 @@ Appendix B GNU Free Documentation License
                      Version 1.3, 3 November 2008
 
      Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-     `http://fsf.org/'
+     <http://fsf.org/>
 
      Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.
@@ -6734,21 +6678,21 @@ Appendix B GNU Free Documentation License
      free program should come with manuals providing the same freedoms
      that the software does.  But this License is not limited to
      software manuals; it can be used for any textual work, regardless
-     of subject matter or whether it is published as a printed book.
-     We recommend this License principally for works whose purpose is
+     of subject matter or whether it is published as a printed book.  We
+     recommend this License principally for works whose purpose is
      instruction or reference.
 
   1. APPLICABILITY AND DEFINITIONS
 
      This License applies to any manual or other work, in any medium,
-     that contains a notice placed by the copyright holder saying it
-     can be distributed under the terms of this License.  Such a notice
+     that contains a notice placed by the copyright holder saying it can
+     be distributed under the terms of this License.  Such a notice
      grants a world-wide, royalty-free license, unlimited in duration,
      to use that work under the conditions stated herein.  The
      "Document", below, refers to any such manual or work.  Any member
-     of the public is a licensee, and is addressed as "you".  You
-     accept the license if you copy, modify or distribute the work in a
-     way requiring permission under copyright law.
+     of the public is a licensee, and is addressed as "you".  You accept
+     the license if you copy, modify or distribute the work in a way
+     requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
      Document or a portion of it, either copied verbatim, or with
@@ -6766,12 +6710,12 @@ Appendix B GNU Free Documentation License
      regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
-     titles are designated, as being those of Invariant Sections, in
-     the notice that says that the Document is released under this
-     License.  If a section does not fit the above definition of
-     Secondary then it is not allowed to be designated as Invariant.
-     The Document may contain zero Invariant Sections.  If the Document
-     does not identify any Invariant Sections then there are none.
+     titles are designated, as being those of Invariant Sections, in the
+     notice that says that the Document is released under this License.
+     If a section does not fit the above definition of Secondary then it
+     is not allowed to be designated as Invariant.  The Document may
+     contain zero Invariant Sections.  If the Document does not identify
+     any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
@@ -6782,27 +6726,27 @@ Appendix B GNU Free Documentation License
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
      general public, that is suitable for revising the document
-     straightforwardly with generic text editors or (for images
-     composed of pixels) generic paint programs or (for drawings) some
-     widely available drawing editor, and that is suitable for input to
-     text formatters or for automatic translation to a variety of
-     formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup, or absence of
-     markup, has been arranged to thwart or discourage subsequent
-     modification by readers is not Transparent.  An image format is
-     not Transparent if used for any substantial amount of text.  A
-     copy that is not "Transparent" is called "Opaque".
+     straightforwardly with generic text editors or (for images composed
+     of pixels) generic paint programs or (for drawings) some widely
+     available drawing editor, and that is suitable for input to text
+     formatters or for automatic translation to a variety of formats
+     suitable for input to text formatters.  A copy made in an otherwise
+     Transparent file format whose markup, or absence of markup, has
+     been arranged to thwart or discourage subsequent modification by
+     readers is not Transparent.  An image format is not Transparent if
+     used for any substantial amount of text.  A copy that is not
+     "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
-     SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML, PostScript or PDF designed for
-     human modification.  Examples of transparent image formats include
-     PNG, XCF and JPG.  Opaque formats include proprietary formats that
-     can be read and edited only by proprietary word processors, SGML or
-     XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML, PostScript or PDF
-     produced by some word processors for output purposes only.
+     SGML or XML using a publicly available DTD, and standard-conforming
+     simple HTML, PostScript or PDF designed for human modification.
+     Examples of transparent image formats include PNG, XCF and JPG.
+     Opaque formats include proprietary formats that can be read and
+     edited only by proprietary word processors, SGML or XML for which
+     the DTD and/or processing tools are not generally available, and
+     the machine-generated HTML, PostScript or PDF produced by some word
+     processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
      plus such following pages as are needed to hold, legibly, the
@@ -6840,8 +6784,8 @@ Appendix B GNU Free Documentation License
      may not use technical measures to obstruct or control the reading
      or further copying of the copies you make or distribute.  However,
      you may accept compensation in exchange for copies.  If you
-     distribute a large enough number of copies you must also follow
-     the conditions in section 3.
+     distribute a large enough number of copies you must also follow the
+     conditions in section 3.
 
      You may also lend copies, under the same conditions stated above,
      and you may publicly display copies.
@@ -6855,12 +6799,11 @@ Appendix B GNU Free Documentation License
      these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
-     front cover must present the full title with all words of the
-     title equally prominent and visible.  You may add other material
-     on the covers in addition.  Copying with changes limited to the
-     covers, as long as they preserve the title of the Document and
-     satisfy these conditions, can be treated as verbatim copying in
-     other respects.
+     front cover must present the full title with all words of the title
+     equally prominent and visible.  You may add other material on the
+     covers in addition.  Copying with changes limited to the covers, as
+     long as they preserve the title of the Document and satisfy these
+     conditions, can be treated as verbatim copying in other respects.
 
      If the required texts for either cover are too voluminous to fit
      legibly, you should put the first ones listed (as many as fit
@@ -6868,40 +6811,39 @@ Appendix B GNU Free Documentation License
      adjacent pages.
 
      If you publish or distribute Opaque copies of the Document
-     numbering more than 100, you must either include a
-     machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a computer-network location from
-     which the general network-using public has access to download
-     using public-standard network protocols a complete Transparent
-     copy of the Document, free of added material.  If you use the
-     latter option, you must take reasonably prudent steps, when you
-     begin distribution of Opaque copies in quantity, to ensure that
-     this Transparent copy will remain thus accessible at the stated
-     location until at least one year after the last time you
-     distribute an Opaque copy (directly or through your agents or
-     retailers) of that edition to the public.
+     numbering more than 100, you must either include a machine-readable
+     Transparent copy along with each Opaque copy, or state in or with
+     each Opaque copy a computer-network location from which the general
+     network-using public has access to download using public-standard
+     network protocols a complete Transparent copy of the Document, free
+     of added material.  If you use the latter option, you must take
+     reasonably prudent steps, when you begin distribution of Opaque
+     copies in quantity, to ensure that this Transparent copy will
+     remain thus accessible at the stated location until at least one
+     year after the last time you distribute an Opaque copy (directly or
+     through your agents or retailers) of that edition to the public.
 
      It is requested, but not required, that you contact the authors of
-     the Document well before redistributing any large number of
-     copies, to give them a chance to provide you with an updated
-     version of the Document.
+     the Document well before redistributing any large number of copies,
+     to give them a chance to provide you with an updated version of the
+     Document.
 
   4. MODIFICATIONS
 
      You may copy and distribute a Modified Version of the Document
      under the conditions of sections 2 and 3 above, provided that you
-     release the Modified Version under precisely this License, with
-     the Modified Version filling the role of the Document, thus
-     licensing distribution and modification of the Modified Version to
-     whoever possesses a copy of it.  In addition, you must do these
-     things in the Modified Version:
+     release the Modified Version under precisely this License, with the
+     Modified Version filling the role of the Document, thus licensing
+     distribution and modification of the Modified Version to whoever
+     possesses a copy of it.  In addition, you must do these things in
+     the Modified Version:
 
        A. Use in the Title Page (and on the covers, if any) a title
-          distinct from that of the Document, and from those of
-          previous versions (which should, if there were any, be listed
-          in the History section of the Document).  You may use the
-          same title as a previous version if the original publisher of
-          that version gives permission.
+          distinct from that of the Document, and from those of previous
+          versions (which should, if there were any, be listed in the
+          History section of the Document).  You may use the same title
+          as a previous version if the original publisher of that
+          version gives permission.
 
        B. List on the Title Page, as authors, one or more persons or
           entities responsible for authorship of the modifications in
@@ -6931,31 +6873,30 @@ Appendix B GNU Free Documentation License
 
        I. Preserve the section Entitled "History", Preserve its Title,
           and add to it an item stating at least the title, year, new
-          authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section Entitled "History" in
-          the Document, create one stating the title, year, authors,
-          and publisher of the Document as given on its Title Page,
-          then add an item describing the Modified Version as stated in
-          the previous sentence.
+          authors, and publisher of the Modified Version as given on the
+          Title Page.  If there is no section Entitled "History" in the
+          Document, create one stating the title, year, authors, and
+          publisher of the Document as given on its Title Page, then add
+          an item describing the Modified Version as stated in the
+          previous sentence.
 
        J. Preserve the network location, if any, given in the Document
           for public access to a Transparent copy of the Document, and
           likewise the network locations given in the Document for
-          previous versions it was based on.  These may be placed in
-          the "History" section.  You may omit a network location for a
-          work that was published at least four years before the
-          Document itself, or if the original publisher of the version
-          it refers to gives permission.
+          previous versions it was based on.  These may be placed in the
+          "History" section.  You may omit a network location for a work
+          that was published at least four years before the Document
+          itself, or if the original publisher of the version it refers
+          to gives permission.
 
        K. For any section Entitled "Acknowledgements" or "Dedications",
-          Preserve the Title of the section, and preserve in the
-          section all the substance and tone of each of the contributor
+          Preserve the Title of the section, and preserve in the section
+          all the substance and tone of each of the contributor
           acknowledgements and/or dedications given therein.
 
-       L. Preserve all the Invariant Sections of the Document,
-          unaltered in their text and in their titles.  Section numbers
-          or the equivalent are not considered part of the section
-          titles.
+       L. Preserve all the Invariant Sections of the Document, unaltered
+          in their text and in their titles.  Section numbers or the
+          equivalent are not considered part of the section titles.
 
        M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
@@ -6968,11 +6909,11 @@ Appendix B GNU Free Documentation License
 
      If the Modified Version includes new front-matter sections or
      appendices that qualify as Secondary Sections and contain no
-     material copied from the Document, you may at your option
-     designate some or all of these sections as invariant.  To do this,
-     add their titles to the list of Invariant Sections in the Modified
-     Version's license notice.  These titles must be distinct from any
-     other section titles.
+     material copied from the Document, you may at your option designate
+     some or all of these sections as invariant.  To do this, add their
+     titles to the list of Invariant Sections in the Modified Version's
+     license notice.  These titles must be distinct from any other
+     section titles.
 
      You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
@@ -6981,15 +6922,15 @@ Appendix B GNU Free Documentation License
      definition of a standard.
 
      You may add a passage of up to five words as a Front-Cover Text,
-     and a passage of up to 25 words as a Back-Cover Text, to the end
-     of the list of Cover Texts in the Modified Version.  Only one
-     passage of Front-Cover Text and one of Back-Cover Text may be
-     added by (or through arrangements made by) any one entity.  If the
-     Document already includes a cover text for the same cover,
-     previously added by you or by arrangement made by the same entity
-     you are acting on behalf of, you may not add another; but you may
-     replace the old one, on explicit permission from the previous
-     publisher that added the old one.
+     and a passage of up to 25 words as a Back-Cover Text, to the end of
+     the list of Cover Texts in the Modified Version.  Only one passage
+     of Front-Cover Text and one of Back-Cover Text may be added by (or
+     through arrangements made by) any one entity.  If the Document
+     already includes a cover text for the same cover, previously added
+     by you or by arrangement made by the same entity you are acting on
+     behalf of, you may not add another; but you may replace the old
+     one, on explicit permission from the previous publisher that added
+     the old one.
 
      The author(s) and publisher(s) of the Document do not by this
      License give permission to use their names for publicity for or to
@@ -6999,8 +6940,8 @@ Appendix B GNU Free Documentation License
 
      You may combine the Document with other documents released under
      this License, under the terms defined in section 4 above for
-     modified versions, provided that you include in the combination
-     all of the Invariant Sections of all of the original documents,
+     modified versions, provided that you include in the combination all
+     of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
      combined work in its license notice, and that you preserve all
      their Warranty Disclaimers.
@@ -7027,20 +6968,20 @@ Appendix B GNU Free Documentation License
      documents released under this License, and replace the individual
      copies of this License in the various documents with a single copy
      that is included in the collection, provided that you follow the
-     rules of this License for verbatim copying of each of the
-     documents in all other respects.
+     rules of this License for verbatim copying of each of the documents
+     in all other respects.
 
      You may extract a single document from such a collection, and
      distribute it individually under this License, provided you insert
-     a copy of this License into the extracted document, and follow
-     this License in all other respects regarding verbatim copying of
-     that document.
+     a copy of this License into the extracted document, and follow this
+     License in all other respects regarding verbatim copying of that
+     document.
 
   7. AGGREGATION WITH INDEPENDENT WORKS
 
      A compilation of the Document or its derivatives with other
-     separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, is called an "aggregate" if the
+     separate and independent documents or works, in or on a volume of a
+     storage or distribution medium, is called an "aggregate" if the
      copyright resulting from the compilation is not used to limit the
      legal rights of the compilation's users beyond what the individual
      works permit.  When the Document is included in an aggregate, this
@@ -7085,8 +7026,8 @@ Appendix B GNU Free Documentation License
 
      However, if you cease all violation of this License, then your
      license from a particular copyright holder is reinstated (a)
-     provisionally, unless and until the copyright holder explicitly
-     and finally terminates your license, and (b) permanently, if the
+     provisionally, unless and until the copyright holder explicitly and
+     finally terminates your license, and (b) permanently, if the
      copyright holder fails to notify you of the violation by some
      reasonable means prior to 60 days after the cessation.
 
@@ -7098,33 +7039,33 @@ Appendix B GNU Free Documentation License
      after your receipt of the notice.
 
      Termination of your rights under this section does not terminate
-     the licenses of parties who have received copies or rights from
-     you under this License.  If your rights have been terminated and
-     not permanently reinstated, receipt of a copy of some or all of
-     the same material does not give you any rights to use it.
+     the licenses of parties who have received copies or rights from you
+     under this License.  If your rights have been terminated and not
+     permanently reinstated, receipt of a copy of some or all of the
+     same material does not give you any rights to use it.
 
- 10. FUTURE REVISIONS OF THIS LICENSE
+  10. FUTURE REVISIONS OF THIS LICENSE
 
      The Free Software Foundation may publish new, revised versions of
      the GNU Free Documentation License from time to time.  Such new
      versions will be similar in spirit to the present version, but may
      differ in detail to address new problems or concerns.  See
-     `http://www.gnu.org/copyleft/'.
+     <http://www.gnu.org/copyleft/>.
 
      Each version of the License is given a distinguishing version
      number.  If the Document specifies that a particular numbered
      version of this License "or any later version" applies to it, you
      have the option of following the terms and conditions either of
      that specified version or of any later version that has been
-     published (not as a draft) by the Free Software Foundation.  If
-     the Document does not specify a version number of this License,
-     you may choose any version ever published (not as a draft) by the
-     Free Software Foundation.  If the Document specifies that a proxy
-     can decide which future versions of this License can be used, that
+     published (not as a draft) by the Free Software Foundation.  If the
+     Document does not specify a version number of this License, you may
+     choose any version ever published (not as a draft) by the Free
+     Software Foundation.  If the Document specifies that a proxy can
+     decide which future versions of this License can be used, that
      proxy's public statement of acceptance of a version permanently
      authorizes you to choose that version for the Document.
 
- 11. RELICENSING
+  11. RELICENSING
 
      "Massive Multiauthor Collaboration Site" (or "MMC Site") means any
      World Wide Web server that publishes copyrightable works and also
@@ -7154,7 +7095,6 @@ Appendix B GNU Free Documentation License
      site under CC-BY-SA on the same site at any time before August 1,
      2009, provided the MMC is eligible for relicensing.
 
-
 ADDENDUM: How to use this License for your documents
 ====================================================
 
@@ -7171,7 +7111,7 @@ notices just after the title page:
        Free Documentation License''.
 
    If you have Invariant Sections, Front-Cover Texts and Back-Cover
-Texts, replace the "with...Texts." line with this:
+Texts, replace the "with...Texts."  line with this:
 
          with the Invariant Sections being LIST THEIR TITLES, with
          the Front-Cover Texts being LIST, and with the Back-Cover Texts
@@ -7182,9 +7122,9 @@ combination of the three, merge those two alternatives to suit the
 situation.
 
    If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License, to
-permit their use in free software.
+recommend releasing these examples in parallel under your choice of free
+software license, such as the GNU General Public License, to permit
+their use in free software.
 
 
 File: ld.info,  Node: LD Index,  Prev: GNU Free Documentation License,  Up: Top
@@ -7196,302 +7136,308 @@ LD Index
 * Menu:
 
 * ":                                     Symbols.            (line    6)
-* -(:                                    Options.            (line  710)
-* --accept-unknown-input-arch:           Options.            (line  728)
-* --add-needed:                          Options.            (line  755)
-* --add-stdcall-alias:                   Options.            (line 1612)
-* --allow-multiple-definition:           Options.            (line 1006)
-* --allow-shlib-undefined:               Options.            (line 1012)
-* --architecture=ARCH:                   Options.            (line  123)
-* --as-needed:                           Options.            (line  738)
-* --audit AUDITLIB:                      Options.            (line  112)
-* --auxiliary=NAME:                      Options.            (line  255)
-* --bank-window:                         Options.            (line 2044)
-* --base-file:                           Options.            (line 1617)
+* -(:                                    Options.            (line  699)
+* --accept-unknown-input-arch:           Options.            (line  717)
+* --add-needed:                          Options.            (line  744)
+* --add-stdcall-alias:                   Options.            (line 1591)
+* --allow-multiple-definition:           Options.            (line  995)
+* --allow-shlib-undefined:               Options.            (line 1001)
+* --architecture=ARCH:                   Options.            (line  122)
+* --as-needed:                           Options.            (line  727)
+* --audit AUDITLIB:                      Options.            (line  111)
+* --auxiliary=NAME:                      Options.            (line  254)
+* --bank-window:                         Options.            (line 2031)
+* --base-file:                           Options.            (line 1596)
 * --be8:                                 ARM.                (line   28)
 * --bss-plt:                             PowerPC ELF32.      (line   16)
-* --build-id:                            Options.            (line 1574)
-* --build-id=STYLE:                      Options.            (line 1574)
-* --check-sections:                      Options.            (line  834)
-* --copy-dt-needed-entries:              Options.            (line  846)
-* --cref:                                Options.            (line  866)
-* --default-imported-symver:             Options.            (line 1049)
-* --default-script=SCRIPT:               Options.            (line  541)
-* --default-symver:                      Options.            (line 1045)
-* --defsym=SYMBOL=EXP:                   Options.            (line  894)
-* --demangle[=STYLE]:                    Options.            (line  907)
-* --depaudit AUDITLIB:                   Options.            (line  177)
-* --disable-auto-image-base:             Options.            (line 1796)
-* --disable-auto-import:                 Options.            (line 1931)
-* --disable-long-section-names:          Options.            (line 1627)
-* --disable-new-dtags:                   Options.            (line 1536)
-* --disable-runtime-pseudo-reloc:        Options.            (line 1944)
-* --disable-stdcall-fixup:               Options.            (line 1649)
-* --discard-all:                         Options.            (line  587)
-* --discard-locals:                      Options.            (line  591)
-* --dll:                                 Options.            (line 1622)
-* --dll-search-prefix:                   Options.            (line 1802)
+* --build-id:                            Options.            (line 1553)
+* --build-id=STYLE:                      Options.            (line 1553)
+* --check-sections:                      Options.            (line  822)
+* --copy-dt-needed-entries:              Options.            (line  834)
+* --cref:                                Options.            (line  854)
+* --default-imported-symver:             Options.            (line 1037)
+* --default-script=SCRIPT:               Options.            (line  534)
+* --default-symver:                      Options.            (line 1033)
+* --defsym=SYMBOL=EXP:                   Options.            (line  883)
+* --demangle[=STYLE]:                    Options.            (line  896)
+* --depaudit AUDITLIB:                   Options.            (line  176)
+* --disable-auto-image-base:             Options.            (line 1780)
+* --disable-auto-import:                 Options.            (line 1914)
+* --disable-large-address-aware:         Options.            (line 1721)
+* --disable-long-section-names:          Options.            (line 1606)
+* --disable-new-dtags:                   Options.            (line 1515)
+* --disable-runtime-pseudo-reloc:        Options.            (line 1927)
+* --disable-stdcall-fixup:               Options.            (line 1628)
+* --discard-all:                         Options.            (line  580)
+* --discard-locals:                      Options.            (line  584)
+* --dll:                                 Options.            (line 1601)
+* --dll-search-prefix:                   Options.            (line 1786)
 * --dotsyms:                             PowerPC64 ELF64.    (line   33)
-* --dsbt-index:                          Options.            (line 2021)
-* --dsbt-size:                           Options.            (line 2016)
-* --dynamic-linker=FILE:                 Options.            (line  920)
-* --dynamic-list-cpp-new:                Options.            (line  826)
-* --dynamic-list-cpp-typeinfo:           Options.            (line  830)
-* --dynamic-list-data:                   Options.            (line  823)
-* --dynamic-list=DYNAMIC-LIST-FILE:      Options.            (line  810)
-* --dynamicbase:                         Options.            (line 1980)
-* --eh-frame-hdr:                        Options.            (line 1527)
-* --emit-relocs:                         Options.            (line  476)
+* --dsbt-index:                          Options.            (line 2009)
+* --dsbt-size:                           Options.            (line 2004)
+* --dynamic-linker=FILE:                 Options.            (line  909)
+* --dynamic-list-cpp-new:                Options.            (line  814)
+* --dynamic-list-cpp-typeinfo:           Options.            (line  818)
+* --dynamic-list-data:                   Options.            (line  811)
+* --dynamic-list=DYNAMIC-LIST-FILE:      Options.            (line  798)
+* --dynamicbase:                         Options.            (line 1963)
+* --eh-frame-hdr:                        Options.            (line 1506)
+* --emit-relocs:                         Options.            (line  470)
 * --emit-stack-syms:                     SPU ELF.            (line   46)
-* --emit-stub-syms <1>:                  SPU ELF.            (line   15)
-* --emit-stub-syms <2>:                  PowerPC64 ELF64.    (line   29)
 * --emit-stub-syms:                      PowerPC ELF32.      (line   47)
-* --enable-auto-image-base:              Options.            (line 1788)
-* --enable-auto-import:                  Options.            (line 1811)
-* --enable-extra-pe-debug:               Options.            (line 1949)
-* --enable-long-section-names:           Options.            (line 1627)
-* --enable-new-dtags:                    Options.            (line 1536)
-* --enable-runtime-pseudo-reloc:         Options.            (line 1936)
-* --enable-stdcall-fixup:                Options.            (line 1649)
-* --entry=ENTRY:                         Options.            (line  187)
-* --error-unresolved-symbols:            Options.            (line 1480)
-* --exclude-all-symbols:                 Options.            (line 1703)
-* --exclude-libs:                        Options.            (line  197)
-* --exclude-modules-for-implib:          Options.            (line  208)
-* --exclude-symbols:                     Options.            (line 1697)
-* --export-all-symbols:                  Options.            (line 1673)
-* --export-dynamic:                      Options.            (line  221)
+* --emit-stub-syms <1>:                  PowerPC64 ELF64.    (line   29)
+* --emit-stub-syms <2>:                  SPU ELF.            (line   15)
+* --enable-auto-image-base:              Options.            (line 1772)
+* --enable-auto-import:                  Options.            (line 1795)
+* --enable-extra-pe-debug:               Options.            (line 1932)
+* --enable-long-section-names:           Options.            (line 1606)
+* --enable-new-dtags:                    Options.            (line 1515)
+* --enable-runtime-pseudo-reloc:         Options.            (line 1919)
+* --enable-stdcall-fixup:                Options.            (line 1628)
+* --entry=ENTRY:                         Options.            (line  186)
+* --error-unresolved-symbols:            Options.            (line 1459)
+* --exclude-all-symbols:                 Options.            (line 1681)
+* --exclude-libs:                        Options.            (line  196)
+* --exclude-modules-for-implib:          Options.            (line  207)
+* --exclude-symbols:                     Options.            (line 1675)
+* --export-all-symbols:                  Options.            (line 1651)
+* --export-dynamic:                      Options.            (line  220)
 * --extra-overlay-stubs:                 SPU ELF.            (line   19)
-* --fatal-warnings:                      Options.            (line  927)
-* --file-alignment:                      Options.            (line 1707)
-* --filter=NAME:                         Options.            (line  276)
-* --fix-arm1176:                         ARM.                (line  111)
-* --fix-cortex-a8:                       i960.               (line   39)
-* --fix-v4bx:                            ARM.                (line   49)
-* --fix-v4bx-interworking:               ARM.                (line   62)
-* --force-dynamic:                       Options.            (line  485)
-* --force-exe-suffix:                    Options.            (line  932)
-* --forceinteg:                          Options.            (line 1985)
-* --format=FORMAT:                       Options.            (line  134)
+* --fatal-warnings:                      Options.            (line  916)
+* --file-alignment:                      Options.            (line 1685)
+* --filter=NAME:                         Options.            (line  275)
+* --fix-arm1176:                         ARM.                (line  110)
+* --fix-cortex-a8:                       i960.               (line   40)
+* --fix-v4bx:                            ARM.                (line   47)
+* --fix-v4bx-interworking:               ARM.                (line   60)
+* --force-dynamic:                       Options.            (line  479)
+* --force-exe-suffix:                    Options.            (line  921)
+* --forceinteg:                          Options.            (line 1968)
+* --format=FORMAT:                       Options.            (line  133)
 * --format=VERSION:                      TI COFF.            (line    6)
-* --gc-sections:                         Options.            (line  942)
-* --got:                                 Options.            (line 2057)
+* --gc-sections:                         Options.            (line  931)
+* --got:                                 Options.            (line 2043)
 * --got=TYPE:                            M68K.               (line    6)
-* --gpsize=VALUE:                        Options.            (line  309)
-* --hash-size=NUMBER:                    Options.            (line 1546)
-* --hash-style=STYLE:                    Options.            (line 1554)
-* --heap:                                Options.            (line 1713)
-* --help:                                Options.            (line  979)
-* --image-base:                          Options.            (line 1720)
-* --just-symbols=FILE:                   Options.            (line  508)
-* --kill-at:                             Options.            (line 1729)
-* --large-address-aware:                 Options.            (line 1734)
-* --ld-generated-unwind-info:            Options.            (line 1531)
-* --leading-underscore:                  Options.            (line 1667)
-* --library-path=DIR:                    Options.            (line  368)
-* --library=NAMESPEC:                    Options.            (line  335)
+* --gpsize=VALUE:                        Options.            (line  307)
+* --hash-size=NUMBER:                    Options.            (line 1525)
+* --hash-style=STYLE:                    Options.            (line 1533)
+* --heap:                                Options.            (line 1691)
+* --help:                                Options.            (line  968)
+* --image-base:                          Options.            (line 1698)
+* --insert-timestamp:                    Options.            (line 1991)
+* --insn32:                              Options.            (line 2054)
+* --insn32 <1>:                          MIPS.               (line    6)
+* --just-symbols=FILE:                   Options.            (line  501)
+* --kill-at:                             Options.            (line 1707)
+* --large-address-aware:                 Options.            (line 1712)
+* --ld-generated-unwind-info:            Options.            (line 1510)
+* --leading-underscore:                  Options.            (line 1645)
+* --library-path=DIR:                    Options.            (line  365)
+* --library=NAMESPEC:                    Options.            (line  332)
 * --local-store=lo:hi:                   SPU ELF.            (line   24)
-* --major-image-version:                 Options.            (line 1743)
-* --major-os-version:                    Options.            (line 1748)
-* --major-subsystem-version:             Options.            (line 1752)
-* --merge-exidx-entries:                 i960.               (line   48)
-* --minor-image-version:                 Options.            (line 1757)
-* --minor-os-version:                    Options.            (line 1762)
-* --minor-subsystem-version:             Options.            (line 1766)
-* --mri-script=MRI-CMDFILE:              Options.            (line  158)
+* --major-image-version:                 Options.            (line 1728)
+* --major-os-version:                    Options.            (line 1733)
+* --major-subsystem-version:             Options.            (line 1737)
+* --merge-exidx-entries:                 i960.               (line   49)
+* --minor-image-version:                 Options.            (line 1742)
+* --minor-os-version:                    Options.            (line 1747)
+* --minor-subsystem-version:             Options.            (line 1751)
+* --mri-script=MRI-CMDFILE:              Options.            (line  157)
 * --multi-subspace:                      HPPA ELF32.         (line    6)
-* --nmagic:                              Options.            (line  439)
-* --no-accept-unknown-input-arch:        Options.            (line  728)
-* --no-add-needed:                       Options.            (line  755)
-* --no-allow-shlib-undefined:            Options.            (line 1012)
-* --no-as-needed:                        Options.            (line  738)
-* --no-bind:                             Options.            (line 1999)
-* --no-check-sections:                   Options.            (line  834)
-* --no-copy-dt-needed-entries:           Options.            (line  846)
-* --no-define-common:                    Options.            (line  878)
-* --no-demangle:                         Options.            (line  907)
+* --nmagic:                              Options.            (line  433)
+* --no-accept-unknown-input-arch:        Options.            (line  717)
+* --no-add-needed:                       Options.            (line  744)
+* --no-allow-shlib-undefined:            Options.            (line 1001)
+* --no-as-needed:                        Options.            (line  727)
+* --no-bind:                             Options.            (line 1982)
+* --no-check-sections:                   Options.            (line  822)
+* --no-copy-dt-needed-entries:           Options.            (line  834)
+* --no-define-common:                    Options.            (line  867)
+* --no-demangle:                         Options.            (line  896)
 * --no-dotsyms:                          PowerPC64 ELF64.    (line   33)
-* --no-enum-size-warning:                ARM.                (line  120)
-* --no-export-dynamic:                   Options.            (line  221)
-* --no-fatal-warnings:                   Options.            (line  927)
-* --no-fix-arm1176:                      ARM.                (line  111)
-* --no-fix-cortex-a8:                    i960.               (line   39)
-* --no-gc-sections:                      Options.            (line  942)
-* --no-isolation:                        Options.            (line 1992)
-* --no-keep-memory:                      Options.            (line  991)
-* --no-leading-underscore:               Options.            (line 1667)
-* --no-merge-exidx-entries <1>:          i960.               (line   48)
-* --no-merge-exidx-entries:              Options.            (line 2028)
+* --no-enum-size-warning:                ARM.                (line  119)
+* --no-export-dynamic:                   Options.            (line  220)
+* --no-fatal-warnings:                   Options.            (line  916)
+* --no-fix-arm1176:                      ARM.                (line  110)
+* --no-fix-cortex-a8:                    i960.               (line   40)
+* --no-gc-sections:                      Options.            (line  931)
+* --no-insn32:                           Options.            (line 2055)
+* --no-insn32 <1>:                       MIPS.               (line    6)
+* --no-isolation:                        Options.            (line 1975)
+* --no-keep-memory:                      Options.            (line  980)
+* --no-leading-underscore:               Options.            (line 1645)
+* --no-merge-exidx-entries:              Options.            (line 2016)
+* --no-merge-exidx-entries <1>:          i960.               (line   49)
 * --no-multi-toc:                        PowerPC64 ELF64.    (line   74)
-* --no-omagic:                           Options.            (line  454)
+* --no-omagic:                           Options.            (line  448)
 * --no-opd-optimize:                     PowerPC64 ELF64.    (line   48)
 * --no-overlays:                         SPU ELF.            (line    9)
 * --no-plt-align:                        PowerPC64 ELF64.    (line   96)
 * --no-plt-static-chain:                 PowerPC64 ELF64.    (line  103)
 * --no-plt-thread-safe:                  PowerPC64 ELF64.    (line  109)
-* --no-print-gc-sections:                Options.            (line  964)
-* --no-seh:                              Options.            (line 1995)
-* --no-tls-optimize <1>:                 PowerPC64 ELF64.    (line   43)
+* --no-print-gc-sections:                Options.            (line  953)
+* --no-seh:                              Options.            (line 1978)
 * --no-tls-optimize:                     PowerPC ELF32.      (line   51)
+* --no-tls-optimize <1>:                 PowerPC64 ELF64.    (line   43)
 * --no-toc-optimize:                     PowerPC64 ELF64.    (line   60)
 * --no-toc-sort:                         PowerPC64 ELF64.    (line   86)
-* --no-trampoline:                       Options.            (line 2038)
-* --no-undefined:                        Options.            (line  998)
-* --no-undefined-version:                Options.            (line 1040)
-* --no-warn-mismatch:                    Options.            (line 1053)
-* --no-warn-search-mismatch:             Options.            (line 1062)
-* --no-wchar-size-warning:               ARM.                (line  127)
-* --no-whole-archive:                    Options.            (line 1066)
-* --noinhibit-exec:                      Options.            (line 1070)
+* --no-trampoline:                       Options.            (line 2025)
+* --no-undefined:                        Options.            (line  987)
+* --no-undefined-version:                Options.            (line 1028)
+* --no-warn-mismatch:                    Options.            (line 1041)
+* --no-warn-search-mismatch:             Options.            (line 1050)
+* --no-wchar-size-warning:               ARM.                (line  126)
+* --no-whole-archive:                    Options.            (line 1054)
+* --noinhibit-exec:                      Options.            (line 1058)
 * --non-overlapping-opd:                 PowerPC64 ELF64.    (line   54)
-* --nxcompat:                            Options.            (line 1988)
-* --oformat=OUTPUT-FORMAT:               Options.            (line 1082)
-* --omagic:                              Options.            (line  445)
-* --out-implib:                          Options.            (line 1779)
-* --output-def:                          Options.            (line 1771)
-* --output=OUTPUT:                       Options.            (line  460)
-* --pic-executable:                      Options.            (line 1095)
-* --pic-veneer:                          ARM.                (line  133)
+* --nxcompat:                            Options.            (line 1971)
+* --oformat=OUTPUT-FORMAT:               Options.            (line 1069)
+* --omagic:                              Options.            (line  439)
+* --out-implib:                          Options.            (line 1764)
+* --output-def:                          Options.            (line 1756)
+* --output=OUTPUT:                       Options.            (line  454)
+* --pic-executable:                      Options.            (line 1082)
+* --pic-veneer:                          ARM.                (line  132)
 * --plt-align:                           PowerPC64 ELF64.    (line   96)
 * --plt-static-chain:                    PowerPC64 ELF64.    (line  103)
 * --plt-thread-safe:                     PowerPC64 ELF64.    (line  109)
 * --plugin:                              SPU ELF.            (line    6)
-* --print-gc-sections:                   Options.            (line  964)
-* --print-map:                           Options.            (line  402)
-* --print-output-format:                 Options.            (line  973)
-* --reduce-memory-overheads:             Options.            (line 1560)
-* --relax:                               Options.            (line 1111)
-* --relax on i960:                       i960.               (line   31)
+* --print-gc-sections:                   Options.            (line  953)
+* --print-map:                           Options.            (line  399)
+* --print-output-format:                 Options.            (line  962)
+* --reduce-memory-overheads:             Options.            (line 1539)
+* --relax:                               Options.            (line 1098)
+* '--relax' on i960:                     i960.               (line   32)
 * --relax on PowerPC:                    PowerPC ELF32.      (line    6)
-* --relax on Xtensa:                     Xtensa.             (line   27)
-* --relocatable:                         Options.            (line  489)
-* --retain-symbols-file=FILENAME:        Options.            (line 1137)
-* --script=SCRIPT:                       Options.            (line  532)
+* '--relax' on Xtensa:                   Xtensa.             (line   27)
+* --relocatable:                         Options.            (line  483)
+* --retain-symbols-file=FILENAME:        Options.            (line 1124)
+* --script=SCRIPT:                       Options.            (line  525)
 * --sdata-got:                           PowerPC ELF32.      (line   33)
-* --section-alignment:                   Options.            (line 1954)
-* --section-start=SECTIONNAME=ORG:       Options.            (line 1293)
+* --section-alignment:                   Options.            (line 1937)
+* --section-start=SECTIONNAME=ORG:       Options.            (line 1273)
 * --secure-plt:                          PowerPC ELF32.      (line   26)
-* --sort-common:                         Options.            (line 1235)
-* --sort-section=alignment:              Options.            (line 1250)
-* --sort-section=name:                   Options.            (line 1246)
-* --split-by-file:                       Options.            (line 1254)
-* --split-by-reloc:                      Options.            (line 1259)
-* --stack:                               Options.            (line 1960)
+* --sort-common:                         Options.            (line 1215)
+* --sort-section=alignment:              Options.            (line 1230)
+* --sort-section=name:                   Options.            (line 1226)
+* --split-by-file:                       Options.            (line 1234)
+* --split-by-reloc:                      Options.            (line 1239)
+* --stack:                               Options.            (line 1943)
 * --stack-analysis:                      SPU ELF.            (line   29)
-* --stats:                               Options.            (line 1272)
-* --strip-all:                           Options.            (line  519)
-* --strip-debug:                         Options.            (line  523)
+* --stats:                               Options.            (line 1252)
+* --strip-all:                           Options.            (line  512)
+* --strip-debug:                         Options.            (line  516)
 * --stub-group-size:                     PowerPC64 ELF64.    (line    6)
+* --stub-group-size=N:                   ARM.                (line  137)
 * --stub-group-size=N <1>:               HPPA ELF32.         (line   12)
-* --stub-group-size=N:                   ARM.                (line  138)
-* --subsystem:                           Options.            (line 1967)
+* --subsystem:                           Options.            (line 1950)
 * --support-old-code:                    ARM.                (line    6)
-* --sysroot=DIRECTORY:                   Options.            (line 1276)
-* --target-help:                         Options.            (line  983)
+* --sysroot=DIRECTORY:                   Options.            (line 1256)
+* --target-help:                         Options.            (line  972)
 * --target1-abs:                         ARM.                (line   32)
 * --target1-rel:                         ARM.                (line   32)
 * --target2=TYPE:                        ARM.                (line   37)
 * --thumb-entry=ENTRY:                   ARM.                (line   17)
-* --trace:                               Options.            (line  528)
-* --trace-symbol=SYMBOL:                 Options.            (line  597)
-* --traditional-format:                  Options.            (line 1281)
-* --tsaware:                             Options.            (line 2005)
-* --undefined=SYMBOL:                    Options.            (line  554)
-* --unique[=SECTION]:                    Options.            (line  572)
-* --unresolved-symbols:                  Options.            (line 1323)
-* --use-blx:                             ARM.                (line   74)
+* --trace:                               Options.            (line  521)
+* --trace-symbol=SYMBOL:                 Options.            (line  590)
+* --traditional-format:                  Options.            (line 1261)
+* --tsaware:                             Options.            (line 1988)
+* --undefined=SYMBOL:                    Options.            (line  547)
+* --unique[=SECTION]:                    Options.            (line  565)
+* --unresolved-symbols:                  Options.            (line 1303)
+* --use-blx:                             ARM.                (line   72)
 * --use-nul-prefixed-import-tables:      ARM.                (line   23)
-* --verbose[=NUMBER]:                    Options.            (line 1352)
-* --version:                             Options.            (line  581)
-* --version-script=VERSION-SCRIPTFILE:   Options.            (line 1360)
-* --vfp11-denorm-fix:                    ARM.                (line   83)
-* --warn-alternate-em:                   Options.            (line 1472)
-* --warn-common:                         Options.            (line 1371)
-* --warn-constructors:                   Options.            (line 1439)
-* --warn-multiple-gp:                    Options.            (line 1444)
-* --warn-once:                           Options.            (line 1458)
-* --warn-section-align:                  Options.            (line 1462)
-* --warn-shared-textrel:                 Options.            (line 1469)
-* --warn-unresolved-symbols:             Options.            (line 1475)
-* --wdmdriver:                           Options.            (line 2002)
-* --whole-archive:                       Options.            (line 1484)
-* --wrap=SYMBOL:                         Options.            (line 1498)
-* -A ARCH:                               Options.            (line  122)
-* -a KEYWORD:                            Options.            (line  105)
-* -assert KEYWORD:                       Options.            (line  762)
-* -b FORMAT:                             Options.            (line  134)
-* -Bdynamic:                             Options.            (line  765)
-* -Bgroup:                               Options.            (line  775)
-* -Bshareable:                           Options.            (line 1228)
-* -Bstatic:                              Options.            (line  782)
-* -Bsymbolic:                            Options.            (line  797)
-* -Bsymbolic-functions:                  Options.            (line  804)
-* -c MRI-CMDFILE:                        Options.            (line  158)
-* -call_shared:                          Options.            (line  765)
-* -d:                                    Options.            (line  168)
-* -dc:                                   Options.            (line  168)
-* -dn:                                   Options.            (line  782)
-* -dp:                                   Options.            (line  168)
-* -dT SCRIPT:                            Options.            (line  541)
-* -dy:                                   Options.            (line  765)
-* -E:                                    Options.            (line  221)
-* -e ENTRY:                              Options.            (line  187)
-* -EB:                                   Options.            (line  248)
-* -EL:                                   Options.            (line  251)
-* -F NAME:                               Options.            (line  276)
-* -f NAME:                               Options.            (line  255)
-* -fini=NAME:                            Options.            (line  300)
-* -g:                                    Options.            (line  306)
-* -G VALUE:                              Options.            (line  309)
-* -h NAME:                               Options.            (line  317)
-* -i:                                    Options.            (line  326)
-* -IFILE:                                Options.            (line  920)
-* -init=NAME:                            Options.            (line  329)
-* -L DIR:                                Options.            (line  368)
-* -l NAMESPEC:                           Options.            (line  335)
-* -M:                                    Options.            (line  402)
-* -m EMULATION:                          Options.            (line  392)
-* -Map=MAPFILE:                          Options.            (line  987)
-* -N:                                    Options.            (line  445)
-* -n:                                    Options.            (line  439)
-* -no-relax:                             Options.            (line 1111)
-* -non_shared:                           Options.            (line  782)
-* -nostdlib:                             Options.            (line 1076)
-* -O LEVEL:                              Options.            (line  466)
-* -o OUTPUT:                             Options.            (line  460)
-* -P AUDITLIB:                           Options.            (line  177)
-* -pie:                                  Options.            (line 1095)
-* -q:                                    Options.            (line  476)
-* -qmagic:                               Options.            (line 1105)
-* -Qy:                                   Options.            (line 1108)
-* -r:                                    Options.            (line  489)
-* -R FILE:                               Options.            (line  508)
-* -rpath-link=DIR:                       Options.            (line 1173)
-* -rpath=DIR:                            Options.            (line 1151)
-* -S:                                    Options.            (line  523)
-* -s:                                    Options.            (line  519)
-* -shared:                               Options.            (line 1228)
-* -soname=NAME:                          Options.            (line  317)
-* -static:                               Options.            (line  782)
-* -t:                                    Options.            (line  528)
-* -T SCRIPT:                             Options.            (line  532)
-* -Tbss=ORG:                             Options.            (line 1302)
-* -Tdata=ORG:                            Options.            (line 1302)
-* -Tldata-segment=ORG:                   Options.            (line 1318)
-* -Trodata-segment=ORG:                  Options.            (line 1312)
-* -Ttext-segment=ORG:                    Options.            (line 1308)
-* -Ttext=ORG:                            Options.            (line 1302)
-* -u SYMBOL:                             Options.            (line  554)
-* -Ur:                                   Options.            (line  562)
-* -V:                                    Options.            (line  581)
-* -v:                                    Options.            (line  581)
-* -X:                                    Options.            (line  591)
-* -x:                                    Options.            (line  587)
-* -Y PATH:                               Options.            (line  606)
-* -y SYMBOL:                             Options.            (line  597)
-* -z defs:                               Options.            (line  998)
-* -z KEYWORD:                            Options.            (line  610)
-* -z muldefs:                            Options.            (line 1006)
+* --verbose[=NUMBER]:                    Options.            (line 1332)
+* --version:                             Options.            (line  574)
+* --version-script=VERSION-SCRIPTFILE:   Options.            (line 1340)
+* --vfp11-denorm-fix:                    ARM.                (line   81)
+* --warn-alternate-em:                   Options.            (line 1451)
+* --warn-common:                         Options.            (line 1350)
+* --warn-constructors:                   Options.            (line 1418)
+* --warn-multiple-gp:                    Options.            (line 1423)
+* --warn-once:                           Options.            (line 1437)
+* --warn-section-align:                  Options.            (line 1441)
+* --warn-shared-textrel:                 Options.            (line 1448)
+* --warn-unresolved-symbols:             Options.            (line 1454)
+* --wdmdriver:                           Options.            (line 1985)
+* --whole-archive:                       Options.            (line 1463)
+* --wrap=SYMBOL:                         Options.            (line 1477)
+* -A ARCH:                               Options.            (line  121)
+* -a KEYWORD:                            Options.            (line  104)
+* -assert KEYWORD:                       Options.            (line  751)
+* -b FORMAT:                             Options.            (line  133)
+* -Bdynamic:                             Options.            (line  754)
+* -Bgroup:                               Options.            (line  764)
+* -Bshareable:                           Options.            (line 1208)
+* -Bstatic:                              Options.            (line  771)
+* -Bsymbolic:                            Options.            (line  785)
+* -Bsymbolic-functions:                  Options.            (line  792)
+* -c MRI-CMDFILE:                        Options.            (line  157)
+* -call_shared:                          Options.            (line  754)
+* -d:                                    Options.            (line  167)
+* -dc:                                   Options.            (line  167)
+* -dn:                                   Options.            (line  771)
+* -dp:                                   Options.            (line  167)
+* -dT SCRIPT:                            Options.            (line  534)
+* -dy:                                   Options.            (line  754)
+* -E:                                    Options.            (line  220)
+* -e ENTRY:                              Options.            (line  186)
+* -EB:                                   Options.            (line  247)
+* -EL:                                   Options.            (line  250)
+* -f NAME:                               Options.            (line  254)
+* -F NAME:                               Options.            (line  275)
+* -fini=NAME:                            Options.            (line  298)
+* -g:                                    Options.            (line  304)
+* -G VALUE:                              Options.            (line  307)
+* -h NAME:                               Options.            (line  314)
+* -i:                                    Options.            (line  323)
+* -IFILE:                                Options.            (line  909)
+* -init=NAME:                            Options.            (line  326)
+* -L DIR:                                Options.            (line  365)
+* -l NAMESPEC:                           Options.            (line  332)
+* -M:                                    Options.            (line  399)
+* -m EMULATION:                          Options.            (line  389)
+* -Map=MAPFILE:                          Options.            (line  976)
+* -n:                                    Options.            (line  433)
+* -N:                                    Options.            (line  439)
+* -no-relax:                             Options.            (line 1098)
+* -non_shared:                           Options.            (line  771)
+* -nostdlib:                             Options.            (line 1064)
+* -O LEVEL:                              Options.            (line  460)
+* -o OUTPUT:                             Options.            (line  454)
+* -P AUDITLIB:                           Options.            (line  176)
+* -pie:                                  Options.            (line 1082)
+* -q:                                    Options.            (line  470)
+* -qmagic:                               Options.            (line 1092)
+* -Qy:                                   Options.            (line 1095)
+* -r:                                    Options.            (line  483)
+* -R FILE:                               Options.            (line  501)
+* -rpath-link=DIR:                       Options.            (line 1160)
+* -rpath=DIR:                            Options.            (line 1138)
+* -s:                                    Options.            (line  512)
+* -S:                                    Options.            (line  516)
+* -shared:                               Options.            (line 1208)
+* -soname=NAME:                          Options.            (line  314)
+* -static:                               Options.            (line  771)
+* -t:                                    Options.            (line  521)
+* -T SCRIPT:                             Options.            (line  525)
+* -Tbss=ORG:                             Options.            (line 1282)
+* -Tdata=ORG:                            Options.            (line 1282)
+* -Tldata-segment=ORG:                   Options.            (line 1298)
+* -Trodata-segment=ORG:                  Options.            (line 1292)
+* -Ttext-segment=ORG:                    Options.            (line 1288)
+* -Ttext=ORG:                            Options.            (line 1282)
+* -u SYMBOL:                             Options.            (line  547)
+* -Ur:                                   Options.            (line  555)
+* -v:                                    Options.            (line  574)
+* -V:                                    Options.            (line  574)
+* -x:                                    Options.            (line  580)
+* -X:                                    Options.            (line  584)
+* -Y PATH:                               Options.            (line  599)
+* -y SYMBOL:                             Options.            (line  590)
+* -z defs:                               Options.            (line  987)
+* -z KEYWORD:                            Options.            (line  603)
+* -z muldefs:                            Options.            (line  995)
 * .:                                     Location Counter.   (line    6)
 * /DISCARD/:                             Output Section Discarding.
                                                              (line   21)
@@ -7503,84 +7449,87 @@ LD Index
                                                              (line    6)
 * [COMMON]:                              Input Section Common.
                                                              (line   29)
-* ABSOLUTE (MRI):                        MRI.                (line   33)
+* 'ABSOLUTE' (MRI):                      MRI.                (line   32)
 * absolute and relocatable symbols:      Expression Section. (line    6)
 * absolute expressions:                  Expression Section. (line    6)
 * ABSOLUTE(EXP):                         Builtin Functions.  (line   10)
 * ADDR(SECTION):                         Builtin Functions.  (line   17)
 * address, section:                      Output Section Address.
                                                              (line    6)
-* ALIAS (MRI):                           MRI.                (line   44)
-* ALIGN (MRI):                           MRI.                (line   50)
+* 'ALIAS' (MRI):                         MRI.                (line   43)
+* 'ALIGN' (MRI):                         MRI.                (line   49)
 * align expression:                      Builtin Functions.  (line   38)
 * align location counter:                Builtin Functions.  (line   38)
 * ALIGN(ALIGN):                          Builtin Functions.  (line   38)
 * ALIGN(EXP,ALIGN):                      Builtin Functions.  (line   38)
 * ALIGN(SECTION_ALIGN):                  Forced Output Alignment.
                                                              (line    6)
-* aligned common symbols:                WIN32.              (line  424)
+* aligned common symbols:                WIN32.              (line  415)
 * ALIGNOF(SECTION):                      Builtin Functions.  (line   63)
 * allocating memory:                     MEMORY.             (line    6)
 * architecture:                          Miscellaneous Commands.
                                                              (line   72)
-* architectures:                         Options.            (line  122)
-* archive files, from cmd line:          Options.            (line  335)
+* architectures:                         Options.            (line  121)
+* archive files, from cmd line:          Options.            (line  332)
 * archive search path in linker script:  File Commands.      (line   74)
 * arithmetic:                            Expressions.        (line    6)
 * arithmetic operators:                  Operators.          (line    6)
 * ARM interworking support:              ARM.                (line    6)
-* ARM1176 erratum workaround:            ARM.                (line  111)
-* AS_NEEDED(FILES):                      File Commands.      (line   54)
+* ARM1176 erratum workaround:            ARM.                (line  110)
 * ASSERT:                                Miscellaneous Commands.
                                                              (line    9)
 * assertion in linker script:            Miscellaneous Commands.
                                                              (line    9)
 * assignment in scripts:                 Assignments.        (line    6)
+* AS_NEEDED(FILES):                      File Commands.      (line   54)
 * AT(LMA):                               Output Section LMA. (line    6)
 * AT>LMA_REGION:                         Output Section LMA. (line    6)
-* automatic data imports:                WIN32.              (line  191)
+* automatic data imports:                WIN32.              (line  185)
 * back end:                              BFD.                (line    6)
-* BASE (MRI):                            MRI.                (line   54)
+* 'BASE' (MRI):                          MRI.                (line   53)
 * BE8:                                   ARM.                (line   28)
 * BFD canonical format:                  Canonical format.   (line   11)
 * BFD requirements:                      BFD.                (line   16)
-* big-endian objects:                    Options.            (line  248)
-* binary input format:                   Options.            (line  134)
+* big-endian objects:                    Options.            (line  247)
+* binary input format:                   Options.            (line  133)
 * BLOCK(EXP):                            Builtin Functions.  (line   76)
 * bug criteria:                          Bug Criteria.       (line    6)
 * bug reports:                           Bug Reporting.      (line    6)
-* bugs in ld:                            Reporting Bugs.     (line    6)
+* bugs in 'ld':                          Reporting Bugs.     (line    6)
 * BYTE(EXPRESSION):                      Output Section Data.
                                                              (line    6)
 * C++ constructors, arranging in link:   Output Section Keywords.
                                                              (line   19)
-* CHIP (MRI):                            MRI.                (line   58)
+* 'CHIP' (MRI):                          MRI.                (line   57)
 * COLLECT_NO_DEMANGLE:                   Environment.        (line   29)
-* combining symbols, warnings on:        Options.            (line 1371)
+* combining symbols, warnings on:        Options.            (line 1350)
 * command files:                         Scripts.            (line    6)
 * command line:                          Options.            (line    6)
-* common allocation:                     Options.            (line  168)
+* common allocation:                     Options.            (line  167)
+* common allocation <1>:                 Options.            (line  867)
 * common allocation in linker script:    Miscellaneous Commands.
                                                              (line   20)
+* common allocation in linker script <1>: Miscellaneous Commands.
+                                                             (line   25)
 * common symbol placement:               Input Section Common.
                                                              (line    6)
 * COMMONPAGESIZE:                        Symbolic Constants. (line   13)
-* compatibility, MRI:                    Options.            (line  158)
+* compatibility, MRI:                    Options.            (line  157)
 * CONSTANT:                              Symbolic Constants. (line    6)
 * constants in linker scripts:           Constants.          (line    6)
 * constraints on output sections:        Output Section Constraint.
                                                              (line    6)
+* constructors:                          Options.            (line  555)
 * CONSTRUCTORS:                          Output Section Keywords.
                                                              (line   19)
-* constructors:                          Options.            (line  562)
 * constructors, arranging in link:       Output Section Keywords.
                                                              (line   19)
-* Cortex-A8 erratum workaround:          i960.               (line   39)
+* Cortex-A8 erratum workaround:          i960.               (line   40)
 * crash of linker:                       Bug Criteria.       (line    9)
 * CREATE_OBJECT_SYMBOLS:                 Output Section Keywords.
                                                              (line    9)
-* creating a DEF file:                   WIN32.              (line  158)
-* cross reference table:                 Options.            (line  866)
+* creating a DEF file:                   WIN32.              (line  153)
+* cross reference table:                 Options.            (line  854)
 * cross references:                      Miscellaneous Commands.
                                                              (line   56)
 * current output location:               Location Counter.   (line    6)
@@ -7590,32 +7539,34 @@ LD Index
                                                              (line   81)
 * DATA_SEGMENT_END(EXP):                 Builtin Functions.  (line  102)
 * DATA_SEGMENT_RELRO_END(OFFSET, EXP):   Builtin Functions.  (line  108)
-* dbx:                                   Options.            (line 1286)
-* DEF files, creating:                   Options.            (line 1771)
+* dbx:                                   Options.            (line 1266)
+* DEF files, creating:                   Options.            (line 1756)
 * default emulation:                     Environment.        (line   21)
 * default input format:                  Environment.        (line    9)
 * DEFINED(SYMBOL):                       Builtin Functions.  (line  119)
-* deleting local symbols:                Options.            (line  587)
+* deleting local symbols:                Options.            (line  580)
 * demangling, default:                   Environment.        (line   29)
-* demangling, from command line:         Options.            (line  907)
-* direct linking to a dll:               WIN32.              (line  239)
+* demangling, from command line:         Options.            (line  896)
+* direct linking to a dll:               WIN32.              (line  233)
 * discarding sections:                   Output Section Discarding.
                                                              (line    6)
 * discontinuous memory:                  MEMORY.             (line    6)
-* DLLs, creating:                        Options.            (line 1673)
-* DLLs, linking to:                      Options.            (line 1802)
+* DLLs, creating:                        Options.            (line 1651)
+* DLLs, creating <1>:                    Options.            (line 1756)
+* DLLs, creating <2>:                    Options.            (line 1764)
+* DLLs, linking to:                      Options.            (line 1786)
 * dot:                                   Location Counter.   (line    6)
 * dot inside sections:                   Location Counter.   (line   36)
 * dot outside sections:                  Location Counter.   (line   66)
-* dynamic linker, from command line:     Options.            (line  920)
-* dynamic symbol table:                  Options.            (line  221)
+* dynamic linker, from command line:     Options.            (line  909)
+* dynamic symbol table:                  Options.            (line  220)
 * ELF program headers:                   PHDRS.              (line    6)
-* emulation:                             Options.            (line  392)
+* emulation:                             Options.            (line  389)
 * emulation, default:                    Environment.        (line   21)
-* END (MRI):                             MRI.                (line   62)
-* endianness:                            Options.            (line  248)
+* 'END' (MRI):                           MRI.                (line   61)
+* endianness:                            Options.            (line  247)
 * entry point:                           Entry Point.        (line    6)
-* entry point, from command line:        Options.            (line  187)
+* entry point, from command line:        Options.            (line  186)
 * entry point, thumb:                    ARM.                (line   17)
 * ENTRY(SYMBOL):                         Entry Point.        (line    6)
 * error on valid input:                  Bug Criteria.       (line   12)
@@ -7637,32 +7588,33 @@ LD Index
                                                              (line    6)
 * FILL(EXPRESSION):                      Output Section Data.
                                                              (line   39)
-* finalization function:                 Options.            (line  300)
+* finalization function:                 Options.            (line  298)
 * first input file:                      File Commands.      (line   82)
 * first instruction:                     Entry Point.        (line    6)
-* FIX_V4BX:                              ARM.                (line   49)
-* FIX_V4BX_INTERWORKING:                 ARM.                (line   62)
+* FIX_V4BX:                              ARM.                (line   47)
+* FIX_V4BX_INTERWORKING:                 ARM.                (line   60)
 * FORCE_COMMON_ALLOCATION:               Miscellaneous Commands.
                                                              (line   20)
 * forcing input section alignment:       Forced Input Alignment.
                                                              (line    6)
 * forcing output section alignment:      Forced Output Alignment.
                                                              (line    6)
-* forcing the creation of dynamic sections: Options.         (line  485)
-* FORMAT (MRI):                          MRI.                (line   66)
+* forcing the creation of dynamic sections: Options.         (line  479)
+* 'FORMAT' (MRI):                        MRI.                (line   65)
 * functions in expressions:              Builtin Functions.  (line    6)
-* garbage collection <1>:                Input Section Keep. (line    6)
-* garbage collection:                    Options.            (line  942)
-* generating optimized output:           Options.            (line  466)
+* garbage collection:                    Options.            (line  931)
+* garbage collection <1>:                Options.            (line  953)
+* garbage collection <2>:                Input Section Keep. (line    6)
+* generating optimized output:           Options.            (line  460)
 * GNU linker:                            Overview.           (line    6)
 * GNUTARGET:                             Environment.        (line    9)
 * GROUP(FILES):                          File Commands.      (line   47)
 * grouping input files:                  File Commands.      (line   47)
-* groups of archives:                    Options.            (line  710)
+* groups of archives:                    Options.            (line  699)
 * H8/300 support:                        H8/300.             (line    6)
-* header size:                           Builtin Functions.  (line  182)
-* heap size:                             Options.            (line 1713)
-* help:                                  Options.            (line  979)
+* header size:                           Builtin Functions.  (line  186)
+* heap size:                             Options.            (line 1691)
+* help:                                  Options.            (line  968)
 * HIDDEN:                                HIDDEN.             (line    6)
 * holes:                                 Location Counter.   (line   12)
 * holes, filling:                        Output Section Data.
@@ -7670,24 +7622,25 @@ LD Index
 * HPPA multiple sub-space stubs:         HPPA ELF32.         (line    6)
 * HPPA stub grouping:                    HPPA ELF32.         (line   12)
 * i960 support:                          i960.               (line    6)
-* image base:                            Options.            (line 1720)
+* image base:                            Options.            (line 1698)
 * implicit linker scripts:               Implicit Linker Scripts.
                                                              (line    6)
 * import libraries:                      WIN32.              (line   10)
 * INCLUDE FILENAME:                      File Commands.      (line    9)
 * including a linker script:             File Commands.      (line    9)
-* including an entire archive:           Options.            (line 1484)
-* incremental link:                      Options.            (line  326)
+* including an entire archive:           Options.            (line 1463)
+* incremental link:                      Options.            (line  323)
 * INHIBIT_COMMON_ALLOCATION:             Miscellaneous Commands.
                                                              (line   25)
-* initialization function:               Options.            (line  329)
+* initialization function:               Options.            (line  326)
 * initialized data in ROM:               Output Section LMA. (line   39)
 * input file format in linker script:    Format Commands.    (line   35)
 * input filename symbols:                Output Section Keywords.
                                                              (line    9)
 * input files in linker scripts:         File Commands.      (line   19)
-* input files, displaying:               Options.            (line  528)
-* input format:                          Options.            (line  134)
+* input files, displaying:               Options.            (line  521)
+* input format:                          Options.            (line  133)
+* input format <1>:                      Options.            (line  133)
 * input object files in linker scripts:  File Commands.      (line   19)
 * input section alignment:               Forced Input Alignment.
                                                              (line    6)
@@ -7707,19 +7660,19 @@ LD Index
 * invalid input:                         Bug Criteria.       (line   14)
 * K and M integer suffixes:              Constants.          (line   15)
 * KEEP:                                  Input Section Keep. (line    6)
-* l =:                                   MEMORY.             (line   74)
+* l =:                                   MEMORY.             (line   68)
 * lazy evaluation:                       Evaluation.         (line    6)
-* ld bugs, reporting:                    Bug Reporting.      (line    6)
+* 'ld' bugs, reporting:                  Bug Reporting.      (line    6)
+* ldata segment origin, cmd line:        Options.            (line 1299)
+* LDEMULATION:                           Environment.        (line   21)
 * LD_FEATURE(STRING):                    Miscellaneous Commands.
                                                              (line   78)
-* ldata segment origin, cmd line:        Options.            (line 1319)
-* LDEMULATION:                           Environment.        (line   21)
-* len =:                                 MEMORY.             (line   74)
-* LENGTH =:                              MEMORY.             (line   74)
+* len =:                                 MEMORY.             (line   68)
+* LENGTH =:                              MEMORY.             (line   68)
 * LENGTH(MEMORY):                        Builtin Functions.  (line  136)
 * library search path in linker script:  File Commands.      (line   74)
-* link map:                              Options.            (line  402)
-* link-time runtime library search path: Options.            (line 1173)
+* link map:                              Options.            (line  399)
+* link-time runtime library search path: Options.            (line 1160)
 * linker crash:                          Bug Criteria.       (line    9)
 * linker script concepts:                Basic Script Concepts.
                                                              (line    6)
@@ -7729,56 +7682,59 @@ LD Index
 * linker script input object files:      File Commands.      (line   19)
 * linker script simple commands:         Simple Commands.    (line    6)
 * linker scripts:                        Scripts.            (line    6)
-* LIST (MRI):                            MRI.                (line   77)
-* little-endian objects:                 Options.            (line  251)
-* LOAD (MRI):                            MRI.                (line   84)
+* 'LIST' (MRI):                          MRI.                (line   76)
+* little-endian objects:                 Options.            (line  250)
+* 'LOAD' (MRI):                          MRI.                (line   83)
 * load address:                          Output Section LMA. (line    6)
 * LOADADDR(SECTION):                     Builtin Functions.  (line  139)
 * loading, preventing:                   Output Section Type.
-                                                             (line   22)
-* local symbols, deleting:               Options.            (line  591)
+                                                             (line   21)
+* local symbols, deleting:               Options.            (line  584)
 * location counter:                      Location Counter.   (line    6)
+* LOG2CEIL(EXP):                         Builtin Functions.  (line  143)
 * LONG(EXPRESSION):                      Output Section Data.
                                                              (line    6)
 * M and K integer suffixes:              Constants.          (line   15)
-* M68HC11 and 68HC12 support:            M68HC11/68HC12.     (line    6)
+* M68HC11 and 68HC12 support:            M68HC11/68HC12.     (line    5)
 * machine architecture:                  Miscellaneous Commands.
                                                              (line   72)
 * machine dependencies:                  Machine Dependent.  (line    6)
 * mapping input sections to output sections: Input Section.  (line    6)
-* MAX:                                   Builtin Functions.  (line  142)
+* MAX:                                   Builtin Functions.  (line  146)
 * MAXPAGESIZE:                           Symbolic Constants. (line   10)
 * MEMORY:                                MEMORY.             (line    6)
 * memory region attributes:              MEMORY.             (line   34)
 * memory regions:                        MEMORY.             (line    6)
 * memory regions and sections:           Output Section Region.
                                                              (line    6)
-* memory usage:                          Options.            (line  991)
-* MIN:                                   Builtin Functions.  (line  145)
+* memory usage:                          Options.            (line  980)
+* MIN:                                   Builtin Functions.  (line  149)
+* MIPS microMIPS instruction choice selection: MIPS.         (line    6)
 * Motorola 68K GOT generation:           M68K.               (line    6)
 * MRI compatibility:                     MRI.                (line    6)
 * MSP430 extra sections:                 MSP430.             (line   11)
-* NAME (MRI):                            MRI.                (line   90)
+* 'NAME' (MRI):                          MRI.                (line   89)
 * name, section:                         Output Section Name.
                                                              (line    6)
 * names:                                 Symbols.            (line    6)
-* naming the output file:                Options.            (line  460)
-* NEXT(EXP):                             Builtin Functions.  (line  149)
-* NMAGIC:                                Options.            (line  439)
-* NO_ENUM_SIZE_WARNING:                  ARM.                (line  120)
-* NO_WCHAR_SIZE_WARNING:                 ARM.                (line  127)
+* naming the output file:                Options.            (line  454)
+* NEXT(EXP):                             Builtin Functions.  (line  153)
+* NMAGIC:                                Options.            (line  433)
 * NOCROSSREFS(SECTIONS):                 Miscellaneous Commands.
                                                              (line   56)
 * NOLOAD:                                Output Section Type.
-                                                             (line   22)
-* not enough room for program headers:   Builtin Functions.  (line  187)
-* o =:                                   MEMORY.             (line   69)
+                                                             (line   21)
+* not enough room for program headers:   Builtin Functions.  (line  191)
+* NO_ENUM_SIZE_WARNING:                  ARM.                (line  119)
+* NO_WCHAR_SIZE_WARNING:                 ARM.                (line  126)
+* o =:                                   MEMORY.             (line   63)
 * objdump -i:                            BFD.                (line    6)
 * object file management:                BFD.                (line    6)
 * object files:                          Options.            (line   29)
 * object formats available:              BFD.                (line    6)
-* object size:                           Options.            (line  309)
-* OMAGIC:                                Options.            (line  445)
+* object size:                           Options.            (line  307)
+* OMAGIC:                                Options.            (line  439)
+* OMAGIC <1>:                            Options.            (line  448)
 * ONLY_IF_RO:                            Output Section Constraint.
                                                              (line    6)
 * ONLY_IF_RW:                            Output Section Constraint.
@@ -7786,15 +7742,15 @@ LD Index
 * opening object files:                  BFD outline.        (line    6)
 * operators for arithmetic:              Operators.          (line    6)
 * options:                               Options.            (line    6)
-* ORDER (MRI):                           MRI.                (line   95)
-* org =:                                 MEMORY.             (line   69)
-* ORIGIN =:                              MEMORY.             (line   69)
-* ORIGIN(MEMORY):                        Builtin Functions.  (line  155)
+* 'ORDER' (MRI):                         MRI.                (line   94)
+* org =:                                 MEMORY.             (line   63)
+* ORIGIN =:                              MEMORY.             (line   63)
+* ORIGIN(MEMORY):                        Builtin Functions.  (line  159)
 * orphan:                                Orphan Sections.    (line    6)
-* output file after errors:              Options.            (line 1070)
+* output file after errors:              Options.            (line 1058)
 * output file format in linker script:   Format Commands.    (line   10)
 * output file name in linker script:     File Commands.      (line   64)
-* output format:                         Options.            (line  973)
+* output format:                         Options.            (line  962)
 * output section alignment:              Forced Output Alignment.
                                                              (line    6)
 * output section attributes:             Output Section Attributes.
@@ -7809,11 +7765,12 @@ LD Index
                                                              (line    6)
 * overlays:                              Overlay Description.
                                                              (line    6)
-* partial link:                          Options.            (line  489)
+* partial link:                          Options.            (line  483)
 * PE import table prefixing:             ARM.                (line   23)
 * PHDRS:                                 PHDRS.              (line    6)
-* PIC_VENEER:                            ARM.                (line  133)
-* position independent executables:      Options.            (line 1097)
+* PHDRS <1>:                             PHDRS.              (line   62)
+* PIC_VENEER:                            ARM.                (line  132)
+* position independent executables:      Options.            (line 1084)
 * PowerPC ELF32 options:                 PowerPC ELF32.      (line   16)
 * PowerPC GOT:                           PowerPC ELF32.      (line   33)
 * PowerPC long branches:                 PowerPC ELF32.      (line    6)
@@ -7835,59 +7792,60 @@ LD Index
 * PowerPC64 TOC sorting:                 PowerPC64 ELF64.    (line   86)
 * precedence in expressions:             Operators.          (line    6)
 * prevent unnecessary loading:           Output Section Type.
-                                                             (line   22)
+                                                             (line   21)
 * program headers:                       PHDRS.              (line    6)
 * program headers and sections:          Output Section Phdr.
                                                              (line    6)
-* program headers, not enough room:      Builtin Functions.  (line  187)
+* program headers, not enough room:      Builtin Functions.  (line  191)
 * program segments:                      PHDRS.              (line    6)
 * PROVIDE:                               PROVIDE.            (line    6)
 * PROVIDE_HIDDEN:                        PROVIDE_HIDDEN.     (line    6)
-* PUBLIC (MRI):                          MRI.                (line  103)
+* 'PUBLIC' (MRI):                        MRI.                (line  102)
 * QUAD(EXPRESSION):                      Output Section Data.
                                                              (line    6)
 * quoted symbol names:                   Symbols.            (line    6)
-* read-only text:                        Options.            (line  439)
-* read/write from cmd line:              Options.            (line  445)
+* read-only text:                        Options.            (line  433)
+* read/write from cmd line:              Options.            (line  439)
 * region alias:                          REGION_ALIAS.       (line    6)
 * region names:                          REGION_ALIAS.       (line    6)
-* REGION_ALIAS(ALIAS, REGION):           REGION_ALIAS.       (line    6)
 * regions of memory:                     MEMORY.             (line    6)
+* REGION_ALIAS(ALIAS, REGION):           REGION_ALIAS.       (line    6)
 * relative expressions:                  Expression Section. (line    6)
-* relaxing addressing modes:             Options.            (line 1111)
+* relaxing addressing modes:             Options.            (line 1098)
 * relaxing on H8/300:                    H8/300.             (line    9)
-* relaxing on i960:                      i960.               (line   31)
+* relaxing on i960:                      i960.               (line   32)
 * relaxing on M68HC11:                   M68HC11/68HC12.     (line   12)
 * relaxing on Xtensa:                    Xtensa.             (line   27)
 * relocatable and absolute symbols:      Expression Section. (line    6)
-* relocatable output:                    Options.            (line  489)
+* relocatable output:                    Options.            (line  483)
 * removing sections:                     Output Section Discarding.
                                                              (line    6)
-* reporting bugs in ld:                  Reporting Bugs.     (line    6)
+* reporting bugs in 'ld':                Reporting Bugs.     (line    6)
 * requirements for BFD:                  BFD.                (line   16)
-* retain relocations in final executable: Options.           (line  476)
-* retaining specified symbols:           Options.            (line 1137)
-* rodata segment origin, cmd line:       Options.            (line 1313)
+* retain relocations in final executable: Options.           (line  470)
+* retaining specified symbols:           Options.            (line 1124)
+* rodata segment origin, cmd line:       Options.            (line 1293)
 * ROM initialized data:                  Output Section LMA. (line   39)
 * round up expression:                   Builtin Functions.  (line   38)
 * round up location counter:             Builtin Functions.  (line   38)
-* runtime library name:                  Options.            (line  317)
-* runtime library search path:           Options.            (line 1151)
-* runtime pseudo-relocation:             WIN32.              (line  217)
+* runtime library name:                  Options.            (line  314)
+* runtime library search path:           Options.            (line 1138)
+* runtime pseudo-relocation:             WIN32.              (line  211)
 * scaled integers:                       Constants.          (line   15)
 * scommon section:                       Input Section Common.
                                                              (line   20)
-* script files:                          Options.            (line  532)
+* script files:                          Options.            (line  525)
+* script files <1>:                      Options.            (line  534)
 * scripts:                               Scripts.            (line    6)
-* search directory, from cmd line:       Options.            (line  368)
+* search directory, from cmd line:       Options.            (line  365)
 * search path in linker script:          File Commands.      (line   74)
 * SEARCH_DIR(PATH):                      File Commands.      (line   74)
-* SECT (MRI):                            MRI.                (line  109)
+* 'SECT' (MRI):                          MRI.                (line  108)
 * section address:                       Output Section Address.
                                                              (line    6)
 * section address in expression:         Builtin Functions.  (line   17)
 * section alignment:                     Builtin Functions.  (line   63)
-* section alignment, warnings on:        Options.            (line 1462)
+* section alignment, warnings on:        Options.            (line 1441)
 * section data:                          Output Section Data.
                                                              (line    6)
 * section fill pattern:                  Output Section Fill.
@@ -7898,7 +7856,7 @@ LD Index
                                                              (line    6)
 * section name wildcard patterns:        Input Section Wildcards.
                                                              (line    6)
-* section size:                          Builtin Functions.  (line  166)
+* section size:                          Builtin Functions.  (line  170)
 * section, assigning to memory region:   Output Section Region.
                                                              (line    6)
 * section, assigning to program header:  Output Section Phdr.
@@ -7906,27 +7864,28 @@ LD Index
 * SECTIONS:                              SECTIONS.           (line    6)
 * sections, discarding:                  Output Section Discarding.
                                                              (line    6)
-* segment origins, cmd line:             Options.            (line 1302)
-* SEGMENT_START(SEGMENT, DEFAULT):       Builtin Functions.  (line  158)
+* segment origins, cmd line:             Options.            (line 1282)
 * segments, ELF:                         PHDRS.              (line    6)
-* shared libraries:                      Options.            (line 1230)
+* SEGMENT_START(SEGMENT, DEFAULT):       Builtin Functions.  (line  162)
+* shared libraries:                      Options.            (line 1210)
 * SHORT(EXPRESSION):                     Output Section Data.
                                                              (line    6)
-* SIZEOF(SECTION):                       Builtin Functions.  (line  166)
-* SIZEOF_HEADERS:                        Builtin Functions.  (line  182)
+* SIZEOF(SECTION):                       Builtin Functions.  (line  170)
+* SIZEOF_HEADERS:                        Builtin Functions.  (line  186)
 * small common symbols:                  Input Section Common.
                                                              (line   20)
 * SORT:                                  Input Section Wildcards.
-                                                             (line   63)
+                                                             (line   62)
 * SORT_BY_ALIGNMENT:                     Input Section Wildcards.
-                                                             (line   54)
+                                                             (line   51)
 * SORT_BY_INIT_PRIORITY:                 Input Section Wildcards.
-                                                             (line   58)
+                                                             (line   57)
 * SORT_BY_NAME:                          Input Section Wildcards.
-                                                             (line   46)
+                                                             (line   43)
 * SORT_NONE:                             Input Section Wildcards.
-                                                             (line  104)
+                                                             (line   98)
 * SPU:                                   SPU ELF.            (line   29)
+* SPU <1>:                               SPU ELF.            (line   46)
 * SPU ELF options:                       SPU ELF.            (line    6)
 * SPU extra overlay stubs:               SPU ELF.            (line   19)
 * SPU local store size:                  SPU ELF.            (line   24)
@@ -7935,155 +7894,156 @@ LD Index
 * SPU plugins:                           SPU ELF.            (line    6)
 * SQUAD(EXPRESSION):                     Output Section Data.
                                                              (line    6)
-* stack size:                            Options.            (line 1960)
+* stack size:                            Options.            (line 1943)
 * standard Unix system:                  Options.            (line    7)
 * start of execution:                    Entry Point.        (line    6)
 * STARTUP(FILENAME):                     File Commands.      (line   82)
-* strip all symbols:                     Options.            (line  519)
-* strip debugger symbols:                Options.            (line  523)
-* stripping all but some symbols:        Options.            (line 1137)
-* STUB_GROUP_SIZE:                       ARM.                (line  138)
+* strip all symbols:                     Options.            (line  512)
+* strip debugger symbols:                Options.            (line  516)
+* stripping all but some symbols:        Options.            (line 1124)
+* STUB_GROUP_SIZE:                       ARM.                (line  137)
 * SUBALIGN(SUBSECTION_ALIGN):            Forced Input Alignment.
                                                              (line    6)
 * suffixes for integers:                 Constants.          (line   15)
 * symbol defaults:                       Builtin Functions.  (line  119)
 * symbol definition, scripts:            Assignments.        (line    6)
 * symbol names:                          Symbols.            (line    6)
-* symbol tracing:                        Options.            (line  597)
+* symbol tracing:                        Options.            (line  590)
 * symbol versions:                       VERSION.            (line    6)
-* symbol-only input:                     Options.            (line  508)
+* symbol-only input:                     Options.            (line  501)
 * symbolic constants:                    Symbolic Constants. (line    6)
-* symbols, from command line:            Options.            (line  894)
+* symbols, from command line:            Options.            (line  883)
 * symbols, relocatable and absolute:     Expression Section. (line    6)
-* symbols, retaining selectively:        Options.            (line 1137)
-* synthesizing linker:                   Options.            (line 1111)
+* symbols, retaining selectively:        Options.            (line 1124)
+* synthesizing linker:                   Options.            (line 1098)
 * synthesizing on H8/300:                H8/300.             (line   14)
 * TARGET(BFDNAME):                       Format Commands.    (line   35)
 * TARGET1:                               ARM.                (line   32)
 * TARGET2:                               ARM.                (line   37)
-* text segment origin, cmd line:         Options.            (line 1309)
+* text segment origin, cmd line:         Options.            (line 1289)
 * thumb entry point:                     ARM.                (line   17)
 * TI COFF versions:                      TI COFF.            (line    6)
-* traditional format:                    Options.            (line 1281)
-* trampoline generation on M68HC11:      M68HC11/68HC12.     (line   31)
-* trampoline generation on M68HC12:      M68HC11/68HC12.     (line   31)
-* unallocated address, next:             Builtin Functions.  (line  149)
-* undefined symbol:                      Options.            (line  554)
+* traditional format:                    Options.            (line 1261)
+* trampoline generation on M68HC11:      M68HC11/68HC12.     (line   30)
+* trampoline generation on M68HC12:      M68HC11/68HC12.     (line   30)
+* unallocated address, next:             Builtin Functions.  (line  153)
+* undefined symbol:                      Options.            (line  547)
 * undefined symbol in linker script:     Miscellaneous Commands.
                                                              (line   13)
-* undefined symbols, warnings on:        Options.            (line 1458)
+* undefined symbols, warnings on:        Options.            (line 1437)
 * uninitialized data placement:          Input Section Common.
                                                              (line    6)
 * unspecified memory:                    Output Section Data.
                                                              (line   39)
-* usage:                                 Options.            (line  979)
-* USE_BLX:                               ARM.                (line   74)
-* using a DEF file:                      WIN32.              (line   57)
+* usage:                                 Options.            (line  968)
+* USE_BLX:                               ARM.                (line   72)
+* using a DEF file:                      WIN32.              (line   52)
 * using auto-export functionality:       WIN32.              (line   22)
-* Using decorations:                     WIN32.              (line  162)
+* Using decorations:                     WIN32.              (line  157)
 * variables, defining:                   Assignments.        (line    6)
-* verbose[=NUMBER]:                      Options.            (line 1352)
-* version:                               Options.            (line  581)
+* verbose[=NUMBER]:                      Options.            (line 1332)
+* version:                               Options.            (line  574)
 * version script:                        VERSION.            (line    6)
-* version script, symbol versions:       Options.            (line 1360)
+* version script, symbol versions:       Options.            (line 1340)
 * VERSION {script text}:                 VERSION.            (line    6)
 * versions of symbols:                   VERSION.            (line    6)
-* VFP11_DENORM_FIX:                      ARM.                (line   83)
-* warnings, on combining symbols:        Options.            (line 1371)
-* warnings, on section alignment:        Options.            (line 1462)
-* warnings, on undefined symbols:        Options.            (line 1458)
-* weak externals:                        WIN32.              (line  407)
+* VFP11_DENORM_FIX:                      ARM.                (line   81)
+* warnings, on combining symbols:        Options.            (line 1350)
+* warnings, on section alignment:        Options.            (line 1441)
+* warnings, on undefined symbols:        Options.            (line 1437)
+* weak externals:                        WIN32.              (line  400)
 * what is this?:                         Overview.           (line    6)
 * wildcard file name patterns:           Input Section Wildcards.
                                                              (line    6)
-* Xtensa options:                        Xtensa.             (line   56)
+* Xtensa options:                        Xtensa.             (line   55)
 * Xtensa processors:                     Xtensa.             (line    6)
 
 
 
 Tag Table:
-Node: Top840
-Node: Overview1636
-Node: Invocation2750
-Node: Options3158
-Node: Environment96090
-Node: Scripts97850
-Node: Basic Script Concepts99584
-Node: Script Format102292
-Node: Simple Example103155
-Node: Simple Commands106251
-Node: Entry Point106757
-Node: File Commands107690
-Node: Format Commands111691
-Node: REGION_ALIAS113647
-Node: Miscellaneous Commands118479
-Node: Assignments122087
-Node: Simple Assignments122598
-Node: HIDDEN124333
-Node: PROVIDE124963
-Node: PROVIDE_HIDDEN126156
-Node: Source Code Reference126400
-Node: SECTIONS129980
-Node: Output Section Description131871
-Node: Output Section Name132958
-Node: Output Section Address133834
-Node: Input Section136069
-Node: Input Section Basics136870
-Node: Input Section Wildcards140776
-Node: Input Section Common145870
-Node: Input Section Keep147352
-Node: Input Section Example147842
-Node: Output Section Data148810
-Node: Output Section Keywords151587
-Node: Output Section Discarding155156
-Node: Output Section Attributes156337
-Node: Output Section Type157438
-Node: Output Section LMA158509
-Node: Forced Output Alignment161580
-Node: Forced Input Alignment161848
-Node: Output Section Constraint162237
-Node: Output Section Region162665
-Node: Output Section Phdr163098
-Node: Output Section Fill163762
-Node: Overlay Description164904
-Node: MEMORY169211
-Node: PHDRS173545
-Node: VERSION178799
-Node: Expressions186892
-Node: Constants187821
-Node: Symbolic Constants188696
-Node: Symbols189247
-Node: Orphan Sections189994
-Node: Location Counter191159
-Node: Operators195595
-Node: Evaluation196517
-Node: Expression Section197881
-Node: Builtin Functions201745
-Node: Implicit Linker Scripts209701
-Node: Machine Dependent210476
-Node: H8/300211492
-Node: i960213554
-Node: M68HC11/68HC12215769
-Node: ARM217211
-Node: HPPA ELF32225185
-Node: M68K226808
-Node: MMIX227717
-Node: MSP430228882
-Node: PowerPC ELF32229930
-Node: PowerPC64 ELF64232758
-Node: SPU ELF238914
-Node: TI COFF241546
-Node: WIN32242072
-Node: Xtensa262197
-Node: BFD265162
-Node: BFD outline266617
-Node: BFD information loss267903
-Node: Canonical format270420
-Node: Reporting Bugs274777
-Node: Bug Criteria275471
-Node: Bug Reporting276170
-Node: MRI283240
-Node: GNU Free Documentation License287883
-Node: LD Index313039
+Node: Top708
+Node: Overview1491
+Node: Invocation2607
+Node: Options3015
+Node: Environment97116
+Node: Scripts98877
+Node: Basic Script Concepts100611
+Node: Script Format103319
+Node: Simple Example104182
+Node: Simple Commands107276
+Node: Entry Point107781
+Node: File Commands108709
+Node: Format Commands112711
+Node: REGION_ALIAS114667
+Node: Miscellaneous Commands119494
+Node: Assignments123102
+Node: Simple Assignments123613
+Node: HIDDEN125344
+Node: PROVIDE125971
+Node: PROVIDE_HIDDEN127164
+Node: Source Code Reference127408
+Node: SECTIONS130990
+Node: Output Section Description132878
+Node: Output Section Name133981
+Node: Output Section Address134858
+Node: Input Section137091
+Node: Input Section Basics137892
+Node: Input Section Wildcards141791
+Node: Input Section Common146992
+Node: Input Section Keep148474
+Node: Input Section Example148964
+Node: Output Section Data149932
+Node: Output Section Keywords152711
+Node: Output Section Discarding156278
+Node: Output Section Attributes157456
+Node: Output Section Type158556
+Node: Output Section LMA159626
+Node: Forced Output Alignment162697
+Node: Forced Input Alignment163213
+Node: Output Section Constraint163601
+Node: Output Section Region164029
+Node: Output Section Phdr164462
+Node: Output Section Fill165126
+Node: Overlay Description166268
+Node: MEMORY170575
+Node: PHDRS174903
+Node: VERSION180157
+Node: Expressions188248
+Node: Constants189177
+Node: Symbolic Constants190051
+Node: Symbols190602
+Node: Orphan Sections191349
+Node: Location Counter192514
+Node: Operators196948
+Node: Evaluation197870
+Node: Expression Section199234
+Node: Builtin Functions203089
+Node: Implicit Linker Scripts211171
+Node: Machine Dependent211946
+Node: H8/300212984
+Node: i960215047
+Node: M68HC11/68HC12217262
+Node: ARM218707
+Node: HPPA ELF32226687
+Node: M68K228310
+Node: MIPS229219
+Node: MMIX229743
+Node: MSP430230908
+Node: PowerPC ELF32231956
+Node: PowerPC64 ELF64234786
+Node: SPU ELF240940
+Node: TI COFF243574
+Node: WIN32244100
+Node: Xtensa264229
+Node: BFD267195
+Node: BFD outline268653
+Node: BFD information loss269941
+Node: Canonical format272467
+Node: Reporting Bugs276829
+Node: Bug Criteria277523
+Node: Bug Reporting278222
+Node: MRI285260
+Node: GNU Free Documentation License289902
+Node: LD Index315038
 
 End Tag Table
diff --git a/share/info/standards.info b/share/info/standards.info
index 0c5f3da..2d39178 100644
--- a/share/info/standards.info
+++ b/share/info/standards.info
@@ -1,5 +1,5 @@
-This is standards.info, produced by makeinfo version 4.13 from
-/mnt/jenkins/workspace/linaro-android_toolchain64-4.9-2014.09/build/objdir/../build/../binutils/binutils-current/etc/standards.texi.
+This is standards.info, produced by makeinfo version 4.8 from
+./standards.texi.
 
 INFO-DIR-SECTION GNU organization
 START-INFO-DIR-ENTRY
@@ -3155,7 +3155,7 @@ the functions, variables, options, and important concepts that are part
 of the program.  One combined Index should do for a short manual, but
 sometimes for a complex package it is better to use multiple indices.
 The Texinfo manual includes advice on preparing good index entries, see
-*note Making Index Entries: (texinfo)Index Entries, and see *note
+*Note Making Index Entries: (texinfo)Index Entries, and see *Note
 Defining the Entries of an Index: (texinfo)Indexing Commands.
 
    Don't use Unix man pages as a model for how to write GNU
@@ -4294,8 +4294,8 @@ have Info files, so every program needs `infodir', but not all need
 
 `lispdir'
      The directory for installing any Emacs Lisp files in this package.
-     By default, it should be `/usr/local/share/emacs/site-lisp', but it
-     should be written as `$(datarootdir)/emacs/site-lisp'.
+     By default, it should be `/usr/local/share/emacs/site-lisp', but
+     it should be written as `$(datarootdir)/emacs/site-lisp'.
 
      If you are using Autoconf, write the default as `@lispdir@'.  In
      order to make `@lispdir@' work, you need the following lines in
@@ -5671,74 +5671,74 @@ Index
 
 
 Tag Table:
-Node: Top930
-Node: Preface2205
-Node: Legal Issues4918
-Node: Reading Non-Free Code5388
-Node: Contributions7118
-Node: Trademarks9356
-Node: Design Advice10991
-Node: Source Language11583
-Node: Compatibility13709
-Node: Using Extensions15337
-Node: Standard C16913
-Node: Conditional Compilation19316
-Node: Program Behavior20714
-Node: Non-GNU Standards21830
-Node: Semantics24111
-Node: Libraries28831
-Node: Errors30076
-Node: User Interfaces32569
-Node: Graphical Interfaces34174
-Node: Command-Line Interfaces35358
-Node: --version37390
-Node: --help43127
-Node: Option Table44000
-Node: OID Allocations58955
-Node: Memory Usage60752
-Node: File Usage61788
-Node: Writing C62538
-Node: Formatting63510
-Node: Comments67799
-Node: Syntactic Conventions71351
-Node: Names74813
-Node: System Portability77025
-Node: CPU Portability79916
-Node: System Functions83817
-Node: Internationalization89014
-Node: Character Set93008
-Node: Quote Characters93821
-Node: Mmap95341
-Node: Documentation96049
-Node: GNU Manuals97155
-Node: Doc Strings and Manuals102893
-Node: Manual Structure Details104446
-Node: License for Manuals105864
-Node: Manual Credits106838
-Node: Printed Manuals107231
-Node: NEWS File107917
-Node: Change Logs108595
-Node: Change Log Concepts109349
-Node: Style of Change Logs111452
-Node: Simple Changes113952
-Node: Conditional Changes115394
-Node: Indicating the Part Changed116816
-Node: Man Pages117343
-Node: Reading other Manuals119549
-Node: Managing Releases120340
-Node: Configuration121121
-Node: Makefile Conventions129786
-Node: Makefile Basics130668
-Node: Utilities in Makefiles133842
-Node: Command Variables135987
-Node: DESTDIR139209
-Node: Directory Variables141358
-Node: Standard Targets155851
-Ref: Standard Targets-Footnote-1169366
-Node: Install Command Categories169466
-Node: Releases173999
-Node: References178004
-Node: GNU Free Documentation License183851
-Node: Index209018
+Node: Top814
+Node: Preface2089
+Node: Legal Issues4802
+Node: Reading Non-Free Code5272
+Node: Contributions7002
+Node: Trademarks9240
+Node: Design Advice10875
+Node: Source Language11467
+Node: Compatibility13593
+Node: Using Extensions15221
+Node: Standard C16797
+Node: Conditional Compilation19200
+Node: Program Behavior20598
+Node: Non-GNU Standards21714
+Node: Semantics23995
+Node: Libraries28715
+Node: Errors29960
+Node: User Interfaces32453
+Node: Graphical Interfaces34058
+Node: Command-Line Interfaces35242
+Node: --version37274
+Node: --help43011
+Node: Option Table43884
+Node: OID Allocations58839
+Node: Memory Usage60636
+Node: File Usage61672
+Node: Writing C62422
+Node: Formatting63394
+Node: Comments67683
+Node: Syntactic Conventions71235
+Node: Names74697
+Node: System Portability76909
+Node: CPU Portability79800
+Node: System Functions83701
+Node: Internationalization88898
+Node: Character Set92892
+Node: Quote Characters93705
+Node: Mmap95225
+Node: Documentation95933
+Node: GNU Manuals97039
+Node: Doc Strings and Manuals102777
+Node: Manual Structure Details104330
+Node: License for Manuals105748
+Node: Manual Credits106722
+Node: Printed Manuals107115
+Node: NEWS File107801
+Node: Change Logs108479
+Node: Change Log Concepts109233
+Node: Style of Change Logs111336
+Node: Simple Changes113836
+Node: Conditional Changes115278
+Node: Indicating the Part Changed116700
+Node: Man Pages117227
+Node: Reading other Manuals119433
+Node: Managing Releases120224
+Node: Configuration121005
+Node: Makefile Conventions129670
+Node: Makefile Basics130552
+Node: Utilities in Makefiles133726
+Node: Command Variables135871
+Node: DESTDIR139093
+Node: Directory Variables141242
+Node: Standard Targets155735
+Ref: Standard Targets-Footnote-1169250
+Node: Install Command Categories169350
+Node: Releases173883
+Node: References177888
+Node: GNU Free Documentation License183735
+Node: Index208902
 
 End Tag Table
diff --git a/share/man/man1/aarch64-linux-android-addr2line.1 b/share/man/man1/aarch64-linux-android-addr2line.1
index 6cdf2c8..1645978 100644
--- a/share/man/man1/aarch64-linux-android-addr2line.1
+++ b/share/man/man1/aarch64-linux-android-addr2line.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ADDR2LINE 1"
-.TH ADDR2LINE 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH ADDR2LINE 1 "2014-08-29" "binutils-2.24.0" "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 --git a/share/man/man1/aarch64-linux-android-ar.1 b/share/man/man1/aarch64-linux-android-ar.1
index 9e4de53..6084bdb 100644
--- a/share/man/man1/aarch64-linux-android-ar.1
+++ b/share/man/man1/aarch64-linux-android-ar.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "AR 1"
-.TH AR 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH AR 1 "2014-08-29" "binutils-2.24.0" "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
@@ -136,7 +145,7 @@ ar \- create, modify, and extract from archives
 ar [\fB\-\-plugin\fR \fIname\fR] [\fB\-X32_64\fR] [\fB\-\fR]\fIp\fR[\fImod\fR [\fIrelpos\fR] [\fIcount\fR]] [\fB\-\-target\fR \fIbfdname\fR] \fIarchive\fR [\fImember\fR...]
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-The \s-1GNU\s0 \fBar\fR program creates, modifies, and extracts from
+The \s-1GNU \s0\fBar\fR program creates, modifies, and extracts from
 archives.  An \fIarchive\fR is a single file holding a collection of
 other files in a structure that makes it possible to retrieve
 the original individual files (called \fImembers\fR of the archive).
@@ -145,7 +154,7 @@ The original files' contents, mode (permissions), timestamp, owner, and
 group are preserved in the archive, and can be restored on
 extraction.
 .PP
-\&\s-1GNU\s0 \fBar\fR can maintain archives whose members have names of any
+\&\s-1GNU \s0\fBar\fR can maintain archives whose members have names of any
 length; however, depending on how \fBar\fR is configured on your
 system, a limit on member-name length may be imposed for compatibility
 with archive formats maintained with other tools.  If it exists, the
@@ -168,7 +177,7 @@ You may use \fBnm \-s\fR or \fBnm \-\-print\-armap\fR to list this index
 table.  If an archive lacks the table, another form of \fBar\fR called
 \&\fBranlib\fR can be used to add just the table.
 .PP
-\&\s-1GNU\s0 \fBar\fR can optionally create a \fIthin\fR archive,
+\&\s-1GNU \s0\fBar\fR can optionally create a \fIthin\fR archive,
 which contains a symbol index and references to the original copies
 of the member files of the archive.  This is useful for building
 libraries for use within a local build tree, where the relocatable
@@ -188,15 +197,15 @@ individually to the second archive.
 The paths to the elements of the archive are stored relative to the
 archive itself.
 .PP
-\&\s-1GNU\s0 \fBar\fR is designed to be compatible with two different
+\&\s-1GNU \s0\fBar\fR is designed to be compatible with two different
 facilities.  You can control its activity using command-line options,
 like the different varieties of \fBar\fR on Unix systems; or, if you
 specify the single command-line option \fB\-M\fR, you can control it
-with a script supplied via standard input, like the \s-1MRI\s0 \*(L"librarian\*(R"
+with a script supplied via standard input, like the \s-1MRI \s0\*(L"librarian\*(R"
 program.
 .SH "OPTIONS"
 .IX Header "OPTIONS"
-\&\s-1GNU\s0 \fBar\fR allows you to mix the operation code \fIp\fR and modifier
+\&\s-1GNU \s0\fBar\fR allows you to mix the operation code \fIp\fR and modifier
 flags \fImod\fR in any order, within the first command-line argument.
 .PP
 If you wish, you may begin the first command-line argument with a
@@ -242,12 +251,15 @@ operation; new members are always placed at the end of the archive.
 .Sp
 The modifier \fBv\fR makes \fBar\fR list each file as it is appended.
 .Sp
-Since the point of this operation is speed, the archive's symbol table
-index is not updated, even if it already existed; you can use \fBar s\fR or
-\&\fBranlib\fR explicitly to update the symbol table index.
+Since the point of this operation is speed, implementations of
+\&\fBar\fR have the option of not updating the archive's symbol
+table if one exists.  Too many different systems however assume that
+symbol tables are always up-to-date, so \s-1GNU \s0\fBar\fR will
+rebuild the table even with a quick append.
 .Sp
-However, too many different systems assume quick append rebuilds the
-index, so \s-1GNU\s0 \fBar\fR implements \fBq\fR as a synonym for \fBr\fR.
+Note \- \s-1GNU \s0\fBar\fR treats the command \fBqs\fR as a
+synonym for \fBr\fR \- replacing already existing files in the
+archive and appending new ones at the end.
 .IP "\fBr\fR" 4
 .IX Item "r"
 Insert the files \fImember\fR... into \fIarchive\fR (with
@@ -340,7 +352,7 @@ If \fIbinutils\fR was configured with
 It can be disabled with the \fBU\fR modifier, below.
 .IP "\fBf\fR" 4
 .IX Item "f"
-Truncate names in the archive.  \s-1GNU\s0 \fBar\fR will normally permit file
+Truncate names in the archive.  \s-1GNU \s0\fBar\fR will normally permit file
 names of any length.  This will cause it to create archives which are
 not compatible with the native \fBar\fR program on some systems.  If
 this is a concern, the \fBf\fR modifier may be used to truncate file
@@ -366,10 +378,10 @@ you do not specify this modifier, files extracted from the archive
 are stamped with the time of extraction.
 .IP "\fBP\fR" 4
 .IX Item "P"
-Use the full path name when matching names in the archive.  \s-1GNU\s0
-\&\fBar\fR can not create an archive with a full path name (such archives
+Use the full path name when matching names in the archive.  \s-1GNU
+\&\s0\fBar\fR can not create an archive with a full path name (such archives
 are not \s-1POSIX\s0 complaint), but other archive creators can.  This option
-will cause \s-1GNU\s0 \fBar\fR to match file names using a complete path
+will cause \s-1GNU \s0\fBar\fR to match file names using a complete path
 name, which can be convenient when extracting a single file from an
 archive created by another tool.
 .IP "\fBs\fR" 4
@@ -403,7 +415,7 @@ advantage from the operation \fBq\fR.
 .IX Item "U"
 Do \fInot\fR operate in \fIdeterministic\fR mode.  This is the inverse
 of the \fBD\fR modifier, above: added files and the archive index will
-get their actual \s-1UID\s0, \s-1GID\s0, timestamp, and file mode values.
+get their actual \s-1UID, GID,\s0 timestamp, and file mode values.
 .Sp
 This is the default unless \fIbinutils\fR was configured with
 \&\fB\-\-enable\-deterministic\-archives\fR.
@@ -417,10 +429,10 @@ when the modifier \fBv\fR is appended.
 This modifier shows the version number of \fBar\fR.
 .PP
 \&\fBar\fR ignores an initial option spelt \fB\-X32_64\fR, for
-compatibility with \s-1AIX\s0.  The behaviour produced by this option is the
-default for \s-1GNU\s0 \fBar\fR.  \fBar\fR does not support any of the other
+compatibility with \s-1AIX. \s0 The behaviour produced by this option is the
+default for \s-1GNU \s0\fBar\fR.  \fBar\fR does not support any of the other
 \&\fB\-X\fR options; in particular, it does not support \fB\-X32\fR
-which is the default for \s-1AIX\s0 \fBar\fR.
+which is the default for \s-1AIX \s0\fBar\fR.
 .PP
 The optional command line switch \fB\-\-plugin\fR \fIname\fR causes
 \&\fBar\fR to load the plugin called \fIname\fR which adds support
diff --git a/share/man/man1/aarch64-linux-android-as.1 b/share/man/man1/aarch64-linux-android-as.1
index ed9fb3d..f0ade69 100644
--- a/share/man/man1/aarch64-linux-android-as.1
+++ b/share/man/man1/aarch64-linux-android-as.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "AS 1"
-.TH AS 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH AS 1 "2014-08-29" "binutils-2.24.0" "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
@@ -137,7 +146,8 @@ as [\fB\-a\fR[\fBcdghlns\fR][=\fIfile\fR]] [\fB\-\-alternate\fR] [\fB\-D\fR]
  [\fB\-\-compress\-debug\-sections\fR]  [\fB\-\-nocompress\-debug\-sections\fR]
  [\fB\-\-debug\-prefix\-map\fR \fIold\fR=\fInew\fR]
  [\fB\-\-defsym\fR \fIsym\fR=\fIval\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-\-gstabs\fR]
- [\fB\-\-gstabs+\fR] [\fB\-\-gdwarf\-2\fR] [\fB\-\-help\fR] [\fB\-I\fR \fIdir\fR] [\fB\-J\fR]
+ [\fB\-\-gstabs+\fR] [\fB\-\-gdwarf\-2\fR] [\fB\-\-gdwarf\-sections\fR]
+ [\fB\-\-help\fR] [\fB\-I\fR \fIdir\fR] [\fB\-J\fR]
  [\fB\-K\fR] [\fB\-L\fR] [\fB\-\-listing\-lhs\-width\fR=\fI\s-1NUM\s0\fR]
  [\fB\-\-listing\-lhs\-width2\fR=\fI\s-1NUM\s0\fR] [\fB\-\-listing\-rhs\-width\fR=\fI\s-1NUM\s0\fR]
  [\fB\-\-listing\-cont\-lines\fR=\fI\s-1NUM\s0\fR] [\fB\-\-keep\-locals\fR] [\fB\-o\fR
@@ -150,6 +160,7 @@ as [\fB\-a\fR[\fBcdghlns\fR][=\fIfile\fR]] [\fB\-\-alternate\fR] [\fB\-D\fR]
 .PP
 \&\fITarget AArch64 options:\fR
    [\fB\-EB\fR|\fB\-EL\fR]
+   [\fB\-mabi\fR=\fI\s-1ABI\s0\fR]
 .PP
 \&\fITarget Alpha options:\fR
    [\fB\-m\fR\fIcpu\fR]
@@ -254,6 +265,7 @@ as [\fB\-a\fR[\fBcdghlns\fR][=\fIfile\fR]] [\fB\-\-alternate\fR] [\fB\-D\fR]
    [\fB\-mips3\fR] [\fB\-mips4\fR] [\fB\-mips5\fR] [\fB\-mips32\fR] [\fB\-mips32r2\fR]
    [\fB\-mips64\fR] [\fB\-mips64r2\fR]
    [\fB\-construct\-floats\fR] [\fB\-no\-construct\-floats\fR]
+   [\fB\-mnan=\fR\fIencoding\fR]
    [\fB\-trap\fR] [\fB\-no\-break\fR] [\fB\-break\fR] [\fB\-no\-trap\fR]
    [\fB\-mips16\fR] [\fB\-no\-mips16\fR]
    [\fB\-mmicromips\fR] [\fB\-mno\-micromips\fR]
@@ -264,6 +276,7 @@ as [\fB\-a\fR[\fBcdghlns\fR][=\fIfile\fR]] [\fB\-\-alternate\fR] [\fB\-D\fR]
    [\fB\-mdspr2\fR] [\fB\-mno\-dspr2\fR]
    [\fB\-mmt\fR] [\fB\-mno\-mt\fR]
    [\fB\-mmcu\fR] [\fB\-mno\-mcu\fR]
+   [\fB\-minsn32\fR] [\fB\-mno\-insn32\fR]
    [\fB\-mfix7000\fR] [\fB\-mno\-fix7000\fR]
    [\fB\-mfix\-vr4120\fR] [\fB\-mno\-fix\-vr4120\fR]
    [\fB\-mfix\-vr4130\fR] [\fB\-mno\-fix\-vr4130\fR]
@@ -357,7 +370,7 @@ as [\fB\-a\fR[\fBcdghlns\fR][=\fIfile\fR]] [\fB\-\-alternate\fR] [\fB\-D\fR]
   [ \fB\-forbid\-unportable\-instructions\fR] [\fB\-Fup\fR]
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-\&\s-1GNU\s0 \fBas\fR is really a family of assemblers.
+\&\s-1GNU \s0\fBas\fR is really a family of assemblers.
 If you use (or have used) the \s-1GNU\s0 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,
@@ -365,7 +378,7 @@ including object file formats, most assembler directives (often called
 \&\fIpseudo-ops\fR) and assembler syntax.
 .PP
 \&\fBas\fR is primarily intended to assemble the output of the
-\&\s-1GNU\s0 C compiler \f(CW\*(C`gcc\*(C'\fR for use by the linker
+\&\s-1GNU C\s0 compiler \f(CW\*(C`gcc\*(C'\fR for use by the linker
 \&\f(CW\*(C`ld\*(C'\fR.  Nevertheless, we've tried to make \fBas\fR
 assemble correctly everything that other assemblers for the same
 machine would assemble.
@@ -400,7 +413,7 @@ runs \fBas\fR automatically.  Warnings report an assumption made so
 that \fBas\fR could keep assembling a flawed program; errors report a
 grave problem that stops the assembly.
 .PP
-If you are invoking \fBas\fR via the \s-1GNU\s0 C compiler,
+If you are invoking \fBas\fR via the \s-1GNU C\s0 compiler,
 you can use the \fB\-Wa\fR option to pass arguments through to the assembler.
 The assembler arguments must be separated from each other (and the \fB\-Wa\fR)
 by commas.  For example:
@@ -508,8 +521,8 @@ compiler output).
 .IX Item "--gen-debug"
 .PD
 Generate debugging information for each assembler source line using whichever
-debug format is preferred by the target.  This currently means either \s-1STABS\s0,
-\&\s-1ECOFF\s0 or \s-1DWARF2\s0.
+debug format is preferred by the target.  This currently means either \s-1STABS,
+ECOFF\s0 or \s-1DWARF2.\s0
 .IP "\fB\-\-gstabs\fR" 4
 .IX Item "--gstabs"
 Generate stabs debugging information for each assembler line.  This
@@ -526,13 +539,22 @@ the location of the current working directory at assembling time.
 Generate \s-1DWARF2\s0 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.
+.IP "\fB\-\-gdwarf\-sections\fR" 4
+.IX Item "--gdwarf-sections"
+Instead of creating a .debug_line section, create a series of
+\&.debug_line.\fIfoo\fR sections where \fIfoo\fR is the name of the
+corresponding code section.  For example a code section called \fI.text.func\fR
+will have its dwarf line number information placed into a section called
+\&\fI.debug_line.text.func\fR.  If the code section is just called \fI.text\fR
+then debug line section will still be called just \fI.debug_line\fR without any
+suffix.
 .IP "\fB\-\-size\-check=error\fR" 4
 .IX Item "--size-check=error"
 .PD 0
 .IP "\fB\-\-size\-check=warning\fR" 4
 .IX Item "--size-check=warning"
 .PD
-Issue an error or warning for invalid \s-1ELF\s0 .size directive.
+Issue an error or warning for invalid \s-1ELF \s0.size directive.
 .IP "\fB\-\-help\fR" 4
 .IX Item "--help"
 Print a summary of the command line options and exit.
@@ -643,6 +665,11 @@ be marked as being encoded for a big-endian processor.
 .IX Item "-EL"
 This option specifies that the output generated by the assembler should
 be marked as being encoded for a little-endian processor.
+.IP "\fB\-mabi=\fR\fIabi\fR" 4
+.IX Item "-mabi=abi"
+Specify which \s-1ABI\s0 the source code uses.  The recognized arguments
+are: \f(CW\*(C`ilp32\*(C'\fR and \f(CW\*(C`lp64\*(C'\fR, which decides the generated object
+file in \s-1ELF32\s0 and \s-1ELF64\s0 format respectively.  The default is \f(CW\*(C`lp64\*(C'\fR.
 .PP
 The following options are available when as is configured for an Alpha
 processor.
@@ -710,7 +737,7 @@ Utility Manual.
 .IX Item "-g"
 This option is used when the compiler generates debug information.  When
 \&\fBgcc\fR is using \fBmips-tfile\fR to generate debug
-information for \s-1ECOFF\s0, local labels must be passed through to the object
+information for \s-1ECOFF,\s0 local labels must be passed through to the object
 file.  Otherwise this option has no effect.
 .IP "\fB\-G\fR\fIsize\fR" 4
 .IX Item "-Gsize"
@@ -810,7 +837,7 @@ and
 \&\f(CW\*(C`bf592\*(C'\fR.
 .IP "\fB\-mfdpic\fR" 4
 .IX Item "-mfdpic"
-Assemble for the \s-1FDPIC\s0 \s-1ABI\s0.
+Assemble for the \s-1FDPIC ABI.\s0
 .IP "\fB\-mno\-fdpic\fR" 4
 .IX Item "-mno-fdpic"
 .PD 0
@@ -948,6 +975,12 @@ accept various extension mnemonics.  For example,
 \&\f(CW\*(C`rdseed\*(C'\fR,
 \&\f(CW\*(C`prfchw\*(C'\fR,
 \&\f(CW\*(C`smap\*(C'\fR,
+\&\f(CW\*(C`mpx\*(C'\fR,
+\&\f(CW\*(C`sha\*(C'\fR,
+\&\f(CW\*(C`avx512f\*(C'\fR,
+\&\f(CW\*(C`avx512cd\*(C'\fR,
+\&\f(CW\*(C`avx512er\*(C'\fR,
+\&\f(CW\*(C`avx512pf\*(C'\fR,
 \&\f(CW\*(C`noavx\*(C'\fR,
 \&\f(CW\*(C`vmx\*(C'\fR,
 \&\f(CW\*(C`vmfunc\*(C'\fR,
@@ -1007,12 +1040,12 @@ with \s-1VEX\s0 prefix.
 .IP "\fB\-msse\-check=\fR\fIerror\fR" 4
 .IX Item "-msse-check=error"
 .PD
-These options control if the assembler should check \s-1SSE\s0 intructions.
+These options control if the assembler should check \s-1SSE\s0 instructions.
 \&\fB\-msse\-check=\fR\fInone\fR will make the assembler not to check \s-1SSE\s0
 instructions,  which is the default.  \fB\-msse\-check=\fR\fIwarning\fR
-will make the assembler issue a warning for any \s-1SSE\s0 intruction.
+will make the assembler issue a warning for any \s-1SSE\s0 instruction.
 \&\fB\-msse\-check=\fR\fIerror\fR will make the assembler issue an error
-for any \s-1SSE\s0 intruction.
+for any \s-1SSE\s0 instruction.
 .IP "\fB\-mavxscalar=\fR\fI128\fR" 4
 .IX Item "-mavxscalar=128"
 .PD 0
@@ -1024,6 +1057,31 @@ instructions.  \fB\-mavxscalar=\fR\fI128\fR will encode scalar
 \&\s-1AVX\s0 instructions with 128bit vector length, which is the default.
 \&\fB\-mavxscalar=\fR\fI256\fR will encode scalar \s-1AVX\s0 instructions
 with 256bit vector length.
+.IP "\fB\-mevexlig=\fR\fI128\fR" 4
+.IX Item "-mevexlig=128"
+.PD 0
+.IP "\fB\-mevexlig=\fR\fI256\fR" 4
+.IX Item "-mevexlig=256"
+.IP "\fB\-mevexlig=\fR\fI512\fR" 4
+.IX Item "-mevexlig=512"
+.PD
+These options control how the assembler should encode length-ignored
+(\s-1LIG\s0) \s-1EVEX\s0 instructions.  \fB\-mevexlig=\fR\fI128\fR will encode \s-1LIG
+EVEX\s0 instructions with 128bit vector length, which is the default.
+\&\fB\-mevexlig=\fR\fI256\fR and \fB\-mevexlig=\fR\fI512\fR will
+encode \s-1LIG EVEX\s0 instructions with 256bit and 512bit vector length,
+respectively.
+.IP "\fB\-mevexwig=\fR\fI0\fR" 4
+.IX Item "-mevexwig=0"
+.PD 0
+.IP "\fB\-mevexwig=\fR\fI1\fR" 4
+.IX Item "-mevexwig=1"
+.PD
+These options control how the assembler should encode w\-ignored (\s-1WIG\s0)
+\&\s-1EVEX\s0 instructions.  \fB\-mevexwig=\fR\fI0\fR will encode \s-1WIG
+EVEX\s0 instructions with evex.w = 0, which is the default.
+\&\fB\-mevexwig=\fR\fI1\fR will encode \s-1WIG EVEX\s0 instructions with
+evex.w = 1.
 .IP "\fB\-mmnemonic=\fR\fIatt\fR" 4
 .IX Item "-mmnemonic=att"
 .PD 0
@@ -1046,6 +1104,10 @@ take precedent.
 .IX Item "-mnaked-reg"
 This opetion specifies that registers don't require a \fB%\fR prefix.
 The \f(CW\*(C`.att_syntax\*(C'\fR and \f(CW\*(C`.intel_syntax\*(C'\fR directives will take precedent.
+.IP "\fB\-madd\-bnd\-prefix\fR" 4
+.IX Item "-madd-bnd-prefix"
+This option forces the assembler to add \s-1BND\s0 prefix to all branches, even
+if such prefix was not explicitly specified in the source code.
 .PP
 The following options are available when as is configured for the
 Intel 80960 processor.
@@ -1177,19 +1239,19 @@ The following options are available when as is configured for a
 PowerPC processor.
 .IP "\fB\-a32\fR" 4
 .IX Item "-a32"
-Generate \s-1ELF32\s0 or \s-1XCOFF32\s0.
+Generate \s-1ELF32\s0 or \s-1XCOFF32.\s0
 .IP "\fB\-a64\fR" 4
 .IX Item "-a64"
-Generate \s-1ELF64\s0 or \s-1XCOFF64\s0.
+Generate \s-1ELF64\s0 or \s-1XCOFF64.\s0
 .IP "\fB\-K \s-1PIC\s0\fR" 4
 .IX Item "-K PIC"
 Set \s-1EF_PPC_RELOCATABLE_LIB\s0 in \s-1ELF\s0 flags.
 .IP "\fB\-mpwrx | \-mpwr2\fR" 4
 .IX Item "-mpwrx | -mpwr2"
-Generate code for \s-1POWER/2\s0 (\s-1RIOS2\s0).
+Generate code for \s-1POWER/2 \s0(\s-1RIOS2\s0).
 .IP "\fB\-mpwr\fR" 4
 .IX Item "-mpwr"
-Generate code for \s-1POWER\s0 (\s-1RIOS1\s0)
+Generate code for \s-1POWER \s0(\s-1RIOS1\s0)
 .IP "\fB\-m601\fR" 4
 .IX Item "-m601"
 Generate code for PowerPC 601.
@@ -1434,7 +1496,7 @@ Xtensa processor.
 Control the treatment of literal pools.  The default is
 \&\fB\-\-no\-text\-section\-literals\fR, which places literals in
 separate sections in the output file.  This allows the literal pool to be
-placed in a data \s-1RAM/ROM\s0.  With \fB\-\-text\-section\-literals\fR, the
+placed in a data \s-1RAM/ROM. \s0 With \fB\-\-text\-section\-literals\fR, the
 literals are interspersed in the text section in order to keep them as
 close as possible to their references.  This may be necessary for large
 assembly files, where the literals would otherwise be out of range of the
@@ -1530,9 +1592,7 @@ Treat undocumented Z80 instructions that do not work on R800 as errors.
 \&\fIgcc\fR\|(1), \fIld\fR\|(1), and the Info entries for \fIbinutils\fR and \fIld\fR.
 .SH "COPYRIGHT"
 .IX Header "COPYRIGHT"
-Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
-2000, 2001, 2002, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation,
-Inc.
+Copyright (c) 1991\-2013 Free Software Foundation, Inc.
 .PP
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3
diff --git a/share/man/man1/aarch64-linux-android-c++filt.1 b/share/man/man1/aarch64-linux-android-c++filt.1
index 5d85790..12d12a9 100644
--- a/share/man/man1/aarch64-linux-android-c++filt.1
+++ b/share/man/man1/aarch64-linux-android-c++filt.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "C++FILT 1"
-.TH C++FILT 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH C++FILT 1 "2014-08-29" "binutils-2.24.0" "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
@@ -265,7 +274,7 @@ Automatic selection based on executable (the default method)
 .ie n .IP """gnu""" 4
 .el .IP "\f(CWgnu\fR" 4
 .IX Item "gnu"
-the one used by the \s-1GNU\s0 \*(C+ compiler (g++)
+the one used by the \s-1GNU \*(C+\s0 compiler (g++)
 .ie n .IP """lucid""" 4
 .el .IP "\f(CWlucid\fR" 4
 .IX Item "lucid"
@@ -285,7 +294,7 @@ the one used by the \s-1EDG\s0 compiler
 .ie n .IP """gnu\-v3""" 4
 .el .IP "\f(CWgnu\-v3\fR" 4
 .IX Item "gnu-v3"
-the one used by the \s-1GNU\s0 \*(C+ compiler (g++) with the V3 \s-1ABI\s0.
+the one used by the \s-1GNU \*(C+\s0 compiler (g++) with the V3 \s-1ABI.\s0
 .ie n .IP """java""" 4
 .el .IP "\f(CWjava\fR" 4
 .IX Item "java"
diff --git a/share/man/man1/aarch64-linux-android-dlltool.1 b/share/man/man1/aarch64-linux-android-dlltool.1
index 303413f..7a8a98e 100644
--- a/share/man/man1/aarch64-linux-android-dlltool.1
+++ b/share/man/man1/aarch64-linux-android-dlltool.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "DLLTOOL 1"
-.TH DLLTOOL 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH DLLTOOL 1 "2014-08-29" "binutils-2.24.0" "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
@@ -168,19 +177,19 @@ has been specified it creates a def file.  Any or all of the \fB\-e\fR,
 \&\fB\-l\fR and \fB\-z\fR options can be present in one invocation of
 dlltool.
 .PP
-When creating a \s-1DLL\s0, along with the source for the \s-1DLL\s0, it is necessary
+When creating a \s-1DLL,\s0 along with the source for the \s-1DLL,\s0 it is necessary
 to have three other files.  \fBdlltool\fR can help with the creation of
 these files.
 .PP
 The first file is a \fI.def\fR file which specifies which functions are
-exported from the \s-1DLL\s0, which functions the \s-1DLL\s0 imports, and so on.  This
+exported from the \s-1DLL,\s0 which functions the \s-1DLL\s0 imports, and so on.  This
 is a text file and can be created by hand, or \fBdlltool\fR can be used
 to create it using the \fB\-z\fR option.  In this case \fBdlltool\fR
 will scan the object files specified on its command line looking for
 those functions which have been specially marked as being exported and
 put entries for them in the \fI.def\fR file it creates.
 .PP
-In order to mark a function as being exported from a \s-1DLL\s0, it needs to
+In order to mark a function as being exported from a \s-1DLL,\s0 it needs to
 have an \fB\-export:<name_of_function>\fR entry in the \fB.drectve\fR
 section of the object file.  This can be done in C by using the
 \&\fIasm()\fR operator:
@@ -199,7 +208,7 @@ binary file and it can be created by giving the \fB\-e\fR option to
 \&\fBdlltool\fR when it is creating or reading in a \fI.def\fR file.
 .PP
 The third file needed for \s-1DLL\s0 creation is the library file that programs
-will link with in order to access the functions in the \s-1DLL\s0 (an `import
+will link with in order to access the functions in the \s-1DLL \s0(an `import
 library').  This file can be created by giving the \fB\-l\fR option to
 dlltool when it is creating or reading in a \fI.def\fR file.
 .PP
@@ -338,7 +347,7 @@ double quotes.
 Specifies the name to be stored in the \fI.def\fR file as the name of
 the \s-1DLL\s0 when the \fB\-e\fR option is used.  If this option is not
 present, then the filename given to the \fB\-e\fR option will be
-used as the name of the \s-1DLL\s0.
+used as the name of the \s-1DLL.\s0
 .IP "\fB\-m\fR \fImachine\fR" 4
 .IX Item "-m machine"
 .PD 0
@@ -392,7 +401,7 @@ party DLLs that were built with MS-Windows tools.
 Specifies that when \fBdlltool\fR is creating the exports file it
 should not append the string \fB@ <number>\fR.  These numbers are
 called ordinal numbers and they represent another way of accessing the
-function in a \s-1DLL\s0, other than by name.
+function in a \s-1DLL,\s0 other than by name.
 .IP "\fB\-A\fR" 4
 .IX Item "-A"
 .PD 0
@@ -451,7 +460,7 @@ actually an import library. See also \fB\-\-identify\-strict\fR.
 .IX Item "--identify-strict"
 Modifies the behavior of the \fB\-\-identify\fR option, such
 that an error is reported if \fIfilename\fR is associated with
-more than one \s-1DLL\s0.
+more than one \s-1DLL.\s0
 .IP "\fB\-i\fR" 4
 .IX Item "-i"
 .PD 0
diff --git a/share/man/man1/aarch64-linux-android-elfedit.1 b/share/man/man1/aarch64-linux-android-elfedit.1
index 482a7e3..29431d5 100644
--- a/share/man/man1/aarch64-linux-android-elfedit.1
+++ b/share/man/man1/aarch64-linux-android-elfedit.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "ELFEDIT 1"
-.TH ELFEDIT 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH ELFEDIT 1 "2014-08-29" "binutils-2.24.0" "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
@@ -189,8 +198,8 @@ The supported \s-1ELF\s0 OSABIs are, \fInone\fR, \fI\s-1HPUX\s0\fR, \fINetBSD\fR
 \&\fI\s-1NSK\s0\fR, \fI\s-1AROS\s0\fR and \fIFenixOS\fR.
 .IP "\fB\-\-output\-osabi=\fR\fIosabi\fR" 4
 .IX Item "--output-osabi=osabi"
-Change the \s-1ELF\s0 \s-1OSABI\s0 in the \s-1ELF\s0 header to \fIosabi\fR.  The
-supported \s-1ELF\s0 \s-1OSABI\s0 are the same as \fB\-\-input\-osabi\fR.
+Change the \s-1ELF OSABI\s0 in the \s-1ELF\s0 header to \fIosabi\fR.  The
+supported \s-1ELF OSABI\s0 are the same as \fB\-\-input\-osabi\fR.
 .IP "\fB\-v\fR" 4
 .IX Item "-v"
 .PD 0
diff --git a/share/man/man1/aarch64-linux-android-gprof.1 b/share/man/man1/aarch64-linux-android-gprof.1
index a3b57b6..0bd43be 100644
--- a/share/man/man1/aarch64-linux-android-gprof.1
+++ b/share/man/man1/aarch64-linux-android-gprof.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "GPROF 1"
-.TH GPROF 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU"
+.TH GPROF 1 "2014-08-29" "binutils-2.24.0" "GNU"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -417,7 +426,7 @@ the output of the program \f(CW\*(C`nm\*(C'\fR.
 \&        ...
 .Ve
 .Sp
-To create a \fImap_file\fR with \s-1GNU\s0 \f(CW\*(C`nm\*(C'\fR, type a command like
+To create a \fImap_file\fR with \s-1GNU \s0\f(CW\*(C`nm\*(C'\fR, type a command like
 \&\f(CW\*(C`nm \-\-extern\-only \-\-defined\-only \-v \-\-print\-file\-name program\-name\*(C'\fR.
 .ie n .IP """\-T""" 4
 .el .IP "\f(CW\-T\fR" 4
@@ -742,7 +751,7 @@ Vol. 13, pp. 671\-685, 1983.
 .PP
 \&\*(L"gprof: A Call Graph Execution Profiler\*(R",
 by S. Graham, P. Kessler, M. McKusick;
-Proceedings of the \s-1SIGPLAN\s0 '82 Symposium on Compiler Construction,
+Proceedings of the \s-1SIGPLAN \s0'82 Symposium on Compiler Construction,
 \&\s-1SIGPLAN\s0 Notices, Vol. 17, No  6, pp. 120\-126, June 1982.
 .SH "COPYRIGHT"
 .IX Header "COPYRIGHT"
diff --git a/share/man/man1/aarch64-linux-android-ld.1 b/share/man/man1/aarch64-linux-android-ld.1
index 2899745..e005735 100644
--- a/share/man/man1/aarch64-linux-android-ld.1
+++ b/share/man/man1/aarch64-linux-android-ld.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "LD 1"
-.TH LD 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH LD 1 "2014-08-29" "binutils-2.24.0" "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
@@ -335,7 +344,7 @@ You can also define the input format from a script, using the command
 .IP "\fB\-\-mri\-script=\fR\fIMRI-commandfile\fR" 4
 .IX Item "--mri-script=MRI-commandfile"
 .PD
-For compatibility with linkers produced by \s-1MRI\s0, \fBld\fR accepts script
+For compatibility with linkers produced by \s-1MRI, \s0\fBld\fR accepts script
 files written in an alternate, restricted command language, described in
 the \s-1MRI\s0 Compatible Script Files section of \s-1GNU\s0 ld documentation.
 Introduce \s-1MRI\s0 script files with
@@ -385,7 +394,7 @@ Specifies a list of archive libraries from which symbols should not be automatic
 exported.  The library names may be delimited by commas or colons.  Specifying
 \&\f(CW\*(C`\-\-exclude\-libs ALL\*(C'\fR excludes symbols in all archive libraries from
 automatic export.  This option is available only for the i386 \s-1PE\s0 targeted
-port of the linker and for \s-1ELF\s0 targeted ports.  For i386 \s-1PE\s0, symbols
+port of the linker and for \s-1ELF\s0 targeted ports.  For i386 \s-1PE,\s0 symbols
 explicitly listed in a .def file are still exported, regardless of this
 option.  For \s-1ELF\s0 targeted ports, symbols affected by this option will
 be treated as hidden.
@@ -505,7 +514,7 @@ Ignored.  Provided for compatibility with other tools.
 .PD
 Set the maximum size of objects to be optimized using the \s-1GP\s0 register to
 \&\fIsize\fR.  This is only meaningful for object file formats such as
-\&\s-1MIPS\s0 \s-1ECOFF\s0 which supports putting large and small objects into different
+\&\s-1MIPS ELF\s0 that support putting large and small objects into different
 sections.  This is ignored for other object file formats.
 .IP "\fB\-h\fR \fIname\fR" 4
 .IX Item "-h name"
@@ -561,7 +570,7 @@ archives multiple times.
 You may list the same archive multiple times on the command line.
 .Sp
 This type of archive searching is standard for Unix linkers.  However,
-if you are using \fBld\fR on \s-1AIX\s0, note that it is different from the
+if you are using \fBld\fR on \s-1AIX,\s0 note that it is different from the
 behaviour of the \s-1AIX\s0 linker.
 .IP "\fB\-L\fR \fIsearchdir\fR" 4
 .IX Item "-L searchdir"
@@ -934,7 +943,7 @@ Marks the object can not be dumped by \f(CW\*(C`dldump\*(C'\fR.
 Marks the object as not requiring executable stack.
 .IP "\fBnorelro\fR" 4
 .IX Item "norelro"
-Don't create an \s-1ELF\s0 \f(CW\*(C`PT_GNU_RELRO\*(C'\fR segment header in the object.
+Don't create an \s-1ELF \s0\f(CW\*(C`PT_GNU_RELRO\*(C'\fR segment header in the object.
 .IP "\fBnow\fR" 4
 .IX Item "now"
 When generating an executable or shared library, mark it to tell the
@@ -947,11 +956,7 @@ first called.
 Marks the object may contain \f(CW$ORIGIN\fR.
 .IP "\fBrelro\fR" 4
 .IX Item "relro"
-Create an \s-1ELF\s0 \f(CW\*(C`PT_GNU_RELRO\*(C'\fR segment header in the object.
-.IP "\fBnosecondary\fR" 4
-.IX Item "nosecondary"
-Convert secondary symbols to weak symbols when generating a shared
-library.
+Create an \s-1ELF \s0\f(CW\*(C`PT_GNU_RELRO\*(C'\fR segment header in the object.
 .IP "\fBmax\-page\-size=\fR\fIvalue\fR" 4
 .IX Item "max-page-size=value"
 Set the emulation maximum page size to \fIvalue\fR.
@@ -960,7 +965,7 @@ Set the emulation maximum page size to \fIvalue\fR.
 Set the emulation common page size to \fIvalue\fR.
 .IP "\fBstack\-size=\fR\fIvalue\fR" 4
 .IX Item "stack-size=value"
-Specify a stack size for in an \s-1ELF\s0 \f(CW\*(C`PT_GNU_STACK\*(C'\fR segment.
+Specify a stack size for in an \s-1ELF \s0\f(CW\*(C`PT_GNU_STACK\*(C'\fR segment.
 Specifying zero will override any default non-zero sized
 \&\f(CW\*(C`PT_GNU_STACK\*(C'\fR segment creation.
 .RE
@@ -1008,7 +1013,7 @@ restore the old behaviour.
 .IP "\fB\-\-no\-as\-needed\fR" 4
 .IX Item "--no-as-needed"
 .PD
-This option affects \s-1ELF\s0 \s-1DT_NEEDED\s0 tags for dynamic libraries mentioned
+This option affects \s-1ELF DT_NEEDED\s0 tags for dynamic libraries mentioned
 on the command line after the \fB\-\-as\-needed\fR option.  Normally
 the linker will add a \s-1DT_NEEDED\s0 tag for each dynamic library mentioned
 on the command line, regardless of whether the library is actually
@@ -1158,7 +1163,9 @@ The format of the table is intentionally simple, so that it may be
 easily processed by a script if necessary.  The symbols are printed out,
 sorted by name.  For each symbol, a list of file names is given.  If the
 symbol is defined, the first file listed is the location of the
-definition.  The remaining files contain references to the symbol.
+definition.  If the symbol is defined as a common value then any files
+where this happens appear next.  Finally any files that reference the
+symbol are listed.
 .IP "\fB\-\-no\-define\-common\fR" 4
 .IX Item "--no-define-common"
 This option inhibits the assignment of addresses to common symbols.
@@ -1333,7 +1340,7 @@ A shared library specified at link time may not be the same as the one
 that is available at load time, so the symbol might actually be
 resolvable at load time.
 .IP "\(bu" 4
-There are some operating systems, eg BeOS and \s-1HPPA\s0, where undefined
+There are some operating systems, eg BeOS and \s-1HPPA,\s0 where undefined
 symbols in shared libraries are normal.
 .Sp
 The BeOS kernel for example patches shared libraries at load time to
@@ -1542,7 +1549,7 @@ warning and continue with the link.
 .IP "\fB\-Bshareable\fR" 4
 .IX Item "-Bshareable"
 .PD
-Create a shared library.  This is currently only supported on \s-1ELF\s0, \s-1XCOFF\s0
+Create a shared library.  This is currently only supported on \s-1ELF, XCOFF\s0
 and SunOS platforms.  On SunOS, the linker will automatically create a
 shared library if the \fB\-e\fR option is not used and there are
 undefined symbols in the link.
@@ -1778,7 +1785,7 @@ encountered in a different order.
 .IP "\fB\-\-warn\-constructors\fR" 4
 .IX Item "--warn-constructors"
 Warn if any global constructors are used.  This is only useful for a few
-object file formats.  For formats like \s-1COFF\s0 or \s-1ELF\s0, the linker can not
+object file formats.  For formats like \s-1COFF\s0 or \s-1ELF,\s0 the linker can not
 detect the use of global constructors.
 .IP "\fB\-\-warn\-multiple\-gp\fR" 4
 .IX Item "--warn-multiple-gp"
@@ -1868,12 +1875,12 @@ file as \f(CW\*(C`_\|_wrap_malloc\*(C'\fR; if you do, the assembler may resolve
 call before the linker has a chance to wrap it to \f(CW\*(C`malloc\*(C'\fR.
 .IP "\fB\-\-eh\-frame\-hdr\fR" 4
 .IX Item "--eh-frame-hdr"
-Request creation of \f(CW\*(C`.eh_frame_hdr\*(C'\fR section and \s-1ELF\s0
-\&\f(CW\*(C`PT_GNU_EH_FRAME\*(C'\fR segment header.
+Request creation of \f(CW\*(C`.eh_frame_hdr\*(C'\fR section and \s-1ELF
+\&\s0\f(CW\*(C`PT_GNU_EH_FRAME\*(C'\fR segment header.
 .IP "\fB\-\-no\-ld\-generated\-unwind\-info\fR" 4
 .IX Item "--no-ld-generated-unwind-info"
 Request creation of \f(CW\*(C`.eh_frame\*(C'\fR unwind info for linker
-generated code sections like \s-1PLT\s0.  This option is on by default
+generated code sections like \s-1PLT. \s0 This option is on by default
 if linker generated unwind info is supported.
 .IP "\fB\-\-enable\-new\-dtags\fR" 4
 .IX Item "--enable-new-dtags"
@@ -1881,7 +1888,7 @@ if linker generated unwind info is supported.
 .IP "\fB\-\-disable\-new\-dtags\fR" 4
 .IX Item "--disable-new-dtags"
 .PD
-This linker can create the new dynamic tags in \s-1ELF\s0. But the older \s-1ELF\s0
+This linker can create the new dynamic tags in \s-1ELF.\s0 But the older \s-1ELF\s0
 systems may not understand them. If you specify
 \&\fB\-\-enable\-new\-dtags\fR, the new dynamic tags will be created as needed
 and older dynamic tags will be omitted.
@@ -1898,9 +1905,9 @@ value can reduce the memory requirements at the expense of speed.
 .IP "\fB\-\-hash\-style=\fR\fIstyle\fR" 4
 .IX Item "--hash-style=style"
 Set the type of linker's hash table(s).  \fIstyle\fR can be either
-\&\f(CW\*(C`sysv\*(C'\fR for classic \s-1ELF\s0 \f(CW\*(C`.hash\*(C'\fR section, \f(CW\*(C`gnu\*(C'\fR for
-new style \s-1GNU\s0 \f(CW\*(C`.gnu.hash\*(C'\fR section or \f(CW\*(C`both\*(C'\fR for both
-the classic \s-1ELF\s0 \f(CW\*(C`.hash\*(C'\fR and new style \s-1GNU\s0 \f(CW\*(C`.gnu.hash\*(C'\fR
+\&\f(CW\*(C`sysv\*(C'\fR for classic \s-1ELF \s0\f(CW\*(C`.hash\*(C'\fR section, \f(CW\*(C`gnu\*(C'\fR for
+new style \s-1GNU \s0\f(CW\*(C`.gnu.hash\*(C'\fR section or \f(CW\*(C`both\*(C'\fR for both
+the classic \s-1ELF \s0\f(CW\*(C`.hash\*(C'\fR and new style \s-1GNU \s0\f(CW\*(C`.gnu.hash\*(C'\fR
 hash tables.  The default is \f(CW\*(C`sysv\*(C'\fR.
 .IP "\fB\-\-reduce\-memory\-overheads\fR" 4
 .IX Item "--reduce-memory-overheads"
@@ -2028,7 +2035,7 @@ disable/enable the default underscore symbol-prefix.
 .IP "\fB\-\-export\-all\-symbols\fR" 4
 .IX Item "--export-all-symbols"
 If given, all global symbols in the objects used to build a \s-1DLL\s0 will
-be exported by the \s-1DLL\s0.  Note that this is the default if there
+be exported by the \s-1DLL. \s0 Note that this is the default if there
 otherwise wouldn't be any exported symbols.  When symbols are
 explicitly exported via \s-1DEF\s0 files or implicitly exported via function
 attributes, the default is to not export anything else unless this
@@ -2072,7 +2079,7 @@ file offsets which are multiples of this number.  This defaults to
 .IX Item "--heap reserve,commit"
 .PD
 Specify the number of bytes of memory to reserve (and optionally commit)
-to be used as heap for this program.  The default is 1Mb reserved, 4K
+to be used as heap for this program.  The default is 1MB reserved, 4K
 committed.
 [This option is specific to the i386 \s-1PE\s0 targeted port of the linker]
 .IP "\fB\-\-image\-base\fR \fIvalue\fR" 4
@@ -2095,7 +2102,14 @@ If given, the appropriate bit in the \*(L"Characteristics\*(R" field of the \s-1
 header is set to indicate that this executable supports virtual addresses
 greater than 2 gigabytes.  This should be used in conjunction with the /3GB
 or /USERVA=\fIvalue\fR megabytes switch in the \*(L"[operating systems]\*(R"
-section of the \s-1BOOT\s0.INI.  Otherwise, this bit has no effect.
+section of the \s-1BOOT.INI. \s0 Otherwise, this bit has no effect.
+[This option is specific to \s-1PE\s0 targeted ports of the linker]
+.IP "\fB\-\-disable\-large\-address\-aware\fR" 4
+.IX Item "--disable-large-address-aware"
+Reverts the effect of a previous \fB\-\-large\-address\-aware\fR option.
+This is useful if \fB\-\-large\-address\-aware\fR is always set by the compiler
+driver (e.g. Cygwin gcc) and the executable does not support virtual
+addresses greater than 2 gigabytes.
 [This option is specific to \s-1PE\s0 targeted ports of the linker]
 .IP "\fB\-\-major\-image\-version\fR \fIvalue\fR" 4
 .IX Item "--major-image-version value"
@@ -2142,7 +2156,7 @@ creation step.
 .IX Item "--enable-auto-image-base"
 Automatically choose the image base for DLLs, unless one is specified
 using the \f(CW\*(C`\-\-image\-base\*(C'\fR argument.  By using a hash generated
-from the dllname to create unique image bases for each \s-1DLL\s0, in-memory
+from the dllname to create unique image bases for each \s-1DLL,\s0 in-memory
 collisions and relocations which can delay program execution are
 avoided.
 [This option is specific to the i386 \s-1PE\s0 targeted port of the linker]
@@ -2185,8 +2199,8 @@ documentation for ld's \f(CW\*(C`\-\-enable\-auto\-import\*(C'\fR for details."
 This message occurs when some (sub)expression accesses an address
 ultimately given by the sum of two constants (Win32 import tables only
 allow one).  Instances where this may occur include accesses to member
-fields of struct variables imported from a \s-1DLL\s0, as well as using a
-constant index into an array variable imported from a \s-1DLL\s0.  Any
+fields of struct variables imported from a \s-1DLL,\s0 as well as using a
+constant index into an array variable imported from a \s-1DLL. \s0 Any
 multiword variable (arrays, structs, long long, etc) may trigger
 this error condition.  However, regardless of the exact data type
 of the offending exported variable, ld will always detect it, issue
@@ -2239,7 +2253,7 @@ A third method of dealing with this difficulty is to abandon
 \&'auto\-import' for the offending symbol and mark it with
 \&\f(CW\*(C`_\|_declspec(dllimport)\*(C'\fR.  However, in practice that
 requires using compile-time #defines to indicate whether you are
-building a \s-1DLL\s0, building client code that will link to the \s-1DLL\s0, or
+building a \s-1DLL,\s0 building client code that will link to the \s-1DLL,\s0 or
 merely building/linking to a static library.   In making the choice
 between the various methods of resolving the 'direct address with
 constant offset' problem, you should consider typical real-world usage:
@@ -2327,7 +2341,7 @@ addresses which are a multiple of this number.  Defaults to 0x1000.
 .IX Item "--stack reserve,commit"
 .PD
 Specify the number of bytes of memory to reserve (and optionally commit)
-to be used as stack for this program.  The default is 2Mb reserved, 4K
+to be used as stack for this program.  The default is 2MB reserved, 4K
 committed.
 [This option is specific to the i386 \s-1PE\s0 targeted port of the linker]
 .IP "\fB\-\-subsystem\fR \fIwhich\fR" 4
@@ -2359,13 +2373,13 @@ Code integrity checks are enforced.
 .IP "\fB\-\-nxcompat\fR" 4
 .IX Item "--nxcompat"
 The image is compatible with the Data Execution Prevention.
-This feature was introduced with \s-1MS\s0 Windows \s-1XP\s0 \s-1SP2\s0 for i386 \s-1PE\s0 targets.
+This feature was introduced with \s-1MS\s0 Windows \s-1XP SP2\s0 for i386 \s-1PE\s0 targets.
 .IP "\fB\-\-no\-isolation\fR" 4
 .IX Item "--no-isolation"
 Although the image understands isolation, do not isolate the image.
 .IP "\fB\-\-no\-seh\fR" 4
 .IX Item "--no-seh"
-The image does not use \s-1SEH\s0. No \s-1SE\s0 handler may be called from
+The image does not use \s-1SEH.\s0 No \s-1SE\s0 handler may be called from
 this image.
 .IP "\fB\-\-no\-bind\fR" 4
 .IX Item "--no-bind"
@@ -2376,6 +2390,11 @@ The driver uses the \s-1MS\s0 Windows Driver Model.
 .IP "\fB\-\-tsaware\fR" 4
 .IX Item "--tsaware"
 The image is Terminal Server aware.
+.IP "\fB\-\-insert\-timestamp\fR" 4
+.IX Item "--insert-timestamp"
+Insert a real timestamp into the image, rather than the default value
+of zero.  This will result in a slightly different results with each
+invocation, which could be helpful for distributing unique images.
 .PP
 The C6X uClinux target uses a binary format called \s-1DSBT\s0 to support shared
 libraries.  Each shared library in the system needs to have a unique index;
@@ -2417,6 +2436,21 @@ This option tells the linker which \s-1GOT\s0 generation scheme to use.
 \&\fItype\fR should be one of \fBsingle\fR, \fBnegative\fR,
 \&\fBmultigot\fR or \fBtarget\fR.  For more information refer to the
 Info entry for \fIld\fR.
+.PP
+The following options are supported to control microMIPS instruction
+generation when linking for \s-1MIPS\s0 targets.
+.IP "\fB\-\-insn32\fR" 4
+.IX Item "--insn32"
+.PD 0
+.IP "\fB\-\-no\-insn32\fR" 4
+.IX Item "--no-insn32"
+.PD
+These options control the choice of microMIPS instructions used in code
+generated by the linker, such as that in the \s-1PLT\s0 or lazy binding stubs,
+or in relaxation.  If \fB\-\-insn32\fR is used, then the linker only uses
+32\-bit instruction encodings.  By default or if \fB\-\-no\-insn32\fR is
+used, all instruction encodings are used, including 16\-bit ones where
+possible.
 .SH "ENVIRONMENT"
 .IX Header "ENVIRONMENT"
 You can change the behaviour of \fBld\fR with the environment variables
diff --git a/share/man/man1/aarch64-linux-android-nlmconv.1 b/share/man/man1/aarch64-linux-android-nlmconv.1
index ce3cdb8..3add2f9 100644
--- a/share/man/man1/aarch64-linux-android-nlmconv.1
+++ b/share/man/man1/aarch64-linux-android-nlmconv.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "NLMCONV 1"
-.TH NLMCONV 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH NLMCONV 1 "2014-08-29" "binutils-2.24.0" "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
@@ -147,7 +156,7 @@ reading \fIheaderfile\fR for \s-1NLM\s0 header information.  For instructions
 on writing the \s-1NLM\s0 command file language used in header files, see the
 \&\fBlinkers\fR section, \fB\s-1NLMLINK\s0\fR in particular, of the \fI\s-1NLM\s0
 Development and Tools Overview\fR, which is part of the \s-1NLM\s0 Software
-Developer's Kit (\*(L"\s-1NLM\s0 \s-1SDK\s0\*(R"), available from Novell, Inc.
+Developer's Kit (\*(L"\s-1NLM SDK\*(R"\s0), available from Novell, Inc.
 \&\fBnlmconv\fR uses the \s-1GNU\s0 Binary File Descriptor library to read
 \&\fIinfile\fR;
 .PP
diff --git a/share/man/man1/aarch64-linux-android-nm.1 b/share/man/man1/aarch64-linux-android-nm.1
index 3aba5f5..e93ebf2 100644
--- a/share/man/man1/aarch64-linux-android-nm.1
+++ b/share/man/man1/aarch64-linux-android-nm.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "NM 1"
-.TH NM 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH NM 1 "2014-08-29" "binutils-2.24.0" "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
@@ -148,7 +157,7 @@ nm [\fB\-A\fR|\fB\-o\fR|\fB\-\-print\-file\-name\fR] [\fB\-a\fR|\fB\-\-debug\-sy
    [\fIobjfile\fR...]
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-\&\s-1GNU\s0 \fBnm\fR lists the symbols from object files \fIobjfile\fR....
+\&\s-1GNU \s0\fBnm\fR lists the symbols from object files \fIobjfile\fR....
 If no object files are listed as arguments, \fBnm\fR assumes the file
 \&\fIa.out\fR.
 .PP
@@ -214,6 +223,10 @@ extension to the standard set of \s-1ELF\s0 symbol types.  It indicates a
 symbol which if referenced by a relocation does not evaluate to its
 address, but instead must be invoked at runtime.  The runtime
 execution will then return the value to be used in the relocation.
+.ie n .IP """I""" 4
+.el .IP "\f(CWI\fR" 4
+.IX Item "I"
+The symbol is an indirect reference to another symbol.
 .ie n .IP """N""" 4
 .el .IP "\f(CWN\fR" 4
 .IX Item "N"
@@ -328,7 +341,7 @@ Display all symbols, even debugger-only symbols; normally these are not
 listed.
 .IP "\fB\-B\fR" 4
 .IX Item "-B"
-The same as \fB\-\-format=bsd\fR (for compatibility with the \s-1MIPS\s0 \fBnm\fR).
+The same as \fB\-\-format=bsd\fR (for compatibility with the \s-1MIPS \s0\fBnm\fR).
 .IP "\fB\-C\fR" 4
 .IX Item "-C"
 .PD 0
@@ -411,7 +424,7 @@ encountered.
 .IP "\fB\-\-portability\fR" 4
 .IX Item "--portability"
 .PD
-Use the \s-1POSIX\s0.2 standard output format instead of the default format.
+Use the \s-1POSIX.2\s0 standard output format instead of the default format.
 Equivalent to \fB\-f posix\fR.
 .IP "\fB\-r\fR" 4
 .IX Item "-r"
@@ -466,8 +479,8 @@ Show the version number of \fBnm\fR and exit.
 .IX Item "-X"
 This option is ignored for compatibility with the \s-1AIX\s0 version of
 \&\fBnm\fR.  It takes one parameter which must be the string
-\&\fB32_64\fR.  The default mode of \s-1AIX\s0 \fBnm\fR corresponds
-to \fB\-X 32\fR, which is not supported by \s-1GNU\s0 \fBnm\fR.
+\&\fB32_64\fR.  The default mode of \s-1AIX \s0\fBnm\fR corresponds
+to \fB\-X 32\fR, which is not supported by \s-1GNU \s0\fBnm\fR.
 .IP "\fB\-\-defined\-only\fR" 4
 .IX Item "--defined-only"
 Display only defined symbols for each object file.
@@ -487,10 +500,9 @@ both size and value to be printed.
 .IX Item "--special-syms"
 Display symbols which have a target-specific special meaning.  These
 symbols are usually used by the target for some special processing and
-are not normally helpful when included included in the normal symbol
-lists.  For example for \s-1ARM\s0 targets this option would skip the mapping
-symbols used to mark transitions between \s-1ARM\s0 code, \s-1THUMB\s0 code and
-data.
+are not normally helpful when included in the normal symbol lists.
+For example for \s-1ARM\s0 targets this option would skip the mapping symbols
+used to mark transitions between \s-1ARM\s0 code, \s-1THUMB\s0 code and data.
 .IP "\fB\-\-synthetic\fR" 4
 .IX Item "--synthetic"
 Include synthetic symbols in the output.  These are special symbols
diff --git a/share/man/man1/aarch64-linux-android-objcopy.1 b/share/man/man1/aarch64-linux-android-objcopy.1
index 870494f..34c0d83 100644
--- a/share/man/man1/aarch64-linux-android-objcopy.1
+++ b/share/man/man1/aarch64-linux-android-objcopy.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "OBJCOPY 1"
-.TH OBJCOPY 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH OBJCOPY 1 "2014-08-29" "binutils-2.24.0" "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
@@ -215,8 +224,8 @@ objcopy [\fB\-F\fR \fIbfdname\fR|\fB\-\-target=\fR\fIbfdname\fR]
         \fIinfile\fR [\fIoutfile\fR]
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-The \s-1GNU\s0 \fBobjcopy\fR utility copies the contents of an object
-file to another.  \fBobjcopy\fR uses the \s-1GNU\s0 \s-1BFD\s0 Library to
+The \s-1GNU \s0\fBobjcopy\fR utility copies the contents of an object
+file to another.  \fBobjcopy\fR uses the \s-1GNU BFD\s0 Library to
 read and write the object files.  It can write the destination object
 file in a format different from that of the source object file.  The
 exact behavior of \fBobjcopy\fR is controlled by command-line options.
@@ -448,7 +457,7 @@ not affected).  Select which byte in the range begins the copy with
 the \fB\-\-byte\fR option.  Select the width of the range with the
 \&\fB\-\-interleave\-width\fR option.
 .Sp
-This option is useful for creating files to program \s-1ROM\s0.  It is
+This option is useful for creating files to program \s-1ROM. \s0 It is
 typically used with an \f(CW\*(C`srec\*(C'\fR output target.  Note that
 \&\fBobjcopy\fR will complain if you do not specify the
 \&\fB\-\-byte\fR option as well.
@@ -501,7 +510,7 @@ It can be disabled with the \fB\-U\fR option, below.
 .PD
 Do \fInot\fR operate in \fIdeterministic\fR mode.  This is the
 inverse of the \fB\-D\fR option, above: when copying archive members
-and writing the archive index, use their actual \s-1UID\s0, \s-1GID\s0, timestamp,
+and writing the archive index, use their actual \s-1UID, GID,\s0 timestamp,
 and file mode values.
 .Sp
 This is the default unless \fIbinutils\fR was configured with
@@ -566,7 +575,7 @@ Set or change the \s-1LMA\s0 address of any sections matching
 section will be loaded into memory at program load time.  Normally
 this is the same as the \s-1VMA\s0 address, which is the address of the
 section at program run time, but on some systems, especially those
-where a program is held in \s-1ROM\s0, the two can be different.  If \fB=\fR
+where a program is held in \s-1ROM,\s0 the two can be different.  If \fB=\fR
 is used, the section address is set to \fIval\fR.  Otherwise,
 \&\fIval\fR is added to or subtracted from the section address.  See the
 comments under \fB\-\-change\-addresses\fR, above.  If
@@ -579,7 +588,7 @@ Set or change the \s-1VMA\s0 address of any section matching
 section will be located once the program has started executing.
 Normally this is the same as the \s-1LMA\s0 address, which is the address
 where the section will be loaded into memory, but on some systems,
-especially those where a program is held in \s-1ROM\s0, the two can be
+especially those where a program is held in \s-1ROM,\s0 the two can be
 different.  If \fB=\fR is used, the section address is set to
 \&\fIval\fR.  Otherwise, \fIval\fR is added to or subtracted from the
 section address.  See the comments under \fB\-\-change\-addresses\fR,
@@ -822,7 +831,7 @@ needed if debugging abilities are required.  The suggested procedure
 to create these files is as follows:
 .RS 4
 .IP "1.<Link the executable as normal.  Assuming that is is called>" 4
-.IX Item "1.<Link the executable as normal.  Assuming that is is called>"
+.IX Item "1.<Link the executable as normal. Assuming that is is called>"
 \&\f(CW\*(C`foo\*(C'\fR then...
 .ie n .IP "1.<Run ""objcopy \-\-only\-keep\-debug foo foo.dbg"" to>" 4
 .el .IP "1.<Run \f(CWobjcopy \-\-only\-keep\-debug foo foo.dbg\fR to>" 4
@@ -847,7 +856,7 @@ optional.  You could instead do this:
 .PD 0
 .ie n .IP "1.<Copy ""foo"" to  ""foo.full"">" 4
 .el .IP "1.<Copy \f(CWfoo\fR to  \f(CWfoo.full\fR>" 4
-.IX Item "1.<Copy foo to  foo.full>"
+.IX Item "1.<Copy foo to foo.full>"
 .ie n .IP "1.<Run ""objcopy \-\-strip\-debug foo"">" 4
 .el .IP "1.<Run \f(CWobjcopy \-\-strip\-debug foo\fR>" 4
 .IX Item "1.<Run objcopy --strip-debug foo>"
@@ -871,7 +880,7 @@ basis.
 .RE
 .IP "\fB\-\-strip\-dwo\fR" 4
 .IX Item "--strip-dwo"
-Remove the contents of all \s-1DWARF\s0 .dwo sections, leaving the
+Remove the contents of all \s-1DWARF \s0.dwo sections, leaving the
 remaining debugging sections and all symbols intact.
 This option is intended for use by the compiler as part of
 the \fB\-gsplit\-dwarf\fR option, which splits debug information
@@ -882,7 +891,7 @@ the .dwo file, then the \fB\-\-strip\-dwo\fR option to remove
 those sections from the original .o file.
 .IP "\fB\-\-extract\-dwo\fR" 4
 .IX Item "--extract-dwo"
-Extract the contents of all \s-1DWARF\s0 .dwo sections.  See the
+Extract the contents of all \s-1DWARF \s0.dwo sections.  See the
 \&\fB\-\-strip\-dwo\fR option for more information.
 .IP "\fB\-\-file\-alignment\fR \fInum\fR" 4
 .IX Item "--file-alignment num"
diff --git a/share/man/man1/aarch64-linux-android-objdump.1 b/share/man/man1/aarch64-linux-android-objdump.1
index e09896a..22ffb71 100644
--- a/share/man/man1/aarch64-linux-android-objdump.1
+++ b/share/man/man1/aarch64-linux-android-objdump.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "OBJDUMP 1"
-.TH OBJDUMP 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH OBJDUMP 1 "2014-08-29" "binutils-2.24.0" "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
@@ -440,9 +449,9 @@ instructions.  \fB32\fR and \fB64\fR select PowerPC and
 PowerPC64 disassembly, respectively.  \fBe300\fR selects
 disassembly for the e300 family.  \fB440\fR selects disassembly for
 the PowerPC 440.  \fBppcps\fR selects disassembly for the paired
-single instructions of the \s-1PPC750CL\s0.
+single instructions of the \s-1PPC750CL.\s0
 .Sp
-For \s-1MIPS\s0, this option controls the printing of instruction mnemonic
+For \s-1MIPS,\s0 this option controls the printing of instruction mnemonic
 names and register names in disassembled instructions.  Multiple
 selections from the following may be specified as a comma separated
 string, and invalid options are ignored:
@@ -453,36 +462,40 @@ string, and invalid options are ignored:
 Print the 'raw' instruction mnemonic instead of some pseudo
 instruction mnemonic.  I.e., print 'daddu' or 'or' instead of 'move',
 \&'sll' instead of 'nop', etc.
+.ie n .IP """virt""" 4
+.el .IP "\f(CWvirt\fR" 4
+.IX Item "virt"
+Disassemble the virtualization \s-1ASE\s0 instructions.
 .ie n .IP """gpr\-names=\f(CIABI\f(CW""" 4
 .el .IP "\f(CWgpr\-names=\f(CIABI\f(CW\fR" 4
 .IX Item "gpr-names=ABI"
-Print \s-1GPR\s0 (general-purpose register) names as appropriate
-for the specified \s-1ABI\s0.  By default, \s-1GPR\s0 names are selected according to
+Print \s-1GPR \s0(general-purpose register) names as appropriate
+for the specified \s-1ABI. \s0 By default, \s-1GPR\s0 names are selected according to
 the \s-1ABI\s0 of the binary being disassembled.
 .ie n .IP """fpr\-names=\f(CIABI\f(CW""" 4
 .el .IP "\f(CWfpr\-names=\f(CIABI\f(CW\fR" 4
 .IX Item "fpr-names=ABI"
-Print \s-1FPR\s0 (floating-point register) names as
-appropriate for the specified \s-1ABI\s0.  By default, \s-1FPR\s0 numbers are printed
+Print \s-1FPR \s0(floating-point register) names as
+appropriate for the specified \s-1ABI. \s0 By default, \s-1FPR\s0 numbers are printed
 rather than names.
 .ie n .IP """cp0\-names=\f(CIARCH\f(CW""" 4
 .el .IP "\f(CWcp0\-names=\f(CIARCH\f(CW\fR" 4
 .IX Item "cp0-names=ARCH"
-Print \s-1CP0\s0 (system control coprocessor; coprocessor 0) register names
+Print \s-1CP0 \s0(system control coprocessor; coprocessor 0) register names
 as appropriate for the \s-1CPU\s0 or architecture specified by
 \&\fI\s-1ARCH\s0\fR.  By default, \s-1CP0\s0 register names are selected according to
 the architecture and \s-1CPU\s0 of the binary being disassembled.
 .ie n .IP """hwr\-names=\f(CIARCH\f(CW""" 4
 .el .IP "\f(CWhwr\-names=\f(CIARCH\f(CW\fR" 4
 .IX Item "hwr-names=ARCH"
-Print \s-1HWR\s0 (hardware register, used by the \f(CW\*(C`rdhwr\*(C'\fR instruction) names
+Print \s-1HWR \s0(hardware register, used by the \f(CW\*(C`rdhwr\*(C'\fR instruction) names
 as appropriate for the \s-1CPU\s0 or architecture specified by
 \&\fI\s-1ARCH\s0\fR.  By default, \s-1HWR\s0 names are selected according to
 the architecture and \s-1CPU\s0 of the binary being disassembled.
 .ie n .IP """reg\-names=\f(CIABI\f(CW""" 4
 .el .IP "\f(CWreg\-names=\f(CIABI\f(CW\fR" 4
 .IX Item "reg-names=ABI"
-Print \s-1GPR\s0 and \s-1FPR\s0 names as appropriate for the selected \s-1ABI\s0.
+Print \s-1GPR\s0 and \s-1FPR\s0 names as appropriate for the selected \s-1ABI.\s0
 .ie n .IP """reg\-names=\f(CIARCH\f(CW""" 4
 .el .IP "\f(CWreg\-names=\f(CIARCH\f(CW\fR" 4
 .IX Item "reg-names=ARCH"
@@ -497,7 +510,7 @@ rather than names, for the selected types of registers.
 You can list the available values of \fI\s-1ABI\s0\fR and \fI\s-1ARCH\s0\fR using
 the \fB\-\-help\fR option.
 .Sp
-For \s-1VAX\s0, you can specify function entry addresses with \fB\-M
+For \s-1VAX,\s0 you can specify function entry addresses with \fB\-M
 entry:0xf00ba\fR.  You can use this multiple times to properly
 disassemble \s-1VAX\s0 binary files that don't contain symbol tables (like
 \&\s-1ROM\s0 dumps).  In these cases, the function entry mask would otherwise
@@ -523,10 +536,10 @@ Print information that is specific to the object file format.  The
 argument \fIoptions\fR is a comma separated list that depends on the
 format (the lists of options is displayed with the help).
 .Sp
-For \s-1XCOFF\s0, the available options are: \fBheader\fR, \fBaout\fR,
+For \s-1XCOFF,\s0 the available options are: \fBheader\fR, \fBaout\fR,
 \&\fBsections\fR, \fBsyms\fR, \fBrelocs\fR, \fBlineno\fR,
-\&\fBloader\fR, \fBexcept\fR, \fBtypchk\fR, \fBtraceback\fR
-and \fBtoc\fR.
+\&\fBloader\fR, \fBexcept\fR, \fBtypchk\fR, \fBtraceback\fR,
+\&\fBtoc\fR and \fBldinfo\fR.
 .IP "\fB\-r\fR" 4
 .IX Item "-r"
 .PD 0
diff --git a/share/man/man1/aarch64-linux-android-ranlib.1 b/share/man/man1/aarch64-linux-android-ranlib.1
index 7c4e9c4..c3abf32 100644
--- a/share/man/man1/aarch64-linux-android-ranlib.1
+++ b/share/man/man1/aarch64-linux-android-ranlib.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "RANLIB 1"
-.TH RANLIB 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH RANLIB 1 "2014-08-29" "binutils-2.24.0" "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
@@ -146,7 +155,7 @@ An archive with such an index speeds up linking to the library and
 allows routines in the library to call each other without regard to
 their placement in the archive.
 .PP
-The \s-1GNU\s0 \fBranlib\fR program is another form of \s-1GNU\s0 \fBar\fR; running
+The \s-1GNU \s0\fBranlib\fR program is another form of \s-1GNU \s0\fBar\fR; running
 \&\fBranlib\fR is completely equivalent to executing \fBar \-s\fR.
 .SH "OPTIONS"
 .IX Header "OPTIONS"
@@ -171,11 +180,13 @@ Show the version number of \fBranlib\fR.
 .IP "\fB\-D\fR" 4
 .IX Item "-D"
 Operate in \fIdeterministic\fR mode.  The symbol map archive member's
-header will show zero for the \s-1UID\s0, \s-1GID\s0, and timestamp.  When this
+header will show zero for the \s-1UID, GID,\s0 and timestamp.  When this
 option is used, multiple runs will produce identical output files.
 .Sp
-This is the default unless \fIbinutils\fR was configured with
-\&\fB\-\-enable\-deterministic\-archives\fR.
+If \fIbinutils\fR was configured with
+\&\fB\-\-enable\-deterministic\-archives\fR, then this mode is on by
+default.  It can be disabled with the \fB\-U\fR option, described
+below.
 .IP "\fB\-t\fR" 4
 .IX Item "-t"
 Update the timestamp of the symbol map of an archive.
@@ -183,10 +194,11 @@ Update the timestamp of the symbol map of an archive.
 .IX Item "-U"
 Do \fInot\fR operate in \fIdeterministic\fR mode.  This is the
 inverse of the \fB\-D\fR option, above: the archive index will get
-actual \s-1UID\s0, \s-1GID\s0, timestamp, and file mode values.
+actual \s-1UID, GID,\s0 timestamp, and file mode values.
 .Sp
-This is the default unless \fIbinutils\fR was configured with
-\&\fB\-\-enable\-deterministic\-archives\fR.
+If \fIbinutils\fR was configured \fIwithout\fR
+\&\fB\-\-enable\-deterministic\-archives\fR, then this mode is on by
+default.
 .IP "\fB@\fR\fIfile\fR" 4
 .IX Item "@file"
 Read command-line options from \fIfile\fR.  The options read are
diff --git a/share/man/man1/aarch64-linux-android-readelf.1 b/share/man/man1/aarch64-linux-android-readelf.1
index f0bf71f..8c2c51e 100644
--- a/share/man/man1/aarch64-linux-android-readelf.1
+++ b/share/man/man1/aarch64-linux-android-readelf.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "READELF 1"
-.TH READELF 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH READELF 1 "2014-08-29" "binutils-2.24.0" "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
@@ -273,7 +282,7 @@ Displays the contents of the file's relocation section, if it has one.
 .IX Item "--unwind"
 .PD
 Displays the contents of the file's unwind section, if it has one.  Only
-the unwind sections for \s-1IA64\s0 \s-1ELF\s0 files, as well as \s-1ARM\s0 unwind tables
+the unwind sections for \s-1IA64 ELF\s0 files, as well as \s-1ARM\s0 unwind tables
 (\f(CW\*(C`.ARM.exidx\*(C'\fR / \f(CW\*(C`.ARM.extab\*(C'\fR) are currently supported.
 .IP "\fB\-d\fR" 4
 .IX Item "-d"
diff --git a/share/man/man1/aarch64-linux-android-size.1 b/share/man/man1/aarch64-linux-android-size.1
index 8534573..8b2fbc1 100644
--- a/share/man/man1/aarch64-linux-android-size.1
+++ b/share/man/man1/aarch64-linux-android-size.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "SIZE 1"
-.TH SIZE 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH SIZE 1 "2014-08-29" "binutils-2.24.0" "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
@@ -142,7 +151,7 @@ size [\fB\-A\fR|\fB\-B\fR|\fB\-\-format=\fR\fIcompatibility\fR]
      [\fIobjfile\fR...]
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-The \s-1GNU\s0 \fBsize\fR utility lists the section sizes\-\-\-and the total
+The \s-1GNU \s0\fBsize\fR utility lists the section sizes\-\-\-and the total
 size\-\-\-for each of the object or archive files \fIobjfile\fR in its
 argument list.  By default, one line of output is generated for each
 object file or each module in an archive.
@@ -160,8 +169,8 @@ The command line options have the following meanings:
 .IP "\fB\-\-format=\fR\fIcompatibility\fR" 4
 .IX Item "--format=compatibility"
 .PD
-Using one of these options, you can choose whether the output from \s-1GNU\s0
-\&\fBsize\fR resembles output from System V \fBsize\fR (using \fB\-A\fR,
+Using one of these options, you can choose whether the output from \s-1GNU
+\&\s0\fBsize\fR resembles output from System V \fBsize\fR (using \fB\-A\fR,
 or \fB\-\-format=sysv\fR), or Berkeley \fBsize\fR (using \fB\-B\fR, or
 \&\fB\-\-format=berkeley\fR).  The default is the one-line format similar to
 Berkeley's.
diff --git a/share/man/man1/aarch64-linux-android-strings.1 b/share/man/man1/aarch64-linux-android-strings.1
index bde23da..9ee80fb 100644
--- a/share/man/man1/aarch64-linux-android-strings.1
+++ b/share/man/man1/aarch64-linux-android-strings.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "STRINGS 1"
-.TH STRINGS 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH STRINGS 1 "2014-08-29" "binutils-2.24.0" "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
@@ -142,7 +151,7 @@ strings [\fB\-afovV\fR] [\fB\-\fR\fImin-len\fR]
         [\fB\-\-help\fR] [\fB\-\-version\fR] \fIfile\fR...
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-For each \fIfile\fR given, \s-1GNU\s0 \fBstrings\fR prints the printable
+For each \fIfile\fR given, \s-1GNU \s0\fBstrings\fR prints the printable
 character sequences that are at least 4 characters long (or the number
 given with the options below) and are followed by an unprintable
 character.  By default, it only prints the strings from the initialized
@@ -205,7 +214,7 @@ octal, \fBx\fR for hexadecimal, or \fBd\fR for decimal.
 .PD
 Select the character encoding of the strings that are to be found.
 Possible values for \fIencoding\fR are: \fBs\fR = single\-7\-bit\-byte
-characters (\s-1ASCII\s0, \s-1ISO\s0 8859, etc., default), \fBS\fR =
+characters (\s-1ASCII, ISO 8859,\s0 etc., default), \fBS\fR =
 single\-8\-bit\-byte characters, \fBb\fR = 16\-bit bigendian, \fBl\fR =
 16\-bit littleendian, \fBB\fR = 32\-bit bigendian, \fBL\fR = 32\-bit
 littleendian.  Useful for finding wide character strings. (\fBl\fR
diff --git a/share/man/man1/aarch64-linux-android-strip.1 b/share/man/man1/aarch64-linux-android-strip.1
index df19671..8c3a48f 100644
--- a/share/man/man1/aarch64-linux-android-strip.1
+++ b/share/man/man1/aarch64-linux-android-strip.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "STRIP 1"
-.TH STRIP 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH STRIP 1 "2014-08-29" "binutils-2.24.0" "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
@@ -154,7 +163,7 @@ strip [\fB\-F\fR \fIbfdname\fR |\fB\-\-target=\fR\fIbfdname\fR]
       \fIobjfile\fR...
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
-\&\s-1GNU\s0 \fBstrip\fR discards all symbols from object files
+\&\s-1GNU \s0\fBstrip\fR discards all symbols from object files
 \&\fIobjfile\fR.  The list of object files may include archives.
 At least one object file must be given.
 .PP
@@ -222,7 +231,7 @@ Remove all symbols.
 Remove debugging symbols only.
 .IP "\fB\-\-strip\-dwo\fR" 4
 .IX Item "--strip-dwo"
-Remove the contents of all \s-1DWARF\s0 .dwo sections, leaving the
+Remove the contents of all \s-1DWARF \s0.dwo sections, leaving the
 remaining debugging sections and all symbols intact.
 See the description of this option in the \fBobjcopy\fR section
 for more information.
@@ -279,7 +288,7 @@ It can be disabled with the \fB\-U\fR option, below.
 .PD
 Do \fInot\fR operate in \fIdeterministic\fR mode.  This is the
 inverse of the \fB\-D\fR option, above: when copying archive members
-and writing the archive index, use their actual \s-1UID\s0, \s-1GID\s0, timestamp,
+and writing the archive index, use their actual \s-1UID, GID,\s0 timestamp,
 and file mode values.
 .Sp
 This is the default unless \fIbinutils\fR was configured with
@@ -337,7 +346,7 @@ needed if debugging abilities are required.  The suggested procedure
 to create these files is as follows:
 .RS 4
 .IP "1.<Link the executable as normal.  Assuming that is is called>" 4
-.IX Item "1.<Link the executable as normal.  Assuming that is is called>"
+.IX Item "1.<Link the executable as normal. Assuming that is is called>"
 \&\f(CW\*(C`foo\*(C'\fR then...
 .ie n .IP "1.<Run ""objcopy \-\-only\-keep\-debug foo foo.dbg"" to>" 4
 .el .IP "1.<Run \f(CWobjcopy \-\-only\-keep\-debug foo foo.dbg\fR to>" 4
diff --git a/share/man/man1/aarch64-linux-android-windmc.1 b/share/man/man1/aarch64-linux-android-windmc.1
index 6f0d6c0..e7686df 100644
--- a/share/man/man1/aarch64-linux-android-windmc.1
+++ b/share/man/man1/aarch64-linux-android-windmc.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "WINDMC 1"
-.TH WINDMC 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH WINDMC 1 "2014-08-29" "binutils-2.24.0" "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
@@ -171,7 +180,7 @@ Windows Message Compiler.
 .IP "\fB\-\-ascii_in\fR" 4
 .IX Item "--ascii_in"
 .PD
-Specifies that the input file specified is \s-1ASCII\s0. This is the default
+Specifies that the input file specified is \s-1ASCII.\s0 This is the default
 behaviour.
 .IP "\fB\-A\fR" 4
 .IX Item "-A"
@@ -202,7 +211,7 @@ Sets the customer bit in all message id's.
 .IP "\fB\-\-codepage_in\fR \fIcodepage\fR" 4
 .IX Item "--codepage_in codepage"
 .PD
-Sets the default codepage to be used to convert input file to \s-1UTF16\s0. The
+Sets the default codepage to be used to convert input file to \s-1UTF16.\s0 The
 default is ocdepage 1252.
 .IP "\fB\-d\fR" 4
 .IX Item "-d"
@@ -259,7 +268,7 @@ of any message exceeds the number specified.
 .IX Item "--nullterminate"
 .PD
 Terminate message text in \f(CW\*(C`bin\*(C'\fR files by zero. By default they are
-terminated by \s-1CR/LF\s0.
+terminated by \s-1CR/LF.\s0
 .IP "\fB\-o\fR" 4
 .IX Item "-o"
 .PD 0
@@ -292,7 +301,7 @@ is the current directory.
 .IP "\fB\-\-unicode_in\fR" 4
 .IX Item "--unicode_in"
 .PD
-Specifies that the input file is \s-1UTF16\s0.
+Specifies that the input file is \s-1UTF16.\s0
 .IP "\fB\-U\fR" 4
 .IX Item "-U"
 .PD 0
diff --git a/share/man/man1/aarch64-linux-android-windres.1 b/share/man/man1/aarch64-linux-android-windres.1
index a45862d..a9a5023 100644
--- a/share/man/man1/aarch64-linux-android-windres.1
+++ b/share/man/man1/aarch64-linux-android-windres.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "WINDRES 1"
-.TH WINDRES 1 "2014-09-12" "binutils-2.23.52.0.2" "GNU Development Tools"
+.TH WINDRES 1 "2014-08-29" "binutils-2.24.0" "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