| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | ARM-Options.html | 78 <dt><code>-mcpu=<var>processor</var>[+<var>extension</var>…]</code></dt>
83 <code>arm1</code>,
84 <code>arm2</code>,
85 <code>arm250</code>,
86 <code>arm3</code>,
87 <code>arm6</code>,
88 <code>arm60</code>,
89 <code>arm600</code>,
90 <code>arm610</code>,
91 <code>arm620</code>,
[all …]
|
| H A D | PDP_002d11_002dOptions.html | 74 <p>The PDP-11 version of <code>as</code> has a rich set of machine
77 <a name="Code-Generation-Options"></a>
78 <h4 class="subsubsection">9.34.1.1 Code Generation Options</h4>
84 <dt><code>-mpic | -mno-pic</code></dt>
85 <dd><p>Generate position-independent (or position-dependent) code.
87 <p>The default is to generate position-independent code.
96 Most options come in two variants: a <code>-m</code><var>extension</var> that
97 enables <var>extension</var>, and a <code>-mno-</code><var>extension</var> that disables
106 <dt><code>-mall | -mall-extensions</code></dt>
111 <dt><code>-mno-extensions</code></dt>
[all …]
|
| H A D | i386_002dOptions.html | 77 <p>The i386 version of <code>as</code> has a few machine
88 <dt><code>--32 | --x32 | --64</code></dt>
100 <dt><code>-n</code></dt>
102 alignment within code sections with multi-byte nop instructions such
108 <dt><code>--divide</code></dt>
118 <dt><code>-march=<var>CPU</var>[+<var>EXTENSION</var>…]</code></dt>
123 <code>i8086</code>,
124 <code>i186</code>,
125 <code>i286</code>,
126 <code>i386</code>,
[all …]
|
| H A D | M.html | 75 changes the syntax and pseudo-op handling of <code>as</code> to make it
76 compatible with the <code>ASM68K</code> assembler from Microtec Research.
81 assembling existing MRI assembler code using <code>as</code>.
92 Other object file formats do not support this. <code>as</code> handles
103 </li><li> <code>END</code> pseudo-op specifying start address
105 <p>The MRI <code>END</code> pseudo-op permits the specification of a start address.
110 </li><li> <code>IDNT</code>, <code>.ident</code> and <code>NAME</code> pseudo-ops
112 <p>The MRI <code>IDNT</code>, <code>.ident</code> and <code>NAME</code> pseudo-ops assign a module
115 </li><li> <code>ORG</code> pseudo-op
117 <p>The m68k MRI <code>ORG</code> pseudo-op begins an absolute section at a given
[all …]
|
| H A D | MIPS-Options.html | 72 <p>The MIPS configurations of <small>GNU</small> <code>as</code> support these
78 <dt><code>-G <var>num</var></code></dt>
89 <dt><code>-EB</code></dt>
90 <dt><code>-EL</code></dt>
91 <dd><p>Any MIPS configuration of <code>as</code> can select big-endian or
97 <dt><code>-KPIC</code></dt>
105 <dt><code>-mvxworks-pic</code></dt>
112 <dt><code>-mips1</code></dt>
113 <dt><code>-mips2</code></dt>
114 <dt><code>-mips3</code></dt>
[all …]
|
| H A D | ARM-Directives.html | 80 <dt><code>.align <var>expression</var> [, <var>expression</var>]</code></dt>
88 <dt><code>.arch <var>name</var></code></dt>
93 <p>Specifying <code>.arch</code> clears any previously selected architecture
98 <dt><code>.arch_extension <var>name</var></code></dt>
103 <p><code>.arch_extension</code> may be used multiple times to add or remove extensions
108 <dt><code>.arm</code></dt>
109 <dd><p>This performs the same action as <var>.code 32</var>.
114 <dt><code>.bss</code></dt>
115 <dd><p>This directive switches to the <code>.bss</code> section.
120 <dt><code>.cantunwind</code></dt>
[all …]
|
| H A D | PowerPC_002dOpts.html | 85 <dt><code>-a32</code></dt>
89 <dt><code>-a64</code></dt>
93 <dt><code>-K PIC</code></dt>
97 <dt><code>-mpwrx | -mpwr2</code></dt>
98 <dd><p>Generate code for POWER/2 (RIOS2).
101 <dt><code>-mpwr</code></dt>
102 <dd><p>Generate code for POWER (RIOS1)
105 <dt><code>-m601</code></dt>
106 <dd><p>Generate code for PowerPC 601.
109 <dt><code>-mppc, -mppc32, -m603, -m604</code></dt>
[all …]
|
| H A D | CFI-directives.html | 72 <h4 class="subsection">7.11.1 <code>.cfi_sections <var>section_list</var></code></h4>
74 <p><code>.cfi_sections</code> may be used to specify whether CFI directives
75 should emit <code>.eh_frame</code> section and/or <code>.debug_frame</code> section.
76 If <var>section_list</var> is <code>.eh_frame</code>, <code>.eh_frame</code> is emitted,
77 if <var>section_list</var> is <code>.debug_frame</code>, <code>.debug_frame</code> is emitted.
78 To emit both use <code>.eh_frame, .debug_frame</code>. The default if this
79 directive is not used is <code>.cfi_sections .eh_frame</code>.
82 by specifying <code>.eh_frame_entry</code> instead of <code>.eh_frame</code>.
84 <p>Some targets may support an additional name, such as <code>.c6xabi.exidx</code>
87 <p>The <code>.cfi_sections</code> directive can be repeated, with the same or different
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | ARM-Options.html | 78 <dt><code>-mcpu=<var>processor</var>[+<var>extension</var>…]</code></dt>
83 <code>arm1</code>,
84 <code>arm2</code>,
85 <code>arm250</code>,
86 <code>arm3</code>,
87 <code>arm6</code>,
88 <code>arm60</code>,
89 <code>arm600</code>,
90 <code>arm610</code>,
91 <code>arm620</code>,
[all …]
|
| H A D | PDP_002d11_002dOptions.html | 74 <p>The PDP-11 version of <code>as</code> has a rich set of machine
77 <a name="Code-Generation-Options"></a>
78 <h4 class="subsubsection">9.34.1.1 Code Generation Options</h4>
84 <dt><code>-mpic | -mno-pic</code></dt>
85 <dd><p>Generate position-independent (or position-dependent) code.
87 <p>The default is to generate position-independent code.
96 Most options come in two variants: a <code>-m</code><var>extension</var> that
97 enables <var>extension</var>, and a <code>-mno-</code><var>extension</var> that disables
106 <dt><code>-mall | -mall-extensions</code></dt>
111 <dt><code>-mno-extensions</code></dt>
[all …]
|
| H A D | i386_002dOptions.html | 77 <p>The i386 version of <code>as</code> has a few machine
88 <dt><code>--32 | --x32 | --64</code></dt>
100 <dt><code>-n</code></dt>
102 alignment within code sections with multi-byte nop instructions such
108 <dt><code>--divide</code></dt>
118 <dt><code>-march=<var>CPU</var>[+<var>EXTENSION</var>…]</code></dt>
123 <code>i8086</code>,
124 <code>i186</code>,
125 <code>i286</code>,
126 <code>i386</code>,
[all …]
|
| H A D | M.html | 75 changes the syntax and pseudo-op handling of <code>as</code> to make it
76 compatible with the <code>ASM68K</code> assembler from Microtec Research.
81 assembling existing MRI assembler code using <code>as</code>.
92 Other object file formats do not support this. <code>as</code> handles
103 </li><li> <code>END</code> pseudo-op specifying start address
105 <p>The MRI <code>END</code> pseudo-op permits the specification of a start address.
110 </li><li> <code>IDNT</code>, <code>.ident</code> and <code>NAME</code> pseudo-ops
112 <p>The MRI <code>IDNT</code>, <code>.ident</code> and <code>NAME</code> pseudo-ops assign a module
115 </li><li> <code>ORG</code> pseudo-op
117 <p>The m68k MRI <code>ORG</code> pseudo-op begins an absolute section at a given
[all …]
|
| H A D | MIPS-Options.html | 72 <p>The MIPS configurations of <small>GNU</small> <code>as</code> support these
78 <dt><code>-G <var>num</var></code></dt>
89 <dt><code>-EB</code></dt>
90 <dt><code>-EL</code></dt>
91 <dd><p>Any MIPS configuration of <code>as</code> can select big-endian or
97 <dt><code>-KPIC</code></dt>
105 <dt><code>-mvxworks-pic</code></dt>
112 <dt><code>-mips1</code></dt>
113 <dt><code>-mips2</code></dt>
114 <dt><code>-mips3</code></dt>
[all …]
|
| H A D | ARM-Directives.html | 80 <dt><code>.align <var>expression</var> [, <var>expression</var>]</code></dt>
88 <dt><code>.arch <var>name</var></code></dt>
93 <p>Specifying <code>.arch</code> clears any previously selected architecture
98 <dt><code>.arch_extension <var>name</var></code></dt>
103 <p><code>.arch_extension</code> may be used multiple times to add or remove extensions
108 <dt><code>.arm</code></dt>
109 <dd><p>This performs the same action as <var>.code 32</var>.
114 <dt><code>.bss</code></dt>
115 <dd><p>This directive switches to the <code>.bss</code> section.
120 <dt><code>.cantunwind</code></dt>
[all …]
|
| H A D | PowerPC_002dOpts.html | 85 <dt><code>-a32</code></dt>
89 <dt><code>-a64</code></dt>
93 <dt><code>-K PIC</code></dt>
97 <dt><code>-mpwrx | -mpwr2</code></dt>
98 <dd><p>Generate code for POWER/2 (RIOS2).
101 <dt><code>-mpwr</code></dt>
102 <dd><p>Generate code for POWER (RIOS1)
105 <dt><code>-m601</code></dt>
106 <dd><p>Generate code for PowerPC 601.
109 <dt><code>-mppc, -mppc32, -m603, -m604</code></dt>
[all …]
|
| H A D | CFI-directives.html | 72 <h4 class="subsection">7.11.1 <code>.cfi_sections <var>section_list</var></code></h4>
74 <p><code>.cfi_sections</code> may be used to specify whether CFI directives
75 should emit <code>.eh_frame</code> section and/or <code>.debug_frame</code> section.
76 If <var>section_list</var> is <code>.eh_frame</code>, <code>.eh_frame</code> is emitted,
77 if <var>section_list</var> is <code>.debug_frame</code>, <code>.debug_frame</code> is emitted.
78 To emit both use <code>.eh_frame, .debug_frame</code>. The default if this
79 directive is not used is <code>.cfi_sections .eh_frame</code>.
82 by specifying <code>.eh_frame_entry</code> instead of <code>.eh_frame</code>.
84 <p>Some targets may support an additional name, such as <code>.c6xabi.exidx</code>
87 <p>The <code>.cfi_sections</code> directive can be repeated, with the same or different
[all …]
|
| H A D | Alpha_002dRelocs.html | 92 <dt><code>!literal</code></dt>
93 <dt><code>!literal!<var>N</var></code></dt>
94 <dd><p>Used with an <code>ldq</code> instruction to load the address of a symbol
98 <code>lituse</code> relocations with this <code>literal</code> relocation. The
99 <code>lituse</code> relocations are used by the linker to optimize the code
103 program. Therefore, if <em>any</em> <code>lituse</code> is paired with a
104 <code>literal</code> relocation, then <em>all</em> uses of the register set by
105 the <code>literal</code> instruction must also be marked with <code>lituse</code>
106 relocations. This is because the original <code>literal</code> instruction
110 <code>literal</code> and <code>lituse</code>, but not a many-to-one. That is, if
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Remote-Configuration.html | 80 <dt><code>set remoteaddresssize <var>bits</var></code></dt>
89 <dt><code>show remoteaddresssize</code></dt>
93 <dt><code>set serial baud <var>n</var></code></dt>
100 <dt><code>show serial baud</code></dt>
104 <dt><code>set serial parity <var>parity</var></code></dt>
106 <code>even</code>, <code>none</code>, and <code>odd</code>. The default is <code>none</code>.
109 <dt><code>show serial parity</code></dt>
113 <dt><code>set remotebreak</code></dt>
116 <a name="set-remotebreak"></a><p>If set to on, <small>GDB</small> sends a <code>BREAK</code> signal…
123 <dt><code>show remotebreak</code></dt>
[all …]
|
| H A D | Values-From-Inferior.html | 77 an object of type <code>gdb.Value</code>. <small>GDB</small> uses this object
83 an example for an integer or floating-point value <code>some_val</code>:
89 <p>As result of this, <code>bar</code> will also be a <code>gdb.Value</code> object
90 whose values are of the same type as those of <code>some_val</code>. Valid
91 Python operations can also be performed on <code>gdb.Value</code> objects
92 representing a <code>struct</code> or <code>class</code> object. For such cases,
94 For example, if <code>val1</code> and <code>val2</code> are <code>gdb.Value</code> objects
95 representing instances of a <code>class</code> which overloads the <code>+</code>
96 operator, then one can use the <code>+</code> operator in their Python script
103 <p>The result of the operation <code>val3</code> is also a <code>gdb.Value</code>
[all …]
|
| H A D | Compiling-and-Injecting-Code.html | 17 <title>Debugging with GDB: Compiling and Injecting Code</title>
19 <meta name="description" content="Debugging with GDB: Compiling and Injecting Code">
20 <meta name="keywords" content="Debugging with GDB: Compiling and Injecting Code">
64 <a name="Compiling-and-Injecting-Code"></a>
70 <a name="Compiling-and-Injecting-Code-in-GDB"></a>
71 <h3 class="section">17.7 Compiling and Injecting Code in <small>GDB</small></h3>
72 <a name="index-injecting-code"></a>
74 <a name="index-compiling-code"></a>
76 <p><small>GDB</small> supports on-demand compilation and code injection into
82 <dd><a name="index-compile-code"></a>
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Remote-Configuration.html | 80 <dt><code>set remoteaddresssize <var>bits</var></code></dt>
89 <dt><code>show remoteaddresssize</code></dt>
93 <dt><code>set serial baud <var>n</var></code></dt>
100 <dt><code>show serial baud</code></dt>
104 <dt><code>set serial parity <var>parity</var></code></dt>
106 <code>even</code>, <code>none</code>, and <code>odd</code>. The default is <code>none</code>.
109 <dt><code>show serial parity</code></dt>
113 <dt><code>set remotebreak</code></dt>
116 <a name="set-remotebreak"></a><p>If set to on, <small>GDB</small> sends a <code>BREAK</code> signal…
123 <dt><code>show remotebreak</code></dt>
[all …]
|
| H A D | Values-From-Inferior.html | 77 an object of type <code>gdb.Value</code>. <small>GDB</small> uses this object
83 an example for an integer or floating-point value <code>some_val</code>:
89 <p>As result of this, <code>bar</code> will also be a <code>gdb.Value</code> object
90 whose values are of the same type as those of <code>some_val</code>. Valid
91 Python operations can also be performed on <code>gdb.Value</code> objects
92 representing a <code>struct</code> or <code>class</code> object. For such cases,
94 For example, if <code>val1</code> and <code>val2</code> are <code>gdb.Value</code> objects
95 representing instances of a <code>class</code> which overloads the <code>+</code>
96 operator, then one can use the <code>+</code> operator in their Python script
103 <p>The result of the operation <code>val3</code> is also a <code>gdb.Value</code>
[all …]
|
| H A D | Compiling-and-Injecting-Code.html | 17 <title>Debugging with GDB: Compiling and Injecting Code</title>
19 <meta name="description" content="Debugging with GDB: Compiling and Injecting Code">
20 <meta name="keywords" content="Debugging with GDB: Compiling and Injecting Code">
64 <a name="Compiling-and-Injecting-Code"></a>
70 <a name="Compiling-and-Injecting-Code-in-GDB"></a>
71 <h3 class="section">17.7 Compiling and Injecting Code in <small>GDB</small></h3>
72 <a name="index-injecting-code"></a>
74 <a name="index-compiling-code"></a>
76 <p><small>GDB</small> supports on-demand compilation and code injection into
82 <dd><a name="index-compile-code"></a>
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/binutils.html/ |
| H A D | windres.html | 70 <p><code>windres</code> may be used to manipulate Windows resources.
73 <p><em>Warning:</em> <code>windres</code> is not always built as part of the binary
83 <p><code>windres</code> reads resources from an input file and copies them into
87 <dt><code>rc</code></dt>
91 <dt><code>res</code></dt>
95 <dt><code>coff</code></dt>
103 <p>When <code>windres</code> converts from the <code>rc</code> format to the <code>res</code>
105 <code>windres</code> converts from the <code>res</code> format to the <code>coff</code>
106 format, it is acting like the Windows <code>CVTRES</code> program.
108 <p>When <code>windres</code> generates an <code>rc</code> file, the output is similar
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/binutils.html/ |
| H A D | windres.html | 70 <p><code>windres</code> may be used to manipulate Windows resources.
73 <p><em>Warning:</em> <code>windres</code> is not always built as part of the binary
83 <p><code>windres</code> reads resources from an input file and copies them into
87 <dt><code>rc</code></dt>
91 <dt><code>res</code></dt>
95 <dt><code>coff</code></dt>
103 <p>When <code>windres</code> converts from the <code>rc</code> format to the <code>res</code>
105 <code>windres</code> converts from the <code>res</code> format to the <code>coff</code>
106 format, it is acting like the Windows <code>CVTRES</code> program.
108 <p>When <code>windres</code> generates an <code>rc</code> file, the output is similar
[all …]
|